Simplify default UI? #2307
Comments
|
My impression is that the immediate needs could be addressed by having an "education" default settings profile. The unneeded tabs/settings could be disabled in a redistributable DB4S settings file that IT department/maintainer can install with the program on student workstations. If there are aspects of DB4S that are not controllable via settings, we can re-visit the matter and try to work towards an accommodation or long-term solution. |
|
xplorer2 (file manager - https://www.zabkat.com/) has the concept of 'layouts' and when first installed, you specify if you want 'beginner' or the 'advanced' layout by default. This at least turns off the numerous panes by default, allowing you to paddle in the shallow end rather than drown in icons... ;)
We could have numerous pre-built profiles with various configurations, but also standalone files (.pro files? 😉 ) allowing easy sharing of profiles. We are looking into supporting multiple dock windows (to view tables at once, etc) so once that has been fleshed out, this would be a good way of showing that off - "here's a layout you can apply to have three tables browsing at the same time....." etc. This is just a suggestion and would take time to implement, but think it would be a good balance between hiding unnecessary dock windows to not scare off beginners, but also allow the advanced features (remote, etc) to be shown when required - a flick of changing a profile. |
|
GitHub desktop has a side panel offering a tutorial. Seems a nice idea.
When you expand a section, it explains what to do with additional links. We could give some details, and link off to the Wiki, for example.
Would be easy to lob this sort of thing in a 'tutorial.db' database so easily updatable. |
|
Good thinking @chrisjlocke. Any interest in taking it on as a project, to kick start your C++ skill development? 😁 |
|
😁 Could be an interesting one! |
|
Saving and loading layouts would be useful, but I'm thinking in a simpler approach, which is straightforward to implement. I would provide a "Simplify Window Layout" menu entry bound to Shift+Alt+0 in addition to the current Reset Window Layout, under a Window Layout, submenu of the View menu. That would hide all the Dock Widgets and the "Edit Pragmas" tab. Additionally, I think it will be useful to add some entries to move the Dock Widgets to the top, left side and bottom, so it is easy to try other window layouts without having to drag and drop all the Dock Widgets. By the way, @justinclift, @chrisjlocke, how should we refer to these "Dock Widgets" in the GUI? I was thinking in menu entries like: "Docks at Bottom", "Docks at Left Side"... but I'm not sure, whether it's correct or understandable for the user. |
I have no idea. Looking at Visual Studio, it refers to Windows, Explorers, Views and Lists, but that's whats /inside/ the dock panels. Hovering over the minimize icon, it refers to Window.
So they're all Windows, but just 'docked' as a status - so not 'docks' as items. I think we can call them whatever the fun we want. ;) |
|
I vote for Platypi and Quokkas |
Hi @scottfurry, Ah, interesting. So in our case, we actually have students installing DB Browser on their own Macs and PCs, so I suspect it might add a non-trivial hurdle for some students if they additionally need to move a settings file into place. Is it perhaps documented where the settings files live on macOS, Windows, and Linux so I could take a look? @chrisjlocke's proposed layouts would be handy, though simply being able to hide all the widgets easily, per @mgrojo's proposal, would suffice for our particular use case! |
|
I agree that the UI can be a bit cumbersome to use. Even just opening a local database to peek "under-the-hood" at the data can be disconcerting if not using DB4S day-in-day-out. I like @chrisjlocke 's idea. |
A new predefined simplified layout has been added with the only the basic functions: schema, browsing and SQL execution. Ideal for courses. Also added options for moving all the docked windows to the bottom, left side or top (for the right, the default can be restored with Reset Window Layout as before). See issue #2307
|
I've just committed the changes for the new Simplify Window Layout and the dock options, which I've named "Dock Windows at Bottom", etc. The saving and loading of the layout can be added in addition to this, if someone wants to contribute the implementation. @dmalan Could you give it a try using tomorrow's nightly build? |
|
The nightly builds have just been rebuilt, including the above new predefined settings change. eg, they're ready for testing |
What am I looking for? I can't see anything on the view menu, or anything different...
|
|
Hmmm, looking at 72ecf14, there should be new menu options:
Just compiled the new code locally on my Linux desktop and tried it. For me they're showing up:
|
|
Looking at the Windows build VM, it seems to have built from the correct things, and latest commit. Not sure why the new options aren't showing there. I've kicked off a new Win64 build now, just to see if something changes... |
|
I did only look at the 32-bit version, but the 64-bit version has the same menu.
Weird... |
|
|
Right is the default, or 'reset windows layout'. Guess it could be labelled 'Dock Windows at Right Side (Default)' |
|
Again, only did a cursory run through to make sure I was getting the menu with latest pull from git. |
|
k, this is the window output log from the new Win64 build run above. Captured doing "Select All", then "Copy" after the main compile piece was finished, while the SQLCipher build was in progress. Anyone see any smoking guns? |
|
Other than being in a detached head? Other than that? Nothing really jumps out as a "smoking gun". |
In fact, 'Dock Windows at ...' moves the visible docked windows to the corresponding side, but does not change the visibility of the windows, so a 'Dock Windows at Right Side' might make sense, but I decided not to added it, because it would be "almost" redundant with the Reset option. Nevertheless, I'm open to suggestions. |
Good idea. 😄 Just did that that specifically, and have triggered the build script to run again (Win64 version only). |
|
@scottfurry Looks like that was the problem. The new rebuilt Win64 nightly build (online now) is showing the new options. Just started the Win32 build manually, so an updated version of that will be online in ~1/2 hour or so too. |
|
That can be an issue every now and again with CMake. No guarantees if build files are regenerated. Out-of-source builds can be our friend. |
|
@scottfurry Agreed. 😄 @chrisjlocke The Win32 nightlies have just been rebuilt and are online. They're showing the new menu options now too. |
|
Thanks so much all for digging into this. 🍰 |
Works great on macOS, @mgrojo! Thanks so much. |
|
Any chance scripting or custom skins can be implemented in the new UI? |
|
Views would be application based though, not project based. If I had a particular view, I'd want that 'global', and I may not save a database as a project. They'd have to be separate files. Maybe. |
|
@sky5walk If we can figure out a sane approach for people to use, then sure. 😄 |
|
There are arguments for a single file vs multiple. |
OK, somehow (?) we have to work out the userbase of DB4S. Is it home usage (like me) just fiddling and tinkering, or is it in teams, using Gits, repos, fossils, badgers, oscars, penguins, etc. OK, made the last ones up. |
|
My understanding of the project file's utility is to store SQL queries and the loaded database. |
|
I've seen some programs take a two pronged approach to loading settings:
That lets orgs/teams/groups/etc apply their own default settings for everyone. Individual users can still tweak things for their own requirements on top of that though. Maybe that would work for us? |
A new predefined simplified layout has been added with the only the basic functions: schema, browsing and SQL execution. Ideal for courses. Also added options for moving all the docked windows to the bottom, left side or top (for the right, the default can be restored with Reset Window Layout as before). See issue #2307 # Conflicts: # src/MainWindow.cpp # src/MainWindow.h
|
I tried out 3.12.1 rc1 and found tiny inconsistencies:
|
|
@c-boeckler Thanks for report a bug. I have succeeded in reproduction the bug and will fix it ASAP. 😄 |
Describe the new feature
Per #2306, we use DB Browser to introduce students to SQL in classes. (Thank you for a wonderful teaching tool!) By default, on macOS, at least, quite a few panels are open by default, none of which are strictly necessary to start creating tables or exploring existing tables:
And I fear they tend to make the tool seem more complex at first glance than it need be, at least for less experienced users (students, in our case). When teaching with DB Browser, for instance, I close all of those additional panels so that students can focus on core features like Database Structure, Browse Data, and Execute SQL:
As via these settings:
While DB Browser's audience is surely broader than ours, might it be compelling to disable some/all of those extra panels by default for new installations, so as to onboard new users a bit more simply? I'm sure a tradeoff might be that some users might not discover those more powerful features, so we do realize our use case is narrower!
The text was updated successfully, but these errors were encountered: