On 07/26/2014 01:49 PM, musikbear wrote: > Tres Finocchiaro wrote >> we should be mindful of how the samples impact our shipped >> tracks, the demos that come with the software. > and thats/ vip! /-but.. re 'we' dead sure that /none/ of the less pedigreed > samples have been used in any shipped demo? > Again, users will hate the devs, if > * there work suddently has changed (result of exchangeing packs but, > preserving names) > * there work is broken/ destroyed (result of removing all old samples)
Backwards compatibility is a tricky issue. On one hand, breaking backwards compat should be avoided as it can discourage people from upgrading if they can't continue on their old works anymore. On the other hand, we can't restrict ourselves from improving the software and providing new functionality - we can't let ourselves be chained by the past. So it's always a balancing act. I think the whole samples issue becomes moot if we first introduce the feature where it's possible to embed all sample data in the project file. Then introduce the sample library changes only after that, and the problem will be solved as old samples will be embedded in the project files. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
