[homam]

Ritesh, you can check the usability flaws I mentioned in my recent posts, the most glaring of which is the fact that the window close sequence, Ctrl-F4, is right next to the selected statement execution sequences, Ctrl-F5, and it doesn't even warn the user to save their changes. The window just vanishes. This happened to me more often than I care to remember. I probably use SQLyog on a daily basis more often than most users here.

Another one is not being able to select a cell range, or even a single cell, and copy it to the clipboard in an intuitive manner. Another one is not being able to kill the currently executing statemet; SQLyog just freezes up until the statement is finished up (or you kill the connection manually from MySQL Admin). This isn't how I'd characterize a responsive UI.

As for Peter's GUI comment, I disagree. In the MS SQL Server world, you have a GUI, wizard-like tool (Enterprise Manager) where you can mange your tables and to some degree manipulate your data, and you also have a DBA/Developer-oriented tool to write queries, check their execution plans, create indexes, manipulate tables schemas and their data, etc, and that is Query Analyzer. They're different tools, and each has its own valid uses and scenarios. Neither can substitute the other effectively.

Now SQLyog seems to be trying to play both roles, i.e. a GUI, wizard-like tool AND a DBA/Developer SQL DML/DDL tool. That's fine, as long as it strives to be user-friendly to both audiences.

[homam]

In the same vein of using the wrong shortcut keys, I just wanted to add that SQLyog, being a Windows application, should adhere to the basic windows editors' shortcut scheme. For example, in almost all Windows editors, pressing F3 repeats the last find.

SQLyog shouldn't fall short of the intuitive expectation of Windows users by using its own proprietary shortcut scheme.

Yes, I grumble here quite often, but hey, I use it on a daily basis, and if I didn't like it, I wouldn't have bothered suggesting improvement 😉

[homam]

CalEvans wrote on Feb 23 2005, 08:00 PM:

CTRL-F4 is the Windows standard for close existing window.

=C=

I agree, so we should move the “execute current query” shortcut to somewhere else, such as the standard Ctrl-E (this would be great for those of us who use both MySQL and MS SQL simultaneously).

It's also standard to prompt the user to save their changes if Ctrl-F4 was used to close an editor window.

I posted this because, for the second time, I just lost significant changes (including statement execution history times) by inadvertently clicking Ctrl-F4 instead of Ctrl-F5.

It's very frustrating when you're about to execute a query and suddenly the whole window vanishes in a blink 🙂

[homam]

Ritesh wrote on Jan 5 2005, 01:28 AM:

The above feature is planned for SQLyog v4.1. You can expect the first BETA of v4.1 by mid-April 2005.

Thanks Ritesh, that's great!

[Author]

Posts