I agree with the marketing / branding side presented by the AM above, although I probably would not use the given example :)

Impression, correct or not, can taint many decisions. "Squatting" has the impression of illegitimacy, lack of blessing, or possibly even stealing. "Camping" implies at least permission, if not promotion. In today's BSA skittish world, staying away from the potential (actual or not) of illegitimacy can't hurt.

The merits of the module appear to be very good, but I would hate to see it dismissed before looking at the merits because of the name.

I hope...

I hope someone out there thought that Squatting was a funny name for a port of the Camping web microframework. Keep in mind that I am aware of the various (vulgar) connotations that a word like "squatting" has -- that's why I picked it! Maybe my sense of humor is nerdy beyond repair, but I thought it was funny.

(What have our corporate overlords done to us?)

I hope someone out there thought that Squatting was a funny name

I thought it was both a hilarious name and a badass piece of software :)

-stvn

controller did model things

 # STEP 2 => Create a Controllers package
  {
    package App::Controllers;
    use Squatting ':controllers';

    # Setup a list of controller objects in @C using the C() function.
    our @C = (
      C(
        Home => [ '/' ],
        get  => sub {
          my ($self) = @_;
          my $v = $self->v;
          $v->{title}   = 'A Simple Squatting Application';
          $v->{message} = 'Hello, World!';
          $self->render('home');
        },
        post => sub { }
      ),
    );
  }
[download]

Hey, man. It's been a while. Hope you're well. :)

Anyway...

You bring up a good point. $self->v is the equivalent of Catalyst's stash. However, now that you bring this up, I think "v" was not the best name for this hashref. The mnemonic I had in mind was "v" for "variable", but I can see how it can be ambiguous with "V" for "View". Ah fuck. ;-)

I think "v" was not the best name for this hashref. The mnemonic I had in mind was "v" for "variable", but I can see how it can be ambiguous with "V" for "View". Ah fuck. ;-)

heh. maybe there could be an alias like $self->stash

But I think Brock or you would be in a better position to actually decide on the verbose descriptive non-deceptive alias than me.

Why would I want to embed Pod::Server?

I think this is going over my head.

Pod::Server is just being used as an example. There's no practical purpose to embedding Pod::Server into anything. I'm just trying to show you guys that the embedding functionality works. The next step if for you guys to use your imagination and try to see a future where you can build significant portions of a site by combining multiple applications together into one cohesive whole.

But seriously, is there some sort of shootout where we see how a web framework handles certain application tasks? Implementing petshop was done by Bivio to compare with the Java petshop, but that is a rather large task.

A 17-line Wiki

Prerequisites

• Squatting
• Text::Textile
• IO::All

Code

package MicroWiki;
use base 'Squatting';
package MicroWiki::Controllers;
use Squatting ':controllers'; use IO::All;
@C = C( Page => ['/', '/(\w+)', '/(\w+).(edit)' ],
get => sub { $_[1] ||= 'Home'; -f $_[1] || 'Edit' > io($_[1]); $x < io
+($_[1]);
$_[0]->v->{page} = $_[1]; $_[0]->v->{text} = $x; 
$_[0]->render($_[2] && 'edit' || 'page') }, post => sub {
$_[0]->input->{text} > io($_[1]); $_[0]->redirect(R('Page', $_[1])) })
+;
package MicroWiki::Views;
use Squatting ':views';
use Text::Textile qw(textile);
our @V = (V(html, page => sub { '<a href="'.R('Page',$_[1]->{page},'ed
+it').
'">edit</a>'.textile($_[1]->{text}) }, edit => sub{sprintf( '
<form method="post" action="%s"><textarea name="text" rows="20">%s</te
+xtarea>'
.'<input type="submit"/></form>',
R('Page', $_[1]->{page}), $_[1]->{text}) })); 1;
[download]

And no line exceeds 78 characters in length. ;-) I can actually shrink this by a few more lines if I tried harder, but I'm satisfied w/ what I have.

To run this Wiki, put the code in a file called "MicroWiki.pm" and type:

squatting MicroWiki
[download]

To embed this into a Catalyst app, add the following code to your Catalyst app's Root controller.

use MicroWiki 'On::Catalyst';
MicroWiki->init;
MicroWiki->relocate('/wiki');
sub wiki : Local { MicroWiki->catalyze($_[1]) }
[download]

If you want to replace the (non-existent) layout:

my $view = $MicroWiki::Views::V[0];
$view->{layout} = sub {
  my ($self, $v, $content) = @_;
  # return a string that wraps around $content
};
[download]

Runs great right out of the box. I have it up at http://ns4.epfarms.org:4234/ if anyone wants to give it a go. I still vote for optional alternate longer names for C(...) and V(...)... yeah yeah patches welcome :)

A 17-line Wiki

sa-weet.

Someone else asked about setting up a Google Group, so I started one a few days ago:

http://groups.google.com/group/squatting-framework