Asset Manager

[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.

[Christoph Hart]

@David-Healey that should be covered by that wildcard function, any file that matches against that wildcard would be excluded from the deinstallation procedure (and before installing it checks if it exists, then does nothing). A big XML file would be a bit tricky though - you can never change that template file because it would never be updated - with script files you can branch out your config stuff into a seperate smaller file.

[David Healey]

@Christoph-Hart said in Asset Manager:

A big XML file would be a bit tricky though - you can never change that template file because it would never be updated

Good point. Maybe I'll just use another script and the Builder stuff to construct the template's module tree instead.

[David Healey]

@Christoph-Hart Regarding templates I had another idea, what about using .hip files?

The user could load one, resave it as an xml and build it out. If I make changes to the template in the future it shouldn't affect their work and could safely overwrite the previous version when they install the update.