Good idea--a very focused solution. I like the way you think Hans. The more precise our grasp of the problem, the cleaner the solution.
Still not sure how it would work. I don't know a way to easily generate all the command words, especially given that plugins may exist. Ideas? In the action.data example, we could check no reserved field name appeared in the csv list, and abort the form with a warning if that occurred. But it is a very specialized kind of case. Are we overlooking other kinds of places this problem might come up? Would it be easier to create a command that "deactivates" certain reserved words so they could be stored safely, or better, limits the commands that trigger actions in a form somehow? For instance if we put something like [session activecommands savedata] at the beginning of the data action form we could save any field we wanted and retrieve it fine. Only one command would do anything in that form. Just brainstorming. Don't know what the code would look like, just trying to find the neatest solution. Cheers, Dan On Tue, Oct 6, 2009 at 11:22 AM, Hans <[email protected]> wrote: > > Perhaps it is enough to add input validation for critical forms to > prevent use of 'command' words. > Input errors happen, and input validation can be a powerful tool. > It needs good markup though, ideally so error messages can appear > beside input fields, to draw attention to where the wrong or missed > input happened. > Call it 'inputcheck' or something like that, a new command, which runs > before any other commands can run. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
