> > could automatically have ".parent.child" concatenated for you to "parent > child" to be returned when you ask for the class name. However,
@Joseph: that's not even such a bad idea. Indeed you could use a Delegator class that implements that Widget style interface that forwards the call to the correct CssResource interface. In case you want to add an extra styl, you just concatenate two style method calls. It's not ideal, but possible. I think a good solution would be that GWT integrates with the closure-stylesheets project. GWT could not have to worry about the css programming like the current browser-style-dependent conditions. This is done by the closure-stylesheet project. New features/updated added to the closure-stylesheets project would automatically be available I think. On Thu, Jul 19, 2012 at 3:06 PM, Joseph Lust <[email protected]> wrote: > Ed, > > Ideally (in the spirit of CSSResource) you'd hack the > CSSResource/ClientBundle setup so that when extending a CSSResource, you > could automatically have ".parent.child" concatenated for you to "parent > child" to be returned when you ask for the class name. However, I've done > no such hacking in the GWT source. > > > Sincerely, > Joseph > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/bUNS9VK5n1QJ. > > 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. > -- 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.
