Ken Yee wrote:The good news it the To CSS Class button works with the submenu (ContextMenu), but it doesn't do anything when you try using it on the Toolbar. It creates an empty style block in the cssblock property and doesn't pull any styles out.
That appears to be a problem. But you can always do it manually. The point is you can use CSS class so that you will be able to skin the controls.
Ken Yee wrote:It also seems to some ID numbering/naming, so it's probably something that should be done last...if you add more controls, I'm not sure how it works since the classes reference ID's instead of putting classes in for each menu item...just some constructive feedback..
It uses automatically generated names when you do the conversion automatically. If you want to control the class names, you just pretend the button does not exist and supply your own CSS class names. For example, setting ToolBar.DisabledStyles.CssClass to whatever CSS class will apply that class when the button is disabled. This is the way how most other controls on the market work. Our advantage is we also support inline CSS text and a CSS Style Editor, which offers a number of benefits such as easy copy and paste, instant preview, etc. But when you wish to skin it, you just would use CSS class as you do with anybody else.
You may want to take a look of this class:
http://doc.essentialobjects.com/library/1/eo.web.elementstyle.aspxThis class is the key of our CSS implementation. Whenever other vendors have a "XXXCssClass" property (type as string), we would usually have a "XXXStyle" property (type as ElementStyle). The difference is while you can only give "XXXCssClass" a class name (for example, "red_item"), you can give both/either class name (for example, "red_item") or CSS text (for example, "color:red") to our "XXXStyle" property.
Don't worry about the ID clashing issue, we have worked out that years ago. :)
Thank you very much for your feedbacks though!
Thanks