On Thu, Oct 30, 2014 at 7:51 AM, Julien Dramaix
wrote:
> If GSS was the default, we would have shipped only .gss files.
>
That's not true. We will still have a release where GSS is default and css
is supported but deprecated that requires css files to be there.
> What I want is to provide the
ok. I will do that in an external third party library
On Thu Oct 30 2014 at 6:19:58 PM 'Daniel Kurka' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:
> I think we should not provide these files as of yet. If someone wants to
> make the transition right now they can
I think we should not provide these files as of yet. If someone wants to
make the transition right now they can easily use the converter with these
files and convert them to gss themselves.
I think we want to make that transition once GSS is default (or about to be
default) inside of Google as a te
If GSS was the default, we would have shipped only .gss files.
What I want is to provide the .gss files for people using GSS and want to
override some style class of cell widgets. We have this case at Arcbees
where css guys want to use their existing mixins to style CellTable.
On Wed Oct 29 2014
The original idea to make the GSS default was to ship .gss files next to
.css files and let the generator automatically use the file with the gss
extension.
We can probably ship the gss files but I think it is optional at this point.
On Wed, Oct 29, 2014 at 5:50 AM, Julien Dramaix
wrote:
> Now t
Now that GSS will be shipped in GWT 2.7 as an experimental feature, I'm
wondering if we shouldn't provide GSS files for all existing CssResource
interfaces present in GWT. The idea is to keep the associated .css files
and use them by default but also to provide GSS files in order that people
can us
