[TYPO3-dev] AbstractPlugin vs ActionController

[Crico Guillaume]

Hi,

It depends mostly on the purpose of your plugin, and if you want to use 
the Extbase features.

ActionController is part of Extbase, and you will have to follow the 
"Extbase way".
This gives you a lot of builtin features (injection of Domain/Model, 
View) but be careful : you have to stick on a lot of conventions (which 
are not so well documented), it is slow (in my opinion), and the Extbase 
API is not very stable (watch Extbase changelog).

The AbtractPlugin on the other way is quite stable, and is great if all 
you want is an "entry point" for your plugin, with few utilities (mostly 
the link related methods). But then you are on your own! The 
AbtractPlugin is the best solution if you have no use of the Extbase 
Domain/Model.

Regards,
Guillaume Crico


Le 07/01/2016 03:55, NGUYEN Duc Quan a écrit :
> Hi,
>
> I am beginning to create extensions and plugins recently. While 
> reading docs, forum threads, tutorials and code I stumbled over the 
> classes AbtractPlugin and ActionController.
>
> I did some searching about the differences and why/when to use which 
> one. I couldn't get a clear answer so I was wondering if someone could 
> give me more informations about the differences.
>
> I am assuming that abstractplugin is for creating frontend plugins 
> rendered with css_styled_content and actioncontroller is a more 
> general way to compute content which should be outputted by a plugin?
>
> Thanks for your help!
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev