I’ve just come across this site, and the core developers of Plone should be forced to print it out and eat it – maybe then they would start listening to some of their users. Leaving the complexity issues aside for the moment, the single thing they need to do is to provide a consistent API between versions that doesn’t break applications already developed. They could then change the internals as much as they liked, and it wouldn’t matter.

I have made this suggestiopn to them on a couple of occassions, and it is as if I am talking a foreign language to them. Their reply is always along the lines that it would « restrict » adding new features/capabilities.

This is total bullshit – you are right, they just like coding for coding’s sake. Could you image how long Oracle would last if each new release broke every application built on top of it ?

I was attracted to Plone because of the capability of building the application model in a UML tool, then automatically generating the code, which I did for a music history project (www.franktraynors.au.com).

It is still running on Plone 2.5 as the very same UML model would not generate to Plone 3 using Joel Burtons public site. Some of the 3rd party applications also break on Plone 3, although I eventually have it all working on a test machine after wasting more time doing so than it took to get the original site functional.

I am dreading even thinking about getting it to run on Plone 4, as NONE of the 3rd party apps are available for Plone 3, due I suspect, to the reasons you give above.

Regards,