[TYPO3-50-general] RFC: Short filenames
Malte Jansen
mail at maltejansen.de
Tue Jan 27 20:47:53 CET 2009
Hi Robert,
Robert Lemke schrieb:
> Hi folks,
>
> we've been discussing this back and forth for almost two years now ;-),
> now I think it's time to put it on the table again.
> As you know the filename of a class file currently reflects the fully
> qualified class name. The question is if we should change this to the
> much shorter unqualified class name:
>
> F3_FLOW3_MVC_Controller_ActionController.php -> ActionController.php
>
> Before you shout "yeah, please", please try hard to think of any
> disadvantages this might give and discuss them in this thread. Please
> also give your personal vote: Should we switch to short filenames?
+1 for short filenames
>
> Here are my thoughts:
>
> Pro:
>
> - shorter to write
> - simplifies move-to-different-namespace refactorings
> - directory structure looks cleaner
> - shorter file names _might_ help avoiding the "paths can only be 200
> characters long" problems on some exotic operating systems
- handling in a tree-view is much easier (e.g. eclipse)
>
> Con:
>
> - doesn't give the full hint on the contents (DefaultController.php ?)
> - name conflicts / confusion when single files are deposited
> temporarily on the desktop or elsewhere
> - classes can't be found that easily anymore in Eclipse's resource
> browser which uses filenames (go to "Navigate" > "Open Resource")
>
> My vote (before discussion): short filenames
Cheers,
Malte
More information about the TYPO3-project-5_0-general
mailing list