Flyspeed 3 under Wine

Avatar
  • updated
  • Completed
Hi

I have been using Flyspeed on Linux running on Wine for some time now and it has always worked very well.However, with the upgrade to version 3.0.0.2, Flyspeed became impossibly slow and since 3.0.0.3 it crashes on startup.
I realise that having Flyspeed run in a non-Microsoft environment is unlikely to be a priority for ActiveDBSoft, but if there is a relatively simple solution it would be great for those of us who prefer Linux to be able to continue using it.
Alternatively, maybe it could be ported to Java and everyone could use it? :-)
Avatar
Anonymous
Hello, Gian. 

Thank you for your feedback.

We will fix the crash in the next version. 

Unfortunately we have no experience in wine, so we failed to run it under wine. Do you have any clue on how to run the tool there? 
Avatar
Gian van der Spuy
Running under Wine does not require anything special. Once Wine is installed (from the package manager - I'm running Kubuntu), Flyspeed can be installed exactly as it would be on Windows. Just click/double-click on the installer and Wine does the rest.
Avatar
Anonymous
Hello, 

Then problem is fixed in the new version.
Avatar
Gian van der Spuy
Just tried it out. Worked perfectly! Thanks so much.

I did notice that queries still take a while to run. This may be related to the fact that I'm connecting via SSH tunneling. I've noticed that it takes a while for connections to open initially (caused by issues with our network). However, once a connection was open, queries used to run instantly. Now there is a lag. Has something changed in the way a query is run? Does running a query reconnect to the server?
Avatar
Anonymous
Hello,

You right. Since version 3 we open a separate connection for each query window. It is not possible to turn off this feature. You can switch to the previous verison (2.10.1.8) for now. We will investigate the possibility to turn it off.
Avatar
Anonymous
Hello.

We released the new version 3.2.1.1. In this version we've got rid of unnecessary re-establishment of database connections, so performance should be much better now. Let me know if it's not the case.