At 06:16 AM 2/13/2003 -0500, David A. Desrosiers wrote:
This is a very hard message for me to respond to without slipping off topic. I've tried five times over several hours without success. I have both a Palm IIIc and several Compaq iPaqs (for development.) The iPaqs have much higher resolution, can view HTML natively, support file and directory structures, and are a lot easier to program for. And I barely touch them except to whore myself for money. They -feel- less powerful, less usable, although it's very hard to quantify why.> Does anyone have knowledge about development of Viewer Code for the Pocket > PC? How far along is the development? Is there any functional beta or > otherwise available?The code exists, and is awaiting someone to take the initiative to port it. No, a beta does not exist, and as far as I know, there are no Plucker developers is working on it. Porting it to Windows doesn't really interest most of the Plucker developers. It awaits someone else to step up and attempt to do it.
Since I did some Py-Plucker coding, some C++ Desktop coding and PlkrData, I considered porting Plucker to wince. But I can itemize why I haven't and probably won't.
1. I suspect anyone with both systems will use the Palm OS one more, so they won't care about wince. I might be wrong; the Pocket PC seems superior on paper and in a quick glance, but long-term usability doesn't feel right.
2. Anyone who is using exclusively the Pocket PC... doesn't need Plucker for offline web browsing. They can use a regular spider such as HT Track and then, very easily, simply copy the entire structure over to the PPC where it will load-and-run just fine.
3. I don't do hobby programming on the PPC. The Plucker Python code, the Desktop stuff, the open source Java I've done... all that was fun AND I can use it. The PPC is easy enough to program for, but it's not fun and I wouldn't use it.
Maybe a more committed PPC developer will come along, but that's unlikely for a fourth reason...
4. If you have a PPC and are a power-user, you already know about #2 and other solutions; you aren't likely to even hear about Plucker.
</soapbox>
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
