Jump to content


  • Content Count

  • Joined

  • Last visited

  1. + 1 for integration with any Zeplin /Figma-like online service so coders can easily explore mockups in read only mode
  2. I never asked to change affinity format, I asked to add an option to use PNG with metadata to save source files
  3. https://pngquant.org/ This is a 8bit PNG compressor with smart palette generation and adaptive dithering algorithm that allows to produce way smaller png files Realy a lifesaver in some situations
  4. and for me this is very annoying not to see real size preview, here is an example - you can see literally nothing :~)
  5. Both PNG and TIFF support custom data blocks (you have to be a programmer to use that file format feature), and vector objects with layers is a data which can be stored inside that image file This is like a postal envelope, from outside it looks like a rectangle of paper, but inside it can contain other pieces of paper with images, text or numbers. All programs which do not understand that data will ignore it and recognize this file as a flat image, but editor which added that data going to recognize it and load as source file.
  6. ok, it was not fair enough as long as one of my layers was a raster so here is a new test: huge but simple file (attached) with 8 2048x2048 artboards - total area 9488x4509 (this is close to a maximum than I ever going to need as GUI designer) afdesign with 500x500 preview: 39kb (yeah sure this is vector data it is tiny) tiff - no layers: 1076 kb tiff - with layers: 1085 kb (as expected only 9 kb of layer data ) png - no layers: 613 kb (as expected way smaller than tiff) so if you supply a full-size preview PNG with layers data it is going to be 622 kb and my point here is that png is a better format than tiff for this purpose so 600kb for the full-size preview is awesome, I surely pay this 600kb to have a full-size preview, yes this is easy to compress file, but even with most complex image compressed png of that size should not be ridiculously huge test.afdesign
  7. no layers data compression completely unrelated thing to preview compression, it is possible to embed whatever you want into a PNG file, any ZIP, RAR, ARJ or whatever affinity uses for compressing layer data
  8. yes TIFF supports ZIP and LZW both produce a worse result compared to PNG as an experiment, i've saved same file 3 times: afdesign with 500px preview - 735KB png without layers data - 707KB tiff with lzw compression and with layers - 1.6MB if png with layers was possible it would be less than 1.4MB (full-size png preview + affinity layers - 500px preview)
  9. wow, didn't notice it before, maybe because export with "Save Affinity Layers" on is way more logical in "save as > TIFF" menu yes, this is it! the only thing is that PNG is way better-compressed format when TIFF files can get really huge PNG going to stay reasonably big "Save Affinity Layers" checkbox for PNG export (what is a synonym for "save as PNG") going to make me happy yes this is a good point, not always and not everyone needs a full-size preview but an option to configure preview size would be a great thing to have To be precise I was not asking to change or replace the affinity file format, I was proposing to add an option to save as "png with affinity layers"
  10. Yes my as well, but those previews are limited to 500x500 pixels, way I suggest going to allow full-size previews There is no need to change affinity file format structure, the only change is to add a wrapper this is like a Christmas gift wrapped in a colorful paper, from outside you see the nice package, but inside it can contain anything There is no need to regenerate high-res preview during work, only when the user explicitly asks to save a file.
  11. am I the only one who needs to have high-resolution previews for source files...
  12. Affinity files have previews, those previews are limited to 512x512 what is, to tell the truth, is not enough, also those previews are not displayed by operation system by default. Some projects i'm working on (UI-design) have hundreds of source files, and it is impractical to recognize those files only by filename or even lo-res preview :( I really love approach Macromedia took with Fireworks file format, they made it so source-data appended to a png image file all image viewers and file browsers recognize it as a picture and show high-resolution preview, but editor knows that besides preview there is a source-data, and when you open that png in editor it is actually a vector source file To remove confusion which png file is a flat raster image and which is a source file, extension suffix can be used kind of .af.png A bit of technical details: This is possible because of the patent-free nature of the PNG format, and it's chunk-based storage layer structure. Data in png file is stored in "Chunks", chunks declare themselves as critical or ancillary, and a program encountering an ancillary chunk that it does not understand can safely ignore it. So it is possible to put native affinity source file data into such chunk. Png serves as a container with nice cover image. And what is the best part of this approach is this is very simple to implement - you get the best support by all image viewers, by simply gluing 2 files together.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.