On Thu, Apr 17, 2008 at 8:20 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > ...Rethinking the whole issue, I'm not sure if it's really worth changing the > behaviour as this would mean that all users have to change their paths for > scripts....
You mean our two users? Just kidding, but I'm not sure if we have that many users at the moment. > ... So which real problems are we trying to fix?... 1) Most scripts, being GET scripts for html content in a typical app, are named html.esp (or html.whatever depending on the language). That can be confusing when editing them, and lead to errors, developer usability suffers. 2) Having all scripts that relate to a given resource type in the same folder, as opposed to split into several folders as is currently the case, makes it easier to have an overview of what's going on. I agree that it's late to make such a change, but the benefits seem worth the effort for me, and now (i.e. before we add more examples and documentation) seems to be the right time. -Bertrand
