I'm starting a new project. Unlike previous project which stumbled
along from GWT 1.1 to till now, I'm trying to be a good Do Bee--I'm
attempting to use MVP and UiBinder as shown in the Contacts2 demo
(http://code.google.com/webtoolkit/articles/mvp-architecture-2.html).
(My project is both practical and a chance for me to try these
techniques.)
I also thought this would be an ideal time to try out WindowBuilder/
GWT Designer. I'd tried it way back with GWT 1.3 or 1.4, and wasn't
pleased. But now--my first UiBinder endeavor--I thought I'd give it a
go.
However, because of conflicting naming conventions between the MVP
example and WindowBuilder, I can't get WindowBuilder to open my
*.ui.xml file in Design mode. Here's an example of the error message
from the Contacts2 example (note this is copied right from Eclipse,
with all the formatting and missing /'s):
You are attempting to use UiBinder
for
Contacts2srccomgooglegwtsamplecontactsclientviewContactsViewuixml
however your form class
comgooglegwtsamplecontactsclientviewContactsView does not have a
UiBinder inner type subclass This is recommended GWT
pattern and
requirement of GWT Designer
So what gives? It seems odd that in GWT 2.3.0 the WindowDesigner tool
won't work with a naming convention that the GWT team espouses.
Is there a way around this? If I stick to the MVP example, it seems
that I can't use WindowDesigner. If I cave to WindowDesigner and drop
the ViewImpl implements View paradigm, what am I giving up?
--
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.
