In this week's KDE Commit-Digest: The menu item styles of the KDE 3 "Classic" menu return to Kickoff. GetHotNewStuff for KDE colour schemes. "Recently Visited" listings in Konqueror. A new simplified hotkeys configuration module. The ability to print a "cheat sheet" of shortcuts. Automation plugin for scheduling checks, and GetHotNewStuff support in KLinkStatus. Support for Synonyms, Antonyms and False Friends in Parley. Improved online play (through GGZ) in KSquares. "Photocopy" functionality in Kooka. Various scripting improvements and integration in Kross and Plasma. Ability to monitor the input and output of processes, and support for pausing and resuming processes in KSysGuard. The ability to scale remote VNC desktops in KRDC. On-the-fly spell checking comes to Kile. Work on a knotify-dbus-plasma bridge. A fullscreen KDE splashscreen, without flicker. Printer-applet (written in Python) replaces KJobViewer. Kubrick and Glimpse move to kdereview. KTip has retired. Various anticipated sanity enhancements to the default settings of a KDE desktop. The bugfix edition KDE 4.0.3 is tagged for release. Read the rest of the Digest here.
Comments
Hi Danny,
thanks for the digest and congrats for these wonderful digests these last two years. I've read them all and it was worth it every time!
Best regards,
Ronald
I hope you don't get tired of hearing the same message time and time again: Thanks Danny!
Much appreciated!
Yes Danny, your work is very much appreciated. Ever since I discovered the commit digest (about a year ago), I look forward to it every week. Amazing how you can create a summary each week from the absolutely immense amount of commits that are done every time. Thanks!
Absolutely. A big thank you to Danny! It is just a pure joy to read Commit Digest every week and getting inspired by all the hard work KDE people do. And happy birthday to CD! It looks like I'm not the only one having a birthday on the same day :)
+1
+2 - incremental adding :D
Now if I add 3, and the next person adds 4, it will grow like n^2.
Sounds like fun.
+4 :D
+5 ;)
Thanks Danny!
+6 (!)
Been a pleasure to read
*7
(n^2 is just too slow, time for n-factorial!)
Seriously, thanks a million, Danny!
Yes, thanks a lot, the digest is always great :-)
+8
*8
Always great to read, thanks! :) As we are in the factorial-function now, we should also include all those KDE-Developers who are commiting..
and the 'SVN Log Message Of The Week' goes to:
Jonathan Riddell: die die ktip, bwahahahah
this should be entered on theDots quotes list to appear in the footer =)
+1
How about this one from Peter Penz:
(must go for breakfast now, otherwise I'll eat my keyboard...).
Love it ;-)
Is KOffice going to use the ribbon interface like MS Office 2007? because that's what the screenshots make it look like. From what I can tell, the ribbon interface isn't the standard of KDE 4, so if it is used in KOffice, it will cause inconsistency.
So far only Kexi uses that kind of ribbon-like interface, the rest of koffice uses different approach in the UI. Let's hope there will be a student for KOffice usability project and bring a nice UI to KOffice.
There even had been a Koffice UI competition on this web site. There was a winner with an interesting concept. Neither I understand why the selected concept will not be implemented, nor I would agree with yet another student project without public control.
a) The koffice ui competion wasn't a student project
b) We have implemented much of Martin's ideas -- and Martin himself is a valued KOffice developer now
c) We have learned a lot in the meantime and have found we could use some expert help
d) Why should anyone care whether you agree to anything or not?
I am sorry. I was completely mistaken. I got the impression someone suggested to "hire" some student who would design his own "personal" optimal UI. This was meant by "public control" - more eyes see more than just a pair of them meaning a winner of a competition would probably follow more advice than "some" student following ust his own plan. I didn't know that the idea origined in the KOffice team to improve the concepts received in the competition. So, please, forget my trolling.
I was referring to this: http://dot.kde.org/1206119837/ ;)
Thanks. I missed that one. ;)
Public control? Who do you think you are to ask the developers to be publically controlled?
Hello,
don't you or anybody else note the uselessness of the argument? KDE is Free Software developed in a public repository. Does that ring something?
KDE makes a point about releasing software before it's ready. Does that ring something?
Why would you even start to think the issue of public vs. non-public exists when KDE is already 100% public all the time?
Yours,
Kay
Well it's called opensource not opendevelopment. The development ist not open to the public.
If you don't believe me try to intgerate a patch in the upcoming 2.6.25 kernel. You will soon understand that not everyone is accepted as developer in a project and that is of course for good reason. So again: It's only the source that is open .
Well it's called opensource not opendevelopment. The development ist not open to the public.
Developement most certainly is open to public view.
Anyone can download a copy of the latest SVN. And file bugs against it.
OTOH, if someone develops something outside of SVN, then it is not open to the public.
Note that even more open development would be an improvement in some cases.
After using KDE 4 from 0.0 to 0.3 I returned to KDE3 and I have to say: Thanks god, it was already time!
Not that KDE4 is horrible, but 4.0 series is so unstable I could not work on it without a Plasma crash, and Plasma was not saving my settings (added plasmoids, geometry, etc), so every time I logged in KDE I had to re-add the plasmoids :-P
So, two questions:
- is there a way to force plasma save? I know that in 4.1 series plasma now save geometry often (there was a bug about this that I've read)
- is there a way to use a dark kicker (much like the one in KDE4) without having to change all colors to deal with a dark background? (I mean having white fonts only in the panel, because black fonts over black is not nice to read).
Thanks in advance, and I'll wait for KDE 4.1.. or 4.2 :-P
1)probably logging out before it crashes...
2)yes there is.search for slim glow on kde-look.org, but for plasma themes that change color, you should wait for 4.1
>1)probably logging out before it crashes...
Yah, and what happens if it crashes IN logout? (that is my case), ehehehhehe.
Just don't log out? ;-)
Yours,
Kay
>1)probably logging out before it crashes...
- Yah, and what happens if it crashes IN logout? (that is my case), ehehehhehe.
>2)2)yes there is.search for slim glow on kde-look.org, but for plasma themes that change color, you should wait for 4.1
- I asked about kicker, not plasma panel :-D
KDE4 doesn't have Kicker.
And what is the title of my post? (back to kde 3.x)
I want to know if there is a way to make kicker look like plasma panel (white fonts on black brackground) without making all windows use this same color scheme.
Configure Panel - Appearance. Not sure you can manage to make it look anything close to Plasma, Kicker was never particularly flexible.
Make a plasma theme... Maybe KDE 4.1 will have color settings for plasma.
Sorry, they are not going to match color with system colors, like Aya theme?
You can fake a BG color for the kicker by specifying an image to use. Getting its fonts to be white without white fonts everywhere else? Well, you could probably change a line or two of code in kicker and compile it.
and laffo at everyone assuming you are talking about the plasma panel in KDE4 :D
I had mine set up with a blank panel (semi-transparent) with white fonts on it. You need to play with the settings but as a general rule go through and turn everything 'transparent' then reduce transparency. That's the only way to get rid of the borders around elements on kicker.
Give KDE4 another go when you get the time. It's settling quickly.
Thanks.
My kde4 installation occasionally crashes on logout too. When it happens I even lose the previously saved plasma-appletsrc file.
When it doesn't crash, it comes back with the right widgets, but the geometry for the taskbar and sytem tray (both in desktop containment, not panel) isn't restored properly.
Just to clarify:
<>is there a way to use a dark kicker in kde3 (much like the plasma panel in KDE4)
hi all
please save kde-forum it is invaded by evil spammers .
friendly
wow that is getting spammed, and moderators seem to be slow in responding to it.
Parsek sounds great.
Konquest is fun for a game or two but it's just too simplistic. I don't expect anything to rival the complexity of Galactic Civilizations II or Master of Orion III (which is actually a pretty good game with current fan patches and mods. Too bad it was a buggy, unplayable monster at release) but a 4X game with a bit more depth would be a great addition for KDE Games. :)
I'm glad you like the idea of Parsek. I also don't plan it will be as complex as GalCiv2 aor MOO3, especially not when it comes to graphics. For now I plan it will just stay a nice 2D client. But there is nothing that prevents the games as complex as Stars!. If you have examine Thousand Parsec a bit you can see it is basically just some protocol made especially for space 4X games. So you can create a ruleset (the actual game rules) as complex (or as simple) as the protocol allows (or will allow in future version). So there should be no problem creating a ruleset similar to Konquest, GalCiv2 or MOO3 or Stars! or any other 4X game. Then I just have to worry to represent all the objects and orders and other stuff from the ruleset properly in the client.
A good strategy game should force the player to decide between a number of trade-offs. If some feature doesn't add trade-offs it doesn't add to depth, it just makes the game more complicated.
Bad example: Weapons in MoO2/3. There was almost always one optimal choice and 20 progressively worse alternatives. Give each type of weapon one niche at which it excels
Good example: Weapons/Shields vs. Stealth/Scanners in MoO3. Normally scanners and cloaks aren't that important but in MoO3 you could easily end up in situations where one side was unable to detect the other and couldn't even fire back.
How they screwed up anyway: The research system meant that normally one side was better in both weapons/shields and stealth/scanners. You had to be careful in fleet composition but a lot of potential was wasted.
In a 4X game the major elements should be
- colonization vs. planetary improvement (i.e. no colony-rush at the beginning of the game where you try to colonize as much as possible and the player who gets the most planets wins. Colonies should be money sinks for some time before becoming profitable and there should be plenty of planetary improvements at the lower tech-levels that can grow your economy just as much)
- tech vs. quantity - kinda related to the first item but in general you should be able to compensate for lack of size by better tech. This means specifically that tech development shouldn't be a linear function of the amount of money you spend. You should be able to make a few choices (perhaps cultural, like the domestic policy sliders in Europa Universalis) a big empire wouldn't wanna make (e.g. less oppressive regime) that compensate for lack of size and even without those there should be diminishing returns on tech spending.
- diplomacy - AI that honors treaties and allies that actually help you in a war
- espionage - You should be able to spend money on establishing a whole organisation in other empires instead of just sending a few assassins. The better your organisation the more you learn about the empire. At the highest level you can see as much information about the other empire as its player. GalCivII had a system like that and it makes espionage actually useful, not to mention much more realistic.
None of this requires much complexity or micromanagement. A Europa Universalis in Space would be nice. =)
I'm gonna have a look at TP rulesets and how much flexibility they provide.
Every single time I use Kdetv with my uvc-based webcam Kdetv doesn't want to exit properly and I must kill the application. Does this happens to me only?
Happens for me too. Submit a bug report! (http://bugs.kde.org/)
UVC is great, and ironically it's largely thanks to Microsoft! Now if only there were an equivalent standard for printers and wifi cards!