On 8/3/2011 7:56 PM, Nick Apperley wrote:
Is there a way to do a clean build from scratch?
You can always delete the compiler output (including .class files). If
you're using Eclipse, the "clean" function will accomplish that task.
When a compile is
done is any caching involved?
I think the answer at the level of problem you're having is "no".
I qualify the "no", because if you are using Gin, and are using
development mode, and you change the Gin binding information, then it's
wise to recompile (i.e. restart development mode). That doesn't seem to
be the case here.
I'm fairly sure you will find the problem is some unexplored linkage
between the .java and the .ui.xml. I've outlined a resolution path
below. I know this can be frustrating. In cases like this, the wisdom to
strategically cripple your application is crucial to isolating the
failure point.
On Aug 3, 2:28 am, Jeffrey Chimene <[email protected]> wrote:
I see nothing there either.
I'd try a few things:
o Simplify the file. Use VerticalPanel or HorizontalPanel or a
combination of them to replace the g:grid when laying out the labels.
o Focus on getting a clean compilation w/o reference to the ui.xml
(obviously, it won't run...) Start commenting out the UiField and
UiHandler annotations one by one. Donotcomment out the field references.
o Does the Template Editor do anything interesting when invoked on this
ui.xml?
o Look at the generated javascript and see if you can find the linkage
to the Problem Child.
--
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.
