You are welcome to share your experience. We can take the necessary time to choose and compare UI frameworks.
Is is possible to see what you are doing with Gwt/Sling ? Thanks 2009/3/19 Glenn Silverman <gl...@glenn3.securesites.net> > I've been getting a lot of mail on this subject, and I'm working on a GWT > front end in Sling > to create and query repository entries for my own projects. I would > certainly be happy to > contribute my two-cents to create a full-blown repository explorer. I > think there might be > an Eclipse incubator project to create one as well, using RCP, or perhaps > RAP tooling. > > Glenn Silverman... > > > Michael Dürig wrote: > >> >> AFAIR Bertil implemented a simple Sling explorer using MooTools while >> working on his thesis. >> >> See https://issues.apache.org/jira/browse/SLING-840 >> >> Michael >> >> Bertrand Delacretaz wrote: >> >>> On Thu, Mar 19, 2009 at 12:37 PM, Christophe Lombart >>> <christophe.lomb...@gmail.com> wrote: >>> >>>> 2009/3/19 Bertrand Delacretaz <bdelacre...@apache.org> >>>> >>>>> ... Ok - a good JCR explorer is something that many of us are looking >>>>> forward to, and it's not a trivial task, and Sling's OSGi plugins open >>>>> some very interesting possibilities.... >>>>> >>>> >>> I am interested to work on that even if it will take a long time to get >>>> a >>>> nice result. We can expect that others will be interesting to >>>> contribute. >>>> Futhermore, it is certainly possible to start with a very simple version >>>> and >>>> add more and more features. >>>> >>> >>> Sure - creating a minimal "kernel" that allows for editing plugins >>> would be a good start. >>> >>> And the rest ("create editing plugins for the Sling JCR Explorer") >>> could still be a GSoC project? >>> >>> 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. >>> >>> ...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 ;-) >>> >>> -Bertrand >>> >>> [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html >>>> >>> >> >
