<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1456265599973_5763">I don't see why everyone is discussing names when we haven't even settled <br></div><div id="yui_3_16_0_1_1456265599973_7515" dir="ltr">the issue of bracket placement.</div><div id="yui_3_16_0_1_1456265599973_5764"><br></div><div id="yui_3_16_0_1_1456265599973_5765">-Jonathan</div><div id="yui_3_16_0_1_1456265599973_5766"><span id="yui_3_16_0_1_1456265599973_7525">ae85b0319a14998c24b317d7e9de8352</span></div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"><font face="Arial" size="2"> On Tuesday, February 23, 2016 4:59 PM, Miller Puckette <msp@ucsd.edu> wrote:<br></font></div> <br><br> <div class="y_msg_container">I think it's wisest to leave cyclone as it is (except for maintenance updates)<br clear="none">and, if you want to write objects for compatibility with newer versions of<br clear="none">Max simply start another library. It won't be any trouble for people to<br clear="none">install both of them, and the cyclone code is probably best left alone (as<br clear="none">is much of Pd) just because it's old and you wouldn't want to be stuck with<br clear="none">old ways of doing things.<br clear="none"><br clear="none">Also, the 'name 'cyclone', although witty, has an unfortunate resonance for<br clear="none">certain Europeans... I think it's best left alone.<br clear="none"><br clear="none">cheers<br clear="none">Miller<br clear="none"><br clear="none">On Tue, Feb 23, 2016 at 06:46:29PM -0300, Alexandre Torres Porres wrote:<br clear="none">> I'm seconding Dan on this, name ideas was something being proposed to me<br clear="none">> and all before Fred shared his intention to stop working on "cyclone". I<br clear="none">> didn't even liked the idea of forking cyclone then, the reason being that<br clear="none">> there was no significant change for for projects, one only being able to be<br clear="none">> updated...<br clear="none">> <br clear="none">> <br clear="none">> now, from a previous thread<br clear="none">> <br clear="none">> 2016-02-20 15:57 GMT-02:00 Matt Barber <<a shape="rect" ymailto="mailto:brbrofsvl@gmail.com" href="mailto:brbrofsvl@gmail.com">brbrofsvl@gmail.com</a>>:<br clear="none">> <br clear="none">> > If a Max 4.6 compatibility library is really necessary, perhaps that could<br clear="none">> > be the fork with the new name.<br clear="none">> ><br clear="none">> <br clear="none">> I agree to Matt on this too, but with the remark that Max 4.6 compatibility<br clear="none">> would also be present in the updates and further development of cyclone<br clear="none">> <br clear="none">> keeping it simple, the whole issue camos with some of us wanting to<br clear="none">> collaborate and work on updates of cyclone, and the current maintainer<br clear="none">> having issues with it, it's not that he didn't want to spend his time<br clear="none">> working on it, more like he was against that others would help him do that.<br clear="none">> <br clear="none">> do we really need to fork in order to update a library keeping its original<br clear="none">> goal?<br clear="none">> <br clear="none">> I'm ok with whatever the community think it's best. I already started<br clear="none">> working a lot on this and now I'm just on it, 20 new objects in the way, a<br clear="none">> whole revision of all help files going on, it's happening...<br clear="none">> <br clear="none">> cheers<br clear="none">> <br clear="none">> 2016-02-23 18:08 GMT-03:00 Dan Wilcox <<a shape="rect" ymailto="mailto:danomatika@gmail.com" href="mailto:danomatika@gmail.com">danomatika@gmail.com</a>>:<br clear="none">> <br clear="none">> > If neither krzysztof not Fred plan to continue development, why can’t it<br clear="none">> > continue under the same name? (Keeping attribution of course!) I’d argue<br clear="none">> > multiple libraries is more confusing to the user especially when they all<br clear="none">> > provide roughly the same functionality but the main one is now very out of<br clear="none">> > date. That, plus the fact that urging people to use [declare -lib cyclone]<br clear="none">> > now requires urging people to do a batch find/replace for “cyclone” when,<br clear="none">> > again, the functionality is the same.<br clear="none">> ><br clear="none">> > --------<br clear="none">> > Dan Wilcox<br clear="none">> > @danomatika <<a shape="rect" href="https://twitter.com/danomatika" target="_blank">https://twitter.com/danomatika</a>><br clear="none">> > danomatika.com<br clear="none">> > robotcowboy.com<br clear="none">> ><br clear="none">> > On Feb 23, 2016, at 1:32 PM, <a shape="rect" ymailto="mailto:pd-list-request@lists.iem.at" href="mailto:pd-list-request@lists.iem.at">pd-list-request@lists.iem.at</a> wrote:<br clear="none">> ><br clear="none">> > i therefore ask both fred and alexandre to change the name of their<br clear="none">> > library, so that they cannot be confused with both the original cyclone<br clear="none">> > library and with each other: neither of the forks is an (or /the/)<br clear="none">> > "official" fork.<br clear="none">> > for what it is worth, git makes it easy to incorporate changes between<br clear="none">> > forks (using pull requests, cherry picking,...) even if the names are<br clear="none">> > different!<br clear="none">> ><br clear="none">> ><br clear="none">> ><br clear="none">> > _______________________________________________<br clear="none">> > <a shape="rect" ymailto="mailto:Pd-list@lists.iem.at" href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list<br clear="none">> > UNSUBSCRIBE and account-management -><br clear="none">> > <a shape="rect" href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><div class="yqt9448718681" id="yqtfd94196"><br clear="none">> ><br clear="none">> ><br clear="none"><br clear="none">> _______________________________________________<br clear="none">> <a shape="rect" ymailto="mailto:Pd-list@lists.iem.at" href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list<br clear="none">> UNSUBSCRIBE and account-management -> <a shape="rect" href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br clear="none"><br clear="none"><br clear="none">_______________________________________________<br clear="none"><a shape="rect" ymailto="mailto:Pd-list@lists.iem.at" href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list<br clear="none">UNSUBSCRIBE and account-management -> <a shape="rect" href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>