which works fine in editor, browser preview and building, using standard folder export. But if I use this script (OrganizedAssets), the mp4’s are correctly moved to /media folder but the hype generated script is looking for it at the root, rather than /media.
From the hype_generated_script.js: hype_video.setAttribute('src', \"./video_01.mp4\");
Is it that the OrganizedAssets doesn’t understand / update references if they’re referenced only in a script, not loaded onto stage?
I can easily get around it (adding /media to the media url for instance) but this breaks it in editor & preview (unless I use ‘Preview Using Export Script:’ option).
I’m thinking that when I train colleagues on how to use Hype, the smoother sailing, the better
The problem is that ${resourcesFolderName} is a simple text replacement and isn’t really smart enough to see that the reset of the code is referencing a video and to adjust like that.
In this case you will want to use add the media/ manually and then use the preview using export script option.
(side note: I’m surprised it works in the editor environment since it is being dynamically added anyways?)
I have downloaded the script, installed it in the right place. I have exported a banner I am working on at the moment, but there is still no js folder generated. I have included a video so you can see for yourself.
It's not so bad, editing the html file will fix it.
Sorry about the delay - I had to investigate why we didn't originally get your emails/reports (it was from an overzealous configuration option in our spam filter).
Theoretically I do think this is the best solution, but there's practical hurdles.
You could use export scripts with node.js right now if you wanted to; the interface is via command line arguments. Python was chosen for all of Tumult's and the initial examples because it is a pretty clear language and was shipped on the system by default. Node unfortunately isn't, and I don't really like having to build/ship runtimes with our apps (Whisk has Java).
Export scripts use the macOS Application Script feature as a way to escape the security sandbox so you can do arbitrary things. It turns out most export scripts don't need this ability at all. Further, JavaScript would be the best language to use to interact with the Hype UI, and could be run the Hype editor WebView even. So there might be some middle ground we can do that either gives appropriate instructions to get node, or provide a minimal amount of functionality found in node for the types of things common in export scripts.
(Whisk has Java).