Implement Doctrine1 about legal HOT 6 CLOSED

Doctrine2 is available in core 1.3 and does not use namespaces. IMO, converting to doctrine1 is a waste of manpower.

from legal.

The plugin uses namespaces internally when it accesses the Doctrine2 code. Doctrine1 will be a no-brainer. Legal doesn't need much.

I might skip D1 altogether anyway, and just keep things in module variables for 2.x. With the 3-4 new document types that Axel added things are getting kind of too big to stay with module variables, but 2.x could probably suffer along a while longer with them.

from legal.

Internally, yes indeed. I hadn't thought of that. Still, converting to an abandoned tech seems a waste.

from legal.

Robert, the agreement for no namespacing was only for Zikula 1.3.0. From 1.3.1 we have introduced PHP 5.3 specific code as promised. There is no point implementing for Doctrine 1.

from legal.

I tend to agree with your comment regarding implementing an abandoned tech. The issue is in order to deal with the 'reset' issue I need to add a 'last updated date/time' field to each of the document types. Without D1 that means another 6 or so modvars. It really should have gotten converted to a db-driven module a while ago--at least when the new types were added.

I suppose we could just whack in the new modvars and deal with things in module version 3.0.0 when it is converted to 1.4. I suppose the only argument for going to D1 now is to allow users of core-1.3 to add more new document types.

What do others think? D1 now and allow more new types for 2.x/core-1.3, or forget it and implement the ability with D2 in 3.x/core-1.4?

from legal.

Re @Drak 's comment... well ok, then. Any further discussion regarding this (db-driven now or later) can happen over on issue #16.

from legal.