I'd be interested in helping with either approach. The phloc-css project looks interesting if we are only trying to add support for newer CSS features, while integration with Closure Stylesheets seems geared more toward extending the CssResource featureset. Much of the existing functionality in GWT's CssResource is also in closure in some capacity, though the implementation is likely different enough to cause interesting issues. There are advantages to making it through those differences - mixins for example.
Another thought would be to implement both - expand CssResource to support new properties with phloc-css, and create a new ResourcePrototype (StylesheetResource perhaps?) with its own resource generator to put code through closure's wringer. -Colin On Monday, August 26, 2013 5:38:45 AM UTC-5, Julien Dramaix wrote: > > Hi all, > > Just to inform you that I would like to give a try to add support of CSS3 > in GWT if nobody is working on. > > After some research, I found another open source CSS parser in java > supporting CSS3 : https://code.google.com/p/phloc-css If we need only a > parser it could be a interesting alternative to Closure syle sheet. > > What do you think ? > > Julien > > > On Thursday, February 2, 2012 9:38:02 AM UTC+1, Thomas Broyer wrote: >> >> On Thu, Feb 2, 2012 at 7:05 AM, Ray Cromwell <[email protected]> wrote: >> > Sorry to hear that. This is actually on our list of priorities for >> > GWT, so we will have to take this up internally. >> >> Just a clarification: I was trying to replace Flute with the parser >> from Closure Stylesheets, replacing the whole CssResource processing >> (or creating a GssResource) with one based on Closure Stylesheets >> should be relatively easy though. For now, my priorities are fixing >> the remaining RF bugs and hope my half-a-dozen-or-so patches will land >> in 2.5 (we're helping a company switch to web apps in GWT, and I'd >> recommend them to use RF over RPC if there wasn't so many pitfalls >> [1], having the fixes in 2.5 would help make the choice based on the >> actual features and limitations due to their designs, rather than >> ditch RF based only on its known bugs [2]). I had very little time >> these past weeks so I couldn't even try fixing issue 6710 which, to >> me, is higher priority. >> >> So, when I'll have time and have fixed 6710 (the last remaining >> "blocker" IMO), I'll see if I can help integrating Closure >> Stylesheets, but I'm afraid not before. Does that sound good to you? >> >> [1] That one in particular caught me when upgrading to a "recent >> trunk" last fall, it's not documented and I can't say if it's a bug or >> simply a limitation due to batching: >> http://code.google.com/p/google-web-toolkit/issues/detail?id=7120#c1 >> [2] One such example: >> http://code.google.com/p/google-web-toolkit/issues/detail?id=7120#c2 >> >> -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
