On Thu, 2003-10-30 at 07:31, Laurens wrote: > My excuses if this is a stupid question but with a 400 Mhz CPU and 64 MB of > RAM in my T3, I am wondering why there is no Plucker Parser available for > the Palm itself. It could fetch internet pages over Bluetooth or Wifi and > liberate me from my PC.
Two reasons:
1.) Because Plucker was designed to be a client-driven solution,
using the desktop/server hardware and processing power to
render the pages into the Plucker document.
2.) Nobody has written one yet that we've seen.
The space considerations to store "real" HTML (with all of the
extraneous stuff we ignore anyway, like Javascript, CSS, comments, etc.)
and then temporary "scratch" space to convert that into a Plucker .pdb,
and then the final .pdb file itself are prohibitive (think 3-4x the
space of your actual "fetched" content so you can read it offline). It
would be simpler to just write a web-browser instead to render webpages,
and have Plucker call/reference that, and store everything in a
semi-peristant cache of some sort.
There are at least a dozen Palm-side web-browsers already, so it would
make sense to not try to reinvent that wheel, AND maintain the Plucker
codebase at the same time (i.e. code for two separate projects).
Incorporating the Palm NetLib functionality into Plucker + the parser +
the space requirements would really bloat the application by an enormous
amount.
But if someone wants to write it up or submit some patches, I'm sure
nobody would have a problem reviewing the code.. ;)
signature.asc
Description: This is a digitally signed message part
