I put online the first draft of the GssResource and its generator
: https://github.com/jDramaix/gss.gwt/pull/1
Don't hesitate to review it, comment and give feedback. Once we'll agree
that is the way to go, we can move the code in a project under gwtproject
account.
This is a WIP and all is ope
Hello,
First sorry for my late reply, I was on holidays in September.
I spent some evenings working on this subject and here is a summary of what
I've done so far :
I first tried to replace the flute parser by the closure stylesheet parser
for the CssResource. My idea was simple : traverse the t
Its never too late - I don't know how far Julien has gotten, but I've been
distracted by other work, as well as trying to nail down conceptually where
GSS meets ClientBundle.
For my part, SASS or LESS are a major step down from what we already have -
the purpose of GWT in general is to let you
I'm a little bit late in this discoussion, i see there is a lot of work
already on going.
But +1 for this.
SASS or LESS would be a big plus.
For me I think supporting OOCSS is more important than supporting CSS3
without workarounds.
Thank you guys!
Sam
On Friday, December 16, 2011 11:51:43 PM
I spent an hour or two last night playing with phloc-css, and it doesn't
seem to be quite as flexible as flute in terms of adding custom behavior
for unknown @-rules (@def, @sprite, etc), or handling arbitrary (and
unknown to both flute and phloc-css) functions like literal() and value().
I pla
Thanks all,
I will focus on Closure stylesheets integration and the introduction of a
new GssResource
Julien
On Tue, Aug 27, 2013 at 5:25 PM, Goktug Gokdogan wrote:
> What we were planning was to add support for GSS, add the missing features
> and then migrate existing users and deprecate the
What we were planning was to add support for GSS, add the missing features
and then migrate existing users and deprecate the older eventually. This
would decrease the maintenance cost a lot in the long term.
We really want to see GSS support for GWT in the long term. On top of
additional features,
On Tuesday, August 27, 2013 1:42:35 AM UTC+2, Colin Alworth wrote:
>
> 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
> towa
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
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 alterna
On Thu, Feb 2, 2012 at 7:05 AM, Ray Cromwell 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
Sorry to hear that. This is actually on our list of priorities for
GWT, so we will have to take this up internally.
On Wed, Feb 1, 2012 at 4:44 AM, Thomas Broyer wrote:
> On Wed, Feb 1, 2012 at 1:16 PM, Daniel Kurka
> wrote:
>> Thomas are you doing something about that?
>
> No, I started lookin
On Wed, Feb 1, 2012 at 1:16 PM, Daniel Kurka
wrote:
> Thomas are you doing something about that?
No, I started looking at it, but quickly gave up, without writing any
line of code (I mean, I have no single commit in my
closure-stylesheets local git branch). I have no strong need for it,
so it was
Thomas are you doing something about that?
I am actually getting really annoyed with all the bugs we have in the
current ClientBundle implementations and all the workarounds needed to get
some css3 working.
I would like to see some decent css3 support in the standard CssResource
and would also de
Replacing Flute with Closure Stylesheets while retaining GWT's semantics is not
easy. First, Flute is a SAC parser while Closure is DOM-like using visitors
(much like GWT's own internal model).
Given Ray's earlier idea to even move to SASS or LESS, I'd rather introduce a
new GssRessource (which
I would also volunteer to put some work into this, since I am hitting more
and more bugs in the way GWT parses CSS files
-Daniel
2011/12/16 Michael Vogt
> Hello.
>
> > How could I refuse? :) SGTM. We will of course, still have to
> > maintain all of the GWT-isms. Actually, I've been wondering
Hello.
> How could I refuse? :) SGTM. We will of course, still have to
> maintain all of the GWT-isms. Actually, I've been wondering if we
> shoudn't just adopt LESS or SASS extensions too.
>
Yes, please.
Greetings,
Michael
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
How could I refuse? :) SGTM. We will of course, still have to
maintain all of the GWT-isms. Actually, I've been wondering if we
shoudn't just adopt LESS or SASS extensions too.
-Ray
On Fri, Dec 9, 2011 at 6:40 AM, Thomas Broyer wrote:
> Hi all,
>
> CssResource uses Flute to parse the CSS. Flut
Escaping css3 is a PITA. I'm 100% on board.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Personally, I would love to see that. Let's see what others have to say.
On Fri, Dec 9, 2011 at 6:40 AM, Thomas Broyer wrote:
> Hi all,
>
> CssResource uses Flute to parse the CSS. Flute only supports CSS 2 (as do
> other CSS parsers in Java: CSSParser, Batik, etc.) and seems totally
> unmainta
Hi all,
CssResource uses Flute to parse the CSS. Flute only supports CSS 2 (as do
other CSS parsers in Java: CSSParser, Batik, etc.) and seems totally
unmaintained (last version is 9 year old!). The version used in GWT has
been patched to add support for the double-colon notation for
pseudo-el
21 matches
Mail list logo
