This discussion is going off in quite a few directions. Some arguments are
concerned with UI design. Some are concerned with UI responsiveness. Some
are concerned with network bandwidth. Some are concerned with the
technology behind the solution.
Jonathan brings up a valid point about the future home of the LSP. Placing
LSP into a CMS could really break this stuff. I agree withe Vesa's point
about version control being overkill, but I believe the proposal is about
the capabilities of download AND upload, which would need some versioning
if done properly.
Since cloud storage is growing more and more in popularity and each cloud
solution (Dropbox, Google Drive, iCloud) has its own implementation of
versioning and asynchronous downloading and uploading, this may better be
done with a QT helper. Some already exist for Amazon and Azure.
>From a project perspective, I don't think this should get a milestone just
yet because there's not a tremendous demand for it yet and it's a
considerable amount of work.
The part I like about this discussion is that it helps us gauge the
possible future needs of LSP. LSP's design decisions taken now could
really help make a feature like this scalable to the software down the road.
------------------------------------------------------------------------------
"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
