Hi all,
as a reminder: Please make sure to get your patches in for GWT 2.7 until
tomorrow (October 7th).
-Daniel
--
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 emai
We worked on a migration plan a few weeks back. I don't think we need to
mix css and gss together inside the same app.
At this point, the libraries have multiple reasonable options on
compatibility:
1- Provide both css and gss file for the resource (recommended).
The library will work fine regard
> Hmm but still a bit of work if a library has lots of inline styles and
wants to use GSS stuff.
If you want to use GSS in all of your inline styles, you have first to
convert them to GSS and it will take more time than simply adding an
attribute that say that this inline style is using GSS.
The p
>
> For inline UiBinder styles, we can add an attribute useGss="true".
>
Hmm but still a bit of work if a library has lots of inline styles and
wants to use GSS stuff. A multi-valued config property like
"CssResource.GssRequired" that takes GWT module names could be used to
enable GSS for inli
In fact, my question is stupid... If third party library want to use GSS,
they just have to use file with .gss extension.
For inline UiBinder styles, we can add an attribute useGss="true".
On Mon, Oct 6, 2014 at 8:41 PM, Jens wrote:
> Oh I forgot to mention that we had decided to use only the
>
> Oh I forgot to mention that we had decided to use only the CssResource
> interface and not create a new GssResource interface.
>
> And we use the extension of the file in order to know if the file has to
> be converted or not
>
Oh I see.
I think a config property is better since a library
Oh I forgot to mention that we had decided to use only the CssResource
interface and not create a new GssResource interface.
And we use the extension of the file in order to know if the file has to be
converted or not.
On Oct 6, 2014 8:24 PM, "Jens" wrote:
> Now I think we should allow the inver
>
> Now I think we should allow the inverse: give the ability to third party
> libraries to use GSS in their CssResource even if the CssResource.enableGss
> is set to false. This could be done by either using an annotation or by
> using a configuration property in the module file.
>
You said
Hi,
I've pushed the code for the so called GssResource.
The code has been split in two patches:
- The first one contains the code for the converter. The converter can be
used in order to convert the existing css files to a GSS compatible file.
- The second one contains the code for the generator
> - User starts loading old nocache.js, you tell load balancers to
> redirect to the new app, the nocache.js runs and tries to load an old
> permutation from a new server where it doesn't exist.
Right.
> I suppose Stephen's deployment strategy is different
Yeah, slightly.
Currently, if we have
On Monday, October 6, 2014 10:25:24 AM UTC+2, Jens wrote:
>
> I'm trying to hook into the
>> failure of when a client loads the .nocache.js from one version,
>> but tries to get the permutation from another.
>>
>
> Hm interesting, we never run into this. How do you update your app? Maybe
> we
>
> I'm trying to hook into the
> failure of when a client loads the .nocache.js from one version,
> but tries to get the permutation from another.
>
Hm interesting, we never run into this. How do you update your app? Maybe
we also suffer this small window but never noticed it. We deploy a se
12 matches
Mail list logo
