– Should the ViewMap only contain visible lines or all lines?
(Currently all lines)
– If all lines, should we compute the Quantitative Invisibility or just a binary visibility?
(currently both are possible. Some technical styles depend on the QI information)
– What types of feature lines should be in the ViewMap?
Currently, there are Silhouettes (smooth or non smooth, depending on the vertices normals), crease edges
and suggestive contours. This choice has an impact on the complexity of the ViewMap and potentially its robustness.
– Should we support chaining ?
(Currently, yes. Makes it harder to potentially support a solution to temporal coherence).
[ Update – 05/07/2008 ]
– How to replace the swig dependency? One difficulty that occurred to me is that Freestyle heavily relies on the use of “directors” that allow cross-language polymorphism. For instance, the operators (eg select, chain etc… ) are implemented in C++ and take as argument various rules (eg predicates, shaders, …) whose base classes are defined in C++ but whose implementations can be either in C++ or in Python. Directors make possible a python implementation . The solution would be to either emulate a similar feature or to break the style module down in a way that doesn’t require cross-language polymorphism.