I do not plan on implementing a GUI for this myself, but if others want
to build a GUI around it that might be cool. Personally I think it would
take more work than it's worth and I am doubtful it would remove the
need to manually write JavaScript. Perhaps it could be helpful as a way
to get st
Will this work with the learning wizard?
On Wed, Mar 22, 2017 at 1:41 PM, Be wrote:
> 1. Existing mappings would not be ported over unless someone wants to
> port them over. The XML system would be kept as it is. Registering input
> callbacks from JS can exist alongside the old system.
>
> 2. I
1. Existing mappings would not be ported over unless someone wants to
port them over. The XML system would be kept as it is. Registering input
callbacks from JS can exist alongside the old system.
2. I agree that would be nice, but that is a separate issue. Owen
started a proposal and proof of
Having to also understand the XML mapping structure and how it worked on
top of learning Mixxx internals was a big sticking point for me. This
proposal would make it significantly easier for anyone with Javascript
background to dig right in.
Two things I'd like to bring up:
1. backwards compatibi
Please rate my proposal for GSoC this year, I am going to code for the
microphone effects please see it and give me suggestions that things which
can i add or remove.
I hope that this is good proposal, and mind my english im not expert of
english ;-)
proposal.pdf
Description: Adobe PDF document
On 03/16/2017 12:18 AM, Be wrote:
> http://mixxx.org/wiki/doku.php/registering_midi_input_handlers_from_javascript
I created a blueprint for tracking purposes:
https://blueprints.launchpad.net/mixxx/+spec/js-controller-input-handlers
Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer
