On Thu, 29 Apr 1999, Alan Johnson wrote:
> I was aiming for a sort of HTML <form></form> to PalmOS Form resource
> converter. The HTML file would be converted into a PalmOS Form via a desktop
> app then inserted into a .prc file.
It strikes me that using a real Tfrm resource probably isn't the best idea
for this, as it ties you to the (undocumented, I believe) resource format.
Better to use your own data format, and then use the dynamic control
creation routines to construct the actual form on the device at run-time
from your representation.
> Of course there would have to be some kind of mapping info so the PalmOS
> app would know what kind of HTML form elements they are and how they
> translate into records in a .pdb file. But that kind of mapping would be
> simple compared to actually creating the form resource from the HTML
> <form></form> code.
I don't see them as separate steps, actually. You have to turn an HTML
form into a representation of a PalmOS form. You then need to translate
that representation into an actual form, but we can handwave that part
away as obvious, since it is a direct one-to-one translation. Figuring out
what to do with the HTML is the interesting bit.
> I was curious to see if it could actually be done of
> if someone had alternative ways to do it.
I'd look at both AvantGo and Satellite Forms -- perhaps there is
something there that already suits your needs. Oh, and have you looked at
the Web Clipper application on the Palm VII?
> --Alan
>
> > You mean normal PalmOS forms? I don't think this is a very meaningful
> > question, as there is no logic for the desktop to "unpack" a form
> > resource, and I don't think form resources were actually meant to carry
> > the dynamic contents of the visible form -- you can't "freeze" and "thaw"
> > forms on the device, after all. It seems like it would be simpler all
> > around to just iterate over the pieces of data you are interested, and
> > store them in a resource in a custom format you are happy with. If the
> > user can design the form (somewhere...) you should have the data you need
> > already available.
> >
> > Kenneth Albanowski ([EMAIL PROTECTED], CIS: 70705,126)
--
Kenneth Albanowski ([EMAIL PROTECTED], CIS: 70705,126)
