I am confused now. In your last comment about what the new field will
be you say "I've changed my mind: the new field should be summary, not
content." But you didn't really explain yourself.
So I am assuming that the new field will be summary (not required) and
the existing field is content (required). Permalinks always show just
the content field. Other pages show summary if it exists, otherwise
content?
Did I get that right?
Also, about the editors list. It is fine with me if you want to upgrade
the rest of the editors, but I think we need to make a stand here and
communicate the fact that the old editors are officially EOLed and are
not supported. Even if they have been upgraded they are still EOLed in
my mind and I don't think we (the dev team) should have to support such
a large list of editors, that is for users to do.
-- Allen
David M Johnson wrote:
Proposal (with some comments)
http://rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_Entry_Content
I believe I've addressed everybody's concerns on this.
I've got code just about ready to commit.
I also did some work to improve the RTE page: upgraded to latest RTE,
added sizing controls to both the summary and text fields, turned on
XHTML and switched to nicer looking icons.
If there are no objections I'll commit this to trunk this weekend.
- Dave
On Apr 12, 2006, at 10:30 AM, David M Johnson wrote:
I'd like to get this into a Roller 2.3 release this month, so please
review and offer feedback.
-Dave
Proposal Entry Content
Add support for both a summary text and full content property for each
Roller weblog entry
All major weblog systems and common newsfeed formats now support the
notion of a both short summary text and full content for each weblog
entry. Roller users have used the Read-More plugin to emuluate summary
and content, but creating a summary by automatically stripping HTML
from and truncating the content is not really an acceptable
alternative. This proposal adds support for a new content property on
the WeblogEntryData object to hold the full content of each blog
entry, supporting the Atom content model and using the conventional
mappings to RSS (i.e. text/summary goes to <description> and content
goes to <content:encoded>).
http://rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_Entry_Content
