Topic: Opebox is the shizznit!

I  had to take a little vacation. So I booted up Peppermint Ice and have been using it all day. It was my distro of choice before I could really get clicking with crunchbang, but it's been weeks. LXD is like an automatic transmission and I've gotten used to a manual. Well, I can't stop reaching for the clutch that isn't there. It's been a right click hell... and I had no control over the vehicle.

So I installed obmenu, logged into an openbox session and....   ahhh, nothing but a pure black screen, a menu, begging for customization popped up upon a right mouse-click at a random spot on my desktop. The power was now back in my hands!

I'm going to see how long I can go with out bringing a panel up. I really love the space in here....  Openbox! wink

Re: Opebox is the shizznit!

When I first built my Arch with a plain Openbox desktop . . . that's what I would get when I first opened the OS.

Just a plain medium gray screen with a 'right-click' menu . . . nothing else.  lol It was really kinda cool

I played with that for a while . . . as I got 'really, really' good at configuring Openbox.

Registered Linux User: #497030
LinuxMint Forum | DeviantART page | Lost-in-the-Box Forum  |  Ask.Debian
#!Crunchbang 'Statler' (Openbox) -- LinuxMint-Debian-Fluxbox Edition

Re: Opebox is the shizznit!

I hated it my first time around with it. I was completely lost. I couldn't understand why menu items wouldn't execute. Why where there uninstalled apps in the menu? Plenty of things disturbed me and I ran away from it fast. But there was something about #! that eventually lured me back and I decided to put the time in.

I really should check out XFCE again to see if there's something I missed, but to tell you the truth, I think I've developed a distaste for menu icons. Maybe this is a silly hang-up.

Re: Opebox is the shizznit!

are_you_root wrote:

I really should check out XFCE again to see if there's something I missed, but to tell you the truth, I think I've developed a distaste for menu icons.

Settings>>Desktop>>Menus, uncheck "Show application icons in menu".

Re: Opebox is the shizznit!

hhh wrote:
are_you_root wrote:

I really should check out XFCE again to see if there's something I missed, but to tell you the truth, I think I've developed a distaste for menu icons.

Settings>>Desktop>>Menus, uncheck "Show application icons in menu".

Thanks, that did the trick.  The curious thing is that I went to make the same change on an install of Debian XFCE. No go! May be a Sid issue though with that deal.

Anyway thanks again. Much more attractive without icons. Less distracting. I'll give some time to XFCE now and see how it measures up to my love for Openbox.

cheers!

Re: Opebox is the shizznit!

vrkalak wrote:

When I first built my Arch with a plain Openbox desktop . . . that's what I would get when I first opened the OS.

Just a plain medium gray screen with a 'right-click' menu . . . nothing else.  lol It was really kinda cool

I played with that for a while . . . as I got 'really, really' good at configuring Openbox.

After installing #! this last weekend with Openbox, I decided to install Openbox in Arch the other day.  For a fairly new linux user I must admit as with are_you _root that it was a little intimidating but as someone who wants to "LEARN" linux and not just have an OS that does everything I thought this could be really nice.

My question for you vrkalak is, I realize and have been reading a lot of Openbox sites including the Arch Wiki that there is a lot you can configure.  But for the new user who has this clean grey blank slate with nothing more than a right click menu (I did install and run menumaker) what should be my first course of action.  I also installed FF and when I minimized it....It disappeared.  smile
I also downloaded from the repos obconf, menumaker, openbox themes, transset-df, pcmanfm, ntfs-3g, amarok, nitrogen, tint2, conky, and wicd.  (do you recommend more?)So I think I have just about everything I need to get started.  I just do not know exactly where I should start first.  smile

Thanks ahead of time for yours as well as any other's response.  smile

All the best,

Ian

Re: Opebox is the shizznit!

I would recommend editing the menu first so you can use it for launching a terminal, file manager, text editor, and web browser at least. Add additional programs as necessary.

Also since Openbox doesn't include any panel, you can access minimized clients by middle-clicking on the desktop. A panel would probably be the second thing you want to configure unless you want to get familiar with being panelless.

Note: ** Please read before posting **

BTW if you wish to contact me, send me an e-mail instead of a PM.

Re: Opebox is the shizznit!

anonymous wrote:

I would recommend editing the menu first so you can use it for launching a terminal, file manager, text editor, and web browser at least. Add additional programs as necessary.

Also since Openbox doesn't include any panel, you can access minimized clients by middle-clicking on the desktop. A panel would probably be the second thing you want to configure unless you want to get familiar with being panelless.

Would I be correct that creating a panel would be configured in the rc.xml file?  I would like to at least see some sort of icon or something if I minimize lets say Firefox or terminal.  smile

Thanks anonymous for taking the time to respond.  smile  I also apologize to are_you_root if it appears I may be threadjacking your post.  It just seemed to fit where I am at.  smile

All the best,

Ian

Re: Opebox is the shizznit!

ichase wrote:

Would I be correct that creating a panel would be configured in the rc.xml file?

No, you wouldn't. Panels are standalone applications, that have their own config files. A good panel to use with openbox is tint2, which is - like openbox - highly configurable by editing its config file found in ~/.config/tint2/tint2rc

Another option would be the xfce4-panel.

Oh, and panels give you the icons you want when you minimize an application wink

Let's do it and don't screw it.
      Github || Deviantart

Re: Opebox is the shizznit!

Thanks Unia,
I downloaded tint2 from the repos.  Once configured, how do I make OB use it as the desk top.  Is tint2 configured then added to the rc.xml?
I have read so many links that cover each of these but nothing that shows the new starting from scratch user how to put them all together.  Maybe they do but my lack of experience may allow me to miss it.

