mdietrich at cpan
May 31, 2009, 9:06 AM
Views: 975
Permalink
|
|
Best practice: How to build app parts reusable?
|
|
Hi,
in one of my Catalyst apps I'm building application parts that I want
to reuse in other Catalyst apps where possible. What's the best
practice to do that? I mean the complete parts from controller, to
model, DBIC schema classes and templates.
Let's assume one part is a guestbook (no, it's not but it's a funny
example ;)). The integration of the controller class is very easy. I
just would build a new controller inside the app which uses the
guestbook controller as base class and sets the correct namespace,
where the guestbook should appear. A similar procedure would get me
the model and schemes into my app, but it requires a wrapper class for
each class the guestbook brings with. And the templates? The only
way I know of is to copy and paste them into the 'root' folder of the
app.
There has to be a better way. But which?
I'm also thinking about whole reusable applications. For example a
shopping system which can be extended and modified by overwriting
methods while the base system can be upgraded seamlessly. (I know
MojoMojo as a standalone Catalyst app, but it's only standalone and
not to be extended locally.)
matt
--
rainboxx Matthias Dietrich
Freier Software Engineer
rainboxx | Tel.: +49 (0) 151 / 50 60 78 64
Tölzer Str. 19 | Mail: matt[at]rainboxx.de
70372 Stuttgart | WWW : http://www.rainboxx.de
XING: https://www.xing.com/profile/Matthias_Dietrich18
GULP: http://www.gulp.de/profil/rainboxx.html
|
PGP.sig
Best practice: How to build app parts reusable?
