On 04/29/2014 11:09 AM, oeai wrote: > On 29.04.2014 11:52, Vesa wrote: >> Sorry but I have no idea what you're trying to say here. Git is for >> source code version control, it has nothing to do with downloading >> presets/samples/projects online. > with > git clone you can download all presets/samples/projects , > git submodule get some of them > git push - publish your own > git branch - create new style or set of instrument > > all these commands are already implemented and all faults have warnings > and exceptions. > how to use it in lmms is a question of these commands interpretation. > so if it is enough to get names of instruments/tracks from comments, > then use > git log and parse it > or just push in git-repo .git-folder and create some specials to link it > with file-repos. - something harder prob.
Eh, that just seems like too much complexity. We'd have to code in a understandable and easily usable API for all of this (because the vast majority of our user base is not comfortable with command line commands or git). We'd have to integrate all of this into the rest of LMMS and that would mean huge increase in complexity that we'd have to also maintain. And if we still need LSP for samples, then we need two mechanisms, and that doubles the work... Better to keep it simple and maintainable. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
