Duncan Booth wrote:
No reason at all beyond the fact that I tend to put changes into the Plone
code first (where possible) and only consider backporting them when they
are stable. The code that does the conversions should be moved to somewhere
in the 'common' folder so that the other versions at least have the option
of using it. Part of the tidyup is Plone (in fact Plone+Archetypes)
specific, so that would have to be made optional somehow.
Besides the resolveuid stuff I couldn't find anything Plone+Archetypes
specific in makeLinksRelative.
The code for setting text styles (that works with tag and class) also needs
porting back into the common core. Any other suggestions for code which
should be common and isn't?
See http://codespeak.net/svn/kupu/trunk/kupu/plone/TODO.txt for a list of
things which might happen. Feedback on this list is most welcome.
What about merging plone's saveDataToField with the default prepareForm
method?
Cheers, Yuppie
