[Kst] RC files

[George Staikos]

On Tuesday 11 January 2005 16:30, Barth Netterfield wrote:
> On Tuesday 11 January 2005 14:34, George Staikos wrote:
> > kstautosaverc:  There is no point in this at all.  It should go through
> > KstSettings, and should be saved as a subgroup in kstrc.  Do we need a
> > migration script here?  I don't think so....
>
> I agree.

  And already done. :-)

> > kstextensionsrc: This needs to exist so that extensions don't clobber Kst
> > settings, and to keep kstrc small.
> >
> > kstdatarc: Ditto above.  This is for data sources only.
>
> What goes in these two?

   Extensions and data sources write their settings there.

> > kstrc: Lots of problems here:
> > 1) passwords are not even obscured.  At least base64 them.  We could also
> > use KWallet here.
>
> These are for elog?  A simple obscuration is fine.  ELOG does not support
> encryption in any way.

   Correct.  Using KWallet would just be to store the password.  Actually when 
ELOG is ported to use kio_http, if the authentication is done via HTTP, then 
KWallet support will be transparent.

   The other problem is EMail password - that really should be in KWallet I 
think.

> > 2) [Kst] is full of things that don't belong there.  We need to regroup.
> > This includes:
> >    i) Email settings - should go to an [EMail] group and drop the "EMail
> > " prefix on keys
>
> ok

   Done.

> >    ii) Grid lines - should go to a [Grid Lines] group I guess, or is this
> > something that really belongs in the .kst files instead?
> >    iii) X Axis display/interpret/etc - Should go to a new group too?
>
> There are a bunch of things that get cached by vector defaults.  I think
> that the spirit of these is the same.  These are default values which are
> implemented for filling dialogs, but get over-ridden by kst files.  As for
> grouping....  don't care.

   Ok, already regrouped.

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/