Changeset 305

Show
Ignore:
Timestamp:
02/16/08 17:44:14 (5 months ago)
Author:
ingy
Message:
Move the sample Foo-Bar to JS-Foo-Bar
Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/src/ingy/JS/lib/JS.pm

    r295 r305  
    55use 5.005.003; 
    66 
    7 our $VERSION = '0.10'; 
     7our $VERSION = '0.11'; 
    88 
    99sub new { 
    …… 
    7777Some JavaScript modules can be installed from CPAN. This module comes 
    7878with a utility called C<js-cpan> that helps you find JavaScript modules 
    79 that have been installed on you system so that you can use them in 
     79that have been installed on your system so that you can use them in 
    8080various projects. 
    8181 
    …… 
    9090Makefiles to set things up. 
    9191 
    92 The Open JSAN project offers the tip off the iceberg in terms of being a 
    93 CPAN for JavaScript. However it has a long way to go and not a lot of 
    94 community to get it there. 
     92The Open JSAN project offers the tip off the iceberg in terms of 
     93being a CPAN for JavaScript. However it has a long way to go and not 
     94a lot of community to get it there. CPAN is a good place to put 
     95JavaScript modules. 
    9596 
    9697Many projects require JavaScript components these days, and it would be 
    …… 
    9899distributions. 
    99100 
    100 There is a simple way to package non-Perl components into Perl/CPAN 
     101There is a dead simple way to package non-Perl components into Perl/CPAN 
    101102distributions. The components get installed in your Perl system but do 
    102103not affect Perl in any other way. 
    103104 
    104 JS is a module to explain and help maintain the JavaScript modules 
     105JS.pm is a module to explain and help maintain the JavaScript modules 
    105106installed from CPAN. 
    106107 
    107 Some module distributions will have both Perl and JavaScript components. 
    108 Others will have only JavaScript components. All JavaScript modules and 
    109 JavaScript module distributions should have a top-level-namespace of 'JS'. 
     108Some module distributions will have both Perl and JavaScript 
     109components. Others will have only JavaScript components. All JavaScript 
     110modules and JavaScript-only distributions should have a top-level-namespace 
     111of 'JS'. 
    110112 
    111113=head1 JS MODULE AUTHOR HOWTO 
    112114 
    113115It turns out that Perl's ExtUtils::MakeMaker will install *any* 
    114 files that you put in the C<lib/> directory, into your perl's 
    115 sitelib. So setting up a JavaScript distribution is very similar to 
     116files that you put in the C<lib/> directory, into your C<perl>'s 
     117C<sitelib>. So setting up a JavaScript distribution is very similar to 
    116118setting on a Perl one. 
    117119 
    …… 
    146148That's it. You've joined the revolution. :) 
    147149 
    148 NOTE: There is a working sample JavaScript module shipped with C<JS.pm> 
    149       in the C<examples/Foo-Bar> directory. 
     150NOTE: There is a working example JavaScript module shipped with C<JS.pm> 
     151      in the C<examples/JS-Foo-Bar> directory. 
    150152 
    151153=head1 AUTHOR