Hi, I'm working with UiBinder to massage designer-created HTML into a GWT app. It seems like this could be really slick.
The biggest hurdle so far is that the designer's css has a lot of "#element-id" declarations, which leads to two irritations: 1) Dashes are not a valid java identifier, so I had to translate the id to "#elementId" in both the css and the ui.xml. I actually tried hacking in a "@UiField(id="element-id")" annotation parameter, and having OwnerField look for it as an override. Unfortunately OwnerField.name itself is later used directly as a identifier in the generated source, so I got compile errors. If this could be made to work, perhaps by rewriting dashes to underscores, I think the feature would be worthwhile. 2) Even after conversion, "#elementId" styles are not being applied to the HTML element. Looking at the generated HTML (in oophm w/firefox), the element doesn't have an "id" element on it at all. Which seems kind of odd...I was at least expecting an obfuscated/rewritten id. So, I can see why the css would not get applied to it. Are either of these valid concerns (e.g. feature request-able), or just the way uibinder will be? For the short term, it seems like my best bet is to have the designer a) use all camel casing and b) use only class-based selectors (e.g. ".elementId"). Does that sound right? Thanks, Stephen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
