> The @external part is what I don't like. This makes it impossible to
I agree with this (stuckagain was just a bit faster then me...)
Like mentioned in the doc. @external is there for legacy support.
I don't like the write legacy code...
Said that: Especially when having large projects with complex
constructions, obfuscating style sheet is an important requirement to
overcome style conflicts (just my experience).
> <g:MenuBar ui:field="menu" stylePrimaryName="{res.style.mesyMainMenu}">
Thanks Christian for your example, but it's missing the problem I
point out in the post that is linked to this issue:
http://code.google.com/p/google-web-toolkit/issues/detail?id=4903
That is: "using Clientbundles/CssResources in reusable components".
Suppose your component has also ImageSources and CssResources and I
want to inject mine such that I change the style and images... How do
you accomplish that?
Please read it and you understand what I mean.
At the moment GWT is still restricted on this issue, but GWT is still
young so it's normal that still functionality like that is missing...
Like David mentioned, GWT dev team is working very hard and it's all a
matter of priorities.
So it's important that we all vote the issues that we find important
such these bugs get solved first...
@David: prepare yourself for the live stream chat with the GWT Dutch
team on the 10 of september... :)... I am at the other end and hope we
have time to discuss these ClientBundle/CssResource issues....
Ed
On Aug 26, 8:46 pm, stuckagain <[email protected]> wrote:
> David,
>
> On Aug 26, 7:54 pm, David Chandler <[email protected]> wrote:
>
> > David,
>
> > At this time, there is a lot of activity around the 2.1 release, and
> > you can get some sense of this by watching the SVN trunk. In addition,
> > the GWT team has considerably stepped up maven support (see recent
>
> I've been looking at all the checkins. I'm aware of what is coming,
> but we already have
> build a fast table with cell renderers, incremental rendering with
> multi TBODYs to get the fastest renderings,
> so we are not really waiting for the new features. It's nice that
> there will finally be a better table, but will it be
> extendible enough ? Will all bugs be fixed quickly ? You can not
> expect the community to fix every bug, especially
> if the problem is somewhere deep inside the compiler or event
> dispatching code (like the one I reported on PopupPanel in IE).
>
> > blog posts), which was one of the top issues in the issue tracker. As
> > always, addressing particular bugs is a question of priorities, but
> > rest assured that the GWT team is well aware that no one wants to see
> > new features added at the expense of stability.
>
> Then why is there so little progress on fixing bugs ? It looks like
> the whole team is working on 2.1.
> When I look at New issues in the tracker I can see over 900 bugs that
> are still marked as new, it takes me back all the way to November
> 2006.
> There are indeed a lot enhancements but there are quite a lot of bugs
> as well... like stack overflows with the RPC... in 2.0 DeRPC was
> released, but with a big warning that it was not stable yet. Will it
> be 100% for 2.1 ? Or is there a newer system used by the data aware
> widgets ?
>
> > As for the @CssResource issue, if this is still unresolved for you,
> > please star issue 4903 (http://code.google.com/p/google-web-toolkit/
> > issues/detail?id=4903) and we'll revisit it.
>
> I read through the newsgroup thread but I must say I don't agree with
> everything that was said there. CssResources are really great, just
> too bad that they were not retrofitted to the existing widgets.
>
> But I guess that the main goal would be for the declarative UI system?
> What I do agree upon is that the build in widgets of GWT are very
> limited in extendability (button in the titlebar of a dialog ... who
> would not want it ?) and they are not supporting CssResource directly
> so I have to fallback to @external which takes away a few nice
> features of using a CssResource.
>
> David
>
> > /dmc
> > David Chandler
> > Google Web Toolkit Team
>
> > On Aug 26, 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].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