Ian

Re: Opebox is the shizznit!

Actually I think I found my answer.  Once configured I would need to add tint2 to my .xinitrc file so that it is activated once I boot in.

Ian

Re: Opebox is the shizznit!

ichase wrote:

Actually I think I found my answer.  Once configured I would need to add tint2 to my .xinitrc file so that it is activated once I boot in.

Ian

I believe that works...also openbox has an autostart.sh file (under ~/.config/openbox/)

here's my entries in autostart.sh for tint2....check out the tint2 thread on the forums for more details on configuring it (you might take someone's sample script for example). 

tint2 &
tint2 -c /home/emile/.config/tint2/tint2rctask &

those two lines actually launch two separate panels.  the regular tint2 command will just launch tint2 using your regular tint2rc config file, the other one can be used to launch tint2 using a different config file.

One of the first things I did when using #! was install gnome-do so that even if my menus didn't lead to a program, I could just type the program name...I realize this is unnecessary because you can also hit alt-f3 to do that...but I prefer gnome-do - and now a rethemed launchy that matches my desktop.

Welcome to OB!

Re: Opebox is the shizznit!

bobrossw wrote:

One of the first things I did when using #! was install gnome-do so that even if my menus didn't lead to a program, I could just type the program name...I realize this is unnecessary because you can also hit alt-f3 to do that...

You should realise though, that this is not standard Openbox behaviour. ichase, are there more issues you need help with?

Let's do it and don't screw it.
      Github || Deviantart

Re: Opebox is the shizznit!

@unia - absolutely...it's like swimming with floaties.

Re: Opebox is the shizznit!

Unia,
I think I have enough to start with but I am sure once I get going I am going to have more questions.

@bobrossw, thanks for some great food for thought.

All the best,

Ian

Last edited by ichase (2011-03-25 00:03:04)

Re: Opebox is the shizznit!

I do have what I hope is a simple question.  I am coming along quite well from the plain grey desktop with a right click menu.
I have my menu set up with the programs I have installed.  I am now using tint2 and have it autostarting.  Have a great backround with the use of Nitrogen and even have conky up and running.  (I still got a LONG way to go to get conky where I want it but I know there is a very imformative thread here for that)

Now, I want to be able to take a screenshot.  I created a small script file and made it executable:

#!/bin/bash
DATE=`date +%Y-%m-%d\ %H-%M`
import -window root "$HOME/Desktop/screenshot $DATE.png"


and added a key binding under the keyboard section of my rc.xml

<keybind key="Print">
<action name="Execute">
<command>screenshot.sh</command>
</action>
</keybind>

Problem is, this is not going to work on this laptop because I have to select the Fn key to select the Print Screen (prt sc) key.  So what would be the correct keybind sequence?  <keybind key="X X">

I would imagine that there is probably a program I can download that would make this all much easier huh?  smile

I have googled this and I can't seem to find the right search criteria to get the answer I need.  smile

Thank you in advance for your help. 

All the best and have a great weekend,

Ian

Re: Opebox is the shizznit!

Even with a Fn key it should still work. Have you tried it and checked?

Note: ** Please read before posting **

BTW if you wish to contact me, send me an e-mail instead of a PM.

Re: Opebox is the shizznit!

here's what mine says...

    <keybind key="Print">
      <action name="Execute">
        <execute>scrot '%Y-%m-%d--%s_$wx$h_scrot.png' -e 'mv $f ~/images/ &amp; viewnior ~/images/$f'</execute>
      </action>
    </keybind>

Re: Opebox is the shizznit!

As bobrossw mentioned, you could install scrot for making screenshots. Scrot is a simple command line utility to do so.
It's in the repo's, so installing it shouldn't be a problem. When you have it installed, you can take bobrossw's keybind and paste it in your rc.xml instead of what you have there now for the screenshot.

Also, if you want to find out specific keys, xev is the tool to use. Run it from a terminal, press the button which name you need and voila, it's in the output.

Let's do it and don't screw it.
      Github || Deviantart

Re: Opebox is the shizznit!

@anonymous I tried it but  Failed to execute Child process "screenshot.sh" no file or directory.  I looked back and made sure there were not spelling errors and what not and everything seems to look ok.  smile

@bobrossw - I don't have scrot installed

Ian

Re: Opebox is the shizznit!

That means the shortcut is working and the problem is with your script. Make sure screenshot.sh is executable and you have it inside a folder thats in $PATH. Or alternatively, use the full path to the file.

Note: ** Please read before posting **

BTW if you wish to contact me, send me an e-mail instead of a PM.

Re: Opebox is the shizznit!

The file is located in:  /usr/local/bin/screenshot.sh

I then made it executable by typing as root:  chmod a+x /usr/local/bin/screenshot.sh

So at this point I am not sure why it's not working.

Re: Opebox is the shizznit!

Does it work if you run it from a terminal?

screenshot.sh

or

/usr/local/bin/screenshot.sh
Note: ** Please read before posting **

BTW if you wish to contact me, send me an e-mail instead of a PM.

Re: Opebox is the shizznit!

when I run it from terminal I get the following:

{root@ichase ichase}# /usr/local/bin/screenshot.sh
/usr/local/screenshot.sh:  line 1:  !#/bin/bash: No such file or directory
/usr/local/screenshot.sh:  line 3: import: command not found

Re: Opebox is the shizznit!

The first error, e.g. line one, shows that the first line in the script (the #!/bin/bash line) is wrong. Though, if I scroll up the page, it looks ok. Double check the /bin/bash line in your script?

Last edited by Unia (2011-03-25 19:22:40)

Let's do it and don't screw it.
      Github || Deviantart