Skip to main content

My Review of KDE4 (SVN)

About Me:

First of all something about myself, I'm Ravi Vagadia. I'm from Amreli a small city in Gujarat state of India. I'm currently doing BS.c. Computer Application (Final Year :P) and I'm (was?) a hardcore Windows user, I've been using Windows from around 10 yrs. I would like to express my views on KDE 4 (Open source Desktop Environment for Linux/Unix based operating systems).
I have been distro swapping since past 4-5 years and finally settled on Arch Linux which is fast, stable and not bloated like some other popular distros.

About KDE4:

K Desktop Environment version 4 (KDE4) was released on 26th January 2008 after many delays and was criticized for its bugs and many incomplete features although it was developers preview release and was not targeted towards general users. However, KDE 4.1 (current stable version) which was released in July 2008, addressed most of the issues and is usable for general desktop users.

KDE desktop is revolutionary and its something more than a simple desktop environment, its a suite of desktop applications. KDE is based on QT4 (pronounced as cute4 :D ) GUI toolkit which uses very low memory and is highly efficient in managing memory and is cross platform toolkit developed by Trolltech (now acquired by Nokia).


here is how my Arch + KDE4 desktop looks like: (click on the image to view full image)


As you can see, traditional desktop icons are replaced with "FolderView", a plasmoid (widget) . FolderView is a container in which you can choose folder so that you can see files from other folders rather than default "Desktop" folder on Desktop. You can put many different types of widgets like "Picture Frame", "Now Playing" etc, same as Mac OS widgets and Windows Vista sidebar widgets but in KDE every part of desktop is a widget which is handled by Plasma(Desktop Shell).

For those people who doesn't like new FolderView concept they can even set FolderView as Desktop Container to get same functionality as traditional (icons on desktop) feel. :
(click on the image to view full image)


you can also set any svg image as wallpaper in KDE4

KDE4 Applications : - No doubt KDE has some of the best apps (Amarok!!) in OSS(Open Source Software) world, although there are many apps which are yet to be ported for KDE4 but I'm sure that devs are working on it.


File Management :
File management application is very important part of any Desktop Environment, KDE 4 uses Dolphin as File manager replacing Konqueror. Some of the awesome features of Dolphin are Tabbed browsing, Split Column view etc. One feature I like the most in Dolphin is "Filterbar" as the name suggests it filters files/folders in current folder with name/extension you type.

I have used "Finder" on Mac OS 10.5 (Leopard), "Nautilus" on Ubuntu and I've been using "Windows Explorer" from Win95 to Vista, although there is huge improvement in Vista's Explorer yet i prefer "Dolphin" as my File manager. it's neat, and fits my needs, Mac OS Finder feels good but lacks advance features.
some screenshots of Dolphin in action :-


Split view / Tabbed File Browsing:-




KDE PIM (Personal Information Management) :-

KDE PIM is the collection of Applications like Email Client(Kmail), Contact Management (Kontact), Calendar, RSS Reader(Akregator) etc


Here is the screenshot :- System Monitor:-

Similar as Windows Task Manager, provides information of your system resources.System Settings:-

Similar to Control Panel in Windows, from here you can change (almost) any settings related to KDE/System.



Final Words:-
I'm using KDE (svn trunk ) last built on 9/9/08. It has many KDE4.2 features like Panel Auto-hiding, resizing panel, Plasmoids as Desktop Containers etc... its running quite stable I'm yet to encounter any serious error/bug. KDE developers are doing great work!!! a big thx for making a wonderful Desktop Environment.


This is my first review!! so plz comment :)





P.S:- Video Review Comming soon!!!! :)

Comments

cyberorg said…
great job for the first review :)

-J
Rajat said…
Nice post....!!!

Hoping for periodic findings from you...

btw, u r now in my _bookmarks_...

KDE :D ROCKS !!!
Gopi said…
great post...
You get very quickly find new topics thats good..

it's really very nice review..
Amit said…
Wow thats really very great. Your words are really wonderful.


Ravi go and go on!!!

Popular posts from this blog

Getting Started with Rancher & Kubernetes

During my time working at Azoi (a startup), I was responsible for maintaining Gitlab for my team along with various other self-hosted internal services. When I first setup Gitlab in 2013, it was quite a task, as setting it up would involve configuring various services using provided scripts and a lot of luck. Fortunately, I found Bitnami Gitlab package to make that process easier. However initial setup is one thing and keeping up with the latest releases was a nightmare.

Fast forward to 2016, I joined eInfochips as Solutions Consultant. Where one of my responsibilities was to modernize development workflow and encourage DevOps culture. It made sense to use Gitlab specially for Gitlab-runner and since this was a fresh setup, I explored few options to setup Gitlab, I found that Gitlab monthly releases were now published as Docker images. So I decided to use Gitlab docker image to host gitlab-ce internally. This time around, the experience was very different, initial setup and upgrading…

Rancher for Microservices : Load Balancing and Scaling Containers.

In my previous post, we saw how easy it is to set up Kubernetes cluster using Rancher. Once you have a cluster up and running, next step is to deploy your microservices on the cluster. In this post, we’ll look at how to deploy, run and scale a docker image on your cluster. We’ll also look at setting up an L7 load balancer to distribute traffic between multiple instances of your app.

Let’s create a simple HTTP service which returns server hostname & current version of the binary (hardcoded). I’ve used go-lang for this, below is code snippet which returns hostname and service version.

All it does is, returns a string "App Version 2.0 running on host: <hostname>", once deployed it will return container hostname.

Next step is to dockerize our service by generating a docker image and push it to DockerHub (or your private Docker registry), below is Dockerfile I used to dockerize this service.


Running this will compile our service and generate a docker image on local mac…