On 19 oct, 01:37, PJ Gray <[email protected]> wrote:
> I have used GWT for a while now, both on a large project and on small
> experimental projects. However, I am still somewhat of a newbie...
>
> One thing I am confused about is the ideal workflow for a UI designer when
> working with a GWT project. In a perfect world, I would want everyone to
> be working on something that would actually be used, even in the design
> phase. However, if a designer makes a HTML mockup of a design, how can
> I leverage that in GWT? What do other projects do? Other than using
> some of the CSS and the images by hand, I see no way to easily use the html
> itself.
HTMLPanel might help in reusing HTML fragments.
> Is this what UIBinder is supposed to provide?
Partly yes (it uses HTMLPanel behind the scene)
> I really want something that would take in a html design and spit out the
> GWT source code.
The "problem" is that your designer won't use <ui:mph> or GWT widgets,
and it probably won't use CssResource specific syntax helpers (@def,
@if user.agent ie6 { }, etc.) so you'll have to copy/paste/adapt, and
rinse/repeat when the designer has/wants to change something. Ideally
(imo), the designer will start by making a "pure HTML" mockup and then
transform it into an *.ui.xml, and only then the programmer enters
into play (eventually tweaking the ui.xml to add ui:field and the
like; ideally in coordination with the designer)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
