In the past we did not support jwm. Now after much input from a user (SamK iirc) we have support for jwm even as far as inclusion in the iso.
This was made to mirror the current setup up (at the time) of fluxbox and icewm.
I see the overwhelming desire to have an supported set of conflicts for openbox. This was started in the past by a few users. Now with version 14 the integration of a new supported desktop should be as easy as having a set of config made by a user of openbox. If one of the many openbox enthusiasts is willing to put in some effort into mirroring the configuration of jwm, icewm, and fluxbox to openbox in a clean manner I am willing to make a deb for this set of config the same as the currently supported window managers. This will probably not be included in the iso, however it will make installation of openbox to antix specs as easy as two checkmarks in the metapackage installer or apt-get install openbox desktop-defaults-openbox. With the deb of default configs built and therefor allowing easy installation, integration into the new alternative desktops menu, menu building script, and slim with rox- and space- options will be no trouble at all.
Therefor if someone knowledgeable with openbox is willing to put in 75% of the work in building a default set of configs I am willing to put together the last bit too call it supported. (though community wise not release wise)
-
Posts: 1,062
- Joined: 20 Jan 2010
-
Posts: 1,445
- Joined: 09 Feb 2012
#2
If you post a poll, expect fewer than a dozen will chime in and I doubt there will be a consensus as to pypanel vs fbpanel vs lxpanel vs tint2 vs...
Overwhelming desire?building a default set of configs
If you post a poll, expect fewer than a dozen will chime in and I doubt there will be a consensus as to pypanel vs fbpanel vs lxpanel vs tint2 vs...
-
Posts: 4,164
- Joined: 20 Feb 2009
#3
You are making me grin skidoo. Because of the crickets chirping when it comes to offering help
on configuring Openbox for AntiX.
I have not messed with LXDE or Open Box since
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.lxde.org/viewtopic.php?f=11&t=31202"
linktext was:"http://forum.lxde.org/viewtopic.php?f=11&t=31202"
====================================
Tint2 since
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://oi44.tinypic.com/nld6r8.jpg"
linktext was:"http://oi44.tinypic.com/nld6r8.jpg"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://i751.photobucket.com/albums/xx158/rokytnji/screeny/screenshot1-1.jpg"
linktext was:"http://i751.photobucket.com/albums/xx15 ... hot1-1.jpg"
====================================
Wbar and LXpanel
The above is on Fluxbox by the way.
and Semplice
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://i49.tinypic.com/33a8936.jpg"
linktext was:"http://i49.tinypic.com/33a8936.jpg"
====================================
Here is a old tint2rc I keep around
on configuring Openbox for AntiX.
I have not messed with LXDE or Open Box since
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.lxde.org/viewtopic.php?f=11&t=31202"
linktext was:"http://forum.lxde.org/viewtopic.php?f=11&t=31202"
====================================
Tint2 since
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://oi44.tinypic.com/nld6r8.jpg"
linktext was:"http://oi44.tinypic.com/nld6r8.jpg"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://i751.photobucket.com/albums/xx158/rokytnji/screeny/screenshot1-1.jpg"
linktext was:"http://i751.photobucket.com/albums/xx15 ... hot1-1.jpg"
====================================
Wbar and LXpanel
The above is on Fluxbox by the way.
and Semplice
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://i49.tinypic.com/33a8936.jpg"
linktext was:"http://i49.tinypic.com/33a8936.jpg"
====================================
Here is a old tint2rc I keep around
Code: Select all
.#---------------------------------------------
# TINT2 CONFIG FILE mouseover
#---------------------------------------------
#---------------------------------------------
# BACKGROUND AND BORDER
#---------------------------------------------
#1 panel background
rounded = 7
border_width = 1
#background_color = #002050 00
background_color = #000510 70
#background_color = #404040 20
border_color = #ffffff 18
#2 active window
rounded = 5
border_width = 1
background_color = #ffffff 18
border_color = #ffff00 100
#3 normal window
rounded = 5
border_width = 2
background_color = #ffffff 18
border_color = #ffffff 0
#4 urgent window
rounded = 5
border_width = 0
background_color = #ba5d00 100
border_color = #ffffff 50
#5 systray
rounded = 2
border_width = 0
background_color = #000000 0
border_color = #ffffff 40
#6 hovered window
rounded = 5
border_width = 1
background_color = #ffffff 18
border_color = #ffffff 100
#7 hovered active window
rounded = 5
border_width = 1
background_color = #ffffff 18
border_color = #aaaa55 100
#8 hovered urgent window
rounded = 5
border_width = 1
background_color = #ba5d00 100
border_color = #ffffff 100
#9 tooltip background
rounded = 7
border_width = 1
background_color = #000000 0
border_color = #ffffff 18
#---------------------------------------------
# PANEL
#---------------------------------------------
panel_items = CSTL
panel_monitor = all
panel_position = bottom left vertical
#panel_position = bottom right vertical
#panel_position = bottom right horizontal
panel_size = 100% 152
panel_margin = 0 0
panel_padding = 5 0
font_shadow = 0
panel_background_id = 1
wm_menu = 1
panel_dock = 0
strut_policy = follow_size
#strut_policy = none
panel_layer = top
#---------------------------------------------
# TASKBAR
#---------------------------------------------
taskbar_mode = multi_desktop
taskbar_padding = 2 3 2
taskbar_background_id = 0
taskbar_name = 1
taskbar_name_padding = 6 3
taskbar_name_font = Liberation Sans 8
taskbar_name_font_color = #ffffff 100
taskbar_name_active_font_color = #ffffff 100
taskbar_name_background_id = 0
taskbar_name_active_background_id = 0
#---------------------------------------------
# TASKS
#---------------------------------------------
task_icon = 1
task_text = 1
task_maximum_size = 140 35
task_centered = 1
task_padding = 6 3
task_font = Liberation Sans 8
task_font_color = #ffffff 100
task_background_id = 3
task_icon_asb = 100 0 0
# replace STATUS by 'urgent', 'active' or 'iconfied'
#task_STATUS_background_id = 2
#task_STATUS_font_color = #ffffff 85
#task_STATUS_icon_asb = 100 0 0
# example:
task_active_background_id = 2
task_urgent_background_id = 4
# use STATUShovered for mouseover effects
task_normalhovered_background_id = 6
task_activehovered_background_id = 7
task_urgenthovered_background_id = 8
urgent_nb_of_blink = 100000
#---------------------------------------------
# SYSTRAYBAR
#---------------------------------------------
systray = 1
systray_padding = 4 4 4
systray_background_id = 5
systray_sort = left2right
# maximum icon size
systray_icon_size = 28
systray_icon_asb = 100 0 0
#---------------------------------------------
# APPLICATION LAUNCHER
#---------------------------------------------
launcher_padding = 2 4 2
launcher_background_id = 5
# Icon size
launcher_icon_size = 32
# Each launcher_item_app must be a full path to a .desktop file
launcher_item_app = /usr/share/applications/iceape-mailnews.desktop
launcher_item_app = /usr/share/applications/iceape-navigator.desktop
launcher_item_app = /usr/share/applications/iron.desktop
launcher_item_app = /usr/share/applications/geany.desktop
launcher_item_app = /usr/share/applications/gimp.desktop
launcher_item_app = /usr/share/applications/vlc.desktop
launcher_item_app = /usr/share/applications/huludesktop.desktop
launcher_item_app = /usr/share/applications/gksu.desktop
launcher_item_app = /usr/share/applications/roxterm.desktop
launcher_item_app = /usr/share/applications/Thunar.desktop
launcher_item_app = /usr/share/applications/rox-filer.desktop
launcher_item_app = /usr/share/applications/qtfm.desktop
#---------------------------------------------
# CLOCK
#---------------------------------------------
time1_format = %H:%M
time1_font = sans bold 9
time2_format = %A %d %B
time2_font = Liberation Sans 8
clock_font_color = #ffffff 90
clock_padding = 1 0
clock_background_id = 0
clock_lclick_command = korganizer
clock_rclick_command = zenity --calendar --text""
clock_tooltip = %A %0d %B %Y %nWeek %W
#time1_timezone = :US/Hawaii
#time2_timezone = :Europe/Berlin
#clock_tooltip_timezone = :/usr/share/zoneinfo/Europe/Paris
#---------------------------------------------
# BATTERY
#---------------------------------------------
#battery = 0
#battery_hide = 80
#battery_low_status = 10
#battery_low_cmd = notify-send -u critical -t 1000000 -i battery-caution"Low battery""Level: 10%"
#bat1_font = sans 8
#bat2_font = sans 6
#battery_font_color = #ffaa00 100
#battery_padding = 1 0
#battery_background_id = 0
#---------------------------------------------
# TOOLTIP
#---------------------------------------------
tooltip = 1
tooltip_padding = 2 2
tooltip_show_timeout = 0.3
tooltip_hide_timeout = 0.1
tooltip_background_id = 9
tooltip_font_color = #ffffcc 100
tooltip_font = Sans 8
#---------------------------------------------
# MOUSE ACTION ON TASK
#---------------------------------------------
mouse_middle = none
mouse_right = close
mouse_scroll_up = toggle
mouse_scroll_down = iconify
#---------------------------------------------
# AUTOHIDE OPTIONS
#---------------------------------------------
autohide = 1
autohide_show_timeout = 0.1
autohide_hide_timeout = 0.1
autohide_height = 2
-
Posts: 1,062
- Joined: 20 Jan 2010
#4
Anyway I have seen / heard of openbox being mentioned as a pretty much constant. Overwhelming desire... maybe the wrong choice of words, but there has been enough people asking about it. So at this point it is not much to having openbox"antiXized" other than making the set of configs. Thus I am offering to do the final stuff if someone is willing to put in some leg work.
No panels in the config... after all as in rocky's posts you can add a panel to anything and everything. __{{emoticon}}__skidoo wrote:Overwhelming desire?building a default set of configs
If you post a poll, expect fewer than a dozen will chime in and I doubt there will be a consensus as to pypanel vs fbpanel vs lxpanel vs tint2 vs...
Anyway I have seen / heard of openbox being mentioned as a pretty much constant. Overwhelming desire... maybe the wrong choice of words, but there has been enough people asking about it. So at this point it is not much to having openbox"antiXized" other than making the set of configs. Thus I am offering to do the final stuff if someone is willing to put in some leg work.
-
Posts: 604
- Joined: 27 Feb 2009
#5
I would offer, but am probably not capable of doing it well enough, to be honest. I don't know anything about coding under linux, not even the scripts, so every line of code is a learning experience.
I learned quite a bit about Openbox when messing with Manjaro OpenRC Openbox and Crunchbang tweaking them for my old P III m, but that's not working for antiX 14r3.x, so I'd need to setup a different sacrificial machine. I like testing on the old one because I really can find the bottlenecks, and then when I put the code on my faster machines it really screams.
The obvious person to do it that has done it in the past week must not have the desire I suppose.
BTW, I did get it working with an auto-generated at login static menu (very fast) and a tint2 panel, with what looks and acts likea a"normal" start button for the menus as well as the right click menu popup method. I'll see if I can find a screenshot of it.
PS: I don't understand"themes", so many of my icons on the menus don't work.
I learned quite a bit about Openbox when messing with Manjaro OpenRC Openbox and Crunchbang tweaking them for my old P III m, but that's not working for antiX 14r3.x, so I'd need to setup a different sacrificial machine. I like testing on the old one because I really can find the bottlenecks, and then when I put the code on my faster machines it really screams.
The obvious person to do it that has done it in the past week must not have the desire I suppose.
BTW, I did get it working with an auto-generated at login static menu (very fast) and a tint2 panel, with what looks and acts likea a"normal" start button for the menus as well as the right click menu popup method. I'll see if I can find a screenshot of it.
PS: I don't understand"themes", so many of my icons on the menus don't work.
-
Posts: 1,062
- Joined: 20 Jan 2010
#6
OK based on a PM and in an attempt to solve problems expressed in another thread I am trying to be more verbose about what is going on.
The requirements in more detail would be. (based on mirror of fluxbox because it is a *box)
- main menu structured in the same manner as the main menu of fluxbox on V14 of antix
- Config files split into sub catagories (refer to ~/.fluxbox/ with menu -> menu-applications -> personal, keys, startup, etc)
- Panel I do not think that a panel should be included as part of the window manager, but I will leave this up to the one who decides to take the project on
- in ls /usr/share/desktop-menu/templates/ there are menu templates for icewm / jwm / fluxbox... it is not neccessary for the maker of the configs to make an openbox.template, but needs to be done... so if they so wish to give it a try it will allow for the auto building of applications and personal menus __{{emoticon}}__
- Make a theme matching the same styling as what is used in the other window managers.
- The wallpaper app should work, however after running and selecting the wallpaper copy ~/.desktop-session/wallpaper-list.conf in with the configs (it will contain the lines to remember the wallpaper) needs to be done for (Rox-openbox, Space-openbox, openbox) On that note there may not be recognition for this. If it does not automatically add these to the alternative desktops menu or slim please let me know and I will fix it.
The requirements in more detail would be. (based on mirror of fluxbox because it is a *box)
- main menu structured in the same manner as the main menu of fluxbox on V14 of antix
- Config files split into sub catagories (refer to ~/.fluxbox/ with menu -> menu-applications -> personal, keys, startup, etc)
- Panel I do not think that a panel should be included as part of the window manager, but I will leave this up to the one who decides to take the project on
- in ls /usr/share/desktop-menu/templates/ there are menu templates for icewm / jwm / fluxbox... it is not neccessary for the maker of the configs to make an openbox.template, but needs to be done... so if they so wish to give it a try it will allow for the auto building of applications and personal menus __{{emoticon}}__
- Make a theme matching the same styling as what is used in the other window managers.
- The wallpaper app should work, however after running and selecting the wallpaper copy ~/.desktop-session/wallpaper-list.conf in with the configs (it will contain the lines to remember the wallpaper) needs to be done for (Rox-openbox, Space-openbox, openbox) On that note there may not be recognition for this. If it does not automatically add these to the alternative desktops menu or slim please let me know and I will fix it.
-
Posts: 604
- Joined: 27 Feb 2009
#7
-config - agree
-panel - no, just add tint2. the repo version is the svn so its easy. do you want an antiX start button? or no start button? openbox people may or may not want a start button, i dunno. i know how to do a start button with tint2
-menu - will have to look. didn't know where to look before. it has a menu but needs antix stuff. i know how to do it by hand or can figure out any generator
-theme - lol, it has one. it doesn't look bad, but i'm not a"glitzy" person. I can set it up with nitrogen and an antiX background like the others?
-wallpaper - i've never messed with that, will need to look
-it gets added to slim, but its just openbox with no space or rox possibilities. i would add the on/off stuff for rox pinboard etc for sure and put space on the main menu. that might be good enough? i don't know how/where to add to slim.
-male suggests obmenu... its a gui to edit the main menu. do you want it or not? i can test it if you do. it wasnt good enough when i tried it with manjaro, but might not be same version. if it actually works right i'm ok with including it, but if not, then i wouldn't. main menu should be redone regardless, IMO.
i installed openbox, openbox-menu, obconf, and tint2 onto the 14.3 alpha RV killah 32 bit on an HP DV9700 laptop w/nVidia 7150m 1440x900 and 2 fast 500gb drives and 3gb mem, and its running.Dave wrote:OK based on a PM and in an attempt to solve problems expressed in another thread I am trying to be more verbose about what is going on.
The requirements in more detail would be. (based on mirror of fluxbox because it is a *box)
- main menu structured in the same manner as the main menu of fluxbox on V14 of antix
- Config files split into sub catagories (refer to ~/.fluxbox/ with menu -> menu-applications -> personal, keys, startup, etc)
- Panel I do not think that a panel should be included as part of the window manager, but I will leave this up to the one who decides to take the project on
- in ls /usr/share/desktop-menu/templates/ there are menu templates for icewm / jwm / fluxbox... it is not neccessary for the maker of the configs to make an openbox.template, but needs to be done... so if they so wish to give it a try it will allow for the auto building of applications and personal menus __{{emoticon}}__
- Make a theme matching the same styling as what is used in the other window managers.
- The wallpaper app should work, however after running and selecting the wallpaper copy ~/.desktop-session/wallpaper-list.conf in with the configs (it will contain the lines to remember the wallpaper) needs to be done for (Rox-openbox, Space-openbox, openbox) On that note there may not be recognition for this. If it does not automatically add these to the alternative desktops menu or slim please let me know and I will fix it.
-config - agree
-panel - no, just add tint2. the repo version is the svn so its easy. do you want an antiX start button? or no start button? openbox people may or may not want a start button, i dunno. i know how to do a start button with tint2
-menu - will have to look. didn't know where to look before. it has a menu but needs antix stuff. i know how to do it by hand or can figure out any generator
-theme - lol, it has one. it doesn't look bad, but i'm not a"glitzy" person. I can set it up with nitrogen and an antiX background like the others?
-wallpaper - i've never messed with that, will need to look
-it gets added to slim, but its just openbox with no space or rox possibilities. i would add the on/off stuff for rox pinboard etc for sure and put space on the main menu. that might be good enough? i don't know how/where to add to slim.
-male suggests obmenu... its a gui to edit the main menu. do you want it or not? i can test it if you do. it wasnt good enough when i tried it with manjaro, but might not be same version. if it actually works right i'm ok with including it, but if not, then i wouldn't. main menu should be redone regardless, IMO.
-
Posts: 604
- Joined: 27 Feb 2009
#8
I did some experimenting this morning...
I would be a lot better off patterning it off the antiX IceWM setup because I understand at least how it works, maybe not how it gets setup, but at least how it works. I don't understand how Fluxbox works, and I don't want to spend much time trying to learn that. I do understand how Openbox works and have converted a system from Openbox to IceWM before based on antiX's IceWM setup, so it makes sense that I can also do the reverse. That would simplify it a lot for me.
The other thing is that Openbox uses ~/.config/openbox as its default directory, and because I don't know where that gets decided, it would be easiest to use that same location to create and store and maintain a per user top level menu and resource file, in a similar manner as other distro's store it.
Also, I see there is a wallpaper.py to set the background image ... nevermind, figured that out, but wait? When I installed Openbox, I lost the wallpaper. I can see that I can out it back with wallpaper.py, but it would be better if it wouldn't get lost when the Openbox is installed.
I would be a lot better off patterning it off the antiX IceWM setup because I understand at least how it works, maybe not how it gets setup, but at least how it works. I don't understand how Fluxbox works, and I don't want to spend much time trying to learn that. I do understand how Openbox works and have converted a system from Openbox to IceWM before based on antiX's IceWM setup, so it makes sense that I can also do the reverse. That would simplify it a lot for me.
The other thing is that Openbox uses ~/.config/openbox as its default directory, and because I don't know where that gets decided, it would be easiest to use that same location to create and store and maintain a per user top level menu and resource file, in a similar manner as other distro's store it.
Also, I see there is a wallpaper.py to set the background image ... nevermind, figured that out, but wait? When I installed Openbox, I lost the wallpaper. I can see that I can out it back with wallpaper.py, but it would be better if it wouldn't get lost when the Openbox is installed.
-
Posts: 1,062
- Joined: 20 Jan 2010
#9
Basing on icewm is fine as they are essentially based on each other. The wallpaper should be lost the first time but not with successive logins into openbox.
-
Posts: 604
- Joined: 27 Feb 2009
#10
BTW, my opinion on the space or rox or neither thing is just to default to neither and let them turn on the rox pinboard via the menu if desired. I wonder if a similar command could control the space icons on the desktop? Then your current openbox option on slim is fine, IMO, and simplifies things.
I will try to set up my test system and get all the menus working and tested. I will be using tint2 and will give it an antiX start button unless you say otherwise. I prefer it that way myself.
When I add a package, at the end it does:
What program is it running? I would think it should update the Openbox menu, too? My plan would be to use the Debian applications menu as is and just see that it gets updated? Maybe it already is being done automatically? I will change the name on the main menu from"Debian" to"All Applications" or maybe"User Applications" unless you prefer something else... It really represents a subset of .desktop files in /usr/share/applications I think.
I will try to set up my test system and get all the menus working and tested. I will be using tint2 and will give it an antiX start button unless you say otherwise. I prefer it that way myself.
When I add a package, at the end it does:
Code: Select all
Processing triggers for menu (2.1.47) ...
Updating fluxbox menu
Updating icewm menu
Updating jwm menu
-
Posts: 1,062
- Joined: 20 Jan 2010
#11
If you make the template file in usr / share / desktop-menu /templates. Named openbox.template and get the template file right it will automatically make the menu after apt - get for you the same as icewm,flubox,and jwm.
Sorry for the short replies I am not at the computer at the moment and answering on my phone
Sorry for the short replies I am not at the computer at the moment and answering on my phone
-
Posts: 604
- Joined: 27 Feb 2009
#12
Ok, I'll look there, thanks
-
Posts: 604
- Joined: 27 Feb 2009
#13
PS: you can skip this message if my change to desktop-menu is implemented, essentially providing the first option suggested below. I didn't expect to be able to modify it, but managed to do it blindly, LOL. Hopefully the other window manager menus are unaffected.
-------------------------
Ok, I got a menu template to almost work. The problem is that openbox requires a unique menu id for each menu and also requires a label for the menu whch will be displayed, but the template program is only allowed to have a name and an icon for each menu. if the menu has no label, it doesn't display at all. if i hard code the menu id, all menu lines get the same description and submenus, and so the only way I could do it was by hard coding the menu id's and then manually just giving each an incrementing counter at the end of the string to make them unique.
1. One solution would be to change the template program when generating for openbox to output a 3rd field, ie output a label field with the same value as the menu name.
2. A 2nd solution would be to do some fancy awk stuff to do the counter thing I did by hand automatically
3. A 3rd solution, and I feel the best would be to use the"debian" menu it generates if the openbox template is missing and just not call it"Debian". Its a shame I spent all that time to get the template right only to find it can't give me the 3rd field and I don't know the language to change the code, and therefore fear I might break the other menus while implementing the openbox one.
-------------------------
Ok, I got a menu template to almost work. The problem is that openbox requires a unique menu id for each menu and also requires a label for the menu whch will be displayed, but the template program is only allowed to have a name and an icon for each menu. if the menu has no label, it doesn't display at all. if i hard code the menu id, all menu lines get the same description and submenus, and so the only way I could do it was by hard coding the menu id's and then manually just giving each an incrementing counter at the end of the string to make them unique.
1. One solution would be to change the template program when generating for openbox to output a 3rd field, ie output a label field with the same value as the menu name.
2. A 2nd solution would be to do some fancy awk stuff to do the counter thing I did by hand automatically
3. A 3rd solution, and I feel the best would be to use the"debian" menu it generates if the openbox template is missing and just not call it"Debian". Its a shame I spent all that time to get the template right only to find it can't give me the 3rd field and I don't know the language to change the code, and therefore fear I might break the other menus while implementing the openbox one.
Last edited by thriftee on 15 Dec 2014, 19:56, edited 1 time in total.
-
Posts: 604
- Joined: 27 Feb 2009
#14
Ok, I don't know the python language at all, and its quite weird to me, but anyway, I managed to change /usr/local/bin/desktop-menu to have an"execute" field for the menu itself when the menu being generated is for openbox, and initialized its value the same as the"name" field. For some odd reason, I got the output, but with the fields in the reverse order expected, and it didn't make sense, but to solve it, I reversed the order on the template, and it generates good menus now.
I don't see how that menu is supposed to get to ~/.config/openbox directory, so will change the rc.xml to hard code go look for the file as /usr/share/desktop-menu/.openbox/menu-applications.xml where the generator is putting it automatically. That essentially means you can't have"per user" menus, as openbox is designed for, but I doubt anyone cares, because the templates and app installs are global anyway.
The actual menu on the screen will not change till openbox is told to reconfigure or restart, which are both menu options, or if one was to logout and back in, thus shutting down and restarting openbox.
Should I post the files here? or where?
I am now working on tint2, and one thing I don't like is that I got tray icons for volume and wifi, but I don't know where those programs were called from?
I don't see how that menu is supposed to get to ~/.config/openbox directory, so will change the rc.xml to hard code go look for the file as /usr/share/desktop-menu/.openbox/menu-applications.xml where the generator is putting it automatically. That essentially means you can't have"per user" menus, as openbox is designed for, but I doubt anyone cares, because the templates and app installs are global anyway.
The actual menu on the screen will not change till openbox is told to reconfigure or restart, which are both menu options, or if one was to logout and back in, thus shutting down and restarting openbox.
Should I post the files here? or where?
I am now working on tint2, and one thing I don't like is that I got tray icons for volume and wifi, but I don't know where those programs were called from?
-
Posts: 1,062
- Joined: 20 Jan 2010
#15
Great job on the menu program! I was actually going to send you a message asking for your progress so I could see what you meant by the extra items. Yes changing the order in the template is how you change the order that the program makes the list. Unless you changed the main items around rather than the substitute order option. Glad you figured it out! I was hoping to make it easier to add other window managers to the script with the templates. Would you have any suggestions for improvement in the area?
Likely you have enabled xdg autostart in / etc / desktop - session / desktop - session.conf. If not than my guess would be that xdg is enabled in openbox. That should account for the wifi app starting. As to the volume icon, likely that is started in the session as well in / etc / desktop - session /startup.
Likely you have enabled xdg autostart in / etc / desktop - session / desktop - session.conf. If not than my guess would be that xdg is enabled in openbox. That should account for the wifi app starting. As to the volume icon, likely that is started in the session as well in / etc / desktop - session /startup.