I thought that all files in the res folder in the image directory were automatically copied to the res folder in the output directory.
But if I save a woff file into the res folder in the image directory, this woff file is not copied to the res folder in the output directory if I click the Make button.
All files should be copied to the output. Have you any code that might be deleting the file before album build is complete? If not, attach the file so others can try it, or try using another skin entirely, does that work?
But now I have to do this for each new version, so David please add this to the standard filetypes.xml file.
Adding woff files to the supported file types (visible in jAlbum’s explore view) doesn’t really make sense - it is not something the average user wants to include in an album. It would be better to code your skin so that you explicitly copy the woff file to the output res folder.
I don't think many users are interested in web fonts, my skins do support already Google fonts, so I do not want to change something for woff files fonts.
I just liked to make a recipe in the manual so that users can still use woff files with some extra code in the css code box and let the user save the woff file in the res directory in the image directory.
I (based on an old post), like you, was mistaken.
I know, but what is the problem if jAlbum copies all files in the image res directory to the output res directory?
Nothing, but updating the supported file types to allow any file type to be copied from the project’s res folder is not sensible. Maybe David will provide a patch to copy anything in the project’s res folder, given that that folder is a ‘special case’.
Maybe David will provide a patch to copy anything in the project’s res folder, given that that folder is a ‘special case’.
I'm about 95% sure this used to be the case - I recall being surprised when I tried to stash a something.js file in res, and it wasn't copied to the output.
I wouldn't want jAlbum to accept totally unsupported files anywhere other than the image directory's res folder, however. But within res, those files should be permitted, using unknown.png as the thumbnail (interesting that such a file already exists in the jAlbum program directory, which suggests that my memory is correct), and they should all be copied to the output directory's res folder.
From an old comment in the Mirage code:
// Copy the Zoomify viewer from the project or album res directory to the output res directory.
// jAlbum copies some files, but ignores some file types (e.g. .js files).
Don't ask me to remember the details.
I have found an old post about copy all files from the project res folder to the output’s res folder. If David does update jAlbum to copy all of the res folder’s contents then I would like to add another change.
The copying of the folder’s contents should be performed after the copying/processing of the skin’s res folder. A user would expect their project files to overwrite the skin’s files.