I’m wondering what the advantages and disadvantages of having a ‘common’ versus ‘separate’ resources folder is?
Are there any problems that I might come across if I were to change my 200 page site from ‘separate’ to ‘common’ resources folder?
I’d like to do this to simplify things, but am worried that it might cause broken links, lost graphics, or even slow my site down - would it be more hassle than it’s worth, or should it work seamlessly and be a good thing to do?
Using seperate Resource-folders has noting to do with speed. Seriously, I can’t thing of any advantage of using seperate folders. Since day one I’ve allways used one common Resource folder.
If I now tick the common folder option, will Freeway need to get the original resources from my hard drive again, or will it just do it on the fly from the many separate resources files that have accumulated?
The reason I ask, is that I may have lost quite a few of the original files I had on my desktop (the ones I dragged and dropped into Freeway) after my old laptop broke down.
No, it’s only got to do with the output. The origional imput (your media) remain the same … it’s just that you can choose where the output will go.
And by the way … Freeway allways needs the origional files … allways. So now you seem to have lost ‘some’ files, Freeway will generate output from the preview. There is no origional file, the only source he has left, is the preview. So your output will be of less quality than when you have the origionals.
I know it’s a large document, but you should concider backing up the allready created ‘Resources’ , and re-import these as pass-through images. That way Freeway won’t touch those images anymore, and you still have imputfiles that are the same quality as the output.
Sometime around 20/5/09 (at 02:30 -0400) Richard van Heukelum said:
your output will be of less quality than when you have the origionals.
Strictly speaking, the output could be of less quality. If the
image isn’t changed on the page then it should be okay, but if it is
scaled up then absolutely: it will be built from the scaled-up
preview image, which will be lower than screen resolution. Soft,
fuzzy, imperfect.
Of course that’s just a minor detail. The moral of the story is
exactly as you say: keep your original media safe and available.
I know it’s a large document, but you should concider backing up the
allready created ‘Resources’ , and re-import these as pass-through
images.
Actually no, not for this particular point.
Using pass-through images will mean that Freeway won’t need to
regenerate them, BUT it won’t prevent it from needing the originals.
In fact, it makes it even more important that they are available as
this tells Freeway never to generate images but always to upload the
original imported image files directly. Plus it makes things less
flexible.
I know I keep saying this, but it is worth remembering that using
Freeway’s pass-through feature imposes restrictions and
responsibilities that aren’t an issue when letting Freeway do its
stuff normally. Sometimes it is a good thing, but it isn’t something
that should be done without thought.
And … I know Keith, but after him losing the origionals there’s no alternative -for now- than using the outputted (is that actually a word?) media files as pass-through origionals. Anything else will deliver less quality. I would personally feel more secure anyway, having control over what will be used in what way.
I’m glad I have TimeMachine running 24/7. That and lots of online storage.
Never used my backup’s before, but now TimeMachine makes it so darn easy … I recover anything, even the bookmark of that particular site I had on my desktop a couple of days ago … brilliant.