RE: [Boa Constr] Zope Support

[Riaan B. <ri...@tb...>]

Hi Yuppie,

> 
> Hi!
> 
> 
> Is anybody currently working on the Zope Support? 
I do now and again when time permits.

> Did anybody try to write a CMF plug-in?

I have not used CMF in a project, so learning the whole framework 
plus wrapping the whole CMF framework will take too much time.

It's definitely one of those things I want but just don't have time for :(

From my investigations into this it looks like CMF objects can be wrapped 
just like all the other Zope objects currently supported.
 
> Does it make sense to write a CMF plug-in right now? I had a look at the 
> code and found todo comments like that in Editor.py:
> 
>      # XXX Unify with the rest of the explorers
>      def openOrGotoZopeDocument(self, zopeObj):
> 
>      # XXX Unify with the rest of the explorers
>      def openZopeDocument(self, zopeObj, wholename):
> 
> The Zope plug-ins are very different to the other plug-ins. Looks like a 
> unified plug-in interface would be very helpful for updating the 
> ZopeExplorer to Zope 2.6 or writing a CMF plug-in.

No. Those comments aren't that accurate anymore.
It has already been unified in the sense that 
Editor.openOrGotoModule('zope://Connection/<meta>/path/obj')
works correctly and that Zope items can be bookmarked.

Zope support as a transport plug-in will probably always remain 
different than other transports (e.g. ftp, ssh, etc) in the sense that 
different Zope uris can return different types of zope transports
while other transports only return a single type.

Nevermind the differences between Zope transports and the simple
transports, just use the current Zope support as examples,
they all follow basically the same model.

Please go ahead and implement CMF support! 
Even just a (working!) prototype would be great.

If I ever refactor the Zope support further, I promise to also update 
the CMF support if its there ;)

Cheers,
Riaan.