sight-doc issueshttps://git.ircad.fr/sight/sight-doc/-/issues2023-03-03T16:39:31+01:00https://git.ircad.fr/sight/sight-doc/-/issues/45(doc): write Tuto16SceneQt3D doc2023-03-03T16:39:31+01:00Romain MANCIAUX(doc): write Tuto16SceneQt3D dochttps://git.ircad.fr/sight/sight-doc/-/issues/44(doc): write Tuto15Matrix doc2023-03-03T16:39:31+01:00Romain MANCIAUX(doc): write Tuto15Matrix dochttps://git.ircad.fr/sight/sight-doc/-/issues/43(doc): write Tuto14Gui doc2023-03-03T16:39:31+01:00Romain MANCIAUX(doc): write Tuto14Gui dochttps://git.ircad.fr/sight/sight-doc/-/issues/42(doc): write Tuto08MesherWithGenericScene doc2023-03-03T16:39:31+01:00Romain MANCIAUX(doc): write Tuto08MesherWithGenericScene dochttps://git.ircad.fr/sight/sight-doc/-/issues/40(doc): write Tuto11Picker doc2023-03-03T16:39:31+01:00Romain MANCIAUX(doc): write Tuto11Picker dochttps://git.ircad.fr/sight/sight-doc/-/issues/23(core): write a section dedicated to matrix naming and notation2023-03-03T16:39:31+01:00Kevin GAUDETkevin.gaudet@ihu-strasbourg.eu(core): write a section dedicated to matrix naming and notation### Description
There is no strict naming convention for matrices and it is often done terribly.
Having such a convention would help us to better understand linear algebra thereby making reviews a lot easier.
### Proposal
The notatio...### Description
There is no strict naming convention for matrices and it is often done terribly.
Having such a convention would help us to better understand linear algebra thereby making reviews a lot easier.
### Proposal
The notation should be similar to what was already described in [this document](/uploads/ac37b5453c224b613411b3fc154eb143/MatricesNotations.odt).
Transform matrices should mention their source and destination spaces in their name. Perhaps like this:
`m_destination_source` (or `matrixDestinationSource`)
Writing the source at the end is helpful for matrix multiplication.
e.g.: `m_a_b * m_b_c = m_a_c`https://git.ircad.fr/sight/sight-doc/-/issues/4(core): add a document for services config and factory extension points2023-09-20T11:27:47+02:00Flavien BRIDAULTfbridault@ircad.fr(core): add a document for services config and factory extension pointsThe following discussion from FW4SPL/fw4spl-doc!23 should be addressed:
- [ ] @fbridault started a [discussion](https://gitlab.lan.local/FW4SPL/fw4spl-doc/merge_requests/23#note_38358): (+4 comments)
> Is that for a future MR or d...The following discussion from FW4SPL/fw4spl-doc!23 should be addressed:
- [ ] @fbridault started a [discussion](https://gitlab.lan.local/FW4SPL/fw4spl-doc/merge_requests/23#note_38358): (+4 comments)
> Is that for a future MR or did you plan to do this now ?sight 24.0https://git.ircad.fr/sight/sight-doc/-/issues/5(core): add an example of how to create an activity.2023-03-03T16:39:32+01:00Emilie WERNERTemilie.harquel@ihu-strasbourg.eu(core): add an example of how to create an activity.### Description
Add an example of how to create or use an activity. Currently there is only a basic description of the XML description of an activity.
### Proposal
Explain how to create and use an activity in a complete application.
-...### Description
Add an example of how to create or use an activity. Currently there is only a basic description of the XML description of an activity.
### Proposal
Explain how to create and use an activity in a complete application.
- create the activity in XML
- how to connect the services in the XML (SDynamicView, SActivityWizard, SCreateActivity, ...)
### Links / references
Existing documentation for Activities: https://fw4spl.readthedocs.io/en/dev/SAD/src/SDM-SAD-Activities.htmlhttps://git.ircad.fr/sight/sight-doc/-/issues/7(core): name convention for the Activities2023-03-03T16:39:31+01:00Thibaut SCHMITT(core): name convention for the Activities### Description
Currently there is no naming convention for the Activities.
We can find names like:
```
<id>2DVisualization</id>
<id>3DVisualization</id>
<id>VolumeRendering</id>
<id>SeshatActivity</id>
<id>Processing</id>
<id>DicomFil...### Description
Currently there is no naming convention for the Activities.
We can find names like:
```
<id>2DVisualization</id>
<id>3DVisualization</id>
<id>VolumeRendering</id>
<id>SeshatActivity</id>
<id>Processing</id>
<id>DicomFiltering</id>
<id>mesherActivity</id>
```
CamelCase or not ? Activity at the end or not ?
### Proposal
Personally I would say `CamelCaseActivity`Romain MANCIAUXRomain MANCIAUXhttps://git.ircad.fr/sight/sight-doc/-/issues/8(docs): add descriptions of samples2023-03-03T16:39:31+01:00Romain MANCIAUX(docs): add descriptions of samples### Description
* Add descriptions of samples
* Also add screenshots of the sample with some details
### Proposal
Example of screenshot:
![ExOpenvslam](/uploads/b737792c0c4448917c5f1c096e64cdfe/ExOpenvslam.png)### Description
* Add descriptions of samples
* Also add screenshots of the sample with some details
### Proposal
Example of screenshot:
![ExOpenvslam](/uploads/b737792c0c4448917c5f1c096e64cdfe/ExOpenvslam.png)https://git.ircad.fr/sight/sight-doc/-/issues/11(doc): write Tuto10LaunchBasicConfig doc2023-09-20T11:27:47+02:00Flavien BRIDAULTfbridault@ircad.fr(doc): write Tuto10LaunchBasicConfig docsight 24.0https://git.ircad.fr/sight/sight-doc/-/issues/12(doc): write Tuto12Scene2D doc2023-09-20T11:27:47+02:00Flavien BRIDAULTfbridault@ircad.fr(doc): write Tuto12Scene2D docsight 24.0