Problems with new session support

[David Nolden]

Am Mittwoch 27 Januar 2010 23:06:58 schrieb Milian Wolff:
> On Wednesday 27 January 2010 22:22:29 David Nolden wrote:
> > Am Mittwoch 27 Januar 2010 18:36:48 schrieb Milian Wolff:
> > > And for that I would need to start every single one of my sessions,
> > > just to give them a name. This totally blows imo... I'd like to have
> > > the old dialog back...
> >
> > I think the old session management dialog was simply one dialog too much.
> > "Opening" a session means simply clicking it, what is so hard about that?
> 
> There is nothing "hard" about it. What sucks is that it's simply slow!
> Starting a new session means opening potentially many projects which and
> triggering parse jobs. Even when I just want to rename something, my PC is
> instantly slowed down. Sure, nowadays I can close KDevelop rightaway, but
>  imo it still sucks.
>
> Oh and of course the "to rename I have to close my existing session".
> 
> > Also the old dialog didn't work right. It couldn't deal with multiple
> > sessions of the same name, it didn't show the contained projects, etc.
> > etc.
> 
> Yes, but this could be improved, no? I really like that you added the
> contained projects and that we can now work with multiple sessions with the
> same name (even though that would be something I'd personally forbid ;-) ).
If you like you can fix the dialog. I still won't find it very useful though.

> > > And note: I have nearly always more than one KDevelop instance running
> > >
> > >  (with different sessions of course) and this also is utterly
> > > unsupported right now. Having the --sessions switch will help, but I'd
> > > still like to see a way to start a session from inside KDevelop without
> > > it
> > >  automatically closing my last instance!
> >
> > Multiple running KDevelop instances are another good reason to not allow
> > deleting or renaming a not-active session: It might be active in another
> > KDevelop instance, so you should better leave it alone.
> 
> But one and the same session can be opened at once, which would have the
>  same problems?
That's something that needs fixing as well.

> > If you like you can add a "Start Additional Session" button to the
> > session menu, then you could spawn another kdevelop instance.
> 
> And this would be less clutter than a button that opens a dialog to manage
> sessions?
One has nothing to do with the other, unlike the dialog, this button would be 
really useful.

> What would speak against making the session buttons open another instance
> without closing the existing one? If the user wants to switch, he can
>  simply close the other instance, no? I personally would find this far
>  better adapted to my personal workflow. What do you think?

Because I think that the more common usecase is _switching_ and not opening an 
additional session. You as a kdevelop developer might be a bit biased as you 
probably often first open a kdevelop session and then an additional testing 
session, but I think that's not the common usecase. It would be very 
inconvenient if you just want to switch to another session, and have to 
manually close the old session behind yourself through "ALT+TAB" etc..

If there is serious evidence that the more common usecase is "opening an 
additional session" then we could change this, but I highly doubt it.

Greetings, David