[PD-dev] Refactoring Pure Data

carmen _ at whats-your.name
Mon Sep 11 20:12:42 CEST 2006


On Mon Sep 11, 2006 at 02:21:33PM +0200, Vincent Lordier wrote:
> Hi enthusiasts devs !
> 
> I want to work on pd's code readability and structure, only refactoring, not
> adding new features. (http://en.wikipedia.org/wiki/Refactoring)
> The final goal is to make PD easy to scale (desactivate MIDI, Audio,
> Network, some CoreLibs, ...)
> 
> 'We've got to undo the MIDI revolution!  said Miller'
> => Well, as far as I know, removing MIDI from PD's hairy code isn't as easy
> as "./configure --nomidi' make install ... yet !
> 
> There is quite a bit to do in this area, some of it is just renaming,
> indenting, some of it might be "cleaning out" stuff.h to separate clearly
> MIDI, Audio, engine, GUI and CoreLibs.
> Again, my goal is not to alter pd in its behavior (yet), nor optimizing
> anything (yet), just to improve readability and separation of modules.
> Any help on this and / or pointers to previous work is welcomed :)
> 
> I want to make it easier for anyone to get into the code, to maintain it and
> to address issues like portability (from embedded - PDa-like or even tinier
> - to bigger systems).
> 
> BUT my main problem right now is : on which version / branch should I work
> on ?

whichever you want. you cant work on the MAIN branch, since youre not g-d. if you work on the devel_0_39 branch yo might break it (it is currently used for DesireData and Vibrez, afaik). 

you might want to at least peak at the devel_0_39 branch, building with 'scons desire=1' since a lot of refactoring has already taken place, mainly in regards to GUI/engine seperation. i dont think anyone has taken on moving all the 'internals' to 'externals'. since the only thing differentiationg an internal and an external is the makefile, and where the source resides (As it is, many externals use private 'internal' headers)...





More information about the Pd-dev mailing list