Two things come to my mind here.

On Tuesday, April 02, 2013 23:49:57 Sven Brauch wrote:
> Hmm, yeah, but it has been like this for a very long time now and I've
> never heard anyone complaining (and I hear a lot of complaints) ;)

1st) Not getting complaints does (unfortunately) not imply that the solution 
is perfect. So this alone is a very weak argument.

> I'm not sure, but I don't really see a need for changing anything in
> kdevelop... I'll ask the others about it.

2nd) To sum up: KDevelop does not have a status bar to save space. 
Interestingly, Kate Part has to add the status bar in vi-mode, otherwise 
KDevelop does not have a status bar. So you don't want a status bar while
at the same time wanting a status bar. Do you see the irony? :-)

From a Kate developers pov, this means that the code/solution in Kate Part is 
not as it should be (more code to maintain), which is something I (personally) 
never like that much.

Cheers,
Dominik

> Best regards,
> Sven
> 
> 2013/4/2 Christoph Cullmann <cullmann@absint.com>:
> >> But where? An extra bar for just the view mode is kind of wasteful.
> >> And even *more* stuff in the tab bar is really not what kdevelop
> >> needs...
> >> Isn't the mode sort of obvious from the cursor shape anyways? I
> >> cannot
> >> remember ever having a problem with not knowing what mode I'm in.
> > 
> > Hi,
> > 
> > I guess for Vi Mode its not that obvious and any normal application has
> > such a status bar around ;) I am not sure if the place in the tab widget
> > header is a that nice location, either, but thats an other issue.
> > 
> > Greetings
> > Christoph
> > 
> >> Cheers,
> >> Sven
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel