End of life warning?

[agitator]

as it looks PloneFormGen won't be updated for Plone 5.1 (correct me if I'm wrong)
and since our GSOC student is working on migrations to EasyForm, we should probably extend the version check with a warning/recommendation to use EasyForms?

[mauritsvanrees]

Where do you get the idea that it won't be updated? Are there changes in 5.1 that you think will be hard for PloneFormGen to adapt to?
Archetypes should continue to work just fine in Plone 5.x, so PloneFormGen should be okay too.
We are still using the old css/js approach, which should preferably be updated, but it still works.

[agitator]

with 5.1 a lot of the portalproperties are not there anymore
tried to update it locally but gave up since it didn't seem to end failing and moved to EasyForm

[keul]

I hope this will not be true. Right EasyForm is ages behind PFG features...

[agitator]

didn't want to offend anyone, just looking for a clear statement here ;-)

[keul]

I started thinking that @agitator was right about this.

This package has some open issues and (more alarming) few perfectly mergeable pull request waiting for approvation but I didn't see any activities recently.

This is a huge problem... I've at least two customer with custom PFG adapter who migrated to Plone 5 because PFG was working and supported.

What I need to do? IMHO collective.easyform is not mature enough (and migration from PFG is not something at low cost).

[smcmahon]

I haven't had a chance to work with PFG and 5.1 (still in alpha at the time of this writing) yet, but I'd be very surprised if there is something we can't fix. I expect we'll be able to keep it working so long as Plone has Archetypes support.

[frapell]

@smcmahon @mauritsvanrees Hey guys, is there talk somewhere on what is going to happen with PFG with Plone 5.2 ? Archetypes won't be ported to Python 3, and while Plone 5.2 should work both with 2.7 and 3, we are approaching the EOL for Archetypes...

Are there any plans on migrating the PFG content types to Dexterity?

Sorry if this has already been discussed somewhere else, if so, can you point me there?

[mauritsvanrees]

I don't know if discussion happened anywhere. I suppose PloneFormGen will work on Plone 5.2 with Python 2 without much trouble. Haven't tried it.
If we port PloneFormGen to Dexterity, then you would more or less end up with collective.easyform, which as far as I know is meant as a Dexterity-replacement for PloneFormGen. There is probably room for improvement in that package, but it seems more logical to improve easyform than to really port PloneFormGen itself.

[witekdev]

@smcmahon @mauritsvanrees Hey guys, is there talk somewhere on what is going to happen with PFG with Plone 5.2 ? Archetypes won't be ported to Python 3, and while Plone 5.2 should work both with 2.7 and 3, we are approaching the EOL for Archetypes...

Are there any plans on migrating the PFG content types to Dexterity?

Sorry if this has already been discussed somewhere else, if so, can you point me there?

Bump
I was wondering if there has been any consensus in the meantime as to the roadmap for PloneFormGen with Plone 5.2 or if people are moving on to https://github.com/collective/collective.easyform or something else? Thanks!

@smcmahon @frapell @mauritsvanrees

[mauritsvanrees]

I am not working on PFG on 5.2, and have no plans in that direction, but am willing to review pull requests.
I have seen several problems today in testing on 5.1, though they can be worked around.

For migration to easyform, Philip has written migration code.

[witekdev]

@mauritsvanrees thanks for the update!