Databases
StackOverflow2013
Postsdbo
POGWT and CSS Development Best Practices
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGWT and CSS Development Best Practices
    text
    copied!<p>I am wondering what the best practices in developing an application where an external CSS developer is involved in designing the look and feel of the site?</p> <p>Ideally, they would be creating CSS files that we could easily integrate into the site over multiple iterations, and the development team would not have to do any manipulation of these files (obviously there would be HTML or template changes to point to the appropriate classes).</p> <p>GWT documentation (http://code.google.com/webtoolkit/doc/latest/DevGuideUiCss.html) lists four approaches:</p> <ol> <li>Using a tag in the host HTML page.</li> <li>Using the element in the module XML file.</li> <li>Using a CssResource contained within a ClientBundle.</li> <li>Using an inline element in a UiBinder template.</li> </ol> <p>The documentation suggests that modern applications would tend to use approaches 3 and 4, however these seem intrusive to the development process, as we do not want to have to constantly update CssResource interfaces with changes to the CSS each iteration (in approach 3) or have to chop and split the CSS files to inline them into our ui.xml files (in approach 4).</p> <p>We are thinking of using approach 2, and hand coding the CSS classes. This would allow us to easily drop in CSS file updates and not have the developers need to touch them. We would lose obfuscation and there would be some work to manage changes to CSS names, though no more than the other approaches. Are there any other considerations I am missing? </p> <p>Is there a best practice for building GWT applications where external CSS designers are involved?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload