I know that Roo just generates a basic look that the developer can finish themselves. However, I really feel that Roo should only generate structure (HTML) and no look (CSS) at all. Who wants all web sites to look similar or have too similar solutions ? Currently using the Roo tags give a "Roo look & feel" that I don't care for. My main problem in making Roo sites look and work the way I want is the lack of full control over the HTML structure.
I don't want premade dojo themes creeping into my interfaces. I want to make my own look. What professional outfit want premade looks to start with? The first thing I do at the GUI stage is to rip out all the stuff that gets in the way. This is currently too timeconsuming, for the newcomer at least.
I suggest to the Roo-team
1. to refocuse more on html structure rather than any kind of implementation of specific themes.
Give the Roo user more control over the generated structure. I don't care how my data looks when I'm building the backend, as long as I can see it. I care about what structure my data have. I want full control of this structure. I don't want DIVitis. I want as much semantic markup as possible.
2. Solve the problem that jspx requires elements to be closed, that are actually according to the HTML5 spec unclosed without a trailing "/", as is the case with the IMG-element for instance. If Roo supports HTML5 it should support the full range of acceptable HTML5 syntax, no?
3. Make it much easier to implement interfaces built by professionals
4. SASS / Compass support or if you have something better would be extremely useful.
5. The menu.jspx would be more useful if it was focused on building the actual navigation. I don't use the generated menu in anything, not even the administrator pages. It's only useful for the Roogenerated pages, which more and more feels simply like test pages, which is nice but has very little to do with the end production.
6. I'd rather just have Roo only generate Spring tags. If we can't have Roo tags that are actually useful , ie that are easily controllable by the user, or build an environment for users that encourages sharing of developed Roo tags that are, then why even have the tags there other than for being some kind proof of concept? I don't really use much of the Roo tags in the production site. I use the Spring tags.
I want total control of my web sites. Currently I feel the only way have that is to rip out much of the Roo GUI at the point of building the interface. Some of the time saved using Roo is lost there which is very unfortunate.
I'm sorry if I come on as being harsh, but I'm frustrated over the possibility that Roo is the wrong choice for building effective web sites. I've spent a year learning to use it. I feel that in many ways it's more efficient to just use Spring with suitable packages as it is. Am I really the only one feeling this way?