|
|
| Line 1: |
Line 1: |
| | <noinclude>{{documentation/versioncheck}}</noinclude> | | <noinclude>{{documentation/versioncheck}}</noinclude> |
| − | Think of the ExtensionsIndex as a repository containing a list of [[Documentation/{{documentation/version}}/Developers/Extensions/DescriptionFile|extension description file]]s <code>*.s4ext</code> used by the Slicer [[Documentation/{{documentation/version}}/Developers/Extensions/BuildSystem|extensions build system]] to build, test, package and upload [[Documentation/{{documentation/version}}/Extensions/Description|extension]]s on the [[Documentation/{{documentation/version}}/Developers/Extensions/Server|extensions server]].
| |
| | | | |
| − | Once uploaded on an [[Documentation/{{documentation/version}}/Developers/Extensions/Server|extensions server]], within Slicer, [[Documentation/{{documentation/version}}/Extensions/Description|extension]]s can be installed using the [[Documentation/{{documentation/version}}/SlicerApplication/ExtensionsManager|extensions manager]].
| + | {{documentation/banner |
| − | | + | | text = [https://slicer.readthedocs.io/en/latest/developer_guide/extensions.html#extensions-index This page has been moved to read-the-docs.] |
| − | The [[Documentation/{{documentation/version}}/Extensions/Catalog|extensions catalog]] provides Slicer users with a convenient way to access the [[Documentation/{{documentation/version}}/Extensions/Description|extension]]s previously uploaded.
| + | | background-color = 8FBC8F }} |
| − | | |
| − | There are multiple branches on the ExtensionsIndex:
| |
| − | | |
| − | * <code>master</code>: This branch contain description files of extensions that will be built against Slicer nightly.
| |
| − | * [...]
| |
| − | * <code>{{documentation/currentversion}}</code>: This branch contain description files of extensions that will be built against latest Slicer {{documentation/currentversion}} available patch release.
| |
| − | | |
| − | The reasoning behind this approach is that since both the Slicer API and ABI associated with Slicer base libraries are changing often, compatibility of the extensions available for download is guaranteed by building extensions against every Slicer revisions.
| |
| − | | |
| − | It means that developer willing to have their extensions available on the different versions of Slicer will have to submit pull requests for each version.
| |
