extending jQuery JCR Resource explorer

[Clemens Wyss <cl...@mysign.ch>]

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?

Re: extending jQuery JCR Resource explorer

[Felix Meschberger <fm...@gmail.com>]

Hi,

On 13.08.2010 07:59, Clemens Wyss wrote:
>> 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 :-)

I still have some of those CHF 0.01 and 0.02 coins, though ;-)

> 
> 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.

Referring to a recent Sling Parent POM is all that's needed. The rest
should have reasonable defaults for a default sling launch. If your
using a different port, you will have to set the sling.url property, yes.

Regards
Felix

> 
>> -----Original Message-----
>> From: Felix Meschberger [mailto:fmeschbe@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:justinedelson@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
>>>> <cl...@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?
>>>>
>>>
>>

RE: extending jQuery JCR Resource explorer

[Clemens Wyss <cl...@mysign.ch>]

>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:fmeschbe@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:justinedelson@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
> >> <cl...@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?
> >>
> >
>

Re: extending jQuery JCR Resource explorer

[Felix Meschberger <fm...@gmail.com>]

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:justinedelson@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
>> <cl...@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?
>>
> 

Re: extending jQuery JCR Resource explorer

[Justin Edelson <ju...@gmail.com>]

On Aug 13, 2010, at 1:22 AM, Clemens Wyss <cl...@mysign.ch> wrote:

>> 2, 4, 5, 6, 10
> ok, so you think/say "mixin types" is not that much a topic?

Hmm. I'm not aware that you can't set a mixin type today, but yes... in my usage of this explorer, I've never found myself wanting to add a mixin. But YMMV.  
> 
>> ACL view/edit
> good point, though this mandates 10) ;-)

Yes
> 
>> Reference/Path property support
> Links? drag&drop?

Display should be links. To add a value, I'd love a browse/search popup, but that's just me. 
> 
>> 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?
No.

> 
> Is esp the right serverside approach? Or would groovy (me, coming from Ruby), or even Java be "helpful"?
I think esp is used currently, so there's that to consider. Also, you can use (J)Ruby if you want; the jruby-all JAR just needs to installed. Mostly, I imagine the amount of new server side code to be minimal.

Justin

> 
> Clemens
> 
>> -----Original Message-----
>> From: Justin Edelson [mailto:justinedelson@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
>> <cl...@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?
>> 

Re: extending jQuery JCR Resource explorer

[Justin Edelson <ju...@gmail.com>]

On Aug 13, 2010, at 3:55 AM, Clemens Wyss <cl...@mysign.ch> wrote:

> will I be able to update/add/delete the values of multivalued properties through the Sling REST API (SlingPostServlet?)?

Yes. You need to set the property as a whole, i.e. pass all values for a property in a same post. There's no way to say "delete the third value from the baz property /content/foo/bar".
 
> 
>> -----Original Message-----
>> From: Clemens Wyss [mailto:clemensdev@mysign.ch]
>> Sent: Friday, August 13, 2010 7:22 AM
>> To: 'dev@sling.apache.org'
>> Subject: RE: extending jQuery JCR Resource explorer
>> 
>> 
>>> 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"?
>> 
>> Clemens
>> 
>>> -----Original Message-----
>>> From: Justin Edelson [mailto:justinedelson@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
>>> <cl...@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?
>>> 
>> 

RE: extending jQuery JCR Resource explorer

[Clemens Wyss <cl...@mysign.ch>]

will I be able to update/add/delete the values of multivalued properties through the Sling REST API (SlingPostServlet?)?

> -----Original Message-----
> From: Clemens Wyss [mailto:clemensdev@mysign.ch]
> Sent: Friday, August 13, 2010 7:22 AM
> To: 'dev@sling.apache.org'
> Subject: RE: extending jQuery JCR Resource explorer
>
>
> > 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"?
>
> Clemens
>
> > -----Original Message-----
> > From: Justin Edelson [mailto:justinedelson@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
> > <cl...@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?
> >
>

RE: extending jQuery JCR Resource explorer

[Clemens Wyss <cl...@mysign.ch>]

> 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"?

Clemens

> -----Original Message-----
> From: Justin Edelson [mailto:justinedelson@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
> <cl...@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?
>

Re: extending jQuery JCR Resource explorer

[Justin Edelson <ju...@gmail.com>]

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 <cl...@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?

Re: extending jQuery JCR Resource explorer

[Felix Meschberger <fm...@gmail.com>]

Hi Clemens,

Sounds very interesting. You are welcome to provide patches in any order
you like ...

If this gets a heavy lift, we might consider moving this to the bundles
location for inclusion in upcoming Sling releases. WDYT ?

Regards
Felix

On 12.08.2010 16:26, Clemens Wyss 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?

RE: extending jQuery JCR Resource explorer

[Clemens Wyss <cl...@mysign.ch>]

Hi Mike,
> I plan on making this UI cleaner too
I'd defer this till the end. Functionality/usability is more important. After all this is a developer tool.

More importantly the basic structure/design of the explorer has to be re-thought
- dynamic tree
  - reloading
  - partial/lazy loading (?)
- plugin (node/type) editors
- handling/editing multivalued properties. At the moment we don't have enough "information" (just the <ul><li>'s) in the client for this...

> > + properties are no more being edited inline, which makes sense
> I did this because I planned on eventually making the UI's
> customizable, via plugins, based on primary type, etc.
also proposed by Bertrand

> - Principal / Group management
10) usermanagement

> - Node type browser / management
?

> - Content loading / exporting interface
6) nt:file -> file upload
7) import/export subtrees, format to be defined

