An extension contains common functions for different extensions

Development
1

Dear all,

I have two different extension1 and extension2 for two different users user1 and user2. These extensions are using the same functions. I created a common scripted module that both extensions can use. My question: Is it ok to add pull request for this extension as it does not do anything by itself?

If I add it to one of the two extensions, one of the users will have to install both extensions. If I add it to both extensions, this produce redundancy.

Best regards!
Ibraheem

2

There are a few examples for utility extensions (SlicerOpenCV, SlicerIGSIO), but in general these are larger extensions that many other unrelated extensions use. It is better to avoid introducing very small utility extensions, as they increases maintenance workload.

Instead of introducing a new utility extension, can you make one extension depend on the other?

3

Thanks Andras!

Instead of introducing a new utility extension, can you make one extension depend on the other?

Yes, but as I mentioned a user will have to install an extension even if he does not need it.OK, I think I got an idea. I will just download the comoon module file to the current module path.

4

If you list the extension as a dependency then it will be installed automatically (user just need to click OK). I would not recommend separate manual download and install of a module.

5

I would not recommend separate manual download and install of a module.

I just figure out this may complicate things. OK, I go for this approach but it would be nice if Slicer offers such thing e.g. an extension that does not appear in the extension manager.