-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login


Sponsoring


-
- Content .- Fans  .- Knowledge Base  . 

Kommander

   1.5.3  

KDE Development Environment

Score 84%
Kommander
zoom


Kommander
zoom


Kommander
zoom


Link:  Link
Minimum required   KDE 3.4.x
Downloads:  37823
Submitted:  May 26 2004
Updated:  Nov 3 2009

Description:

Kommander 1.5 is the final special release in the 3x series. I resume work on the KDE4 version the last week of October. As to why this is still KDE3 vs KDE4 I was basically doing my apprenticeship in C++ and I needed fully functional design and plugins. I have 3 internal applications built with Kommander totaling 96 files and over 41,000 lines of actual script. I am very much intent on a vastly enhanced KDE4 version and porting this. I'm also planning on getting a KDE4 version of Quanta which can use parts built with Kommander.

This release is all about the little things I wanted, like being able to create a text report with links I could click to run scripts. This has the much requested menu button, There is extensive enhancement to widgets with special attention on Tree/Detail widgets and Tables. Widgets now can give geometry for use with popping up widgets and positioning them. There is also control of background color, for that special attention getter.

The applications I have written are used with databases 6 hours or more a day every week. The last new feature added here is 2 dimensional arrays. I have also included docs with this release. There is some out of date information but the new parser section is completely up to date.

Kommander consists of an editor and a program executor. It uses the *.ui files generated by Qt Designer and used by KDE and extends the simple preview to a full on interactive window using DCOP to communicate with widgets. Kommander is intended for non programmers and programmers alike as a rapid development tool aimed at the 80/20 rule. It doesn't do everything, but it does what you mostly need real fast. Kommander Plugins are easy to create and we have a lot of them. Please have a look as they are easy to install and offer great benefits.

* database access http://www.kde-apps.org/content/show.php/Kommander+Database+Plugin+(1.3)?content=75805
* date/time functions http://www.kde-apps.org/content/show.php/Date+Time+Functions?content=77727
* a time widget http://www.kde-apps.org/content/show.php/Kommander+TimeWidget?content=77724
* The Action proxy enables control of MainWindow programs as if they were native Kommander http://www.kde-apps.org/content/show.php/Kommander+Action+Proxy?content=77994
* open with dialog http://www.kde-apps.org/content/show.php/Kommander+OpenWithDlg?content=77745
* KPart loader http://www.kde-apps.org/content/show.php/Kommander+KPart+Loader+plugin?content=75807
* HTML part http://www.kde-apps.org/content/show.php/Kommander+KHTML+plugin?content=75810
* HTTP tool - talk with web sites like you were an HTML data form http://www.kde-apps.org/content/show.php/Kommander+HTTPform+plugin?content=75808

The new parser is the default so you have variables and unlimited nested conditional statments. Some plugins require the new parser but you can run a mix of old and new by using #!kommander in new scripts in an old parser dialog. You can also use a shebang like #!/usr/bin/php to use other languages in a script widget. This also adds testing for the exec bit to prevent accidental execution of downloaded dialogs. There are now extensive help docs with the editor.




Changelog:

1.5.3 fixed matrix_rowToArray using column headers and added sequential find with matrix_findRow
1.5.2 added setTabLabel for TabWidget. I know someone asked here last year, but since I'm in code mode here it is.
1.5.1 fixed array_remove bug
1.5 Everything you always wanted but were afraid to ask for - see our changes at http://kommander.kdewebdev.org/changes.php?releasenum=0
1.3.1 tasty touches for user power - see our changes at http://kommander.kdewebdev.org/changes.php?releasenum=1
1.3-final is a huge improvement over previous versions. See our changes at http://kommander.kdewebdev.org/releases.php?releasenum=2
1.2.9 is a development release from years ago. It is left here just in case you have a KDE 3.2 or 3.3 system that has trouble with newer releases. We strongly advise against getting it unless a new release fails to build on an old system!




LicenseGPL
(kommander-1.5.3.tar.bz2)
Donate
Send to a friend
Subscribe
Other  Apps  from sequitur
Report inappropriate content



goto page: prev   1  2  3  4  5 

-

 Compilation problem

 
 by Raman on: Mar 8 2006
 
Score 50%

./configure
------------------------
configure: creating ./config.status
fast creating Makefile
fast creating kommander/Makefile
fast creating kommander/editor/Makefile
fast creating kommander/editor/pics/Makefile
fast creating kommander/editor/templates/Makefile
fast creating kommander/executor/Makefile
fast creating kommander/factory/Makefile
fast creating kommander/plugin/Makefile
fast creating kommander/pluginmanager/Makefile
fast creating kommander/widget/Makefile
fast creating kommander/widgets/Makefile
config.pl: fast created 11 file(s).
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

