somecollagist / spock

Spock Computer Science NEA

• https://somecollagist.github.io
• [email protected]
• Random product of autonomous energy

spock's Issues

Some Tips/Recommendations

Thought I might leave some tips and recommendations for this project, as I ended up doing something (sort of) similar in implementation for my EPQ.

Framework

I think your using WPF? If you're still just learning, I'd recommend learning Avalonia. It's generally a lot nicer, and, it's cross platform! That said, WPF is mostly fine unless you want to get fancy with the styles (or if you want chains of synced DependencyProperty values).

Having logic in the UI

What you're doing with having the logic for each component in the UI class does work alright - it's what I ended up doing for exposing properties for blocks in a flowchart - if you want to have two-way real-time coupling between the values in the UI and code behind it can get messy (the mentioned chaining of DependencyProperty above). That said, it looks like your UI might not be dynamically generated per component, whereas mine was, so you will likely have more success with this approach than I had. Either way, I'd generally recommend INotifyPropertyChanged instead of DependencyProperties for anything apart from directly on the UI components.

MVVM Toolkit

The Microsoft.Toolkit.Mvvm package on nuget is great. Would recommend, as it saves a lot of boilerplate code for DependencyProperties. The ObservableObject class and Command classes are particularly nice to have.

Seperating Projects

This is a small thing, mainly preference, but ideally your Core folder would be a separate project to the UI, and the UI would import the Core project, but not vice versa (anything in the other direction should be done via Dependency Injection). Not a big deal, but I often find it can help make clear what belongs in Core and what doesn't.

In case you're wondering what I did, for reference, here's my EPQ project: Dynamo