[TYPO3-50-general] Old names in FLOW3 code

[Robert Lemke]

Hi Martin,

Am 08.03.2008 um 17:10 schrieb Martin Kutschker:
>
> But what does this mean if I want to use/extend the framework for my  
> own
> application? Do I have to stick to just one top-level namespace for my
> own code?

Technically you can use any class name or top-level namespace but  
currently
the package manager and class loader just ignores anything else than  
T3_*.
However, you can always manually register any class or your own class  
loader
and it would be easy to add a method to the package manager which  
allows for
registering new top-level namespaces.

I suggest implementing that as soon as there's a demand for it.

> I assumed that I could use T3_/F3_ (or better FLOW3_) along with  
> MYAPP_
> names. You have probably discussed the names of top-level namespaces,
> but longer names like FLOW3 or TYPO3 are nice than F3 and T3. And you
> seem to prefer "speaking" anyway.

The question is where to draw the line between packages belonging to  
FLOW3 / TYPO3
and which packages are "the application". Look at the TYPO3 extension  
- their class
name starts with "tx_" and it would be difficult to tell which  
extension in an
average project is "the application".

So I suggest that all those who are writing applications based on  
FLOW3 just use our
prefix and if that's not possible or if legacy code needs to be  
integrated we add some
feature which makes that possible.

About the question "F3_" or "FLOW3_" ... yes, generally I prefer  
speaking names but
I don't see a problem using the shortcut here. Some class like  
"FLOW3_FLOW3_Component_Manager"
looks too ugly for me, don't you think?

robert
-- 
http://typo3.org/gimmefive
http://buzz.typo3.org/people/robert-lemke/