You say "I plan on making". Any time frame? In order to prevent duplicate work/effort I can/would wait till you are "done". WDYT

Regards
Clemens


> -----Original Message-----
> From: Mike Moulton [mailto:mike@meltmedia.com]
> Sent: Sunday, August 15, 2010 7:09 AM
> To: dev@sling.apache.org
> Subject: Re: extending jQuery JCR Resource explorer
>
>
> On Aug 13, 2010, at 10:47 PM, Clemens Wyss wrote:
>
> > I had a first look at your explorer. If I get this right:
> > + new, more appealing, GUI
> I plan on making this UI cleaner too, just didn't have time
> to have one of my designers make me a better comp.
>
> > + new js-tree
> The big problem with this tree is it pre-loads the entire
> tree structure. This will not scale well. This is definitely
> an item I think needs work.
>
> > + properties are no more being edited inline, which makes sense
> I did this because I planned on eventually making the UI's
> customizable, via plugins, based on primary type, etc.
>
> > + privileges, minimal
> The reading of privileges is there, it's still missing
> editing. Though, this should be rather easy given the
> existing framework I have in there.
>
> > did I miss a "hidden feature"?
> Nothing hidden that comes to mind. I had planned some
> additional features though, given time. Like...
>
> - Principal / Group management
> - Custom UI Plugins
> - Node type browser / management
> - Content loading / exporting interface
>
> >
> >> -----Original Message-----
> >> From: Clemens Wyss [mailto:clemensdev@mysign.ch]
> >> Sent: Saturday, August 14, 2010 7:20 AM
> >> To: 'dev@sling.apache.org'
> >> Subject: RE: extending jQuery JCR Resource explorer
> >>
> >>
> >> Hi Mike,
> >> cool. If you don't mind, I will take "your" code base and
> >> build upon this
>
> Your welcome to use it as you wish. As I have time, I can
> help further this along as well.
>
> >>
> >> Thx
> >> Clemens
> >>
> >>> -----Original Message-----
> >>> From: Mike Moulton [mailto:mike@meltmedia.com]
> >>> Sent: Saturday, August 14, 2010 12:00 AM
> >>> To: dev@sling.apache.org
> >>> Subject: Re: extending jQuery JCR Resource explorer
> >>>
> >>>
> >>> I'm a little late to this thread but I wanted to bring this
> >>> up anyway. A while back when I first was learning Sling I
> >>> created an extended explorer based on the original version in
> >>> the contrib. section. My explorer uses jQuery and
> >>> accomplished most of the items of the current jQuery
> >>> explorer. Before an extended set of work started on
> >>> enhancements I wanted to donate this codebase in case it's of
> >>> any use in this effort. I would love to see a mature explorer
> >>> ship as a part of Sling, and any work I can do to help that,
> >>> I will do.
> >>>
> >>> I created SLING-1653 [1] with the codebase in it.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/SLING-1653
> >>>
> >>>
> >>> On Aug 13, 2010, at 9:21 AM, Bertrand Delacretaz wrote:
> >>>
> >>>> On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss
> >>> <cl...@mysign.ch> wrote:
> >>>>> ...Anything important/fancy missing? How would you
> >>> priorize these features?..
> >>>>
> >>>> A nice thing would be to use the Sling script resolution
> to plugin
> >>>> custom content editors based on resource types.
> >>>>
> >>>> Maybe just use .explorer.edit selectors to generate a
> composite UI
> >>>> where users can plugin their own editing components, and define a
> >>>> simple set of guidelines/constraints that those components must
> >>>> follow.
> >>>>
> >>>> -Bertrand
> >>>
> >>>
> >>
>
> -- Mike
>

Re: extending jQuery JCR Resource explorer

[Mike Moulton <mi...@meltmedia.com>]

