Skip to main content

About this blog and the writer

I should knock down the barriers and finally put some content to this blog. I intend to make this as my technology biased blog partly as a reminder for myself about things and problems I've encountered and hopefully also solved.

About me... I'm Finnish information technology science student currently writing my masters thesis about web site usability. To be exact I'm doing research about usability of Ajax based web applications. My intention is to get some data if much hyped myth that Ajax applications have better usability have actually some ground in it. My research application is Plone web CMS (Content Management System) which is probably best open source web CMS currently available.

Reasons for me picking this certain web application is my backgrounds as a Plone developer in University of Jyväskylä. I've been working with Plone since Autumn 2006 and in that time I've managed to do quite a few things with Plone from translating ready products to developing new ones. Products in Plone are basicly different containers for different types of publications (eg. News, Events etc.) which have specific content, workflows and views. Since Plone 3.0 Plone got some more Ajax-stuff behind it which makes it perfect research application for me. University of Jyväskylä is using currently Plone 2.5 which isn't using heavily any Ajax-stuff. This makes them a perfect usability comparsion target for my research.

Well that's about my masters thesis. I'm going to use this blog for posting stuff about stuff I encounter in my work and hobbies. It may be about Plone, but also about other web technologies or programming as well. Or just about latest TV-show I've seen.

Now I'm going to go back to my masters thesis. Good byebyes!

Popular posts from this blog

Domain name registration through Google - when things go wrong.

Not too many people know, that you can register new domains through Google. This can be done when you're registering for Google Apps Standard Edition which is free and somewhat stripped version of their Google Apps Premium Edition. Latter one is tailored more to suit business needs.

With $10/year prize tag it's not cheapest option, but you'll get "private domain registration to protect against spam at no extra cost, full DNS control and domain management, automatically configured to work with Google services, email, calendar, instant messaging, web pages and more also at no extra charge".

As a comparsion GoDaddy offers .org domains at $14.99/year so it's actually not that bad offer. Google actually is just collecting the data and sending it to their partners (godaddy, enome) which does the registration. I decided to give it a try at January 11th. To my big surprise things didn't went that smoothly. It's been now one week since my order - the domain I …

Plone 4, ZEO and supervisor

This post belongs also to the "lessons learned" category.

With Plone 3, ZEO and supervisor combination you've probably configured your supervisor to start plone instances by running $BUILDOUT/parts/client1/bin/runzope.

Problem is that with Plone 4 your $BUILDOUT/parts/client folder doesn't contain anything else than etc folder. You know starting instances by targeting supervisor to use $BUILDOUT/bin/client1 fg doesn't work like you'd expect (supervisor would control the client1 script - not the actual plone process).

My colleague Jussi Talaskivi figured that using 'console' argument instead of 'fg' for bin/client1 script should do the trick. With 'console' argument stopping, starting and restarting Plone 4 instances with supervisor works like a charm.

Below is full example of working supervisor configuration.

[buildout] parts = supervisor [supervisor] recipe = collective.recipe.supervisor port = 8200 user = xxxx password = xxxx pr…

cd under development packages nested folders without repeating yourself

To me Plone development environment means Fedora 12, terminator and vim. As I do lots of development in the shell there has been one annoying little thing which I'm tired of - cd:ing under development packages inner structure to where the actual code lives.

Doesn't seem much but if you repeat that many times a day you'll get tired of it. Of course you can always launch vim for the package root and open the file you wanted from there, but it's still extra effort.

Few weeks ago me and my colleague Jussi Talaskivi started to think that there has to be a script which takes you to your destination simply by parsing dotted name and using information from there to cd you to the correct place. After spending some time googling around we found none. Annoyed by this we decided to do this missing script by ourself.

Soon it turned out that this wasn't that easy task as it sounds - simple shell or python script where you just parse correct path from arguments wouldn't do t…