[OBSOLETE] The bunsenlabs 'exit' menu entry

damo · 2016-07-26 18:32:43

@xaos52

Did you have a look at my suggestion for dealing with multiple monitors, using Under Mouse instead of Active Window? I believe your version needs an <applications> setting in rc.xml, if the screens have different resolutions - that is my experience anyway.
Comment on commit 9b7aea....989c

EDIT: Also, is it better to use a "defaultColour" variable, instead of hard-coding "#222222" many times?

Last edited by damo (2016-07-26 19:25:21)

damo · 2016-07-26 19:23:01

hhh wrote:

More feedback...
The panel icon is generic, what happened to the lovely Exit (red X) Faenza icon that I bugfixed?
I see a flash of a standard window when I Enter/click a button action. A yad window?
Running bl-exit (merlin) while editing the config can crash stuff, maybe?
Make button:hover bg-color editable, I think it relies on GTK ATM. The theme options "Active, Normal, Prelight" don't all work the way things are.

I'd like to see bl-exit(merlin) use the icontheme icons as default, as well as being able to use the bl-exit dark/light icons as a user option;

It would be good if the gtk theme settings could be read for the panel/button colours;

I've tried editing and saving bl-exitrc while the exit dialog is open - no crashes yet ;

bl-exit (BL and merlin) uses gtk for the window (not yad), which runs if there is no bl-exitrc. Maybe it flashes on when the new panel exits? Bug? I'm not seeing this behaviour BTW.

hhh · 2016-07-26 23:28:08

Thanks, I'll keep testing when I can. A lot on my plate ATM. Especially bloody life, the bleedin'jerk. Bloody hell, life can be a bitch sometimes.

What is it with life, that as soon as you settle one crisis another one screams at you in no time at all? So hard not to stress, I couldn't concentrate at all today. Just keep swimming, I guess.

xaos52 · 2016-07-27 12:43:12

hhh wrote:

The panel icon is generic, what happened to the lovely Exit (red X) Faenza icon that I bugfixed? wink

Restored the lovely red icon.
It got lost by introducing the merlin window.

hhh wrote:

I see a flash of a standard window when I Enter/click a button action. A yad window?

Nope. I don't see this.
yad is not even mentioned in the script.

hhh wrote:

Running bl-exit (merlin) while editing the config can crash stuff, maybe?

I am not using a lock on the config file, so there might be a very short time slot where you are writing your changes to disk that the config file is in an inconsistent state while bl-exit is reading it.
This should occur very rarely. If not, there must be some other problem. Let me know if you can reproduce.

xaos52 · 2016-07-29 11:55:05

Pushed a new version to the merlin branch:

Added a custom gtk rc file, which allows to set any combination of colors for the buttons, overriding the theme settings. Very powerfull.
Example file is in styles/light.rc

Added section [style] to bl-exitrc, which allows to specify directory and filename of the style rc file, relative to the bl-exit config dir.

Removed the corresponding options from bl-exitrc.

Please play with it, and let me know if something does not work as expected.

Better examples of style rc files are welcome.

@damo: I am still looking around for a better solution for a multi-screen setup.

EDIT:
The custom config settings also work for the original button layout (no theme specified in bl-exitrc)

maestrobwh1 · 2016-08-01 21:19:49

Exit menu entry:

Q1- I do use this. I have power-manager set up to hibernate the machine after x amount of time, and I also have the sleep button tied to "hibernate;" however, that being said, it is available in other 'nix distributions and a lot of people either A) want to save their session but not want the power drain that still happens with sleep or B) still use a regular hard disk were loading seems a bit faster when restoring from hibernate. I do have an SSD, and against conventional wisdom, writing a full memory to a swap partition does not overtly wear out the SSD.
Q2- It should be there and grayed out with some documentation as to what needs to be done to enable it if a proper swap space was not set up during the install. I still had to add resume=uuid="disk uuid" to my /etc/default/grub even though I set up swap to be slightly larger than my RAM. I also installed pm-utils so that this functionality was a bit more fluid.

xaos52 · 2016-08-03 10:22:26

Inspired by hhh's Bunsen-Orange:

xaos52 · 2016-08-13 10:22:32

I may have a - python - solution for the multi-monitor problem.
The newest version places the bl-exit window on the monitor where the cursor is - with correct width and independent of openbox policy.

Does not need a 'primary' monitor set.

Needs testing with different combinations of xrandr settings and openbox policy placement.

xaos52 · 2016-08-17 09:43:33

New version in repo.

With more example bl-exit/styles rc-files.

johnraff · 2016-08-19 07:25:17

Now trying 2.2.0 (script only) I get the standard BL window along with messages about missing configs.

