atom feed55 messages in org.apache.incubator.sling-devSimplifying script paths and names?
FromSent OnAttachments
Bertrand DelacretazApr 14, 2008 8:45 am 
Carsten ZiegelerApr 14, 2008 9:11 am 
Alexander KlimetschekApr 14, 2008 9:26 am 
Carsten ZiegelerApr 16, 2008 1:00 am 
Bertrand DelacretazApr 16, 2008 5:44 am 
Carsten ZiegelerApr 16, 2008 5:52 am 
Felix MeschbergerApr 16, 2008 8:11 am 
Carsten ZiegelerApr 16, 2008 9:10 am 
Carsten ZiegelerApr 16, 2008 11:20 pm 
Bertrand DelacretazApr 17, 2008 12:00 am 
Gert VanthienenApr 17, 2008 12:50 am 
Juanjo VázquezApr 17, 2008 1:34 am 
Alexander KlimetschekApr 17, 2008 1:48 am 
Michael MarthApr 17, 2008 6:39 am 
Bertrand DelacretazApr 18, 2008 12:21 am 
Bertrand DelacretazApr 18, 2008 12:25 am 
Felix MeschbergerApr 18, 2008 12:56 am 
Michael MarthApr 18, 2008 1:33 am 
Bertrand DelacretazApr 18, 2008 1:37 am 
Bertrand DelacretazApr 18, 2008 1:44 am 
Felix MeschbergerApr 18, 2008 2:11 am 
Bertrand DelacretazApr 18, 2008 2:16 am 
Felix MeschbergerApr 18, 2008 4:19 am 
Carsten ZiegelerApr 18, 2008 4:59 am 
Felix MeschbergerApr 18, 2008 5:54 am 
Bertrand DelacretazApr 18, 2008 5:59 am 
29 later messages
Subject:Simplifying script paths and names?
From:Bertrand Delacretaz (bdel@apache.org)
Date:Apr 14, 2008 8:45:52 am
List:org.apache.incubator.sling-dev

Hi,

Currently, working with selectors requires you to put scripts in subfolders, for example

/apps/foo/html.esp /apps/foo/someselector/html.esp

and worse, all GET scripts which produce html are named html.esp, which can be confusing when editing them.

We talked about this with David and Felix, here's a proposal for simplifying those names in the "happy case", while keeping the current conventions to resolve potential name conflicts where needed. Comments welcome.

= Proposal =

The following variants should be accepted for script names, examples:

a) sling:resourceType=foo, request = bar.html

Sling searches for the following scripts and uses the first one found:

/apps/foo/html.esp /apps/foo/foo.esp

The only change is that the script used for html rendering can optionally be named foo.esp, to avoid having many scripts called "html.esp" which is not practical when opening many of them in an editor or IDE.

a) sling:resourceType=foo, request = bar.selector.html

The following scripts can be used to process this request, the first one found being used:

/apps/foo/selector/html.esp /apps/foo/selector.html.esp (same but with dots instead a subfolder) /apps/foo/selector.esp /apps/foo/html.esp (not specific to the selector) /apps/foo/foo.esp (not specific either)

In the "happy case" people would then just have those two scripts to handle the above cases:

/apps/foo/foo.esp /apps/foo/selector.esp

-Bertrand