Good - your configure finished. Start make now
--------------------------------
make
--------------------------------
execbutton.h:74: error: 'MyProcess' has not been declared
execbutton.cpp:138: error: prototype for 'void ExecButton::processExited(MyProcess*)' does not match any in class 'ExecButton'
execbutton.h:74: error: candidate is: virtual void ExecButton::processExited(int*)
make[3]: *** [execbutton.lo] Błąd 1
make[3]: Leaving directory -----------------------------

What am I doing wrong?

System: Mandriva 2006
Kernel: 2.6.12-17mdk
gcc: 4.0.3 (4.0.3-0.20060215.2mdk for Mandriva Linux release 2006.1)


Reply to this

-
.

 Re: Compilation prob

 
 by bmahn on: Aug 29 2006
 
Score 50%

hi!

// do this in execbutton.h
#include "myprocess.h"

do "make" again
bye.


Reply to this

-
.

 Slackware 11.0 Pack

 
 by gohanz on: Oct 13 2006
 
Score 50%

http://www.slacky.it/index.php?option=com_remository&Itemid=29&func=fileinfo&id=1361


Reply to this

-

 kde error

 
 by ffrits57 on: Nov 1 2006
 
Score 50%

I got the next error message. What to do?

hecking for KDE... configure: error:
in the prefix, you've chosen, are no KDE headers installed. This will fail.
So, check this please and use another prefix!


Reply to this

-

 Re: kde error

 
 by thstaerk on: Jan 2 2007
 
Score 50%

which distro ?
On suse: yast2 -i kdelibs3-devel


Reply to this

-

 window positioning

 
 by dsvilko on: Nov 8 2007
 
Score 50%

Is it possible in any way to move or position the window on screen? The command-line option --geometry gets ignored, dcop call is missing and even my window manager can't remember the window's position. It's always centered.


Reply to this

-

 Re: window positioning

 
 by sequitur on: Feb 25 2008
 
Score 50%

That depends on what window you're talking about. The editor is a hacked early Qt Designer and as such is only partially right with KDE. I have set up the special window settings on the text edit dialog for the editor no problem.

In the just released version you have full access to slots, so while window and widget position and size information are blocked normally in the signal/slot dialog and functions you can call the slot directly for a window to set this on a Kommander dialog.


Eric Laffoon
kdewebdev (Quanta/Kommander) project lead

Reply to this

-

 essential problems

 
 by trisz on: Feb 25 2008
 
Score 50%

I had essential problems with Commander.

I spent about the same time to learn Commander as to learn python-qt.
The result was disappointing for Commander. It is slow, some basic problem cannot be solved, and demands extra force to solve small problems.
Basic functions are missing from the editor, such as syntax highlighting.
The Help file is also missing. It is told, that the usage is trivial, but it is not. It is trivial to use python-qt, but not to use Commander.
I think, the whole application must be rewritten.

I recommand to everybody to use python-qt instead.


Reply to this

-
.

 Re: essential problems

 
 by sequitur on: Feb 25 2008
 
Score 50%

Nice troll. I hoped I'd never see the day... Let's inject some facts here.

1) It's Kommander, not Commander
2) With Python you have to learn a language whereas with Kommander you can point and click with a function browser... which is why there are so many Kommander scripts here that it has it's own content category.
3) With Py-Qt you are directly accessing the C++ class structure to do things and manually writing your windows scripting instead of drawing them visually and rendering them with a Qt library. I found it easier to learn C++ and use Designer without the extra layer of Python to learn.
4) The editor has had syntax highlighting for several years. The new release adds highlighting for the new parser. In fact it's been the Kate part for a few years so it has Python highlighting too.
5) The help file is included and it's 946 KB in my source directory. (That's larger than the entire initial release of Quanta Plus) However I can point you to numerous applications where people never wrote any code and had great success with Kommander. I also have a mailing list and answer every user question on it. It must be a lot easier to tell people not to use Kommander here than to ask me for help via email.

As to whether you should use Py-Qt or Kommander, why choose? Python can easily be used within Kommander using #!/usr/bin/python which means full access with DCOP bindings and the ability to use PyQt also, which can further extend Kommander by accessing Qt's QObject class. You know what that is right? It means anything you can do in C++... and you're not using Python to draw your window, but C++, though you didn't write it, you drew it. You can also use PHP, Ruby, Perl, Rexx or if you're truly insane, scheme, in Kommander, which you can't do with Py-Qt.

I'd like to think you don't mean to be some kind of a rude dumbass, but after staying up till 4 AM every night the last 6 weeks working on this and falling behind in my work you make a summary judgement without even reading the changelog, let alone downloading, then advise others to ignore my work? I think I'd rather buy Steve Ballmer lunch than take this from a member of the community, and I'd rather have my head shaved with a rusty knife than be in the same room with baldy. Your opinion seems rooted in fertilizer, not factual relevent and up to date observations. If there is anything people should be wary of it is taking counsel no more researched or thought out than yours.


Eric Laffoon
kdewebdev (Quanta/Kommander) project lead

Reply to this

-

 Re: Re: essential problems

 
 by trisz on: Feb 26 2008
 
