On 27 April 2012 06:59, Philip Whelan <[email protected]> wrote:
>
> I disagree here, VDJ's syntax is horrible and the language itself is
> probably not very feature complete. I know that is not as relevant for
> normal (or even most power users), but no reason to re-write our own
> just for that. The Javascript engine is actually a part of Qt.
>
i don't think there's anything horrible about it - it basically just makes
use of the ternary operator to achieve quite a lot. i think whatever
scripting format is used it needs to make 90% of the kind of functionality
needed as simple as possible while allowing more advanced mapping options
as well. vdscript covers that 90% but that's also where it stops...
> One solution to make the syntax for scripts easier would be to use
> CoffeeScript which compiles into JS.
>
coffeescript looks more appealing than javascript - at least from first
look. i guess it depends how it is used and what objects/actions/functions
can be used within it to control mixxx. personally i really don't like the
current scripting format in mixxx or the xml format for controllers. the
xml format seems way too verbose - not a biggie if it's only edited via
mixxx itself, but it's not great for manually editing. again vdj uses xml
pretty well for it's controller definition files and mappers - worth taking
a look at anyway.
> Another option would be to include a UI in the MIDI mapper that
> resembles traktor's modifier system which generates Javascript, but
> that could lead to all sorts of problems if a user were to modify the
> script then try to fix it in the UI later.
>
the simple solution there i guess would be to create a config file that is
just used by the UI which in turn can generate the javascript (if we really
need to use javascript at all - but no reason why not as the internally
executed format if anything else can be converted to it)
having a UI with similar features to traktor could well help to get a lot
of traktor users on board. it seems NI is wanting to lock down traktor to
their own controllers now, or at least seems to be going in that direction
(with traktor 2.5 remix decks and the F1, not to mention HID support for
their S2/S4/X1 controllers) and i know i'm not the only traktor user who is
looking at alternatives right now.
there's lot that can be improved in the traktor editor window tho and it's
an area people moan about a lot on the DJTT forum. NI doesn't seem
interested at all in improving it. having a midi editor with a similar
workflow would certainly get a lot of that crowd interested in mixxx.
back to scripting tho... most of the time what people would need to do is
fairly simple, i.e: map directly a control to one or more actions within
mixxx, toggle the input to the output, set a shift condition, modify the
action based on a shift condition, send back different midi
values/velocities for led feedback whether trigged via midi from the
controller or by an internal event in mixxx and do any number of these
things from one controller/mixxx event.
all of this should be covered by a "as simple as possible" scripting format
- and the vdj style does work for all of those. djdecks also has a simple
scripting format.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