Looking at the merlin repo it's clear there are a lot of other files, in the directories "dark", "light" and "styles", along with bl-exitrc. At present there is no information on where they are to be installed, so we're not ready for a merge yet. debian/install will need to be edited, at least.

Anyway, to test, I put those three dirs and bl-exitrc into ~/.config/bl-exit/
Sorry to report it still seems to be missing something. With that config I get a dialogue box with four buttons, but no captions or tooltips so I don't know what the buttons do. To "cancel" I have to press Esc.

Minor detail: the box fills the screen completely, right up to the edges. I would personally prefer a couple of pixels space on each side - is that configurable?

Anyway, screenshot:

Last edited by johnraff (2016-08-20 03:40:15)

xaos52 · 2016-08-19 07:57:21

No tooltips implemented.
The images should be self-explanatory.
Tooltips may be interesting at first, but will annoy soon after IMO.

Detailed config info is present as comments in bl-exitrc.

I was going to edit debian/install for the deuterium merge.

Window margins are not configurable for the moment, but it should be easy to add.

I would be interested in seeing the 'missing config' messages you mentioned.

johnraff · 2016-08-19 08:39:12

xaos52 wrote:

The images should be self-explanatory.

Not to me, sorry.
Anyway, there was nothing that looked like a "cancel" button, and both the far left and far right buttons looked like "shutdown" to me.

Tooltips may be interesting at first, but will annoy soon after IMO.

Quite possibly, but I think the default setup should be informative, leaving the user to remove the annoying extras later. Either tooltips or captions, no?

Detailed config info is present as comments in bl-exitrc.

Maybe, but there is still a need to optimize the default settings IMO. The average user should be able to get a reasonably useful interface out of the box, without having to configure anything.

EDIT: Maybe anyway make the "cancel" button visible by default?

I would be interested in seeing the 'missing config' messages you mentioned.

Here:

john@bunsen1:~$ bl-exit
Loading theme 'Dark Theme' by MerlinElMago
DEBUG bl-exit custom style rc file does not exist
DEBUG bl-exit config section default not present
DEBUG bl-exit config section cancel show=0
DEBUG bl-exit config section cancel onerror=0
DEBUG bl-exit config section default not present
DEBUG bl-exit config section logout show=1
DEBUG bl-exit config section logout onerror=0
DEBUG bl-exit config section default not present
DEBUG bl-exit config section suspend show=1
DEBUG bl-exit config section suspend onerror=0
DEBUG bl-exit config section default not present
DEBUG bl-exit config section hibernate show=0
DEBUG bl-exit config section hibernate onerror=0
DEBUG bl-exit config section default not present
DEBUG bl-exit config section hybridsleep show=0
DEBUG bl-exit config section hybridsleep onerror=0
DEBUG bl-exit config section default not present
DEBUG bl-exit config section reboot show=1
DEBUG bl-exit config section reboot onerror=0
DEBUG bl-exit config section default not present
DEBUG bl-exit config section poweroff show=1
DEBUG bl-exit config section poweroff onerror=0

EDIT2:

bl-exitrc wrote:

NB The "dark" directory contains light icons for a dark theme, and vice versa.

Agreed, that's how it should be, but now it's the other way round.

Last edited by johnraff (2016-08-19 08:48:43)

xaos52 · 2016-08-19 09:00:47

The 'error messages' are just debugging messages for parsing the bl-exitrc file which are still active - should be deactivated in deuterium.

OK. I will work on your suggestions.
Making everything configurable remains my motto, but more intuitive default settings will be coming your way.

johnraff · 2016-08-19 09:06:09

A couple more things...

*) The "minimal" theme setting in bl-exitrc does not work:

john@bunsen1:~$ bl-exit
Traceback (most recent call last):
  File "/home/john/bin/bl-exit", line 712, in <module>
    sys.exit(main())
  File "/home/john/bin/bl-exit", line 709, in main
    return blexit.main()
  File "/home/john/bin/bl-exit", line 571, in main
    self.configure()
  File "/home/john/bin/bl-exit", line 494, in configure
    self.configured_theme.set_details_from_config(self.cp, default_theme)
  File "/home/john/bin/bl-exit", line 455, in set_details_from_config
    config_value = cp.get(self.theme, key)
  File "/usr/lib/python2.7/ConfigParser.py", line 330, in get
    raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'minimal'

*) For some reason, the "dark.rc" style gives very little colour change when hovering the cursor, or selecting with the keyboard. The others are all OK in this respect.

*) "blue.rc" gives a bright red box!

johnraff · 2016-08-19 09:17:57

