Community
Participate
Working Groups
Provide more feeds that can be used for mashups. For example a feed for each UMA type.
We can use the controller app/controllers/rss_controller.rb to create those feeds. Currently a URL like http://epf.eclipse.org/rss/xp will produce a rss feed of changes in Wiki in xp We can change the list method in rss_controller to also support feeds like http://epf.eclipse.org/rss/xp/[uma_type] We also need to change routes.rb I think so that uma_type will be part of the path and not a parameter. We need that for page caching.
Created attachment 111713 [details] mylyn/context/zip Page.overview_table and PageTest.test_overview_table
Added method for getting overview table from page HTML, see Page.overview_table
Created attachment 112378 [details] Patch that includes feed support This patch includes support to generating feed for EPF Practices, as well as a more generic feed generation for any UMA type.
At this point, I assigned the bug to me as the assumption is that needs to be done so I commit the code I wrote to CVS.
Code has been added to CVS. I'm assuming this is the expected core functionality to solve the bug, as per the description says, so I'm marking it as resolved fixed. Tests are welcome. Since this hasn't been deployed into production yet, you can test the functionality by synchronizing with CVS and invoking the following URLs in your local install of the wiki: - http://myepfwiki/rss/[wiki folder]/practice/[practice_name] (replace [wiki folder] by the wiki name, and [practice_name] by the UMA name - or file name - of the practice) - http://myepfwiki/rss/[wiki folder]/[uma_type] (replace [wiki folder] by the wiki name, and [uma_type] by the name of the type you want to retrieve, i.e., role, task, guideline, concept, etc...)
Bug was resolved closed as per comment #6. However there are at least two considerations for further discussion: 1) Do we need UI support to this feed generation, to make easier for users, so they don't have to type the url as proposed in the resolution? It would be "nice to have" a tab on the Home page where you see all wiki sites listed, and for each wiki site a feed button for "practices" feed, and a feed button for "UMA types" feed. For practices, users would be presented with a combo box with available practices names. For UMA types, users would be presented with a combo box with available UMA types. 2) Mashup support might be a much larger thing than what we are providing as solution here. Certainly feeds are something we can provide to feed readers, mashup environments and such to consume, but saying that the wiki needs to provide Mashup support may be erroneously interpreted. We are not saying that the wiki has to become a Mashup environment itself, so we might change the name of this bug to be more generic, such as "Provide advanced feed generation capabilities" or similar. What are your thoughts on this?
There were 2 issues I found and just fixed. Committed to CVS: 1)There was a nil being returned when running the (individual) practice feed. Some elements do not have brief descriptions, and not only that, some elements do not even have overviewTable sections in their page. When that section was not found, a nil was being returned and an exception was raised. Solution: Fixed, by verifing if a nil is returned before processing the returned string. 2)Feeds on a wiki site based on RMC-published site did not return images for the channel and items. The <td> section attributes where the image source is located get published in different order when comparing an EPF vs. an RMC published site. EPF: <td width="50"><img src="./../../images/role.gif" alt="" title=""></td> RMC: <td width="50"><img title="" alt="" src="./../../images/role.gif"></td> Solution: Fixed the regular expression to find src in any location inside the img tag
According to observation 1) on comment #7, I provided a UI for the feed generation. It's based on a new page that can be accessed from link (Feeds) on the top nav bar on the home page, thus taking user to select wiki, element and practice name. I'll attach a patch first, do some more tests (please everyone test) and then commit to CVS for deployment to production to happen.
Created attachment 114279 [details] UI additions - patch Patch created according to comment #9
