The goal of this set of actors it to help developers collect and package complex project files with a range of linked files.
So, this User actor doesn't collect your media. Nothing listed in the media bins will be collected, doing that can be done via: TROIKATRONIX : ISADORA - DX – PY – Collect_Media
This actor, searches the binary of your Isadora file to find linked files that are harder to see/find. For example the data file for the data array actor will be listed.
Current file types it will find: ".izz", ".txt", ".py", ".srt", ".oni", ".json", ".csv", ".xml", ".js" [I just fixed a bufg with .js files, so that isn't in the user actor yet.]
If you link other file types let me know. Right now this looks inside javascript for read() and include() calls, and will 'find' those files if they are not dynamically created [eg, this fails : read(basePath + "file.txt") ]. It does NOT attempt to find linked files within Pythoner code. The options Python offers here is far to broad.
Currently the JSON and Report, only provide the Scene name that each file is used/located in. I would like to extend this later with a breadcrumb path to help navigate into user actors if the file path is internal, as well as, adding the Q# alongside the Scene Name.
@jfg said:
Why do you have to copy the addresses you have obtained back into the inbox?
This was simply to make it clear what is being done. I am happy to change this later. Really there are 2 primary actors inside. By making you copy the path, you have more control over running each on 1, another file (doesn't need to be the active Isadora file), 2 re-running either function independently.. but I am not married to the approach.