[TYPO3-50-general] RFC: Short filenames
Robert Lemke
robert at typo3.org
Tue Jan 27 10:53:01 CET 2009
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?
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
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,
robert
More information about the TYPO3-project-5_0-general
mailing list