Quoting Andy Levy <andy.levy_at_gmail.com>:
> On Thu, May 15, 2008 at 7:35 AM, <gibsoa02_at_student.uwa.edu.au> wrote:
>> Quoting Andy Levy <andy.levy_at_gmail.com>:
>>
>>> On Thu, May 15, 2008 at 12:38 AM, <gibsoa02_at_student.uwa.edu.au> wrote:
>>>>
>>>> Quoting Andy Levy <andy.levy_at_gmail.com>:
>>>>
>>>>> On Wed, May 14, 2008 at 7:14 AM, <gibsoa02_at_student.uwa.edu.au> wrote:
>>>>>>
>>>>>> I originally had that train of thought but the thing which made me
>>>>>> think
>>>>>> otherwise was when i looked at all the overlay icons in the options.
>>>>>> There I
>>>>>> could see an example of a locked folder. Is this just an
>>>>>> unused/redundant
>>>>>> icon? If so, is there any chance of adding an option for this feature?
>>>>>
>>>>> Remember that those lock icons are just overlays on top of the
>>>>> "regular" icon. Rather than code a special case in the Settings dialog
>>>>> box to not show the Locked overlay on folder icons, I imagine it's
>>>>> easier to just loop through all icon types and show the overlays.
>>>>>
>>>>> Any directory-locking feature would first require support from the
>>>>> Subversion libraries themselves. What would be the use case requiring
>>>>> such a feature?
>>>>>
>>>>
>>>> The reason behind having a lock icon showing on the folder level is
>>>> because
>>>> we have a development working folder accessed by all our system
>>>> programmers
>>>> which contains multiple sub-projects that later compile into one. When
>>>> someone is working on a project, they are required to lock it as it is
>>>> mainly binary files. This is done at a folder level.
>>>
>>> In other words, you have multiple developers sharing a working copy.
>>> Which negates half the reason to even *use* a version control system
>>> in the first place.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
>>> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>>>
>>>
>>
>> True.
>> Be that as it may, the choice was this or Visual Source(Un)safe so I guess
>> you can see where I'm coming from. The only reason we has a single working
>> directory is because our primary programming method follows the
>> lock-modify-unlock method which only requires one working folder.
>
> No, it doesn't "only require one WC." Far from it, in fact. I think
> you're misunderstanding how locks actually work.
>
> Give each developer their own WC. It's now SVN is intended to be used.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>
>
We were wanting to keep the same working directory so that other
developers can easily identify when a directory (in our case
sub-project) is locked. We were going to use the svn:needs-lock
parameter on all sub-projects but the problem is that the program we
use to compile (Citect SCADA) requires the files to not be read only
before it will compile the full package.
Thanks for all the help. We will most likely be switching to separate
working directories in the coming weeks but were hoping for an easy
way to see directories that have locked files in it by a lock overlay
on the parent directory :)
Regards,
Andre Gibson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-16 00:49:32 CEST