Re: Re: Why all the different string types?

Jens Miltner wrote:

> 
> Another thing to consider would be to make the sandbox settings  
> local, i.e. don't use global variables to hold the values: at least  
> MacCvs allows to open more than one sandbox browser simultaneously  
> and currently, it's a bit of a hack to switch settings when a window  
> comes to front (because settings are global in the current  
> implementation).

Jens, thanks for the reply.  I don't use the Mac, so please help me 
understand what you mean by local sandbox settings.  Do these get 
persisted or is their lifetime only while the app instance is running? 
If they get persisted, what differentiates one set from another?   Are 
they connected to a specific project, like non-global settings?  If so, 
could we persist them in the same store that maintains the project settings?

Perhaps what we should do is use the global settings as the default, and 
allow the project settings to override.  If we do that, I'd like to 
break out Admin-Preferences into two separate menu items: Global 
settings and Project settings.  Having two sets of the same settings in 
a single dialog box would get very confusing.

Let's be explicit.  In gCvs, on the Preferences dialog is a Globals tab 
with the following settings:

Checkout read=only
Use TCP/IP compression
Quiet mode
Dirty files support
Prune empty directories
Supply control when adding files

In WinCvs, I see

File attribute (equivalent to Checkout read-only in gCvs)
CVS Messages (equivalent to Quiet mode in gCvs)
Prune empty directories
Compression level
Encrypt communication
Checkout text files with Unix LF
Disable splash screen
Supply control when adding files
Match path case with Entries case
Logout automatically after N minutes

Are these the ones you are referring to, or are you referring to 
everything in the Settings dialog?

Regardless, I still like the idea of having Project setting inherit the 
global ones but allow for override.  But now having written all this, it 
sounds like a better name would be "Default settings" and then "Project 
settings".

Some things seem truly global, like path to CVS executable, preferred 
external diff program.  Why would you want that to vary by project? 
Perhaps we need to revisit what is a global and what is per project.

-- 
Guy Rouillier


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/