[Typo3-dev] [Good||Silly] idea ???

Kraft Bernhard kraftb at gmx.net
Tue Mar 8 14:01:53 CET 2005


dan frost wrote:
> The main problem with XCLASSes in TYPO3 is the lack of a separation of 
> concerns - people are extending one class for several reasons. There 
> should be several classes.

You're right.

I noted for example that link-generation functions are spread all over T3 ..
pibase, t3lib_div, etc ... while other functions which don't fit together are
crowded into one class.

Would need some cleanup and some "creative" person to find fitting names for
new classes (Often a problem: finding the right name for each "thing")

> Nice idea though - have you come across Aspect Oriented Programming? 
> Might make things easier...

No ... haven't heard that term before.

googled and found:
http://www-106.ibm.com/developerworks/java/library/j-aspectj/

Question: Isn't that a possiblity to do "automated" tasks. The only example on this
page was logging so I'm a little bit curious what else I can do with it (except something
like "function-constructors/destructors" - I would call an aspect like the log-thing like
that :)

Why would that help for overloading methods/classes.

How can such a thing be implemented in php ? are there any possibilties ?




greets,
Bernhard
-- 
Kraft Bernhard
MOKKA Medienagentur <http://www.mokka.at>
T: +43 - 1 - 895 33 33 - 50




More information about the TYPO3-dev mailing list