[OBSOLETE] The bunsenlabs 'exit' menu entry

xaos52 · 2016-07-14 19:01:17

^ OK with me

I sometimes get carried away with options and configurations and whatnot.
KISS principle may be advised here.
Thanks for holding me back, Damo.

Perhaps no new package is needed then?
Everything can be shipped with bunsen-utilities?

xaos52 · 2016-07-14 19:14:20

Scrot:

damo · 2016-07-14 19:22:40

If '~/config/bl-exit/' contains:

bl-exitrc
dark/*.png
light/*.png

then the code just needs to test for dark or light theme selected in bl-exitrc, and uses the *.png from the appropriate subdir.

And there needs to be a test for the primary monitor in use, to place the panel.

It is years since I've coded any python though 8o

hhh · 2016-07-14 21:31:22

^ Yes to merlin branch, perfect.

damo · 2016-07-14 21:53:52

Should this discussion be continued in Development?... The bunsenlabs 'exit' menu entry

In the meantime...

1) Correction to one variable, and added others to be read from bl-exitrc (only hard-coded defaults are being read ATM):
Changed

                    print( 'Loading '+self.cp.get('theme', 'name')+' by ' + self.cp.get('theme', 'author'))
                    self.dialogHeight = int(self.cp.get('theme', 'dialogHeight'))
                    self.windowBackgroundColor = self.cp.get('theme', 'windowBackgroundColor')
                    self.buttonColorStateNormal = self.cp.get('theme', 'buttonColorStateNormal')
                    self.buttonColorStateActive = self.cp.get('theme', 'buttonColorStateActive')
                    self.buttonColorStatePrelight = self.cp.get('theme', 'buttonColorStatePrelight')
                    self.buttonSpacing = int(self.cp.get('theme', 'buttonSpacing'))
                    self.sleepDelay = float( self.cp.get('theme', 'sleepDelay') )

to

                    print( 'Loading '+self.cp.get('theme', 'name')+' by ' + self.cp.get('theme', 'author'))
                    self.dialogHeight = int(self.cp.get('theme', 'dialogHeight'))
incorrect -->       #self.windowBackgroundColor = self.cp.get('theme', 'windowBackgroundColor')
                    self.dialogBackgroundColor = self.cp.get('theme', 'windowBackgroundColor')
                    self.buttonColorStateNormal = self.cp.get('theme', 'buttonColorStateNormal')
                    self.buttonColorStateActive = self.cp.get('theme', 'buttonColorStateActive')
                    self.buttonColorStatePrelight = self.cp.get('theme', 'buttonColorStatePrelight')
                    self.buttonSpacing = int(self.cp.get('theme', 'buttonSpacing'))
                    self.sleepDelay = float( self.cp.get('theme', 'sleepDelay') )
added -->           self.overallOpacity = int(self.cp.get('theme','overallOpacity'))

2) To use bl-exitrc opacity value:

Change ->    #for o in range(1,100):
To ->        for o in range(1,self.overallOpacity):
                    sleep(self.sleepDelay)
                    while gtk.events_pending():
                        gtk.main_iteration(False)
                    self.set_opacity(float(o)/100)

I now have a set of inverted icons, so I'll see about how to use them as Dark/Light alternatives.
BTW, to invert the colours of all icons in a directory, keeping the same name, an imagemagick command is:

for i in *.png;do convert $i -negate $i; done

Light theme scrot:

Last edited by damo (2016-07-15 01:03:01)

damo · 2016-07-15 01:17:37

Could alternative themes be set with bl-exitrc, using something like...

[theme]
theme=Light
   [[Light]]
     name=Light
     etc
   [[Dark]]
     name=Dark
     etc

hhh · 2016-07-15 01:18:48

The whole thread should have been posted in Dev. Merging, since @damo and @xaos52 are adopting this into bunsen-utilities.

hhh · 2016-07-15 01:25:13

Merged from... https://forums.bunsenlabs.org/viewtopic.php?id=2365

johnraff · 2016-07-15 05:39:52

damo wrote:

Isn't this getting unecessarily complicated for a briefly-visible exit panel?

I was wondering the same, but maybe if the methods and processes developed here can then be re-used in other user interface windows then it will be worth the effort.

Last edited by johnraff (2016-07-15 05:40:26)

xaos52 · 2016-07-15 11:43:54

I created the bunsenlabs/bunsen-utilities merlin branch and posted my first version of it.

@damo,
I have not included your corrections from post #145.
You can do that yourself now.

I suggest we merge our changes into merlin frequently so that we can keep our local versions of the merlin branch synchronized.

I will be working on:
1. Making the script more robust to typo's in the config file.
2. Cheching how to implement getting the primary screen dimensions in python
3. Checking how to implement your proposed bl-exitrc layout suggestion in post #146

Damo wrote:

if '~/config/bl-exit/' contains:
bl-exitrc
dark/*.png
light/*.png
then the code just needs to test for dark or light theme selected in bl-exitrc, and uses the *.png from the appropriate subdir.

OK. Will do that.

BTW:
We need 2 more images per set for actions hybernate and hybridsleep.
Up to you for obvious reasons

xaos52 · 2016-07-15 18:33:01

New scrot:

Looks like the Hybridsleep images landed up in the wrong directories.
Dark image in light dir and vice versa.

We're almost there, I think

damo · 2016-07-15 19:08:02

xaos52 wrote:

...
Looks like the Hybridsleep images landed up in the wrong directories.
Dark image in light dir and vice versa.
...

I put the black images in "dark" and the white ones in "light". I was unsure if the names would refer to the images or the theme, but there is still plenty to do anyway...

EDIT: ref window position and monitors, have you seen http://www.pygtk.org/pygtk2reference/cl … creen.html

Last edited by damo (2016-07-15 19:13:50)

xaos52 · 2016-07-16 07:50:48

damo wrote:

I put the black images in "dark" and the white ones in "light". I was unsure if the names would refer to the images or the theme, but there is still plenty to do anyway... wink

Could you switch em around?
I am using the 'theme' key from the 'theme' section of the config file to determine the theme details and the directory where the png's for the theme reside.

damo wrote:

EDIT: ref window position and monitors, have you seen http://www.pygtk.org/pygtk2reference/cl … creen.html

Yes, I have been using these reference pages for pygtk2.
I think those functions return values for the 'whole screen', which for my configuration is the total of external and laptop monitor sizes.
But I will check again.

I had an epihany this night that it was indeed the openbox policy that placed the merlin window.
I guess using the openbox fragment you posted in the commit comments will solve this.

Thanks

damo · 2016-07-16 20:14:00

UPDATE: git commit

Added Bunsen themes to bl-exitrc, and enabled adding other themes by the user.

The user could also include their own icon directory, as long as the names follow the 'bl-exitrc' convention.

Example user theme

Last edited by damo (2016-07-16 20:30:20)

xaos52 · 2016-07-17 08:46:29

Nice one, damo

hhh · 2016-07-19 06:00:53

I'm sorry, I've been busy testing autostart configs on live-build. Should I build my own bunsen-utilities package from merlin to test this?

NM...
https://forums.bunsenlabs.org/viewtopic … 451#p32451

Going to test now!

hhh · 2016-07-19 13:44:39

Unnecessarily fussy? More like flipping gorgeous, must-have lickable yes love love love.

How do I disable mouse-hover so it doesn't override keyboard navigation?NM, it's a theming issue. I see the hover-outline now. Beautiful!

MerlinElMago · 2016-07-19 14:34:12

Whoa... I didn't think it would become so popular

Thanks for all the 'likes'.

I'm not gone...I'm just being pretty busy with a project. If I have some more time I will check the dual monitor issue.

Best regards
Merlin

hhh · 2016-07-22 00:08:02

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.

xaos52 · 2016-07-22 13:15:12

Showing a default image-not-found png when the user configuration refers to a non-existing file.

Configured for four buttons. One of the buttons configured for non-existing png file.

#141 2016-07-14 19:01:17

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

#142 2016-07-14 19:14:20

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

#143 2016-07-14 19:22:40

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

#144 2016-07-14 21:31:22

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

#145 2016-07-14 21:53:52

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

#146 2016-07-15 01:17:37

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

#147 2016-07-15 01:18:48

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

#148 2016-07-15 01:25:13

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

#149 2016-07-15 05:39:52

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

#150 2016-07-15 11:43:54

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

#151 2016-07-15 18:33:01

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

#152 2016-07-15 19:08:02

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

#153 2016-07-16 07:50:48

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

#154 2016-07-16 20:14:00

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

#155 2016-07-17 08:46:29

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

#156 2016-07-19 06:00:53

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

#157 2016-07-19 13:44:39

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

#158 2016-07-19 14:34:12

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

#159 2016-07-22 00:08:02

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

#160 2016-07-22 13:15:12

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

Board footer