Saturday, September 13, 2008

Ubuntu 8.10 Inreped Ibex: Part 1

Alright, I know it's technically Saturday and I said I would have this up on Friday but I ran into some technical difficulties. The update is installing on my test computer as we speak. The problem is that I started the upgrade _Thursday_ night. So far several packages have failed to upgrade properly as well, including update manager. However this is an _alpha_ release (alpha 5) so I expect these problems and won't hold it against them. They will be duly reported.

Well point is that I have nothing really to say tonight. I wish I did. But I don't. Only thing I can really throw in there is that it would be nice if the bandwidth on the Ibex repositories were higher. Upgrading my laptop to 8.04 from 7.10 took roughly four hours total. The massive download _alone_ for Ibex took over 14 hours. Not ok in my book.

More to come as I finally get to rev up the system and take a look around.

Until then.

Thursday, September 11, 2008

Inroducing BrowserBox WM

The BrowserBox window manager project has now started. This aims to be a lightweight desktop environment with integrated net capabilities. Some of the planned features include:

- Desktop integration with Google Gadgets
- Desktop configurable with html, javascript, and ruby on rails
- Configuration tools for the desktop for those with less programming skills or none at all
- Desktop integration with the Gecko web browser engine

The basic idea behind it all is to allow for seamless integration between the world wide web and dynamic content on the desktop.

The project is based on the blackbox window manager and is currently in the planning stages and will being development shortly.

This project is currently looking for volunteers to help!
Positions available include:

- C++ Programmers: Must be competent with C++ and have some GUI design knowledge
- Perl Programmers: Must be able to write automated configuration scripts
- Web Designers: Must be able to work well with HTML or XHTML and Java
- Graphic Designers: To design default themes and logos

If you are interested in volunteering for the project please e-mail me at hpypenguin [at] users [dot] sourceforge [dot] net for more information or with details of your experience.

Wednesday, September 10, 2008

First Look at Ubuntu 8.10: Intrepid Ibex

Well I had planned on this being the first article I wrote about the forthcoming Ubuntu release but I'm afraid that at this time I can not do that. The upgrade will not properly work on the test desktop I selected. The problem, according to the feedback from update manager, is an inability to correctly modify the repositories prior to the actual upgrade taking place.

When I have time I will look further into the issue and see if there is already a workaround known and if not what I can do to create one.

Until then I have selected another test desktop which will take a full install of Ibex from CD. However, I will not consider these results to be reliable in terms of upgrading as we're talking about different processes being used at this point.

To highlight some on the features of the new version I will be using ext4 with LVM and both Gnome 2.2.3 and KDE 4.1. I've never been a fan of KDE but I suppose it deserves a place in the reviews as many people do like it and use it with Ubuntu on a regular basis.

Bugs found during this test will be listed here and be submitted to the development team.

The desktop that will be used has a Pentium 4 at 2.6Ghz and 2GB DDR400 RAM along with a 30GB and a 60GB IDE Hard Drive. Testing will begin this Friday the 12th and will continue for five days with posts being made at least once a day on the status and results.

Sorry for the delay.

Ah, before I forget the version will be Alpha 5.

Until then.

Tuesday, September 9, 2008

Five Window Managers You Should Try

1.) FVWM - http://www.fvwm.org
A lightweight highly customizable window manager for the minimalist in all of us. It can be tweaked and turned into just about anything you want it to be. Although I found one of it's forks, FVWM-Crystal, to be more to my liking, there's no denying that this is the base that makes Crystal such a joy to use.

2.) IceWM - http://www.icewm.org
My personal favorite and the window manager that runs my infamous development oriented laptop from the recent How-tos. Easy to configure and easy to use. This manager is compliant enough with gnome (and even have an official gnome support version) that I was able to run a bunch of gnome apps and even the gnome menu bar within it without a hitch. Lightest memory footprint I've recorded occupying only 3.9% of my laptops 512MB RAM at the most. Anyone looking for sheer performance and a remarkably easy setup would do well to look at this. Check out the IceWM Configuration How-to on this site for tips if you need help.

3.) Enlightenment - http://www.enlightenment.org
I didn't like it but what do I know. One of the more popular lightweight environments availible. While I had a multitude of problems with it sheer number of users alone justifies at least taking a look. It's a real hit and miss on this one. You either love it or hate it. I will say that it can be made to look exceptionally nice when the effort is put in.

4.) Fluxbox - http://fluxbox.sourceforge.net
The ultimate in simplicity. Designed to be as usable as possible, any sort of attractiveness seems to be an after thought. Which as far as I'm concerned is a good thing. When testing this window manager I was pleased with the results but I suffered from extreme configuration issues. My laptop wouldn't do much with it even after fetching the latest version off the website. I'm still not entirely sure what the problem was. So I had to run it on one of my testing desktops. As a result the test results are somewhat tough to analyze as that desktop has far more processing power then my laptop does. Suffice to say it was pleasant enough and I'm confident that when and if I work those issues out that it will run well on the laptop too.

