BartShoot
Node editor, many operations - how to make it maintainable
Hi, I'm trying to develop an app with node editor that ideally will provide no code openCV functionality.
There are many methods, many different inputs and outputs and I probably have to wrap them some way - my first attempt looked like this https://github.com/BartShoot/projekt-praca-inz/blob/main/PrototypeWPF%2FPrototypeWPF%2FViewModels%2FOperations%2FBlurViewModel.cs
I tried to keep IOperation as generic as possible but due to this creating inputs and outputs for viewmodels is quite bad. Is there a way to make it more fool-proof? Maybe there is a better way to manage them that I'm missing?
Thanks in advance
1 replies
Desktop crossplatform application? How to approach it?
Hi,
I recently made prototype for image processing application with WPF and will try to make it properly now but I want to be able to use it on Windows Linux and MacOS at the least.
I don't think I know all the options but first I was considering either AvaloniaUI or something based on web frontends like react or angular.
My wpf app was using https://github.com/miroiu/nodify to implement node editor, it would be great if it worked or good alternative was available. Also it would be great if launching the app locally would be easy, I'm not considering deploying this to cloud as web application for now.
My wpf app was using https://github.com/miroiu/nodify to implement node editor, it would be great if it worked or good alternative was available. Also it would be great if launching the app locally would be easy, I'm not considering deploying this to cloud as web application for now.
27 replies