At 10:43 AM -0600 1/12/06, Oliver Block wrote:
>On 1/12/06 12:56 AM, "Dan Shoop" <shoop@iwir...> wrote:
>>...Well since it's not advised to save/open files directly from
>> photoshop to a fileshare that might be the first thing to fix, the
>> workflow. ;)
>We have found that the costs of opening/saving Photoshop files directly to a
>fileshare are often outweighed by the benefits. Many design shops and ad
>agencies are not willing to enforce workflow policies that produce
>consistent movement of files from workstations to the server. Many of those
>shops find that the small speed decrease and occasional troubleshooting
>involved with a properly configured file server (and network) are well worth
>the benefits of having all their files stored centrally at all times.
Then you stand to reap what you sow. Specifically Aodbe doesn't
support it. Period.
>1) Many of our clients choose not to require their users to move Photoshop
>files to the server immediately after the users finish working on them, AND
>2) Those same clients want all their files to be on a central file server at
>all times for the purposes of information sharing and backup
>...I would be interested to hear success stories in which a technological or
>workflow mechanism reliably facilitated #2 above without having users open
>and save their Photoshop files directly to a file server.
Then implement an XSan.
Or run a Code Versioning System.
> Ideally, I would
>like a check-out mechanism that would bring files to the user's desktop and
>then check them back into the server when the user is finished with the
>files, but many of our clients cannot afford such systems (or at least can't
>afford the systems I've evaluated).
Oh please, some of the most popular Code Versioning Systems are free.
Like cvs, subvsersion, et al.