Difference between revisions of "Roadmap"

From TexGen
Jump to navigationJump to search
 
(48 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== ChangeLog ==
 
== ChangeLog ==
−
* '''Core'''
 
−
** Introduced new 'ObjectContainer' class to ease memory handling
 
−
** Fixed a bug with saving to XML file
 
−
** Improved SectionMeshRectangular to deal with circular-like cross sections
 
−
** Changed AssignDomain to take a const reference.
 
−
** Added SetThickness function to CTextileWeave
 
−
** If yarn interpolation function, resolution, section and section mesh are not defined defaults are used now instead of giving error messages
 
−
 
−
* '''Renderer'''
 
−
** Extended CRenderer::Start method to include the ability to render window size
 
−
** Added function to take screenshot
 
−
 
−
* '''GUI'''
 
−
** Updated to be compatible with wxWidgets 2.8
 
−
** Updated GUI to work with wxWidgets unicode build
 
−
** Introduced new modeller page
 
−
 
−
* '''General'''
 
−
** Added twill weave example script
 
−
** Created unit tests for GridFile.py, FlowTex.py, WiseTex.py and TexGenv2.py
 
−
** Updated TexGenv2.py to read Up vectors. However there is still no support for varying cross section definition.
 
−
** Added tolerance to find PointInsideYarn
 
−
** Updated lenticular cross section to allow a distortion lenticular cross section
 
−
** Changed the behaviour of FlowTex.py in response to request from Bart
 
−
** Fixed problem with calling CTexGenRenderer::ResetCamera(XYZ) from python.
 
−
** Cleaned up C++ example programs
 
−
** Changed doxyfile to generate windows .chm help file and included in the installer
 
−
** Added option to create static builds
 
−
 
  
 
== Todo ==
 
== Todo ==
 
http://sourceforge.net/tracker/?group_id=181000
 
http://sourceforge.net/tracker/?group_id=181000
−
* Export to VTK files
+
* Add ability to set textile name in the 2d weave wizard
−
* Export to STL files
+
* 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.
−
* Add overloaded constructors for CFibreDistribution class
+
 
−
* Textile summary reporting tool
 
−
* Add function to test if Repeat vector corresponds to yarn end pos - start pos
 
 
* '''Modeller'''
 
* '''Modeller'''
−
** Add ability to create/delete/duplicate yarns - '''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
−
** Add ability to create/delete yarn nodes - '''Done'''
 
−
** Outliner (Tree control showing yarns and nodes) - '''Done'''
 
−
** See preview of cross section in cross-section dialog box - '''Done'''
 
−
** Ability to set repeat vectors - '''Done'''
 
−
** Size of widgets, nodes and yarn path should depend on size of window - '''Done'''
 
−
** Perhaps add option to trim to domain - '''Done'''
 
−
** Add a window to select snapping distance - '''Done'''
 
−
** Option to type in textile name on create new textile - '''Done'''
 
−
** Popup menu in the outliner when right clicking on a yarn to assign sections and whatnot
 
 
** 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'''
 +
** 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

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"