Thanks for the feed back.
My two bits:
Suggestions
1: remove the name space from the RODL - either its part of the definition or its not (service builder can ask if it doesn’t know)
2: in service builder change the label ‘Namespace:’ to be 'Namespace (maybe/sometimes/it depends):'
3: when service builder is invoked from the IDE throw up a warning saying RODL namespace is incorrect and (optionally) correct it. I like this one because it is not so much a breaking change to existing users.
Understand it would be a breaking change, but if you have a few RODL files in a project then can be nice if the RODL namespace was honoured. Otherwise if the RODL generation took the project default namespace and added the directory it is in it would be better than what it does now (ie the developer has some control over the namespace).
The IDE integration is useless to us (and breaks our code if people accidentally open the RODL from within the IDE). We will continue to manually generate code from the RODL.
:-).
No need for reply - just food for thought.