No CSS style with GXT 3.0.0 grid.

No CSS style with GXT 3.0.0 grid.

Hello,

I got the same kind of warnings with my project. And also the user.agent property is ignored. We still have 6 permutations.

Moreover, I built 2 grids
- Using Ext GWT 2.2.5-gwt22, everything works fine. CSS style on the header looks as usual.
- But when I use GXT 3.0.0, the css style disappear completely. It looks like there is something wrong with the "BlueGridAppearance stuffs". I was expected to find the BlueGrid.css within the resource files in Firebug for example. But it is missing. I just got something like a default css getting the same name as our widget. I don't get it why it doesn't work as in the basic grid example, where no style properties are defined.

I have this problem in both hosted mode and during a normal compilation using Maven (gwt-maven-plugin 2.4.0, gwt 2.4.0).

I did a comparison between my grid built thanks to GXT3 and the one given as example. It appears that some CSS styles for my column headers (Border-right 1px solid #D0D0D0, border-left: 1px solid #EEEEEE, Font 11px arial,tahoma,helvetica,sans-serif and padding: 4px 3px 4px 5px) are not generated during the compilation.
That is why I get a strange column header. I can correct this issue by adding a setColumnClassSuffix() on each ColumnConfigs. Then I can add these missing styles manually for this redefined CSS class in the <head> tag for example. But this patch should be really temporary because warnings are still there. The InlineClientBundleGenerator still detect some problems. I bet this is the source of my bad CSS style.

We had a dependency to GWT Incubator 2.0.1 within the pom file of our project. This tool allowed us to handle some canvas. We just removed it. Then the compilation process and the look and feel of our column headers were OK.

I am sorry but I didn't dive into the source of this conflict. I didn't have time for that. But for instance, our GWT Incubator 2.0.1 is a deprecated project. Make sure that all your dependencies within your project are up-to-date before a migration. It should help a bit.

TillF - can you post your full .gwt.xml file so we can see what other dependencies you might have? Earlier on in trying to reproduce this we thought it was a Windows-specific issue, perhaps related to line-endings, but we've been unable to reproduce it on any of our test machines.

So far, zetomatoz's source of the issue seems to make the most sense, that some other library is interacting with GXT. I'll be looking into the specifics that allow Incubator 2.0.1 to interfere to try to pin down the exact piece that caused the problem. I'd be willing to believe that other libraries might have the same issue.

Having looked more closely at the gwt-incubator project as of version 2.0.1, it appears to have a prototype version of the same ClientBundle and CssResource that GWT now has internally, and that GXT's appearances are all based off of. GWT-incubator's defaults configure these features in ways that no longer make sense and include old versions of these classes - either remove GWT-incubator, or any other project with early copies of ClientBundle, or be sure that you override its values and classes with those found in GWT itself.