Ok, I've given this some thought and talked this over with others, and I
think this is the best idea we've come up with:
Currently, when bbkeys fires the Next Window message, blackbox catches the
message, and switches to the next window.
The same functionality is used for catching this event as for when the
button on the toolbar is pressed.
I propose that instead of blackbox handling the window cycling call from
bbkeys (it should still internally handle the toolbar one), it instead
passes it to the bbcycle application. This application could cycle windows
in any fashion seen fit, classic style, KDE style, or any style devised at a
later date.
I'm not sure if this would actually reduce blackbox's code size, or if
something would need to be added to pass the message along to bbcycle. But
this would be something generic which could be reused, and is, imo, the most
flexible option for this.
This method would not require any changes whatsoever to the bbkeys
application, which is as it should be, as it is still the NextWindow
functionality, and the user shouldn't have to change their key bindings to
change how they cycle windows!
I'd especially really like to hear what you core developers think of this,
since it encrouches on your territory somewhat :-) but I believe this would
really improve the window manager and keeps most of the work out of the main
codebase.
xOr
