Skip to content
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

[FEATURE] GUI revamp #2865

Open
livingsilver94 opened this issue Sep 28, 2023 · 1 comment
Open

[FEATURE] GUI revamp #2865

livingsilver94 opened this issue Sep 28, 2023 · 1 comment
Labels
Effort: Tremendous Info: Might introduce regressions Type: Breaking change Fix or feature that will cause existing functionality to change Type: Feature adds functionality

Comments

@livingsilver94
Copy link

QON uses QtWidgets, and it's showing its age. The fact that it's software-rendered is irrelevant since it's all text, but the overall look and feel, and potentially the appeal to new maintainers/contributors are subpar.

I totally understand QON is a long-running project that predates QtQuick, still it's probably the time to cross a new path. It's no coincidence that most recent OSS note-taking applications are based on Electron. Can't comment the like of Bear, since it's closed-source.

Describe the solution you'd like

Move the GUI to QML and QtQuick. This way, we could achieve a modern and better look more easily compared to QtWidgets. Separating logic and representation is also a good practice, impossible with .cpp QWidget subclasses.

Easily noticeable visual defects

Qt theming has always been an issue so I won't blame QON for that. But, just by opening the application for the first time a user can notice how many separators are drawn in the main window. The main editing areas has 2 outlines and double separators divide many icons in the top bar, since the top bar is customizable. This shouldn't be the default in my opinion, since not to overwhelm the user should be a priority over personalization.

I think those two defects don't come from the design of QON but from QtWidgets itself.

A long-term goal

Oh yeah, it surely is. Don't take me wrong, my aim is not to complain about the look of QON but to highlight why other applications chose to use a different technology to achieve an objectively more modern look.

What do you think? :)

@pbek pbek added Type: Feature adds functionality Type: Breaking change Fix or feature that will cause existing functionality to change Effort: Tremendous Info: Might introduce regressions and removed Type: Support labels Sep 29, 2023
@pbek
Copy link
Owner

pbek commented Sep 29, 2023

QML has its advantages, but QOwnNotes should first and foremost as fast as possible, even on old hardware. With QML you don't really get that anymore...
But if you want to port components like https://github.com/pbek/qmarkdowntextedit and the preview to QML we certainly can talk again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Effort: Tremendous Info: Might introduce regressions Type: Breaking change Fix or feature that will cause existing functionality to change Type: Feature adds functionality
Projects
None yet
Development

No branches or pull requests

2 participants