PHP

Over at jswiki you can see what physics libraries, game engines, webgl abstractions, and audio shims are available: http://goo.gl/cSmLC ^pi

Chromium and Google Chrome (version 4 and higher) have built-in support for Greasemonkey-style user scripts.

To use, click on any .user.js file. You should see an install dialog. Press OK to install.

Known issues:
Chromium does not support @require, @resource, unsafeWindow, GM_registerMenuCommand, GM_setValue, or GM_getValue.
GM_xmlhttpRequest is same-origin only.

Match Patterns

The preferred way to specify the pages that a user script should run against in Chromium is the @match attribute. Here are some examples of its use:

// ==UserScript==
// @match http://*
// @match http://*.google.com/*
// @match http://www.google.com/*
// ==/UserScript==

See these comments for details on the @match syntax. 

Support for Greasemonkey-style @include patterns is also implemented for compatibility, but @match is preferred.

With Greasemonkey-style @include rules, it is not possible for Chrome to know for certain the domains a script will run on (because google.* can also run on google.evil.com). Because of this, Chrome just tells users that these scripts will run on all domains, which is sometimes scarier than necessary. With @match, Chrome will tell users the correct set of domains a user script will run on.

The Text_Wiki package allows you to transform text structured using Wiki rules into any defined target output format, such as XHTML, RTF, LaTeX, and so on.> Note: The current release only supports XHTML and plain-text output. RTF, LaTeX, DocBook, and so on will be added as the codebase stabilizes and matures.Text_Wiki achieves this level of flexibility by using one class for each part of the transformation process:

*
one class for parsing each markup rule (e.g., bold, code, wikilink, etc)
*
one class for rendering each general format (e.g., XHTML, DocBook, RTC, etc)
*
one class for rendering each rule in each formatText_Wiki comes with its own set of markup rules (see the ]]), but you can write any rules you like to match whatever style you're used to. Text_Wiki draws its default rules from a number of codebases, most notably WikkiTikkiTavi and coWiki; while no code has been directly copied from those codebases, they were indispensible in learning how to process Wiki text.