Hi all, As you probably all know by now I have developed a Plucker Reader for the Zaurus. For this platform the palm database format (pdb) which the Plucker format is based on is more hindrance than help (except for supporting random access) because there is no built in library so it has to be decyphered from scratch.
Having said that, overall it works very well and with the Plucker format overlaid on top its fantastic. However, given that the pdb format is artificial on the Zaurus in the first place, would there be huge opposition to having a more "heavy-weight" version of Plucker for non-Palm devices with a modified database format? The two main differences I have in mind is that the length field in the database headers and text headers etc be expanded to 32 bits and maybe adding support for other graphics formats (oh, and changing the version number in the header so readers which choose to do so can support both formats simultaneously). This would address the most common observations re breaking up pages into 32kb chunks and limiting graphics to 60kb. So does this sound reasonable, or is it total anathema? And if it is reasonable, are there any gotchas if I'm going to modify the distiller and my reader to handle it? (One obvious thing is not to preallocate the data for expanding compressed records to the maximum possible size of data =8^O ). Comments? Brickbats? Alternative approaches? Cheers Tim _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