Score 50%

I need e.g. 3 days for a small python-qt application, but I need a whole week if I use Kommander. I am not a beginner, and the upside-down logic of Kommander is strange for me, and remains strange forever. It is a sufferig for a practiced user to work with Kommander (It is a fact not a troll.)
I know, it is simplier to create a qt/kde binding for an object-oriented language like python. One need not to fill up the gap between the C++ library and the script. (It does not apply to the scripting format of python.) Your task is not easy.
Kommander is useful for a beginner, but bash and sh deserve more attention. I think, it must be a work of a team. (It is only an opinion not a troll.)

I will not use Kommander for python. How can I set the widget flags, for example?


Reply to this

-
.

 Re: Re: Re: essential problems

 
 by sequitur on: Feb 27 2008
 
Score 50%

There's a sizable difference between approaching with a different mind set and recommending others not use it. If for instance you are an avid Python programmer and used to PyQt that is another matter, and hardly relevent to most users. It is the fact that you had your information incorrect and advised people not to use it that prompted the troll response. Sorry if inaccurate, but your post was not in the best form.

First of all you may be surprised to know that many KDE developers feel it is easier to just use C++ and don't see the logic in Kommander. So you're not alone, you're just not in the majority. The logic with Kommander is you draw your interface and then run your logic in widgets, which is an object oriented type of thinking.

Before answering your question I contend that with PyQt, KJSEmbed or any C++ bindings you have to know what is being done with the classes and architecture of Qt/KDE to effectively use the bindings. I've sat through numerous sessions of developers proudly extolling how accurately they follwed the KDE model. I haven't done much but look at some docs, so maybe you have contrary experience.

To access settings in Kommander with Python you have several ways. Up front though I do admit, it's not what I plan to have in KDE4 where it will be functionaly identical. First off Python has DCOP bindings. The initial parser in Kommander was little more than a DCOP interface. However it's rather limited, but useful if you don't need to do anything fancy, just practical. Using PyQt you can access the QObject. Don't ask me how Python does it, but I know it has many of the types of Qt whereas Kommander is simply text.

So in C++ it would be
const QObjectList * QObject::children () const
This returns a list of children. You should be able to use the interface to QObject, get that list and reference child("isChecked") for instance to see if a checkbox is checked.

The research I've done for this has been related to KDE4 where I understand from my friend Sebastian Sauer who wrote Kross that it is easy to expose virtually every property and slot of an object to any DBUS enabled language.

The paradox is I need people working with those languages to help insure the interface works well for them. The function browser makes coding easy if you just have a vague idea what the functions are, and my objective is to add support for other languages here.

Even in the worst case, if you find all the current methods too difficult, it's quite easy to create a plugin, which will put your functions in the function browser. So for instance even in the KDE3 version one could create a map of functions including the bindings and make native Python function calls for anything Kommander does, and anything C++ does that Kommander does not.

At a base level though, if you are more comfortable typing commands to draw a window than visually drawing it then you are both statistically unusual and not a good prospect for Kommander. Nothing wrong with that.

The point is that Kommander does have extensive docs now, does have an excellent text editor and can be accessed internally with DCOP enabled Python and PyQt. If you were to decide to try it and were interested in helping I'd be happy to work with you on one of our lists to help to make sure Kommander is more useful to more developers. I think your evaluation was out of date, but it's also true that some people have enough difference in their approach as not to be compatible. Kommander was initally modelled after a program called Kaptain, which at first I could not see any use for. It was a paradigm shift for me. If there is a way you and I can make the "big tent" fit what you do that would be great, and if not we both have something we like. ;-)


Eric Laffoon
kdewebdev (Quanta/Kommander) project lead

Reply to this

-
.

 Opposite...

 
 by PaT on: Feb 26 2008
 
Score 50%

Well, just to contradict the claims above, i will take this short moment to thank Mr. Laffoon for his hard work. I've used Kommander on many occasions in the past and always liked it a lot. I can't wait to play with the new features. I also donated 10 bucks right away to help maintain the development of this wonderful piece of software.

Sincerely, ATU (Anti-Troll Unit).

And while i'm here, a little question ;)
Are transparent icons on eg. push buttons looking nicer nowadays? They used to look quite bad. It would be a nice touch to make Kommander scripts look better...


Reply to this

goto page: prev   1  2  3  4  5 

Add commentBack






-
-
Do you like or dislike Ubuntu Unity?
 Yes, unity is alien technology!
 It is less confusing than Gnome 3 default, shell.
 Granny thinks it is much more usable than Gnome 2
 Canonical is embarrasing itself with this split project
 Gnome 3 default shell is much better
 I dislike Unity, Gnome 3 default shell is alien technology!
 None of the above, I like the 2Gb for free and Apple alike behavior. Will post a comment instead

resultmore
 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Apps
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
Events RSS   

Participate
Groups
Forum
Add App
Public API
About KDE-Apps.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2003-2014 KDE-Apps.org Team  
All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.