For a while there have been some commercial tools in this area, such as RefWorks, and EndNote, which seem to be the two most popular choices. These tools allow you to manage your bibliography in a big database, and more importantly, it integrates with Word so you can pull in a reference from your database and it will format it in accordance with some citation style (APA, MLA, etc.) so you don’t have to sit and double-check whether you’ve remembered all the details of your selected/dictated style. Furthermore, these tools allow you to easily grab material from online publication databases such as PubMed, CiteSeer, and many others, so you don’t have to manually write up all the information about each bibliographic item.

While commercial tools are all fine and well, we have actually had this functionality in LaTeX for a long while using BiBTeX. The catch here is, of course, that you need to maintain your BiBTeX database yourself. So, wouldn’t it be nice if we could get both things? An application that can easily fetch bibliography information from the web, something that can integrate with Word for those who need that, something that can export to BiBTeX so it can be readily used with LaTeX, and even something that can help you keep track of where you put all the articles you need for your thesis? And would it hurt if this thing was actually open source? I think not!

Yesterday my fiancée was complaining about managing bibliographies in Word (I have, unfortunately, been unable to persuade her to change to LaTeX exclusively), and as the kind person I am, I immediately put the followship of the ring, extended edition, on pause and went to look for something that’d help her maintain a database of bibliographies. Something which, preferably, is a tad easier and faster to use than BiBTeX. Now, I’m aware of things like pybliographer that gives BiBTeX a more userfriendly exterior, but I was aiming for something a little more userfriendly and more like RefWords and EndNote with integration to Word.

And lo and behold, after a short while of searching, I came upon one of the most nifty extensions to Firefox that I have seen to date: Zotero. This extension integrates your bibliographic database management directly into the application most of us use to find literature with: the browser. As an added bonus it also offers integration with Word, it works across platforms, it’s open source. Basically it fulfills all the needs I listed above to perfection. Count me amazed. I will definitely be using this for myself as well and just export to BiBTeX when I need to cite works from my LaTeX documents.

For the more technically minded of us who have a tendency to prefer our own variations on bibliographies and citations (when we aren’t otherwise bound by journals or other draconian requirements) and thus create our own .bst-styles for BiBTeX, then Zotero uses the Citation Style Language, which is an XML-based format for formatting citations and bibliographies. Lastly, Zotero has been funded and developed by the Center for History and New Media, so this is a tool by the academe for the academe with a commercial tool’s polish. Give it a try today.

van Wyk et al. have developed something called Silver that allows them to specify these extensions using attribute grammars, which is a context-free grammar that has been extended with attributes, semantic rules and conditions. He described how they use forwarding in the attribute grammars to get modularity through refinement of the functionality of the extension.

