Rosetta Code:Wiki Wishlist

From Rosetta Code
Revision as of 21:36, 18 March 2008 by rosettacode>Mwn3d (I fixed userboxes)

What do you wish Rosetta Code's wiki did?

Granted wishes

  • Language expertise registry, like the userboxes on Literate Programs. --IanOsgood 20:55, 5 March 2008 (MST)
I tried to make something like that based on things I saw on wikipedia. You can check it out and change it: Template:User. You can see it in use on my userpage. --Mwn3d 19:27, 5 March 2008 (MST)
  • I wish div boxes didn't mess up the edit links on a page.
Fixed for userboxes only. You need to put your userboxes in between {{usertop}} and {{userbottom}} now.

Short Circuit

  • I wish there was a quick way to pump out pages in LaTeX
  • I wish there was a way to go to a language page, click on a task link, and jump to that language for that task
  • I wish there was a clean (i.e. easily editable) way to share code between pages
  • I wish there was a way to display a cross-section of the Solutions by Language category and the Solutions by Task category
  • I wish C++ worked
  • I wish pages could include a list of "what links here", rather than have it as a link on the side
  • I wish C# worked
  • I wish it were possible to give libraries aliases. (i.e. GTK, Gtk, GTK+, Gtk+, Gtk2 and PyGTK are all pretty much the same.)
  • I wish there was a program to convert Vim syntax highlighting scripts into PHP files, so that we might have more robust syntax highlighting.

Mwn3d

  • I wish the Google search were built into the page and didn't log me out
  • I wish links weren't case-sensitive
  • I wish a category's links on pages would disappear when the category was deleted
  • I wish I could hit the tab key while adding code without the cursor moving to the summary box
  • I wish there were an easier way (or that people participated in existing easier ways) to debate about content on pages--talk pages get crowded quickly
  • The Wikipedia solution is to archive old conversations to talk archive pages. And there is always the Village Pump.
  • The Wikipedia's Village pump is simply a set of pages dedicated to talk, and so archived. I had to go with forum software because I didn't know how to set up a bot to do the archiving. It could be worth looking into again. --Short Circuit 21:46, 3 March 2008 (MST)
  • I wish there were more stats available for use in the content of pages
  • Number of uses for a template
Not like that. Short Circuit had asked a while ago on IRC for a way to count the number of times {{header}} was used so he could tell how many examples there were on the site. That page only shows how many pages use a template, instead of how many times a template is used. --Mwn3d 17:28, 4 March 2008 (MST)
  • User-specific stats like number of edits (with options to filter out talk edits and minor edits)
  • I've seen such things on Wikipedia. Also, total edits are listed on your preferences page.
This wish is low priority for me. I just thought it'd be cool to put the number of edits I had on my userpage. --Mwn3d 17:28, 4 March 2008 (MST)
  • I wish you had to preview an edit to make it
  • I wish div boxes didn't mess up the edit links on a page.
  • I wish the links in the Java syntax highlighting went to Java 1.5 (or higher) JavaDocs

Ce

  • I wish there were syntax highlighting for C++ (the C highlighting doesn't know C++ keywords)
  • What about <cpp>?
  • I wish the forum (village pump) and the wiki were integrated (especially, single login for both, but also the forum style sheet might be adapted to fit better to the wiki look)

Ian Osgood

  • More outreach to other programming language communities. Most languages haven't seen new examples for a year. Maybe via comp.lang.* postings, IRC, and programming language portals.
  • Category for starter tasks which should be easy for new contributors.
  • Way to see which tasks are not performed by a language (sort of an inverse category: (Solutions by Language) - (language category) ).
  • Merge or delete similar tasks.
  • Delete empty and singleton language implementation categories.
  • Help:Style Guide, demonstrating the preferred formatting for each Rosetta Code language. (Or would that be a declaration of Edit War?)
I think we would get a lot of unnecessary nerd fights about curly braces and whitespace. Maybe if RC invented a language we could make a standard. --Mwn3d 13:11, 8 March 2008 (MST)

SGeier

  • As somewhat more fine-grained tagging system would be cool. Say, tag all tasks that only make sense for OO languages so as to be able to look at only (or all but) those tasks. Or everything that has to do with GUI programming. Or file I/O. Ideally coupled with all the other functions, so I could have a "list of everything that Rosetta Code knows about doing file I/O in Ada" or such.
  • Definitely something like "list of all tasks for which there is no solution in language-X yet".Sgeier 18:20, 5 March 2008 (MST)