Packaging Files

[REACT]

I'm currently testing the software to consider whether I should purchase.

All three seem incapable of packaging files in one folder or even to package completely.
Is it just me? Or is there some setting I've overlooked?

[GarryP]

Welcome to the forums @REACT

Did you look at menu “File → Save as Package” ?

[REACT]

I did...
I saved as a package to my desktop from each of the three softwares.

In every packaging case, Three items appeared SEPARATELY on the desktop...

1. A 'Fonts' Folder (which did not contain every font from the document)
2. An 'Images' Folder
3. A 'Packaged' File with the document name but NO File Image.

Obviously, when you're working professionally, this would be unacceptable.
 

Edited March 24, 2023 by REACT

[walt.farrell]

The Fonts folder should contain all the fonts used in the document, if you chose to include them while Packaging. One exception: It will not contain any fonts that you installed via .affront files, but those used fonts will be included directly in the .afpackage file itself.

Having separate Images and Fonts folders helps in some scenarios. But if you're going to physically send the package to someone else (rather than sharing over a network), then yes you'll need to zip the 3 items together.

[REACT]

Adobe has separate image and font folders as well as the original document - but they all come packaged in a single folder. 
You have the reassurance of knowing everything will be contained in that single folder. 

But separate folders and files all over the place is not in my view, confidence inspiring. In a high-paced workflow,
you shouldn't need to be worried about whether something has been missed. Or have to waste time searching for separate folders and files.
 

Edited March 24, 2023 by REACT

[REACT]

The whole point of packaging is peace of mind. That you don't have to go searching for all the elements used in a job.
The system does it for you.
And when you package to send to a printer, supplier or client, you don't find yourself in the compromising position
of being told you omitted something.

Edited March 24, 2023 by REACT

[GarryP]

When you create a package you have to select a folder in which to package things.
Once you have selected that folder, all of the ‘stuff’ for document should be in that folder, and sub-folders of that folder.
Is that not happening for you?

[REACT]

Yes. I've done that... but you don't seem to be getting my point?

Even if you select a folder, they come SEPARATELY into that folder and you have to manually create a new folder
to insert them into in order for them to be properly packaged. Which means you can't be sure that everything has actually
been packaged properly. And the original file as I said earlier, has no file image - so you're not really sure what it actually is.
And also as I said earlier, the files in both the font and image folders do not look complete.

I have none of these issues with Adobe. Which would make me worried about cancelling my Adobe subscription and moving
to Affinity.

And Garry, I'm a professional with 39 years experience under my belt, so I do actually know what I'm doing.

Edited March 24, 2023 by REACT

[Hangman]

It should be noted that the .afpackage file does not include any fonts or linked images used in any placed .afdesign or .afphoto files which to me feels like an omission...

2 minutes ago, REACT said:

Even if you select a folder, they come SEPARATELY into that folder and you have to manually create a new folder
to insert them into in order for them to be properly packaged.

Or you simply zip the root folder that you've selected to add your .afpackage files to, there's no need to manually create any new folders...

[Old Bruce]

I have always chosen an empty folder. One that I create either at the time of export or earlier. This avoids overwriting files. Embedded image files are not included in the export.

[Old Bruce]

having said what I said I should point out that an automatically created and Named folder would be a nice touch.

[REACT]

I don't get what this 'overwriting files' thing is.
It's not an issue with Adobe. You can't overwrite anything in Adobe unless you deliberately want to.

[Hangman]

6 minutes ago, Old Bruce said:

Embedded image files are not included in the export.

Strictly speaking they are in as much as they are embedded in the document (rather than linked), so the respective embedded files are there by default as layers in the layers panel rather than as separate standalone files, if that's what you mean...

[REACT]

The packaging thing is a real deal breaker for me.

I've only tried Affinity for one day so far and there are many things I like.
But if I've found a deal breaker on day one, I wonder what other nasties lie in wait for me. 🤔

[Hangman]

9 minutes ago, REACT said:

I don't get what this 'overwriting files' thing is.
It's not an issue with Adobe. You can't overwrite anything in Adobe unless you deliberately want to.

Same here, it's warning you that you are about to potentially overwrite existing files and asking if you are okay to do that...

[REACT]

1 minute ago, Hangman said:

Same here, it's warning you that you are about to potentially overwrite existing files and asking if you are okay to do that...

If there is any possibility of overwriting, Adobe simply adds 'copy' or 'copy-1' to the automatically named packaged folder.
Of any file for that matter.

[REACT]

I'd pay double for the Affinity suite if they just bothered to address all annoying issues and glitches like this.

[Seneca]

2 minutes ago, REACT said:

I'd pay double for the Affinity suite if they just bothered to address all annoying issues and glitches like this.

What are those issues and glitches you would like to pay double to be fixed. The fact the the program rightfully warns you that you are about to do something you might regret later?

[REACT]

12 minutes ago, Seneca said:

What are those issues and glitches you would like to pay double to be fixed. The fact the the program rightfully warns you that you are about to do something you might regret later?

Have you actually read this thread?
Sounds like you haven't.

[Seneca]

1 minute ago, REACT said:

Sounds like you haven't.

You are right. I take it back.