[PD-dev] devel branch for 'externals'

[Thomas Grill]

Hi Hans-Christoph,
i like this idea very much.
I don't think i'm going to implement new features to flext in the near
future but rather optimize it and make it work better with Max/MSP
(thread-safety, compatibility with overdrive mode, timing problems etc.) -
i'd really like to calm down development and work towards a stable API with
a shared flext library to allow for small and efficient externals.
I'm grateful for any additional ideas (and significant new parts).

best greetings,
Thomas


> > It depends. Sometimes this is one of the advantages of CVs: That
> > someone else can quickly fix a small bug. This doesn't work for Thomas
> > Grill's externals of course, which are overwritten every night, IIRC,
> > but there read-only wouldn't make much sense anyways.
>
> flext is a great example actually.  Say I wanted to do more than just a
> bug fix, but add a significant feature to a part of flext.  I could
> commit my changes to the 'devel' branch, and still track Thomas'
> changes.  Then when my new feature is implemented to Thomas'
> satisfaction, he could incorporate it into his CVS.  This is what we
> are already doing with the pd source, so it  should work.  Since flext,
> etc. is changing quite a bit, that would mean more merging work, but
> for something like maxlib, it doesn't change much these days so a
> branch should be easy to maintain.