• PloneFormGen

Comparing

Current Version

by stevem, modified October 11, 2008
to

Version 18

by stevem, modified October 11, 2008

Key

  • inserted
  • deleted

PloneFormGen's internals are getting long-in-the-tooth, and need to be advanced to take advantage of Zope 3 and Plone 3 technologies.

Some early ideas for architectural work:

  • Switch the internal form representations to Z3 schema's maintained in the form object, rather than the field objects, with synchonization maintained by en event system;
  • Use z3c.form and plone.z3cform for presentation.

The combination of these would give PFG an efficiency of operation comparable to native formlib / z3.form fields. We may have an earlier sprint to work out the architectural details on this so that the DC sprint may be concretely productive. Let SteveM know if you're interested.

Other things that should happen during this refactoring:

  • Development of a mechanism for presenting forms in viewlets and portlets;
  • Developing a strategy for incorporating in-line validation;
  • Brainstorming on what a form editor AJAXified with KSS might look like (optilude thinks we may be able to share code with Dexterity);
  • Brainstorming form import/export.

We'd be able to use folks that know or would like to learn Z3 schemas and forms; anyone who can write tests; anybody that's got ideas for how PFG should meet the future; and anybody who'd like to develop docs. I'd particularly love anyone sufficiently dedicated to the long-run health of the project to help write migrations.

By the way, my bottom-line standard for this refactoring work is that we must have a very close to 100% reliable migration path from existing PFG, and the product must end up easier -- not harder -- for end users. If you'd like a new feature, try to come up with a plan for incorporating it that won't increase complexity.

Please sign up if you're interested!

Interested

Steve McMahon (stevem on #plone and OpenPlans, smcmahon on plone.org) - Release Manager

Andrew Burkhalter (andrewb on #plone and OpenPlans, andrewb on plone.org)

Alex Clark (aclark) - Cheer leading and coding, time-permitting :-)

Kelly Craig (kcraig) - Will be there, glad to help any way I can, have a few ideas to make it easier :)

Ed Crewe (edcrewe) - Should be there, coding if needed.

Jesse Snyder (jessesnyder) - Excited to contribute however I can!

Rob Gietema - I have some idea's and demo material for a form editor (can only be there on saterday morning tho :( )

Stéphan Geulette (sgeulette) - After a short sprint for plonegov the morning, I will be there to learn more about zope schemas and z3c.form.

Tasks

Task Name Owner/Interested? Bug/Feature Area
Projected Difficulty
New validator: Validate that a field contains no html, spam protection or no offsite links
Matt
Validation Architecture
Medium/Large
API call on FormFolder: all active/executable adapters
Form Folder API
Small
Copy/Paste of adapter leads to an event and the adapter is activated within the form
Bug Small
More overrides on some of the label fields, etc.
Feature Small
Better error messages for things like invalid email addresses Bug Small
Go to complete GS installation (think about and discuss Plone 2.x implications)
Feature Small
Link in folder contents view redirects directly to edit Usability ?
Default if no value entered for a field
Feature Small
Chain forms brainstorm (this is something Steve M mentioned during his talk)
Aleksi ?
Max length of certain form fields isn't long enough (for example custom success action)
Usability
Small
More efficient bulk editing interface using KSS (UI examples:http://wufoo.com/examples/)
Rob Usability Large
CSRF protection Bug Medium
Research z3c.form for rendering of form folder (why? this allows for including forms within viewlets/portlets throughout various sections of the site)
Ed, Stefan, Matt?
Feature Very Large
Put in place form folder portlet infrastructure (ultimately will depend upon the above ^^^)
Feature Large
GenericSetup export/import (wire PloneFormGen up to the content export/import setup handlers), allow for both bulk form export/import (i.e. entire site) and individual form export/import.
Andrew Feature Large
Anything to help with content creation (i.e. testing any online documentation, an adapter that helps) -- from Joel
Feature/Docs Medium Large, Small
Think more about beginner, advanced modes, any gains here -- from Joel
Usability Large
GenericSetup export import of PloneFormGen tool settings (i.e. permissions, etc.)
Feature Medium
Locking bug
Steve
id conflicts in fieldsets



Regular expression convenience method for validator overrides