Tutorial reorganization
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Review the current Chapter 1 and Chapter 7 tutorial organization alongside the listed tutorial entries. Determine a proposed grouping for the entries and document the agreed reorganization; done means the chapter structure and tutorial placement have been settled and updated.
Written by the indexing model from the issue text.
Description
Chapter 7 is getting a bit out of control. Meanwhile, Chapter 1 is simultaneously an intro chapter and a "viewer features" chapter. Let's use this issue to discuss some reorganization. For reference, here're the current tutorial entries (that we have code for; so this includes ones that have missing documentation):
Tetgen
FastAutomaticSkinningTransformations
SignedDistance
MeshImplicitFunction
SweptVolume
BiharmonicDeformation
Boolean
GaussianCurvature
ExplodedView
SLIM
HarmonicParam
NRosyDesign
ViewerMenu
CSGTree
AsRigidAsPossible
Events
ScreenCapture
BoundedBiharmonicWeights
CurvatureDirections
MarchingCubes
LaplaceEquation
Decimation
LSCMParam
MEX
ShapeUp
Planarization
AmbientOcclusion
Laplacian
WindingNumber
Statistics
Gradient
GeodesicDistance
BiharmonicCoordinates
Kelvinlets
SCAF
MultipleViews
Triangle
DirectDeltaMush
FileIO
IterativeClosestPoint
FastWindingNumber
MIQ
DualQuaternionSkinning
Picking
MultipleMeshes
MarchingTets
DrawMesh
ARAPParam
Colors
EigenDecomposition
Matlab
Slice
QuadraticProgramming
FacetOrientation
Overlays
Sort
FrameField
BlueNoise
LinearEqualityConstraints
Normals
Subdivision
DataSmoothing
HeatGeodesics
ImGuizmo
PolyharmonicDeformation
Serialization
- Dominant language
- Python
- Stars
- 5
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libigl/libigl.github.io
-
Missing tutorial entry : 112_SelectionMay be free again @alecjacobson claimed this 2035 days ago, and no pull request is open. Open
libigl/libigl.github.io#52 · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
libigl/libigl.github.io#41 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
libigl/libigl.github.io#40 · 1 comment ·
-
Missing tutorial entry: 720_BlueNoiseMay be free again @alecjacobson claimed this 2191 days ago, and no pull request is open. Open
libigl/libigl.github.io#39 · 1 assignee ·
-
Missing tutorial entry: 718_IterativeClosestPointMay be free again @alecjacobson claimed this 2192 days ago, and no pull request is open. Open
libigl/libigl.github.io#38 · 1 assignee ·
All issues in libigl/libigl.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
qgis/QGIS-Plugins-Website#459 ·
-
bug severity:medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
bot-found bug priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
madenvel/KalinkaPlayer#179 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ls1intum/edutelligence#1098 ·
Maintainers usually reply within 1 day