Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better data structure for the process tree #5

Open
ForNeVeR opened this issue Dec 24, 2023 · 3 comments
Open

Better data structure for the process tree #5

ForNeVeR opened this issue Dec 24, 2023 · 3 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@ForNeVeR
Copy link
Owner

ForNeVeR commented Dec 24, 2023

Currently, we rely on a plain list ObservableCollection<ProcessModel> Processes model.

This is problematic in some ways.

  1. It's unclear how to efficiently find the process whenever we decide to delete it.
  2. It is unclear how to produce the tree structure from them.

Currently, I am thinking about declaring some sort of observable dictionary (is there such a class in BCL? if not, we could create our own).

Make sure to review and eliminate every instance of TODO[#5] in the application code.

@ForNeVeR ForNeVeR added enhancement New feature or request help wanted Extra attention is needed labels Dec 24, 2023
@Vazovsk1y
Copy link

@ForNeVeR
Copy link
Owner Author

Yep, could be.

ForNeVeR added a commit that referenced this issue Dec 27, 2023
@DmitryZhelnin
Copy link

DmitryZhelnin commented Mar 18, 2024

If you are going to stick with ReactiveUI it is possible to use SourceCache from DynamicData package.

EDIT: I mean ReactiveUI already has reference to DynamicData so no new packages are needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants