[TYPO3-ect] Zend style extensions scheme

[Peter Niederlag]

Hello,

Elmar Hinz schrieb:
> Peter Niederlag schrieb:
> 
>>Would it make sense to "flatten" to always flatten the extension-key, at
>>least for naming of directories? Could we handle such a big change?
>>
> 
> 
> Hello Peter,
> 
> last week I provided a patch for TER2 that checks that the key lalala
> will not be given if la_la_la is already registered. It's already
> online. One step forward to unique pathes at least.
> 
> I would propose to forbid underscores in new keys at all. That would
> also be a preparation for a migration to PEAR style where underscores
> have special functionality.
> 
> I would like to see camelStyledKeys instead. Do you think that would
> cause problems with DB names and filesystem on WIN?

Good question. I think there can be unsolvable problems, since
apparently PEAR works on Windows. We just need to make sure 'camelCase'
and 'camelcase' is interpreted as the same ext-Key by TER2.

I really like the '_' as separator, part of extension-key.

Why not keep validation as is, that is let the '_' be in there, but just
not using it anywhere else but as extension-key?

Well, I guess I might have to adopt and accept the fact that camelCase
is claner and mor consistant.

> Where is the underscore version of keys used at all?
> I think that is only in the pathes to the extension. Am I right?

That seems to be true. That#s good news. ;)

> All other uses of the key are of the flattend version? Right?

seems so.

> All calls for files go through the extMgm?

Theres is things like
"label" => "LLL:EXT:foo_bar/locallang_db.php:tx_foobar_catalog.responsible",

> Then we could indeed flatten all keys with one automated skript. Only
> hardcoded pathes would break.

Personally I am all in favor of this.

Peter
-- 
Peter Niederlag
http://www.niekom.de * TYPO3 & EDV Dienstleistungen *
http://www.typo3partner.net * professional services network *