Sorry, yet another request: by renaming ~/config/bl-exit/bl-exitrc it's possible to go back to the current BunsenLabs exit box, ie small, centred. Is it possible to add an option in bl-exitrc to get that result, for people who prefer the "classic" look? Renaming or deleting bl-exitrc is a bit inelegant.

xaos52 · 2016-08-19 09:21:39

Should be Minimal with capital M

*' s are configurable.

Will rename 'blue.rc' to 'darkred.rc'

Sorry, yet another request: by renaming ~/config/bl-exit/bl-exitrc it's possible to go back to the current BunsenLabs exit box, ie small, centred. Is it possible to add an option in bl-exitrc to get that result, for people who prefer the "classic" look? Renaming or deleting bl-exitrc is a bit inelegant.

Commenting out the 'style' section in bl-exitrc reverts to the 'classical' look.

Will add this o the bl-exitrc comments.

EDIT:
No need to apologize.
Keep the remarks coming...

Last edited by xaos52 (2016-08-19 09:30:41)

johnraff · 2016-08-19 09:53:13

xaos52 wrote:

Should be Minimal with capital M

The other theme names are lowercase.

*' s are configurable.

What does this mean?

Will rename 'blue.rc' to 'darkred.rc'

There's already a darkred.rc which is... dark red.
blue.rc is bright red. (and a blue style might be nice...)

Commenting out the 'style' section in bl-exitrc reverts to the 'classical' look.

This didn't work for me. You mean this section?

[style]
dir = styles
rcfile = None

Any chance of enabling something like this?

[theme]
# set the theme
theme = classic

----
Packaging question:
Where should the image files be installed? I find they don't work in /etc/bl-exit (and I'm not sure if /etc is appropriate for images anyway).

They work in the user's personal config dir, but I don't think that's a satisfactory default location, for various reasons.
I looked in bl-exit unsuccessfully for a hint as to the paths searched for "icondir". Maybe something like /usr/share/images/bunsen/exit for the default icons, with the user's directory also checked for alternatives to those?

EDIT: OK I've found that bl-exit looks in the directory holding the active bl-exitrc file, so with no user config they work in /etc/bl-exit, but with a user bl-exitrc the icon directories must be copied into ~/.config/bl-exit too. I still think it would be cleaner to have /usr/share/images/bunsen/exit checked first, followed by the config file dir (as now) if the style directory isn't found.

Last edited by johnraff (2016-08-19 10:17:33)

xaos52 · 2016-08-19 10:12:53

The other theme names are lowercase. tongue

Euuh, no...
There are 'Dark Theme' and 'Light Theme'
Blame Damo for this.
He started using 'BunsenDark' and 'BunsenLight' - which have been removed since then - and I followed suit.

Comment out the entire '[theme]' section to revert to 'classical'

What does this mean?

The items you marked with '*' are configurable.

Any chance of enabling something like this?
[theme]
# set the theme
theme = classic

Yes.

I am looking for images in the directory where I found 'bl-exitrc'.
I can change that to adopt your proposed schema.

I plan to start working on all this from next monday onward.
So if you have more requests, please go ahead.

Last edited by xaos52 (2016-08-19 10:20:26)

Sector11 · 2016-08-19 16:32:13

xaos52 wrote:

No tooltips implemented.
The images should be self-explanatory.

There are only four, shouldn't there be five?

The only one I can honestly say I get at this point is Hybernate/Suspend:

[¿LogOut?] [Hybernate/Suspend] [¿Reboot?] [¿Power Off?]

What about [Cancel] ?

Maybe something like this for Cancel.

damo · 2016-08-19 20:21:09

Sector11 wrote:

....
Maybe something like this for Cancel.

There is already a Cancel option, but it needs to be enabled in the config file. I would prefer to see it enabled default.

#161 2016-07-26 18:32:43

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#162 2016-07-26 19:23:01

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#163 2016-07-26 23:28:08

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#164 2016-07-27 12:43:12

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#165 2016-07-29 11:55:05

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#166 2016-08-01 21:19:49

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#167 2016-08-03 10:22:26

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#168 2016-08-13 10:22:32

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#169 2016-08-17 09:43:33

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#170 2016-08-19 07:25:17

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#171 2016-08-19 07:57:21

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#172 2016-08-19 08:39:12

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#173 2016-08-19 09:00:47

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#174 2016-08-19 09:06:09

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#175 2016-08-19 09:17:57

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#176 2016-08-19 09:21:39

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#177 2016-08-19 09:53:13

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#178 2016-08-19 10:12:53

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#179 2016-08-19 16:32:13

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#180 2016-08-19 20:21:09

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

Board footer