demcanulty wrote:the open source Max Dev Kit ,which cooks raw data from the Quneo, has received a very tepid response so far
connerlacy wrote:Hi All,
I'm happy to announce the QuNeo Editor source is up on github as a private repository.
connerlacy wrote: jrussell has already made some excellent headway on getting a fully functional Linux build going.
connerlacy wrote:If you'd like access to the source, just send me a message with your github account name and I'll add you as a collaborator.
elmquist wrote:First of all thanks a lot for you taking the lead on the Linux port of the QuNeo editor, jrussel! I am looking forward to use it though I will use a source code distribution and possibly try to see if I can run it on QT5.1 as that is where my focus is anyway.
elmquist wrote:It does take time to build an open source project so please do not expect wonders when releasing the source code. There may be a slow start and not everyone may want to run early binary releases when the source code will be available soon.
elmquist wrote:What license will the editor be released under?
elmquist wrote:Is qmake being used to build the editor?
elmquist wrote:As for the types of access to the device I am only used to work with the exclusive access to MIDI devices and that is plenty for me. But I can surely see the advantage of being able to configure and test the device without having to constantly start and stop the programs (as long as preset updates work in shared mode).
Which one should be the default? Well given that the first thing people has to do is upgrading their firmware the exclusive access seems to be the right default. Otherwise people have to make special actions before they can upgrade the firmware - and that will be quite a noise generator!
Should the shared mode be selectable as a command line option or as a setting inside the GUI? Possibly both! No matter where it will be placed users have to be aware of the option of shared access and they have to be able to find it easily.
Have you considered how the editor should find its runtime files? The easy way is to require them to be in the same directory as the application is started from. Another is to hard code the path to the files inside the binary. Quite a few Unix applications does so. And finally there is the option of having the application to search for itself using the name its called as together with the PATH environment variable and derive the location of the runtime files from that. As long as the editor is a source code distribution I think that the hard coded path will work best though perhaps with a command line option to override the default value.
Users browsing this forum: No registered users and 4 guests