[TYPO3-mvc] Typo3 4.5 - will all pibase extensions stop working?

David Bruchmann david at bruchmann-web.de
Mon Aug 23 12:19:40 CEST 2010


----- Ursprüngliche Nachricht -----
Von: Stephen Bungert <stephenbungert at yahoo.de>
Gesendet: Montag, 23. August 2010 11:09:10
An:
CC:
Betreff: Re: [TYPO3-mvc] Typo3 4.5 - will all pibase extensions stop 
working?
> I just recently started looking at fluid/extbase, I bought he book too.
>
>
> I started by trying to convert a pibase extension to extbase. It went really
> quick at first, list and everything are all automatically done, there is
> even a way to edit/delete records in the FE! I'm very impressed, I like it a
> lot, I plan on making all new extensions with extbase/fluid - but somethings
> that were easy, or that I knew how to do with pibase, I don't know about in
> extbase - there is still a lot that I have to learn - and getting used to
> the MVC structure. But I am glad that 4.5 is different from 5!
>


I've read about MVC since a longer time but didn't yet program an own 
extension. Nevertheless I tried some things and searched for special 
possibilities.

One (for me central) item is missing in both frameworks (pi_base and 
extbase): addressing multidimensional URLs i.e. to change only one cObj 
on a page like index.php?tx_xyz_abc[cObj_3][controller]=mycontroller.

Another item I'm missing in this context (but perhaps I still haven't 
discovered all the fluid-possibilities) that it's a bit hard or 
impossible until now to determine if foreign parameters shall be 
included in the URL like this:
index.php?tx_xyz_abc[cObj_3][controller]=mycontroller&tt_news[ttnews]=12
The URL-Functions in pi_base are a lot but in extbase/fluid I've the 
impression it's more limited until you don't write your own viewHelper.

Intention of this post is that you try out special challenges for the 
framework and post bug- and feature-Requests as soon as possible.

In the moment the situation is a bit difficult: on the one hand pi_base 
will be obsolet in future on the other hand extbase still isn't 
'perfect' or/and isn't documented enough.
BTW: I've the book too but even there is included a lot basic-knowhow in 
a compressed kind and many things are decribed very well, many other 
things are missing - especially the aspect how to extend or overwrite 
extbase/fluid-classes (the example for the viewHelper avoids a szenario 
where the URL or incoming parameters are changed and have to be parsed 
by the new extension).

As I didn't had a look to flow3 until now I don't know anything about 
the possibilities of the framework and perhaps some possibilites I'm 
requesting here are already included there but not in extbase/fluid.

I suppose beside the framework 'extbase/fluid' we need some more 
basically included viewHelper.

So, try and test a lot - perhaps you have good ideas for some missing 
features ;)

Greets,
David


More information about the TYPO3-project-typo3v4mvc mailing list