1

Some people think of programming like building new things with pieces. Why don't using this approach in desktop? We have OLE on Windows, have KPart on KDE, had Banboo on Gnome Desktop, etc. But.. there's still no user.

The idea is about:
- Letting application register interfaces window is supporting to WM's(preferable by DBus)
- Allow user to move one window in corner of another and select type of connection, based on information provided by application in first point
- One window will register own interface to another window

Use case? Imagine KDevelop can use any console widget/backend, not only KonsolePart. User simple move xterm to corner of KDevelop's window, select "providing console functionality" and accept. KDevelop will now gets information new window wants to cooperate as console window. In next step KDevelop will configure xterm, setting current working directory, aliases, etc. (if possible, of course). Another example is moving one Dolphin's window to another Dolphin's window and select plain or 'file browser'. When selecting plain, then nothing happens, but user can move these two windows meanwhile. If selected file browser, then one of dolphins window will hide some widgets, because they gets configured by another Dolphin instance. It can hide file information panel, places panel, etc.

What do you think?

Another example could be attaching vim-command-line panel to text editor window, so this panel could control text editor. Super, right?! Or programming language syntax autofill/syntax checker control to IDE's window.