[Typo3-dev] singletons instead of pre-loaded objects

Kasper Skårhøj kasper2004 at typo3.com
Thu Aug 12 16:15:34 CEST 2004


> Many classes are just "namespaces" for functions (eg t3lib_div), some 
> are just way too huge (tslib_content!) and mix up different 
> functionality (eg the mail composing classes also send the mails) or 
> have too much functionality (piBase has more stuff then your average 
> plugin needs).
> 
> Some points are not real issues, but eg tslib_cObj is very hard to 
> extend just because of its size (and its - sorry - not really good 
> designed from an OO viewpoint).

True.

But again; It works and it is not an overnight operation to change with
backwards compatibility in mind.

Therefore we should all support a guy like Dan Frost who has outlined a
new vision for TypoScript which is more object oriented. I'm all padding
his shoulders shouting "go go go" to take this to a level where it will
gradually phase the old "tslib_cobj" class out and introduce this as a
total substitution. That would even carry with it another great
advantage - that more and more of TYPO3s important bits are supplied but
others than me! (which is also a long-term goal for us).








More information about the TYPO3-dev mailing list