Me again, Thinking about it a bit more it would probably much better if the HTML form that the JS worked on was not the same as the one the user is filling in. So you have a fancy form generated by GWT and an underlying very simple one that the JS works on.
Some advantage are: 1) The JS should never touch your real form (difficult to sandbox though!) They could call "alert" or window.location... XSS fun... 2) If your MyTextBox stores its state in something like http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/dom/client/TextAreaElement.html to go to/from HTML. So, as you describe, in preview/edit mode you would have a natural way for Widgets to add themselves to the model. 3) The fancy form the user sees could be very different to the abstract model form. And you could evolve this without breaking the model. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
