So is JSAN dead?

[Klortho]

Hi, I'm new. In reading Javascript, the Definitive Guide, Flanagan
mentions JSAN. It seems the website is a bit stale, is there anything
a new guy can do to help jumpstart it?

[Dan Brook]

s/new guy/anyone/

Enquiring minds would like to know!

To the best of my knowledge the project has stalled sufficiently that
all momentum is gone and is unlikely to be regained at this point.
Opinions to the contrary are most welcome.

Cheers,
Dan Brook

[Nickolay Platonov]

Hello all,

I'm trying to develop a new action for Module::Build::JSAN.
Its - install action, to allow local installation of js modules.

If someone have an experience with Module::Build and wants to help - please email me.

Regards, Nickolay

[David E. Wheeler]

On Apr 14, 2009, at 9:32 AM, Nickolay Platonov wrote:

> I'm trying to develop a new action for Module::Build::JSAN.
> Its - install action, to allow local installation of js modules.

I moved it to GitHub, BTW; have you forked it?

http://github.com/theory/module-build-jsan/tree/master

> If someone have an experience with Module::Build and wants to help -
> please

Not sure I follow what you're trying to do.

Best,

David

[Nickolay Platonov]

Hi David,

Yep, I forked it and currently trying to add some new features.

My goal is - to have a local javascript library, something like:

/usr/local/lib/javascript

and I'd like to be able to install javascript modules into it, just with usual:

./Build install

thats generally a Module::Build configuration task, currently trying to solve it.

The next thing will be to integrate testing into it..

Nickolay

[David E. Wheeler]

On Apr 14, 2009, at 10:06 AM, Nickolay Platonov wrote:

> Hi David,
>
> Yep, I forked it and currently trying to add some new features.
>
> My goal is - to have a local javascript library, something like:
>

> */usr/local/lib/javascript*

>
> and I'd like to be able to install javascript modules into it, just
> with
> usual:
>

> *./Build install*

>
> thats generally a Module::Build configuration task, currently trying
> to
> solve it.

Well, right now Build.PL is not distributed in the package. So you'd
have to restore that.

> The next thing will be to integrate testing into it..

Using Spidermonkey or something?

Best,

David

[Nickolay Platonov]

Not exactly - I have a following scheme in mind:

- establish a small local http-server (using HTTP::Daemon)
- use your test-simple-js
- redirect tests output to local daemon during 'make test'

this should work for all browsers

And if such scheme will be used on Windows machine - than the module can be tested with all major browsers.

[Nickolay Platonov]

Not exactly - I have a following scheme in mind:

- establish a small local http-server (using HTTP::Daemon)
- use your test-simple-js
- redirect tests output to local daemon during 'make test'

this should work for all browsers

And if such scheme will be used on Windows machine - than the module can be tested with all major browsers.

[Kang-Min Liu]

On Apr 15, 2009, at 2:02 AM, Nickolay Platonov wrote:

> Not exactly - I have a following scheme in mind:
>
> - establish a small local http-server (using HTTP::Daemon)
> - use your test-simple-js
> - redirect tests output to local daemon during 'make test'
>
> this should work for all browsers
>
> And if such scheme will be used on Windows machine - than the module
> can be tested with all major browsers.

That will require Test/Simple.js (or subclass of it) to actually POST
the TAP result back to the http server but
this seems really cool and feasible.

An alternative is to does something like watir (http://
wtr.rubyforge.org) did. Either using
win32ole to talk to IE, or use a firefox extension to talk to firefox.
I've tried to use watir
recently and it is really fast on win32 (comparing to selenium).
Apparently using win32ole
is the right way to go. It might be overkill in this case, but it's a
know working solution on windows.

Cheers,
Kang-min Liu

[Nickolay Platonov]

That will require Test/Simple.js (or subclass of it) to actually POST
the TAP result back to the http server but
this seems really cool and feasible.

Yep, thats it. But do not forget also about Chrome and Safari - we need a general solution (which will also work on Linux)

Meanwhile I had initial results. To try it out:

- install Module::Build::JSAN from http://github.com/SamuraiJack/module-build-jsan/tree/master
- Test distribution is attached to this message
- try to install it with usual

perl Makefile.PL
make
make install

The root of the local library can be specified with JSLIB environment variable or ENV{HOME}/.jsan will be used as default.

more info about test distribution:
http://groups.google.com/group/joose-js/browse_thread/thread/527058dce840441d
http://groups.google.com/group/joose-js/browse_thread/thread/22c051afd1df2a6

P.S. I failed to create the distribution with simple
./Build dist
the tarball was totally messed - seems the directory structure was flattened, so I had to use

./Build dist --tar=tar --gzip=gzip

Anyone is familiar with this issue?

Regards, Nickolay

[David E. Wheeler]

On Apr 14, 2009, at 10:54 AM, Nickolay Platonov wrote:

> Not exactly - I have a following scheme in mind:
>
> - establish a small local http-server (using HTTP::Daemon)
> - use your test-simple-js
> - redirect tests output to local daemon during 'make test'
>
> this should work for all browsers

So what browser will you use to run the tests? I don't think you need
a server; it's just JavaScript, the browser can load it from the file
system.

> And if such scheme will be used on Windows machine - than the module
> can be
> tested with all major browsers.

Not following you here.

Best,

David

[David E. Wheeler]

On Apr 14, 2009, at 1:24 PM, Nickolay Platonov wrote:

> P.S. I failed to create the distribution with simple
> ./Build dist
> the tarball was totally messed - seems the directory structure was
> flattened, so I had to use
>
> ./Build dist --tar=tar --gzip=gzip
>
> Anyone is familiar with this issue?

No, but it certainly sounds like a bug. What version of Module::Build?

Best,

David

[Nickolay Platonov]

I'm going to test the modules in all major browsers sequentially.
Lets say it will be IE6,7,8, FF2,3, Chrome, Safari

The reason why the local daemon will be needed - is that I need to somehow receive the test output information.
It can be only POST'ed to daemon, because javascript have no IO except ajax.

As about Windows - I meant that all those browsers can be installed on it simultaneously.
It should be possible to open each browser window with given URL from perl, collect the output info, summarize it, and report to user.


About ./Build dist - its a very strange issue, because on other distributions (non-Jsan) all works good.
Since M:B:Jsan do not override make_tarball, I'm not sure what happening..

[Klortho]

Don't forget Opera.
Sounds very cool indeed.