What this means is that at the core level you could write an extension, say to introduce SQL statements directly in your language, you could introduce using connection select name, address from customers where balance > `balance and have it automatically converted to connection.Execute("select name, address from customers where balance > " + balance). This means at the core level your extension is nothing but a macro in the pre-processing sense.

Given your extension at the core level any error reporting, for instance is forwarded, is forwarded to your generated code. This is where the extension refinement comes in, because if you define the appropriate error reporting extensions to your module you could return better errors. And their framework builds further onto this, also making syntax- and control-flow analysis available using two temporal logics, CTL and LTL-FV. You can read more about temporal logics in Logic in Computer Science by Huth and Ryan.

Everything cannot be bliss, however, as this thing requires that the host language is written with these extensions in mind – that is, it has been written in Silver. van Wyk’s team is working on both a C and Java implementation, but given the sizes of in particular Java, it probably isn’t realistic that they’ll get a full model of Java for this. Another problem is, of course, that writing a full-fledged extension requires the programmer to know about attribute grammars, forwarding, temporal logic and a lot of other nitty gritty things. So, get ready to hire me or someone like me.

On a more realistic note I think the ramifications of having support for this in a language are huge as you can customise your language on the basis of your needs very easily. But I don’t think it will be feasible until the day that these extensions become easier to write. Until then I’m afraid it will remain an academic exercise, but here’s to hoping.

One of my courses at DIKU has been on scripting- and domain specific languages, in particular how we can use them to solve recurring problems, when we develop them, and a long range of presentations on different languages and the problems they try to solve. This course is (/was) a seminar course, which means that students are meant to participate in the lecturing by giving one or more presentations. For this course we are (/were) meant to give two presentations each.

The last paragraph was, of course, the world’s best thought-out foreshadowing of getting to the point where I talk about what I talked about. Catchy, right?

My first presentation, and in my opinion the better rehearsed of the two, was on using the .NET framework as a platform for embedding scripting languages and creating domain specific languages for web-based pipelines. The .NET framework is indeed superb for doing these things, but not superb in the way that C is superb for it, nay, superb in the way that everything is easy and doesn’t require a lot of code. But if you do not believe me, you can look at the slides for yourself.

The second presentation was on domain specific languages for specifying illustrations. Now many people may ask why on Earth we would need something like that, when we can just draw stuff in Adobe Illustrator or equivalent. However, Illustrator does not lend itself kindly to automatically (meaning programatically) generating large-scale visualisations of systems. We could, for instance, visualise the internet using a program. We could visualise the order of page visits made by website visitors, and many other things. One of my great interests is typography and keeping fonts consistent between documents and illustrations and whatnot, but the presentation only touched briefly on this. In the presentation I discussed GraphViz, METAPOST and TikZ/PGF. The slides are available here.

This brings me to the second part (or third, depending on how you count) of this post: reactions. I have been teaching in different contexts over the past decade (God is it that long already). I have taught high school students maths, I have tutored grade school pupils in maths, I have given lectures on error handling methodologies for corporations, I have taught employees advanced/new programming methodologies in corporations, but this was my first real, terrifying encounter with presenting for the academe. But presenting here is different.

Lansky does portray the situation fairly well, except there isn’t a lot of taking notes in this course. Reflecting on it, however, I can see how right he is. We hardly ever react to any of the witticisms, puns or great revelations. We just sit there and try to embrace it all, catalogue it, connect it to existing material and just not fall behind in keeping up with the new information that is presented. We simply do not have time to pick up the small off-remarks that are meant to liven up the crowd. But God it’s frustrating when you’re the speaker as you haven’t got the vaguest inkling of whether the crowd is bored witless of what you’re saying, or whether it’s the coolest thing they’ve heard of since sliced bread. I have since received word from a couple of people that at least parts of my presentations were interesting, so that is something, at least.

There are, however, a few pointers I’d like to share with other people who are going to be presenting to the academe. Not so much pointers that I give because I have now done presenting to this particular crowd, but pointers that I have come to understand as part of listening to presentations daily for almost seven years in this world. The points are fairly simple: know your material, know it really well, rehearse before you speak, and rehearse multiple times before you speak, and lastly, make sure that your slides support your talk. Your slides should not be your talk. It is not interesting to have slides read aloud to you. Dazzle us with your message, use slides to underline your points, illustrate the key topics. If you wish to learn more about good presentation methods, I will warmly recommend Garr Reynold’s blog on professional presentation design: Presentation Zen. He has a lot of interesting ideas, but I believe a lot of them a better suited for product pitches, broad overviews and the like. Presenting a programming language will need more stuff on the slide, but there are still things to be learned. If you look at my slides you will see that I in particular do not honour his No more bullet points mantra. I happen to like a small number of bullet points to underline my message. But like humans then no two presentations are created alike.

Before I get overly philosophical, let us derail the discussion to the third (or fourth) and last part of my post: cool gadgets for doing presentations. If you’ve stuck with me this far then I will present to you: Trust Wireless Presenter TK-3300p.

The presenter functions as a wireless trackball mouse with dedicated buttons for page up and page down and it comes with a nifty red laser pointer. I used it for my second presentation and the flow of the presentation became a lot better than when I had to walk back and forth between the computer to change slides. The Trust presenter is fairly inexpensive, so even if you only have a small number of presentations each year, I will warmly recommend it as it makes your presentation just that much more well-connected, and it gives a better impression on your audience. Plus, of course, you aren’t interrupted every time you have to move to the computer. And, of course, it still has the cool gadget factor. The presenter is placed next to my Creative MuVo memory stick so you can compare size. The presenter is placed very nicely in your hand and it contains a left mouse button underneath that is operated with your index finger. The three top buttons can be a bit tricky to get right all the time, but with a bit of practice it is fairly easy. Alright, enough product placement and endorsement for one post, and back to my paper for me. More on that in a later post (I hope).