From: Mike C. <rda...@gm...> - 2013-02-23 13:04:35
|
Hi Toby, I could afford help with the back-porting. I just checked that some GUI functions are not yet implemented within current Master branch, also those resources seems not yet used within project files, there are relative paths, but if you move resource, it'll not load, so maybe this could be added? Best regards Mike C. On Thu, Feb 21, 2013 at 10:28 AM, Mike Choi <rda...@gm...> wrote: > Hi, > I see now that VST plugins are also covered there, btw what state is now > that resource browser? Does it work outside relative paths of base > direcories? > > Also is integration with project files and resource items working? > > Best regards > Mike C. > > On Thu, Feb 21, 2013 at 2:07 AM, Mike Choi <rda...@gm...> wrote: > >> Hi Toby, >> >> Thanks for notifying, sorry I didn't know about that. Does it handle VST >> plugins as well? I was aiming mostly just for loading project files, to >> avoid need of absolute paths wherever resources are stored locally, I see >> this incorporate also online resources and other things. BTW do you have >> some work notes, or future plan about this? >> >> Thanks, Best regards >> Mike C. >> >> >> On Wed, Feb 20, 2013 at 10:28 PM, Tobias Doerffel < >> tob...@gm...> wrote: >> >>> Hi, >>> >>> As for the identification and relocation of file resources by hashsums >>> and file properties, everything has been implemented in the master >>> branch already (resources framework, see include/*Resource*.h >>> src/core/*Resource*.cpp and src/gui/*Resource*.cpp) (and even is used >>> by AudioFileProcessor, Sf2Player and so on). Before reinventing the >>> wheel, we should backport this resource framework to a separate >>> working branch based on the current stable branch. >>> >>> Best regards >>> >>> Toby >>> >> >> > |