There are new methods in GWT 2.0 that go some way to helping with this
kind of thing.
For example:
widget.getElement().getStyle().setBorderWidth(5, Unit.PX);
ThomasWrobel wrote:
> This used to confuse me greatly, so I'm very glade theres a specific
> error message now.
>
> On Oct 6, 8:00 am
It's not a catch-all, of course. If you make errors like using 'float'
instead of 'cssFloat', it will still let it through silently.
Ian
http://examples.roughian.com
2009/10/6 ThomasWrobel
>
> This used to confuse me greatly, so I'm very glade theres a specific
> error message now.
>
> On Oct
This used to confuse me greatly, so I'm very glade theres a specific
error message now.
On Oct 6, 8:00 am, Ian Bambury wrote:
> It's always been the case that you needed to use camelCase, it hasn't always
> been the case that GWT would report the use of hyphens as an error.
> Ian
>
> http://exam
It's always been the case that you needed to use camelCase, it hasn't always
been the case that GWT would report the use of hyphens as an error.
Ian
http://examples.roughian.com
2009/10/5 Joe Cole
>
> Has this always been the case? I've just started encountering these
> errors after upgrading
Has this always been the case? I've just started encountering these
errors after upgrading to 1.7.
On Oct 6, 4:43 am, Paul Robinson wrote:
> It's a javascript thing. All CSS names in javascript have to be
> camelcase. So it's "border-left" in html, but "borderLeft" in any
> javascript DOM code.
It's a javascript thing. All CSS names in javascript have to be
camelcase. So it's "border-left" in html, but "borderLeft" in any
javascript DOM code.
Joe Cole wrote:
> Can someone explain why this code from com.google.gwt.dom.client.Style
> is enforcing camelcase:
>
> private void assertCamelC
Can someone explain why this code from com.google.gwt.dom.client.Style
is enforcing camelcase:
private void assertCamelCase(String name) {
assert !name.contains("-") : "The style name '" + name
+ "' should be in camelCase format";
}
--~--~-~--~~~---~--
