2009/3/19 Bertrand Delacretaz <[email protected]>
>
>
> Sure - creating a minimal "kernel" that allows for editing plugins
> would be a good start.
Just to avoid confusion ...
What do you mean by "editing plugins" ? a specific editor for each kind of
content ?
>
>
> And the rest ("create editing plugins for the Sling JCR Explorer")
> could still be a GSoC project?
why not .. Depending on what does mean "editing plugins" :-).
>
>
> > Can we based this work on the following proposal [1] ?
>
> I think so, and feel free to update that of course.
>
> One thing is that the resulting explorer should IMHO be usable for
> pure JCR repositories (non-Sling), even though the explorer itself
> would run under Sling. Probably not a big challenge, just one thing to
> add to the spec.
with use cases like : register a new jcr repo, see the list of available
repos, ...
>
>
> > ...What about the UI framework to use ? A JCR Explorer will require
> advanced
> > UI widgets and I'm wondering which framework will be the more
> appropriate,
> > Dojo ? Gwt ? Extjs ? .... ? :-(
> > I have a prototype with Extjs but It is certainly not compatible with the
> > ASF license....
>
> Yes, that's the problem. We have a few things based on dojo already,
> and the Felix OSGi console now uses jQuery, so I guess options are
> open. I think I'd vote for jQuery to have some alignement with the
> Felix project, but whoever does the job gets to decide I guess.
>
> Or better, leave the choice of the UI framework to the set of plugins ;-)
My personal short list is jquery and gwt but I have to check how gwt can
work with Sling.
jquery is a little bit young in term of widgets like treeview, grid.
I'm just wondering if working with GWT will not be more productive for this
kind of application.
Christophe
>
>
> -Bertrand
>
> > [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html
>
