This has been implemented (as a module) at https://github.com/mwoehlke-kitware/Slicer/tree/3603-in-slicer-extension-wizard.

Note: It is also possible to use SlicerWizard directly via the interactor, e.g.:

from SlicerWizard import TemplateManager
tm = TemplateManager()

add templates

extensionPath = tm.copyTemplate(dest, "extensions", "default", "MyExtension")

Few remarks / questions:

• Destination of new extension: Could the default be the home directory ?
• Associate an icon with the wizard
• Add a link/button in the extension manager allowing to switch to the extension wizard ?
• In the settings, what is the difference between "Additional template paths" and the two other entries ?

// --------------------------------------------------------------
On my workstation, I got the following message:

add generic template paths None
add paths None for extensions
Traceback (most recent call last):
File "/home/jchris/Projects/Slicer-1-SuperBuild-Qt485/Slicer-build/lib/Slicer-4.3/qt-scripted-modules/ExtensionWizard.py", line 63, in init
self.setupTemplates()
File "/home/jchris/Projects/Slicer-1-SuperBuild-Qt485/Slicer-build/lib/Slicer-4.3/qt-scripted-modules/ExtensionWizard.py", line 185, in setupTemplates
for path in paths:
TypeError: 'NoneType' object is not iterable

Warning, the module "ExtensionWizard" has no widget representation
Warning, there is no UI for the module "ExtensionWizard"

=> Seems the built-in template are not discovered.

// -----------------

I added a:

if paths is None:
continue

to the ExtensionWizard at line 184 to move further.

// -----------------

After clicking on "Create Extension" ... no templates where listed. I manually added:

/path/to/Slicer/Utilities/Templates/Extensions/Default
/path/to/Slicer/Utilities/Templates/Extensions/SuperBuild

to "Additional template paths for extensions"

and

/path/to/Slicer/Utilities/Templates/Modules/CLI
/path/to/Slicer/Utilities/Templates/Modules/Loadable
/path/to/Slicer/Utilities/Templates/Modules/Scripted

to "Additional template paths for modules"

After restarting, only the "Superbuild" type of extension was listed and clicking create lead to an exception:

Traceback (most recent call last):
File "/home/jchris/Projects/Slicer-1-SuperBuild-Qt485/Slicer-build/lib/Slicer-4.3/qt-scripted-modules/ExtensionWizard.py", line 238, in selectExtension
xd = SlicerWizard.ExtensionDescription(sourcedir=path)
File "/home/jchris/Projects/Slicer-1-SuperBuild-Qt485/Slicer-build/bin/Python/SlicerWizard/ExtensionDescription.py", line 125, in init
p = ExtensionProject(sourcedir)
File "/home/jchris/Projects/Slicer-1-SuperBuild-Qt485/Slicer-build/bin/Python/SlicerWizard/ExtensionProject.py", line 50, in init
raise IOError("CMakeLists.txt not found")
IOError: CMakeLists.txt not found

/path/to/Slicer/Utilities/Templates/Extensions/Default
/path/to/Slicer/Utilities/Templates/Extensions/SuperBuild
/path/to/Slicer/Utilities/Templates/Modules/CLI
/path/to/Slicer/Utilities/Templates/Modules/Loadable
/path/to/Slicer/Utilities/Templates/Modules/Scripted

None of these contain templates. They are templates. You should add /path/to/Templates/Extensions and /path/to/Templates/Modules to their respective categories. Or, better, add /path/to/templates to the generic templates paths.

I pushed a fix for the empty paths; thanks. I'm not entirely sure why this is happening, however; the list of sub-keys should be empty, so a None should only happen in case of an explicit empty value. But of course we should guard against that anyway...

About not finding the "built in" templates, I believe we are still missing install rules, and we can't go looking in the source directory (because end users won't have source). That should be fixed, of course, but for the moment I've been treating it as a separate issue.

For some reason, [1] made me think the template were also installed. Can you add install rules for the template ?

My understanding is that:

1) the section "Additional template paths" is here in case the user want to use an existing extension as model

2) the section "Additional template paths for extensions": Contains the template for just the extension "skeleton": Superbuild or default

3) the section "Additional template paths for modules": Contains the templates for just modules (CLI, Loadable, Scripted, ... or any module the user whis to add)

Is there a way to consolidate (1) and (2) so that the user is presented with only these lists:

Additional template paths for extensions
Additional template paths for modules

[1] https://github.com/mwoehlke-kitware/Slicer/commit/e9db155def891e46b91262cb665b7d6bcce6dd2a

It's always possible my memory is out of date :-).

Destination of new extension: Could the default be the home directory ?

Yes. However, I'm dubious of making such a change. It is one click to get to the home directory, and the current default is "the current directory", which, at least on KDE, is effectively the last directory used in a file dialog. If one creates several extensions in the same place, this is quite convenient. If the home directory is forced, and the user is creating extensions somewhere else, it will require more effort to select the same directory over and over.

This is not an unusual behavior for such dialogs (e.g. kwrite's open dialog works this way also).

Few remarks related to topic "3603-in-slicer-extension-wizard" (d7db914ef6) [1]

After creating a package, I was able to use the wizard :) out of the box. The template were all available and everything went really smoothly. Great works.

Before integrating, this one should be addressed:

• Add command/target to copy template into the Slicer share directory associated with the build tree.

These remarks can be addressed later on:

• After creating an "Default" extension with a "scripted" module, the wizard ask the user if he would like to load it. This is very nice. Would it be possible to (1) indicate to the user what are the path of the scripted modules and explain that the user can edit them. and (2) ask him if he would like to load the module right way.

• Add a "publish" and a "contribute" actions allowing to respectively publish on github and contribute to the extension index.

• MetaData -> Contributors: Remember the last "first" contributor used to create an extension and use it when creating a new one.

• MetaData -> Category: Autocomplete with list of existing category

[1] https://github.com/mwoehlke-kitware/Slicer/tree/3603-in-slicer-extension-wizard

Add command/target to copy template into the Slicer share directory associated with the build tree.

This is already done by r23227. Is it not working?

Add a "publish" and a "contribute" actions allowing to respectively publish on github and contribute to the extension index.

I believe this is (or should be?) covered by 0003606?

Add command/target to copy template into the Slicer share directory associated with the build tree.

Sorry; misread. A fix has been pushed to the branch and this should be working now.

Works great. Please integrate 3603-in-slicer-extension-wizard and REBASE-wizard-launcher

This is implemented in r23263 - r23293.

The "Add selected modules to search path" feature lead to error ... see below for step to reproduce.

Start Slicer -> Modules -> ExtensionWizard -> Create Foo extension, added Bar scripted module.

Then, check the option "Add selected module to search path", the following error happen:

Traceback (most recent call last):
File "/home/jchris/Projects/Slicer-1-SuperBuild-Qt485/Slicer-build/lib/Slicer-4.3/qt-scripted-modules/ExtensionWizard.py", line 291, in selectExtension
self.loadModules(path)
File "/home/jchris/Projects/Slicer-1-SuperBuild-Qt485/Slicer-build/lib/Slicer-4.3/qt-scripted-modules/ExtensionWizard.py", line 321, in loadModules
rawSearchPaths = list(settings.value("Modules/AdditionalPaths"))
TypeError: 'NoneType' object is not iterable

The proposed fixe:
https://github.com/mwoehlke-kitware/Slicer/tree/fix-wizard-settings-list-bug

works well. I tested on linux and I confirm that the error doesn't show up. Looks good to integrate.

Thanks for the report. The issue in #0012006 is fixed in r23302.