OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

2 Pages V  < 1 2  
Reply to this topicStart new topic
> Call For Zync Plugin Developers, NEED PLUGIN DEVELOPERS
cyphactor
post Feb 22 2005, 02:12 AM
Post #16





Group: Members
Posts: 40
Joined: 20-October 04
Member No.: 5,123



QUOTE(eji @ Feb 21 2005, 07:48 AM)
I'd like to put in my vote for syncing to OS X using zync. I don't have any programming abilities to speak of, but I can put myself to work as a guinea pig if you need help. I'm running the latest version of OS X and using an SL-6000, a configuration a lot of users seem to have but developers don't.

What I'd really like to see is syncing to/from the DTM using the standard Apple apps: iCal (uses .ical format, just like KO/Pi) and Address Book (.vcf, though KA/Pi is struggling with v3.0). Even better would be integration with iSync. Tiger (OS X 10.4), as I understand it, is opening up the iSync API so developers can integrate it with their apps system-wide, and developer copies of Tiger are available all over BT sites. I already have two major PIM suites on my iBook, Apple's and Microsoft's, and adding KOrganizer to that would seem to be overkill.
*


If I had a Mac (I am working on aquiering one right now) I would be working on integration with Mac. I have been talking to a couple of people who have taken the code and compiled it on Mac and am going to start working on debugging it and making sure it is portable to Linux and Mac. I will need all the Mac testers I can get.
Go to the top of the page
 
+Quote Post
cyphactor
post Feb 22 2005, 02:44 AM
Post #17





Group: Members
Posts: 40
Joined: 20-October 04
Member No.: 5,123



QUOTE(marshmn @ Feb 22 2005, 09:29 AM)
cyphactor,

Firstly, thank you for what you are doing, I'm sure that there are a lot of people here who will appreciate some way to sync with Linux apps such as kdepim, evolution etc...


Well, thank you very much for your acknowledgment of all my hard work and efforts in this project.

QUOTE(marshmn @ Feb 22 2005, 09:29 AM)
I just can't help thinking that OpenSync would be a much easier solution, which would provide quicker results, and would be much easier to maintain in the future.

It seems to me, that OpenSync would allow you (and anyone else that helps) to concentrate on the Zaurus side of things and getting that right. No need to worry about all the different PIM software out there as other developers will be able to take care of that. Also the infrastructure etc will all be done for you. And when Evolution changes something, well you should just be able to pick up the new Evolution plugin for OpenSync and off you go. If you continue with this project as-is then you'll constantly have to maintain plugins for all the different PIM software.

The pool of developers working on OpenSync is bound to be greater than those working on Zync, purely because OpenSync will have a much broader user base and hence interest will be naturally higher, does it not make sense to tap into this?


Yes, OpenSync did, from the initial perspective, look like a much easier solution. Such, that would provide quicker results and would be much easier to maintain in the future. However, after looking at the OpenSync code and the way it is setup I decided that it would take me longer and be more painful to implement the Zaurus sync into OpenSync. You are totally correct about the problem with maintaining plugins for all the different desktop PIM applications. This could stand to be a huge problem depending on how much the APIs for integrating with the PIM applications change. Hopefully they won't change very much and it won't be two hard to maintain them.

I also have designed the plugin interface for Zync so that it is very very easy to write plugins.

QUOTE(marshmn @ Feb 22 2005, 09:29 AM)
I do understand your issues with all the dependancies... I think this is one of the biggest problems for a lot of users with Linux... they try to install an app, find it needs x number of dependancies, each of which require x more etc etc... I've been there, and yes it's a pain... it's getting slightly easier with things like APT, but still. I still think that painful as this is though, it's still got to be easier than implementing, effectively, a duplicate of OpenSync...

Just my 2 cents... and caveat here - I don't even have a Zaurus yet!

Good luck with whatever you decide, and when I get my Z I may even be tempted to help...


I am still going to stick with going the direction I am. Beyond the dependency problems, ugly design / lack of code docs / etc, in my opinion (no offense to designers, I just think it could have been done better. I do understand it is in early dev stages but still.), there is also the problem of making it portable. It will be a lot easier for me to tackle my infrastructure and plugin API in making them portable than it would be to do it with OpenSync (that is without adding even more dependencies).

I already have pretty much everything implemented except for all the plugins. The To-Do plugin should be very stable I have been using Zync and the KOrganizer To-Do plugin for a while and have had no problems. I am working on changing some internals in the Zaurus sync protocol implementation to make it better designed and better implemented along with making it more robust so that if a new version of the DTM sync protocol comes out zync will be able to handle it without any code changes.

Let me know when you get your Zaurus, I can use any help in testing or development that you can give.
Go to the top of the page
 
+Quote Post

2 Pages V  < 1 2
Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 1st September 2014 - 01:01 PM