Hello,
lets say someone has a not-supported controller and is willing to help but has
no clue how to script a full featured mapping.
And then there is someone who is willing to help coding, just like in this
joint effort for VCI-100 mapping in the forum .
Do we have some kind of guideline which informations the coder needs (a
volunteer who make the script without actually owning the controller)?
The infos may be often very similar, so it may help save time on both ends if
there would be a blueprint imho.
jus
On 17 Sep 2010, at 04:30, RJ Ryan wrote:
> Hey all,
>
> Just wanted to bring up a list of hardware devices that Mixxx doesn't have
> mappings for:
>
> http://mixxx.org/wiki/doku.php/hardware_compatibility#devices_we_don_t_have_mappings_for
>
> Do you own any of these devices? Consider contributing to Mixxx by making a
> mapping and sharing it on the forums. We'll include it in Mixxx and people
> with your device everywhere will have a good experience right out of the box
> with Mixxx.
>
> Also feel free to add devices we are missing to the list.
>
> Thanks!
> RJ
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev_______________________________________________
> Mixxx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
