Skip to content

GUI Redesign Incorporation into Master#696

Open
masonwillman wants to merge 505 commits intomasterfrom
GUI-Redesign
Open

GUI Redesign Incorporation into Master#696
masonwillman wants to merge 505 commits intomasterfrom
GUI-Redesign

Conversation

@masonwillman
Copy link
Contributor

The GUI Redesign is at an appropriate stage where we need to merge with the master branch. This will allow users to use the updated GUI as needed and provide us developers with up to date ninja code.

masonwillman and others added 30 commits August 26, 2025 09:50
GUI Redesign Point Initialization Page
GUI Redesign Weather Model Page Refactor
GUI Redesign Initial Ninja Com Integration
…nings.

seems the duplicate "aboutQtAction" and "exportSolutionAction" were introduced in commit/merge 787ef5e, one of the extra "verticalLayout_26" was added in commit/merge 5f5cc8e, and the additional "verticalLayout_" "_26", "_29", and "_31" were added in commit/merge 006911f. It is confusing though, because some of the later commits/merges make it look like these same changes were added then as well, but I double checked and these commits seem to be the earliest that such additions were found in the raw files of the mainwindow.ui file code.

Not detecting any differences in code behavior, so I think that these should be the only quirky changes accidentally introduced during the last few merges.
…nd point radius should update alongside bounding box coordinates, for #648
GUI Redesigns Surface Input Improvements for DEM dowloading and reading
GUI redesign weather model initial work
…es, to wrap up pull request 79f16b6, as part of the old commit badc48d.
it technically works, but there's some weird final extra flush-like emit that is occurring after the process is done, leading to the final message and close being replaced with another message
latwood and others added 20 commits February 4, 2026 14:28
…and numRuns counting methods, it definitely follows the exact method as the old code now.

That being said, the method definitely needs refactored to be less confusing. I wrote the old code methods 2 years ago, but apparently I did it too cleverly, because even I am having a rough time reading exactly how it works as it is now. Apparently I was too clever for myself lol.

For issue #687
…sured tree properly updates when new dem file is specified
…ector<> of the specific QWidget types. For issue #687
…function, also an improvement to the organization of the domainAvgTable checkRows() app state checking methods. Should be a lot clearer now. For issue #687
…d, moved the state checking to appState, now the icons and tooltips are getting updated accordingly. For issue #687
…from commit 7d8c075, if there are differences between qt4 and qt6 GUI results, it is something else
…to improve inputWindHeight combo boxes while I was at it.
…t4 GUI "orange" color isn't quite dark enough though. For issue #604, related to issue #638.
…of 150% darker than "orange" is better, but still not quite a good color. For issue #604, related to issue #638
…ks like "dark-orange" is better, the old qt4 gui "orange" was "QColor(255, 165, 0)". Probably gonna leave it as is for now. For issue #604, related to issue #638.
… a bit better, and make it so you don't have to click into the first text box to edit it.
<link rel="stylesheet" href="leaflet/L.Control.Layers.Tree.css" />

<!-- Leaflet and Draw dependencies -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/jszip/3.10.1/jszip.min.js"></script>

Check warning

Code scanning / CodeQL

Inclusion of functionality from an untrusted source Medium

Script loaded from content delivery network with no integrity check.
<!-- Leaflet and Draw dependencies -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/jszip/3.10.1/jszip.min.js"></script>

<script src="https://cdnjs.cloudflare.com/ajax/libs/jszip/3.10.1/jszip.min.js"></script>

Check warning

Code scanning / CodeQL

Inclusion of functionality from an untrusted source Medium

Script loaded from content delivery network with no integrity check.
@latwood
Copy link
Collaborator

latwood commented Feb 7, 2026

As far as I can tell, it definitely looks good. Not sure if we should try to address the two security things in map.html before the merge, or after the merge. But the overall merge appears to have everything correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants