andsee

That's good news, fingers crossed it will be released soon. We are just evaluating plastic at the moment and need to avoid losing work when two people work on a binary file simultaneously, as selecting one or the other as the result of a merge is not acceptable. What are your thoughts on allowing a project to be setup so that certain file extensions or pattern matches can only be checked out exclusively? I would hope that such files also automatically received the make read only option on clients. Our ideal working scenario is that any files as possible work in the plastic way, in that they can be writable all the time on the client and edited by anyone at any time. These files would be any file that can be merged or that carries little risk of loss of work if a merge question of select which one you want is presented. However some binary files need protection and you don't want users changing them accidentally without first ensuring that no one else is working with that file. I can't see a safe way of working with Plastic without this.