yosemite status added.
Merge pull request #134 from vertexclique/patch-1

Yosemite status added.
sqlexport: rewrite "to sql file" export to use streaming
Install icon to hicolor directory
Merge pull request #136 from manisandro/icon

Install icon to hicolor directory
Adjust OSX wording to show 10.6 through to 10.10 work
gitignore: add testdata directory
I18N - Simplified Chinese
Merge pull request #138 from efreeking/patch-2

I18N - Simplified Chinese
i18n: Add Chinese translation to project files
Added 3.4.0 release date
Trivial wording tweak
Updated version in CFBundleVersion to 3.4.99

This reflects it's the development for 3.5.x series.
Updated currentrelease to 3.4.0
Fixed outdated link to Qt website
Show tooltips in DB Structure views

When hovering over an item in the tree views of the Database Structure tab
or DB Schema pane, show a tooltip with the contents of that field.

See issue #139.
Fixed build-essentials → build essential typo

Thanks @WIStudent for pointing out the typo. :smile:
Add initial SQLCipher support

Add some basic initial support for SQLCipher. Note that this is more of
a POC than a final implementation.

This commit adds an option called 'sqlcipher' to the cmake and qmake
projects which - when enabled - replaces the default SQLite3 include and
library files by their SQLCipher counter-parts. Especially on MacOS X
there might be some more work required in finding the correct include
paths. The SQLCipher library supports unencrypted databases, too, so
even if the option is enabled the program behaves like before. You can
see the difference, though, in the About Dialog where the SQLite version
string will say 'SQLCipher version xy'.

When the sqlcipher option is enabled and you try to open a file which is
neither a project file nor a normal SQLite3 database it is assumed now
that the file is an encypted database. There is no way to tell between
an invalid file and an encypted file, so in both cases a password dialog
pops up. When the correct password and page size are entered the file is
opened and can be edited like any other database before.

Creating encrypted databases isn't supported yet. So for testing you
need to fall back to the sqlcipher command line tool.

See issue #12.
cipher: Fix build option and use a dialog for entering the password

Fix the sqlcipher build option in the qmake project to actually enable
the SQLCipher support.

Add a new dialog called CipherDialog which is used to ask the user for
the password and other encryption details instead of using standard Qt
input dialogs.