Re: [gwt-contrib] CSS3 support in CssResource: Closure Stylesheets?

[Colin Alworth]

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 played briefly with modifying the jjt file, but realized that any gain 
made there comes at the cost of re-namespacing and trying to rebase such a 
change along as phloc-css changes. As a drop-in replacement, I'm not seeing 
a good strategy here, though I'm open to suggestions. 

Closure doesn't quite seem a perfect fit either, though perhaps I am 
missing some details about it (I've only gone through the docs at 
http://code.google.com/p/closure-stylesheets/ and the wiki), specifically 
around the @sprite/gwt-image feature in CssResource, but also the other 
Java-specific pieces like @eval to get outside values into the css and @def 
to get inside values back out again. Can anyone comment on those aspects of 
how a GssResource could look?

On Tuesday, August 27, 2013 2:19:39 PM UTC-5, Julien Dramaix wrote:
>
> 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 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, there are other benefits with moving to GSS; Google is 
>> committed to maintain GSS and support it in the long term, we can get 
>> direct support from the authors as they are close to us. One other major 
>> advantage more specific to us is, we can reuse tons of already available 
>> GSS resources. For that reason, we would love to see you moving in this 
>> route and will definitely help you along the way, and also provide you 
>> additional contact points from the team for support.
>>
>>
>>
>> On Tue, Aug 27, 2013 at 3:24 AM, Thomas Broyer 
>> 
>> > wrote:
>>
>>>
>>>
>>> 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 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.

>>>
>>> +1 to that (obviously, as I think that's what I was proposing) 
>>>
>>> -- 
>>> 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 
>>> google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  -- 
>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "GWT Contributors" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-web-toolkit-contributors/e0qUfkqBSog/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-web-toolkit-contributors+unsubscr...@googlegroups.com
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Thoughts on dropwizard framework as a backend for GWT

[Ray Cromwell]

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 at 12:46 PM, Rafiq Ahamed  wrote:

> I agree. My thoughts are more towards integrating the good things from
> spiffyUI (spiffyui.org) into GWT. Wondering why no a great concept like
> SpiffyUI is not going mainstream but the same old JSF like Vaadin is
> getting into mainstream. The great thing about thick clients is that, they
> can be easily wrapped with android wrappers or IOS wrappers or even JavaFX
> wrappers.
>
> On Monday, August 12, 2013 12:02:43 AM UTC+5:30, John A. Tamplin wrote:
>
>> On Sun, Aug 11, 2013 at 2:21 PM, Rafiq Ahamed  wrote:
>>
>>> Dear Folks,
>>>Any thoughts on DropWizard framework (http://dropwizard.codahale.**
>>> com/ ) as a backend for GWT. RESTFUL
>>> webservices is the way to go and I feel GWT RPC is an Anti-Pattern.
>>>
>>
>> GWT RPC was never intended to be the solution to all problems.  It is
>> easy to use and allows you to send entire object graphs without much
>> effort.  Of course, you get versioning issues and you can send entire
>> object graphs without much effort.
>>
>> You can already use JSON easily now if you prefer, and protos with a bit
>> more effort.  REST vs other options is really more about the server anyway.
>>
>>
>>>And also, what about integrating ApacheCouchDB or ApacheSolr (Json
>>> style Schema less 4.4 version) as a backend for GWT so that the application
>>> can be developed rapidly. This is the approach I have taken for one of my
>>> new project.
>>>
>>
>> GWT has generally been server-agnostic, so I would expect any server-side
>> integration with a specific framework would be a separate project.
>>
>> --
>> John A. Tamplin
>>
>  --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] CSS3 support in CssResource: Closure Stylesheets?

[Julien Dramaix]

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 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, there are other benefits with moving to GSS; Google is
> committed to maintain GSS and support it in the long term, we can get
> direct support from the authors as they are close to us. One other major
> advantage more specific to us is, we can reuse tons of already available
> GSS resources. For that reason, we would love to see you moving in this
> route and will definitely help you along the way, and also provide you
> additional contact points from the team for support.
>
>
>
> On Tue, Aug 27, 2013 at 3:24 AM, Thomas Broyer  wrote:
>
>>
>>
>> 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 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.
>>>
>>
>> +1 to that (obviously, as I think that's what I was proposing)
>>
>> --
>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/e0qUfkqBSog/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] CSS3 support in CssResource: Closure Stylesheets?

[Goktug Gokdogan]

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, there are other benefits with moving to GSS; Google is
committed to maintain GSS and support it in the long term, we can get
direct support from the authors as they are close to us. One other major
advantage more specific to us is, we can reuse tons of already available
GSS resources. For that reason, we would love to see you moving in this
route and will definitely help you along the way, and also provide you
additional contact points from the team for support.



On Tue, Aug 27, 2013 at 3:24 AM, Thomas Broyer  wrote:

>
>
> 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 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.
>>
>
> +1 to that (obviously, as I think that's what I was proposing)
>
> --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Gwt benchmarks without Benchmark

[Daniel Kurka]

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 custom linker like this one:
https://gwt-review.googlesource.com/#/c/4220 (only one permutation, turn on
source maps)
3. run that through d8 (e.g. d8 -prof mymodule.nocache.js)
4. use the tickprocessor to see the profile (e.g.
tools/linux-tick-processor --source-map=yoursourcemap.json v8.log

-Daniel


On Mon, Aug 26, 2013 at 8:45 PM, Goktug Gokdogan  wrote:

> The latest benchmarks (before the removal Benchmarks suite) was done by
> custom infra:
>
> https://gwt.googlesource.com/gwt/+/master/reference/Microbenchmarks/src/com/google/gwt/reference/microbenchmark
>
> If you would like to collect timing from some previous GWTTestCases you
> can do that by overriding some base methods on GWTTestcase (runBare
> includes gwtSetup and doRunTest does not) and log the timings.
>
> PS: Old benchmark suite was a hack over GWTTestCase infra that was adding
> a lot of complexity without much benefit.
>
>
>
> On Mon, Aug 26, 2013 at 11:16 AM, John A. Tamplin  wrote:
>
>> On Mon, Aug 26, 2013 at 1:47 PM, Colin Alworth wrote:
>>
>>> Shortly after 2.5.1, the Benchmark classes were removed from GWT (
>>> https://gwt.googlesource.com/gwt/+/39eb6001a037fd8b6580a73a2540e6e9c04e54c2and
>>> https://gwt.googlesource.com/gwt/+/00c7ce43df3a629b7302ab902a07431db7224e2b)
>>> - what are folks using for low-level performance testing these days?
>>>
>>> I'm wrapping up a changeset to emit JS TypedArrays when int[], double[],
>>> etc are used in code, and while I can see that some projects clearly
>>> improve with this, others seem to take a hit (specifically in rapidly
>>> allocating arrays that have a short lifetime). I'd like to record some
>>> numbers to paint this picture without rolling my own benchmark/gwtPerf
>>> tool, but I'm not quite clear on the current state of this sort of metrics.
>>>
>>> From the comment that originally deprecated the Benchmark class:
>>>
 This didn't get enough adaption externally or internally. The way it's
 implemented requires special support from GWTTestCase infrastructure. Also,
 we are not going have an environment to automate benchmarks written on this
 any time soon.

 If there is enough demand later, parts of this code can be resurrected
 to build a new benchmark system.

>>>
>>> Thoughts?
>>>
>>
>> I argued against removing it at the time, since I found it useful for JRE
>> work in particular.  I'm not sure what sort of demand would be required to
>> get it reinstated, but it would probably mean someone taking ownership of
>> it.
>>
>> --
>> John A. Tamplin
>>
>> --
>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Google Germany GmbH
*Dienerstr. 12*
*80331 München*

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] CSS3 support in CssResource: Closure Stylesheets?

[Thomas Broyer]

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 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.
>

+1 to that (obviously, as I think that's what I was proposing) 

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.