Kommander is a powerful but easy to learn development environment. “Graphical Scripting with Kommander” takes us through the creation of a graphical interface for Konstruct, a tool for downloading, configuring and installing KDE from source packages. The article also lists some of the exciting developments coming to Kommander in the near future.
Graphical Scripting with Kommander
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Why does the name of almost every KDE app have to start with the letter ‘K’? Poor taste IMO. An arbitrary style for its own sake.
On-topic though, doesn’t KDE already have KDevelop?
is there a stupi script that makes always the same comment each time kde is mentioned?
i’ve heard thi K stuff for years…relax people, the K is going to stay there just like the “i” in the apple iLife programs, it’s called branding and it’s a good thing.
You should know how nice it is to find a good name on which the K stands out. It is really fun to do. 🙂
KDevelop is for writing code, Kommander is for graphical scripting. To glue scripts together and to provide a nice looking gui.
Let’s say that 2 years ago, you bought a digital camera. At that time, you wrote a script, to download the pictures to a directory and change the name all in one go. Now with Kommander, you keep using your *well tested* script and provide just a gui to that task. Let’s say that this task is very usefull, and you want to make a real program others can use it as well, then you would probably use KDevelop to make a new program that does that task.
A very interesting article, but it uses v1.1-beta. The current version is 1.0. Their script, which is downloadable, doesn’t work under 1.0, and I don’t want to install the beta version.
Still, interesting.
these Kommander developers are so excited about their app they always only talk about a newer version than everybody has
but anyway, Kommander is a great development tool…
Why do people keep complaining about the K names? I admit it would be more effective if all programs were given sensible names with a K at the start (which isn’t part of the word), but the whole point is branding. Let’s say I bring out a soft-drink and call it Z-Cola and it becomes quite popular. I can next release my next drink called Z-Lemonade and everyone who knows about Z-Cola will assume it’s from the same company. It’s free advertising and completely logical. Apple do it with their “i” prefix on everything (iTunes, iPod, iMac, iChat) and nobody ever complains about it.
It is different something like i-Name from something like “K”ame, apple just adds the “i” plus word, KDE applications substitute one letter of the name(except from some applications like K-Mail, that sounds good) but words like Konqueror, KolorPaint, KuickShow, that is what makes it annoying, sounds bad and looks bad in the spelling.
No they are not.
As the last user mentioned they sound really bad and are bad in spelling.
Besides it is not good for people whos native language isn’t english. People learn quickly and seeing this confufes them.
>As the last user mentioned they sound really bad
Why?
Konqueror -> spelled Conqueror
KMail -> spelled Kay-Mail
What’s the problem with that?
How do you spell gEdit? And gThumb?
>Besides it is not good for people whos native language isn’t
>english. People learn quickly and seeing this confufes them.
Thanks for making me feel smart =)
For nearly every category of Windows software there’s an app called Win*whatever*…
e.g. WinGate, WinFax, WinMine etc. etc. etc.
The ‘K’ wouldn’t be my first choice, but it does let users know in an instant that the app is designed for KDE….a_good_thing IMHO.
…WinAce, Winrar, Winamp, winAVI, winLyrics, WinCal, WinMMPC, WinLogger, … (Just completing the list…)
Yes, but you don’t see something like Wamp, War, Wal, Wogger, etc, just win+word.
Not the case with KDE apps.
get over it.
You know what’s far worse than the K? Seeing people bitch about it in the comments for nearly every KDE-related article on the page. I can only second cr@zy: Get over it.
*You* start a project, *you* get to choose the name. If you’re not the founder of the project, you keep quiet and just use it.
I mean, what’s next, an action against recursive acronyms? We’ll just call it RAARC (RAARC’s an Action Against Recursive Acronyms). Anyone for RAARC/Linux?
But there are advantages to the common scheme (Common but not universal: in fact there are a handful of KDE apps that don’t start with “K”, I’m not at my linux box right now, but alsaplayer comes to mind) If I see that there is a new application called KSuperDuperApp, I don’t have to wonder if I already have the majority of its dependencies installed. If I run KDE, I probably do. And if not, I can choose to run GFantasticApp or XOldFashionedApp instead. Clear. Simple. Unambiguous.
But don’t let me stop you from starting up a new project and calling it whatever you like. An unrelated name will make it slightly less likely that it will reach its intended audience, but it will be *your* right to name it.
Ahem, before some nitpicker points it out for me, that should have been either “aCronyms” or “RAARA”.
Because its Kool!
why not allow arbitrary scripting languages to be ‘plugged’ ?
This would be ubercool imo (I’m especially thinking of ruby, tcl and perl here, wich are direct descendants of sh/awk/sed, but other will fit.. )
This is planned. Check discussions about Kommander on Dot:
http://dot.kde.org/1104779564/
http://dot.kde.org/1103960583/