We are in the process of buying a couple of Instantiations GWT
Designer licenses. The WYSIWYG capability in their tool is not very
flexible, though. We were not able to create any useful screens using
the WYSIWYG feature alone. Had to do a lot of manual tweaking.
On Dec 5, 9:16 am, rakesh wagh
After I started this thread, a new article has come up on the GWT blog
which talks about how the folks at studyblue.com approached the
styling issue. Here is the link to the post:
http://googlewebtoolkit.blogspot.com/2008/12/gwt-no-need-to-shortchange-your-style.html
On Dec 6, 10:02 am, Chii
I fully agree with this way of working.
We've been able to work with web designer with a very similar way of
working.
Our GWT components are very simple, and all the style is managed by CSS.
I think that it's really important to keep in mind that GWT is not a Swing
API in disguise :-)
2008/12/9
I would think Dreamweaver is more or less redundant in a GWT project,
save perhaps for doing mock ups of widget layouts for demo,
discussion. The traditional distinction between page designers and
Java server programmers no longer exists really with GWT. You write
GWT client code in Java, but you
Here are few things to consider:
- Check the Instantiation Designer tool. Personally never used it
beyond evaluation... but you and your team might have some luck with
it.
- Let the HTML team design the layout. Let the GWT team design the
application and place the components as per the layout.
Are there any best practices in bringing together a multi-disciplinary
team of Java developers and HTML/CSS designers in developing a
commercial GWT application? Our Java guys cannot do CSS and our HTML/
CSS guys prefer working in DreamWeaver. I haven't seen any material
that talks about the team
