Re^3: Extending HTML::Template, how to do it?

in reply to Re^2: Extending HTML::Template, how to do it?
in thread Extending HTML::Template, how to do it?

Honestly if you're interested in frameworks, then you should really look at what's happening in the CGI::Application world at this time. It has a new plugin/callback system and if you look at CPAN you'll see lots of new plugins including one for session integration.

And if those aren't enough for you, there is a soon to be arriving CGI::Application::Framework. And if that still isn't enough for you, I'd look at Catalyst.

-- More people are killed every year by pigs than by sharks, which shows you how good we are at evaluating risk. -- Bruce Schneier

Comment on Re^3: Extending HTML::Template, how to do it?

Replies are listed 'Best First'.
Re^4: Extending HTML::Template, how to do it? by techcode (Hermit) on Jun 17, 2005 at 13:47 UTC
Yeah! As it seems CGI::Application was updated just few days ago - didnt know that. But still, there are things (allready mentioned) that I simply dont like on CGI::Application, and some things that I miss (that "plugin" or however you want to call it possibility). Eventialy, what I want to do. Create a plugin, it will be (use base/ISA) child of my mai<bn module so that I could use it's data (configs, db connections ...etc). And then be able to put simple tag to call that plugin in any template on my site (since everything goes over CGI::App) To be precise, all requests except for graphic/css/similar, are processed by mod_rewrite and call index.cgi (yeah only one). Based on parameters, my main module derived from CGI::App calls specified modules. All works great, but it's not soo good as I hope. I simply want more integration that more screens in one place. Basicly I want whole site, in central unit that does specific things (auth for instance) and then call on itself the rest of the code from specific modules/sections. As it turned out I actualy faked OOP by passing $self as first param. And as I said, everything is working, but not as easy to maintan as I would like For instance: (code included here) Read more... (8 kB) OK it's probably partialy my fault as I was only starting with OOP when I wrote that but still ... Any ideas of how do acomplish something like this, but in a more elegant way?	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: Extending HTML::Template, how to do it?
by techcode (Hermit) on Jun 17, 2005 at 13:47 UTC

Yeah! As it seems CGI::Application was updated just few days ago - didnt know that.

But still, there are things (allready mentioned) that I simply dont like on CGI::Application, and some things that I miss (that "plugin" or however you want to call it possibility).

Eventialy, what I want to do. Create a plugin, it will be (use base/ISA) child of my mai<bn module so that I could use it's data (configs, db connections ...etc). And then be able to put simple tag to call that plugin in any template on my site (since everything goes over CGI::App)

To be precise, all requests except for graphic/css/similar, are processed by mod_rewrite and call index.cgi (yeah only one). Based on parameters, my main module derived from CGI::App calls specified modules. All works great, but it's not soo good as I hope.

I simply want more integration that more screens in one place. Basicly I want whole site, in central unit that does specific things (auth for instance) and then call on itself the rest of the code from specific modules/sections.

As it turned out I actualy faked OOP by passing $self as first param. And as I said, everything is working, but not as easy to maintan as I would like