Citerar Vesa <[email protected]>: > If there has to be an option for downloading presets/samples/whatever > from LSP or elsewhere, fine... but it should be configurable, it should > not break existing functionality, and it needs to be implemented better. > > Particularly, the file browser shouldn't get broken so horribly as in > these pictures: > > http://www-user.tu-chemnitz.de/~doto/lmms/lmms-goes-online-2.png
Nothing too horrible about that if we stick to the parts relevant to network resources. > - What if the online address changes, That kind of change rarely comes as a sudden surprise, but it should of course be anticipated. No big deal. > what if the site gets hacked, > etc... it's not a security problem as long as we only download > presets/samples and no executable code of any kind, but it's still > something we need to think about. Oh yes, it is. Buffer overflows and so on... > - We have to ensure that web searches do not slow down the software... > there needs to be a proper separation of online/local because not > everyone has super fast internet connections - some people still live in > areas without broadband. > If we have to wait for LMMS to poll external > websites every time we browse our LOCAL samples/presets... then it makes > LMMS unusable for many people. That's a no-no. That's a "nobody has even suggested it", I hope. Google can pull it off with billions in infrastructure and infinite (smart) code monkeys, but LSP? Hardly. > - We have to ensure that LMMS works regardless of the status of the web > connection. If the online files aren't available, or the web connection > is down entirely, local functionality must NOT, under ANY CIRCUMSTANCES, > be impaired IN ANY WAY because of it. I'm writing in caps because this > is **VERY IMPORTANT**. > - There should not be a wait time at startup while LMMS checks for > online connections. I thought polling in the background, caching and stuff like that could solve most of these problems? > Online sources should only be polled when the user > explicitly asks for them. ... but obviously not if this is a hard requirement. Or would you settle for a checkbox like "refresh LSP resources in background" as explicit enough? > Proper separation of local and online spaces must be implemented before > this feature is brought anywhere near master, IMO. Not anything like in > the images Toby posted... but rather maybe an extra tab in the sidebar > that contains all of the online stuff so people can safely ignore it if > they don't need it, and still use the local functionality without > impairment. Your "proper separation" is really mostly about a minor UI detail, which probably is the easiest thing to change in this whole discussion. I'd like to see this network stuff separated into a helper program of some kind. Something like a cloud storage or version control client, possibly with LMMS only reading files from a local directory. How's that for separation? -- [email protected] softrabbit on #lmms ------------------------------------------------------------------------------ "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 [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
