DHTML schemata branch being merged? CMFEditions use case.

I was just wondering what the plans are for merging the
mrtopf-dhtml-schematas branch into the base archetypes code.  I've seen a
few mentions in the mailing list about getting it merged, but no activity
has occurred in the branch for a while.

Our current use case is using Archetypes-based content types with
CMFEditions, which currently has no auto-versioning support for content
types with schematas (only the "Content" schemata ends up being
auto-versioned). We thought about was to modify CMFEditions,
such as implementing schemata support for CMFEditions (making all
schematas trigger auto-version maybe?), but then we would get a new
"edition" with each schemata save (so, for some of our content types, we
would get six new editions with one page edit). Needless to say, having
six verisions on a single page save is pretty sloppy. Having all schematas
save with a single "save" action would probably be the best way to solve
the problem.

Our content editors are also annoyed by the time it takes to "switch"
between schematas, and the ability to accidentially "switch" and not save.
 It seems like the DHTML schematas branch would solve those issues too.

Is the mrtopf-dhtml-schematas branch still slated for merging?  Has anyone
found any critical issues with that branch that would need addressing
prior to merge?  Is there any way I can help?

Matt Hahnfeld
[email protected]



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642