Well, after more than one month I asked this question on StackOverflow I
still got no answers.
It must be something so stupid to find out that no one took the time to
answer it.
Oh well...
I'll keep using the old CSS2 content assist on Eclipse till the UiBinder is
dead on 3.0.
On Tuesday,
*.ui.xml files have their own UiBinder editor in Eclipse provided by the
GPE plugin. It might be that your Eclipse settings regarding CSS simply do
not take effect in that editor.
As a workaround you could probably avoid using ui:style inline styles and
instead create a *.gss file for it,
Thanks Jens for the answer.
Ok, I was missing the GWT DIY Policy™ on this one =)
I'll take a look and update this thread and the StackOverflow question if I
get something.
On Thursday, July 16, 2015 at 3:07:52 PM UTC-3, Jens wrote:
You could also use the open source fork of GPE
Issue reported: https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/79
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
You could also use the open source fork of GPE
https://github.com/gwt-plugins/gwt-eclipse-plugin
and figure out how to patch it to provide CSS 3 autocompletion.
-- J.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from
(Cross-posted from StackOverflow:
http://stackoverflow.com/questions/30823483/how-to-get-autocomplete-of-css3-properties-on-eclipse-inside-the-uistyle-tag
- I got 0 answers and comments there so far)
I can enable autocomplete of CSS3 properties for .css and .gss files on
Eclipse by following
