It's for this reason that the translation updater is called "Resource manager". The plan was to extend it to more resources such as plugins, soundfonts, palette, styles and so on. However, it still means we need to package the soundfont with released versions of MuseScore.
For large files in git, a possible solution is setting up git LFS https://help.github.com/articles/working-with-large-files/ lasconic 2015-10-19 16:37 GMT+02:00 ABL <antonio.lo...@alice.it>: > What about implementing something similar to what has been done for the > translations? I.e. the updated sf3 is stored on a server (separate from the > git repository) and continuously updated and the user can download the > updated version and it automatically replaces the old version. > By doing something like this, we could reduce the problem of engulfing the > git history with huge files, and we could also update the "released" > version > of the soundfont if we find a problem after the release of a new MuseScore > version. > > Ciao, > ABL > > > > -- > View this message in context: > http://dev-list.musescore.org/FluidR3Mono-GM-sf3-tp7579534p7579538.html > Sent from the MuseScore Developer mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Mscore-developer mailing list > Mscore-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mscore-developer >
------------------------------------------------------------------------------
_______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
