Andras Lasso

This issue has come up here: https://github.com/Slicer/Slicer/pull/6417#issuecomment-1150568993 Currently, we cannot distinguish between optional and required dependencies, so we can either consider all dependencies are optional, or all dependencies are required....

Yes, these issues still persist. They are due to that in current Slicer source code some dynamically created strings are not marked as translatable and we would need to implement...

Non-translatable strings: - [ ] Color table names are not translatable (see in Volumes module / Display section) Documentation improvements: - [ ] Add documentation for Data Probe (describe what...

- [x] Some strings appear in weblate but are actually non-translatable. This includes string properties in .ui files, such as `nodeTypes` in `qMRMLNodeComboBox`.

The new Girder-based extensions server backend can provide dependency information, so this feature should be fairly easy to implement now. Listing direct dependencies is trivial, but if the frontend downloads...

Is this the same as this issue? https://github.com/Slicer/Slicer/issues/5753

Here is an overview of the filters that make up processing pipeline for vector volumes (I've created this a couple of years ago, so I don't remember what the colors...

Having a general mechanism would be good. The …_ITK_ITK_... duplication is not very nice (and it would happen often, as variable names are often prefixed by the library name). Maybe...

Is the double-underscore a typo? I would not use it (it is typically reserved for machine use). EP is used very commonly for "external project". See CMake (EP_PREFIX, EP_BASE, …...

Yes, I agree that @phcerdan's syntax is simpler, but passing several parameters as a string blob would make it hard to interpret the values. For example, sometimes we set default...