[TYPO3-ect] Final goal of the new framework ?

[Jean-Baptiste Rio]

Hi,

Thanks to JH and Michael for your answers
> 
> 1. Screw backwards compatibility: Anyone who still likes the XCLASS 
> hell, the GLOBALS['foo'] inflation, the weird includeonce and require 
> statements and various mysql_bla() calls is invited to maintain and 
> develop the 4.0 branch until GNU HURD comes out or the end of time...

I'm not that kind of guy :p I just want to avoid nights of work to 
simply rebuild my extensions because the main class has disappeared. As 
far as i have the insurance that the pibase class is still available, 
i'm ok with any kind of new framework.

> 
> 2. The basic extension *functionality* is not touched at all by the new 
> approach, so in the *worst* case, you'd just move some code around and 
> everything will be fine. I see this actually as a good thing because we 
> can finally enforce compatibility with DBAL and the CGL.

I have no experiment with DBAL stuff but i use the t3lib_div "exec_...3 
functions . Is it enough to be compatible or do you plan to modify that 
too ?

> The MVC approach has basically nothing to do with web services. I 
> personally dislike SOAP as it has too much overhead and 
> specificationisms. For now, we will build the new extensions with their 
> own libs (so they are "statically linked"), then get the libs into the 
> core and then see what's happening.

Sometimes i'm a bit surprised by the extension meaning the Typo3 
community has. I see three main kinds of extensions :
A - Short or heavy development to add new specific Typo3 functions 
(templavoila, ...)
B - Short (sometimes heavy) implementation of an external application / 
protocol / module / ... (by example : HTMLArea, NuSOAP)
C - Short implementation to modify, enhance, ... TCA and other Typo3 
static parameters

A => Targetted by the new framework ? Am I right ?

B => When you plug  an external application, made and managed by an 
external team, is it a clean job to statically link it ? I don't think 
so. Instead, it could be more valuable to leave it outside typo3 and to 
interact with it through web services.

C => Is it relevant to use the new framework ? I'm not sure : Too heavy, 
  not built for that goal,...

IMHO, when i start such a job, i design, fix the final goals, ask for 
people agreement, produce some document before binding a prototype. The 
risk i see for this new prototype is that it could be not understood as 
the good practice for new extensions.
Again, i'm not against this new prototype, i just "rise up my finger" 
and ask if you have thought to the "change management". It is just a 
question of adhesion, as we say in french :)

Sorry, if you feel that i try to slow down the process, it's not my aim.

Regards,

JB