Rosetta Code:Village Pump/Javascript Functionality Add: Difference between revisions

From Rosetta Code
Content added Content deleted
(Competition announcement.)
 
(Add vptopic template.)
Line 1: Line 1:
{{Vptopic
I'd like to announce a competition that's been brewing in my head for a few weeks: The JavaScript Functionality Add
|topic=Javascript Functionality Add

|summary=Discussion of adding functionality to RC using JavaScript.
'''The Goals'''
}}
==Overview==
===The Goals===
# Come up with the most useful feature additions you can think of for Rosetta Code.
# Come up with the most useful feature additions you can think of for Rosetta Code.
# Implement them in JavaScript such that they work with IE7+ and Firefox 3.5+. (Broader support is awesome, but not strictly necessary.)
# Implement them in JavaScript such that they work with IE7+ and Firefox 3.5+. (Broader support is awesome, but not strictly necessary.)
Line 8: Line 11:
The most useful and stable features will be added to the site-wide JavaScript load.
The most useful and stable features will be added to the site-wide JavaScript load.


'''To consider'''
===To consider===
# Take a good look at the CSS involved and surrounding code examples; Ages ago, I added CSS classes that the site highlighting doesn't use, with the intent of enabling programmatic awareness.
# Take a good look at the CSS involved and surrounding code examples; Ages ago, I added CSS classes that the site highlighting doesn't use, with the intent of enabling programmatic awareness.
# For the moment, consider any exposed functionality and structured formatting on the site fair game; I don't know that any of it will be removed in the foreseeable future.
# For the moment, consider any exposed functionality and structured formatting on the site fair game; I don't know that any of it will be removed in the foreseeable future.
Line 17: Line 20:
# If you're hampered by problems with the way the site content exists, this would be a good time to identify specific limitations and fix them where possible.
# If you're hampered by problems with the way the site content exists, this would be a good time to identify specific limitations and fix them where possible.


'''Prize'''
===Prize===
# Inclusion to sitewide JS load, for whatever that's worth.
# Inclusion to sitewide JS load, for whatever that's worth.
# My appreciation, for whatever that's worth.
# My appreciation, for whatever that's worth.

Revision as of 20:33, 17 November 2010

Javascript Functionality Add
This is a particular discussion thread among many which consider Rosetta Code.

Summary

Discussion of adding functionality to RC using JavaScript.

Discussion

Overview

The Goals

  1. Come up with the most useful feature additions you can think of for Rosetta Code.
  2. Implement them in JavaScript such that they work with IE7+ and Firefox 3.5+. (Broader support is awesome, but not strictly necessary.)
  3. The features shouldn't be necessary for use of the site.

The most useful and stable features will be added to the site-wide JavaScript load.

To consider

  1. Take a good look at the CSS involved and surrounding code examples; Ages ago, I added CSS classes that the site highlighting doesn't use, with the intent of enabling programmatic awareness.
  2. For the moment, consider any exposed functionality and structured formatting on the site fair game; I don't know that any of it will be removed in the foreseeable future.
  3. Don't forget about the MediaWiki API.
  4. If you'd like some changes server-side, mention it. If it can be done within reasonable resource requirements (server and my own time), and isn't a major problem in some other respect, I might do it.
  5. If you've got ideas for features that could be implemented in JavaScript, but don't have the ability or urge to implement it, mention it; perhaps someone else will pick it up.
  6. If you're limited by testing resources, mention it; perhaps someone with another browser will lend a hand.
  7. If you're hampered by problems with the way the site content exists, this would be a good time to identify specific limitations and fix them where possible.

Prize

  1. Inclusion to sitewide JS load, for whatever that's worth.
  2. My appreciation, for whatever that's worth.
  3. Maybe, just maybe, I'll be able to send a specialized T-shirt, mug, greeting card or some such. It depends on how many people I'd have to send to.
  4. What do you need prizes for? I thought you guys all coded because you enjoyed it! --Michael Mol 14:01, 19 May 2010 (UTC)