|There's more than one way to do things|
Re: Existing webapp on which to build?by dash2 (Hermit)
|on May 27, 2003 at 18:14 UTC||Need Help??|
For a full-featured Content Management System, try Bricolage (search google). Or maybe, for user registration Slashcode?
But it sounds like you really want just user registration, login and logout, plus some custom database stuff. The danger of going with a full-fledged system is that you have to learn the system, which can take as long as just writing the code - especially if the code is fairly simple. Also, you add another layer, which means that you want to make very sure that whatever you choose is 100% reliable, and very well documented. (Debugging your own code is boring enough without having to debug other people's code.)
For user registration, maybe build it with CGI::Session? You could also use User::Identity but I haven't played with it, and maybe it looks too complex for this stuff. Alternatively, you could integrate it with Apache authentication (check out the Apache:: namespace on CPAN).
For the database stuff, recommend a database object layer such as Class::DBI or Tangram. This will mean less SQL for him to write. I haven't seen PHP that can do that. (Except when I've written it :o)
I believe GD::Graph has great modules for generating graphs using the GD image library. PHP can generate images, but bewarned that there are problems using recent versions of GD unless you have an up-to-date PHP (like 4.2 or better).
And for generating HTML, there are loads of solutions. If he's naturally a programmer, just CGI would be fine, but if he likes to write HTML, then there's HTML::Template and Template::Toolkit. Mason is also good, but is rather heavyweight and more for use with mod_perl... I imagine this is more of a CGI job.