Do not create uninstall shortcut in start menu

According to Microsoft Design guidelines (http://msdn.microsoft.com/en-us/library/windows/desktop/aa511447.aspx) no icons for uninstallers should be created.

Signed-off-by: Sven Strickroth <email@cs-ware.de>
Do not create folder for single link

Signed-off-by: Sven Strickroth <email@cs-ware.de>
Some database code cleanups.
Made transaction management a bit more transparent. Some fixes.
Enable the overall file count in progress again.
[tx-robot] updated from transifex
[tx-robot] updated from transifex
Make sure all queries are initialized on our database object.

Since we use a database with the non default name, we need to do that,
otherwise the query is initialized on the default db which is not open
in our case.
Handle changing source file in upload correctly.

Delete the file on the server if the source file is new, but
the source did not arrive completely within a timespan.
[tx-robot] updated from transifex
Refresh the Protocol widget when the dialog is raised.
Do not show an error message if user aborted. Also CSYNC_STATUS fixes.
Do not display error messages if user aborts the sync run.
Handle SoftError and show blacklisted files.
Build on OS X
Merge pull request #1165 from csware/startmenu-according-to-ms-guidelines

Startmenu according to ms guidelines
Fix some SQL error and warning

Such as:
 Error opening the db:  "Driver not loaded Driver not loaded"
or
 QSqlDatabasePrivate::removeDatabase: connection '...' is still in use, all queries will cease to wor

We need to clear the QSqlDatabase _db handle before calling removeDatabase.
And we also need to give a different name to different folder database, just to be sure
Fix mutex usage in the journal

All public function must lock the mutex. And therefore none of the journal
function may call public function because the mutex is already locked.

So have a public commit that lock the mutex,  and a private  commitInternal
that assume the mutex is locked
Disable quota polling when default account does not exist or is offline
Query credentials when needed. Put the account offline if user aborts.

This is only implemented for HTTP auth. Shibboleth still does its own thing.