Use ClientBundle in a large Enterprise Application?

Question

We\'re building a large enterprise application (dozens of modules) with GWT and need to decide whether to use ClientBundle or not. I was curious what pros/cons the StackOver

Answer 1

I have been using client bundle heavily in m-gwt.

One thing that was bothering me was styling for devices that did not have dev mode. So styling could mean recompiling the complete app.

Mostly all CSS3 Rules can be used in ClientBundle by using the literal function, so that should be okay. It gets a little tricker with @media queries. You can inject the css as a simple textresource as a workaround, but its kind of ugly.

When you are talking about several gwt modules, consider using multiple clientbundles so you can still use split points to keep the download file size under control (Depending on how big your .js files get)

I have used clientbundles in several big gwt apps and for me compile time checking and refactoring support beats the little quirks that are still in client bundles.

Answer 2

Just two additional notes:

• There is a utility available in GWT which allows to automatically create the interfaces for your CSSResources
• It's true that debugging styles can be a little bit cumbersome because of the obfuscated names. I had good success by using Firebug to change styles in dev-mode directly in the browser and when I am satisfied I change them in my GWT app.