On Apr 12, 2006, at 12:01 PM, Matt Raible wrote:
It sounds good - but would we *have* to use it?  I'd like an option to
disable it and keep the current system.

I definitely do not want to force anybody to do both summary and content, but I would like to offer both summary and text fields on the weblog editor. You can choose to use one on or both. Plus, I'd like to keep the ability to "size" the fields -- so you could size the one you don't use smaller. (I'd rather do that than introduce more config. options).

Does that work for you?


This seems like it might lead
to shorter "summary" type RSS feeds, and I think those suck.  I want a
full feed or I'll unsubscribe. ;-)

The default behavior for Roller feeds is full-content and I am not proposing to change that. If you enter both a text/summary and content then *both* will appear in your feeds. That's the way Wordpress, Typepad and many MT installations do it, so feed readers know how to handle.

Here's how it will work in the feeds:

   For RSS
      text --> <description>
      summary --> <content:encoded>

   For Atom
      text --> <summary>
      content --> <content>


- Dave





Matt

On 4/12/06, David M Johnson <[EMAIL PROTECTED]> 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




Reply via email to