Google Summer of Code 2017

From FreeCAD Documentation
Revision as of 15:11, 13 January 2016 by Ickby (talk | contribs) (Ideas for Google Summer of Code 2016)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Google Summer of Code

Possible Mentors

Ickby Yorik

Implementation Ideas

1. Advance freecad test system: Provide functionality to do a file-based result comparision, for example allow to store a file with the expected document object structure together with the test case and provide a function to compare the test result with this expected structure. Multiple such comparators are possible and will make writing complex tests much easier. Also handling input files for tests and all the file storing could be automated. (I like this for the new part design as I recently noticed that the whole complexity of the workbench is very hard to handle, fixing one thing may break annother which worked few months back... we need to create more unit-tests.)

2. Topological Naming: With the new Part Design we further stress the freecad linking system, it is time to handle those more gracefully. I do have a few Ideas how to handle links in a mixed way, using occ's topological naming as well as a comparison approach. A student could at least start with implementation and provide the framework for us to finally handle chaning links.