An interesting thread over at kuro5hin on the tribulations one person had when writing a filter to convert XML documents to LaTeX using XSLT (with examples of how some of the transformations would be handled using Perl or Haskell instead).
My initial reaction when faced with problems such as the one described in this post (lots [...]

This paper sets out to show that XSLT is a true functional language, by implementing 35 of the most common functions that you would encounter in such a language (foldl, map, minimum, sum, sumTree etc)! It’s long (the PDF version is 76 pages) - mostly because of the code: just because XSLT can implement all [...]

I’m trying to learn how to abstract common elements of XSLT away. For example, the MusicDatabase’s shiny new XML output gives the run-length of a CD, or a track on it, in seconds. But, for output, we’d really like to show it as minutes and seconds (i.e. 308 would become 5:08).
This is fairly simple to [...]

I spent most of today trying to integrate AxKit with Template::Toolkit.
Unfortunately there isn’t really a lot of information on this available that I could find. I think most people see them as either/or approaches, rather than complementary. There is a mailing list for the two combined, but it’s fairly quiet - and seems to be [...]

Steve complains that this series hasn’t progressed in a few weeks. The next entry in the series was going to be a look at searching, using Class::DBI::mysql::FullTextSearch. But, when we used it we discovered that DBIx::FullTextSearch (which this uses) just doesn’t scale well. There’s well over 7 million tracks in the Music Database now, [...]

Last week we built the first few pages for The Music Database, to show
how everything hangs together.
Before we delve a little deeper into some more complex pages, we’ll look at cleaning up the HTML.
We left our CD details page looking like this:

[% META browser_title = "CD details" %]

<h1>[% cd.title %]</h1>

[...]

Yesterday we built our first page. Because we had to set up some
database mappings it may have seemed more complicated that it actually
was. If we wanted to add another page today that viewed a CD in a
different way, all we would have to do is add another lined to the
config_info in Site.pm:

sub config_info [...]

We already have a database built of the freedb data (it’s a little out
of date, but we can resync that later). So the basic version of the
first page is fairly simple. We’ll add a page to display the details of
a given CD, and use it as an example of how FireCore works.
To construct our Model [...]

FireCore is much harder to actually set up than it should be. Once it’s all configured for a site it’s wonderful (as we’ll see later), but actually getting to that point is much too complex. There’s a whole range of things that need to be remembered: configuring the database, adding the requisite controls to the [...]

I wrote a few days ago about building systems bottom up. We’re hoping to apply this approach to The Music Database. And we’re going to document our sucesses and failures as we go.
The system we’re using for this is called FireCore. I’ll talk in more detail about it later, but for now I’ve written [...]

keep looking »