Topics to address during the workshop :
Monday 10 : How things currently work
- Jamoma Externals:
- development environments (Xcode, Cygwin/GCC/Make)
- essential C/C++ (walk-through of a simple extern like jcom.round)
- essential debugging (step-through of a simple extern)
- advanced explanation and step-through: how jcom.send and friends
work for global and local message passing
- The process for fixing a real bug. This one is from Nils:
only the very last created jcom.remote__meter__xyz is reporting.
e.g.
1. if you have created a jcom.remote_meter_1 and conneted it to a
jcom.meter~ .... the jcom.meter~ objects works fine.
2. now, if you create another jcom.remote , e.g. jcom.remote__meter__3
and connect it to a jcom.meter~.... the first created
jcom.remote__meter__1 stops working but the last created
meter works... and so on.....
Trond and I are thinking that there is an issue in the code for jcom.out.cppline 436-450.
- Walk through a merge and release
- Discuss Windows maintenance
- Discuss pattr-support
Tuesday 11 to Thursday 13 :
Discussing and designing the *Libs
- FunctionLib
- RampLib (should we split the RampLib in 2 ? -> FunctionLib and scheduling mode : sched/queue/signal/bang(as in bline)...etc...)
- units and Unitlibs
- have a look at how all this works with the SpatDIF draft we did in Bergen...
Discussing and implementing solutions for :
- modularity and communication/integration with other platforms, environments, and projects (e.g. Integra, Virage)
- namespaces, file naming conventions, messaging structure in general (global/local sends, slashes, wildcards...)
- organization of the stabilization and documentation : how to make Jamoma useable in real world's applications, for different kind of people ?
Other Development Topics:
- matrix/mixer module (or maybe it shouldn't actually be a module?) discuss
- implementation of remote audio, and also remote video etc.
- Jamoma timing infrastructure (Jamoma Clock, Jamoma Scheduler, etc.)
- Should we create our own typedefs, and if so what should they be? What about this:
UInt64, Float32, etc. ?
- Texture modules and generic functions (crop, alpha, brcosa...etc...), i.e. shaders and stuff...
- autonomy of jcom.hub/parameter... etc... (-> Pd port ?)
Thursday 13 evening : "movie-night" : presentation of participants' works documentations
Friday 14 : Presentation of the work done during the week to the "extended team", getting feedback from them....
Saturday 15 : Open workshop for Brussels Maxers
- General Presentation of Jamoma
• Using Jamoma modules
• Making Jamoma modules
- Case studies ?
