roberts
Group: Members
Posts: 4983
Joined: Oct. 2003 |
 |
Posted: Nov. 08 2007,16:28 |
 |
I am supporting it all under /opt. This way it supports legacy mode.
You are correct to assume a common single simple name of the scripts that code in the core DSL will look for and process.
/opt/.mydsl_menu/jwm/ directory contains:
make - the code to make the mydsl menu include
restart - the code needed to restart/refresh to make the menu updates visible
menu_template - the "empty" or starting menu usually has a placeholder used as the target of insertion for the make script.
I did not use any extension (.lua, .sh, .pl) on the script names so that you can write your scripts in any supported language.
To remain backward compatible the default remains fluxbox menu specifications.
/opt/.mydsl_menu/fluxbox directory contains the same three named files but with content specific to fluxbox.
This way a .tar.gz (legacy able) extension can write to /opt/.mydsl_menu and the dynamic mydsl menu creation, update, and cleanup will all work.
For the main system menu ((static)) I am now using a bash include
to there is a fluxbox.inc and a jwm.inc. This include file is the code snippet that would have been needed inside the .xinitrc case statement.
Edited by roberts on Nov. 08 2007,16:33
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
