I understand. But what I mean is that I know so little about Sling so I can't even be trusted with what chapters to have in a documentation of it. What I would like to be provided with is something like this;
1. Quick start to develop with Sling 1.a Installation 1.b Check that things work 1.c Mount as webDAV (in windows and Linux) 1.d Most important facts about Sling resources. Where the monsters are and how to defy them. 2. Examples on how to access Sling resources from client 2.a From Ajax-clients in browser 2.b From Java programs 3. Examples on how to write Sling server-side scripts 3.a What kind of resources can be used in scripts 3.b Simple example in Rhino 3.c Simple example in Erb 3.d Simple example in Jsp 4. etc... And then I can fill in the actual content by asking around adn experiment, but I would need someone to help me with the general outline. Cheers, PS On Jan 19, 2008 3:59 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi Peter, > > Am Samstag, den 19.01.2008, 15:36 +0100 schrieb Peter Svensson: > > YES! It worked. Thanks so much for saturday support :) > > Actually you do have a lot of documentation, but only for internal > > development, not for devlopers using Sling. > > Yes. And especially the docs on the site is outdated and does not > reflect the current Sling API.... > > > I can write that, but I have to > > learn it first. > > Now, this is good news ! > > > If someone gave me a chapter index, with sub-subjects, I could fill them > in > > by pestering people on this list, and it could be published as user > > (developer of) dox. > > There is nothing like that. My current approach is to take, what is > there and try to adapt to the current Sling API. This documentation > stuff is in flux right now, and I tend to create docs upon user > problems. > > Regards > Felix > > > > > Cheers, > > PS > > > > On Jan 19, 2008 3:10 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > > > > > Hi Peter, > > > > > > Am Samstag, den 19.01.2008, 14:15 +0100 schrieb Peter Svensson: > > > > OK, Good that I've still _some_ intuition working :) But now I > wonder > > > where > > > > the path "/apps/nt/folder/" can be found? Is it somwhere in the > > > "real" > > > > filestructure of Sling, or is it within SLings own resource > hierarchy? > > > I > > > > can't seem to find it. > > > > > > The resource hierarchy of Sling is primarily based on the repository > > > content. So if you are looking for an /apps/nt/folder location, you > > > would look in the repository. If such a path does not exist, you may > > > create it yourself - e.g. in WebDAV by just creating the respective > > > directories. > > > > > > > > > > > I can't find /sling/script either. Should I create those directores, > and > > > if > > > > so, where? In my file system or inside SLing? > > > > > > You would create through WebDAV in the JCR Repository. > > > > > > > > > > > Sorry for all the confusion. > > > > > > No problem. We are very gratefull to everyone taking the path of > > > exploring Sling. It also shows us our documentation issues .... > > > > > > Regards > > > Felix > > > > > > > > > > > > > > Cheers, > > > > PS > > > > > > > > On Jan 19, 2008 12:42 PM, Bertrand Delacretaz < > [EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > On Jan 19, 2008 12:39 PM, Bertrand Delacretaz < > [EMAIL PROTECTED]> > > > > > wrote: > > > > > > > > > > > ...2. transform that to a valid repository subpath, so for > example > > > > > > nt:folder becomes nt:folder... > > > > > > > > > > ...becomes nt/folder, of course. > > > > > > > > > > -Bertrand > > > > > > > > > > > > >
