apaku at gmx.de
Tue Dec 8 13:03:31 UTC 2009
On 08.12.09 13:55:33, David Nolden wrote:
> Am Dienstag 08 Dezember 2009 13:48:13 schrieb Andreas Pakulat:
> > On 08.12.09 10:15:06, Niko Sams wrote:
> > > On Tue, Dec 8, 2009 at 04:40, David Nolden <zwabel at googlemail.com> wrote:
> > > > Am Montag 07 Dezember 2009 21:37:44 schrieb Niko Sams:
> > > >> On Mon, Dec 7, 2009 at 21:24, David Nolden <zwabel at googlemail.com>
> > > >> wrote:
> > >
> > > - the new instance takes it's time, some loading indicator would be nice
> > You mean like the splashscreen? Or do you mean for the projects being
> > loaded?
> > > - would it make sense that creating a new session has all settings
> > > copied from the current one (except projects, workingsets and global
> > > launches)
> > Thats why in the session-dialog there's new and clone. IMHO both have
> > use-cases so if we supply New in the menu we should have Clone too.
> Only if it's clearly defined what the distinction between "New" and "Clone"
> is. Right now if it was in the menu, I wouldn't have a clue which one to
> If you mean by "Clone" creating a new session that also contains the same
> projects, I cannot see a real use-case for that. Why would you want to work on
> the same projects within multiple sessions?
Hmm, thats true. Though if more of the settings in configure kdevelop are
inside the session that one might want to take at least those into a new
You will have a long and unpleasant discussion with your supervisor.
More information about the KDevelop-devel