[TYPO3-dev] OT: Re: PHP requirement

[Xavier Perseguers]

Hi,

> MVC, factory and strategy can be learned without ExtBase or FLOW3. From
> what I read here dependecy injection is not part of ExtBase.

The way 4.2 is coded is quite far away from FLOW3's "purity" level. But 
it works and is used in production, I agree :-)

Now, dependency injection is not part yet but could become part of 
ExtBase later. Do you think it is a must? I don't think so. Of course it 
would be very great but let's start creating well-coded extensions, 
refactor the core where it makes sense and "slowly" move to new paradigms.

I agree however that MVC, factory and all those design patterns should 
be learned "outside" of TYPO3, with references but then examples are 
highly needed to put the theory in action.

I know core devs and many others already write good extensions with MVC 
and other "state-of-the-art" paradigms in mind but there is a *huge* 
list of extensions that do not have this level of quality (documentation 
is another point thought).

This is why I find ExtBase a good answer for turning the new paradigm 
theory into something more palpable, that fits as well as possible into 
TYPO3's world.

> Many extensions use already MVC and factories, perhaps also strategies
> could be introduced into the Core when it makes sense during a
> "refactoring session".

I agree.

> But if it's just a "toy" and a learning tool then it shouldn't be named
> ExtBase which implies to be a real, stable foundation for the future.

For the time being I must admit that I could not (yet) use it in a 
real-life scenario. But I do not consider it as a toy, only as an 
unfinished work that needs quite some work and feedback and perhaps 
helping hands to become the new base. Who is working on it except 
Jochen? He did such a great job for the moment...

I thought it should become part of 4.3, isn't it the case anymore?

Core devs should advertise its use and try it and give feedback to 
enhance it.

I do not say that people (Dmitry for instance - as I know its way of 
programming) should change their already good habits but only that 
"a-bit-less-good" programmers and "newbies" should learn a "better way", 
if not *THE* way to code (which btw does not exist).

> And why extensions only? Why not <InspiringName>Base to be accompanied
> by <InspiringName>FE and <InspiringName>BE?

I agree! As said I could not yet use ExtBase "as-this" but started to 
refactor my whole code to get the same directory structure and naming 
convention. This is also a way of using ExtBase I guess, as it would 
another developer to feel a bit more confortable than if I used any 
other CGL which would be great too.

Now, ExtBase targets FE but more and more I think that BE and FE 
programming should be much more similar. This is why I made a playground 
to find a way to define common abstract controllers and views to 
hopefully have much less this separation in mind. And at the same time, 
I try to define kind-of best practices to use ExtJS as there is no real 
example on how to integrate it nicely into the rest.

> Anway, those who want to use it, may do so. I'm just a bit disappointed
> that's all.

I'm not!

ExtBase is definitively a bridge to holy v5 and FLOW3. And using FLOW3 
instead of ExtBase is I guess a wish from all of us.

-- 
Xavier Perseguers
DBAL-Member

http://xavier.perseguers.ch/en/tutorials/typo3.html