wiki:wxGUIDevelopment/ImprovingSingleWindowUX

Version 26 (modified by lindakladivova, 17 months ago) ( diff )

--

Mini project 2023: Improving Single-Window GUI user experience

Title: Improving Single-Window GUI user experience
Student Name: Linda Kladivova
Organization: OSGeo - Open Source Geospatial Foundation
Mentor Name: Anna Petrasova, Martin Landa, Vaclav Petras
GitHub Repository: view repository
Budget: 1000 € (via GRASS GIS Student Grants)

Abstract

The project builds on the discussion with users and the usability testing of a new and old GUI, which took place in April 2022. The proposed work can be divided into two main topics - the reorganization of the Console pane and the implementation of the ability to undock a map window. Additionally, the project plans to address the topic of saving Single-Window GUI layouts to workspaces.

Goal

The core part of the work will be devoted to reorganizing the Console pane and implementing the ability to undock a map window. The first topic lies in ensuring a better visual separation of Console output and Command prompt functionality. Today, it is not clear which buttons belong to the Command prompt and which to the Output window. Moreover, in the Single-Window GUI layout, the widget with buttons managing the Command prompt is partly hidden after the GRASS launch. The graphical proposal for separating Console output and Command prompt functionality is included in https://github.com/OSGeo/grass/issues/2585 . Besides visual separation, accessing the command history with the Log File button is not intuitive and will be replaced by a button for simply exporting the entire command history.

Based on the results from usability testing, undocking and docking map windows is also essential functionality for users. This project aims to add a button to the map display toolbar enabling undock and dock map display windows. Adding this functionality will allow users to achieve a similar layout as in Multi-Window GUI if desired.

The last topic develops the idea that users should be able to save user-defined layouts in a Single-Window GUI within the workspace. This functionality is the first step for managing user-defined layouts in GRASS.

Timeline

Time Period

Milestones

Tasks

Status

November 21 - November 25
Week 1

Undock and dock Map Display panel (enable using Single-Window as Multi-Window)


Ready to merge

November 28 - December 2
Week 2

Undock and dock Map Display notebook pane, replace Log File button in Console pane by Export history button


Ready to merge

Merged

December 5 - December 9
Week 3

Undock and dock Map Display notebook pane, replace Log File button in Console pane by Export history button


Ready to merge

Merged

December 19 - December 23
Week 4

Undock and dock Map Display notebook pane, add input string to command prompt


Ready to merge

Merged

January 2 - January 6
Week 5

Undock and dock Map Display notebook pane, add hint to command prompt


Ready to merge

Closed (abandoned)

Merged

January 9 - January 13
Week 6

Undock and dock Map Display notebook pane, reorganize Console buttons


WIP

WIP

January 16 - January 20
Week 7



January 23 - January 27
Week 8



Weekly reports

Week 1

1) What did I complete this week?
At the beginning of this week, I was a bit stuck on the Console reorganization topic (see Issue https://github.com/OSGeo/grass/issues/2585). As it is probably the most important topic of the project, for the next weeks we better clarified how the result should look like. To fully use the time between, I changed the timeline a bit and first started to work on the issue of map display page (un)docking. I set up the PR ​https://github.com/OSGeo/grass/pull/2667 for that topic and plan to continue on it next week. Moreover, I noticed a bug appearing when a user moves a map display notebook page (or wants to pull it out of a map display notebook).

2) What am I going to achieve for next week?

After more testing and fixing I would like to merge the above-mentioned PR dealing with Map Display page (un)docking - please see ​https://github.com/OSGeo/grass/pull/2667. Specifically, I need to test the behaviour of undocked map display panel when switched to 3D mode. In the meantime, I am going to prepare locally the branch dealing with Console panel reorganization. I would also like to address some small bugs I have revealed when working in Single-Window.

3) Is there any blocking issue?
No, it isn't.

Week 2

1) What did I complete this week? I was mainly working on PR https://github.com/OSGeo/grass/pull/2667 dealing with dock/undock map display functionality. This PR is finished and waits for the final review. Further, I started to work on the Console reorganization topic, specifically, I have set up the new PR https://github.com/OSGeo/grass/pull/2682 replacing the togglable "Log file" button with the "Export history" button. This first step is going to better steer the direction of Console reorganization.

2) What am I going to achieve for next week?

