RE: [cgiapp] Application program structure

["Dimitris Papaharisis" <suppressed>]

Hi Michael and List

I 'd love to see some "core" module and plugin module examples if possible.
The whole plugin architecture of C::A is not 100% clear (at least to me) but
sounds really powerfull. Any different suggested ways to implement plugins?

I m currently using sepparate .cgi's and .pm's for my different modules

> -----Original Message-----
> From: petersm [mailto:suppressed
> Sent: 15 December 2003 17:07
> To: Mike; suppressed
> Subject: Re: [cgiapp] Application program structure
>
>
> The way we do it is to have one .cgi file which uses one CGI::Application
> module with very few (actually only one) run mode. This module
> will look at
> the URL and main site template to decide which other
> CGI::Application modules
> to 'require' and 'run()'. It then puts the output of those
> modules into the
> appropriate places in the outer template. All session management and auth
> takes place in the one .cgi file and it's corresponding module.
> This allows us
> to simplify the functionality of every other module (having maybe 5-10 run
> modes) and for the functionality to be limited in scope. This
> allows us to do
> things like this...
> We want an image gallery utility running in the center of the
> screen. We want
> the navigation bar to be dynamically generated and we also want a
> poll running
> on one side of the screen. We can put the image gallery into one
> module, the
> nav bar into another, and the poll in another. All with their appropriate
> templates. We love this environment and have found that it scales
> very easily,
> gives us lots of resuable code (the plugin modules that we simply
> add to a new
> site with just modifications to the templates, not code) and is
> very easy to
> maintain since everything that is associated is grouped together
> into one module.
> HTH
> Michael
> Venzia
>
> ---------- Original Message -----------
> From: "Mike" <suppressed>
> To: <suppressed>
> Sent: Tue, 16 Dec 2003 02:26:09 +1000
> Subject: [cgiapp] Application program structure
>
> > Hello,
> >
> > I'm in the process of converting my scripts to using
> > CGI::Application.  I have incorporated some of my code into
> > CGI::Application, CGI::Session and HTML::Template format - all of
> > which I think work well together.
> >
> > I just need some clarification as to application structure now.
> > Before moving across to the new format, I had quite a few perl
> > scripts (about 50) each with a few subroutines to do their job. I
> > can easily combine a few scripts to yield a functional module file
> > with the related run modes.
> >
> > My question is: Is it a requirement to have ALL perl scripts in one
> > big application module with one set of (maybe 50 to 100) run modes?
> > I previously was able to redirect to another perl script which
> > performed a different function (from a menu screen), but am having
> > trouble keeping session parameters between different instance
> > scripts (each instance script is started from a particular menu
> > option) using the new format. Is it possible to do it that way, or
> > should there be only one instance script with one application module
> > containing many run modes?
> >
> > Thanks in advance,
> > Mike.
> ------- End of Original Message -------
>
>
> ---------------------------------------------------------------------
> 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
>
>


---------------------------------------------------------------------
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