Hi, I have had a long internal debate about this one ever since I wrote version 1 - whether linked files should be incorporated into the timeline file, or whether they should just reference the external file. I have always chosen the latter, as I think the more common use is to link to external reference material which itself may need to change regularly, and therefore should be hosted outside of our application. Images are a bit different to this, and so at some stage I will probably look to include an option to store images directly inside the timeline file. If you want to have image links that show up for a web export, one option may be to upload them to a web server (or any hosting service) and then include links to the image files on the web rather than on a local hard drive. Then they should be accessible from anywhere. That said, the web export should be able to locate and display files from your local hard drive too - although that may be dependent on browser etc. Which one are you using? Matt
Okay, I tested various set-ups. I’m using Safari 9.1 by the way. Anyway, set-ups: 1) Image stored online, accessing file:///…/projectname/aeontimeline.html displays image 2) Image stored offline, accessing file:///…/projectname/aeontimeline.html displays image. 3) Image stored online, accessing https://…/projectname/aeontimeline.html displays image. 4) Image stored offline, accessing https://…/projectname/aeontimeline.html doesn’t display image. For all tests the browser was online; I’d expect (2) to work fine offline. I moved the test image into file:///…/projectname/images and changed the internal link, but this didn’t solve the issue, so I’m assuming the link paths are stored as absolute paths. This is fine for most cases, but I figure a file path truncation process in the web export might check for links that work with relative paths for the resulting .js or .html file Or alternatively copy the local image files into the images folder and have the internal link for the web export link to the copies instead of the originals, I suppose. I gather I’m arguing for m ore of an edge case than a general one, but the result would be an easily movable folder (or zip-file) that I could hand to co-workers that they could check with their browser, even when they’re offline or the computer doesn’t have internet access because of security reasons and such. Hm… basically I want the web export to work off a single folder (with subfolders) and still display everything properly, even when I access that folder from another computer. Two other issues that cropped up: A) The graphic for the "Group" button in the web exported version never showed the proper image, but the "image not loaded" image of the browser. 2) When I load the web exported version, I start at weird places, like 4154 CE or 10205 CE.
Hi, Thanks for the feedback, and sorry for the delayed response. In the longer term, having some kind of "gather external links" option that can drop all the external links into a local folder is definitely on the cards both generally and for web export. I have fixed the toolbar icon issue for the web export from Mac. With regards to the weird start place, the timeline is meant to open up where you had it on your timeline view, but I will do some testing to see if I can reproduce the case where this doesn't work.
I notice that in order to get the web export to start correctly I have to place the timeline where I want it, and at the zoom that I want it, save it, close it, then reopen it and export to web. That works.
Hi Ron, Thanks for the report on the start dates... I have known this seemed a little intermittent for a while, so it will be good if you have cracked the magic code that makes it work - that will make it easier for me to fix it generally. With regards to the anchors etc. I agree that this would be a good next step, although it is probably something I won't be able to get to for a while. Matt