5.) Wm2 - http://www.all-day-breakfast.com/wm2/
If all you really want is frames around your X programs, that's about all you're gonna find here. That is it's one and only selling point. There's a narrow niche for this window manager but a real one. If you hate extras of any kind this is the one for you.

There you have it. If you think I left one or two off let me know!

Until then.

Sunday, September 7, 2008

Configuring IceWM: Basics

When I started using IceWM I found little in the way of straight forward tutorials for configuring it. The documentation available from the website is suitable for most cases but certainly lacking in some regards. So I'm going to present some tips on configuring this handy window manager as easily as possible.

First things first. I would recommend against using IceConf. This program is a gui that gives you some options and will automatically generate config files for you. I advise against it because the options it lists are not comprehensive, not very well explained and the files it generates may leave off certain features enabled by default that you may wish to keep but not know how to implement yourself. Foremost of which is the right-click menu. This menu goes away after using IceConf and when I started tweaking and configuring my window manager I didn't know how to get it back. Nor was the preferences file generated by the program commented well enough to let me know what I needed to change to fix it.

Now that that's out of the way let's get started. These directions are for Debian based systems and file paths as well as some commands may be different on other distributions. First make a new directory in your home folder called '.icewm'. Now copy the contents of '/usr/share/icewm/' into the new directory '.icewm'. These are the default config files for the window manager. Editing the ones in your home folder not only means that you will have backups and that on a multi-user station you won't be messing with other people's settings. At some point you may want to add a file called 'startup' but we'll get to that later.

The first file you probably want to edit is called 'preferences'. It can be easily modified using your favorite text editor by simply uncommenting and/or changing the boolean operator of a given function. The file is well commented and functions are well explained in most cases. If you don't know and can't figure out what something does you have two choices. To be on the safe side don't touch it and assume it doesn't matter much anyways or if your willing to take a bit of a risk mess with it and see what happens. I strongly encourage the latter. After all you can always change it back and you have backups handy just in case, may as well have some fun. Besides almost all of the options in the file have to do with things like color, size and style. It's doubtful that you're going to break anything by changing these values.

The next file is called 'keys'. This allows you to change the key bindings within the environment. Again it's pretty self explanatory. Modifiers available include Alt, Ctrl, Shift, Meta, Super, and Hyper. To add a key binding on a new line type

key "$key1+$key2+key3.." $command

where $key(n) are the keys to use for the bindings and $command is the command with options to execute. The keys to use must be surrounded by double quotes. The command should not be quoted. I find this to be the most useful section to configure. Since I have IceWM on a laptop and the mouse is awful this allows me to bypass using it completely if I so choose (and I do, because I hate the built in mouse on laptops, all of them)

The last file you're most likely going to want to edit is called 'menu'. This file controls what is displayed in your start menu. This is also pretty darn easy to edit. Notice a theme here? It's really quite simple to make tons of changes. To add a program to the menu find the section you would like it to go under and on a new line but staying inside the {} brackets type:

prog "$Name" $Icon $Command

where $Name is the name you would like to appear in the menu, $Icon is the path to the icon to be used (or in in lieu of using an icon type '-' without the quotes of course) and $Command is the command with options to execute. To add a menu or sub menu type:

menu "$Name" folder {
$prog1 line
$prog2 line
....
$prog(n) line
}

where $Name is the name of the menu and $prog(1, 2, n) are the lines for the programs you would like to appear in that menu as described above. Menus can be nested inside other menus too. Anything that appears within the {} brackets of a menu will appear under that menu and that goes for separate menus as well. Here's an example taken from my menu file:

menu "Development" folder {
menu "Math and Science" folder {
prog "Octave" octave octave-2.9.12
prog "Maxima" maxima maxima
prog "R" R R
prog "SciLab" scilab scilab
}
menu "IDEs" folder {
prog "Geany" geany geany
prog "Eclipse" eclipse eclipse
}
menu "Help and Documentation" folder {
prog "DHelp" dhelp dhelp
prog "DWWW" dwww dwww
}
}

If you can't tell from the example this creates a menu called 'Development' that then has three submenus; 'Math and Science', 'IDEs' and 'Help and Documentation'. The quotes around the names of the programs and menus are not strictly necessary unless there is a space in the name. They are included for consistency.

The last file I'm going to cover here is called 'toolbar'. It is edited in the exact same way as the 'menu'. The difference here is that changes applied to this file appear on the toolbar itself rather than in the menu.

Well that wraps it up for today. At some point I'll cover some more advanced configuration methods for IceWM including using the startup file and building themes. Until then.