[plumi-discuss] plone3-plumi buildout

[andy nicholson]

plone3-plumi buildout
http://plumi.org/browser/plumi-buildout-plone3/trunk

This is in a completely non-functioning state from svn atm. I have more
work to check into svn on this, but its all hacks , in this phase,
trying to figure out a nice way to move across to a buildout based
distribution, and at the same time, not breaking backwards compatibility
etc. We could just say 0.2-final is the last in non-buildout format ,
for example.

There is a new instance,on the engagemedia.org server, running plone3
+plumi, with not much functionality working, and probably outright bugs

/opt/instances/plumi-buildout-plone3
runs on 8580 when on.

The code that lives in 
/opt/instances/plumi-buildout-plone3/products/plumi-plone3-compat
is the plumi-plone3 compatibility work. Ive not committed the latest
work for this stage into SVN yet , nor figured out what exactly to do in
terms of these changes to our products themselves.

The good news is that all the changes necessary have been reduced to
just our code ATMediaFile/ATVideo/PlumiSkin - so thats nice. There are
new plone3 versions of all the dependencies. 

I put that aside for the moment on the day, and continued to try a
migration of an existing plumi-0.2 zodb - I was in the middle of getting
the first migration step working, but having no success.
The instance on the redfern above, has a copy of demo.plumi.org's zodb.

I needed to hack on the plone.app.blob code itself to get our
ATEngageVideo objects even recognised as needing migration to the new
zodb blob storarge engine. 
The 'correct' way is to now write our own migration code.

http://plumi.org/browser/plumi-buildout-plone3/trunk/MIGRATING


> Also how far along did you get with plone 3? Were you doing it using  
> ATvideo or with p4a-vid?


I have i mind that the trunk of the buildout project evolves like:

Plone 3 compatible products brought in.

Migration from ATEngageVideo/ExternalStorage to
ATEngageVideo/plone.app.blob storage working

Migration from ATEngageVideo/p.a.b to p4avideo "subtype" enhanced ATFile
object/p.a.b working

        p4a apparently works just with ATFile objects that marked with a
"marker interface" to change "types" (subtyping)
        So we can use 'schemaextendeder' project to come up with a
content
object mimicking ATEngageVideo (to hold our customised schema).
        We then actually migrate to this new schema-extended content
object
based on ATFile, and then can mark the object with the 'marker
interfaces' from p4a.

Template work to integrate PlumiSkin , and the views now available from
p4avideo

New products from p4a integration.

New plone3 third party products integration


-- 
Andy Nicholson

+44 774 733 4891 [ .uk ]

+61 406 306 715 [ .au ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.plumi.org/pipermail/discuss/attachments/20080325/d13e1510/attachment.pgp