Friday, July 2, 2010

Automatically Process Text in CreoleParser

We are using the fantastic CreoleParser in our Knowledge Base and one of the requests was to automatically link text such as "bug #1234" to the bugs DB. Luckily this is fairly simple to do, though I haven't found much documentation on it.

To start, you will need your own dialect object:

from creoleparser import Parser, parse_args
from creoleparser.dialects import creole11_base

from .elements import AutoLink

base = creole11_base(macro_func=macro_func)

class MPDialect(base):
    auto_links = (AutoLink((('mwl', 'mwl[#|:](?P<mwl>\d+)', 
                             ('lwl', 'lwl[#|:](?P<lwl>\d+)', 
                             'MySQL Worklog #%(lwl)s'),
                             ('mybug', 'mybug[#|:](?P<mybug>\d+)',
                              'MySQL Bug #%(mybug)s'),
                             ('lpbug', 'lpbug[#|:](?P<lpbug>\d+)',
                              'Bug #%(lpbug)s'))),)

    def __init__(self, *args, **kwargs):
        super(MPDialect, self).__init__(*args, **kwargs)[self.auto_links])[self.auto_links])

    def inline_elements(self):
        elements = super(MPDialect, self).inline_elements
        return elements

def create_parser(method='html'):
    """Creates a parser customized for projects at Monty Program


    return Parser(MPDialect, method=method)

This is just setting up the dialect, the real work is done in the AutoLink element:

import re

from creoleparser.elements import InlineElement, sanitizer
from genshi import builder as bldr

class AutoLink(InlineElement):
    Used for translating text like bug#45 to a link
    def __init__(self, patterns, tag=''):
        Patterns is a tuple of tuples, with each individual tuple containing
        the following:
            the code for this link, used in the regular expressions, 
                i.e. 'bug'
            the regexp pattern to look for in the content, i.e. 
            the url to link to, in str formatting sentence, i.e.
            the string to use as the title, i.e. 'Bug #%(bug)s'
        self.patterns = patterns
        super(AutoLink, self).__init__(tag=tag,token=None)
        self.regexp = re.compile(self.re_string(), re.IGNORECASE)
    def re_string(self):
        return "|".join([pattern[1] for pattern in self.patterns])

    def _build(self,mo,element_store, environ):
        return bldr.tag.a(self.alias(mo), href=self.href(mo))
    def href(self,mo):
        """Returns the string for the href attribute of the Element."""
        for pattern in self.patterns:
            if[0]) is not None:
                return pattern[2] % mo.groupdict()

    def alias(self,mo):
        """Returns the string for the content of the Element."""
        for pattern in self.patterns:
            if[0]) is not None:
                return pattern[3] % mo.groupdict()

And thats it, creoleparser scans all text for the regular expressions you defined and replaces them with links.

Monday, January 18, 2010

Separating javascript from HTML (and automatically running it)

In the old days I wrote event handlers inline *shudder*, then I was enlightened by jQuery and separated event handlers from HTML. I still had a problem though, most of my javascript was still included in my HTML templates, just in a <script> block, like this:

$(document).ready(function() {
$('div.fancy_widget').click(some function here);
<div class="fancy_widget">
Something fancy that needs to be clicked here

This is better, but still leaves JS mixed in our templates. A common solution is to put all your code in an external JS file (good) and run it for every page. jQuery is fast so for most part this doesn't cause problems but it doesn't seem right to me. Why would I want to try to bind an event to div.fancy_widget if that only appears on a few pages?

This is my solution:
Separate page / widget specific code into individual classes in an external file.


function fancy_widget()

fancy_widget.ready = function()
    $('div.fancy_widget').click(some function here);

In your HTML file, add "fancy_widget" as the class on your body tag:

<body class="fancy_widget">

Run this code snippet (also in external.js)

$(document).ready(function() {
    // check the class of the body and try to execute the prep functions if there is a class defined for that
    $.each($("body").attr('class').split(" "), function() {
        if (this == '') {
        if (eval("typeof " + this) !== "undefined" && eval("typeof " + this + '.ready') == 'function') {
            eval(this + '.ready()');

This will cause fancy_widget.ready() to be called on any page with a body class of "fancy_widget". I also use this for page specific functionality.

I am sure this can be improved and extended but though I would go ahead and publish it.

Friday, October 30, 2009

Tweaking ModelForms in django

I try to use a lot of ModelForms in django, it makes things simple and keeps information in once place. However, sometimes I need to change one property of a field. The docs just suggest you define the field again in the form but this means you have to redefine all aspects of the field. Here is an easier way:

class ProfileForm(forms.ModelForm):

def __init__(self, *args, **kwargs):
super(ProfileForm, self).__init__(*args, **kwargs)

self.fields['details'].widget.attrs['cols'] = 100;
self.fields['details'].widget.attrs['rows'] = 12;

Saturday, August 22, 2009

MP Team meeting in Majorca

So a few weeks back my company had our first company meeting in beautiful Majorca Spain. Even though this is a resort location we worked hard planning the future of MariaDB. One great thing about working for an open company is almost everything we do can be put on our public wiki. You might especially be interested in our MariaDB's release plan.

Since I am not a MariaDB dev, my responsibility is to get our website ready for the GA as well as work for the Open Database Alliance. I decided to use django for the new ODBA site which has given me a chance to learn python and use framework instead of re-inventing the wheel. Once I finish the project I will writeup my thoughts on django as I decide if I want to use it for other projects.

Thursday, August 13, 2009


This has been mentioned all over but for some reason I still made the same mistake everyone else did.

When setting up a user profile in django, the value for AUTH_PROFILE_MODULE should just be the application name then the name of the model. For example, my project's name is "foo", the application is "bar" and the model is UserProfile. It made sense for me to put:

That gave me a "too many values to unpack error". The proper value is
AUTH_PROFILE_MODULE = 'bar.UserProfile'

Hopefully this helps someone out, maybe just me in a few months when I forget what I did.

Wednesday, August 5, 2009


I have been meaning to start blogging for a while but never made the time for it while working at MySQL / Sun. Now that I am at Monty Program AB I am making time to share my random thoughts about technology, especially web applications and MySQL / MariaDB.

I was at MySQL (then Sun) for 5 years, during that time my primary responsibility was providing tools for the excellent support team, primarily Eventum but also other internal items. My team also developed the MySQL Network portal (since rebranded to MySQL Enterprise. My co-workers were great and I liked what I did but after the Sun acquisition I saw things changing and based on the number of colleagues who left ahead of me I wasn't the only one.

In May of 2009 I left Sun and returned to startup culture, working with Monty at his new company Monty Program AB as Lead Web Developer. In such a small company there are a ton of different things to do and so far I have not been bored, always a new project to tackle and best of all I feel I make a difference.

I probably will not be a prolific blogger (I actually want to get real work done) but when I start rambling it will generally be on my work here at MPAB or web development in general.