> This is easy to do... I even like more the old widgets then the new Cell > widget for css customization. Did you try it.... ? Because it's hard, and in many cases, espcially with dependent styles not possible! Have a look as this issue and the related topic...: http://code.google.com/p/google-web-toolkit/issues/detail?id=4903
I would love to hear how you do it? GWT is busy with many bugs, but it's all a mather of priorities... I am also sometimes frustrated about some bugs not being fixed... but that's the way it is...: it's open source and it's all a mather of priorities... I always manage to work around it, or fix them in some other way... About the GWT future: still no worries and confident of a robust GWT future with many awesome AJAX app's. On Aug 26, 2:25 pm, Christian Goudreau <[email protected]> wrote: > Didn't read everything but: > > > How come I can not use CssResource with the standard widgets of GWT ? > > This is easy to do... I even like more the old widgets then the new Cell > widget for css customization. > > And as far sa I can tell, a big majority of the bug I've seen so far are > often because the user don't use GWT in the right way. I'm not denying that > there's bug, but the big business app I've worked on never had issue with > GWT itself. > > Cheers, > > > > On Thu, Aug 26, 2010 at 4:40 AM, stuckagain <[email protected]> wrote: > > Hi, > > > Since I get no response from the GWT dev-team on reported bugs I am > > beginning to wonder about the future of GWT. It looks like stability > > of the existing features is not very high on the list. I've heard > > excuses in all the previous release that you guys were going to sort > > out long-standing bugs after the next major release ... but years have > > passed now and the collection of open and even new issues is going in > > the wrong direction. > > > So I have to ask the obvious question: > > Is Google going to abandon it now that Google Wave has been axed ? > > > The focus of 2.1 seems to be fast app development for enterprise apps, > > which is very good... but one of the major requirements in enterprises > > when selecting a toolkit is the maturity and stablity of the toolkits, > > how much support do you get, how fast are bugs fixed ... etc... right > > now I find it harder every day to sell GWT for newer projects. > > > From that perspective I'm not that sure that I would want to rely on > > the Spring-Roo and Data aware widgets. > > > When we report bugs on other opensource projects (like struts in the > > past or eclipse and many others) the new bug reports are quickly > > detected and you get some basic feedback... right now the issue > > tracker seems like you guys are using the SUN bug database. There are > > still important bugs open from the beginning years of Java! > > > One other remark about dogfood: > > How come I can not use CssResource with the standard widgets of GWT ? > > They all rely on primary stylename and style dependent names to switch > > states ... which makes it impossible to optimize the CSS with > > CssResource. Are we really supposed to write our own widgets ? Writing > > our own widgets is not too hard, but I hate it when I can not even use > > the most fundamental UI widgets. > > > Again: I'm sounding very negative above, but that is just because I > > care about the success of GWT! I want it to succeed but it needs to > > grow up. > > > David > > > -- > > 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. > > -- > Christian Goudreauwww.arcbees.com -- 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.
