in reply to Re: They do different things! (was Re: 1001 CPAN Template modules)
in thread 1001 CPAN Template modules

I apologize - I have only read bits and pieces on Mason and I remember reading where it describes itself as a CMS. (No, I don't have the citation. Sorry.)

However, your statements help illustrate the basic thrust of my point - Mason isn't a templating system, at its heart. It's an application framework. You write a Mason app, not a Perl webapp. That Mason is in Perl and you can use Perl is kinda secondary. It would be like writing an app in Oracle's AppServer. You'll be using some SQL and PL/SQL, but that's not the main thrust of the thing.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

  • Comment on Re: Re: They do different things! (was Re: 1001 CPAN Template modules)

Replies are listed 'Best First'.
Re: Re: Re: They do different things! (was Re: 1001 CPAN Template modules)
by autarch (Hermit) on Apr 23, 2004 at 05:01 UTC

    I apologize - I have only read bits and pieces on Mason and I remember reading where it describes itself as a CMS. (No, I don't have the citation. Sorry.)

    A long time ago the most interesting free Mason app was "the Mason CMS", which was used at CMP media, where Mason was originally written, IIRC.

    You write a Mason app, not a Perl webapp.

    Sort of. When I write a "Mason app", most of the logic is still in Perl modules. Mason is really just the frontend. It's just that app server bits it has built in make writing these frontends really simple.