Spec: use MVVM

[Lamparter]

📄 Description

Currently, Rebound does not implement MVVM namespace structure. Code should be moved from code-behind into reusable ViewModels/Models, like so:

• [ ] Rebound.Models
• [ ] Rebound.ViewModels
• [x] Rebound.Views

⚡ API Changes

API	Description
VIEWS	Contains views for pages with little code-behind except button handlers
MODELS	Contains reusable models for logic
VIEWMODELS	Contains ViewModels for logic attached to pages

👥 Usage scenarios

For example, the code-behind for the installer (InstallationWindow.xaml.cs) would now be a separate model.

🔙 Backward Compatibility

Shouldn't affect anything.

🤔 Difficulty

Medium

[Lamparter]

I can't use MVVM app model as in [ObservableProperty] and bindings and etcetera but I can copy the classic MVVM project style, that looks like this:

• Assets
• Properties
• Helpers
  • collapsed reusable code goes here

    should mostly be in Rebound.Helpers but I'm kind of having second thoughts about it

• Models
  • reusable app code goes here/core business logic
• Views
  • pages/presentation go here
• ViewModels

  should probably just use code-behind for ViewModels

• UserControls
• MainPage.xaml
• App.xaml

  other files should not be here unless strictly necessary/appconfig files