Roadmap - Revision history

WikiSysop: /* Todo */

2008-04-23T13:45:32Z

Todo

WikiSysop: /* Todo */

2007-11-21T16:23:21Z

Todo

WikiSysop: /* Todo */

2007-11-19T12:42:56Z

Todo

WikiSysop: /* Todo */

2007-11-12T13:22:55Z

Todo

WikiSysop: /* Todo */

2007-11-01T11:02:53Z

Todo

WikiSysop: /* Todo */

2007-11-01T11:01:12Z

Todo

WikiSysop: /* Todo */

2007-11-01T10:59:43Z

Todo

WikiSysop: /* Todo */

2007-09-13T15:57:21Z

Todo

WikiSysop: /* Todo */

2007-09-03T10:57:35Z

Todo

WikiSysop: /* Todo */

2007-09-03T10:56:53Z

Todo

@@ Line 3: / Line 3: @@
 == Todo ==
 http://sourceforge.net/tracker/?group_id=181000
 * 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.
 * '''Modeller'''
@@ Line 20: / Line 14: @@
 ** 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)
 * '''Bugs'''

@@ Line 10: / Line 10: @@
 * 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'''

@@ Line 6: / Line 6: @@
 * Restore hybrid meshing algorithm making sure mesh faces conform - '''Not worth it...'''
 * Finish ABAQUS output and run a real case to ensure it works
-** Needs a way to define periodic boundary conditions
+** Needs a way to define periodic boundary conditions - '''Difficult to do for general cases'''
 * 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.

@@ Line 3: / Line 3: @@
 == Todo ==
 http://sourceforge.net/tracker/?group_id=181000
-* Add quadratic element support for mesh generator
+* Add quadratic element support for mesh generator - '''Done!'''
-* Restore hybrid meshing algorithm making sure mesh faces conform
+* Restore hybrid meshing algorithm making sure mesh faces conform - '''Not worth it...'''
 * 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.

@@ 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.
 * '''Modeller'''

@@ Line 13: / Line 13: @@
 * 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.
 * Package a version of python with the texgen installer to make things easier for the user. Perhaps have a separate installer for TexGen as a python library. - '''Done! Needs testing...'''
 * '''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
+** 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)
 * '''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

← Older revision		Revision as of 15:57, 13 September 2007
Line 39:		Line 39:
	** GetYarnLength doesn't seem to be working in python scripts		** 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)		** 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 10: / Line 10: @@
 * Write custom control for 2d weave and 3d weave wizard (will replace current toggle buttons on 2d weave wizard) - '''Done!'''
 * 3d weave wizard should contain top down view and cross section view. Cross section position selected from top down view and weave pattern controlled from cross section view. - '''Done!'''
-* Move pattern control out of the weave wizard and put it in a resizable window of its own.
+* Move pattern control out of the weave wizard and put it in a resizable window of its own. - '''Done!'''
 * 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.
 * Package a version of python with the texgen installer to make things easier for the user. Perhaps have a separate installer for TexGen as a python library. - '''Done! Needs testing...'''
 * '''Textile summary reporting tool'''

@@ Line 22: / Line 22: @@
 ** Properties: Areal density, Fibre linear density, fibre density - '''Done!'''
 ** Store fibre count + fibre diameter separately - '''Done!'''
-** Make gui window for viewing and setting properties
+** Make gui window for viewing and setting properties - '''Done!'''
 * '''Modeller'''
-** Implement the remaining cross section types, for hybrid will need a custom control
+** Implement the remaining cross section types, for hybrid will need a custom control - '''Done!'''
-** Update PythonConverter.cpp for power ellipse and hybrid sections
+** Update PythonConverter.cpp for power ellipse and hybrid sections - '''Done!'''
 ** 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