Slashdot Mirror
KDE 2.2 Tagged
ByTor-2112 writes "According to dot.kde.org, KDE 2.2 has been tagged out. Awesome." Plans were originally to release 2.2 today, but scheduled release is now next Monday, to allow some time for more stability/speed work. 2.2 rocks my world. Excellent work on the part of all the KDE developers. Other dates mentioned are 2.2.1 in September, and opening work up on 3.0, which will hopefully come out at the beginning of 2002.
Great. I'm very glad to see that KDE is making headway. (Now if they'd just fix the minor security hole in their screensavers...) I'll be upgrading my Linux desktop for 2.2 pretty soon.
I just wish installing KDE on Solaris was as simple. Non-Linux situations just don't receive as much attention as they need to if KDE is really going to live up to its cross-platform promise. I've converted some of my Solaris users to KDE on the strength of the 1.1.2 release alone; if I can give them 2.2 on the SPARCs as soon as it appears on the x86s, I'll have won them over, I think. :-)
(They really like browsing the contents of a tar file in Konqueror. But they still laugh when the "system information" screen complains that it can't find the IRQs in use, or the game controllers, or any of the other all-the-world's-a-PC things. Enh, it's a start...)
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
You simply must spend time diggin through all that 2.2 offers before offering an opinion on it. The depth of available features are astounding.
:-)
For example, I *love* how finegrained Konqueror's support for cookie and javascript is. You can specify particular sites that allowed to run javascript, to the exculsion of all others.
Kasbar, the newly spiffed up task switcher, pop up a scaled down screenshot of the app whose icon your mouse is hovering over. This makes it WAY easier to pick the web browser windows you REALLY meant.
Konqueror's support for file-data-as-the-icon has truly matured. It renders text, html, pics, postscript and pdf, alphablending in the normal icon underneath the data. Sweet and really effective for me.
KMail gives surprising good control of mail. Some of the options make procmail unecessary, except for really advanced stuff. ANd it supports IMAP now.
Konsole may be a bit bulky for a shell, but I love having a menu listing all my nachines on the network, giving me one click ssh to them, all in one manageable window.
How many times have you seen a newbie click the icon to launch a program, get tired of waiting for it to come up, and click it again? Of course, two copies get launched, confusing the user. Well, KDE now "attaches" the 16x16 icon of th program you asked to launch to the mouse cursor, throbbing gently until the app comes up. this gives *useful* feedback to the user. Not only does it tell them that something is happening(which an hourglass can do), but it tells them what is being launched, boosting their confidence.
The kicker can now take up less than the full screen. The default is not to have a handle on the left, making good use of Fitt's law; slam the mouse to the lower left and you are *sure* to get the Start Menu when you click.
KDE is full of wonderful touches. Keep digging, you'll be pleasantly surprised, constantly
poor little dot server. it goes down for like a week or something, and now it's being slashdotted.
maybe they should switch to an IIS server
if you think that was anything other than a joke, kill yourself; you're stealing my oxygen
We dance to all the wrong songs.
--Refused.
I really really am. I use GNOME and have virtually ignored KDE with extreme prejudice. I know it is rather small-minded of me but at least I admit it.
I love the progress that KDE has been making. It has been steady and strong. I love the sane orderly and approach that KDE has taken from the beginning.
Originally, I hated KDE because of the non GPL issue. Now that is resolved. Next I hated it because it lacked nice eye candy. There have been terrific improvements in the theming department though there is more to go before it wins me over. I still don't like the lack of choice in window managers but I'm having second thoughts on that position since by only having one WM, more uniform configurability is possible.
I still hate that seemingly everything has an inappropriate use of "K" in there somewhere. Of course GNOME stuff is prone to the same problem, but you have to understand, I'm in the U.S. and it reminds us of K-Mart... bleah... white trash... too much associative crap associated with "K" words.
Just the other day I was wishing KDE and GNOME would just merge.
And where is GNOME's promised 2.0 release!?!? I'm getting seriously disillusioned. I think when I install this RedHat 7.2(beta) I'll give KDE a try... nothing new for me to see with the GNOME 1.4 there anyway.
Damnit Miguel?!?! What happened to the enthusiasm and momentum?! Put your marketting hat on!
This sort of short update schedule, etc. is great. I've always like that about OpenBSD (new version every 6 months) and if I remember correctly, Linus had made comments about trying to get the Kernel on that type of track as well.
Fewer "massive" changes that take 2 years to complete and more "evolutionary" style.
Whatever happened to that idea? (Officially)
Learning HOW to think is more important than learning WHAT to think.
Great timing with this release. I figure by the time my infant gets into college, this'll show up in Debian stable.
(Blah, blah, blah. I use Progeny. Now go away Debian flamers, it's a joke.)
Jesus was all right but his disciples were thick and ordinary. -John Lennon
For more information on KDE, the release and support for 2.2, please visit irc.openprojects.net #kde-users. For anyone interested in the development path that we'll be taking in the future, discussions about that will happen on the mailing lists (lists.kde.org) and #kde. Please do not fill #kde with support related questions... go to #kde-users for that if possible. Thanks, and enjoy the release. Troy Unrau troy@kde.org
I can't find any. Can someone relpy with some links for all?
Thanks.
I like c++ alot. I just think the fsf version of it really sucks. I love tail-recursion and the way c++ does handles. I believe oop can really make gui development faster and more bug-free if its done right. I hate gnome's c++ like hack written in c.
Anyway the orignally arguement why c was the defacto standard in gnome and not c++ was that g++ was mediocre and sucked really bad on anything non-intel. The other one was that comprises in the core QT libraries had to be made so it could compile under g++. This slowed kde down quite alot. I know alot of c die hards like to blame c++ on this but I believe its due to limitation in the g++ compiler. I noticed some code really runs fast on Visual c++ and runs slower and is more bloated on linux with gcc. Anyway I would love to see faster load times on kde3.0.
Do any of you know if the new compiler can help make kde3.0 run better?
http://saveie6.com/
KDE 3.0 will basically be what you would imagine KDE 2.3 would be (i.e. no world shaking new changes), but ported to QT 3. This will enable much better handling of 'foreign' languages, and a rewritten styling/themeing engine, plus other extras (data aware widgets for example).
-- Help Digitise the Public Domain at DP.
The only reason that the GNOME core won't be bonoboized is if there isn't enough time before the freeze to do it in. (The GNOME guys are really serious about getting the release out in a timely fashion, they set an early freeze date of July 31 and limited the feature set due to that.) Havoc never had any objections to the GNOME core being bonoboized, the argument was about his library (GConf) being replaced for GNOME 2.0 without his knowledge. The gnome-core maintainers have always planned on bonoboizing the panel (Vertigo), nautilus already uses bonobo, and the control-center is moving away from any embedding mechanism, which was a joint decision with both the Ximian guys (Chema, Zaphod) and Havoc.
Sorry for drifting so far off-topic...
Yeah, like everybody's favorite compiler... It stalled for a year or so due to political arguments, hence the EGCS fork. After the FSF formally handed control of GCC to EGCS, the team got the 2.95 series out the door... but it still took forever to get 3.0 released. Afterwards, everybody sat down and said, "Okay, now that that's done, what could be improved?" and the result is the new development plan. The 3.0.1 code should be freezing in another ten days or so.
I suspect that this is just part of the growth of projects. A massive growth spurt (fast development) followed by a slowing and ossifying, followed by a clean-out-the-crap cycle which leads to a growth spurt...
You realize that can mean anything you want it to mean, right? It's way too vague of a term.
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
I just wish installing KDE on Solaris was as simple.
PatriotSoft makes Solaris 8 KDE packages. Only catch is they replace Sun's dtgreet logo with their own but that is easily fixed. We have been using their KDE 1.x package in production where I work for 1.5 years now. The KDE 2.x stuff seems to have problems when you logon on graphically more than once but that might be fixed now (run the control panel while logged in twice but only on a box no one cares about).
You can get the packages at: ftp://ftp.patriots.net/pub/solaris_packages/8-Spar c/KDE/
-- Argel
Give a man a fish and he'll eat for a day. Teach a man to fish and he'll get hit by a nuclear submarine.
-- Argel
You forgot at least one step. You do have the person read and understand the Makefile, right? I mean, you don't really expect them to "make install" without checking out what is going to happen first. Especially when it's a Makefile that's was stored remotely! Actually, you do mention "make -n" but only to see what's going on when things break.
The reality is that there is a certain level of trust involved in downloading and installing software. If a black hat wants to replace some well known installation package with a trojan, it doesn't really matter whether it's being installed via "lynx -source | sh" or "configure && make && make install". Some people will download the go-gnome.com script and check it out. Most won't. Some people look at Makefile's before they "make install". Most don't. make is just as powerful a scripting language as sh, so it's not like one is "safer" to run as root than another. I agree that it certainly feels as though one is safer than the other, but if you think about it for a little bit, they are basically equivalent. Actually, it's easy to prove that they are equivalent. A Makefile can execute any arbitrary shell script that happens to have been downloaded with the tarball. A shell script can include a Makefile which it saves and make's. Any task which can be performed with one can be performed with the other!
In the end, the go-gnome.com trick is a really easy way to bootstrap yourself into having Gnome running. It's something that anybody can run. And yes, they are putting a lot of trust in the source of the shell script. Just like they would be doing if they downloaded tarballs and compiled them. Two paths to the same place with equivalent risk levels. The difference is, a newbie user might get one of them to work. Unless things have changed drastically, trying to compile Gnome from scratch is a challenge even if you have a lot of Linux experience. Last time I tried it, I ended up chasing down to about third-order dependencies before giving up. I don't think a Linux newbie has a chance in hell of compiling Gnome from scratch.
Umm, not exactly a FUD...
;)
Here is an example - at my previous work I had to install them some sort of developer enviroment for the developers - and since I use personally KDE all the time - I thought, what the heck - and installed KDE 2.1 and KDevelop...
All the developers loved it. Just the CEO asked me where did I get a version of Visual Studio for Linux and do we have license for this. Guess what my answer was...
I've seen it on lots of cases, talking to commercial companies who develop some Linux solutions. Most of them use KDevelop even for developing kernel modules!...
Hetz (Heunique)