PRIORITY LIST

[EverlastingEndeavour]

Priority list for Sneedacity

1. Conan package dependency is bad and needs remote repositories, it's a pure botnet thing we want to remove it (DONE)
2. Implement additional cmake fixes/hacks to improve build stability in the short term.
3. Audacity forked wxwidgets for no reason and never updated it, we want to support wxwidgets upstream again
4. Audacity cmake is terrible, we want to fix it (preferably replace it with meson)
5. A better gui would be a great improvement

This may be edited according to the project progress.

Last Updated: 07/16/21

[ghost]

rearrange the gui, making it more usable but probably break some like gui automation thing one person uses

[Ckath]

if its going to be in order I'd put unfuck cmake after conan and wxwidgets. will have to do whatever ungodly things to get that working and then cleaning up the build system can be considered.
at least in my mind.

besides that, its not super high on priority but I'd like to look at #145 soon too.

[BasedRimuru]

Nice, if we remove conan anything will be possible

[Ckath]

make sure to just format this and then lock it after things are worked out. some huge thread isnt much better than all the issues on their own

[BasedRimuru]

Do you mind if I edit it?

[blancdesir]

this should go into milestones

[sonsofsneed3]

IMO GUI streamlining is one of the most important issues, but it should be very carefully tweaked tiny increment by tiny increment and totally aligned with user sneedback

[kostas-from-cyber-space]

2\. Audacity forked wxwidgets for no reason and never updated it, we want to support wxwidgets upstream again

in a similar vein, is there a reason for having all those dependencies in repo (in /lib-src)?

[sneedcat]

2\. Audacity forked wxwidgets for no reason and never updated it, we want to support wxwidgets upstream again

in a similar vein, is there a reason for having all those dependencies in repo (in /lib-src)?

Stability. Either we ship dependencies, either people need them installed. Also, shipping dependencies is good for windows. We can clone the repositories, but we need to be sure that they are API compatible with the older version or we need to change it. Cloning a specific release/commit is a good thing, and might be implemented in the future.

[nobuyukinyuu]

Divorcing the code base from wxwidgets somewhat would be great; like openMPT, the UI hasn't seen a modern refresh in years outside of basic color theme support (still no rearranging of elements last i checked), but unlike openMPT, you can't even leverage an API to design a new interface that suits your own workflow, either.

[ghost]

Audacity forked wxwidgets for no reason and never updated it, we want to support wxwidgets upstream again

note that upstream is already planning to address this audacity/audacity#625

A better gui would be a great improvement

are maintainers willing to maintain a different UI long term? why not just wait and see what muse does and just keep merging the changes from upstream? that's the stated goal of the project anyway

[ghost]

are maintainers willing to maintain a different UI long term?

Don't worry I have autism

I think the consensus right now is, after uncoupling wxwidgets, Conan, etc, that there'll be some rewriting in Qt, because Qt is infinitely superior to wx and GTK. It'd also be significantly easier to deal with, better theming, etc. plus it has other things in the core like QString and all that, that might be useful. Also it would finally be a chance for me to use Qt in an actually good application (besides passman++), and as I said I have autism so I can probably easily do it

Pretty much no reason not to use Qt and it would give a major advantage over Audacity. GUI rewrite is pretty important imo

[ImGonnaChuck]

Built executable segfaults on Debian 11 #267
Program depends on build folder after install #263
Compilation fails on cairo.h not found #85
the windows builds broke again #258

[Ckath]

besides the build issues probably key to find some solution to upstream merging, preferably (semi) automated, #217. it'd be a somewhat valid option as audacity alternative at that point again.
not sure how syncable with upstream it is at this point with the source changes, but at least a lot of stuff should be mergable still

[Ckath]

wrong button