David A. Desrosiers > > the default really should be not to submit forms. > > ... [how to decide] when a form is to be treated like > > a link
I think that it almost always safe to spider the results of a form; the only question is whether to post the form in the first place. > Here's a problem.. not everyone uses a Palm in a cradle to sync > their Plucker content. What this means, is that with the > implementation of > forms support in Plucker, you now need a way to fetch the > form data back OFF > the Palm handheld, post it, parse and collect the results of > that post, and > then push that back to the Palm. Definately changes the way > Plucker works, > and the earlier main design goals (client driven, > disconnection operation). Sometimes the data will be known in advance. (Example: plucking a weather or map site for a known location.) That doesn't cover all forms, but it covers a fair number - including the ones that sparked this. To get the data off - plucker can already export an url to memopad. Could it also export data? I think there was an experimental version (by masakaze?) that took the memopads as new urls to launch, or some such. How hard would it be on the viewer side to (1) recognize variables, including default values (2) allow editing the values (3) put them into a memo (or even a new database, so long as it had the backup bit set) As in, should I look at what I would need to do on the parser side, or is this hard enough that I'll have to wait until I'm ready to do both ends? >What about forms that (incorrectly) use Javascript to validate > input, or draw buttons and checkboxes? javascript support would not be in version 1 of forms processing. :D -jJ _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
