Settings for the Novice: Yast Revolutionized


Connect to the Internet in More Than 10 Clicks (BUG)

(As requested by my audience, I wish to make a distinction in pointing out that my post is mistaken in thinking that the described features of KDE are a default. They are, contrarily, a BUG with my own installation. Nevertheless, I will hold the secondary method of connecting to the internet as something that can be revised and improved.)

As KDE worked on the new Network Manager for version 4, they decided to make the interface more powerful and through the use of the network manager widget, more accessible to users. The interface is indeed powerful and full of features aimed at working out every corner of customization on a given network. Wireless or wired network, they both have their particulars when it comes to connecting to the internet.

However, seeing at different operating systems, KDE's network connection manager seems cumbersome and hard to work with. Nevertheless, the disappointment comes from the first run of this software, not from the daily usage of it. Once everything is set up correctly, network manager will not even ask you to connect to the internet. It will do it automatically. Automatization however, comes at a cost of more than 10 clicks and a little extra knowledge about the particular network you are trying to access.

I really like the way that Mac OSX does it. They have an icon sitting in the system tray, as you click it, a drop down menu displays all the available networks. Users select one and you would be connected to it after typing a password if necessary. The next time you are around such network, Mac OSX will connect to it automatically unless you decided to run on a different network.

Another method out there is very similar to what Mac does. Ubuntu tries to connect to the internet in a simlar way. They also feature a network icon in the system tray. If you click on it, you get a drop down menu with available networks as well. Selecting and entering a password are very much the same as in Mac, except Ubuntu (and KDE) have an added feature of password protection through Gnome's Keyring and KDE's KDE Wallet.

During the first time that a user selects a network that is password protected, he is asked to create an extra password to store the password just entered into the wireless network setup. At first, this was very confusing to me, I didn't know if my password for the keyring or wallet had to be my root password, or a different password. I also ran into the mistake to placing the wireless network password into the keyring, thinking that it was the password for the wireless network being requested. Obviously, this can be solved by being smarter ;) But it does show that there is a learning curve that is not so smooth when working with networks. I think people who are trying to connect to the internet on a Mac also run into confusion as well. An icon sitting at the top bar that does not connect to the internet unless you click on it also represents a learning curve but one that takes less time and effort to do what we do most on a computer, browse the internet. Mac does not have a keyring or wallet that pops up upon login when you are trying to connect to a specific network. I believe these settings could change to make it easier on users to connect. If security seems to be an issue, probably Linux can get by easily with it. openSUSE could also benefit from a more seamless connection to networks by simplifying the process, it would stand out as the distribution with the easiest connection learning curve.

This is what one currently sees as you try to connect to the internet under KDE 4.6

 You connect not by clicking on an available network, you do it by clicking network manager.

 Then you are presented with a screen that contains the first network setup designed for wired networks. However, in my case, I need to add a wireless network, so I click on the second tab.

 After that, if this is the first time, then I do not see any available networks. I need to click on add.

 A rather complicated form shows up in which a tiny button called "scan" will eventually show me how to find the wireless network I want to connect to.

 Once clicked, I am greeted with a very tiny window that shows all available wireless networks around me. If you are in the place where I am, it is really hard to see where I am to click. Instead I choose "Details" which organizes the view in a list.

I select the one I am to connect to and hit OK.

Later, to finish the process, I need to hit OK a couple of times and then I get back to the desktop. But I am not connected yet. I need to go back to the Wireless icon on the system tray and now I am able to see the new connection I added through the prior steps. Once I click on it, the setup will finally end by connecting to the wireless network.

I think this is really too long. It could be made short and there are plenty of good options out there that have simplified this process. openSUSE will benefit from a simpler way to connect to the internet if they choose to create a more simple method. My idea would be to simply show a drop down menu with the available networks, select, enter password and connect. If a keyring or wallet is necessary, allow this services to unlock passwords at system startup without having to enter it everytime.

By the way, this is the way I have my current KDE 4.6 with openSUSE 11.4. I am liking it so far.


openSUSE Release Party - Provo, UT

The openSUSE release party was a lot of fun and I was very happy to be there one more time. The Novell facility in Provo, UT is pretty big and had plenty of room to accommodate the few of us that attended. I met a few personalities as well, most of them participants of the SLED version of openSUSE sponsored by Novell. I also had the chance to talk to some of the guys there about what they did as part of the project and felt like my contributions to the project seem to be so much smaller than theirs. People working for XEN, the package manager, Yast and others have put a lot of effort into making openSUSE a great distribution.

I am happy for their achievement and their contribution as well. openSUSE would not be my favorite distribution if it wasn't for much of the work that these people do. So a big THANK YOU to all of them. They also had pizza, a few goodies and 2 big screens. That did it for me. I was happy to see openSUSE handling big screens like that. Although with gnome 3 and the resolution, there were some glitches.

Anyway, I promised some pics and here they are. They are not the greatest quality, I used my Palm Pre to take the shots and the lighting was not that great for this tiny phone.

Me and my goodies :D


Going to the openSUSE Launch Party :D

I know this is unusual, but I am going to the openSUSE launch party in Provo, Utah this week. I am excited. I know the team has been working hard in bringing a freshly updated version of my favorite distribution. I believe openSUSE has one of the strongest communities out there.

Changes in directives recently have made me think that openSUSE is becoming a pillar for the Linux community. We are headed in a good direction and I am hoping that we will also be able to work on the GUI as well :D I guess that will always be my initiative. Working with the GUI and making it more polished is something that can be done with some effort and "cool" thinking.

I recently read an article that reviewed the newest release and, although not the main part of the article, the author did point out how hard it could be working with Yast. He said "it screams 'developer,'" and I tend to agree with the author. Simply, Yast is too powerful and great not to make it more accessible to all of the users out there.

If you want to check it out, click here.

Anyways, I will be taking some pics and stuff at the Novell building :D

See you all soon


Bring Back Domino!

The Domino KDE style was an emergent and versatile style theme. It had the ability to be customized much like what Qt Curve or Bespin does. However, Domino had the ability to be customized and be previewed instantly has you made the changes. The configuration widow had all sorts of simple modifiers that could truly give some personality to your KDE 3.

This thing was so good that I even created my own versions of the style with my own tweaks and posted them at

This thing was something very worth the time playing with. I think it was one of the best styles that someone coded for KDE. You could control brightness, button shape, etc. Well mixed with the window decoration, one was able to create very concise and simple themes for your linux machine. However, with the coming of KDE 4, the developer of Domino decided not to port this theme to KDE 4 and the development stopped.

It also seems that the project did not attract any more devs that would have wanted to port it to KDE 4. So here I am, talking to the openSUSE people that know how to code well, asking them to give this style a chance to style openSUSE with KDE 4. Would you take it into consideration?

Oxygen is a beautiful style, very well thought. However, Oxygen is not like Domino when it comes to customizing your theme. Also, Oxygen ships by default with just about any other distro out there. openSUSE could step up with differentiation by using this style. Maybe what I am asking for is rather unrealistic, but Domino is such a great style, it deserves a chance.