-
-
Notifications
You must be signed in to change notification settings - Fork 295
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
[Feat] Single-Window GUI: Decide on the form of the GUI arrangement #1747
Comments
|
Just to make sure: we're talking about first startup ? Afterwards the user can define other defaults ? I have a clear preference for options 3 and 4, as I think console and Python are already advanced use cases and should, therefore, not encumber the GUI at first startup. In 4 it would be nice if there could be something more explicit than the small icons that there is something available. Either slightly larger icons (maybe longer vertically) with text, or possibly a button saying "open other windows", or something like that. If that is not possible, I prefer 3. |
Yes, all presented options (and of course others) are simply reachable by moving/docking given panes.
Yes, the fourth option seems to me also not suitable for the first startup, even though I believe that this option will be the standard way of using GRASS for many people.
|
|
For a first time user, yes, option 3 seems better, so they know which other panes are available. |
|
Is addressed here: #1775 |




Is your feature request related to a problem? Please describe.
This Issue opens the place for the discussion. :-)
We still have a lot of work to do to create a Single-Window GUI, but I think it makes sense to open this Issue now so that everyone has enough time to share their thoughts.
As the result of this Issue, we should decide how the initial GUI startup will look like and we can also set up the further coding priorities.
Please, feel free to ask questions and express your preferences related to the Single-Window GUI in general. This is a good place for sharing it.
The text was updated successfully, but these errors were encountered: