Hi Mathew, On Sun, Dec 19, 2010 at 5:55 PM, Matthew Hill <[email protected]> wrote:
> Thanks for posting this. It's really my pleasure, Mathew. > > A suggestion for your app: please style the widgets rather than leaving > them as default. > Many of the GWT widgets are very bland and that's putting it mildly. I've also found that some are almost impossible to style both in appearance and in dimensions when using UiBinder such as the TabLayoutPanel which I find very frustrating. It also seems that there are 2 'classes' of Widgets in the GWT framework as far as styling is concerned: there are those that allow a direct override of their default styles via a stylesheet with selectors and attributes matching those the widget uses internally and those that don't and I don't understand why there is this discrepancy. Being able to easily apply styling using css should be a given with any widget framework yet GWT makes this difficult to sometimes impossible. I've got a million good things to say about GWT but this is definitely one area where I believe it needs a major improvement and overhaul, even if it meant that the framework implement code-breaking changes to make this happen. My understanding is that a theme's css selectors are the last to be applied which means that they override everything you do in your application's style sheets and inline style declarations. I understand that because that is what the documentation says but the same documentation also suggests several ways to override this yet I have been unable to do so and to be quite frank the documentation doesn't adequately provide decent examples for each of the suggested ways, especially where you are using UiBinder. And like I infer above, it shouldn't require a lot of documentation to support styling as it should be just a matter of applying a style via css, either in a style sheet or inline. And all that should be required to document a widget's style should be to list the widget's css selectors. That's it! So, about your suggestion that I style the widgets rather than leaving them at their defaults, I've decided to proceed along with development as is and once all the functionality has been implemented to then go back and focus on styling. If I cannot style a default widget I will write my own as a replacement. It isn't something I really want to do and spend my time on but if I have no other choice then what can I do? -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- *Jeff Schwartz* -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
