On 10/18/07, Tobias Bocanegra <[EMAIL PROTECTED]> wrote: > ...you would add a 'selector' for different views of the same content. > eg: > /content/blog/entry1.html for view and > /content/glob/entry1.edit.html for editing...
That's correct, see ScriptFilenameBuilderTest for examples of how this translates to different script names. The script names that microsling tries to find are also logged. > ...you just iterate over the child content and call <sling:include/> or > whatever the aequivalent in microsling is. we need to elaborate this... We don't have sling:include in microsling yet, I'll create a JIRA issue for that. > ...usually you would put the 'static' content, in a 'docroot' node as > nt:files and let the > default nt:file script spool them to the client.... We also need to enhance the default servlet to serve files...on my way to JIRA. -Bertrand
