See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=20295

Also back-ported to 4.1.1 - See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=20297

Fixed in https://github.com/jcfr/Slicer/tree/2145-support-for-installing-extension-from-file

@Matt: Since I don't want to interfere in the work you are currently doing with the extension infrastructure, I delegate the final step regarding topic [1]. After installing the extension given an archive, the user should be given the option to "force" the revision and ensure Slicer won't complain the extension is not compatible at the next startup.

[1] https://github.com/jcfr/Slicer/tree/2145-support-for-installing-extension-from-file

From: http://slicer-devel.65872.n3.nabble.com/Adding-library-paths-for-modules-tp4028431p4028432.html

As explained here [1], when extension are installed using the extension manager, launcher setting are updated to consider Slicer modules location and also standard location like "/path/to/extension/{bin, lib/Slicer-4.2}" [2][3]. (Note that the value of these paths is abstracted using Slicer_BIN_DIR and Slicer_LIB_DIR).

But when you manually add the module path through the settings ... launcher settings are not updated. This will be fixed as part of issue 2145 [3]

It means that after the user install your extension, launcher setting will be automatically updated.

If you would like to help us improving the system so that launcher settings can be updated after manually adding module path to the settings, let me know and I would be happy to provide guidance.

Thanks
Jc

[1] http://slicer-devel.65872.n3.nabble.com/Unloaded-module-when-linked-to-OpenCV-tp4028392p4028399.html

[2] https://github.com/Slicer/Slicer/blob/master/Base/QTCore/qSlicerExtensionsManagerModel.cxx#L581-595

[3] https://github.com/Slicer/Slicer/blob/master/Base/QTCore/qSlicerExtensionsManagerModel.cxx#L443-472

[4] http://www.na-mic.org/Bug/view.php?id=2145

This is implemented by https://github.com/mwoehlke-kitware/Slicer/tree/2145-install-extension-from-package.

Some notes:

• Installing via Python should work, in theory (the relevant method in qSlicerExtensionsManagerModel is public and Q_INVOKABLE).

• The extension is assumed to be compatible with currently running Slicer. That is, the arch, os and slicer_revision for the installed extension are set to those of the currently running Slicer. Since the extension is useless without this step, I don't see a purpose to giving the user an option as opposed to just doing it always. (Note that the extension itself does not specify any of these attributes anyway - they come from the extension server and the related automated build system - so we're not ignoring anything that was provided by the extension file.)

• There are also actions related to 0002089 currently visible but not implemented (as parts of the UI came from changes that were started to implement that feature). If 0002089 is not implemented by release, we should probably hide these (e.g. by commenting out the lines to add them to the menu).

It works well. I like the menu in the extension manager.

Few remarks:

a) When installing an extension archive, is it possible to:

• (if the extension manager page is loaded and visible) display a midas notice by exposing a function qSlicerExtensionManagerModel::info/critical/.... See [1][2].
  In case the user selected the "Manage tab" and install the extension from file .... a popup should be displayed.

  In both case ... info should be printed in the log.

  If installed from python, not popup should be displayed.

b) If installing an extension that has slicerRevision different from the current running Slicer, would it be possible to remind the user he did so. (the slicerRevision associated with the installed extension is in the bundled description file)

c) In case of dependent extension, since the dependency are also stored in the bundled description file. We should let the user know which dependency are missing.

d) It should be possible to pass a list of extension archives. If passed in the right order, no warning about missing extension should be displayed.

[1] https://github.com/Slicer/Slicer/blob/e365f3a97094675f0e4d46ab22833da0cf28afd6/Base/QTCore/qSlicerExtensionsManagerModel.cxx#L256

[2] https://github.com/Slicer/Slicer/blob/e365f3a97094675f0e4d46ab22833da0cf28afd6/Base/QTGUI/qSlicerExtensionsInstallWidget.cxx#L274

(a) Done.

(b) The .s4ext in the archive does not currently contain the slicer revision. (I'm not sure how I feel about relying on the name of the archive for that purpose. I guess it would be okay to do so if it is just a warning.)

(c) AFAIK Just Works (and "already" did; see 0002912).

(d) How to specify the list, and install order, is potentially non-trivial. We decided not to do this at this time.

Before we integrate "2145-install-extension-from-package", is it possible to also add the "theme" tweak ? Similarly to what has been done for [1]

[1] https://github.com/Slicer/Slicer/commit/ef0a5efe3e6f074e23ff8735c276d2b2f03b283c

Fixed by r23398 -> r23404

See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=23398