| Both sides previous revision Previous revision Next revision | Previous revision |
| wordpress [2017/05/18 16:43] – Sectioning for easier edition. Replaced HTML table with DokuWiki table Toni Corvera | wordpress [2017/05/19 01:27] (current) – Finishing touches Toni Corvera |
|---|
| ====== WordPress Plugins from OutlyerNet ====== | ====== WordPress Plugins from OutlyerNet ====== |
| |
| <alert type="warning" icon="fa fa-warning">Most of these plugins are unmaintained since I have little use for them.</alert> | |
| |
| <callout type="warning" title="Caveat emptor" icon="true"> | <callout type="warning" title="Caveat emptor" icon="true"> |
| If you know that's the case, please contact me :). | If you know that's the case, please contact me :). |
| |
| I can't say for sure either if I'm inadvertently breaking something or punching security holes into <abbr title="WordPress">WP</abbr> although I can't see any such problems in the code I'm publishing. | I can't say for sure either if I'm inadvertently breaking something or punching security holes into WordPress although I can't see any such problems in the code I'm publishing. |
| </callout> | </callout> |
| |
| </callout> | </callout> |
| |
| ===== Interlinks+ ===== | ===== Relative URLs ===== |
| |
| <callout type="success" icon="true" title="No longer needed">This plugin was integrated back into the main [[//wordpress.org/extend/plugins/interlinks/|Interlinks]] so it is deprecated.</callout> | <callout type="success" icon="true">This plugin works correctly with current versions of WordPress as of 2017.</callout> |
| |
| <p><a href="files/kd-o-interlinks.php">Download v1.0a+</a> (last update october 13th 2007)</p> | [[/files/wordpress/net_outlyer_wp-relativeurls.php|Download v1.5]] (last update october 14th 2007). |
| |
| Interlinks+ is based on [[http://www.harleyquine.com/php-scripts/interlinks/|Interlinks]] by Harley. The original adds a very nifty feature: it enables wiki-style interlinks (e.g. <html><code>[[Some article]]</code></html> will be converted to a link to the post/page titled <html><var>"Some article"</var></html>). | Relative URL<nowiki>s</nowiki> is mainly targeted at people with a **local copy** of their WordPress site and those that **reorganise and/or change their pages hierarchy often** although many standard installations can also take advantage of it. |
| |
| There's a feature I missed in Interlinks: Support for [[wp>Help:Piped_link|piped links]]; continuing with the above example, <html><code>[[Some article|That's a nicer title IMHO]]</code></html> would link to <html><var>"Some article"</var></html> but the link text will be <html><var>"That's a nicer title IMHO"</var></html>. | //Relative URLs// can be seen as kind of complementary to Interlinks: It creates a valid URL or link from a relative path. |
| | \\ |
| | If you want to link to a post Interlinks or Interlinks+ are better alternatives, but if you want to link to a given file in your site neither will help you. |
| | \\ |
| | I guess so far it isn't clear what's the need for such a plugin, so let's clarify a bit, note that: |
| |
| Additionally I added a couple extra modifications to generate valid XHTML, and made the link also display the article's title. | * Pages can be accessed from more than one URL (I'm assuming your WordPress installation is in a subdirectory and URL redirection is being used): |
| | * <html><samp>http://example.com/parentpage/page/</samp></html> |
| | * <html><samp>http://example.com/wordpress/parentpage/page/</samp></html> |
| | * <html><samp>http://example.com/wordpress/?page_id=2</samp></html> |
| | * Using an absolute URL to refer to stuff in the site has the potential of being broken if you |
| | * Change WordPress' path, e.g.: <html><samp>http://example.com/wordpress/</samp></html> is moved to <html><samp>http://example.com/</samp></html> or <html><samp>http://example.com/blog/</samp></html>. |
| | * Change your (sub)domain, e.g. <html><samp>http://example.com/</samp></html> becomes <html><samp>http://blog.example.com/</samp></html>. |
| | * Using a relative URL to refer to stuff in the site has the potential of being broken if you (or visitors) |
| | * Access from a different URL, e.g.: A relative URL like <html><samp>images/im.jpg</samp></html> will point to different things when accessed from <html><samp>http://example.com/parentpage/page</samp></html> (<html><samp><var>http://example.com/parentpage/page/images/im.jpg</var></samp></html>) and <html><samp>http://example.com/wordpress/?page_id=2</samp></html> (<html><samp><var>http://example.com/wordpress/images/im.jpg</var></samp></html>). |
| |
| Let's compare Interlinks and Interlinks+:^ ^ Interlinks |^ Interlinks+ || | | | Finally, if you use a local copy of WordPress to test stuff, chances are your local copy would have quite a different URL, e.g. <html><samp>http://localhost/~username/wordpress/</samp></html> and you might want your URLs to point to the local copy and not the on-line site.</p> |
| ^ Code ^ Generated HTML ^ Rendered HTML ^ Generated HTML ^ Rendered HTML | | | | |
| | <code>[[My article]]</code> | <code><a href="http://example.invalid/my-article/">My article</a></code> | http://example.invalid/my-article/ | <a href="http://example.invalid/my-article/" title="My article">My article</a> | http://example.invalid/my-article/ | | | | |
| | <nowiki>[[My article|My first article]]</nowiki> | * <code html><font color='red'>My article</font></code> | My first article</font> | My article | My first article | <a href="http://example.invalid/my-article/" title="My article">My first article</a> | http://example.invalid/my-article/ | | |
| | * [[Broken]] | * <font color='red'>Broken</font> | Broken | | * Broken | | | | |
| |
| | ===== Interlinks+ ===== |
| |
| | <callout type="info" icon="true" title="No longer needed">This plugin was integrated back into the main [[//wordpress.org/extend/plugins/interlinks/|Interlinks]] so it is deprecated.</callout> |
| |
| <div class="tiny"><dfn class="tt">*</dfn> indicates a broken interlink</div> | [[/files/wordpress/kd-o-interlinks.php|Download v1.0a+]] (last update october 13th 2007). |
| <table style="width:100%;padding:0;margin:0;border:1px solid black;font-size:small;"> | |
| |
| <!-- End of Interlinks+ --> | Interlinks+ is based on [[http://www.harleyquine.com/php-scripts/interlinks/|Interlinks]] by Harley. The original adds a very nifty feature: it enables wiki-style interlinks (e.g. <html><code>[[Some article]]</code></html> will be converted to a link to the post/page titled <html><var>"Some article"</var></html>). |
| |
| ===== Relative URLs ===== | There's a feature I missed in Interlinks: Support for [[wp>Help:Piped_link|piped links]]; continuing with the above example, <html><code>[[Some article|That's a nicer title IMHO]]</code></html> would link to <html><var>"Some article"</var></html> but the link text will be <html><var>"That's a nicer title IMHO"</var></html>. |
| |
| <p><a href="files/net_outlyer_wp-relativeurls.php">Download v1.5</a> (last update october 14th 2007)</p> | Additionally I added a couple extra modifications to generate valid XHTML, and made the link also display the article's title. |
| |
| <p><em>Relative <abbr title="Uniform Resource Locator">URL</abbr>s</em> | Let's compare Interlinks and Interlinks+: |
| (hereon <abbr title="Relative URLs">RU</abbr>) is | |
| mainly targeted at people with a <strong>local copy</strong> of their | |
| WordPress site and those that <strong>reorganise and/or change their | |
| pages hierarchy often</strong> although many standard installations | |
| can also take advantage of it.</p> | |
| |
| <p><abbr title="Relative URLs">RU</abbr> can be seen as kind of complementary | ^ \\ Case 1: Standard interlink ||^ |
| to Interlinks: It creates a valid URL or link from a relative path. | | Example: ''<nowiki>[[My article]]</nowiki>'' ||| |
| <br /> | ^ ^ Interlinks ^ Interlinks+ ^ |
| If you want to link to a post Interlinks or Interlinks+ are better alternatives, | ^ Generated HTML | <code html><a href="http://example.invalid/my-article/">My article</a></code> | <code html><a href="http://example.invalid/my-article/" title="My article">My article</a></code> | |
| but if you want to link to a given file in your site none of them will help you. | ^ Rendered HTML | <html><a href="http://example.invalid/my-article/">My article</a></html> | <html><a href="http://example.invalid/my-article/" title="My article">My article</a></html> | |
| <br /> | ^ \\ Case 2: Interlink with user-supplied text ||^ |
| I guess so far it isn't clear what's the need for such a plugin, so let's clarify | | Example: ''<nowiki>[[My article|My first article]]</nowiki>'' ||| |
| a bit, note that:</p> | ^ ^ Interlinks ^ Interlinks+ ^ |
| | ^ Generated HTML | <code html><font color='red'>My article</font></code> | <code html><a href="http://example.invalid/my-article/" title="My article">My first article</a></code> | |
| | ^ Rendered HTML | <html><span style="color:red;"><nowiki>My article|My first article</nowiki></span></html> <label type="warning">broken link</label> | <html><a href="http://example.invalid/my-article/" title="My article">My first article</a></html> | |
| | ^ \\ Case 3: Broken link ||^ |
| | | Example: ''<nowiki>[[Broken]]</nowiki>'' (where "Broken" doesn't exist) ||| |
| | ^ ^ Interlinks ^ Interlinks+ ^ |
| | ^ Generated HTML | <code html><font color='red'>Broken</font></code> | <code html><span style="color:red;">Broken</span></code> | |
| | ^ Rendered HTML | <html><span style="color:red;">Broken</span></html> <label type="warning">broken link</label> | <html><span style="color:red;">Broken</span></html> <label type="warning">broken link</label> | |
| |
| <ul><li>Pages can be accessed from more than one URL (I'm assuming | ==== Usage ==== |
| your WordPress installation is in a subdirectory and URL redirection | |
| is being used): | |
| <ul> | |
| <li><samp>http://example.com/parentpage/page/</samp></li> | |
| <li><samp>http://example.com/wordpress/parentpage/page/</samp></li> | |
| <li><samp>http://example.com/wordpress/?page_id=2</samp></li> | |
| </ul> | |
| </li> | |
| |
| <li>Using an absolute URL to refer to stuff in the site has the potential | Enclose your local URL in double braces (e.g. <html><samp></html>''<nowiki>{{myrelative/url}}</nowiki>''<html></samp></html>), to get a full URL generated dynamically, e.g. to <html><samp>http://example.com/wordpress/myrelative/url</samp></html>. |
| of being broken if you | |
| <ul> | |
| <li>Change WordPress' path, e.g.: <samp>http://example.com/wordpress/</samp> | |
| is moved to <samp>http://example.com/</samp> or <samp>http://example.com/blog/</samp>. | |
| </li> | |
| <li>Change your (sub)domain, e.g. <samp>http://example.com/</samp> | |
| becomes <samp>http://blog.example.com/</samp>.</li> | |
| </ul> | |
| </li> | |
| |
| <li>Using a relative URL to refer to stuff in the site has the potential | Enclose your local URL in double braces along a text description (separated by a space) to get a dynamically generated link to the full URL. |
| of being broken if you (or visitors) | \\ |
| <ul> | <html><samp></html>''<nowiki>{{the_url/file.txt The text file}}</nowiki>''<html></samp></html> would become |
| <li>Access from a different URL, e.g.: A relative URL like <samp>images/im.jpg</samp> | <html><samp><a href="http://example.com/wordpress/the_url/file.txt">The text file</a></samp></html>. |
| will point to different things when accessed from | |
| <samp>http://example.com/parentpage/page</samp> | |
| (<samp><var>http://example.com/parentpage/page/images/im.jpg</var></samp>) | |
| and <samp>http://example.com/wordpress/?page_id=2</samp> | |
| (<samp><var>http://example.com/wordpress/images/im.jpg</var></samp>). | |
| </li> | |
| </ul> | |
| </li> | |
| </ul> | |
| | |
| <p>Finally, if you use a local copy of WordPress to test stuff, chances | |
| are your local copy would have quite a different URL, e.g. | |
| <samp>http://localhost/~username/wordpress/</samp> and you might | |
| want your URLs to point to the local copy and not the on-line site.</p> | |
| | |
| <h3 id="ru-usage">Usage</h3><!-- of Relative URLs --> | |
| |
| <p>Enclose your local URL in double braces (e.g. <samp>{{myrelative/url}}</samp>), to get a | Note you'll have to encode any spaces in the url (e.g. to link to "<html><samp>the file</samp></html>"; you'll have to encode the space (replace it with ''%20'') |
| full URL generated dinamically, e.g. to <samp>http://example.com/wordpress/myrelative/url</samp>.</p> | i.e.: <html><samp></html>''<nowiki>{{the%20file}}</nowiki>''<html></samp></html>. |
| |
| <p>Enclose your local URL in double braces along a text description (separated by a space) | ==== Escaping Relative URLs ==== |
| to get a dinamically generated link to the full URL. | |
| <br /> | |
| <samp>{{the_url/file.txt The text file}}</samp> would become | |
| <samp><a href="http://example.com/wordpress/the_url/file.txt">The text | |
| file</a></samp>. | |
| <br /><br /> | |
| Note you'll have to encode any spaces in the url (e.g. to link to | |
| "<samp>the file</samp>" you'll have to encode the space (replace it with | |
| <kbd>%20</kbd>) i.e.: <samp>{{the%20file}}</samp>.</p> | |
| |
| <h4 id="ru-escape">Escaping <em>Relative URLs</em></h4> | If you want to write literal double curly brackets (''{{'') then you'll have to use an //html entity// such as <html><samp></html>''{''<html></samp></html> and |
| | <html><samp></html>''}''<html></samp></html> (or <html><samp></html>''{''<html></samp></html> and <html><samp></html>''}''<html></samp></html>). |
| <p>If you want to write literal double curly brackets (<kbd>{{</kbd>) then | For maximum security use at least one on each end, e.g. |
| you'll have to use an html entities such as <samp>&#x7b;</samp> and | <html><samp></html>''{{\_whatever\_}}''<html></samp></html> will be parsed correctly as |
| <samp>&#x7d;</samp> (or <samp>&#123;</samp> and <samp>&#125;</samp>). For | <html><samp></html>''{{\_whatever\_}}''<html></samp></html>. |
| maximum security use at least on each end, e.g. | \\ |
| <samp>&#x7b;{ whatever &#x7d;}</samp> will be parsed correctly as | |
| <samp>{{ whatever }}</samp>. | |
| <br /> | |
| BUT beware of the visual editor in WordPress (although if you use it you're | BUT beware of the visual editor in WordPress (although if you use it you're |
| probably used to fight it ;).</p> | probably used to fight it ;). |
| | |
| <!-- End of Relative URLs --> | |
| |
| ===== JS Base2 ===== | ===== JS Base2 ===== |
| |
| <p><a href="files/js-base2-1.0+0.9a.tar.gz">Download v1.0+0.9a</a> (last update october 24th 2007). (Note <var>1.0</var> is the plugin version and <var>0.9a</var> is the base2's version used in the plugin).</p> | <callout type="danger" icon="true" title="Abandoned">This plugin is abandoned. Additionally, Base2 doesn't seem to be updated anymore.</callout> |
| |
| <p>A completely trivial plugin that loads <a href="http://dean.edwards.name">Dean Edwards'</a> <strong>base2</strong> JavaScript library (see <a href="http://dean.edwards.name/weblog/2007/03/yet-another">[1]</a> and <a href="http://code.google.com/p/base2/">[2]</a>).</p> | [[/files/wordpress/js-base2-1.0+0.9a.tar.gz|Download v1.0+0.9a]] (last update october 24th 2007). (Note <var>1.0</var> is the plugin version and <var>0.9a</var> is the Base2 version used in the plugin). |
| |
| <p>This library is mostly a cross-browser fix of the <abbr title="Document Object Model">DOM</abbr> plus a selectors <abbr title="Aplication Programming Interface">API</abbr> implementation (allowing selection from <abbr title="JavaScript">JS</abbr> with <abbr title="Cascading Style Sheets">CSS</abbr> selectors).</p> | A completely trivial plugin that loads [[http://dean.edwards.name|Dean Edwards]] **base2** JavaScript library (see [[http://dean.edwards.name/weblog/2007/03/yet-another|[1]]] and [[http://code.google.com/p/base2/| [2]]]). |
| |
| <p>It is used by the following plugin :)</p> | This library is mostly a cross-browser fix of the <html><abbr title="Document Object Model">DOM</abbr></html> plus a selectors API implementation (allowing selection from JavaScript with CSS selectors). |
| |
| <!-- End of JS Base 2 --> | <label type="info">Note</label> It is used by the following plugin :) |
| |
| ===== JS Syntax Highlighter ===== | ===== JS Syntax Highlighter ===== |
| |
| <p><a href="files/js-syntax-highlighter-0.2.tar.gz">Download v0.2</a> (last update october 25th 2007).</p> | <callout type="danger" icon="true" title="Abandoned">This plugin is abandoned.</callout> |
| |
| <p>This plugin loads <a href="http://code.google.com/p/syntaxhighlighter/">Alex Gorbatchev's</a> <strong>SyntaxHighlighter</strong> JavaScript script. With a twist :)</p> | [[/files/wordpress/js-syntax-highlighter-0.2.tar.gz|Download v0.2]] (last update october 25th 2007). |
| |
| <p>SyntaxHighlighter is a script that will highlight code from JavaScript when marked appropriately, hence allowing you to post raw code that will be automagically prettyprinted on load. | This plugin loads Alex Gorbatchev **[[http://code.google.com/p/syntaxhighlighter/SyntaxHighlighter]]** JavaScript script. With a twist :) |
| <br /> | |
| | //SyntaxHighlighter// is a script that will highlight code from JavaScript when marked appropriately, hence allowing you to post raw code that will be automagically pretty-printed on load. |
| | \\ |
| I needed a couple workarounds to use it on my site and they were the motivation for this plugin: | I needed a couple workarounds to use it on my site and they were the motivation for this plugin: |
| </p> | |
| |
| <dl> | First problem: Code must be enclosed in either a ''<pre>'' or a ''<textarea>'' tag, with their ''name'' attribute set to certain (user-selectable) value.\ The problem is, ''<pre>'' has no ''name'' attribute so the page wouldn't validate. |
| <dt>First problem: Code must be enclosed in either a <code><pre></code> | \\ |
| or a <code><textarea></code> tag, with their <code>name</code> | (emsp) ** My solution:** (Note I opted to not modify SyntaxHighlighter code) Mark code with a class and then, on-the-fly, add the name attribute from JavaScript (this makes the HTML validate as the invalid attribute is only created in-memory). |
| attribute set to certain (user-selectable) value. | |
| <br /> | |
| The problem is, <code><pre></code> has no <code>name</code> attribute so | |
| the page wouldn't validate.</dt> | |
| <dd style="margin-bottom:1em"><strong>My solution:</strong> (Note I opted to not modify SyntaxHighlighter | |
| code) Mark code with a class and then, on-the-fly, add the name attribute from | |
| JavaScript (this makes the HTML validate as the invalid attribute is only | |
| created in-memory).</dd> | |
| |
| <dt>Second problem: Each supported language has its own associated JavaScript | \\ |
| file which you should load when writing code for a that language. I felt | Second problem: Each supported language has its own associated JavaScript file which you should load when writing code for that language. I felt loading them site-wide was was overkill (and I don't know which languages I might need), while loading them as needed, in the article body, felt cumbersome. |
| loading them site-wide was was overkill (and I don't know which languages I | \\ |
| might need), while loading them as needed, in the article body felt cumbersome.</dt> | (emsp) **My solution:** Load the common script, see if any languages are needed and load them dynamically. As a side effect the page will load faster (the required languages are loaded after the page ended loading). |
| <dd><strong>My solution:</strong> Load the common script, see if any languages are | |
| needed and load them dinamically. As a side effect the page will load faster | |
| (the required languages are loaded after the page ended loading).</dd> | |
| </dl> | |
| |
| <p>So <strong>in short</strong> this plugin loads SyntaxHighlighter allowing your | So **in short** this plugin loads SyntaxHighlighter allowing your pages to validate and only loading language files as needed. |
| pages to validate and only loading language files as needed.</p> | |
| |
| <p>I also changed the CSS file a bit to use fonts I consider look better | I also changed the CSS file a bit to use fonts I consider look better and added colours to <html><var></html>functions<html></var></html> and <html><var></html>variables<html></var></html>. |
| and added colours to <var>functions</var> and <var>variables</var>.</p> | |
| |
| <h3 id="jsh-usage">Usage</h3> | ==== Usage ==== |
| |
| <p>Plugin installation:</p> | Plugin installation: |
| <ol> | - Decompress in the ''wp-content/plugins'' folder, it will create its own folder. |
| <li>Decompress in the <code>wp-content/plugins</code> folder, it will create | - Activate it from WordPress' admin panel. |
| its own folder.</li> | |
| <li>Activate it from <abbr title="WordPress">WP</abbr>'s admin panel.</li> | |
| </ol> | |
| |
| <p>Syntax highlighting:</p> | Syntax highlighting: |
| <ol> | - Wrap your code in a ''<pre>'' or ''<textarea>'' with class ''syntax-highlight'' and the appropriate class for the language of the block, e.g. ''cpp'' for C++ (see [[http://code.google.com/p/syntaxhighlighter/wiki/Languages|the full list]]). |
| <li>Wrap your code in a <pre> or <textarea> with class '<code>syntax-highlight</code>' and | - There's no step 2 :P But remember the highlighting takes place a bit after loading the page. |
| the appropriate class for the language of the block, e.g. '<code>cpp</code>' for C++ (see | |
| <a href="http://code.google.com/p/syntaxhighlighter/wiki/Languages">the full list</a>).</li> | |
| <li>There's no step 2 :P But remember the highlighting takes place a bit after loading the page.</li> | |
| </ol> | |
| |
| <h4 id="jsh-no-base2">Usage without <em>base2</em></h4> | === Usage without base2 === |
| |
| <p>I dropped support for such a situation. You can try with an older version of | I dropped support for such a situation. You can try with an older version of ''loader.js'' but keep in mind that then languages **won't be autoloaded**. |
| loader.js but keep in mind that then languages <strong>won't be | |
| autoloaded</strong>.</p> | |
| |
| <h3 id="jsh-caveats">Caveats of the current version</h3> | ==== Caveats of the current version ==== |
| |
| <h4 id="jsh-passing-options">Passing options for a single block</h4> | === Passing options for a single block === |
| |
| <p>Passing options for a block to SyntaxHighlighter needs a workaround as | Passing options for a block to SyntaxHighlighter needs a workaround as my loader won't detect the language then, the workaround is to use a hidden, empty block without options, i.e: |
| my loader won't detect the language then, the workaround is to use a hidden, | \\ |
| empty block without options, i.e:<br /> | If you want to have something like |
| If you want to have something like</p> | |
| | |
| <!-- Ensure correct loading of language file --> | |
| <div style="display:none !important;"><pre class="syntax-highlight html javascript"></pre></div> | |
| |
| <pre class="html:nogutter syntax-highlight"> | <file javascript> |
| <pre class="syntax-highlight javascript:firstline[10]"> | <pre class="syntax-highlight javascript:firstline[10]"> |
| function doSomething() { | function doSomething() { |
| } | } |
| </pre> | |
| </pre> | </pre> |
| | </file> |
| | <label type="info">PLEASE NOTE</label> This is not an actual representation of the plugin in action. This page doesn't use SyntaxHighlighter. |
| |
| <p>Then you'll need to add a hidden block with the language class(es) needed. | \\ |
| That block can have the classes of all needed languages:</p> | Then you'll need to add a hidden block with the language class(es) needed. That block can have the classes of all needed languages: |
| |
| <pre class="html:nogutter:firstline[5] syntax-highlight"> | <file javascript> |
| <!-- Hidden, meaningless, code block --> | <!-- Hidden, meaningless, code block --> |
| <div style="display:none !important;"> | <div style="display:none !important;"> |
| <pre class="syntax-highlight html cpp"></pre> | <pre class="syntax-highlight html cpp"></pre> |
| </div> | </div> |
| </pre> | </file> |
| |
| <h4 id="jsh-disabled-aliases">Disabled language aliases</h4> | === Disabled language aliases === |
| |
| <p>Due to the way the code is written the following language name aliases won't | Due to the way the code is written the following language name aliases won't be looked for (all of them have alternatives): ''c++'', ''c#'', ''vb.net''. |
| be looked for (all of them have alternatives): <code>c++</code>, <code>c#</code>, | |
| <code>vb.net</code>.</p> | |
| |
| <p>They could be enabled with some escaping but I didn't feel the need :p</p> | They could be enabled with some escaping but I didn't feel the need :p |
| |
| <h3 id="jsh-config">Customisation</h3> | ==== Customisation ==== |
| | |
| <p>There're a couple things you might want to tweak, to change them edit the file <code>loader.js</code> | |
| (note that the version actually loaded in the browser is the one in the <code>js/</code> directory, | |
| but it is shipped packed with <a href="http://dean.edwards.name/packer/">Dean Edwards' packer</a>, | |
| which makes it quite harder to edit. I suggest you to edit the version in the <code>full-js/</code> | |
| directory and once you're happy with it pack it again.</p> | |
| | |
| <script type="text/javascript" src="http://outlyer.net/site/wp-content/plugins/js-base2/base2-dom-fp.js"></script> | |
| <script type="text/javascript" src="http://outlyer.net/site/wp-content/plugins/js-syntax-highlighter/js/shCore.js"></script> | |
| <script type="text/javascript" src="http://outlyer.net/site/wp-content/plugins/js-syntax-highlighter/js/loader.js"></script> | |
| <script type="text/javascript"> | |
| dpLoader.init('http://outlyer.net/site/wp-content/plugins/js-syntax-highlighter'); | |
| </script> | |
| | |
| <pre class="syntax-highlight javascript:firstline[19]"> | |
| bloggerMode: false, // Set to true if the blogging software adds <br />'s | |
| // See: <http://code.google.com/p/syntaxhighlighter/wiki/BloggerMode> | |
| opts: [ // Options for HighlightAll, see <http://code.google.com/p/syntaxhighlighter/wiki/HighlightAll> | |
| true, // Show Gutter | |
| false, // Show Controls (!*not default*) | |
| false, // Collapse all | |
| 1, // First line | |
| false // Show columns | |
| ], | |
| WAIT_TO_LOAD: 200, // (ms) Period to wait between checks for language loading | |
| FAIL_TIMEOUT: 120000, // (ms) After this period will stop trying to load languages | |
| </pre> | |
| |
| <p>These are the meaningful variables, I think they're self explanatory enough, | There're a couple things you might want to tweak, to change them edit the file ''loader.js'' (note that the version actually loaded in the browser is the |
| a note of warning though: if some of the languages fails loading you'll have to | one in the ''js/'' directory, but it is shipped packed with [[http://dean.edwards.name/packer/|Dean Edwards' packer]], which makes it quite harder to edit. |
| wait for <code>FAIL_TIMEOUT</code> milliseconds before syntax highlighting gets | I suggest you to edit the version in the ''full-js/'' directory and once you're happy with it pack it again. |
| enabled. Set it too low, though, and you'll get bogus failures.</p> | |
| |
| <!-- End of JS Syntax Highlighter --> | <file javascript> |
| | bloggerMode: false, // Set to true if the blogging software adds <br />'s |
| | // See: <http://code.google.com/p/syntaxhighlighter/wiki/BloggerMode> |
| | opts: [ // Options for HighlightAll, see <http://code.google.com/p/syntaxhighlighter/wiki/HighlightAll> |
| | true, // Show Gutter |
| | false, // Show Controls (!*not default*) |
| | false, // Collapse all |
| | 1, // First line |
| | false // Show columns |
| | ], |
| | WAIT_TO_LOAD: 200, // (ms) Period to wait between checks for language loading |
| | FAIL_TIMEOUT: 120000, // (ms) After this period will stop trying to load languages |
| | </file> |
| |
| <hr style="margin-top:1em;" /> | These are the meaningful variables, I think they're self explanatory enough, a note of warning though: if some of the languages fail loading you'll have to |
| <footer> | wait for ''FAIL_TIMEOUT'' milliseconds before syntax highlighting gets enabled. Set it too low, though, and you'll get bogus failures. |
| <div class="footer"> | |
| <address>© 2007 <span id="email">Toni Corvera <outlyer at gmail dot com></span> | |
| <br /> | |
| <span class="tiny">[<a href="http://outlyer.net./pubkey.asc">GPG Key</a>]</span></address> | |
| <br /> | |
| <aside><address> | |
| Other than by e-mail, you can leave your comments about any of these plugins in the | |
| <a href="http://outlyer.net/codigo/wordpress/" hreflang="es">WordPress code</a> page in my site. | |
| </address></aside> | |
| |
| | <WRAP rightalign small> |
| | //(c) 2007 Toni Corvera < outlyer at gmail dot com >// |
| | </WRAP> |
| |
| |