Difference between revisions of "Roadmap"

From TexGen

Revision as of 11:02, 1 November 2007

Add quadratic element support for mesh generator
Restore hybrid meshing algorithm making sure mesh faces conform
Finish ABAQUS output and run a real case to ensure it works
Add ability to set textile name in the 2d weave wizard
Memory management, may want to think about how the textile and yarn classes are stored. Currently the yarn has no knowledge of its parent. This can be troublesome for some functions. It is often useful for the yarn to have access to information about the textile it belongs to. Consider adding a parameter to yarn which points back to its parent. This removes the ability for the yarn to be copied, however this is not such a big deal anyway. There are few cases when this is necessary or useful.
Work on geometry solver, use calculated displacements to modify geometry

Modeller
- Popup menu in the outliner when right clicking on a yarn to assign sections and whatnot (could also enable the pop-up in the main render window) - then remove the buttons on the modeller page to clean things up a bit
- Have option to see repeat vectors graphically along with some repeated yarns
- Do sorting based on camera position for transparency
- Box selection (paraview have made a plugin for this)
- Layers so that picking of nodes belonging to specific yarns made easier
- Add undo ability
- Make sure python code is generated for all important operations (e.g. python code should be generated when mouse is released from a move operation)
- Add ability to place an image in the background so that it can be used to fit geometry to, probably want orthographic projection for this and ability to switch layers on/off

Bugs
- GetYarnLength doesn't seem to be working in python scripts
- Picking in the modeller seems screwed up sometimes (need to click a bit above desired position)
- White lines appear in the 3d modelling wizard

@@ Line 8: / Line 8: @@
 * Add ability to set textile name in the 2d weave wizard
 * Memory management, may want to think about how the textile and yarn classes are stored. Currently the yarn has no knowledge of its parent. This can be troublesome for some functions. It is often useful for the yarn to have access to information about the textile it belongs to. Consider adding a parameter to yarn which points back to its parent. This removes the ability for the yarn to be copied, however this is not such a big deal anyway. There are few cases when this is necessary or useful.
+* Work on geometry solver, use calculated displacements to modify geometry
 * '''Modeller'''