Ok, *if* we want to change the behaviour of the script resolution, we
should definitly do this before our first planned release.
Carsten
Alexander Klimetschek wrote:
Am 14.04.2008 um 18:11 schrieb Carsten Ziegeler:
Hmm, isn't there a better way? This solves the problem only partially
- I ran
into the same trouble if I want to support a different format like
pdf; still all my scripts would be named "pdf.esp".
Without further thinking if this creates other problems, would about
using a simple rule like "replacing the last slash with a dot"?
So instead of looking it /apps/foo/html.esp Sling would look at
/apps/foo.html.esp.
With selectors this becomes /apps/foo.selector.html.esp".
Hmm, wouldn't it be solved by extending the proposed list as follows?
Here each selector-specific script can also be named with the (uniquely
named) resource type in the file name:
/apps/foo/selector/html.esp
/apps/foo/selector.html.esp (same but with dots instead a subfolder)
/apps/foo/foo.selector.html.esp (NEW, for unique filenames of selector
scripts)
/apps/foo/selector.esp
/apps/foo/foo.selector.esp (NEW, for unique filenames of selector scripts)
/apps/foo/html.esp (not specific to the selector)
/apps/foo/foo.esp (not specific either)
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
>> Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ <<
--
Carsten Ziegeler
[EMAIL PROTECTED]
