Rosetta Code:Wiki Wishlist: Difference between revisions

From Rosetta Code
Content added Content deleted
(my wishes, some responses)
(→‎[[User:Mwn3d|Mwn3d]]: talk and village pump)
Line 18: Line 18:
* 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
* 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 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. --[[User:Short Circuit|Short Circuit]] 21:46, 3 March 2008 (MST)
* I wish there were more stats available for use in the content of pages
* I wish there were more stats available for use in the content of pages
:* Number of uses for a template
:* Number of uses for a template

Revision as of 04:46, 4 March 2008

What do you wish Rosetta Code's wiki did?

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.)

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
  • 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.
  • I wish you had to preview an edit to make it

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) ).
  • Language expertise registry, like the userboxes on Literate Programs.
  • 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?)