[TYPO3-dev] Better use pibase while everyone use extbase?

[Popy]

Hi,

First of all, there are other alternatives than pibase / Extbase out there.
Many developpers came with their own library fitting their coding style.
Extabse success is strongly tied to the fact that it is entitled as "the
way to code extensions" in the official Typo3 communication.
Yet, while I agree on most things you said, don't forget that pibase is a
very very old legacy, which contains many misleading/stranges features,
while offering very few tools to develop a plugin.


Cordialement,
Pierre Dudoret

2014-10-05 15:57 GMT+02:00 Jigal van Hemert <jigal.van.hemert at typo3.org>:

> Hi,
>
> On 4-10-2014 14:15, Daniel Siepmann wrote:
>
>> why should I use extbase to develop extensions? Everyone says it's future
>> proof.
>>
>
> The answer: "it depends".
>
> PiBase requires more work from you as developer in areas of getting the
> data, displaying the data, preventing security issues and so on.
> If you need more freedom than extbase offers you pibase could be your
> weapon of choice.
>
> In extbase it's easy to find the records you need from the repository,
> pass them to the fluid template and take care of the display methods there
> with viewhelpers.
> In pibase you have to loop through the records in the PHP code and use
> TypoScript for extra display options. If you apply stdWrap to all data and
> have the possibility to define extra markers in TS the template designer
> has some degree of flexibility.
> In extbase it's easier to store information in the database. Updating the
> repository takes care of all the issues.
>
> Every system has its pros and cons. If the pros outweigh the cons for you,
> you found the system that suits you.
>
>
> --
> Jigal van Hemert
> TYPO3 CMS Active Contributor
>
>
> TYPO3 .... inspiring people to share!
> Get involved: typo3.org
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>