Rosetta Code:Village Pump/Features Wanted: Difference between revisions
→Rosetta Planet: xfeeds? |
→Rosetta Planet: Yes. |
||
Line 23: | Line 23: | ||
: This is implemented. I'm looking for volunteers who'd like (or, at least, wouldn't mind) their blogs aggregated. Preferably using a specific Atom/RSS feed for articles that would like to show up in the planet. --[[User:Short Circuit|Short Circuit]] 04:09, 4 August 2009 (UTC) |
: This is implemented. I'm looking for volunteers who'd like (or, at least, wouldn't mind) their blogs aggregated. Preferably using a specific Atom/RSS feed for articles that would like to show up in the planet. --[[User:Short Circuit|Short Circuit]] 04:09, 4 August 2009 (UTC) |
||
:Will you add it to the xfeeds on the main page eventually? --[[User:Mwn3d|Mwn3d]] 14:48, 4 August 2009 (UTC) |
:Will you add it to the xfeeds on the main page eventually? --[[User:Mwn3d|Mwn3d]] 14:48, 4 August 2009 (UTC) |
||
::Once I've got some more blogs in there. I'd rather my gripes about the C++ standard license be a little farther down the list. :) --[[User:Short Circuit|Short Circuit]] 01:29, 5 August 2009 (UTC) |
|||
==Per-language news feed aggregation== |
==Per-language news feed aggregation== |
Revision as of 01:29, 5 August 2009
A place to put the features we want. Please keep each feature in its own section. Some of these may be doable by bot. Others may be doable by writing MediaWiki extensions to fill additional namespaces.
Logically Separate Code Samples
The absolute biggest thing I would like would be able to do something akin to "SELECT code FROM table WHERE (some expression tying language, library, paradigm, family, or a version of which.)". The best way I can think of to do this is to make each code sample a separate piece of information, associated with a set of tags. --Short Circuit 02:52, 10 July 2009 (UTC)
- I'm not convinced that that's a good idea. Sometimes a language solves a problem in a more discursive style (i.e., interleaved text and code) that makes doing that sort of thing much more awkward. Cut-n-paste works... —Donal Fellows 10:05, 4 August 2009 (UTC)
On-server, on-domain language documentation
I'd like to be able to link to documentation on-domain where such documentation is retrievable progrommatically and legally. With, e.g. the output of perldoc -f, or kernel syscalls, etc formatted for display on-site and associated with related content on the site. --Short Circuit 02:52, 10 July 2009 (UTC)
Keyword indexing
"See other code samples that use this keyword" --Short Circuit 02:52, 10 July 2009 (UTC)
Per-language RSS or twitter feeds
Whenever a task gets added, twitter it in the "new tasks" feed. Whenever a language gets added, twitter it in the "new languages" feed. Whever a new task is solved in a language, twitter it in that language's feed. --Short Circuit 02:52, 10 July 2009 (UTC)
Rosetta Planet
I'd like to be able to pull in blogs from members of the Rosetta Code community that relate to Rosetta Code and to programming. --Short Circuit 02:52, 10 July 2009 (UTC)
- This is implemented. I'm looking for volunteers who'd like (or, at least, wouldn't mind) their blogs aggregated. Preferably using a specific Atom/RSS feed for articles that would like to show up in the planet. --Short Circuit 04:09, 4 August 2009 (UTC)
- Will you add it to the xfeeds on the main page eventually? --Mwn3d 14:48, 4 August 2009 (UTC)
- Once I've got some more blogs in there. I'd rather my gripes about the C++ standard license be a little farther down the list. :) --Short Circuit 01:29, 5 August 2009 (UTC)
Per-language news feed aggregation
I'd like each language page to be able to display RSS feeds related to that language. --Short Circuit 02:52, 10 July 2009 (UTC)
Better commenting system
I hate to say it, but the MediaWiki page editing format is horrible for maintaining threaded conversations. I'd love to have something that could integrate IRC, talk/VP pages, email and even NNTP. --Short Circuit 02:52, 10 July 2009 (UTC)
Better data export
I'd love to have cached copies of MediaWiki data available for quick export, even if the cache is only updated daily or weekly. --Short Circuit 02:52, 10 July 2009 (UTC)
Semantic Pages
I'd love for pages served up by the wiki side of things to be semantically arranged, to simplify programmatic access and client-side acceleration of their use. --Short Circuit 02:52, 10 July 2009 (UTC)
More powerful theme
I would like a wiki theme that is more aware of Rosetta Code's structure, such as prominent display of the categories a page is in, and in-page exploration of related categories without changing the current page. --Short Circuit 02:52, 10 July 2009 (UTC)
- How about custom "Add an example" and "Add a language" GUIs? They would make some of these other features easier (for example, tagging examples with libraries, languages, and versions), and they would allow for more uniformity across pages (alphabetization and standard lang tags, works with, and libheaders). I don't know how hard that would be to make though. Watch out for SQL injection ;). --Mwn3d 20:39, 13 July 2009 (UTC)
Mobile theme
I would like a stripped down version of the wiki interface for mobile environments. --Short Circuit 02:52, 10 July 2009 (UTC)
Non-Web Interface
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. --Short Circuit 02:52, 10 July 2009 (UTC)