I appreciate the feedback on suitability, as I don't know this area of programming very well. I suspect I will be two or three years on this project, so any mistakes will be biting me for quite some time. The built in sling explorer works well and gives me quite a lot of confidence that the programmatic side is working (tests are all very well but its nice to see stuff).
On Fri, Jul 8, 2011 at 4:03 PM, Bertrand Delacretaz <[email protected]> wrote: > On Fri, Jul 8, 2011 at 4:51 PM, Mark Herman <[email protected]> wrote: >> I agree, it sounds like Sling will work for what you need. Personally I >> first was interested in using the JCR, and after learning that, Sling was >> very easy to pick up. I would definitely recommend getting some sort of JCR >> explorer so you can get a feel of how a jcr repository works, looks and >> feels. There are open source projects or you can use Day's developer >> product.... > > There's even an explorer in Sling, > http://localhost:8080/.explorer.html if you have the > org.apache.sling.extensions.explorer bundle. > > It's not perfect, but improving it would be a great way of learning Sling ;-) > > -Bertrand >
