Revision history for ImprovedRecentChanges
Revision [23070]
Last edited on 2016-05-20 07:38:45 by MinusF [Replaces old-style internal links with new pipe-split links.]Additions:
seems like [[http://www.feedicons.com/ | these]] icons will be the standard in the future.
the xml icon is nice but it's not clear that it is a feed. i have already [[http://obiit.org/orsorum/RecentChanges | replaced]] it (also please note that
~&It will be trivial to add custom menu items, including a feed icon, once WikkaMenus and WikkaMenulets are available with the [[WikkaSkinOptimization | new template]] -- DarTar
the xml icon is nice but it's not clear that it is a feed. i have already [[http://obiit.org/orsorum/RecentChanges | replaced]] it (also please note that
~&It will be trivial to add custom menu items, including a feed icon, once WikkaMenus and WikkaMenulets are available with the [[WikkaSkinOptimization | new template]] -- DarTar
Deletions:
the xml icon is nice but it's not clear that it is a feed. i have already [[http://obiit.org/orsorum/RecentChanges replaced]] it (also please note that
~&It will be trivial to add custom menu items, including a feed icon, once WikkaMenus and WikkaMenulets are available with the [[WikkaSkinOptimization new template]] -- DarTar
No Differences
Additions:
~~& the external feed service is not for human readable feeds, it's because of the statistics and such... --MinusF
Additions:
~& MinusF, I like very much the new icons, thanks for suggesting this (although I find the one on your site way too big). As for human readable feeds, instead of using an external service, a nice alternative is to provide styling through CSS (see [[RSSHandler]] for some first tests) -- DarTar
Deletions:
Additions:
~~~& See [[RSSHandler]] -- DarTar
~& MinusF, I like very much the new icons, thanks for suggesting this. As for human readable feeds, instead of using an external service, a nice alternative is to provide styling through CSS (see [[RSSHandler]] for some first tests) -- DarTar
~&It will be trivial to add custom menu items, including a feed icon, once WikkaMenus and WikkaMenulets are available with the [[WikkaSkinOptimization new template]] -- DarTar
~& MinusF, I like very much the new icons, thanks for suggesting this. As for human readable feeds, instead of using an external service, a nice alternative is to provide styling through CSS (see [[RSSHandler]] for some first tests) -- DarTar
~&It will be trivial to add custom menu items, including a feed icon, once WikkaMenus and WikkaMenulets are available with the [[WikkaSkinOptimization new template]] -- DarTar
Additions:
~~~&Agreed -- DarTar
~1) Make the author's name clickable if the corresponding page exists. (see FormatUserMethod) --- Since this might clutter up the page with a lot of links, I suggest we add a simple username check to the link parser and a special CSS class for userpages. The parser will check if a given link corresponds to an existing user page; if it does, the link is rendered with a ##class="user"## attribute. If it doesn't, raw text is displayed instead of a link. For instance: --- ""<span class="recentchanges"> (<a href="http://wikka.jsnx.com/UserAdmin/revisions" title="View recent revisions list for UserAdmin">08:45 UTC</a>) [<a href="http://wikka.jsnx.com/UserAdmin/history" title="View edit history of UserAdmin">history</a>] - <a href="http://wikka.jsnx.com/UserAdmin">UserAdmin</a> ⇐ <a href="http://wikka.jsnx.com/DarTar" style="text-decoration:none; border:1px black dotted;">DarTar</a> <span class="pagenote">[Updating links and changelog]</span>"" --- Such functionality makes sense also outside the scope of the RecentChanges action. It would be nice to mark links to internal user pages in a different, CSS-driven way. As a further extension, links corresponding to user pages could be given a specific tail (much as external links), for instance an icon or a some specific HTML code. See LinkTails for further discussions on this issue.
~1) Make the author's name clickable if the corresponding page exists. (see FormatUserMethod) --- Since this might clutter up the page with a lot of links, I suggest we add a simple username check to the link parser and a special CSS class for userpages. The parser will check if a given link corresponds to an existing user page; if it does, the link is rendered with a ##class="user"## attribute. If it doesn't, raw text is displayed instead of a link. For instance: --- ""<span class="recentchanges"> (<a href="http://wikka.jsnx.com/UserAdmin/revisions" title="View recent revisions list for UserAdmin">08:45 UTC</a>) [<a href="http://wikka.jsnx.com/UserAdmin/history" title="View edit history of UserAdmin">history</a>] - <a href="http://wikka.jsnx.com/UserAdmin">UserAdmin</a> ⇐ <a href="http://wikka.jsnx.com/DarTar" style="text-decoration:none; border:1px black dotted;">DarTar</a> <span class="pagenote">[Updating links and changelog]</span>"" --- Such functionality makes sense also outside the scope of the RecentChanges action. It would be nice to mark links to internal user pages in a different, CSS-driven way. As a further extension, links corresponding to user pages could be given a specific tail (much as external links), for instance an icon or a some specific HTML code. See LinkTails for further discussions on this issue.
Deletions:
~~&"go to ..." as a link title is totally redundant: that's what a link **is**. A title should provide //extra// information about the target (such as why you should go there, or what to expect there) - not available in this context, so just don't use a title --JW
~1) Make the author's name clickable if the corresponding page exists. --- Since this might clutter up the page with a lot of links, I suggest we add a simple username check to the link parser and a special CSS class for userpages. The parser will check if a given link corresponds to an existing user page; if it does, the link is rendered with a ##class="user"## attribute. If it doesn't, raw text is displayed instead of a link. For instance: --- ""<span class="recentchanges"> (<a href="http://wikka.jsnx.com/UserAdmin/revisions" title="View recent revisions list for UserAdmin">08:45 UTC</a>) [<a href="http://wikka.jsnx.com/UserAdmin/history" title="View edit history of UserAdmin">history</a>] - <a href="http://wikka.jsnx.com/UserAdmin">UserAdmin</a> ⇐ <a href="http://wikka.jsnx.com/DarTar" style="text-decoration:none; border:1px black dotted;">DarTar</a> <span class="pagenote">[Updating links and changelog]</span>"" --- Such functionality makes sense also outside the scope of the RecentChanges action. It would be nice to mark links to internal user pages in a different, CSS-driven way. As a further extension, links corresponding to user pages could be given a specific tail (much as external links), for instance an icon or a some specific HTML code. See LinkTails for further discussions on this issue.
Additions:
also i would like to add the feed icon (a small one 16x16 perhaps) to $navigation_links
and $logged_in_navigation_links but it's not trivial at the moment as far as i can tell...
and $logged_in_navigation_links but it's not trivial at the moment as far as i can tell...
Additions:
~~&make it configurable ;-) i like the double arrow very much. -- MinusF
====feed icons====
seems like [[http://www.feedicons.com/ these]] icons will be the standard in the future.
the xml icon is nice but it's not clear that it is a feed. i have already [[http://obiit.org/orsorum/RecentChanges replaced]] it (also please note that
it is a feddburner feed actually -- perhaps this could be also configurable?)
====feed icons====
seems like [[http://www.feedicons.com/ these]] icons will be the standard in the future.
the xml icon is nice but it's not clear that it is a feed. i have already [[http://obiit.org/orsorum/RecentChanges replaced]] it (also please note that
it is a feddburner feed actually -- perhaps this could be also configurable?)
Additions:
~~&The arrow doesn't show up correctly on all platforms, depending on charset etc. Use → instead. -- TKN
Additions:
CategoryDevelopmentActions
Deletions:
Additions:
~1) Replace ""⇒"" with ""⇐"": IMO it makes more sense to have the arrow point FROM the author TO the PAGE, for instance: --- ""<span class="recentchanges"> (<a href="http://wikka.jsnx.com/UserAdmin/revisions" title="View recent revisions list for UserAdmin">08:45 UTC</a>) [<a href="http://wikka.jsnx.com/UserAdmin/history" title="View edit history of UserAdmin">history</a>] - <a href="http://wikka.jsnx.com/UserAdmin">UserAdmin</a> ⇐ DarTar <span class="pagenote">[Updating links and changelog]</span>""
Deletions:
Additions:
~~&"go to ..." as a link title is totally redundant: that's what a link **is**. A title should provide //extra// information about the target (such as why you should go there, or what to expect there) - not available in this context, so just don't use a title --JW
Additions:
~~&Get rid of the arrow altogether and just write "by" - it's clearer and avoids rendering problems. --JW
Additions:
~&My four "biggies" about our current RecentChanges are all to do with **content** and its usability and usefulness:
~~1) Change the name "RecentChanges" to "RecentlyChanged" (both page and action!) - analogous to "RecentlyCommented" - because that's what it **is**. (Note that I have already created a "RecentComments" page, and have been able to do that since there is at least an action provided for both "views"; for "changes" this is not the case.)
~~1) Make a **real** RecentChanges action.
~~1) Make corresponding pages for //both// actions like we have now for comments.
~~1) Provide feeds (for both) in several modern formats: RSS 1.0, RSS 2.0, Atom.
~&(Side note: Corresponding feeds for comments would be useful, too.) --JavaWoman
~~1) Change the name "RecentChanges" to "RecentlyChanged" (both page and action!) - analogous to "RecentlyCommented" - because that's what it **is**. (Note that I have already created a "RecentComments" page, and have been able to do that since there is at least an action provided for both "views"; for "changes" this is not the case.)
~~1) Make a **real** RecentChanges action.
~~1) Make corresponding pages for //both// actions like we have now for comments.
~~1) Provide feeds (for both) in several modern formats: RSS 1.0, RSS 2.0, Atom.
~&(Side note: Corresponding feeds for comments would be useful, too.) --JavaWoman
