> Inline style in each UiBinder xml file will not be maintainable. > From a code maintenance perspective stylesheets should be used > extensively. >
Its not maintainable by designers if they quickly want to see changes because they would need to recompile the application. Super Dev Mode helps here a bit but is definitely a different workflow for designers. But if your developers maintain the CSS itself it works pretty well because you dont have to search the CSS...its just there. -- User does not have the ability to change/select alternate CSS files > -- Prevents the application from being re-labeled by an OEM SaaS unless > you also provide source code > These two points alone nearly rule out ClientBundle if you do not want to expose your source code and/or you dont develop the new re-labeled theme for a client in-house. For these two use cases its probably the a good solution to just put all CSS into your database, provide a suitable edit widget for your customers, and make your host html page a dynamic page (e.g. jsp) so you can embed the customers CSS dynamically. > -- Now you have to maintain and keep in sync three separate items. Class > name in CSS, Variable Names in CssResource file, declarations in UiBinder > XML File > In general GPE / IntelliJ tells you that something is not in sync. So for a SaaS that should support themes defined by customers I would not use ClientBundle, because ClientBundle means that a change inside the bundle needs a recompile of your app. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
