[Typo3-dev] Normalisation / OOP - a Case Study (ObTS)

[dan frost]

Martin T. Kutschker wrote:
> dan frost wrote:
> 
>>
>> My conclusions are:
>> - In TYPO3 there is often a "hook" point where we could hijack the 
>> flow into alternative classes (like i did in the switch statement)
> 
> 
> This is good. And is see that it is possible to make large changes if 
> such a hook exist. It's much harder if there is no such hook and even 
> harder if no such hook can ever exist because the task simply 
> invlolves/affects many parts of the code.

Yes - but: I had to make my own hook for a long time. Ok, this is 
hacking but it makes sense for a little while. you can test stuff.
> 
>> In my opinion: it is best to start with the attitude "breaking stuff 
>> doesn't matter - just make it great" and work back.
> 
> 
> I saw the reason for ObTS, I don't see it for normalisation.

Yes and no... It's nice to had a clean slate at the beginning and then 
worry about things later on