Bill, Thank you for a great idea! We had some discussions about such an approach having some beer but have not planned anything specific yet. You gave me an example of a concrete implementation and it is definitely a feature to consider.
We have a long-term plans to support Rumba development in Eclipse and other popular IDEs (NetBeans and IntelliJ IDEA come to mind first). The most basic level of integration could include code completion and error highlighting, more advanced would include full-scale WYSIWYG page editor where you could just drop a business object on the page and the IDE would generate some default controls for you. IDE integration would help to kill two birds with one stone: make prototyping quick while generating pages that are easy to maintain and adapt to web design requirements. That's not a promise though rather some ideas for the future. This is a task of its own and not a small one :). Rumba itself is our first priority, everything else is just a sweet addition. --- Bill Schneider <[EMAIL PROTECTED]> wrote: > Just took a look at this and there is some cool > stuff going on there. > > I've been working on a framework based on a similar > idea of a generic > CRUD back-end so you don't have to write new > Hibernate DAOs, Spring > business beans, or JSF backing beans for every new > entity type. > However, my end goal is really a generic *front* end > analogous to Trails > or Naked Objects, for rapid-prototyping basic CRUD > UIs. I often find > developing even a generic front-end JSP with the > right syntactic > validation etc. is more time-consuming than the > back-end. > > Putting the two ideas together, what would you think > of new JSF > components like these: > > <r:inputObject> that would automatically create all > of the right > h:input* and h:select* fields based on reflection > and Hibernate > metadata. For example, Enumerations and > many-to-one's could > automatically map to a selectOneListbox with the > right f:converter > magic. Strings would become inputText with the > size/maxlength from > EJB3/Hibernate tags. You could customize formatting > or conversion of > specific fields via <f:facet>. > > <r:outputObject> would be similar but for display > details instead of > input. > > Enhanced <r:dataTable> would determine columns to > display from the > objects by reflection or Hibernate metadata. (This > may not be nearly as > useful because h:column is already pretty > lightweight.) __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
