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
Deletions:
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


Revision [18731]

Edited on 2008-01-28 00:12:34 by MinusF [Modified links pointing to docs server]

No Differences

Revision [12614]

Edited on 2006-01-11 12:47:25 by MinusF [Modified links pointing to docs server]
Additions:
~~& the external feed service is not for human readable feeds, it's because of the statistics and such... --MinusF


Revision [12611]

Edited on 2006-01-11 07:48:52 by DarTar [reply to 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:
~& 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


Revision [12606]

Edited on 2006-01-11 07:21:33 by DarTar [reply to MinusF]
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


Revision [12605]

Edited on 2006-01-11 07:14:18 by DarTar [adding link and removing one point]
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.
Deletions:
~1) Add a link title to the page name, for instance: ""<a href="http://wikka.jsnx.com/UserAdmin" title="Go to UserAdmin">UserAdmin</a> "" (roll-over with your mouse to display the title);
~~&"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.


Revision [12602]

Edited on 2006-01-11 00:06:47 by MinusF [adding link and removing one point]
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...


Revision [12601]

Edited on 2006-01-10 23:54:18 by MinusF [adding link and removing one point]
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?)


Revision [11224]

Edited on 2005-09-30 12:40:47 by TroelsKnakNielsen [suggestion to arrow]
Additions:
~~&The arrow doesn't show up correctly on all platforms, depending on charset etc. Use → instead. -- TKN


Revision [8582]

Edited on 2005-05-28 11:46:31 by JavaWoman [move to subcategory]
Additions:
CategoryDevelopmentActions
Deletions:
CategoryDevelopment


Revision [7370]

Edited on 2005-04-18 11:20:01 by DarTar [typo]
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:
~1) Replace ""⇒"" with ""&lArr"": 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>""


Revision [7369]

Edited on 2005-04-18 11:15:40 by JavaWoman [comment about link titles]
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


Revision [7365]

Edited on 2005-04-18 11:11:25 by JavaWoman [comment about arrows]
Additions:
~~&Get rid of the arrow altogether and just write "by" - it's clearer and avoids rendering problems. --JW


Revision [7364]

Edited on 2005-04-18 11:09:13 by JavaWoman [my biggies about RecentChanges]
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


Revision [7348]

The oldest known version of this page was created on 2005-04-18 09:21:32 by DarTar [my biggies about RecentChanges]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki