Dev:Source/Architecture/Event Refactoring

Existing (old) related but different? work on the Event Refactor idea

BlenderDev/GhostRefactoring BlenderDev/EventSystemRefactoring

Because this project impacts so many areas, the above pages should be referenced, and eventually merged into this page to reduce potential confusion. This is THE designated page for discussion about the Event Refactor goals and design.

Goals

The tentative and speculative goals of the Event Refactor are quite broad, and include, but are not limited to:

• Input device abstraction
  • Allowing for support of "virtual input devices" when necessary.
  • User settable keyboard and mouse bindings.
• Tool code abstraction and improvement
• Support for the development of macros
  • Support "loose-state" macros expressed in Python
  • Support for recording blender "filmstrip tutorials" for training purposes (limited event language, run through Python)
• Support for "Construction History" type features.
• Better OS independence and input conformity.
• Ability to run blender on multiple monitors.
• Support a move to a stateful UI for blender (allowing for better RenderMan integration)

Implementation Details

Those are some of the things I know about. More to come later. This is really just a stub for interested parties.

--jdpf 19:34, 28 February 2007 (CET)