On Aug 13, 2010, at 10:47 PM, Clemens Wyss wrote:

> I had a first look at your explorer. If I get this right:
> + new, more appealing, GUI
I plan on making this UI cleaner too, just didn't have time to have one of my designers make me a better comp.

> + new js-tree
The big problem with this tree is it pre-loads the entire tree structure. This will not scale well. This is definitely an item I think needs work.

> + properties are no more being edited inline, which makes sense
I did this because I planned on eventually making the UI's customizable, via plugins, based on primary type, etc.

> + privileges, minimal
The reading of privileges is there, it's still missing editing. Though, this should be rather easy given the existing framework I have in there.

> did I miss a "hidden feature"?
Nothing hidden that comes to mind. I had planned some additional features though, given time. Like...

- Principal / Group management
- Custom UI Plugins
- Node type browser / management
- Content loading / exporting interface

> 
>> -----Original Message-----
>> From: Clemens Wyss [mailto:clemensdev@mysign.ch]
>> Sent: Saturday, August 14, 2010 7:20 AM
>> To: 'dev@sling.apache.org'
>> Subject: RE: extending jQuery JCR Resource explorer
>> 
>> 
>> Hi Mike,
>> cool. If you don't mind, I will take "your" code base and
>> build upon this

Your welcome to use it as you wish. As I have time, I can help further this along as well.

>> 
>> Thx
>> Clemens
>> 
>>> -----Original Message-----
>>> From: Mike Moulton [mailto:mike@meltmedia.com]
>>> Sent: Saturday, August 14, 2010 12:00 AM
>>> To: dev@sling.apache.org
>>> Subject: Re: extending jQuery JCR Resource explorer
>>> 
>>> 
>>> I'm a little late to this thread but I wanted to bring this
>>> up anyway. A while back when I first was learning Sling I
>>> created an extended explorer based on the original version in
>>> the contrib. section. My explorer uses jQuery and
>>> accomplished most of the items of the current jQuery
>>> explorer. Before an extended set of work started on
>>> enhancements I wanted to donate this codebase in case it's of
>>> any use in this effort. I would love to see a mature explorer
>>> ship as a part of Sling, and any work I can do to help that,
>>> I will do.
>>> 
>>> I created SLING-1653 [1] with the codebase in it.
>>> 
>>> [1] https://issues.apache.org/jira/browse/SLING-1653
>>> 
>>> 
>>> On Aug 13, 2010, at 9:21 AM, Bertrand Delacretaz wrote:
>>> 
>>>> On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss
>>> <cl...@mysign.ch> wrote:
>>>>> ...Anything important/fancy missing? How would you
>>> priorize these features?..
>>>> 
>>>> A nice thing would be to use the Sling script resolution to plugin
>>>> custom content editors based on resource types.
>>>> 
>>>> Maybe just use .explorer.edit selectors to generate a composite UI
>>>> where users can plugin their own editing components, and define a
>>>> simple set of guidelines/constraints that those components must
>>>> follow.
>>>> 
>>>> -Bertrand
>>> 
>>> 
>> 

-- Mike

RE: extending jQuery JCR Resource explorer

[Clemens Wyss <cl...@mysign.ch>]

I had a first look at your explorer. If I get this right:
+ new, more appealing, GUI
+ new js-tree
+ properties are no more being edited inline, which makes sense
+ privileges, minimal
did I miss a "hidden feature"?

> -----Original Message-----
> From: Clemens Wyss [mailto:clemensdev@mysign.ch]
> Sent: Saturday, August 14, 2010 7:20 AM
> To: 'dev@sling.apache.org'
> Subject: RE: extending jQuery JCR Resource explorer
>
>
> Hi Mike,
> cool. If you don't mind, I will take "your" code base and
> build upon this
>
> Thx
> Clemens
>
> > -----Original Message-----
> > From: Mike Moulton [mailto:mike@meltmedia.com]
> > Sent: Saturday, August 14, 2010 12:00 AM
> > To: dev@sling.apache.org
> > Subject: Re: extending jQuery JCR Resource explorer
> >
> >
> > I'm a little late to this thread but I wanted to bring this
> > up anyway. A while back when I first was learning Sling I
> > created an extended explorer based on the original version in
> > the contrib. section. My explorer uses jQuery and
> > accomplished most of the items of the current jQuery
> > explorer. Before an extended set of work started on
> > enhancements I wanted to donate this codebase in case it's of
> > any use in this effort. I would love to see a mature explorer
> > ship as a part of Sling, and any work I can do to help that,
> > I will do.
> >
> > I created SLING-1653 [1] with the codebase in it.
> >
> > [1] https://issues.apache.org/jira/browse/SLING-1653
> >
> >
> > On Aug 13, 2010, at 9:21 AM, Bertrand Delacretaz wrote:
> >
> > > On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss
> > <cl...@mysign.ch> wrote:
> > >> ...Anything important/fancy missing? How would you
> > priorize these features?..
> > >
> > > A nice thing would be to use the Sling script resolution to plugin
> > > custom content editors based on resource types.
> > >
> > > Maybe just use .explorer.edit selectors to generate a composite UI
> > > where users can plugin their own editing components, and define a
> > > simple set of guidelines/constraints that those components must
> > > follow.
> > >
> > > -Bertrand
> >
> >
>

