[TYPO3-ect] Party Information Framework: Please vote!

[David Toshack]

>>> B) Start with 4.1 on our own
>>> We might start right away with the design and development of the Party
>>> Information Framework, based on 4.1. If the commercial project starts
>>> anyway, Robert may or may not decide to cooperate with us, but we will
>>> not focus on that possibility.

-- snip --

> I think that it's possible to create a solution which keeps 5.0 in mind
> but already runs with 4.x. It's more a question of layering and
> abstraction. Of course we don't know yet how a business layer in 5.0
> looks like or how templating will work but as long as we keep the layers
> below clean and don't open lots of inter-dependencies with other parts
> of TYPO3, it will be fairly easy to create a 5.0 version later on.
> 
> In fact I think that inter-dependencies is the most important part of it
> - make sure that you don't rely on the framework (4.x) if not really
> neccessary and if you do, try to implement it in a way that dependencies
> can be configured (eg. passed in a constructor or by setting a property).
> 
> So my vote (if I have any): Go for B and try to work as clean as
> possible - then you're always on the safe side.
> 
> Cheers,
> robert

+1 for (B). And +1 for keeping 5.0 in mind with layering and
abstraction. IMHO a good basis would be the up and coming lib/div
extension. Functionality for object relations are currently being
discussed[1] and should hopefully combat 4.x/5.0 framework
incompatibility through the use of inter-dependencies.

I haven't delved into the code of the new IRRE features of 4.1 but I
would assume it will be related to what is being discussed in the
footnote[1].


Cheers,
David

[1]
http://lists.netfielders.de/pipermail/typo3-team-extension-coordination/2007-January/001209.html