Hi Mike The source is always available from http://cvs.handhelds.org/cgi-bin/viewcvs.cgi/opie/ under noncore/apps/opie-reader but that tends to be out of date (because I don't have direct access to the cvs due to firewalls etc) so you can request it direct from me at any time.
I slipped up a bit with the first version because the example texts I was using were novels I didn't appreciate the importance of navigational keys (back/forward) so I'm just fixing that then there should be another release at the weekend. Its support for Plucker isn't ideal because it was always intended to be a linear text reader rather than a hypertext reader but is works surprisingly well - especially given the amount of stuff I haven't quite worked out from the spec yet 8^). Expect some more questions about these once I've sorted out the basic functionality. The first one is: How come I can't convert all the Palm graphics files into pngs using netpbm? This has temporarily stalled my adding graphics support - it could be that I've misinterpreted the format for graphics inserts but some graphics files convert okay. It would save me from a lot of head scratching if there is a known limitation in the reverse graphics translation process or if you have a pointer to the correct way to do the translation. Then I could focus on the right problem - my understanding of the Plucker format 8^). BTW it runs under QT-embedded. Changing it to run under standard QT would be trivial if anyone wants a QT version. Similarly the Agenda version runs on fltk which is a very small toolkit running on X. Anyone wants to have an X version can just install fltk and recompile the Agenda version (might need some source changes now, it didn't used to though). You could very easily add QT and X to your list! Having said that it doesn't look brilliant on larger screen devices so I can't imagine it going anywhere except Zaurus, iPaq and Agenda devices, but you never know. Also, I suspect the dedicated Plucker readers are likely to handle Plucker documents better though QTReader should be an adequate stop gap for anyone who wants one now. I'd welcome your comments on how I've interpreted the Plucker spec as I suspect I haven't necessarily got it all correct 8^) and I know that I have completely ignored the paragraph attributes and haven't taken advantage of the record type index for efficiency - but I had a bit of a tight deadline for the first release (1 week from start of coding to release with a day job to go to!!!!). Send me an e-mail direct and I'll reply with the latest source once I added the navigation stuff - probably Sunday night. Cheers Tim > Message: 9 > Date: Fri, 20 Sep 2002 00:03:49 +0200 > From: Michael =?iso-8859-1?Q?Nordstr=F6m?= <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: QTReader (was: iSilo vs. Plucker) > Reply-To: [EMAIL PROTECTED] > > On Thu, Sep 19, 2002, Tim Wentford wrote: > > BTW I posted an announcement to the announcements list re QTReader > > (www.timwentford.uklinux.net) but haven't seen it yet - is that list > > working? > > I don't know how the announcements list works (maybe it is > moderated?). I will check with Mark. > > I don't have a Zaurus, so I can't test your QTReader, but it seems > to be a cool reader. That would mean that we now have readers for > PalmOS, any device that include support for GTK, and now also any > device that includes support for Opie. > > Is the source code for your reader available, too? It would be > interesting to take a look at how you implemented the Plucker > support. > > /Mike _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
