>Take care of maintainability ;-) +1, so either esp or groovy. Will proceed with esp for the moment
> Just my CHF 0.02 really. we both know there is at minimum the CHF 0.05 :-) maven question: I'd like to make use of "-P autoInstBundle" to speed up the development cycle. What needs to be modified/added in the pom.xml to be able to?: mvn -P autoInstallBundle package -Dsling.url=http://localhost:8080/system/console Tried to add "<relativePath>../../parent/pom.xml</relativePath>" to the <parent>-element, but no success. Any hint/help appreciated. > -----Original Message----- > From: Felix Meschberger [mailto:fmesc...@gmail.com] > Sent: Friday, August 13, 2010 7:35 AM > To: dev@sling.apache.org > Subject: Re: extending jQuery JCR Resource explorer > > > Hi, > > On 13.08.2010 07:22, Clemens Wyss wrote: > >> 2, 4, 5, 6, 10 > > ok, so you think/say "mixin types" is not that much a topic? > > > >> ACL view/edit > > good point, though this mandates 10) ;-) > > > >> Reference/Path property support > > Links? drag&drop? > > > >> I need to make some modifications to the explorer to support > >> non-default workspaces, but hopefully that change will be > >> minor (keeps slipping off my list). > > is there a jira entry for this task? > > > > Is esp the right serverside approach? Or would groovy (me, > coming from Ruby), or even Java be "helpful"? > > Basically: Whatever you like and can be supported with JSR-223 (Java > Script API). > > If you choose groovy, fine. That's included with Sling already. If you > chose Java, fine. If you choose ESP or ECMA, fine. > > One part of my heart even says: If you use multiple languages for this > on the server-side it would be a nice example for the versatility of > scripting support in Sling ... The other part of my heart says: Take > care of maintainability ;-) > > Just my CHF 0.02 really. > > Regards > Felix > > > > > Clemens > > > >> -----Original Message----- > >> From: Justin Edelson [mailto:justinedel...@gmail.com] > >> Sent: Thursday, August 12, 2010 9:07 PM > >> To: dev@sling.apache.org > >> Subject: Re: extending jQuery JCR Resource explorer > >> > >> > >> Nice of you to ask about prioritization... > >> > >> 2, 4, 5, 6, 10 > >> > >> Would be the highest priority items for me. I'd also add > >> these to your list: > >> > >> ACL view/edit > >> Reference/Path property support > >> > >> I need to make some modifications to the explorer to support > >> non-default workspaces, but hopefully that change will be > >> minor (keeps slipping off my list). > >> > >> Justin > >> > >> > >> On Aug 12, 2010, at 10:26 AM, Clemens Wyss > >> <clemens...@mysign.ch> wrote: > >> > >>> As "promised", I (actually it's we, MySign) intend to > >> extend the jQuery JCR Resource (contrib/explorers/jQuery) > >> explorer in order to make it more valuable for developers. > >>> > >>> Features currently available (as of May 17th 2010, rev 945149): > >>> + login > >>> + browse JCR > >>> + add node (name, sling:resourceType and jcr:primaryType > >> have to be entered manually (input field)) > >>> + delete node > >>> + view properties (multivalue properties are shown "inline" > >> in an input field) > >>> + modify/update property (single value properties only) > >>> + delete property > >>> > >>> desirable features: > >>> 1) jcr:primaryNodeType properties should be selectable > >>> 2) view/add/edit/delete multivalued properties > >>> 3) view/add/edit/delete mixin types, mixin types should be > >> selectable > >>> 4) simplified input for "known types", such as date (see > >> also 1) and 3) ) > >>> 5) search/filter functionality (SQL2, JQOM?) > >>> 6) nt:file -> file upload > >>> 7) import/export subtrees, format to be defined > >>> 8) input validation > >>> 9) ajax'ify the client > >>> 10) usermanagement > >>> more to come... > >>> > >>> WDYT? Anything important/fancy missing? How would you > >> priorize these features? > >> > > >
