On 11/6/05, Kieren Diment <[EMAIL PROTECTED]> wrote: > 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. >
That is a good write up. It is pretty much my understanding. I agree with CDBI::Loader::Relationship not being real handy for big apps. But then again , I could not even get it to work with a tiny one . A few things.: I could not find Maypole::Login::USC. You must mean Maypole::Plugin::Authentication:.USC. I would drop the Form stuff until the next release that will have a whole new suite of tools. Form handling is broken now anyway since teh CGI::Untaint was updated last Xmas. If you say anything I would say "Use CGI::Untaint 2.43 if you want it to work. " I think when you say methods you mean "actions" . Someone will correct me if I am wrong but In Maypole::Terminology the word "method" means exactly what it does in perl.. The word "action' is a method that is Exported and mapped to a uri somehow. One thing I would suggest is if you are making an app of any size , go ahead and make a custom model class and inherit from whickever of maypole's you desire. This give you a convenient place to add methods. and actions to all classes. Regairding teh "search" and "delete" actions which class with CDBI methods, the best advice is to not use them -- IE: override them to just do what CDBI meant for them to do and unexport them. Then make methods of different name to do search and delete web pages. I'm think everyone on the planet belives that was just a screwed up design. Perhaps it was more proof of concept code to show you could do it if you had to. > 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!] > What problem are you having with this? This is how i do it . I would be explicit about the directory and spell it out. Something like " .. make a directiory called '/usr/local/apaceh2/lib/BeerDB/ . . .' thanks. ------------------------------------------------------- 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
