You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having a look at what it would take to support Plone 5. I did a few changes in pull request #3 to ease this. Those changes are fine for earlier Plone versions as well.
Basic functionality already works without needing changes, except javascript. So that is good.
The controlpanel configlet is completely broken and Plone cannot even start without a few hacks.
I think the best way forward is to switch to using plone.app.registry instead of the portal_properties tool. Maybe we can then get rid of custom widgets code too.
Do you have any plans for porting to Plone 5?
What are your thoughts about compatibility? Is it fine if the master branch supports only Plone 5? 4.3 as well? More? Python 2.6 support still needed?
I have not tried making any add-ons compatible with Plone 5 yet. I guess supporting 4.3 plus 5.0 is reasonable for most add-ons. I am not sure if front-end changes are hard to keep working in 4 and 5 together.
The text was updated successfully, but these errors were encountered:
I am having a look at what it would take to support Plone 5. I did a few changes in pull request #3 to ease this. Those changes are fine for earlier Plone versions as well.
I have some notes for Plone 5 here: https://github.com/zestsoftware/quintagroup.seoptimizer/blob/zest-plone5/PLONE5-TODO.txt
Summary:
I think the best way forward is to switch to using plone.app.registry instead of the portal_properties tool. Maybe we can then get rid of custom widgets code too.
Do you have any plans for porting to Plone 5?
What are your thoughts about compatibility? Is it fine if the master branch supports only Plone 5? 4.3 as well? More? Python 2.6 support still needed?
I have not tried making any add-ons compatible with Plone 5 yet. I guess supporting 4.3 plus 5.0 is reasonable for most add-ons. I am not sure if front-end changes are hard to keep working in 4 and 5 together.
The text was updated successfully, but these errors were encountered: