What I want to know, before I start trying to implement it, is if anyone else is working on this at the moment, so I can avoid duplicating large amounts of work.
What I'm considering starting out with is a simple system to create entries offline and store them, with syncing to the livejournal (or other service) server. It would be useful in the future to have support for downloading the user's entire journal and keeping the local entries synced with the server, so for the purposes of editing old entries (and maybe, if possible, even replying to comments) it would be completely irrelevant whether or not you were connected to the net until you wanted to sync. Support for editing entries from multiple services and syncing them all at once would also be a neat feature, but probably not something that's necessary to do immediately.
Related to this would be a Palm conduit that works in OS X, but if the AvantGo people can't figure out how to do it (and even Palm took a really long time to do the basic necessities for X), I don't think I'll be able to either.
- Current Mood:
contemplative
Comments
I'm gutted. Bleh!
I think I'd pay for 10.2 if iSync included Avantgo support.
I really wouldn't expect iSync to support AvantGo, but it would be really nice if iSync is easy to add conduits to, and if Apple released a conduit development kit that didn't require CodeWarrior, that'd be nice too.
Maybe Apple will realize that turning the iPod into a PDA with no input is kind of pointless, and they'll just buy out Palm.
As for buying out Palm... I think that would be a really bad move, and would generate a lot of bad feeling or result in Apple having to have its fingers in stuff they might not want to.
Now, just making a Palm OS handheld, that could make sense. They don't have to buy Palm to do it (Sony didn't, IBM didn't, and Handspring certainly didn't).
Of course, any Apple PDA is going to arrive too late for me. If I'm going to replace my currently unused Palm V, I'm probably going to do it this month. :o)
Unfortunately, this is a pretty big project since the iJournal code as it's written is a bit of a mess; it good for what it does now, but for handling more than one entry at a time it looks like it will need a pretty substantial redesign.
It almost is starting to look to me like it would be better to write a new client from scratch that takes the best of iJournal's design and Yax's functionality, but I'm not quite masochistic enough to try that