I am perhaps a little biased, but I think that CGI::Path handles path-based applications rather well. And yes, the docs aren't the best. It is rather mature in-house, but hasn't really caught on out of house. Millions of dollars have gone through applications built on CGI::Path and its predecessor if that means anything.
I would like to get the docs up a bit, would like to have some out of house folks start to implement it, and I think those two goals could work together. Earl > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:templates- > [EMAIL PROTECTED] > Sent: Wednesday, March 02, 2005 5:03 AM > To: Stephen Quinney > Cc: [email protected] > Subject: Re: [Templates] CGI::Prototype examples? > > >>>>> "Stephen" == Stephen Quinney <[EMAIL PROTECTED] > services.oxford.ac.uk> writes: > > Stephen> I hope this isn't too off-topic, I've not found anywhere more > Stephen> appropriate so here goes. I really like the MVC approach for > website > Stephen> design, I reckon I've sorted out the Model (Class::DBI) and the > View > Stephen> (Template Toolkit) but I've still not got a controller system > with > Stephen> which I'm really happy. It looks to me that CGI::Prototype could > be a > Stephen> good fit with the approach I'm looking for but there's not a lot > of > Stephen> helpful documentation/examples around. Is there anyone using this > Stephen> module who is willing to share the code so I can get a good idea > of > Stephen> how it actually works? > > I'm working intensely with the $client this week that is doing > the most active development with CGI::Prototype. I'm even presenting > a one-hour talk on it at a PerlMongers meeting tomorrow. > > I expect a new release of CGIP with more examples and better docs > within two weeks, and I'll see about putting my talk online as well. > > Also, I'm getting funded to write CGI::Prototype::Pathinfo, which > maintains state through extended paths, rather than hidden fields. > Should be pretty interesting. > > The $client is very pleased so far... controller code is getting > reused across multiple related projects, and CGIP has just exactly the > right abstractions and hoks for them. View code (templates) are also > getting reused, although they're just starting to figure that out. > > -- > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 > 0095 > <[email protected]> <URL:http://www.stonehenge.com/merlyn/> > Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. > See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl > training! > > _______________________________________________ > templates mailing list > [email protected] > http://lists.template-toolkit.org/mailman/listinfo/templates _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
