On 11-2-2013 18:00, David Given wrote:
It doesn't show up at all in Chrome. I went into my skin to add RSS
links to the <head> elements, and then discovered they were already there...
No, in Chrome you need an extension too, like I wrote earlier:
You can install the RSS Subscription Extension (by Google)
https://chrome.google.com/webstore/detail/rss-subscription-extensio/nlbjncdgjeocebhnmkbbbdekmmmcbfjd
(or at http://goo.gl/XeLSB for short)
Customising the <head> link will probably require some clever TH1
scripting to figure out what kind of page the user is looking at, and
then generate the appropriate RSS feed URL, since the header is common
for all pages.
Yes, well, figuring out what kind of page we're on is not all that
difficult; the default header already does that a lot (I don't really
know how easy it is to match the start of a string in TH1, though).
I was rather wondering how to get the ticket UUID for the current page...
Is it worth having more obvious links in the main body text for the
appropriate pages?
I should think so, since none of the major browsers show a feed icon by
default anymore (except Opera). But that's something that can already
be included in the customizable pages for editing and viewing tickets.
It might be nice to include them in the default templates, though.
What parts (if any) are still missing? i still can't believe nobody
proposed this feature a long time ago.
Hm. A feed for a specific ticket report activity? Unfortunately I have
no idea how to implement it.
Well, I was expecting the timeline.rss to accept the same (basic)
options as the timeline page, but I noticed that the ?y=e parameter (the
list of events) isn’t recognized, as yet.
I can't seem to make this work --- it just returns the same timeline
view (the same as y=all). I see some code but don't follow how it works.
Can you give me a sample URL?
http://fossil-scm.org/index.html/timeline?y=e
Seeing as this results in 4 entries, events aren't used very extensively
by the Fossil team themselves, it seems... :-)
But I can't figure out why the rss code doesn't isolate the events with
event.type='e', either.
Also: I notice that the RSS feeds link to the change description page
(e.g.
https://cowlark.com/calculon/info/75c4948da0fe0e5a970148e44870b4be3940922a).
This is useful from a technical perspective, but not necessarily user
friendly, at least for tickets, where linking directly to the ticket
itself would be more appropriate. Any thoughts on this?
That is true. I do like seeing what the specific changes were; it’s
just that from a UX viewpoint it would be nice to have a link to the
ticket itself feature more prominently; for example the ticket title
linking to the 'view ticket' page.
But that would require changing the 'info' page's output for ticket changes.
--
Martijn Coppoolse
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
