Menu Pipes in Fluxbox
Posted: Mon 21 Jul 2014, 17:36
Hi.
A search on the forum for Menu Pipes in Fluxbox did gave a result of two postings. Though I could not find any useful hints to this.
So I've made a little trial and error until I found a way to include a static build file containing code for the Fluxpup Menus.
Example for a static menu category:
This has been saved as /root/.fluxbox/menu.add
Example for code to add to the file /root/.fluxbox/menu.base:
Attached Images shows the result after refrshing the menu.
To have a pipe -let's say for some scripts in /mnt/sda1/my-scripts- one just would need to write a little script that reads the directory /mnt/sda1/my-scripts and would echo its input (output of reading) in a modified form like this:
That's all.
I'm using Menu Pipes heavily in my LazY Puppy builds, but almost used in Openbox, which uses real Menu Pipes, that are updated immediately when opening the Menu.
Currently I'm creating such feature for JWM in L.A.S.S.I.E., but statically like this one here, that needs to be updated manually. To have a static Menu Pipe to be updated manually is the way I do prefer now, since there is a lot of Scripts, RoxApps and PortableApps for Linux and Wine included in my external Application directories, so the real Openbox Menu Pipes do take sometimes 1 or 2 seconds to give access to the menu category.
Since the content of these directories doesn't change very often, it's not really needed to update those Menu Pipes each time when opening the Menu. That's why I prefer the "static-pipes" now.
However: atm I don't have any time to do any further work for Menu Pipes in Fluxpup, I decided to post this here. Maybe someone else is interested in this and might do some work for some scripts do make users able to create easily Menu Pipes for Fluxbox.
RSH
A search on the forum for Menu Pipes in Fluxbox did gave a result of two postings. Though I could not find any useful hints to this.
So I've made a little trial and error until I found a way to include a static build file containing code for the Fluxpup Menus.
Example for a static menu category:
Code: Select all
[submenu] (LazY FluX)
[exec] (Desktop-Laufwerks-Symbole) {eventmanager desktop}
[exec] (Desktop-Symbole) {lazy-icon_switcher}
[exec] (FlSynclient Touchpad ) {flsynclient}
[exec] (Fonts) {fontmanager}
[exec] (PupClockset) {PupClockset}
[end]
Example for code to add to the file /root/.fluxbox/menu.base:
Code: Select all
[separator]
[include] (/root/.fluxbox/menu.add)
[separator]
To have a pipe -let's say for some scripts in /mnt/sda1/my-scripts- one just would need to write a little script that reads the directory /mnt/sda1/my-scripts and would echo its input (output of reading) in a modified form like this:
Code: Select all
[exec] (Menu-Title-here) {Path-and-Script-here}
I'm using Menu Pipes heavily in my LazY Puppy builds, but almost used in Openbox, which uses real Menu Pipes, that are updated immediately when opening the Menu.
Currently I'm creating such feature for JWM in L.A.S.S.I.E., but statically like this one here, that needs to be updated manually. To have a static Menu Pipe to be updated manually is the way I do prefer now, since there is a lot of Scripts, RoxApps and PortableApps for Linux and Wine included in my external Application directories, so the real Openbox Menu Pipes do take sometimes 1 or 2 seconds to give access to the menu category.
Since the content of these directories doesn't change very often, it's not really needed to update those Menu Pipes each time when opening the Menu. That's why I prefer the "static-pipes" now.
However: atm I don't have any time to do any further work for Menu Pipes in Fluxpup, I decided to post this here. Maybe someone else is interested in this and might do some work for some scripts do make users able to create easily Menu Pipes for Fluxbox.
RSH