| Age | Commit message (Collapse) | Author |
|
|
|
menu fixups
move enabled into the 'normal menu item' specific data stuff
|
|
any more.
redo the client-menu plugin to work with the new menu api
|
|
|
|
with the keyboard, only when doing it with the mouse.
|
|
split the menu into its own file.
|
|
make workspace changing a grabbed/interactive process like focus cycling is, with the popup and all.
this is some hot shit.
|
|
FIFO menus are the only plugin that takes advantage of this.
Example:
<menu id="root" label="Openbox 3">
<menu id="fonk" label="fonk" plugin="fifo_menu">
</menu>
</menu>
This creates a FIFO ~/.openbox/fifo_menu/fonk to which you can send
menus to. The menus sent to it must be like
<fifo>
<item>
etc...
</fifo>
I think. If my memory serves me right.
It is all hideous, but I just wanted to experiment and see if it was
possible.
|
|
59 files changed, 1691 insertions(+), 607 deletions(-)
Adding the beginings of ObConf. Adding a resistance-config plugin for ObConf.
Creating an obparser library that obrender can use, the kernel can use, plugins can use, and ObConf and its plugins can use. (its just code for using libXml2)
|
|
|
|
Since we have no menu parser see menu_startup() to customize
|
|
|
|
|
|
|
|
|
|
|
|
order te startup so that plugins can set up their config shit before parsing the config, then the config is parsed, engine is loaded, and finally the plugins are officially started.
|
|
|
|
|
|
start a focus plugin.
|