Recently, I wrote about integrating two different Zope 2 projects (both developed in-house) together. I finished that integration today - at least the primary functionality. Now I can start adding new features that actually take advantage of both systems, should the need arise.
As I was wrapping up today's work, appreciative of the component architecture stylings of each system, I started yearning again for Zope 3. Zope X3 3.0.0 is now released, but I fear it will be some time before I can start using it in earnest, given our current customer base and application state. Still, I thought, adapters and views would be nice technologies to have in each system, and especially in the bridge product.
And then tonight, I remembered Five, the Zope 3 in Zope 2 project. It's another interesting bridge project which allows use of some fundamental pieces of Zope 3's component architecture in Zope 2. Five is still a young project, but I hope to look into it soon. There are quite a few elements I've been implementing in half-form (or less) in recent projects that Zope 3 has and Five aims to bring to the Zope 2 world. This not only brings some nice tools to the Zope 2 developer, it should also start closing the gap between Zope 2 and Zope X3 by letting developers who choose to use it start migrating their applications and systems.