Re: [cgiapp] Splitting large projects.

[John Day <suppressed>]

At 01:31 PM 4/8/2004, Sam Tregar wrote:

I have downloaded Krang, but man, that thing is daunting! I will have a good look at it.

So what I get from you and the others here is that I could:

1.. Take CGI::A, subclass it with  a pile of utility functions or modules then call it BaseApp

2.. Take BaseApp.pm and subclass it, adding a bundle of run mode code and coming up with MyApp1.pm, this would inherit all the stuff from CGI::A and BaseApp and has its run-mode methods in it.

3.. For each MyApp module we then create a simple instance script that instantiates the MyAppX.pm via its inherited new method.

So adding something to the BaseApp.pm module adds it to everything else and the run mode selection is handled easily by redirection or form actions. Each MyAppX.pm module could even provide its own sub-menu information - the top level menu functions being hard coded to point to the various MyAppX.pm modules.

OK, I think I am understanding this, from what I have said, does it appear to you like I am understanding?

John


>You might be interested in looking at Krang, perhaps the largest
>open-source CGI::App project:
>
>  http://krang.sf.net
>
>Krang divides its UI into multiple separate web apps, each with their
>own CGI::App sub-class and .pl script.  These modules all use the
>underlying core API modules to interact with the database, access
>configuration and share functionality.  When one app needs to transfer
>control to another all they do so via redirects or by producing HTML
>forms with their "action" parameter set to the target script.
>
>-sam


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed