Rick Olson wrote:
>> These two approaches are not incompatible.  An active-record aware DSL
>> for feeds would make it easy to produce a full function and tailored
>> feed.  A set of conventions could make it even easier to get started for
>> tables that follow the conventions.
> 
> One issue I have is that my models usually store raw textile/markdown
> content.  I usually run a few filters like RedCloth, the auto_link
> helper, or the white_list plugin on my content before displaying them
> in a feed.  Though, I suppose one compromise is to include the modules
> into the model and do the processing in a callback.

I may have misunderstood or read too much into the use of :body in your 
example.  Taking a look at Mephisto, I see

  xm << %{<content type="html">#{sanitize_feed_content 
article.body_html}</content>}

Can you explain how :body was intended to work?

> I'm also discovering the importance of proper xml:base usage (or just
> converting relative links to absolute links):
> http://mephistoblog.com/assets/2006/9/26/SafariScreenSnapz003.png

That's another one of the areas that is grossly underspecified with RSS 
2.0.  If I read app/views/feed/_article.rxml correctly, the following 
would address the issue:

   xm.entry "xml:base" => site.permalink_for(article) do ...

- Sam Ruby

P.S.  Off topic for this mailing list, but I'm going to take a look at 
importing my weblog into Mephisto.  Be forewarned that I'm a tough 
customer to please.  I'm particularly unhappy about sites like 
mephistoblog.com that purport to be XHTML, but aren't even well formed 
XML as they contain strings like

   <a href="/tips">Tips & Tricks</a>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core
-~----------~----~----~----~------~----~------~--~---

Reply via email to