Ruben Malchow wrote: > [tables - which Chris just fixed]
> [fonts - Alex needs more detail] > >(As Alex mentioned, you could write your own onboard > >interpreter -- there are even python and java environments > >for a palm that you could use with the current parsers -- > >but I wouldn't recommend it for speed.) > well, openwave and similar commercial products do run ok > on a cellphone There are tradeoffs with different environments. Python is good for programmer time, but not always so good for running quickly in a very limited environment. The same is true of java, except that the phone makers have often built in some help for it. If you want fast parsing on the palm, I would recommend C. That is one reason the viewer is written in C. If you want fast development, then C may not be the best choice. There are actually libraries (like wwwlib) that already do most of it -- but it was still faster to rewrite in awk/perl/python/java. > oh, one more thing concerning size: with the mainstream boom > in digital cameras, smartphones and the like, i would bet that > storage prices (like cf- mmc- or sd-cards) will become _very_ > cheap. indeed, it already is amazingly cheap - 128 megs for > 50 eur is not all that expensive. Eventually, yes. But not everyone is using a palm that can even take external cards. I am now -- and have noticed that access to the card is very slow. There are also limits to the working memory, though these have certainly grown. (You can still find web sites telling how to upgrade from 256K; new machines often start with 32 Meg.) If you're buying new units anyhow, that probably changes your perspective. If you wait two years, things will have changed anyhow. (I doubt anyone would have even tried to use anti-aliased fonts on the original palm pilot.) But for now, support of older machines is an important part of the project. -jJ _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
