Give conversation windows sense of time

This is a feature I missed, so here is my approach to include timestamps in chat windows. I have to admit that I like timestamps on every message so I shamelessly implemented that first (it was the easiest, too). But it is disabled by default, it can be activated in Preferences -> General. The default behaviour is:
 - Add a date/time separator whenever a new conversation is started or one hour has passed since the last exchange of messages. This uses the separator which is shown when the chat partner is offline. When a new conversation is started and the partner is offline this text is still shown.
 - I liked the idead of @obvio171 so one can double click a bubble to see the timestamp of the message. This might be a little tricky, because you have to click the bubble not the text in it. This is because if you include the MouseArea on top of the text the text can't be selected anymore (while writing these lines I'm thinking a tool tip on mouse over might be a better solution).

Here are a few examples:

Default behaviour on Xubuntu with locale set to en_US. Bubble 2 got double clicked
![screenshot - 10222014 - 01 01 53 am](https://cloud.githubusercontent.com/assets/6523647/4732752/3be04daa-59c0-11e4-88e9-10e60f5864b8.png)

Default behaviour on Xubuntu with locale set to de_DE. Bubble 2 got double clicked, partner went offline before sending message 2.
![screenshot - 22 10 2014 - 10 03 28](https://cloud.githubusercontent.com/assets/6523647/4732914/15af1830-59c2-11e4-9ecf-3b07e866f766.png)

Default behaviour on Windows with threshold set to a few seconds.
![unbenannt2](https://cloud.githubusercontent.com/assets/6523647/4732980/047dcec0-59c3-11e4-8401-26cfbeb3df18.png)

Same window with 'show timestamp on every chat message' activated
![unbenannt](https://cloud.githubusercontent.com/assets/6523647/4732981/04866652-59c3-11e4-9737-ca64f6ac90a0.png)

What do you think?
What's the purpose of the || false?

Aside from seeming to be unrelated to this change, the alwaysOpenBrowser var should always have a value, either true or false. By turning this from a simple data binding into an expression, you remove the ability for the engine to easily optimize the binding by just connecting to alwaysOpenBrowser's change signal, and force it to evaluate it as a javascript expression