-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
MainWindow is a giant monolithic mess #107
Comments
Not off-topic at all I'll have a look at GPGME as soon as I can . . |
Maybe it would be handy, if some elements of mainwindow.cpp such as the treeview get their own subclasses, as this would make it easier to implement special features |
Something went wrong here in checkConfig.. |
This also changes the behavior of the main window: If content should be hidden nothing is shown. Else the password is always shown as a field (either with hidden with dots or openly visibly.) the rest is shown as plain text or as field depending on the template settings. This is results in a nicer ui and needs one translation (Password hidden) less.
This also changes the behavior of the main window: If content should be hidden nothing is shown. Else the password is always shown as a field (either with hidden with dots or openly visibly.) the rest is shown as plain text or as field depending on the template settings. This is results in a nicer ui and needs one translation (Password hidden) less.
* Split datahelpers.h to userinfo.h and passwordconfiguration.h * Rename passwordConfiguration to PasswordConfiguration * Move some code to separate methods in MainWindow * Handle PasswordConfiguration in QtPassSettings and in ConfigDialog
Visit my fork at branch |
I have started a new branch to at-least get the
QProcess
andQSettings
handling out of there for now.Refactoring turned out to be harder than I expected because of the spaghetti mess the configuration and process handling has become.
Adding features is so much nicer than creating an architectonically correct app.
I would actually think it's probably wise to first brainstorm about an optimal way of handling QtPass from an architectural perspective.
If anyone has any ideas about this (or would like to flowchart something together) I'd be more than thankful.
This is also an issue to gather my progress reports, I might create a new branch to do some refactoring instead of continuing with the https://github.com/IJHack/qtpass/tree/feature/refactoring branch.
The text was updated successfully, but these errors were encountered: