Plugin Directory

Changeset 487165


Ignore:
Timestamp:
01/09/2012 08:51:42 PM (14 years ago)
Author:
tombenner
Message:

Adding links to readme references to "examples"

Location:
wp-coffeescript
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • wp-coffeescript/tags/1.0/README.md

    r487155 r487165  
    88WP CoffeeScript is a WordPress plugin that makes enqueueing [CoffeeScript](http://coffeescript.org) as easy as enqueueing JavaScript.  Instead of using [`wp_enqueue_script()`](http://codex.wordpress.org/Function_Reference/wp_enqueue_script), as you would for JS, you just use `enqueue_coffeescript()`, which takes almost exactly the same arguments.  The only difference is that the second argument should be the file path instead of the URL.  If you'd like to compile multiple CS files into a single JS file, you can use an array of file paths as the second argument.
    99
    10 Please note that the [CoffeeScript executable](http://coffeescript.org/#installation) must be installed on the server.  You can also set a custom path to the executable (see the examples).
     10Please note that the [CoffeeScript executable](http://coffeescript.org/#installation) must be installed on the server.  You can also set a custom path to the executable (see the [examples](https://github.com/tombenner/wp-coffeescript)).
    1111
    1212If you'd like to grab development releases, see what new features are being added, or browse the source code please visit the [GitHub repo](http://github.com/tombenner/wp-coffeescript)
     
    17171. Put `wp-coffeescript` into the `wp-content/plugins` directory
    18181. Activate the plugin through the 'Plugins' menu in WordPress
    19 1. Make sure that the [CoffeeScript executable](http://coffeescript.org/#installation) is installed on the server or set a custom path to the executable (see the examples)
     191. Make sure that the [CoffeeScript executable](http://coffeescript.org/#installation) is installed on the server or set a custom path to the executable (see the [examples](https://github.com/tombenner/wp-coffeescript))
    2020
    2121Examples
  • wp-coffeescript/tags/1.0/readme.txt

    r487155 r487165  
    1212WP CoffeeScript is a WordPress plugin that makes enqueueing [CoffeeScript](http://coffeescript.org) as easy as enqueueing JavaScript.  Instead of using [`wp_enqueue_script()`](http://codex.wordpress.org/Function_Reference/wp_enqueue_script), as you would for JS, you just use `enqueue_coffeescript()`, which takes almost exactly the same arguments.  The only difference is that the second argument should be the file path instead of the URL.  If you'd like to compile multiple CS files into a single JS file, you can use an array of file paths as the second argument.
    1313
    14 Please note that the [CoffeeScript executable](http://coffeescript.org/#installation) must be installed on the server.  You can also set a custom path to the executable (see the examples).
     14Please note that the [CoffeeScript executable](http://coffeescript.org/#installation) must be installed on the server.  You can also set a custom path to the executable (see the [examples](https://github.com/tombenner/wp-coffeescript)).
    1515
    1616If you'd like to grab development releases, see what new features are being added, or browse the source code please visit the [GitHub repo](http://github.com/tombenner/wp-coffeescript).
     
    20201. Put `wp-coffeescript` into the `wp-content/plugins` directory
    21211. Activate the plugin through the 'Plugins' menu in WordPress
    22 1. Make sure that the [CoffeeScript executable](http://coffeescript.org/#installation) is installed on the server or set a custom path to the executable (see the examples)
     221. Make sure that the [CoffeeScript executable](http://coffeescript.org/#installation) is installed on the server or set a custom path to the executable (see the [examples](https://github.com/tombenner/wp-coffeescript))
    2323
    2424== Frequently Asked Questions ==
  • wp-coffeescript/trunk/README.md

    r487155 r487165  
    88WP CoffeeScript is a WordPress plugin that makes enqueueing [CoffeeScript](http://coffeescript.org) as easy as enqueueing JavaScript.  Instead of using [`wp_enqueue_script()`](http://codex.wordpress.org/Function_Reference/wp_enqueue_script), as you would for JS, you just use `enqueue_coffeescript()`, which takes almost exactly the same arguments.  The only difference is that the second argument should be the file path instead of the URL.  If you'd like to compile multiple CS files into a single JS file, you can use an array of file paths as the second argument.
    99
    10 Please note that the [CoffeeScript executable](http://coffeescript.org/#installation) must be installed on the server.  You can also set a custom path to the executable (see the examples).
     10Please note that the [CoffeeScript executable](http://coffeescript.org/#installation) must be installed on the server.  You can also set a custom path to the executable (see the [examples](https://github.com/tombenner/wp-coffeescript)).
    1111
    1212If you'd like to grab development releases, see what new features are being added, or browse the source code please visit the [GitHub repo](http://github.com/tombenner/wp-coffeescript)
     
    17171. Put `wp-coffeescript` into the `wp-content/plugins` directory
    18181. Activate the plugin through the 'Plugins' menu in WordPress
    19 1. Make sure that the [CoffeeScript executable](http://coffeescript.org/#installation) is installed on the server or set a custom path to the executable (see the examples)
     191. Make sure that the [CoffeeScript executable](http://coffeescript.org/#installation) is installed on the server or set a custom path to the executable (see the [examples](https://github.com/tombenner/wp-coffeescript))
    2020
    2121Examples
  • wp-coffeescript/trunk/readme.txt

    r487155 r487165  
    1212WP CoffeeScript is a WordPress plugin that makes enqueueing [CoffeeScript](http://coffeescript.org) as easy as enqueueing JavaScript.  Instead of using [`wp_enqueue_script()`](http://codex.wordpress.org/Function_Reference/wp_enqueue_script), as you would for JS, you just use `enqueue_coffeescript()`, which takes almost exactly the same arguments.  The only difference is that the second argument should be the file path instead of the URL.  If you'd like to compile multiple CS files into a single JS file, you can use an array of file paths as the second argument.
    1313
    14 Please note that the [CoffeeScript executable](http://coffeescript.org/#installation) must be installed on the server.  You can also set a custom path to the executable (see the examples).
     14Please note that the [CoffeeScript executable](http://coffeescript.org/#installation) must be installed on the server.  You can also set a custom path to the executable (see the [examples](https://github.com/tombenner/wp-coffeescript)).
    1515
    1616If you'd like to grab development releases, see what new features are being added, or browse the source code please visit the [GitHub repo](http://github.com/tombenner/wp-coffeescript).
     
    20201. Put `wp-coffeescript` into the `wp-content/plugins` directory
    21211. Activate the plugin through the 'Plugins' menu in WordPress
    22 1. Make sure that the [CoffeeScript executable](http://coffeescript.org/#installation) is installed on the server or set a custom path to the executable (see the examples)
     221. Make sure that the [CoffeeScript executable](http://coffeescript.org/#installation) is installed on the server or set a custom path to the executable (see the [examples](https://github.com/tombenner/wp-coffeescript))
    2323
    2424== Frequently Asked Questions ==
Note: See TracChangeset for help on using the changeset viewer.