Yes, I noticed this the other day when I tried to use the ModuleWizard - would have been better to do everything at once in a branch before changing the trunk :-p

Sure. I could easily revert the changes. So that you/we have more time to improve the ModuleWizard.

That said, instruction could easily be updated to specify:

1) Create an extension folder having one file:

/path/to/NewExtension/CMakeLists.txt

with the following content:

cmake_minimum_required(VERSION 2.8.9)

#-----------------------------------------------------------------------------
if(NOT Slicer_SOURCE_DIR)
set(EXTENSION_NAME LoadableExtensionTemplate)
set(EXTENSION_HOMEPAGE "http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Extensions/LoadableExtensionTemplate")
set(EXTENSION_CATEGORY "Examples")
set(EXTENSION_CONTRIBUTORS "Jean-Christophe Fillion-Robin (Kitware)")
set(EXTENSION_DESCRIPTION "This is an example of extension bundling a loadable module")
set(EXTENSION_ICONURL "http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/Extensions/Testing/LoadableExtensionTemplate/LoadableExtensionTemplate.png?revision=21746&view=co")
set(EXTENSION_SCREENSHOTURLS "http://wiki.slicer.org/slicerWiki/images/4/42/Slicer-r19441-LoadableExtensionTemplate-screenshot.png")
endif()

#-----------------------------------------------------------------------------
if(NOT Slicer_SOURCE_DIR)
find_package(Slicer REQUIRED)
include(${Slicer_USE_FILE})
endif()

#-----------------------------------------------------------------------------

Add below your modules

add_subdirectory(NewModule)

#-----------------------------------------------------------------------------
if(NOT Slicer_SOURCE_DIR)
include(${Slicer_EXTENSION_CPACK})
endif()

2) Use ModuleWizard to integrate modules.

That first step could easily be done with an "ExtensionWizard.py", then step 2 would be done using "ModuleWizard.py"

It means we would have a clear separation between "Modules" and "Extensions".

The "ExtensionWizard" would simply asked for:
--target /path/to/folder (optional arg, by default current dir)
EXTENSIONNAME

Moving forward, the "ExtensionWizard" could also be extended to propose:

• github registration
• midas registration
• etc ...

Yep, I know how to do it but I don't have time right now ;)

The module wizard instructions have been updated to describe how to create extensions with multiple modules of different types.

http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/ModuleWizard

The current behavior isn't bad - people still need to do a little bit of hand editing, but since they are developers that's not bad.

Good point. Thanks for working on this.

To simplify, few days ago I created a new template named:
../Extensions/Testing/EmptyExtensionTemplate/

I didn't get a chance to commit it but that would simplify the documentation. What do you think ?

Moving forward, I was even thinking about adding a wizard hint to the template, something like:

<Wizard:add_subdirectory>

Yes, I almost created and committed an Extensions/Testing/GenericExtensionTemplate - probably would have been just like your EmptyExtensionTemplate ;)

But then as I was thinking about it, we probably don't need to do too much hand holding at this stage - if the only thing the developer needs to do is edit a few add_subdirectory commands they really have it pretty easy. I guess from my perspective once they have a working extension framework and can add arbitrary modules to it they have everything they need at that level. There are lots of other complicated tasks that we can simplify with a similar amount of effort (like adding more python documentation or something) so I figured we are in pretty good shape on this.

Of course if you want to further improve the documentation or templates that would be great!