[TYPO3-50-general] just to argue a bit: What about Doctrine?

[Abraham Block]

In theory there's I can't imagine what's stopping you from using doctrine
(2.0 not 1.0). If I'm not mistaken, it might be as simple as implementing
the Repository interface to talk to doctrine EntityManager.
It certainly won't be a walk in the park like using the built in features,
but as long as the API of FLOW3 is using interfaces, anything is possible.

On Sat, Nov 7, 2009 at 6:35 AM, Fernando Arconada <falcifer2001 at yahoo.es>wrote:

> Hello
>
> TYPO3 it's a big project, FLOW3 looks really great as framework. But i'm
> a bit worried about reinventing the wheel. This days we could read that
> Zend Framework endorses Doctrine, of course Symfony do the same
> (Doctrine's author is working at Sensio)
> http://old.nabble.com/Discontinuing-Zend-Entity-in-favour-of-Doctrine-
> integration-td26117819.html
>
> I only want to know, Why the TYPO3/FLOW3 solution (of course i'm only
> talking about ORM) it is better than Doctrine?
> Why dont integrate Doctrine?
>
> Doctrine it's a big project, very well documented and spreaded in the
> open source comunity.
>
> Our babies are always the most beautiful and we are very proud of them.
> But really we are doing all better than other frameworks? are there
> something writen about this?
>
>
> Hope your answers
>
>
> Fernando Arconada
> _______________________________________________
> TYPO3-project-5_0-general mailing list
> TYPO3-project-5_0-general at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-5_0-general
>