Nice work! On Wed, Jun 3, 2015 at 2:39 PM, Juan Pedro Bolívar Puente < raskolni...@gnu.org> wrote:
> Hi! > > I have been working the last couple of weeks on polishing a big release > of Mixco. There have been significant improvements in tooling and > usability. Also documentation has improved, making less emphasis on > CoffeeScript and more emphasis on helping JavaScript developers. > > You can check the current status here: > > - http://sinusoid.es/mixco/ > - https://github.com/arximboldi/mixco > - https://www.npmjs.com/package/mixco > > If you have NodeJS, you can now simply install it with: > > $ npm install -g mixco > > Please, *feedback* is highly welcome. In the upcoming weeks I will > improve it and make sure it works perfect with the next Mixxx release. > One thing I noticed was that the mixxxVersion attribute in <MixxxControllerPreset> was not specifiable. > Also, a couple of questions: > > - Does it make sense to reference the project in the wiki? > Definitely! feel free to add it as a section in the controller documentation. > > - Would you like to include the scripts with Mixxx, even if they are > precompiled? The M-Audio Xponent script improves a lot over what is now > distributed, and there is no Novation Twitch support in mainline Mixx now. > > The compiled scripts should definitely be included! Please submit a PR for 1.12. You're already an author on the existing Xponent preset so that's essentially permission to update it :). > - Would you eventually consider integrating this framework into > mainline Mixxx? If so, what prep work would you like me to do? > We will probably always need the JS/XML for the "plain" way of writing presets. The reason is that we want to keep a low barrier to entry to writing a controller script. Using mixco is easier and more ergonomic in the long run but includes a ramp-up cost that might exclude a variety of folks who are handy enough with HTML/JS and a text editor to get going with our basic stuff but not savvy enough to install Node/npm, use a terminal, and learn coffeescript. Adding support for loading mixco files directly without compiling sounds like it would be useful. All you would have to do is create a class like MidiControllerPresetFileHandler that produces a MidiControllerPreset from the .mixco.coffee file. Looking at the dependencies -- would we need to build and distribute these dependencies with Mixxx in order to compile a load a mixco file ? That may become unwieldy. "argp": "^1.0.4", "browserify": "^10.2.3", "chai": "^2.3.0", "chai-spies": "^0.6.0", "coffee-script": "latest", "coffeeify": "^1.1.0", "colors": "^1.1.0", "globby": "^2.0.0", "gulp": "^3.9.0", "gulp-cached": "^1.1.0", "gulp-changed": "^1.2.1", "gulp-mocha": "^2.1.0", "gulp-rename": "^1.2.2", "heterarchy": "^1.0.5", "mocha": "^2.2.5", "node-promise": "^0.5.12", "sinon": "^1.14.1", "sinon-chai": "^2.7.0", "string": "^3.1.3", "through2": "^0.6.5", "underscore": "^1.8.3", "winston": "^1.0.0" > > Thanks a lot! > > JP > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > 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
