MySQL Workbench progress update on Linux port

As you probably know, or at least heard, we are currently porting Workbench to Linux. Generally speaking the porting process is split in several stages. The first one is to compile non-GUI Back-End which represents about 80% of the total application code. The next stage is to ensure that unit-tests are run correctly for the ported stuff. The third is to create user interface and to bind it to the back-end/core. After that we will have alpha version of Workbench for Linux.
Regarding tests, actually a portion of unit-tests are already passed. These are 121 of 122 going well. At the moment we are working on non-GUI back-end, and core part is compiled and run, so now the modules and plugins are in progress. I must admit that process of porting is pretty smooth, most of the code has already been prepared with Linux/OS X ports in mind. I will be posting our progress on the porting efforts frequently, please keep checking our blog.

7 thoughts on “MySQL Workbench progress update on Linux port”

  1. Hey its good to hear that you work heavily on getting MWB to other systems out there – but please don’t forget the buglist in the meantime. I just bought the standard edition today and while the software is nice there are some bugs driving me nuts! So gotta go to your bugtracker now and start submitting..

  2. rafsoaken, we hear you. Please make sure to file everything you find so we can fix it. We are currently working on the next release build which should be online the next days. Bug fixing is straight forward so if you do the bug reporting, we will do the fixing, fast.

    Patrik, one problem with Qt is the licensing. Another is the fact that we want a native experience on each platform. The porting process is only heavy one time. Once we have the back-end to compile on Linux, we should be ok on Mac and Solaris. Then comes the UI port. After the WB 5.1 release we are going to keep all platforms in sync.

  3. Are there any plans to make MySQL source-available to build on other platforms such as, oh, say, NetBSD and/or MacOS X (Leopard)?

  4. As soon as we have our code compiling on Linux we will release it as source tar ball. This should work on NetBSD as well.

    We are also working on a native OS X port. But that requires more efforts because we have to implement the UI using Cocoa which is quite different to the .Net UI and GTKmm.

  5. mzinner, actual Qt licensing is very similar to MySQL ones, you are both using a dual licensing model which permits both commercial and free softwares. Even Trolltech compares their business model to MySQL ones:

    From :

    “Trolltech, along with companies like MySQL and Sleepycat, uses a business model for its desktop developer tools unit called Dual Licensing. The Dual Licensing business model allows software companies to provide their products for two distinct uses – commercial and open source software development.”

    It sounds more than MySQL GUI developers were more comfortable/skilled with GTK+ than with Qt 4 which is an argument I would understand. But technically speaking, Qt 4 was IMHO probably a better choice.

  6. These are really good news for Linux!
    enthusiasts and was one of the cons of using Linux for me.
    Thanks a lot!!!

Comments are closed.