Cove583 wrote:I tried using GWT designer using a class inherited from a class inherited from the Composite class (much like all of the GWT Kitchen Sink classes that are derived from 'Sink'.
Cove583 wrote:I tried several sample cases and each time I got a designer error.
Cove583 wrote:What are the design goals of GWT designer?
Cove583 wrote:Is the design such that I should be able to look at the designer view of a GWT element regardless of how I have constructed my classes?
Cove583 wrote:That is, is this just a matter of working out the kinks of a new product, or are there deeper design issues here?
Cove583 wrote:I certainly understand that parsing Java code is not an easy task and my hat off to you all for trying.
Cove583 wrote:it would be helpful if the designer placed all of it's generated code in it's own method, (such as a designerInit() method)
Cove583 wrote:in order to seperate it from the rest of the code- and then in turn, attempted to parse only this method.
Cove583 wrote:This would help drive home the understanding that making substantial manual modification to the designer generated code might cause the parser to fail.
Cove583 wrote:then additional manually created GWT code could be written outside the scope of the designer(if desired) without concern about the parser.
Cove583 wrote:GWT Designer has the potential to be greatly beneficial from a productivity point of view, but I would not want the use of it to preclude a good inheritance design of the UI.
Users browsing this forum: No registered users and 3 guests