Re: Organizing project files with UIBinder

Here's my quick stab at these, hope it helps.

1. I've never seen this done differently, and personally I find it helpful to have them in the same package.

2. UIBinder is only client side.

3. UIBinder will work with classic CSS. You could also consider using CssResource (gss) or using gss embedded in UIBinder templates.

On Monday, December 14, 2015 at 8:31:14 AM UTC-5, va...@ant.ee wrote:

Hello all,

        I have read the chapter http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html about GWT project layout, but still have some questions:

1. View .ui.xml files are "by default" located at the same folder where .java files are. Is it better to move them to some "resource" package?  How to bind .ui.xml in corresponding composite .java if so?
2. Going through UIBuinder example there is only "client" side that is executed at client browser. Is server side remains pretty much the same as described at http://www.gwtproject.org/doc/latest/DevGuideServerCommunication.html ?
   
3. If I have root .css (gss) at my WEB-INF -- will this resource be accessible for all .ui.xml modules ?

Thanks

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.