[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Kate Sessions (was: Re: KDE/kdesdk/kate)
From:       Dominik Haumann <dhdev () gmx ! de>
Date:       2007-07-12 7:35:25
Message-ID: 200707120935.25719.dhdev () gmx ! de
[Download RAW message or body]

On Thursday 12 July 2007, Dominik Haumann wrote:
> On Thursday 12 July 2007, Dominik Haumann wrote:
> > SVN commit 686651 by dhaumann:
> >
> > install default.katesession into the global KDE folder.
> > This way, we can provide sane defaults.
> > If the user invokes "Session" > "Save as default" then the defaults are
> > saved in a local default.katesession file (in
> > .kde/share/apps/kate/default.katesession) If the local
> > default.katesession file exists, it is used and the global one is
> > ignored.
> >
> > CCMAIL:kwrite-devel@kde.org
> >
> >
> >  M  +16 -2     app/katesession.cpp
> >  M  +8 -5      app/katesession.h
> >  M  +1 -1      data/CMakeLists.txt
> >  A             data/default.katesession
>
> My plan was as follows:
> If you start Kate the first time in KDE4, it copies the
> default.katesession to .kde/share/apps/kate/sessions/`i18n("Default
> Session")`.katesession.
>
> This way, we have the same behaviour back as in KDE3 times, but more
> flexible:
> 1. we can have sane defaults in the first place by fine tuning
>    default.katesession
> 2. we initially have a i18ned "Default Session", which you can even
> rename
>
> #1 is implemented by this commit.
>
> #2 is still a todo.
>
> Thoughts welcome.

Another idea would be: When no session exists, simply start a new session 
without popping up the session chooser. This way, users not wanting/using 
sessions are never confronted with sessions.
This would be another option to #2 as I see it....

Dominik
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]