Dev:WeeklyMeetingAgenda/2004-10-24th

The Conference dev meeting.

• . Python API <-> internals
  • Python replacement for C dev? Python scripts (bundled) should work on same level as 'normal' code. Michel wrote proposal for mirrorring internal from Blender in BPY one2one. See experimental page ImageRefactoring.
  • core functionality has to work at all times → strict control is necessary (+already enough work to do)
  • Python → prototyping new tools → implement in C when feasible (comp. SculpMesh by %MAINWEB%.TomMusgrove).
  • Python team should create 'specification/guidelines/documentation' on how exposing UI functionality through the BPY API is to be done. This to prevent rather exotic and hackish solutions.
  • UI level commands can be Pythonised. Proposal by Campbell B for working on Pythonising UI func. (Nathan L should search those Lost Patches).
• . Release status: currently b-con 3. Check stability of new features (everybody), UI tweaking (Matt E). Scripts that are going to be bundled need to be tested thoroughly and have scripts documented (page on CMS or wiki). Blender release could be announced on Python announcement ML
• . Project admins:
  • proposed:
    • Willian
  • module owners should be more visible as access points for new developers. (Currently see: http://www.blender3d.org/cms/Project_list.228.0.html)
• . Roadmap: after 2.34
  • Character anim (Ton + ... )
  • Softbodies (Jens O W, ... )
  • Generalising metaball architecture (Jiri H). Mesh governing structure, Ipos.
  • Booleans?

• • request for vector rendering

• • event system (Ton?)
  • image module refactoring (Michel S.)