I plan to merge both above-mentioned PRs and proceed to work on the Console reorganization topic according to Issue https://github.com/OSGeo/grass/issues/2585. Not only it involves the widget reorganization itself, but it also improves user experience by adding >>> to the command prompt window.

3) Is there any blocking issue? No, it isn't.

Week 3

1) What did I complete this week?

I returned to the PR https://github.com/OSGeo/grass/pull/2667 dealing with dock/undock map display functionality because although the PR was finished in terms of functionality I am satisfied with the code. I have started with refactoring and created a new MapNotebook class in a separate file. I think for future maintenance it is an important step. I am still working on it.

This week I also finished PR https://github.com/OSGeo/grass/pull/2682 implementing the Export history button in the Console pane and I am waiting for the final mentor review.

2) What am I going to achieve for next week?

I hope I will finally start working on the Console reorganization issue. This topic should not be such time-consuming as docking functionality. On Thursday I am going on holiday (till Sunday) so I am going to extend a bit my project timeline.

3) Is there any blocking issue? No, it isn't.

Week 4

1) What did I complete this week?

I fully refactored the PR https://github.com/OSGeo/grass/pull/2667 dealing with dock/undock map display functionality and currently, this thing is almost finished. In addition, the PR https://github.com/OSGeo/grass/pull/2682 implementing the Export history button in the Console pane was approved. So these two PRs are finally approaching the merge.

I have started to work more intensively on the second major project topic which sounds basically "How to make the Console pane more user-friendly". I started by adding an input prompt sign to the Command prompt. This sign should help beginners notice the Command prompt and better understand the difference between the Command prompt and the Command output. For this purpose, I created the PR https://github.com/OSGeo/grass/pull/2718 which is still under process.

2) What am I going to achieve for next week?

Besides working on PR https://github.com/OSGeo/grass/pull/2718, I plan to more focus on the Console reorganization topic.

3) Is there any blocking issue? No, it isn't.

Week 5

1) What did I complete this week? The PR https://github.com/OSGeo/grass/pull/2682 implementing the Export history button in the Console pane was merged.

The first part of the week I worked on PR https://github.com/OSGeo/grass/pull/2718 which adds an input prompt sign to the command prompt widget. However, although it was our suggestion from https://github.com/OSGeo/grass/issues/2585, the intervention into the command prompt showed programmatically as very unfortunate - it was really hard to cover all cases of how the text in the command prompt could be managed. So, we decided to implement the task differently by showing a hint in the case that the command prompt is not focused. I think it is an even more user-friendly solution. It is already prepared for merging (see https://github.com/OSGeo/grass/pull/2728).

Meanwhile, I worked on adding "isDocked" parameter to workspace handling in the PR https://github.com/OSGeo/grass/pull/2667 dealing with dock/undock map display functionality. It was the thing I forget to consider. However, the workspace issue revealed another error in https://github.com/OSGeo/grass/pull/2667 related to closing undocked map display frame.

2) What am I going to achieve for next week?

The goal for the next week is to merge both - https://github.com/OSGeo/grass/pull/2728 and https://github.com/OSGeo/grass/pull/2667. Then I plan to create a PR on the Console reorganization according to the suggestion in https://github.com/OSGeo/grass/issues/2585.

3) Is there any blocking issue? There is one blocking error in https://github.com/OSGeo/grass/pull/2667 related to the erroneous closing of undocked map display frame (wrapped C/C++ object of type MapPageFrame has been deleted). I have already spent several hours to fix it but unsuccessfully. I will probably put it off now and go back later, with more ideas in my mind.

Week 6

1) What did I complete this week? I finished PR https://github.com/OSGeo/grass/pull/2728 which adds a hint to the Console prompt (it is already merged). Moreover, I opened a new PR ​https://github.com/OSGeo/grass/pull/2746 related to button reorganization in the Console pane.

2) What am I going to achieve for next week? The goal for the next week is to finish the Console reorganization topic by merging ​https://github.com/OSGeo/grass/pull/2746. I would also like to start working on the issue of perspectives (user-defined layouts). I plan to start by saving pane arrangements to workspace files.

3) Is there any blocking issue? There is still a problem with the PR https://github.com/OSGeo/grass/pull/2667 but it is not a blocking issue.

Week 7

1) What did I complete this week? 2) What am I going to achieve for next week? 3) Is there any blocking issue?

Week 8

1) What did I complete this week? 2) What am I going to achieve for next week? 3) Is there any blocking issue?

Attachments (2)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.