RE: extending jQuery JCR Resource explorer

[Clemens Wyss <cl...@mysign.ch>]

Hi Mike,
cool. If you don't mind, I will take "your" code base and build upon this

Thx
Clemens

> -----Original Message-----
> From: Mike Moulton [mailto:mike@meltmedia.com]
> Sent: Saturday, August 14, 2010 12:00 AM
> To: dev@sling.apache.org
> Subject: Re: extending jQuery JCR Resource explorer
>
>
> I'm a little late to this thread but I wanted to bring this
> up anyway. A while back when I first was learning Sling I
> created an extended explorer based on the original version in
> the contrib. section. My explorer uses jQuery and
> accomplished most of the items of the current jQuery
> explorer. Before an extended set of work started on
> enhancements I wanted to donate this codebase in case it's of
> any use in this effort. I would love to see a mature explorer
> ship as a part of Sling, and any work I can do to help that,
> I will do.
>
> I created SLING-1653 [1] with the codebase in it.
>
> [1] https://issues.apache.org/jira/browse/SLING-1653
>
>
> On Aug 13, 2010, at 9:21 AM, Bertrand Delacretaz wrote:
>
> > On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss
> <cl...@mysign.ch> wrote:
> >> ...Anything important/fancy missing? How would you
> priorize these features?..
> >
> > A nice thing would be to use the Sling script resolution to plugin
> > custom content editors based on resource types.
> >
> > Maybe just use .explorer.edit selectors to generate a composite UI
> > where users can plugin their own editing components, and define a
> > simple set of guidelines/constraints that those components must
> > follow.
> >
> > -Bertrand
>
>

Re: extending jQuery JCR Resource explorer

[Mike Moulton <mi...@meltmedia.com>]

I'm a little late to this thread but I wanted to bring this up anyway. A while back when I first was learning Sling I created an extended explorer based on the original version in the contrib. section. My explorer uses jQuery and accomplished most of the items of the current jQuery explorer. Before an extended set of work started on enhancements I wanted to donate this codebase in case it's of any use in this effort. I would love to see a mature explorer ship as a part of Sling, and any work I can do to help that, I will do.

I created SLING-1653 [1] with the codebase in it.

[1] https://issues.apache.org/jira/browse/SLING-1653


On Aug 13, 2010, at 9:21 AM, Bertrand Delacretaz wrote:

> On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss <cl...@mysign.ch> wrote:
>> ...Anything important/fancy missing? How would you priorize these features?..
> 
> A nice thing would be to use the Sling script resolution to plugin
> custom content editors based on resource types.
> 
> Maybe just use .explorer.edit selectors to generate a composite UI
> where users can plugin their own editing components, and define a
> simple set of guidelines/constraints that those components must
> follow.
> 
> -Bertrand

RE: extending jQuery JCR Resource explorer

[Clemens Wyss <cl...@mysign.ch>]

> A nice thing would be to use the Sling script resolution to plugin
> custom content editors based on resource types.
sounds interesting

> -----Original Message-----
> From: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
> Sent: Friday, August 13, 2010 6:22 PM
> To: dev@sling.apache.org
> Subject: Re: extending jQuery JCR Resource explorer
>
>
> On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss
> <cl...@mysign.ch> wrote:
> > ...Anything important/fancy missing? How would you priorize
> these features?..
>
> A nice thing would be to use the Sling script resolution to plugin
> custom content editors based on resource types.
>
> Maybe just use .explorer.edit selectors to generate a composite UI
> where users can plugin their own editing components, and define a
> simple set of guidelines/constraints that those components must
> follow.
>
> -Bertrand
>

Re: extending jQuery JCR Resource explorer

[Bertrand Delacretaz <bd...@apache.org>]

On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss <cl...@mysign.ch> wrote:
> ...Anything important/fancy missing? How would you priorize these features?..

A nice thing would be to use the Sling script resolution to plugin
custom content editors based on resource types.

Maybe just use .explorer.edit selectors to generate a composite UI
where users can plugin their own editing components, and define a
simple set of guidelines/constraints that those components must
follow.

-Bertrand