0002923: MacOSX - Slicer's additional module paths are user-dependent but extensions are not

ID	Project	Category	View Status	Date Submitted	Last Update

0002923	Slicer4	Core: Extensions	public	2013-02-07 12:32	2014-09-17 22:57

Reporter	akaiser	Assigned To	jcfr
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	Slicer 4.2.2-1
Target Version	Slicer 4.4.0	Fixed in Version	Slicer 4.4.0

Summary	0002923: MacOSX - Slicer's additional module paths are user-dependent but extensions are not
Description	When a user different from the user that installed the extensions loads Slicer on a Mac, the extensions are still specified as installed in the extension manager (files being in the package), though they do not load because the additional module paths that should contain the paths to the binary directories of these extensions are empty, which means they seem to be user-dependent. We need to specify the paths manually in the Slicer settings to get the extensions to load. After checking the ~/.config/www.na-mic.org/Slicer-(revision).ini in the user's home directory, the paths were indeed empty, the file having been recreated when starting Slicer. It seems inconsistent that the extensions are stored in the package, but that the modules paths are stored in the home directory. For example, on Linux, the extensions are not stored with the package but are in the local home directory of the user, so different for each user.
Tags	No tags attached.

jcfr 2013-02-07 13:07 administrator ~0007838	Settings are management uniformly across all the operating system. There are two kind of settings: User settings: Slicer.ini User+Revision settings: Slicer-<Revision>.ini It simply turns out that on mac, because we don't have yet the concept of "Slicer.framework", "Slicer.app" and "ExtensionA.plugin", "ExtensionB.plugin", we decided to "install" the extension directly within the application bundle "Slicer.app". To keep things simple ... I don't think we will consider this approach any time soon. Considering that on MacOSX, "Slicer.app" can be shared between multiple user, we could probably install the extension within the bundle into a subdirectory like: ExtensionA-<username>-<slicerrevision> See https://github.com/Slicer/Slicer/blob/master/Base/QTCore/qSlicerExtensionsManagerModel.cxx#l1471-1472 Would this be sufficient ?

matthew-woehlke 2014-04-23 05:53 developer ~0011646	I'm not sure I see how this is a duplicate of 0003552, which had to do with where extensions are downloaded prior to install. Has the OS/X behavior changed otherwise? (At least on Linux, extensions are installed AFAICT into the user's home directory.)

Date Modified	Username	Field	Change
2013-02-07 12:32	akaiser	New Issue
2013-02-07 12:32	akaiser	Status	new => assigned
2013-02-07 12:32	akaiser	Assigned To	=> jcfr
2013-02-07 12:58	jcfr	Target Version	=> Slicer 4.4.0
2013-02-07 13:07	jcfr	Note Added: 0007838
2014-04-22 15:53	jcfr	Relationship added	duplicate of 0003552
2014-04-22 15:54	jcfr	Duplicate ID	0 => 3552
2014-04-22 15:54	jcfr	Status	assigned => resolved
2014-04-22 15:54	jcfr	Fixed in Version	=> Slicer 4.4.0
2014-04-22 15:54	jcfr	Resolution	open => fixed
2014-04-23 05:53	matthew-woehlke	Note Added: 0011646
2014-09-17 22:57	jcfr	Status	resolved => closed