[TYPO3-mvc] extension key: ext_base vs. extbase

[Jochen Rau]

Hi,

I don't mind if it is ext_base or extbase as long as the extension 
provides a good base for extension developers.

It wasn't a typo. ext_base and therefore ExtBase follows a stringent 
rule: two separated english words are connected with an underscore. But 
what about abbrevations and acronyms? Well, I'd say if there must be at 
least two chars in each "section". "my html class" results in 
MyHtmlClass (and not MyHTMLClass), for example.

Now I have to remember that "Extension Base" results in "Extbase" and 
not "ExtBase".

To make a long story short: I'll change the naming to Extbase and 
continue with making Extbase better afterwards. ;-)

Regards
Jochen


Michael Stucki schrieb:
> Hi Ingo,
> 
> see Jochens post from March 26 - maybe it was just a typo?
> 
> I would prefer "extbase" over "ext_base" anyway, but I think you are
> right that we already agreed on this.
> 
> - michael
> 
> Ingo Renner schrieb:
>> Hi all,
>>
>> I was a little surprised to see Jochen announce the new extension ke to
>> be ext_base as my understanding from the review session in Laax was that
>> it's going to be extbase.
>>
>> IMO extbase would have a few advantages over ext_base:
>>
>> * no conflicts due to the underscore (class names, table names and so on
>> ... extbase, e_xtbase, ex_tbase, ext_base, ... and so on all result in
>> the same table and class names)
>>
>> * with the current conventions with the new MVC framework it would be
>> ExtBase in class names, this is no problem with good IDEs and editors
>> but in case you'd have to do quick jobs on the commandline or through a
>> textarea field you'd always have to make sure to type the b in uppercase
>>
>>
>> Apart from that I remember having registered the key extbase quite some
>> time before the discussion for the MVC project even started and to suit
>> as a multipurpose extension base that would also bring a small framework
>> of other often used classes like feedreaders/writers, and so on (though
>> by now I'd say that's something for t3lib)
>>
>>
>> To make a long story short: I'd welcome it if the extension key is going
>> to be extbase instead of ext_base.
>>
>>
>> best
>> Ingo
>>
> 
>