Asset Manager

[Christoph Hart]

@David-Healey I did some polishing a few days ago but it‘s not pushed yet. When it is it should be ready for local use. I‘ll let the robot write an explanation how to use it then.

[Christoph Hart]

Alright, here we go. Robot says this:

https://github.com/christophhart/HISE/blob/develop/guidelines/development/asset-manager.md

[dannytaurus]

@Christoph-Hart Love the 'coming soon'. Very subtle!

[David Healey]

@dannytaurus Guess we cut the ribbon during the next meet up?

[Chazrox]

I feel like this is what everyone needs to fill in the gaps in development for some projects.

[David Healey]

Do Local Asset Folders have to be HISE projects? I have a library of script files I want to share across projects but they don't belong to any individual project. Currently I keep them in the Global Scripts Folder. I'd like to include some fonts too.

[Christoph Hart]

@David-Healey yes - this enforces the proper versioning and folder structure. But you can just put them in the scripts folder at the exact location where you want them to end up in your project that imports it and it should work. In fact I tested this system with the rhapsody template and it worked flawlessly.

[HISEnberg]

@Christoph-Hart Looks very promising. The setup seems straightforward enough (the robot maybe generated too much text description). Happy to throw some FX Libraries and HIsescripts at it if you need some beta testing before launching.

[David Healey]

@Christoph-Hart In my framework I want to include some script files that are templates that the user should edit. When there is an update to the framework I don't want it to overwrite these files, it should only create them if they don't already exist. Does the asset manager support this?

Can we add an Icon for our asset packages that shows in the asset manager?

Edit: Ok I just tested the version thing and I see it skips modified files and then it gives the option to "clean up" - aka delete. There doesn't seem to be an option to ignore the modification and dismiss the cleanup button. And you can't install a newer version until you cleanup.

[Christoph Hart]

@David-Healey yes good idea. So ideally you could define a wildcard for user editable config files - if they dont exist they are copied over but they are not deleted / overriden when updated or uninstalled.

[David Healey]

@Christoph-Hart Yes that would be ideal.

[Christoph Hart]

@David-Healey should this also extend to preprocessor definitions? I think currently it removes them but there might be a case for a similar usage there

[David Healey]

@Christoph-Hart Yes that would make sense

[David Healey]

@Christoph-Hart In addition to script files I can see a situation where I would want to include a project xml as a starting template. So that would be another file I'd want to allow the user to change.