-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gui Changes consume too much real estate #115
Comments
While I am not relenting on all the changes [;-)], I have made some changes for the next release which should handle your biggest concerns. In particular, I decreased the font size and tweaked the header so that the overall height is the same as before. In addition, the color is now used to render just the drop shadow and the form icons. The still seems to be enough to make the windows distinctive (even during Alt+Tab) without being overwhelming. The tabs are invisible by default because they serve no use until you run a query. My overall goal is to make the user interface simple and approachable for individuals that are more in the scripting/admin camp who aren't necessarily programmers. In addition, I am trying to balance the use cases of someone who wants to use the import/export functionality right away vs. someone who uses the tool primarily as an AML editor. Hopefully, the new compromise achieves that. |
Hi Eric, the recent theme changes were good, it looks much cleaner now, I really like it now ;-) \Ralf |
Thanks! I appreciate it. On Tue, Jan 12, 2016 at 3:49 AM rneuber1 notifications@github.com wrote:
|
The theme changes introduced by the latest commits change the GUI in a way that makes it harder to use, it is way too "heavy" due to the large, colored title bars etc.
It uses more real estate for the TOC (let alone its header).
It starts up with no tabs visible, you have to run a query for the "Code/Report/Table" tabs to appear.
In general, the previous non-flar design looked more professional and technical (which is the intended audience for such a tool). ;-)
The text was updated successfully, but these errors were encountered: