I would recommend installing WebKit.
xulrunner is only needed for Linux distros that don't have WebKit
installed.
These are typically older Linux distros that have xulrunner 1.9.x
installed.
On May 13, 8:20 am, Thad thad.humphr...@gmail.com wrote:
Okay, this was a dumb question brought on by too little sleep and too
much office time. The solution (of course) is to rename the
*View.ui.xml file to *ViewImpl.ui.xml. Duh!
Now my stumbling block is the version ofxulrunner. In Eclipse 3.6,
WindowBuilder wants 1.9.1.x or 1.9.2.x. I'm running openSuSE 11.4, and
it hasxulrunner-2.0.1 installed. I've tried `ln
-sxulrunner-2.0.1xulrunner-1.9.1.17` (just picking a version one up from an
old one)
but that didn't work. I'll dittle with this for a while (though
considering past frustrations with WindowBuilder, I dunno why).
On May 12, 6:42 pm, Thad thad.humphr...@gmail.com wrote:
I'm starting a new project. Unlike previous project which stumbled
along fromGWT1.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/
GWTDesigner. I'd tried it way back withGWT1.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
recommendedGWTpattern and
requirement ofGWTDesigner
So what gives? It seems odd that inGWT2.3.0 the WindowDesigner tool
won't work with a naming convention that theGWTteam 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 google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
