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
toward
If this is purely JavaScript related you can use d8 (the v8 command line
profiler) to do the profiling for you.
I recently added source maps support to it so you can actually profile
obfuscated GWT code just fine.
Here is what you need to do:
1. Build v8 yourself
2. Compile your code using a
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,
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 gok...@google.com wrote:
What we were planning was to add support for GSS, add the missing features
and then migrate existing users
There was talk at the last GWT meetup of adding official JAX-RS support to
GWT. There are several implementations floating around (RestyGWT,
Errai-JAXRS, etc) Is this another JAXRS implementation? I'd be interested
in seeing a comparison between the major implementations.
On Sun, Aug 11, 2013
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
