Hi, On 27.08.2010 15:29, Clemens Wyss (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/SLING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903403#action_12903403 > ] > > Clemens Wyss commented on SLING-1671: > ------------------------------------- > > regarding the "pluggable resource/node editors": > within the /libs/sling/servlet/default/explorer/edit folder you can place > custom esp's to override the default editor for specific sling:resourceTypes. > As an example I placed the sling_redirect.esp in there, which handles nodes > of sling:resourceType == 'sling:redirect', such as the root-node/folder. > > This "feature"/behavior is of course (and not only, I guess ;-) ) to be > discussed
I like this feature ! +100 as we say ;-) Yet, the intention of the separation of /apps and /libs is (at least in our case at Day) that we (Day) provide stuff in /libs while customers and partners provide extensions/overwrites in /apps. Now from the POV of Sling, I would assume that we (Sling) provide defaults below /libs and users of Sling (people implementing applications with Sling) will add extensions in the /apps area. My question: Is such functionality supported by your code ? Or can it be added ? For example the ResourceResolver.getResource(String) method will use the search path (ResourceResolver.getSearchPath()) to resolve relative paths. Regards Felix > > >> New features for jQuery JCR Explorer - step 1 >> --------------------------------------------- >> >> Key: SLING-1671 >> URL: https://issues.apache.org/jira/browse/SLING-1671 >> Project: Sling >> Issue Type: New Feature >> Components: Extensions >> Reporter: Clemens Wyss >> Assignee: Clemens Wyss >> Priority: Minor >> Attachments: sling-1671-clemens.patch >> >> >> + property (type) specific editors (e.g. date, boolean) >> + search (SQL2, JQDOM, sql and xpath) >> + optimized tree (navigation) >> + pluggable resource/node editors >
