My interest is that I'm a huge fan of FOSS and would love to contribute but don't have time or skill to contribute code. I like Rane hardware, they are a US (my country) company (made in US too) but their stuff is not cheap. I think I paid over $900 for the SL4 ,vinyl, and Serato license bundle. I have used Linux as my only computer for over a decade and work as a Linux admin. This device is the only thing I use Windows for and it sort of works (possibly my AMD CPU which Serato does not recommend). I would love to not need Windows and be able to use a modern Rane digital vinyl device. If Tukka or someone can get it working on Linux I can afford to buy myself another one.
-Jamie On 06/11/2015 12:22 PM, 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 (Be) > 2. Re: Rane SL4 Support (Jamie Carranza) > 3. mapping file name conventions (Be) > 4. Re: mapping file name conventions (S?bastien Blaisot) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 11 Jun 2015 11:34:46 -0500 > From: Be <b...@gmx.com> > Subject: Re: [Mixxx-devel] Rane SL4 Support > To: mixxx-devel@lists.sourceforge.net > Message-ID: <5579b8a6.6000...@gmx.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > It would be awesome if you lent Tuuka your SL4 for driver development. > > The ALSA developers apparently have no interest in working on this > driver. As far as I can tell, there is no good reason for someone > interested in DJing with Linux to purchase an SL2/3/4, so no one has > written a Linux driver for them yet. They are really expensive because > they are bundled with the price of a Serato software license. The > cheapest one, the SL2, costs $500 whereas the Traktor Audio 6 costs > $300. I don't see any reason for someone not interested in using Serato > to buy one of these rather than one of Native Instruments' DJ sound > cards with phono preamps. I think this driver only matters for Serato > DJs who want to use the hardware they already have with Linux. > > On 06/11/2015 10:51 AM, Jamie Carranza wrote: >> Thanks, I figured it was Alsa, Linux or something low level. Thought I'd >> ask. >> >> -Jamie >> >> On 06/11/2015 01:51 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 (Sean M. Pappalardo - D.J. Pegasus) >>> 2. Re: Rane SL4 Support (Be) >>> 3. Re: formating source Code with clang-format (Daniel Sch?rmann) >>> 4. wiki overhaul (Be) >>> 5. Re: travis-ci restart (S?bastien BLAISOT) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Wed, 10 Jun 2015 11:22:40 -0700 >>> From: "Sean M. Pappalardo - D.J. Pegasus" <spappala...@mixxx.org> >>> Subject: Re: [Mixxx-devel] Rane SL4 Support >>> To: mixxx-devel@lists.sourceforge.net >>> Message-ID: <55788070.4010...@mixxx.org> >>> Content-Type: text/plain; charset="windows-1252" >>> >>> >>> >>> 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 >>> >>> -------------- next part -------------- >>> A non-text attachment was scrubbed... >>> Name: smime.p7s >>> Type: application/pkcs7-signature >>> Size: 4255 bytes >>> Desc: S/MIME Cryptographic Signature >>> >>> ------------------------------ >>> >>> Message: 2 >>> Date: Wed, 10 Jun 2015 14:02:09 -0500 >>> From: Be <b...@gmx.com> >>> Subject: Re: [Mixxx-devel] Rane SL4 Support >>> To: mixxx-devel@lists.sourceforge.net >>> Message-ID: <557889b1.9050...@gmx.com> >>> Content-Type: text/plain; charset=windows-1252; format=flowed >>> >>> I posted on alsa-devel about this a few months ago and got no response. >>> I emailed Mark Hills, the xwax developer, who wrote the driver quirk for >>> the old SL1 (a USB 1.1 device; the SL2/3/4 series is USB 2.0). He >>> responded to me initially but I never heard back from him after that. I >>> posted on this list and Tuuka Pasanen said he would be interested in >>> writing a driver. I setup a Windows 7 VM with KVM/QEMU on my laptop, >>> plugged in my friends' SL4, and recorded the raw USB traffic with >>> Wireshark on GNU/Linux (outside of the VM). I sent that data to Tuuka >>> but I haven't heard anything about it in a while. >>> >>> I don't own an SL2, SL3, or SL4 (and am not really interested in owning >>> one), but I'd love to see Linux support this common DJ hardware. >>> >>> On 06/10/2015 01:03 PM, 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? >>>> >>>> -Jamie >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> _______________________________________________ >>>> 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: 3 >>> Date: Wed, 10 Jun 2015 23:23:33 +0200 >>> From: Daniel Sch?rmann <dasch...@mixxx.org> >>> Subject: Re: [Mixxx-devel] formating source Code with clang-format >>> To: Max Linke <max_li...@gmx.de> >>> Cc: mixxx-devel <mixxx-devel@lists.sourceforge.net> >>> Message-ID: <5578aad5.7030...@mixxx.org> >>> Content-Type: text/plain; charset=utf-8; format=flowed >>> >>> Hi, >>> >>> I have played a bit with clang-format and it turns out that >>> we need >>> >>> AlwaysBreakBeforeMultilineStrings: false >>> ColumnLimit: 0 >>> >>> To fix most cluttering the issues. >>> >>> But now we have a new one: >>> Double indentation fails in certain palaces. >>> >>> >>> >>> >>> Am 10.06.2015 um 17:01 schrieb Max Linke: >>>> On 06/10/2015 04:16 PM, Daniel Sch?rmann wrote: >>>>> Which version of clang-format do you use? >>>>> Can this be a bug like this: >>>>> https://github.com/travisjeffery/ClangFormat-Xcode/issues/81 >>>>> >>>>> Can you give an example where ColumnLimit: 0 fails? >>>> I use clang-format-3.6 >>>> >>>> >>>>> QLayout* pLayout = NULL; >>>>> - if (context.hasNode(node, "Layout")) { >>>>> - QString layout = context.selectString(node, "Layout"); >>>>> - if (layout == "vertical") { >>>>> + if (context.hasNode(node, >>>>> + "Layout")) { >>>>> + QString layout = context.selectString(node, >>>>> + "Layout"); >>>>> + if (layout == >>>>> + "vertical") { >>>>> pLayout = new QVBoxLayout(); >>>>> - } else if (layout == "horizontal") { >>>>> + } else if (layout == >>>>> + "horizontal") { >>>>> pLayout = new QHBoxLayout(); >>>>> - } else if (layout == "stacked") { >>>>> + } else if (layout == >>>>> + "stacked") { >>>> This doesn't happen if I set the column limit to 80 >>> >>> >>> ------------------------------ >>> >>> Message: 4 >>> Date: Wed, 10 Jun 2015 17:01:26 -0500 >>> From: Be <b...@gmx.com> >>> Subject: [Mixxx-devel] wiki overhaul >>> To: Too Many DJs <mixxx-devel@lists.sourceforge.net> >>> Message-ID: <5578b3b6.4050...@gmx.com> >>> Content-Type: text/plain; charset=utf-8; format=flowed >>> >>> I have started overhauling the wiki. Take a look and feel free to edit. >>> >>> On the front page, I: >>> * moved the info about GSoC to its own page, >>> * moved the links to old meeting minutes to their own page, >>> * removed the outdated and confusing link about the Hercules driver, >>> * updated the manual link to the current online manual, and >>> * reorganized a lot of other links. >>> On other pages, I: >>> * added Crossfade to the page about live GNU/Linux distros >>> * removed outdated info about MixxxOS >>> * added info about Native Instruments Traktor controllers to the >>> hardware compatibility page >>> * updated compilation instructions for Fedora. >>> * updated info about using two sound cards in the FAQ >>> >>> To do: >>> * Rewrite beginner's guide considering info that is already in manual. I >>> am also working on revising the manual, especially chapter 3. >>> * Add prices to hardware compatibility tables >>> * Update info about controllers where info is available >>> * Organize sound cards on hardware compatibility page into a table with >>> info about each OS and the capabilities of the hardware >>> * add more sound cards >>> * undicate which controllers bundle sound cards >>> >>> >>> >>> ------------------------------ >>> >>> Message: 5 >>> Date: Thu, 11 Jun 2015 10:51:00 +0200 >>> From: S?bastien BLAISOT <mi...@blaisot.org> >>> Subject: Re: [Mixxx-devel] travis-ci restart >>> To: S?bastien BLAISOT <mi...@blaisot.org> >>> Cc: mixxx-devel <mixxx-devel@lists.sourceforge.net> >>> Message-ID: <43859d3ceb3981cb3eadbe2cd3c2b...@blaisot.org> >>> Content-Type: text/plain; charset="utf-8" >>> >>> >>> >>> Hi all, >>> >>> I have 2 consecutive builds that failed in travis-ci in the EngineBuffer >>> tests. Not at the same place (stalled builds killed by travis-ci) (Pull >>> Request 606). >>> >>> https://travis-ci.org/mixxxdj/mixxx/builds/66159337 >>> >>> https://travis-ci.org/mixxxdj/mixxx/builds/66339484 >>> >>> I can see no relation between this two commits and engineBuffer >>> >>> I have compiled Mixxx on my computr without problem (and it builds fine >>> under travis-ci but the tests are failing). >>> >>> I don't know what to do with that. can somebody take a look at that ? >>> >>> --- >>> S?bastien Blaisot >>> >>> Le 10/06/2015 09:44, S?bastien BLAISOT a ?crit : >>> >>>> Hi, >>>> >>>> I have a failed (stalled) build in travis-ci on PR606 (last commit). I >>>> suspect a temporary problem on travis-ci. >>>> >>>> Is there a way to restart travis-ci compilation other than pushing a new >>>> commit ? >>>> >>>> Thanks, >>>> >>>> -- >>>> S?bastien Blaisot >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >>>> http://mixxx.org [1] >>>> >>>> Mixxx-devel mailing list >>>> Mixxx-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [2] >>> >>> Links: >>> ------ >>> [1] http://mixxx.org >>> [2] 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 35 >>> ******************************************** >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> 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: 2 > Date: Thu, 11 Jun 2015 09:42:43 -0700 > From: Jamie Carranza <ja...@demurgatroid.net> > Subject: Re: [Mixxx-devel] Rane SL4 Support > To: mixxx-devel@lists.sourceforge.net > Message-ID: <5579ba83.5090...@demurgatroid.net> > Content-Type: text/plain; charset=windows-1252; format=flowed > > 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 >> ******************************************** > > > > ------------------------------ > > Message: 3 > Date: Thu, 11 Jun 2015 14:02:18 -0500 > From: Be <b...@gmx.com> > Subject: [Mixxx-devel] mapping file name conventions > To: Too Many DJs <mixxx-devel@lists.sourceforge.net> > Message-ID: <5579db3a.80...@gmx.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Mappings included in Mixxx have the XML file named with hyphens > separating words but the script files are named with spaces separating > words. Having two naming conventions gets confusing and annoying, > especially when typing the file names in a shell. I suggest switching > the script files to using hyphens to separate words. Thoughts? > > > > ------------------------------ > > Message: 4 > Date: Thu, 11 Jun 2015 21:21:49 +0200 > From: S?bastien Blaisot <mi...@blaisot.org> > Subject: Re: [Mixxx-devel] mapping file name conventions > To: mixxx-devel@lists.sourceforge.net > Message-ID: <5579dfcd.2050...@blaisot.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Le 11/06/2015 21:02, Be a ?crit : >> Mappings included in Mixxx have the XML file named with hyphens >> separating words but the script files are named with spaces separating >> words. Having two naming conventions gets confusing and annoying, >> especially when typing the file names in a shell. I suggest switching >> the script files to using hyphens to separate words. Thoughts? > I don't care that much if we use hyphens, spaces or whatever, provided that: > > - wherever possible, use the same convention/name for js and xml files > - only use characters that are acceptable for filenames on all OSes > (regardless of OS language) > - resulting filenames are easily human-readable > - It's easy to find all files from the same brand / model (this files > are near each other when alphabetically sorting) > > It's probably more readable to have a word separator different from a > brand/model/comment/type/whatever separator. > Something like > brand - model[ - comment].type.{xml,js} > with word separated by space if we have brand or model which contains > several words. > > let's try it with an example : > > American Audio - RADIUS 2000.hid.js > American Audio - RADIUS 2000.scripts.js > American Audio - RADIUS 2000 - CH1.midi.xml > American Audio - RADIUS 2000 - CH2.midi.xml > > This way, all files from the same brand are all together, as well as all > files from the same model adn it's easy to read. > ------------------------------------------------------------------------------ _______________________________________________ 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
