Rosetta Code:Village Pump/Features Wanted: Difference between revisions
Rosetta Code:Village Pump/Features Wanted (view source)
Revision as of 21:24, 8 October 2009
, 14 years ago→Non-Web Interface: reasons
(→Non-Web Interface: reasons) |
|||
Line 61:
I would like for there to be an interface for interacting with Rosetta Code that doesn't depend on having a web browser. A console-based interface using ncurses would be slick, or even a standalone XUL-based app. --[[User:Short Circuit|Short Circuit]] 02:52, 10 July 2009 (UTC)
::This may be a stupid question, since I don't understand the goal you're trying to achieve with that; but what part of this request is NOT served by Lynx running in a console? [[User:Sgeier|Sgeier]] 18:15, 8 October 2009 (UTC)
:::: An interesting question. Probably the biggest reason is due to some of the limitations of HTML web design; There are three sets of important links on each page, and each set of links winds up amassed prior to the page body. Browsers like w3m work slightly better, but are still clunky for navigating pages. Having function keys or other keyboard shortcuts corresponding to those menus and common page editing behaviors would improve my workflow on MW sites.
::::
:::: There are other features that would come in handy as an editor, such as an abbreviated list of of recent changes in-page, quick assess to a listing of category membership and intrawiki, interwiki and outbound links. Those aren't part of the default data that gets served up with a wiki page.
::::
:::: I'm loathe to implement such things via JavaScript as part of the theme. I've been down the theme modification path with the Rosetta theme, and theme modifications make MW upgrades ''very'' painful. I've even brought the subject up in ##mediawiki, and was told that you're not supposed to modify those themes. Then there are the reactions one gets from using a client-side language as part of a web page. --[[User:Short Circuit|Michael Mol]] 21:24, 8 October 2009 (UTC)
==Powerful Search==
| |||