I've finally started writing the documentation I've been threatening
to. I've put the draft pod up on the wiki at
http://maypole.perl.org/?ManualCookBookTrainingWheels . I would
appreciate comments re errors and omissions.
Part of the purpose of this is for me to understand how to use Maypole
more effectively, and for me to work out what I'm doing wrong.
Hopefully this will also assist others. It's also an opportunity for
those of you who are more perl-apache-mvc literate than me to gain an
insight into a non-guru's thought processes, so while some of it
repeats from elsewhere, I think it's useful, in that it demonstrates
how to think about maypole for neophytes.
I also need some help with the following if possible:
1.
Structuring your code.
...
The standard BeerDB contains four tables: beer, brewery, pub
and
style. Each of these tables has an associated class which are
BeerDB::Beer, BeerDB::Brewery, BeerDB::Pub, BeerDB::Style.
Although
this is a simple database, and Maypole works well, out of the
box
with the BeerDB, it's worth separating out each class into
separate
files.
So, if we've got BeerDB.pm in /usr/local/src/beer/lib, we can
create
a directory called BeerDB, and then create the files Beer.pm,
Brewery.pm, Pub.pm and Style.pm under this directory.
[Help - can't work out how to do this properly!]
2.
Over-riding search methods.
[At this stage, I really don't know how to do this.] - One example
would be for providing for full text search within a table.
Cheers for now
kd
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Maypole-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-users
