Re: Bug#44845: Save filelist in Kate

Hi Charles,

On Monday 08 July 2002 02:50, Charles Samuels wrote:
> søndag 07 juli 2002, 05:00 pm, skrev Anders Lund:
> > On Sunday 07 July 2002 19:28, [email protected] wrote:

<SNIP>

> >
> > I completely don't understand?
> >
> > I can have any number of documents open in kate, as long as i have
> > memory... Apart from the fact that you have to manually manage file
> > lists, I don't see the problem.
>
> Well, the problem isn't that I can open only one file at a time in Kate (I
> -can- open multiple files in kate with no problem).  The problem is that I
> often need to have multiple instances of Kate running, because each Kate
> should have a different program I'm editing, with all the files from a
> single app open.

Ok, read on...

<SNIP>

> > > KDE permits Controlled SDI.  In other words, the actual document Kate
> > > should open is the file list.  The current Kate style, MDI, is
> > > specifically not permitted by the KDE style guide!  Please make Kate
> > > Controlled SDI, or at least, provide a nice way to have multiple
> > > instances of Kate running, with different file lsits in each, and don't
> > > make them trample on eachother either.
> >
> > Well, we, the kate developers, agreed on the MDI style we have, as that
> > was what made us feel good. It has a lot of features.
>
> Well, I like the MDI style, but, as I said with controlled SDI, instead of
> having "the base document" for Kate being the text file, it should be the
> file list.
>
> Basically, no difference, except the File menu is like this:
>
> New File
> New Workspace
> ===========
> Open File
> Open Workspace
> ===========
> Save File
> Save Workspace
> ===========
> Close File
> Close Workspace
>
> Or somesuch.
>
> Then I should be able to click in Konq on a "Kate Workspace" file, and it
> will open the workspace (and all the files associated with it).
>
> And even better, It'd be nice if Kate would start up and show you a list of
> recent workspaces.  That way I don't have to wait 30 minutes while all the
> files open up on startup, if I don't want the last used workspace open.

~2-3min for ~100 files here :-\ (and that is actually sometimes what I do...)

Well, I'll start considering how to best allow for something like that, along 
with coordinating with jowenn's efforts. Maybe we could allway use a 
workspace (hm, do I like that phrase?), so if none were specified we just use 
"DEFAULT". That may help keeping seperate session lists.

> > We did have a SDI mode, but it didn't really work well, so it was
> > ditched. Maybe in the future, it will be a choice, but implementing that
> > is non trivial, neither is deciding on designs. Will you help?
> > Personally, since I originally introduced the frame splitting, I am not
> > very keen on it. I really enjoy working with it as it is, though I would
> > like file lists too.
>
> As I see it, Kwrite is the SDI mode, so there's really no conflict.

Uhm, well, kinda. To me, Kate has a host of advantages to kwrite, including 
the file list/selector, as well as several plugins. I mainly use kwrite to 
test changes in the editor component as I code them in Kate...

> > On a side note, Kate has a configuration dialog, amongst others revealing
> > the option "Allow Kate to use more than 1 UNIX process" - maybe not the
> > most obvious text, but it does allow you to run more instances.
> >
> >
> > They won't be able to keep distinct session config though. Yet...
>
> This is exactly the feature I want :D

Ok, I can't promise for 3.1, but I can try! I do have a long TODO though, 
including the kate manual, printing, some plugins... I put this on as well.

> > We are glad you appreciate Kate enough to get frustrated this way, so I
> > hope we can get all that working before too long...
>
> I do!  I really really do.  I hope my complaining doesn't come of as, uhm,
> complaining, because I just love using Kate, aside from this, it's easily
> my favorite editor.

:-)))

-anders