Plone 4 and 5, plans and progress
by baekholt on May 20, 2009
- 9,341 views
My opening talk at the European Plone symposium in Sorrento, Italy, May 2009.
My opening talk at the European Plone symposium in Sorrento, Italy, May 2009.
About the plans and development of the Plone CMS in the near future (2009-10).
Geir Bækholt
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 12
- Downloads
- 116
- Comments
- 4
- Embed Views
- Views on SlideShare
- 7,280
- Total Views
- 9,341
1–4 of 4 previous next Post a comment
Stability often comes at the cost of innovation. We cannot do all that much fancy within the scope of Plone 3. That would break the promise.
So, as happy as we are with Plone 3 —time to get innovating again.
Planned a big release with massive changes in 2010
But as work progressed, it became evident that there was quite some release-worthy stuff that wouldn’t have to wait for such a major overhaul —and till 2010.
Not as radical as the work on Plone trunk
Will have new features, —but stuff that is stable now.
Features that are too big for a 3.x release. (i,.e require migration, compatibility changes, might break addons)
Not experimental
Hopefully a 2010 release as Plone 5.
Hanno will be release manager for Plone 5.
Kupu is no longer maintained.
The new editing UI for Plone trunk will also be based on TinyMCE.
Plone integration already.
You will still be able to use Kupu with Plone 4, of course. We’ll just switch the default.
Store binary objects outside the ZODB
On the filesystem
Tested. We have this running in a 7000 employee intranet.
faster
scalable
replaces Folder, ATFolder, Large folder etc
Makes it simple for product authors to define upgrade steps between versions.
Site admin vs Manager
Major source for confusion for newbies.
Deco is the front end editing interface
It also makes it easier for us to build more advanced menus, as we don’t have to take theming stuff into consideration.
Much simpler job for themers.
Since deco handles layout properly
no more need for “use content as default page”
…based on the typography and overall feel from Plone org.
Dexterity will be there for those that want to switch
And if you don’t need types, you’ll not have to relate to either.
Quite faster. Maintained,
Used by Repoze.BFG, Pylons, Plone
We have used this in a 7000-employee intranet we deployed last year. It works wonderfully. There is no way ZCatalog could have handled the load and the amount of content.
XDV is deliverance reimplemented as compiled XSLT. Currently has less features than deliverance, but has much better performance. Laurence’s goal is to have it compile down to a single XSTL transform that can be placed in the pipeline. No special software required to host it. Developed and used. Used on Plone.org.
plone.Grok directives for these common scenarios. No more need for zcml.
split more tools into configuration and functionality
There are currently no in-place migration to Plone trunk (like we have in previous Plone versions)