there is a small drawback (or feature?
) with artwork in the export templates.
when we created the export templates, we had one scenario in mind:
- we would like to create an export which we can pass over to friends. thus it should be a simple HTML page which holds all meta data about ones library.
To create a html page which we can simple give away, we should use artwork which is in the internet (for this we take the urls to the artwork we scraped), so you have only to pass over the HTML/CSS files. The drawback here is, that after resetting the internal database, all urls are gone and we do not have that for exporting. We can also have an url to another file than you have locally available.
BUT: what to change? should we link the artwork in the export templates to our local artwork files? (passing the export list to friends would result unavailable links), or should we copy over the artwork to the export (you wouldn't like to give a 100mb export to your friends, would you?)?
We could down scale the artwork and copy it to the export template (CPU intensive! the export could take several minutes depending on your CPU power/library size), but this isn't implemented yet.
as you can see - the topic artwork in the export templates is tricky.. and there is no better way available (yet)
sorry for that