[Bf-committers] Transform Refactoring
zaphar at gmail.com
Fri Sep 17 16:06:05 CEST 2004
> >> - What I really miss is the target & result of this
> >> work... what is the aim?
> > Semester seems to start slowly despite mainly heavy
> > courses, so I should have time to start laying out the
> > ground work (conversion and pre transform, numerical
> > handling and probably tackle one of the easy
> > transformation (scale or grab)) in the next week.
> > Could be totally ready for the conference, but that
> > depends entirely on school workload.
> I didn't mean scheduling, I mean functional targets to illustrate &
> market your work! :)
> Targets could be like:
> - put blender transform() tools in separate C file, with documented API
> - restructure the long code into manageable & understandable
Hear hear!! lol
> - enable transform() functionality for other tools too, like 3d
> transform-widgets, python, etc. This by eliminating the sub-loops and
> make it an 'event handle'
> - provide access to transforms based on vertex-normals, face-normals
> (for extrusions for example)
> For large code restructure projects it works well to not only have
> technical targets (getting code back in control) but also clearly
> define targets that exceed the current functional level and shows that
> the new code will be future proof for exciting development.
> Or in other words; what's in it for our poor users! :)
More information about the Bf-committers