Tukka, if you're interested in trying to get it to work, I'm more than happy to send it to you. Let me know your address.
-Jamie On 06/11/2015 07:08 AM, mixxx-devel-requ...@lists.sourceforge.net wrote: > Send Mixxx-devel mailing list submissions to > mixxx-devel@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > or, via email, send a message with subject or body 'help' to > mixxx-devel-requ...@lists.sourceforge.net > > You can reach the person managing the list at > mixxx-devel-ow...@lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mixxx-devel digest..." > > > Today's Topics: > > 1. Re: Rane SL4 Support (Tuukka Pasanen) > 2. Re: Fwd: Re: formating source Code with clang-format > (Tuukka Pasanen) > 3. Re: formating source Code with clang-format (Owen Williams) > 4. Re: formating source Code with clang-format (Gavin Swanson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 11 Jun 2015 14:56:22 +0300 > From: Tuukka Pasanen <pasanen.tuu...@gmail.com> > Subject: Re: [Mixxx-devel] Rane SL4 Support > To: mixxx-devel@lists.sourceforge.net > Message-ID: <55797766.3040...@gmail.com> > Content-Type: text/plain; charset="windows-1252" > > Hello, > Sorry being quiet for a while because lack of time for this project. > Having SL4 for testing would be easier (I could even just lent one not > for owning). I don't know are ALSA people interested with this kind not > mission critical device. As I have make little reasearch I could be > rather easy to set this up with ALSA (or it's very frustrating mission :D). > > Sincerely, > Tuukka > > 10.06.2015, 21:22, Sean M. Pappalardo - D.J. Pegasus kirjoitti: >> >> On 06/10/2015 11:03 AM, Jamie Carranza wrote: >>> Hi, I'm not a developer but have much interest in using a Rane SL-4 on a >>> Linux system. Would it help to donate one to Mixxx developers to help >>> get it working on Linux? I have one I'd be willing to give up if so. >>> >>> Or is the issue with Alsa or Pulseaudio not supporting the device? >> Exactly: since Mixxx uses any devices the OS supports, you'll want to >> talk to the ALSA team about adding a driver for your audio device. >> >> Sincerely, >> Sean M. Pappalardo >> "D.J. Pegasus" >> Mixxx Developer - Controller Specialist >> >> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 2 > Date: Thu, 11 Jun 2015 15:04:06 +0300 > From: Tuukka Pasanen <pasanen.tuu...@gmail.com> > Subject: Re: [Mixxx-devel] Fwd: Re: formating source Code with > clang-format > To: mixxx-devel@lists.sourceforge.net > Message-ID: <55797936.9060...@gmail.com> > Content-Type: text/plain; charset="windows-1252" > > Hello, > I'm with auto formatting people. Before we had code auto formatting it > was mostly complaining coding style. Now like RJ said nobody can argue > because there is one to rule them all system. I also like to see > cppcheck and flawfinder style hooks to check code for dummy mistakes. > Never seen astyle has broke something like code didn't work anymore. > > Thanks, > Tuukka > > 09.06.2015, 23:48, RJ Ryan kirjoitti: >> On Tue, Jun 9, 2015 at 4:43 PM, RJ Ryan <rr...@mixxx.org >> <mailto:rr...@mixxx.org>> wrote: >> >> I can remember that RJs biggest issue in the clang autotransformer >> was the alignment >> with the openparenthesis. If we set it just to double indent most >> issues should be solved (sove-able) >> >> >> FWIW this was Emacs code formatting, not clang-format. I don't believe >> I ever shared the results of my previous experiments with using >> clang-format in mixxx. >> >> BTW: https://bugs.launchpad.net/bugs/1392757 >> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 3 > Date: Thu, 11 Jun 2015 09:30:55 -0400 > From: Owen Williams <owilli...@mixxx.org> > Subject: Re: [Mixxx-devel] formating source Code with clang-format > To: mixxx-devel <mixxx-devel@lists.sourceforge.net> > Message-ID: <1434029455.11018.28.ca...@legoogs.cam.corp.google.com> > Content-Type: text/plain; charset="UTF-8" > > So we have people who prefer 80 columns, and people who prefer unlimited > columns. There's not really a compromise position between these two > options, so how do we choose? > > > On Wed, 2015-06-10 at 09:28 -0400, Owen Williams wrote: >> On Wed, 2015-06-10 at 09:16 -0400, RJ Ryan wrote: >>> >>> The part of clang-format which frees you from having to talk about >>> code style is that there is only one right way to format the code. >>> Letting the developer have any choice in the matter goes against this. >>> >> Agree. I don't really feel strongly about line length, so 80 is fine >> with me. >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> >> > > > > > ------------------------------ > > Message: 4 > Date: Thu, 11 Jun 2015 14:08:03 +0000 > From: Gavin Swanson <gavinswan...@gmail.com> > Subject: Re: [Mixxx-devel] formating source Code with clang-format > To: Owen Williams <owilli...@mixxx.org>, mixxx-devel > <mixxx-devel@lists.sourceforge.net> > Message-ID: > <CAKHrxHH1zKBQKX6G_oP7=wb-z8+sejx+_ybneozzoak5oia...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Compromise = 120 Columns > > My main issue with 80 column split: > > Modern IDEs provide some kind of Tab Completion like capability which > lessons the pain of writing out (reasonably) long descriptive variable and > function names (which everyone should be doing). When your using these > longer names you end up splitting very simple lines at 80 columns, and it > ends up reducing readability. > > This is an obviously contrived example, but I have run into this very issue > with 80 column limits and long variable/function names (mostly crops up due > to nesting). > > void raise_importance(const listType lessImportantThingList, const > VariableTypeForImportantThings somethingImportant) > { > for(auto lessImportantThing(lessImportantThingList.begin()); > lessImportantThing == lessImportantThingList.end(); > lessImportantThing++) > { > if (somethingImportant == lessImportantThing) > { > VariableTypeForImportantThings moreImportantThing = > make_more_important(lessImportantThing); > } > } > } > > So the function definition portion can be easily wrapped, but even then in > this example the end of the line is sitting at 79 characters, if it was a > templated type of some kind it would get harry quickly. > > The line in the if can't be logically split to 80 characters in a readable > way, following most line split methods. > > These are the 80 character issues I have run into. Yes they can happen with > anything less than infinite line length, but they are highly likely to > happen at 80, much less so I've found at 120. > > On Thu, Jun 11, 2015 at 6:32 AM Owen Williams <owilli...@mixxx.org> wrote: > >> So we have people who prefer 80 columns, and people who prefer unlimited >> columns. There's not really a compromise position between these two >> options, so how do we choose? >> >> >> On Wed, 2015-06-10 at 09:28 -0400, Owen Williams wrote: >>> On Wed, 2015-06-10 at 09:16 -0400, RJ Ryan wrote: >>>> >>>> The part of clang-format which frees you from having to talk about >>>> code style is that there is only one right way to format the code. >>>> Letting the developer have any choice in the matter goes against this. >>>> >>> Agree. I don't really feel strongly about line length, so 80 is fine >>> with me. >>> >>> >>> >>> >> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >>> http://mixxx.org >>> >>> >>> Mixxx-devel mailing list >>> Mixxx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >>> >>> >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------------------------ > > > ------------------------------ > > _______________________________________________ > Get Mixxx, the #1 Free MP3 DJ software Today > http://mixxx.org > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > > End of Mixxx-devel Digest, Vol 109, Issue 36 > ******************************************** ------------------------------------------------------------------------------ _______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
