23 Jan
2011
23 Jan
'11
2:37 a.m.
Hi,
I'm wondering if there exists any scripts for generating menus for
audio users such as ourselves :-)
Of course though this question enters my mind after I set out to write
my own BASH (4) script.
To begin with my script will generate a menu for Fluxbox.
The file ~/fluxbox/init should be edited to specify ~/.fluxbox/my-menu
as the session.menuFile.
The script will generate a basic my-menu consisting of items such as
xterm, firefox, audio sub-menu, htop, nedit, alsamixer, system sub
menu, and logout and shutdown.
The audio sub menu is a separate file ~/.fluxbox/my-audio-menu
generated by searching a list of audio applications and adds those
found on the system running the script. Other sub menus should easily
be added (but are hard coded for now).
The system sub-menu is a separate file ~/.fluxbox/menu and is
generated by (currently) mmaker if it exists, or fluxbox-generate_menu
as a fallback.
The list of audio applications currently only covers those I use^d^d^d
intend to use^d^d^d^d^d^d^d have installed/compiled with the intention
of using.
I'd imagine there should already be a script out there to do this
which possibly works with a number of WMs/DEs?
But, I also imagine it would be quite difficult to make it work easily
with all. I think *box and xfce should be manageable.
Any opinions/thoughts/suggestions/etc?
Cheers,
James.
--
_
: http://jwm-art.net/
-audio/image/text/code/
23 Jan
23 Jan
3:43 a.m.
i've uploaded the first version of the script here (temporarily):
http://jwm-art.net/code/lau_flux_menu
i will create a proper online home for the code later.
be warned: it will clobber your existing fluxbox menus.
i forgot to mention that it creates a bristol submenu for all the
different bristol emulation modes.
it's easy to make this script recognise applications it is currently
missing. let me know them if you will.
cheers,
james.
On 23 January 2011 01:36, James Morris <jwm.art.net(a)gmail.com> wrote:
Hi,
I'm wondering if there exists any scripts for generating menus for
audio users such as ourselves :-)
Of course though this question enters my mind after I set out to write
my own BASH (4) script.
To begin with my script will generate a menu for Fluxbox.
The file ~/fluxbox/init should be edited to specify ~/.fluxbox/my-menu
as the session.menuFile.
The script will generate a basic my-menu consisting of items such as
xterm, firefox, audio sub-menu, htop, nedit, alsamixer, system sub
menu, and logout and shutdown.
The audio sub menu is a separate file ~/.fluxbox/my-audio-menu
generated by searching a list of audio applications and adds those
found on the system running the script. Other sub menus should easily
be added (but are hard coded for now).
The system sub-menu is a separate file ~/.fluxbox/menu and is
generated by (currently) mmaker if it exists, or fluxbox-generate_menu
as a fallback.
The list of audio applications currently only covers those I use^d^d^d
intend to use^d^d^d^d^d^d^d have installed/compiled with the intention
of using.
I'd imagine there should already be a script out there to do this
which possibly works with a number of WMs/DEs?
But, I also imagine it would be quite difficult to make it work easily
with all. I think *box and xfce should be manageable.
Any opinions/thoughts/suggestions/etc?
Cheers,
James.
--
_
: http://jwm-art.net/
-audio/image/text/code/
--
_
: http://jwm-art.net/
-audio/image/text/code/
3:56 a.m.
Am Sonntag, den 23.01.2011, 01:36 +0000 schrieb James Morris:
I'm wondering if there exists any scripts for
generating menus for
audio users such as ourselves :-)
there is a discussion in debian, suggested by rosea.grammostola I think,
http://wiki.debian.org/DebianMultimedia/DebianMultimediaMenu
the problem with self generated menus is, that every time when you run
update-menu (by installing a new package in debian for example), the
system will overwrite your settings, so a more general solution will be
more helpful. I hope they coming forward.
greats hermann
11:02 a.m.
On 23 January 2011 02:56, hermann <brummer-(a)web.de> wrote:
Am Sonntag, den 23.01.2011, 01:36 +0000 schrieb James
Morris:
I agree with the view that the very long menu lacks usability (and
cohesion). I don't like the idea of that many sub menus within the
sound+video sub menu (i'd rather bring the audio menu up to the
top-level).
I have dispensed with the idea of multi-media so that audio and video
are separate (but then I'm biased toward audio/midi).
Perhaps the most popular apps could be migrated to the top level menu
(like I have done with xterm, firefox, nedit, htop, alsamixer). The 5
(max?) most popular audio apps could be under the "Audio" sub-heading
(the 5 would/should be easily customizable by the user of the script).
Then, instead of a single audio sub menu, we have 2 or 3 audio
sub-menus. Loose categorizations such as controllers (ie sequencers)
the controlled (ie synths/samplers/fx) and editors (ie snd,
audacity,etc).
I'm wondering if there exists any scripts for
generating menus for
audio users such as ourselves :-)
there is a discussion in debian, suggested by rosea.grammostola I think,
http://wiki.debian.org/DebianMultimedia/DebianMultimediaMenu the problem with self generated menus is, that every
time when you run
update-menu (by installing a new package in debian for example), the
system will overwrite your settings, so a more general solution will be
more helpful. I hope they coming forward.
The idea with this script is that it allows some level of
customizability by encouraging the user to edit the actual script.
hopefully most of the things to be edited will just/eventually be
along the lines of:
variable="something"
greats hermann
11:25 p.m.
After some more work all menus are specified as BASH arrays within the script.
Here's the new version which also recognizes many more applications:
http://jwm-art.net/code/lau_flux_menu_0.0.1
Here's the obligatory screenshot:
http://jwm-art.net/code/lau_flux_menu_0.0.1.png
Here's the listing format for a menu:
MENU_ARRAY=(
"command1, name"
"--"
"+submenu_file, name"
"!fluxbox_command, name"
)
# notes:
# **** "--" creates a menu separator.
# **** the command should not be specified with path.
# **** whitespace must not be placed between command and comma.
# **** whitespace after the comma is removed.
# **** the * character must not be used.
# **** () in the name will be replaced with {} as
fluxbox can't handle ().
The menu generation is now a function which is called with four
parameters, like so:
create_menu "My Menu" ~/.fluxbox/my-menu-file MENU_ARRAY[@]
Which basically means all the menus generated by the script are easily
customizable so that my choices don't have to be your choices.
The script uses the 'which' command to figure out both if the command
exists on the system and the full path for the command.
The worst bug I know of it has is that while it can handle commands such as:
xterm -e alsamixer
jaaa -J
it cannot handle:
xterm -e sudo halt
Usage of xterm is hard coded at present. If the command begins with
"xterm -e" it performs the which command on the command after.
Cheers,
James.
--
_
: http://jwm-art.net/
-audio/image/text/code/
5057
days inactive
5057
days old
linux-audio-user@lists.linuxaudio.org
4 comments
2 participants
participants (2)
-
hermann -
James Morris