This gives us non-object-based templated pages. And a little start on

[maypole.git] / lib / Apache / MVC.pm

diff --git a/lib/Apache/MVC.pm b/lib/Apache/MVC.pm
index 467f0f97b83ffb5f01c2d55b59a3bb191c3513f8..c9db3ae415008cf9dcf1613abdf95d90fe766515 100644 (file)
--- a/lib/Apache/MVC.pm
+++ b/lib/Apache/MVC.pm
@@ -6,7 +6,7 @@ use UNIVERSAL::require;
 use Apache::Constants ":common";
 use strict;
 use warnings;
-our $VERSION = "1.0";
+our $VERSION = "0.1";
 __PACKAGE__->mk_classdata($_) for qw( _config init_done view_object );
 __PACKAGE__->mk_accessors ( qw( config ar params objects model_class
 args action template ));
@@ -73,16 +73,24 @@ sub handler {
     $r->get_request();
     $r->parse_location();
 
+    warn "Parsed location\n";
     $r->model_class($r->class_of($r->{table}));
     my $status = $r->is_applicable;
-    return $status unless $status == OK;
-    $status = $r->call_authenticate;
-    return $status unless $status == OK;
-    $r->additional_data();
+    if ($status == OK) { 
+        $status = $r->call_authenticate;
+        return $status unless $status == OK;
+        $r->additional_data();
     
-    $r->model_class->process($r);
-    $r->view_object->process($r);
-    return $r; # For debugging.
+        $r->model_class->process($r);
+    } else { 
+        warn "Plain template $r->{path}";
+        # Otherwise, it's just a plain template.
+        delete $r->{model_class};
+        $r->{path} =~ s{/}{}; # De-absolutify
+        $r->template($r->{path});
+        warn $r->template;
+    }
+    return $r->view_object->process($r);
 }
 
 sub get_request {
@@ -93,8 +101,11 @@ sub get_request {
 
 sub parse_location {
     my $self = shift;
-    my $uri = $self->{ar}->path_info();
-    my @pi = split /\//, $uri;
+    $self->{path} = $self->{ar}->uri;
+    my $loc = $self->{ar}->location;
+    $self->{path} =~ s/^$loc//; # I shouldn't need to do this?
+    warn "Path is $self->{path}";
+    my @pi = split /\//, $self->{path};
     shift @pi while @pi and !$pi[0];
     $self->{table} = shift @pi;
     $self->{action} = shift @pi;
@@ -112,7 +123,6 @@ sub is_applicable {
     return DECLINED() unless exists $config->{ok_tables}{$self->{table}};
 
     # Does the action method exist?
-    # XXX We should set the method class to the class for the table
     my $cv = $self->model_class->can($self->{action});
     warn "We don't have that action ($self->{action})" unless $cv;
     return DECLINED() unless $cv;
@@ -137,3 +147,49 @@ sub additional_data {}
 sub authenticate { return OK }
 
 1;
+
+=head1 NAME
+
+Apache::MVC - Web front end to a data source
+
+=head1 SYNOPSIS
+
+    package BeerDB;
+    use base 'Apache::MVC';
+    sub handler { Apache::MVC::handler("BeerDB", @_) }
+    BeerDB->set_database("dbi:mysql:beerdb");
+    BeerDB->config->{uri_base} = "http://your.site/";
+    BeerDB->config->{display_tables} = [qw[beer brewery pub style]];
+    # Now set up your database:
+    # has-a relationships
+    # untaint columns
+
+    1;
+
+=haed1 DESCRIPTION
+
+A large number of web programming tasks follow the same sort of pattern:
+we have some data in a datasource, typically a relational database. We
+have a bunch of templates provided by web designers. We have a number of
+things we want to be able to do with the database - create, add, edit,
+delete records, view records, run searches, and so on. We have a web
+server which provides input from the user about what to do. Something in
+the middle takes the input, grabs the relevant rows from the database,
+performs the action, constructs a page, and spits it out.
+
+This module aims to be the most generic and extensible "something in the
+middle".
+
+An example would help explain this best. You need to add a product
+catalogue to a company's web site. Users need to list the products in
+various categories, view a page on each product with its photo and
+pricing information and so on, and there needs to be a back-end where
+sales staff can add new lines, change prices, and delete out of date
+records. So, you set up the database, provide some default templates
+for the designers to customize, and then write an Apache handler like
+this:
+
+    package MyCorp::ProductDatabase;
+    use base 'Apache::MVC';
+    __PACKAGE__->set_database("dbi:mysql:products");
+