feature requests

[Priyanka328]

GUI Feature request:

• Allow (re-)import of tasks from the gui. Like "import task" and "update task" in case the orogen file changed
• Configuration setup

[hwiedPro]

Hey guys!
I used the xdbi-remove script to remove existing model in my Serverless database.
If I use just a name of the model it will not work. I have to provide uri information to delete the model.
Probably the xdbi-remove will be a part of gui soon. But until that point, can xrock-gui provide uri information for the model? So the user dont need to search in database folder for the uri of the required model.
So see this issue as small feature request ;) Thank you in advance!

From issue by Anna

[m0rsch1]

There is a tool called xdbi-find which can resolve XTypes by properties (including name) and returns the URI.
That URI can then be passed to xdbi-remove. Btw. as far as i know, the URI information is already available in the GUI, right @Priyanka328 ? Is it not visible in the model key in the NodeData widget?

[Priyanka328]

Hey guys!
I used the xdbi-remove script to remove existing model in my Serverless database.
If I use just a name of the model it will not work. I have to provide uri information to delete the model.
Probably the xdbi-remove will be a part of gui soon. But until that point, can xrock-gui provide uri information for the model? So the user dont need to search in database folder for the uri of the required model.
So see this issue as small feature request ;) Thank you in advance!

From issue by Anna

This issue is resolved by a removed icon.

[haider8645]

• XRock Improvements:
  • (done) We need global variables in ComponentModels for task configurations that can be handled by
  • (done) Allow to override single configurations of submodules from higher level
  • Create deployment manifest for dependencies in component network
  • Designing navigation template
  • Implement method to configure specific components in template

[haider8645]

Add git source and branch to information in component database to be able to check that in workspace, otherwise the configuration could be incompatible with the installed version

[m0rsch1]

Is this still valid? @haider8645 @Priyanka328

[Priyanka328]

global variable feature is already implemented.

Is this still valid? @haider8645 @Priyanka328