Hello, folks.
In conjunction with a current project I've written code that does the
following:
1. Adds an 'excerpt' field to a content type, which is basically used
like Description (in listings) but is rich-text. This field is
invisible on the edit screen.
2. Adds a button to kupu which can be used to mark a cutoff point in the
primary text field. (This appears as a graphical marker in wysiwyg
mode, and as <!--more--> in the HTML -- pretty much identical to
Wordpress' UI for this.)
3. Overrides the content type's setText mutator to grab everything from
before the cutoff marker and put it into the 'excerpt' field.
Is this something others would find useful? It seems to be a pretty
common pattern for blogs, and I've seen it requested a couple times
recently on IRC.
Being a relatively new Plone / product developer, I'm not quite sure
what the best way to proceed is, so I'd appreciate some advice.
Assuming this is something the community wants, I can see three possible
directions:
1. Try to get my code included in Plone and kupu. We need both the new
field to store things in on the Plone side, and the new button for
inserting the marker on the kupu side, so I'm not sure which would need
to happen first. Based on what I've seen, I think I would create
branches of the relevant products in svn, put them together into a
review bundle and then attach that to a new PLIP?
2. Turn my code into an add-on product. The thing that's stopping me
from doing this is that I would have to override some fairly large
chunks of kupu in a new skin layer, which seems like it could become a
maintenance nightmare as new versions of kupu are released.
3. Write a tutorial for plone.org explaining how to make the necessary
changes (which really aren't that involved).
Any thoughts on which approach would be best?
thanks,
David
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
