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

[Johannes Reichardt]

Hi Dan and others,

just as idea - how about a public white paper with well thought 
specifications for such an "ideal typo3"? If that is perfect people 
might want to participate anyway - also i wouldnt care at all about 
backwards compatibility since it makes things more complicated than 
necessary - also converting extensions is not that hard since the logic 
itself always remains.

- Johannes

>>
>>
>> But an expiremtal branch living in the SF CVS?
>
>
> Maybe not - it doesn't have to be
>
>>
>>> Every few months we could try to merge parts of the playground 
>>> branch with the main branch and make a "demo" version of Kasper et 
>>> al to test the changes.
>>
>>
>>
>> Staying on SF would have the benefit of CVS's merge feature.
>>
>> And I recommend small changes. You'll never ever get hundres of 
>> changed lines into the Core. Kasper is like Linus in this respect. 
>> Make it small chunks so he can chew on it.
>>
>
> Ok - so put the playground somewhere else so we can really hack around 
> without worrying anybody.
>
> In order to "prepare for the future" we'll need to be able to try 
> completely different things.
>
> dan
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
>