fix for issue #13

On Tue, Jul 15, 2014, at 00:48, Mateusz Mikołajczyk wrote:
> > @@ -193,6 +193,9 @@ CalamaresApplication::onPluginsReady()
> >               this, &CalamaresApplication::startPhase );
> >  
> >      startPhase( Calamares::Prepare );
> > +    m_mainwindow->move(
> > +        this->desktop()->availableGeometry().center() - m_mainwindow->rect().center()
> 
> i'll try to remember that.. but i believe it's just the matter of
> personal taste - for me, the missing 'this' raises an eyebrow exactly the
> same way as for you the existing 'this' does.

I fully agree with you it is all about personal taste, but in the end
consistency is more important than satisfying personal tastes. This is
why I force myself to use Calamares coding style (and you are more than
welcome to point out places where I fail to do so :))

If we don't enforce consistency, then reading code is harder (this call
is prefixed with "this->" so it's a member method, this other one is
not, is it a top-level function or a member method for which the author
did not care about adding the "this->" prefix?) and contribute code is
harder as well (this method uses spaces inside parenthesis, this other
one does not, how should I write my calls?)