Skip to content

JPRO-cleanup Move Concept specific controllers out of properties into concept#727

Open
vollbrecht-work wants to merge 1 commit into
ikmdev:mainfrom
vollbrecht-work:JPRO-code-cleanup-3
Open

JPRO-cleanup Move Concept specific controllers out of properties into concept#727
vollbrecht-work wants to merge 1 commit into
ikmdev:mainfrom
vollbrecht-work:JPRO-code-cleanup-3

Conversation

@vollbrecht-work

Copy link
Copy Markdown
Contributor

This is a first step to more clearly represent the current hirachical structure.

This will hopefully in the future make it simpler to actually create "shared" properties classes.

This PR does not move out History / Hierarchy Controllers. Since they currently are not exclusivly used by the ConceptController, but also still part of kview.lidr.mvvm.view.properties.

This is a first step to more clearly represent the **current** hirachical structure.

This will hopefully in the future make it simpler to actually create "shared" properties classes.

This PR does not move out History / Hierarchy Controllers. Since they currently are not exclusivly used
by the ConceptController, but also still part of kview.lidr.mvvm.view.properties.

@carldea carldea left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work!
I approved but I noticed merge conflict. I will merge once things are resolved.

@dholubek

dholubek commented Sep 9, 2025

Copy link
Copy Markdown
Contributor

@vollbrecht-work can you resolve the merge conflicts? can you test create concept and summon a concept from the concept navigator to verify that everything is working? I pulled down the branch and got an exception when choosing create concept.

@carldea

carldea commented Sep 10, 2025

Copy link
Copy Markdown
Contributor

There's much activity in these files :-). Let me know maybe we redo this PR when others are finished with these files. Up to you. Know what I mean?

Other developers have updated many of these files. And this PR is becoming out of date. I think it might be easy to abandon this PR and recreate it. Let me know your thoughts.

@vollbrecht-work

vollbrecht-work commented Sep 10, 2025

Copy link
Copy Markdown
Contributor Author

yeah after we are done with the more pressing work i will rebase this once more

@carldea

carldea commented Sep 12, 2025

Copy link
Copy Markdown
Contributor

@vollbrecht-work could you rebase and resolve conflicts again. sorry. I think we should merge this come first thing monday if possible.

@dukke dukke requested review from dholubek and dukke September 13, 2025 13:24

@dukke dukke left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding to @dholubek point I would test Concept creation and editing an existing Concept before merging, if possible.

@carldea

carldea commented Sep 17, 2025

Copy link
Copy Markdown
Contributor

I'm wondering if we should redo this PR, because it's out of date. @vollbrecht-work Let me know your thoughts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants