I'm with you that it seems very low level. If your users know enough to write that much JS then they would probably be better off with proper developer tools!?
So as you say, same engine but with more complete wizards might be better. > My key question in former posting thus becomes how to get these code > snippets running in the preview and production window (the objects & > wirings behind the scenes)??? I'm afraid I don't really see the problem here. > Simple string copies into specific dom objects ... seem not to be > sufficient, seem they? In their example you would probably have to do something like reload the constructed page so script tags would be processed and old event handlers replaced/ removed. In the design I was talking about, because the HTML/DOM, is just the data model/config you would just have to tell your Widgets to refresh themselves. If you like Form Boss then you might be better off keeping it simple (like them) and just working on a chunk of HTML. Is certainly the most flexible way of doing it. Quite a few off the shelf WYSIWYG JS editors that let you write custom editor panels. Not very GWT though ;) On Aug 12, 5:18 pm, "A.Augustini" <[email protected]> wrote: > Hello Sam, > hello everybody: > > @Sam: I've have to "digest" your thoughts in your 2 last postings a > little bit... > > ...but for the meanwhile: today I found "Form Boss II", a commercial > form wizard tool with an "interesting" ui and -- more important -- > some features that are close to mine. I think that these short intro > vids (<= 4 mins each) could make more comprehensive what I'm trying to > achieve in GWT. > > 1.http://www.formboss.net/j-wiz > [especially last third of the vid on surveys] > > 2.http://www.formboss.net/features > =>vid2 "Conditional Fields" > also useful: > =>vid1 "Conditional Page Logic" > (modified php logic for page routing) > > Here you'll see a "multi-page form editor" with in-place edit > functionality. The interesting part is "Conditional Processing" > subpanel where endusers can compose some script code via event & > operation, ... selection fields. > IMO the "drawback" still is that the enduser (form admin) still has to > provide hand-written script routines (see "Extra Head Code" panel in j- > wiz vid). [Maybe this could be taken a step further hiding this script > programming text area behind a more graphical ui -- comparable to the > "Conditional Processing" panel's one]. > > My key question in former posting thus becomes how to get these code > snippets running in the preview and production window (the objects & > wirings behind the scenes)??? > Simple string copies into specific dom objects ... seem not to be > sufficient, seem they? > > Kind regards, > Alessandro -- 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.
