> > i already tried to split up the engine communication from the drawing > > part .. > > > > the engine-part of gobj classes is PatcherGobj, which is derived from he > > base class, that is exposed from the py_nova module. the drawing part > > for ordinary objects is the GObjBox class ... > > Yeah, I saw a bit of this. I need to figure out how communication and > dispatching is working a bit better before I can contribute anything > useful to the discussion. How about creating a place on the wiki where > we can take notes about these things as time goes on? Sort of a working > architecture page.
an extended version of the stuff that i am currently writing for my bachelor thesis should be somehow put into the source repository ... unfortunately the files in ./doc are quite obsolete ... > > or maybe you want to port fiddle~? :) > > I think that might be a bit much for starting off. Fiddle uses an fft > though, so maybe I'll look into doing ffts next... yes ... a working fft framework would help for that ... some kind of wrapper for fftw/kissfft, whatever is available ... cheers, tim -- [EMAIL PROTECTED] ICQ: 96771783 http://tim.klingt.org The aim of education is the knowledge, not of facts, but of values William S. Burroughs
signature.asc
Description: This is a digitally signed message part
_______________________________________________ nova-dev mailing list [email protected] http://klingt.org/cgi-bin/mailman/listinfo/nova-dev http://tim.klingt.org/nova
