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

[bnd] BndEditModel to provide mechanism for handling included files #4792

Closed
kriegfrj opened this issue Aug 16, 2021 · 2 comments
Closed

[bnd] BndEditModel to provide mechanism for handling included files #4792

kriegfrj opened this issue Aug 16, 2021 · 2 comments
Labels
abeyance need of contributor [requires is:closed] stale Stale issue or pull request

Comments

@kriegfrj
Copy link
Contributor

It would be good if the BndEditModel were able to be a bit smarter about handling included files.

There are two situations where this becomes relevant that spring to mind:

  1. If you have inherited properties, then the GUI will only display the properties directly defined in the file you're editing. Seamlessly handling inherited properties in the GUI would likely require more work, but having BndEditModel at least aware of that would be a first step.
  2. The "hot redeploy on change" functionality available in Bndtools currently only works when changes are directly made to the bndrun that you launched with. For example, if I am live coding in the Bnd workspace on the bndtools.core project, and I have launched using bndtools.win32.x86_64.bndrun and I edit bndtools.shared.bndrun (which the win32 launch file -includes), it will not automatically update my running instance. If the BndEditModel were aware of -include and could calculate the final set of properties, these could be used as the basis of the diff to figure out if the running process needed to be updated.
@bjhargrave bjhargrave added the abeyance need of contributor [requires is:closed] label Aug 20, 2021
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@github-actions github-actions bot added the stale Stale issue or pull request label Aug 21, 2022
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Bnd/Bndtools or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
abeyance need of contributor [requires is:closed] stale Stale issue or pull request
Projects
None yet
Development

No branches or pull requests

2 participants