2015-12-22 12:51 GMT-02:00 katja katjavetter@gmail.com:
With the recent increased effort of testing, fixing and innovation there's an opportunity to redefine intentions and ambitions.
Totally agree, I guess we can just keep the idea that it is a library of clones in a generic approach that doesn't restrict to "4.5", I guess the mentioning of that version is because it was the current version at the time, not because it had to remain restrained to it...
So I think the subtitle description should just be
*a library of clones of Max/MSP objects*
Let's try to figure out a generic approach where backward compatibility doesn't conflict with MaxMSP compatibility and innovation, so anyone can contribute to the project according to their skill, interest and ambition.
Sure. Well, that makes it more generic and open to updates.
My proposal would be to sacrifice forward compatibility of older
versions if needed. Classes which pose the compatibility dilemma may be made to operate in multiple modes. Sometimes this can be achieved by message, and when the number or type of inlets / outlets are concerned (like average~) it can be achieved with creation arguments.
If we're discussing [average~], how about my idea of having a second right signal outlet as default? I think it's an easy and simple solution. Help file would explain how the left control outlet is for backwards compatibility. Done.
I became aware how big a project it really is. It could use the love and care of more people besides Alexandre and Fred Jan.
I'm seeing if I can find collaborators out there.
Cyclone (part of miXed) was unfortunately abandoned by it's original
author Krzysztof Czaja after 2005. The ambitions with this wonderful project were then in practice scaled down to fixing bugs in the alpha versions
You can see at the description that it had many ambitions indeed. We could edit the project like saying it was "meant to eventually become part of a much larger project, aiming at unification and standardization of computer musician's tools."
I guess we can edit that and rule it out, hehe...
Project description could tell more about current development, that it started back in the days of max/msp 4.5 and that it is now open to newer developments to keep up with latest versions of Max and such details.
I also owe this list a document from my research with a "To Do List", it's not like it'd be a huge thing, and we could also describe more about the scope of and focus of the project, which is not suppose to turn Pd into clone of Max, stuff like that.
Help files could tell up to which version an object is and give details of what it has or not as a clone in comparison to the original.
I could work on that on the help files.
cheers