I have found myself using different methods to make designs, but I was wondering what was the best practice for archiving FINISHED products.
In terms of anchor and path complexity: would it be best to save files as paths with width controls, or should I be outlining strokes and flattening as compound objects?
If it turns out that the results would vary with every project, then I can accept saving two versions and deleting whichever happens to be the bigger file.
Well now, no need to drag my beliefs into this, but if you must know...
My understanding is that progress should be reduced to it's simplest form at regular intervals. The extraction of modular devices (commonly used symbols, purposefully arranged actions, etc.) from previous projects is what drives "development". I have no intention of destroying my work. Just making sure that snapshots exist in case my memory/workspace fails me.
That said, let's pretend I have a client with a portable device of limited capabilities, and I have to keep the poor things CPU from lagging by giving it less instructions when redrawing the vector graphics. Then let's throw in a time limit that only gives time for a few adjustments:
How will I ever prepare this file?
Does printing to PDF handle the vectors differently than say, using the "Save as" function? Either way, this is not very far off from a consideration I had before, about exporting vector-only designs as SVG's and using a supporting browser for the visuals.
The options I considered and the one provided looks great for file size (removing editing tags for clients makes perfect sense), but it still does not address the lack of hardware acceleration on a portable device. OK, I know that the devices we have today can handle this situation with ease. This really meant to be educational so that things can be brought to a larger scale in the future.
For instance, indexing a bitmap image does wonders for file size, but display speed ultimately comes down to resolution. I am trying to apply the same principles to my vector work.
I believe the saving option Smallest File Size is about as good (small) as it gets.