KDE/kdevplatform

[David Nolden]

Am Montag 27 Juli 2009 18:13:29 schrieb Andreas Pakulat:
> On 27.07.09 18:07:38, Andreas Pakulat wrote:
> > On 27.07.09 17:11:16, David Nolden wrote:
> > I didn't say that you cannot create the sane API right now and port all
> > plugins to use it. Just the multi-mainwindow part needs far more work.
>
> I'm sick of this, do whatever the fuck you want. I'm not using
> multi-mainwindows (yet), so if things start to fall apart for that use-case
> I don't care.
>
> If things start to fall apart for single mainwindow, I'll just create a
> stable branch and revert the changes there, so that I can have something
> usable.

We _have_ multi-mainwindow support now, if you want it in numbers, working 
maybe like 5% (You can open it, and use the editor). Now I want to improve 
that to 15%, without breaking single-mainwindow. In practice I use single-
mainwindow 100% of the time yet.

There is absolutely no reason for those changes to break single-mainwindow 
use.

Maybe your broken build gave you a bad feeling about those changes. But here 
they have been perfectly stable in the single-window usecase, so I cannot let 
you flag them as "inherently unstable". There is nothing to worry about.

And yes, multi-window will not be working perfectly for quite a time, but that 
does not contradict trying to improve it stepwise!

So to summarize the problems that need to be solved:
- Toolbar management is slightly broken (Not specifically a fault of multiple-
main-windows)
- Shortcuts are not reloaded in additional mainwindow when changed in first
- Shortcut configuration in additional mainwindow is unstable

But all those problems have been there before even if not that visible, and 
are only effective when multiple-mainwindow is actually used. So if we feel it 
is not stable enough, we can just remove the "New Mainwindow" action before 
releasing KDevelop 4.0, and be fine.

Greetings, David