Re: Re[2]: gCvs GTK2

Guy, Richard,

I am not sure that the re-write of preferences is such a good idea. It's
fairly easy to extend current model to do almost everything and if the only
purpose of change would be to allow copying between different architectures
then it's not worth the hasle. For example the whole set of fonts can easily
be packed up together into one setting

There is alot of things to do without that. I for one would like to see gCvs
and MacCvs to start using new CVSROOT arrangements where it's effectively
removed from the settings and used as a command setting for commands where
it's actually needed. Just do a search for INTERNAL_AUTHEN macro in the code
to see what I mean. It would allow to remove Authen.cpp/h files - coupld of
thousand lines each - and code would look much cleaner in many places.

Best Regards,
Jerzy

----- Original Message ----- 
Wrom: WCUFPEGAUTFJM
To: [email protected]
Sent: Sunday, January 09, 2005 21:39
Subject: Re: [cvsgui-dev] Re[2]: gCvs GTK2


On Sun, 9 Jan 2005 14:53:36 +0100
Richard Wirth <[email protected]> wrote:

>
> Hello Guy,
>
> From the last mail:
> RW> And it looks to me like we should
> RW> implement an interface and a dialog to choose all the different
> RW> fonts for all different parts of the GUI, not only for the
> RW> ConsoleWindow. And ofcourse make this persitent.
>
> So what about extending the Admin->Preferences dialog to choose the
> font for GraphView, FilesView, FoldersView, ConsoleView and
> Menues/Toolbars? It's not much to implement.
> I'm using gCvs at Linux and Solaris at the moment. But on varying
> resolutions and on different X-Servers. So using fixed defaults is
> often a bad thing.
> But if we do so, the $HOME/.gcvsrc should not be used for the Gtk-2
> port any more. It would make the old gCvs 1.1 conflicting. I'd like to
> put all persitent values in the $HOME/.gcvs directory (like the browse
> locations already are). And it would be good if the persitent settings
> where not stored in machine dependent binary format but in textual
> representation. It could than be copyed easyly to another
> architecture, and a simple text editor could be used to modify /
> correct a setup. Any sugestions about the textual format (any
> implementations for reuse????)?

Interesting you should raise this topic now, I was just thinking about
it last night.  I'd like to separate project-specific preferences from
common preferences.  Fonts would be common preferences, as would editor,
cvs version; looking now at gCvs Preferences, I would say everything
on the gcvs tab plus CVS version from the General tab are all common
preferences, while the rest appear to be project-specific.  This
separation becomes even more relevant if we want to have a whole set of
font selections.

As for format, I'd suggest either a properties file or XML; I have no
strong preference for either, though properties would probably be
lighter weight.

-- 
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 the Yahoo! Terms of Service.


 
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/