> 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'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 > > Now, I just need to write this because I really want it in Mephisto... > > I'm checking out Mephisto as I write this. :-) > > I'd be more than glad to flesh out an initial implementation for you to > critique, adapt, and/or adopt. That would be great. It would be nice to have a good library for this so I can feel confident my future projects output good feeds. > - Sam Ruby -- Rick Olson http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
