- Create a new servlet that extends HttpServlet to handle your dynamic resources
- Override doGet() and intercept requests to files you want to be dynamic, and fulfill the request from the database
- Ideally, remember when the user-defined css was last modified, and provide the necessary etag and last-modified headers, then respond with not-modified when appropriate to avoid sending css every time.
- Change your web.xml so that the dynamic resources are mapped to your new servlet
- add <stylesheet src='customised.css'/> or similar to your gwt.xml
- make sure this css is the last one specified by your gwt.xml (so its contents will override everything else)
Instead of loading from the database, you could make your sevlet load from a file if you want.
Paul
On 26/08/11 12:00, Otto Chrons wrote:
> We are trying out GWT 2.3 for the first time to develop a web
> application for professional users (not consumers).
>
> What is the best way to enable a web designer to work on customizing
> the UI, especially CSS, without having him work through the full GWT
> compile/package scheme? Ideally we would just compile the production
> version of the app, deploy it and the designer could then work with
> the "static" deployment and directly edit CSS files so that changes
> could be seen just by reloading the web page.
>
> - Otto
>
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment