Add SegmentEditorSLIC

[AnnaPSQ]

New extension

• Extension has a reasonable name (not too general, not too narrow, suggests what the extension is for)
• Repository name is Slicer+ExtensionName
• Repository is associated with 3d-slicer-extension GitHub topic so that it is listed here. To edit topics, click the settings icon in the right side of "About" section header and enter 3d-slicer-extension in "Topics" and click "Save changes". To learn more about topics, read https://help.github.com/en/articles/about-topics
• Extension description summarizes in 1-2 sentences what the extension is usable (should be understandable for non-experts)
• Any known related patents must be mentioned in the extension description.
• If source code license is more restrictive for users than BSD, MIT, Apache, or 3D Slicer license then the name of the used license must be mentioned in the extension description.
• Extension URL and revision (scmurl, scmrevision) is correct, consider using a branch name (main, release, ...) instead of a specific git has to avoid re-submitting pull request whenever the extension is updated
• Extension icon URL is correct (do not use the icon's webpage but the raw data download URL that you get from the download button - it should look something like this: https://raw.githubusercontent.com/user/repo/main/SomeIcon.png)
• Screenshot URLs (screenshoturls) are correct, contains at least one
• Homepage URL points to valid webpage containing the following:
  • Extension name
  • Short description: 1-2 sentences, which summarizes what the extension is usable for
  • At least one nice, informative image, that illustrates what the extension can do. It may be a screenshot.
  • Description of contained modules: at one sentence for each module
  • Tutorial: step-by-step description of at least the most typical use case, include a few screenshots, provide download links to sample input data set
  • Publication: link to publication and/or to PubMed reference (if available)
  • License: We suggest you use a permissive license that includes patent and contribution clauses. This will help protect developers and ensure the code remains freely available. We suggest you use the Slicer License or the Apache 2.0. Always mention in your README file the license you have chosen. If you choose a different license, explain why to the extension maintainers. Depending on the license we may not be able to host your work. Read here to learn more about licenses.
  • Content of submitted s4ext file is consistent with the top-level CMakeLists.txt file in the repository (description, URLs, dependencies, etc. are the same)

[jcfr]

To improve readability and ensure that the number of completed or remaining tasks is properly reported, in the future, consider using [x] instead of [ x] for checkboxes:

-[ x] Repository name is Slicer+ExtensionName
+[x] Repository name is Slicer+ExtensionName

This will ensure the rendering works as expected:

Before	After

---

_{This comment was adapted from my GitHub saved replies, it is licensed under a Creative Commons Attribution 4.0 International License and you were welcome to reuse it.}

[AnnaPSQ]

Hello, I can't see my extension in the 3D Slicer Extension Catalog. Did i miss something or made a mistake ? Could you please give me some information about how can I proceed to make my extension available from the catalog ? Thank you very much for your answer, Have a good day, Anna Pasquier Le jeu. 28 juil. 2022 à 00:34, Jean-Christophe Fillion-Robin < ***@***.***> a écrit :

…

To improve readablity of future contribution, consider updating markdown description using [x] instead of [ x] for checkboxes. For example: - - [ x] Screenshot URLs (screenshoturls) are correct, contains at least one+ - [x] Screenshot URLs (screenshoturls) are correct, contains at least one This will ensure the rendering works as expected: Before After [image: image] <https://user-images.githubusercontent.com/219043/181420823-56016c92-b5f4-4872-9ad1-6d52bf33eae2.png> [image: image] <https://user-images.githubusercontent.com/219043/181421133-b822f00a-4ad9-4974-a060-6eba622eeafb.png> — Reply to this email directly, view it on GitHub <#1850 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASQDVOVW37HKELYHHC74PBLVWIEUDANCNFSM52HBC5PA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pieper]

Hi Anna -

The extension becomes part of the nightly extension build and package process once a pull request (PR) like this is merged in this repository. We don't have a formal schedule for reviewing these but there are several people who typically look when their schedule permits. Usually we wait until all the boxes in the checklist are checked to know that a PR is ready for review.

It would be great if you could address the unchecked items and let us know when things are ready to go or if you have any questions. Some I see, like the tutorial, you already have but it's not checked on the list.

Thanks,
Steve

[AnnaPSQ]

Hi Steve,
Thank you very much for your answer. I have now checked all the items ! I'll certainly come back to you with more questions when i update the extension.

Thank you for the time you devote to this project, it's really nice to be able to contribute so easily!

Anna

[jcfr]

Reviewing the content of the repository, here are few additional nitpicks that would help users discover and use your extension

• Remove the PDF and add instructions into a markdown file. This help review and reference the documentation without having to download a file.
• Update both the extension and the effect icons to be more descriptive (e.g by including the name)
• Reference sample dataset that the user may download to test the effect.

@lassoan may have useful feedback specific to the proposed editor effect ¹

Footnotes

1. https://github.com/AnnaPSQ/Slicer-SLICSegmentEditorEffect/tree/master/SegmentEditorSlic/SegmentEditorSegmentEditorSlicLib ↩

[jcfr]

@AnnaPSQ Did you have a chance to make progress and further improve the documentation ?

[jcfr]

@AnnaPSQ To move forward, let us know if you have any questions.

[AnnaPSQ]

Hello, I'm really sorry I forgot to answer your previous e-mails. I'm not working on this project anymore so don't have much time for it (it was the subject of my last Internship). I can try to find some time to do the documentation in the wanted format since it already exists in a pdf file on the repo. Thank you for the interest you show for this project ! Anna Pasquier Le mer. 15 nov. 2023 à 22:03, Jean-Christophe Fillion-Robin < ***@***.***> a écrit :

…

@AnnaPSQ <https://github.com/AnnaPSQ> To move forward, let us know if you have any questions. — Reply to this email directly, view it on GitHub <#1850 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASQDVORKNCNTY55N2QPXICDYEUUZJAVCNFSM52HBC5PKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBRGMZDKNZZGI3A> . You are receiving this because you were mentioned.Message ID: ***@***.***>