-
Notifications
You must be signed in to change notification settings - Fork 2
Migrate to MVVM architecture #55
Copy link
Copy link
Open
Labels
Far-FutureThis is something I want to add that would require a lot of workThis is something I want to add that would require a lot of workFeatureNew feature or requestNew feature or requestImprovementBug fixes, Performance improvements, other improvements.Bug fixes, Performance improvements, other improvements.help wantedExtra attention is neededExtra attention is needed
Description
Metadata
Metadata
Assignees
Labels
Far-FutureThis is something I want to add that would require a lot of workThis is something I want to add that would require a lot of workFeatureNew feature or requestNew feature or requestImprovementBug fixes, Performance improvements, other improvements.Bug fixes, Performance improvements, other improvements.help wantedExtra attention is neededExtra attention is needed
Migrate from plain code-behind to MVVM. Currently blocked by documentation hell: Avalonia docs are outdated and incorrect, workarounds point to ReactiveUI docs that are already broken, which point to further "workarounds" using syntax that only appears in ancient VBA-era Microsoft docs that
"could" be used in C#. Every layer of the stack references something that no longer works. Every prior attempt to adopt CommunityToolkit or ReactiveUI has ended in project abandonment. Will revisit when the ecosystem matures, or if someone with the skills to navigate the bugs and documentation graveyard
can help.