Re: Automatic image naming
@Rob, can you or the team describe exactly what happens if a named image is added to the design page and then "mangled". Stretched, cropped, toned, filtered variant-scaled, etc. Are all these effects going to become CSS Classes so there is one export image and not 20 derivatives?
Acorn
Re: Automatic image naming
Once it gets implemented I'll have a play and send an installer around to the beta testers, will have to let you know on that.
It's likely there will be image copies (or even duplicate names) in which case it will keep the name but add an incremental integer at the end.
Re: Automatic image naming
Don't overlook all the prior proposals and faults identified:
My main concern is the current disconnect between the Bitmap gallery filename [Right-click > Save > Export], the Names gallery [filename="yetAnotherFileName"], the Page and Layer gallery [Photo 'importFileName (Optimised)' (318 dpi)] and the export image filename [26.jpg & 26@2.jpg].
Acorn
Re: Automatic image naming
Really good additions, Acorn!
Re: Automatic image naming
Rob, wouldn't true image linking be a solution for webby stuff using an original filename and keep larger sites more responsive? This would also be true for people making books, brochures, large format stuff, to also keep files more responsive?
2 Attachment(s)
Re: Automatic image naming
I'm all for naming images rather than the current numbering system where by on each publish all the images are given newer, higher numbering.
I'd like it to be roughly as my suggestion in Acorns 4th link above.
You'd also need to sort out the very bad bug present in all releases so far whereby an image named under 'filename=myImage' and used across variants alternately exports the image at different resolutions on each subsequent publish.
I've brought this matter up a few times but it's never been seriously addressed as far as I'm aware.
I attach a xar file showing this bug.
Re: Automatic image naming
Re: Automatic image naming
It's early days so I don't have answers to most of your concerns yet about how it's going to work but will certainly take it into consideration.
@gary - I'm hoping filename would be used by default, and there would also be a text field in the Web Properties > Image section with "image name" or something similar where you could manually enter the name should you wish to change it.
@egg - This would kind of be expected I suppose, both variants will be looking to the same image but as the properties (such as the image's dimensions) are different, it'll be distorted or poor quality. It's something that may be solved with this feature. Once it's implemented I'll try to get an installer for you to play around with
@mwenz - It depends, for a website if you import and resize a photo from a digital camera, you wouldn't want to use the huge original image but an smaller, more optimized version. If it's for a print document then I'd be inclined to agree. Also if the image is changed in anyway, such as a filter applied, rotated etc then we'd have to re-export it with the changes.
Re: Automatic image naming
Probably A so filename is set by default, but as long as it's possible to change the filename much like you can the alt text then it should be good either way.
Re: Automatic image naming
Quote:
Originally Posted by
Rob-Xar
...
@mwenz - It depends, for a website if you import and resize a photo from a digital camera, you wouldn't want to use the huge original image but an smaller, more optimized version. If it's for a print document then I'd be inclined to agree. Also if the image is changed in anyway, such as a filter applied, rotated etc then we'd have to re-export it with the changes.
I'm not really seeing a difference between web/print.
It seems to me that in addition to storing the original filename, you would just need to also save the pathname, be it a full path if outside a project folder or a relative path if in or under the project folder.
This is akin to what happens in a layout application. Output to the various export options--whether the export is to pdf, eBook, html5, etc.--doesn't alter the original image even when/if the image is sized at other than 100%, had various image effects applied, etc. But the effects/sizing is carried into the output format.
Re: Automatic image naming
If you take a photo from a 12mp camera - 4000 x 3000 and say its about 6mb, you wouldn't want to use that in web without reducing the file size and resolution down to only what's needed, otherwise it would only take a few of them to make pages take a long time to download and/or make the website sluggish.
In print the file size is less of an issue.
This is also assuming nobody does anything with the image, i.e. crop it, stretch, apply filters in which we'd need to re-export it.
There's probably some other technical issues I'm not aware about with keeping the photo separate from the project file.
Re: Automatic image naming
Quote:
Originally Posted by
Rob-Xar
If you take a photo from a 12mp camera - 4000 x 3000 and say its about 6mb, you wouldn't want to use that in web without reducing the file size and resolution down to only what's needed, otherwise it would only take a few of them to make pages take a long time to download and/or make the website sluggish.
In print the file size is less of an issue.
This is also assuming nobody does anything with the image, i.e. crop it, stretch, apply filters in which we'd need to re-export it.
There's probably some other technical issues I'm not aware about with keeping the photo separate from the project file.
Yes, no, no...
Just yesterday I helped someone with a print issue where the effective resolution of a 7 degree rotated image was over 2000dpi and couldn't figure out why on earth its output to a print pdf was crappy. Stuff happens for print images, too. And oh, just for fun, it exported to html like crap, too.
You are putting up false arguments, almost like you didn't read anything I wrote. So I'll drop it, Rob.
Re: Automatic image naming
Quote:
Originally Posted by
mwenz
You are putting up false arguments, almost like you didn't read anything I wrote. So I'll drop it, Rob.
Well if your not going to explain why then fine, stuff it then.
Re: Automatic image naming
Quote:
Originally Posted by
Rob-Xar
Well if your not going to explain why then fine, stuff it then.
I did. So I'll go a little slower then.
Just because a file is linked doesn't mean it cannot be resized in Xara applications. Same goes for any effects and/or alterations one may make. One can do these things in any/every application that has/uses linked files.
At anytime, one can replace said image and any/all effects, size, rotation, filters, etc, being a property of the container frame, are applied to the replacement image. Assuming a future where Xara applications retain the name, that name is then used for the exported image when web output is used.
If filename/path were configured to do so, this all is what WebPlus did.
Re: Automatic image naming
Quote:
Originally Posted by
Acorn
Don't overlook all the prior proposals and faults identified:
My main concern is the current disconnect between the Bitmap gallery filename [Right-click > Save > Export], the Names gallery [filename="yetAnotherFileName"], the Page and Layer gallery [Photo 'importFileName (Optimised)' (318 dpi)] and the export image filename [26.jpg &
26@2.jpg].
Acorn
Agree totally!
Really like Egg's suggestion as per he 4th link above
