[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cgiapp] Re: Wiki as "Best practices" of CGI::App


In article <suppressed>, Peter Masiar wrote:
> Hi list,
> 
> There was a proposal couple months ago on this list to create
> a CGI::App based wiki as example of "best practices".
> 
> And it was me who voted against it, suggesting instead to join development
> of very good and mature wiki clone Twiki (at Twiki.org).

Peter,

I like wiki's, am impressed by Twiki, and like the idea of more "best
practices" CGI::Apps available as open source. So I support this
project. However, I want to spend my own spare cycles turning Cascade
[1] into such an application. It's already written and working as a
CGI::App, but I'd like to make some big changes:

 1. http://summersault.com/software/cascade

 - All pages become valid XHTML
 - mimimize or elimiate use of global variables
 - move from one instance script and a mega module to
 	more instance scripts with smaller, hopefully more re-usable
	functions.
 - Switch to CGI::Session for session handling
 - use Data::FormValidators new validation features
 - use new OO image upload module (recently mentioned here)
 - better MVC design
 - possibly use mod_auth_pg 
 - better error handling / logging, possibly with Log::Log4Perl
 - better testing practices, using Test::More, WWW::Mechanize,
     Test::DatabaseRow...and friends. 

But we don't need to complete. I woud love to see your project get going
so I can see examples of best practices in action, and possibly
contribute as a beta tester.

	Mark
 
--
http://mark.stosberg.com/ 


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed


Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.