On Thu, Oct 11, 2012 at 4:21 PM, Alexander Klimetschek <[email protected]> wrote: > ...Autogenerating node types from some kind of UI definition is not a good > idea. Just try to start with nt:unstructured and go from there...
But the reverse, generating an UI from a JCR micro-tree, might be very cool. Using Sling selectors, a path like /content/someDocument.ui.json would generate a UI definition for someDocument. This UI generation can then be based on all metadata that the JCR micro-tree provides: paths, properties, sling:resourceType, mixins, and even node types but as Alex says we're not fans of having many of those, as that tends to break JCR's agility. -Bertrand
