Description: Kor is an implementation of a desktop workspace, consisting of a desktop window, 'run command' dialog and panel(s). Each component can be disabled, so Kor can be also used for example only as a 'run command' dialog.
Although still under development, it is already usable for users who consider the current feature set sufficient and can handle manual configuration.
Current status (0.3.3): - run command dialog - desktop window - panels - Plasma applets support for panels - native clock applet (more to be done) - image, color and Plasma wallpaper support - config file (no configuration UI) - follows KDE color scheme and widget style - some Plasma applets have various problems that seem to be their bugs, which however do not show with plasma-desktop (workarounds for some cases are included)
See the README file for further details.Last changelog:
0.3.3: - fix wallpaper with Qt raster graphics system 0.3.2: - various Plasma-related fixes and workarounds - non-blocking run command dialog updating - native clock applet 0.2.4: - fixes for panel positioning - configurable panel background color, including transparent - fixed translation support - block desktop splashscreen until panels and wallpaper are ready - worked around problems with some icons not showing in Plasma systemtray applet - fixed background of Plasma applets 0.2.1: - Plasma wallpaper support - workarounds for some Plasma applet bugs 0.2: - basic panels and desktop window 0.1.1: - first public release - run command dialog
you will have to explain the name to me one day...
In any case, I like the idea of Kor as plasma is eating more mem and CPU than I like and LXDE is just too damn ugly :D
Will try it once it builds again (right now broken for 12.1) and will let you know how it went.
Cheers
J
The entry says in depends on KDE4.x, so it indeed does use kdelibs. Plasma libs can are used to optionally load Plasma applets (since there are only few native ones and Plasma ones generally more or less work for me).
Do not listen to critics. When KDE 4.x started, every developer said: "he who writes decides". So it is up to you the author decides.
Is it possible to use with windowmaker, for instance ? I would like to replace plasma and kwin, mainly in a laptop that i cant use both. I would use your software and windowmaker (with its own window manager).
Thanks in advance for the simple yet effective work.
I don't know WindowMaker, so I have no idea. It is not listed among the window managers supporting the EWMH spec, so there might be trouble, but I can't really say more than that you need to try and see.
Well then differences with krunner they seem to be only aesthetic, as krunner can run any command and do much more than that, that's why it is so special :)
Good luck with your project then.
all my respect for your work, but if you feel that krunner is unusable due to its bugs why don't you try to work on them instead of writing a totally new piece of code which has much less capability?
The idea is that
- it just does the job of simply running commands, which I can't quite say about KRunner, as it has a number of annoying problems (granted, those are simply bugs, but nevertheless it's annoying)
- I'm more used to the KDE3 dialog and dislike the fact that the KRunner dialog looks like no other dialog
- I was curious and wanted to try it
- it is simply an alternative
- it is only 0.1.1 (but who says I'm stopping there)
Ratings & Comments
10 Comments
you will have to explain the name to me one day... In any case, I like the idea of Kor as plasma is eating more mem and CPU than I like and LXDE is just too damn ugly :D Will try it once it builds again (right now broken for 12.1) and will let you know how it went. Cheers J
You replace the plasma desktop, the panel and the runner, it's a new DE. Are you using kdelibs or only Qt? And the plasmalibs?
The entry says in depends on KDE4.x, so it indeed does use kdelibs. Plasma libs can are used to optionally load Plasma applets (since there are only few native ones and Plasma ones generally more or less work for me).
Do not listen to critics. When KDE 4.x started, every developer said: "he who writes decides". So it is up to you the author decides. Is it possible to use with windowmaker, for instance ? I would like to replace plasma and kwin, mainly in a laptop that i cant use both. I would use your software and windowmaker (with its own window manager). Thanks in advance for the simple yet effective work.
I don't know WindowMaker, so I have no idea. It is not listed among the window managers supporting the EWMH spec, so there might be trouble, but I can't really say more than that you need to try and see.
Well then differences with krunner they seem to be only aesthetic, as krunner can run any command and do much more than that, that's why it is so special :) Good luck with your project then.
I believe this neverending list of bugs was a rationale for creating something that works. https://bugs.kde.org/buglist.cgi?bug_status=REOPENED&bug_status=NEW&bug_status=ASSIGNED&bug_status=UNCONFIRMED&columnlist=opendate%2Cchangeddate%2Cbug_status%2Cresolution%2Cshort_desc&field-1-0-0=bug_status&field0-0-0=product&field0-0-1=component&field0-0-2=short_desc&field0-0-3=status_whiteboard&field1-0-0=product&field1-0-1=component&field1-0-2=short_desc&field1-0-3=status_whiteboard&query_format=advanced&remaction=&type-1-0-0=anyexact&type0-0-0=substring&type0-0-1=substring&type0-0-2=substring&type0-0-3=substring&type1-0-0=substring&type1-0-1=substring&type1-0-2=substring&type1-0-3=substring&value-1-0-0=REOPENED%2CNEW%2CASSIGNED%2CUNCONFIRMED&value0-0-0=krunner&value0-0-1=krunner&value0-0-2=krunner&value0-0-3=krunner&value1-0-0=crash&value1-0-1=crash&value1-0-2=crash&value1-0-3=crash&order=bugs.creation_ts%2Cbugs.bug_status%2Cbugs.priority%2Cmap_assigned_to.login_name%2Cbugs.bug_id&query_based_on=
all my respect for your work, but if you feel that krunner is unusable due to its bugs why don't you try to work on them instead of writing a totally new piece of code which has much less capability?
which is the advantage of kor over using krunner ? AFAIK you can use karruner to do the same things you mention in the description of kor.
The idea is that - it just does the job of simply running commands, which I can't quite say about KRunner, as it has a number of annoying problems (granted, those are simply bugs, but nevertheless it's annoying) - I'm more used to the KDE3 dialog and dislike the fact that the KRunner dialog looks like no other dialog - I was curious and wanted to try it - it is simply an alternative - it is only 0.1.1 (but who says I'm stopping there)