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

use Perl Log In

Log In

[ Create a new account ]

Matts (1087)

  (email not shown publicly)

I work for MessageLabs [] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.

Journal of Matts (1087)

Friday August 04, 2006
03:56 PM

AxKit2 Status: XPathScript, gallery

[ #30531 ]

Things are going really well with AxKit2. I got XPathScript working thanks to a patch from Yanick Champoux. And I spent a couple of days porting AxKit::App::Gallery.

This would have taken me less time but I wanted to try and get rid of the XPathScript in AxAppGallery because it's rather verbose, slows things down a bit, and I thought it could be done a bit simpler under AxKit2 (this wasn't possible under AxKit1). I was right.

The gallery code is now pretty verbose, and I think it could be slimmed down a fair bit, or at least cleaned up, but I think it's great that we can ship AxKit2 with a working application that almost everyone will appreciate.

It got me thinking - everyone likes apps. So we should ship with a few to show people how things work, but also to get people to hit the ground running. So I'm thinking of the following apps to ship:

- A gallery (done)
- A wiki (port of AxKit::XSP::Wiki)
- A blog

If anyone else has ideas of what might be cool "standard" apps, let me know. What do people build first when they get their hands on a new technology?

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.
  • I've of course have AxKit 1.x taglibs and a small cart demo in Handel. Depending on what needs to happen for an upgrade to AxKit2, I should be able whip up something without much doom and gloom.
    • The simple summary is that you no longer write config directives - you write a plugin. A simple example plugin would be:

      sub hook_xmlresponse {
        my ($self, $input) = @_;
        return OK, $input->transform(XSP => XSLT('/path/to/style1.xsl'));

      This way you control how the transformation happens with perl rather than with config directives. You also have to do caching yourself. The reason being that caching was one of the most complicated parts of the AxKit code, and it didn't always get it right,

  • When you say "blog", does that include comments? Most blogs do allow comments, though the message list is usually flat, not threaded. I'd prefer threads myself.

    Furthermore... you can take features as you can see on Perlmonks/Everything as an example. For example: polls.

    And a feed system to generate RSS would be nice, too.