[TYPO3-core] RFC: #15094: Refactor of content objects of tslib_content

Dmitry Dulepov dmitry at typo3.org
Mon Jul 19 11:44:39 CEST 2010


Hi!

Steffen Kamper wrote:
>> tslib_content_Coa
> should we now use ContentObjectArray ?

+1.

>> tslib_content_CoaInt
> see above - btw, what does Int means originally?

I always thought of it as of "Internal". Not sure it is correct though.

>> tslib_content_Ctable
> have no idea what C stands for

"Content"

>> tslib_content_PhpScript
>> tslib_content_PhpScriptInt (do we need these two, maybe deprecate them?)

+1 to deprecate.

> We also have this obts right now, i'm not sure if it's still used, but
> it's also not following the naming conventions. This way adding own
> elements is now like a "gap" as tslib_content try to hint the class name
> with tslib_content_[object], but without any official guide, just a side
> effect. I would appreciate any suggestions how to deal that ;)

I would say we need to deprecate it. That project is long time dead I think.

-- 
Dmitry Dulepov
TYPO3 core&security teams member
Twitter: http://twitter.com/dmitryd
Read more @ http://dmitry-dulepov.com/


More information about the TYPO3-team-core mailing list