JavaScript Archive Network
- Brian Cassidy worked over the site's style to make it IE
friendly. By far the coolest thing of the day.
- Adam Kennedy is working on an alternative JSAN Client.
- David Wheeler added support for tags in META.yml, in Module-
Build-JSAN. This is very cool, it means you can supply a list of tags
in Build.PL. Who needs categories anymore?
- David also tweaked the JSAN Library to always refer to
JSAN.globalScope to find the global scope.
JSAN 0.08 was
released with this change (I forgot to update the Changes file!). I
also added tags to this library.
- I added support for stripping inline POD from JavaScript
libraries in Moudle-Build-JSAN. This will keep JSAN.js lean.
- I added tag support to the incoming processor.
- I added a tag cloud to the
home page
- The incoming processor now builds
pages for
tags too.
Categories are known to be a broken system. Taxonomy is much
better. Therefore, authors can control the categories (tags) on JSAN
by including them in the META.yml. Here is what the JSAN Library's
META.yml file looks like now.
---
name: JSAN
version: 0.08
author:
- Casey West
abstract: JavaScript Archive Network
license: artistic
build_requires:
Test.Simple: 0.11
provides:
JSAN:
file: lib/JSAN.js
version: 0.08
generated_by: Module::Build version 0.2701
tags:
- jsan
- use
- import
- libraries
Of course this was generated using Module-Build-JSAN (which is in
the JSAN SVN). Here's
the Build.PL.
use Module::Build::JSAN;
my $build = Module::Build::JSAN->new(
module_name => 'JSAN',
license => 'artistic',
dist_author => 'Casey West ',
abstract => 'JavaScript Archive Network',
create_readme => 1,
build_requires => {
'Test.Simple' => '0.11',
},
tags => [qw[jsan use import libraries]],
);
$build->create_build_script;
Posted from caseywest.com, comment here.
