I definitely believe the Sling deserves to have better node explorer then it does now.
Would it be based on the RESTed? I would be thrilled to have it in there, however this is something the community needs to decide on. Having said that, I am very much willing to help out in any case. ---- In my opinion, the node explorer is most likely the first thing new user is exposed to. The curl command line access is cool, but the appreciation of it comes much later down the line. I actually didn't start to appreciate the power and beauty of the Sling (I knew, tried it and failed before) until I had an access to the CQ with CRXDE-lite which enabled me to easily see the content itself. The Sling is content driven, everything is content, we all know that. But it didn't really sinked in for me until I was actually able to see it visually. My rational for creating the RESTed was not just to have a node browser but also quick and customizable user interface to the content. I do use it personally as kind of free-form database (along the like of EverNote / SimpleNote / DevonThink....). I think this would be the killer 'use case' for the Sling actually. I'll release some of this stuff later on... perhaps it could be used to inspire others. Ondrej On Wed, Apr 10, 2013 at 1:43 PM, Bertrand Delacretaz <[email protected] > wrote: > Hi Ondrej, > > On Tue, Apr 9, 2013 at 10:51 PM, Ondrej Florian <[email protected]> wrote: > > ...The first one is RESTed and it is basically a node 'explorer' with > potential to become a base for simple development environment. > > You'll find it here => https://github.com/onflapp/RESTed ... > > I briefly tested it (create a node with sling:resourceType, create > folders and add a rendering script to it), works very well and the > interface is very intuitive and looks good! > > Do people think we should have this in Sling, assuming Ondrej is > interested in maintaining it here? I do. > > -Bertrand >
