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