Hi Walter,

We already have the printerfriendly skin and the link at the bottom of any page for a printer friendly view so I don't think we need that.

I think if we are going to implement some kind of email this page to a friend feature, it should be implemented as a control that can be re-used across features or pages rather than implementing it inside the RSS feature itself.

If you want to try and make the rest of those improvements its fine with me. I would say go ahead and do it in the existing feature as I'm not opposed to any of those enhancements. When you are finished you can send me the changed files and I'll review it. If for any reason you end up with something I don't want to include back in the project, you can always clone it at that time to make your own feature and then revert the original.

One feature I would love to see in the RSS module or possible in a new different RSS feature would be the ability to have a feature where you could subscribe to a whole bunch of feeds and then selectively publish individual items from any of those feeds. So only the admin or editor would see all the subscribed feeds and the public side would show only posts approved by the editor.

Also would be good if we could support atom feeds in addition to RSS. I looked at this project a while back and it looks useful for managing all kinds of feeds.

http://www.codeplex.com/Argotic

I am swamped so I can't get to this stuff right now.

Best,

Joe

Sounds great Walter!

I would do the selective publishing feature last as that will (I would think) require adding database table(s).

All of the other options can be implemented as modulesettings using existing tables so I would get all those things done first and then we can integrate your work up to that point into svn, then after that proceed with the additional things if you're still motivated.

Best,

Joe 

Hi,

Those settings in the backend are only defaults and really you should not change those because they will be updated according to config files whenever you upgrade. That backend allows developers to manually install and configure features but we don't use that for included features because we also have an installation system that allows installing features by config files so you can just upload the feature and visit the setup page.

Each instance of feed manager gets its own settings, when you first add a feed manager to a page it gets the default settings. You can edit the settings for the feed manager instance by clicking the gear icon next to the title. There are no new fields when selective publishing is enabled. Add a feed for it to consume and with selective publishing enabled you can pick and choose which if any items in the feed to publish. With selective publishing disabled it just uses all of them. So its a way of filtering out posts when you don't want all the posts in a given feed. For example you could subscribe to a bunch of blogs and then just publish the best posts that you read. So I could for example aggregate a bunch of blogs and feeds about content management but selectively publish only the gems and filter out the noise thereby adding value to my feed about content management.

Hope it helps,

Joe