On Sat, Apr 26, 2008 at 7:16 PM, Carsten Ziegeler <[EMAIL PROTECTED]>
wrote:

>
> Well, on the other hand, it has been pointed out that the real issue is
> just the fact that all scripts are named "htlm.*". I'm really not very
> optimistic that the simple looking solution to duplicate the node name (or
> whatever makes up the last node in the hierarchy) to get the file name is a
> clear and simple concept. Telling people that they can write "foo.jsp" to
> get html while they have to use "pdf.jsp" to get a pdf, seems very
> complicated to explain and understand. And as I pointed out, as soon as you
> are heavily using any other format than html, you end up with the same mess
> (all files named pdf.*)
>

I did think a bit about the refactoring and renaming problems that might
occur when using prefixes. Since this is a restless architecture it might be
necessary to replicate at least the script which is calling the script which
is needed by both resources. This is pretty easy when having the scripts
named the same way (no prefixes). Having a prefix would require renaming, as
well as renaming the parent node would require changing the prefix. (which
would break the default refactoring features for renaming in Eclipse)

Propably it is usefull to remember that a script is never identified simply
by its name but additionaly the path. So the name does never identify the
script (which script is called?) but identfies under which circumstances it
is called(when is it called?).

It may be usefull to have an optional prefix (nodename as prefix) to
"freeze" a path and prevent usage at another location. (This feature would
come along with the renaming problem but would at least not be the default
behaviour and require the awareness of the developer of the constraint he
produces).

Dominik

Reply via email to