Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

sri (5109)

sri
  (email not shown publicly)
http://labs.kraih.com/

Journal of sri (5109)

Wednesday November 05, 2008
10:33 AM

Want Mojo documentation?

I've submitted a grant proposal to the Perl Foundation, you can leave a comment there to show them your interest, every comment counts!
Monday November 03, 2008
09:00 AM

Mojo website launched!

08:53 AM

Mojo 0.8 released (full Windows compatibility)

Monday October 20, 2008
01:31 PM

Mojo 0.7 released (Perl on Rails in 150 lines of code)

Tuesday October 14, 2008
08:32 AM

Dispatchers for dummies! :)

Saturday October 11, 2008
06:06 AM

Mojolicious?!

Because explaining internals always sucks, this will be much more fun. :)
Thursday October 09, 2008
06:22 AM

The core of the Mojo Web Framework

This time i'm showing you a bit about the basic ideas behind Mojo.
Wednesday September 24, 2008
01:19 PM

Mojo, a new kind of web framework

It started as a Catalyst competitor but resulted in something different, the good kind of different. :)

Here's the first part of my upcoming blog article series, Why Mojo won't kill Catalyst.
Sunday November 05, 2006
05:05 PM

Did TPF give up on Perl5?

Saturday May 06, 2006
07:20 AM

Mojo applications, valid cpan modules or not?

You may know, by default Catalyst applications are valid cpan modules, with the application name as root namespace.
Now that i'm designing Mojo with usability in mind i can't think of a good reason for keeping that format.

When i made the decision 1 1/2 years ago for Catalyst i thought it would be useful to be able to upload applications to cpan, but today there is only one!

Installing the applications on a host system doesn't make much sense either, so why do it again?


With the old format a Mojo app would look like this:

TestApp
TestApp/lib
TestApp/lib/TestApp
TestApp/lib/TestApp/Component
TestApp/lib/TestApp/Component/Example.pm
TestApp/lib/TestApp/Context.pm
TestApp/lib/TestApp/Dispatcher
TestApp/lib/TestApp/Dispatcher/Example.pm
TestApp/lib/TestApp/SomethingElse.pm
TestApp/lib/TestApp.pm
TestApp/Makefile.PL
TestApp/script
TestApp/script/testapp_server.pl
TestApp/t
TestApp/t/01use.t

A newer (non valid) version could look like this.

TestApp
TestApp/Component
TestApp/Component/Example.pm
TestApp/Dispatcher
TestApp/Dispatcher/Example.pm
TestApp/SomethingElse.pm
TestApp/Context.pm
TestApp/Application.pm
TestApp/Makefile.PL
TestApp/script
TestApp/script/server.pl
TestApp/t
TestApp/t/01use.t

The basic layout for scripts and tests makes sense and can naturally stay...