Difference between revisions of "Roadmap"

From TexGen
Jump to navigationJump to search
 
(18 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
== Todo ==
 
== Todo ==
 
http://sourceforge.net/tracker/?group_id=181000
 
http://sourceforge.net/tracker/?group_id=181000
−
* Add TexGen icon as bookmark for web browsers - '''Done!'''
 
−
* Export to VTK files - '''Done!'''
 
−
* Export to STL files - '''Done!'''
 
−
* Add function to test if Repeat vector corresponds to yarn end pos - start pos - '''Done!'''
 
 
* Add ability to set textile name in the 2d weave wizard
 
* Add ability to set textile name in the 2d weave wizard
−
* Write custom control for 2d weave and 3d weave wizard (will replace current toggle buttons on 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.
 
* 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.
 
−
 
−
* '''Textile summary reporting tool'''
 
−
** Create a new class containing information about the textile. - '''Done!'''
 
−
** Store all information in SI units, have function to set values. Each function should have a second parameter that specifies what unit it is given in. - '''Done!'''
 
−
** If information is not given it should be clear that it is not (i.e. set to 0 for example only if 0 would not be a valid value) - '''Done!'''
 
−
** The units in which the textile is measured in will need to be specified because this will impact upon volume calculated, etc... - '''Done!'''
 
−
** Properties: Areal density, Fibre linear density, fibre density - '''Done!'''
 
−
** Store fibre count + fibre diameter separately - '''Done!'''
 
−
** Make gui window for viewing and setting properties
 
  
 
* '''Modeller'''
 
* '''Modeller'''
−
** Implement the remaining cross section types, for hybrid will need a custom control
 
 
** 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
 
** 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
 
** Have option to see repeat vectors graphically along with some repeated yarns
−
** Make sure everything is sound with domains
 
 
** Do sorting based on camera position for transparency
 
** 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
 
** Layers so that picking of nodes belonging to specific yarns made easier
 
** Add undo ability
 
** 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)
 
** 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'''
 
* '''Bugs'''
−
** When user clicks create textile from the modeller and then presses cancel, a new textile is created anyway. - '''Fixed'''
+
** GetYarnLength doesn't seem to be working in python scripts
−
** When deleting last node on a yarn the yarn surface no longer visible... - '''Unable to reproduce'''
+
** Picking in the modeller seems screwed up sometimes (need to click a bit above desired position)
 +
** White lines appear in the 3d modelling wizard

Latest revision as of 13:45, 23 April 2008

ChangeLog

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
    • 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)
  • 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
Retrieved from "http:///index.php?title=Roadmap&oldid=1828"