with the following example, thanks to @osolorzano we can load a project with ressources stored inside the module:
The example doesn't work to load an inheritable project. Is it possible ?
I would like to load from a module an inheritable project, inherited by others "classic" projects....
As in, if you modify the project export zip provided by the module to be inheritable you get an exception? I don't recall any conscious effort being made to restrict these immutable projects from participating in inheritance trees.
Reproduced the issue, it looks like in the designer launcher the list of projects that fills out that dropdown for Parent Project pulls from the same list of "valid" projects we use all around the designer launcher which excludes the immutable projects. I can write up a ticket for this.
However, if you create the project via the gateway web ui, then it appears there as a valid parent. From my limited testing there it looks like it works as expected at that point.
Do note that while you can do this, there's no attempt to prevent a user in one of these children projects in a designer from overriding any resource or viewing them in read-only mode for scripts. It just prevents the read-only parent from being edited directly.
It works from the gateway webpage. The project loaded is inheritable. The issue is when we create a project from the designer launcher where we can't select it in the parent project list.
It would be useful if we could have some settings on ressources to allow or not allow:
Please don't pollute this topic with wish-list items that the designer architecture simply cannot provide.
Whether you can override something is controlled by the "overridable" attribute you can already set inside the resource metadata. If particular workspaces/areas in the designer don't respect that, it's a bug.
Whether you can open a resource is nominally the role of the "restricted" attribute. Implementation/support for that is a lot spottier than overridable, though, and we're unlikely to go back through and spend a lot of time fixing it.
The ability to load projects from modules was never intended as a full replacement for OEM locking, and we have no real desire to re-implement it again. Consider any project you package into a module as strictly read-only, but not "secure" against someone malicious trying to access its internals.