Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Bricolage (Score:3, Interesting)

    I must admit, bricolage looks really quite cool.

    What I cannot seem to find anywhere though is what itch got scratched in writing this thing? Whose site is the canonical example bricolage site? Are there any "live" sites yet?
    • by drowsy (1798) on 2002.02.26 21:30 (#5167)
      I'm working on a site for launch Real Soon Now.

      I only have time to say that this is scratching a generic CMS itch, in that there are none in perl, and perl professionals spend a great deal of time in other environments because there are end-user apps ready for userland.

      There are good frameworks, to be sure , your axkit is one of them. But this is an app, and as such, I would say that this is "the Cliffs Notes for Mason" to steal a phrase.

      • Re:Bricolage (Score:3, Interesting)

        Thanks for your answer - I wasn't suggesting AxKit was a replacement - it's fundamentally not a CMS - it's a publishing framework with some cool dynamic capabilities. Of course people are building CMS's on top of AxKit, just like they have mason, but nothing has been released yet. And I've been saying for over 2 years now we need a solid CMS for mod_perl users. Thank god you guys wrote one!

        Interesting times ahead ;-)
        • Re:Bricolage (Score:3, Interesting)

          AxKit could probably be used as a "burner" (output engine thingy) for bricolage.

          In other news then I'm looking at using it for and that kind of sites.

            - ask

          -- ask bjoern hansen [], !try; do();

          • That would be great, noting that some people have used Mason has a handler in AxKit!

            For XSLT, I'd rather use AxKit than anything else.

            That said, I would use Bric to manage XML/XPathScript docs (you could use the new SOAP process), and publish to an AxKit server.

            Mason would still be the burner for me. The way autohandlers, etc. work in Mason seem very well suited for the care and feeding of XML/XSL docs.

          • AxKit could probably be used as a "burner" (output engine thingy) for bricolage.

            Personally, I'd like nothing better than to see this happen. I think that Sam did a nice job developing the subclassable burner architecture, and it'd be really cool to see AxKit, XSLT [], EmbPerl, Apache::ASP, and Template Toolkit burners added. It'd make Bricolage the ideal solution for just about any Perl web maven.

            • except this thing with the database support... Wait; who's that guy in the mirror who said he would get MySQL to work? ...?! :-)

                - ask

              -- ask bjoern hansen [], !try; do();