On 07/29/2014 04:07 PM, musikbear wrote: > Perhaps a 2.0 on an other core is not a 2 y prospect, but a 5+ ..? > imo we should improve and expand /what we got/.
No offense musikbear, but what you're saying is analoguous to: "oh, I know our house is slanted and the foundations are crumbling, but maybe we can still keep building the second floor"... What we got will only take us so far, eventually we WILL hit a wall where it's no longer possible to get by with "what we got". We can probably make do and keep patching things up the best we can, but for the long run, we're going to need to fix the foundations. Here, I'm looking for ideas for how we can achieve that. > But all work on current > core, should have a pin stuck in it. A pin marked /'re-usable' as module/. > Vesa, you are the one who can say if such /modulation/ at all is possible? > If it is, then a 2.0lmms would not be a 'scratch' project, and further > devellopment on 1.x, would also be a little'working for the future' > Does that sounds like garbadge? I'm not really sure what you're suggesting here... we can try to develop and improve the current engine, but I'm not sure if it's possible to improve it sufficiently. Some argue, it isn't. I don't know, it could turn out that fixing the current engine would be even more work than just replacing it with a better one. ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
