Waldo Bastian, the KDE
2.2 release coordinator, has tagged KDE 2.2 for final release. Though
KDE 2.2.0 was scheduled for release today, it has been
slightly delayed to increase stability and speed. The current
schedule is to release KDE 2.2.0 next Monday, August 13. Future plans
include a KDE 2.2.1 bugfix/translation release, scheduled for September
2001. But the main development activity will occur in the KDE 3.0 branch,
which will be based on Qt 3.x and is scheduled for release early next year. Congratulations to all KDE developers for reaching yet another important milestone. Waldo's
announcement follows.
From: Waldo Bastian <[email protected]>
To: [email protected], [email protected], [email protected]
Subject: KDE 2.2 tagged
Date: Sun, 5 Aug 2001 18:26:11 -0700
Hiya,
This is to inform you that the final tagging for KDE 2.2 has taken place.
Changes that, at this moment, do not have the KDE_2_2_RELEASE tag will not be
part of KDE 2.2.
KDE_2_2_BRANCH
For KDE 2.2.1 a KDE_2_2_BRANCH branch has been opened. To update to this
branch use:
cvs update -r KDE_2_2_BRANCH
The KDE 2.2 branch remains frozen, that means that all fixes for KDE 2.2.1
should be posted for review first. The message freeze remains in effect for
this branch as well. The KDE 2.2. branch will be released as KDE 2.2.1 in
about a month from now.
Head
The HEAD branch will become KDE 3.0 and is open for all your hacking
pleasure. The HEAD branch is the cvs branch that you get by default.
If you want your application to be part of KDE 3.0, _THIS_ is a good time to
move it out of kdenonbeta.
As mentioned before, Dirk Mueller will coordinate the KDE 3.0 release.
Thanks
I hereby would like to thank everyone for his or her patience and commitment,
thanks to you KDE 2.2 seems to have become the stable release that we all
wanted it to be.
Thank you very much.
Cheers,
Waldo
--
Andrei Sakharov, Exiled 1980-1986, USSR, http://www.aip.org/history/sakharov/
Dmitry Sklyarov, Detained 2001-????, USA, http://freesklyarov.org/
Comments
Thanks for all the hard work, KDE 2.2 is the best integrated, most comfortable desktop for linux. Looking forward to Three O.
Maarten aka datadevil
I think KFind is the worst application KDE has and it was ignored right from KDE 1.1.
I have complaint many times at bugs.kde.org about KFind's inability to do case insensitve search.
Is it still that bad or improved in KDE 2.2? Or do I wait for KDE 3.0 to get KFind do case insensitive search.
If you don't like it, fix it!-)
Mine can do case insensitive searches.
you are free to use the command line toll called "find" which is imho the underlying engine used by KFind.
feel free to uncheck "case sensitive search"
cu
Mine has a checkbox for case insestivity.
(kde 2.2)
If you dont like it, find another similar tool at www.freshmeat.net. Build one yourself, fix kfind, or use the 'find' command tool.
I find it very bad practice to tell someone "fix it yourself" or "get another tools" or other non-sense when there seems to be a real bug. This will lead to several programs with different bugs. I would much rather have a single bug free program than use 2 or 3 depending on which bug I'm trying to avoid.
If a KDE (or other program) has a flaw we should fess up and fix it.
I would suggest you find the author/maintainer and e-mail them directly. Try to have an exact scenario that fails. If that fails and bugs.kde.org isn't helping I would put something out on one of the more common mailing list, but be sure to mention that you exhausted all other avenues first.
Read the replys above yours. There are at least two that say KFind *does* have a way to do case insensitive searches.
One goes as far as to say "uncheck the 'case sensitive search' box" or something like that.
So: no, contacting the author asking him to do something he already did is not a good idea, and reporting it in bugs.kde.org repeatedly is ot a good idea either.
If you report a bug and it gets closed, see if it fixed. When the bug is closed, there should be an explanation, which may vary ("that's not a bug" or "already implemented in CVS", for example).
If you report a bug, and it gets closed and you don't like the explanation, of you feel it is not a real fix, then probably the developer did not understand your bug report, or what you got is as much as you gonna get.
In either case, reposting the bug is probably useless unless you add new information, or can convince the author of WHY he should do ehat you ask.
Well, you're right that the original poster did something stupid by asking for a feature which obviously is implemented. Thus, say the poster maybe that ha should just open his eyes, bit...
Nevertheless, excuse me that I shout,
PLEASE STOP ANSWERING COMPLAINTS ABOUT SOFTWARE WITH "USE THE SOURCE FIX IT YOURSELF". We are not talking on the Linux developper mailing list!
That's exactly the language used by the people who want Linux (whatever Unix) to stay in their elite coder corner and not in the mainstream. That are the wrong propagandists for KDE, a desktop also for the average and novice user.
I thought that this kind of response was only common on gnotices.
Hi,
actually, that's the way free software works. You have three choices.
a) do it yourself
b) ask nicely if someone's going to do it
c) PAY SOMEONE (like all Windows users do)
actually four:
d) live without it
IMHO: If there is one thing more disgusting than develpers telling users to get productive themselves, then it's (particularly novice) users trying to force some feature down a developer's throat by nagging and bitching about.
Note: I do not say that all users are like that. But some are, and they are not really helping the cause.
-- Jens
> c) PAY SOMEONE (like all Windows users do)
I like this option. Unfortunately there's no very direct way to do it; I suppose emailing the author and asking how much he or she would like to implement that feature, or something. There are also those sites that allow you to post open source jobs and how much you're willing to pay, but I've never been very impressed with their interfaces.
Here's something that might be cool: add a buyfeatures.kde.org or something which allows people to post features or bugfix requests, and how much they are willing to pay. Other users could add their voice to a particular item by offering more money. In order to make it "real", you'd need to have an interface where they enter a credit card number that is validated, so that people don't shirk out of paying.
In fact, I like this idea so much that I'd be willing to build the website, and get my company (which happens to provide online credit card processing) to donate the processing for free. I suspect there may be some legal issues in transfering the money to the proper party, I suppose we'd need to look into this.
What do you guys think, good idea? If so, who should I contact about starting such a project? Perhaps send this post to one or more of the KDE mailing lists?
This sounds like a really good idea, and probably a first dedicated to a purely open souce project. However there are probably more people who will say that they are interested in paying than will actually sign up with their credit card number.
This is a pretty interesting idea. It may be better to move this discussion into a more appropriate forum like one of the KDE lists.
Jason.
I support this idea, and I'm glad to see that others do also. I think people who contribute to free software projects should be rewarded for their work. This is the most equitable way to give monetary rewards to developers that I can think of.
Such a system could be built on top of the bug (and wish) reporting system that currently exists (see bugs.kde.org). People could pledge to pay a small amount of money if wishlist item xxx was implemented. When a bugs.kde.org bug is closed it would indicate a buyfeatures.kde.org feature was implemented.
The main problem I see is that perhaps it is too early for such a system to be implemented. Implementing features can be a lot of work and being offered a small amount of money to implement a difficult feature would be insulting to the developers.
Perhaps it would be better to start with creating a vote-a-wish site, and then later extending it into a site where people could pledge to pay money. There used be a vote-a-wish site and it was very popular but it was closed due to lack of maintenance. Again I think a vote-a-wish site should be tied into the bug tracking system.
Also please note that once money becomes involved suddenly all the fun can dissappear in something. There can be nasty disagreements (eg over whether a wish was really fulfilled) and the type of people attracted to the project could change for the worst.
Having said that I really believe an idea like this could work. Email me if you would like to discuss the most appropriate person to contact etc.
BTW: I'm just speaking for myself here.
> PLEASE STOP ANSWERING COMPLAINTS ABOUT SOFTWARE WITH "USE THE SOURCE FIX IT YOURSELF". We are not talking on the Linux developper mailing list!
> That's exactly the language used by the people who want Linux (whatever Unix) to stay in their elite coder corner and not in the mainstream. That are the wrong propagandists for KDE, a desktop also for the average and novice user.
Elite coder corner? I suppose it might be trendy to attempt to alienate someone who does something for free for you but more likely you are misinterpreting what you are being told. Contrary to what you might think those who develop free software do not have unlimited time and resources to do so. I myself am struggling to clear some business issues to return to the massive learning and working effort of free software development. It would be nice to think that my convictions, efforts and struggles to transform myself into a coder on a level I could be satisfied would not be met with hostility that I was elitist and further had failed to meet your needs.
I suggest you take a little time to read through some of the developer interviews that have been posted here. The main developer on kpresenter is a good example. He learned C++ to follow his vision. At some point in time you must decide if you will contribute to the free software community of merely be a critic.
I can't suggest enough considering the debt we have to those who develop free software. In the end it's not just a matter of price but freedom and extensibility. At some time you're no longer a newie... maybe you'll want to switch off the TV and look at some source code?
FWIW:
revision 1.17
date: 2001/03/28 12:45:58; author: pfeiffer; state: Exp; lines: +11 -6
configuration for case [in]sensitive search,
by Owen Brydon
Obiously this person did not see the check-box for case-insensitive
searches. If they are using a 2.2beta-1 or equiv (what I'm using)
then I'm not sure why they did not see the check-box. However,
they could be using an older version which either does not have the
ability to do case-insensitive searches, or is not easy to find
where to turn off case-sensitive searches.
Instead of slaming this person and telling them to "go and write their own",
try helping them. That type of pissy attitude does no one good, especially
when it is on a official KDE forum -- besides it being a horribly
rude thing to say. Usually the only people I hear saying things like
that, generally are people that use and/or develop-for OSS projects.
I've heard responses of that type in perl, c/c++, mozilla, and gnome irc channels. Please
do not let KDE become like that -- which is one of the reasons I
liked KDE from the beginning. When I went in their channel asking them for help,
I didn't find some asshole bitching at me because I don't know what
they know.
You have to be able to tollerate your users and your fellow users.
Case insensitivy searching has been in KDE *AT LEAST* since 2.1 as it's the version I'm using and it's available there - and *VERY* easy to find, it's a simple checkbox.
Obviously this person did not check for that feature *FOR MONTHS*, nevertheless he started his message with "I think KFind is the worst application KDE has" and, according to his own post, has flooded bugs.kde.org with duplicate feature requests for a feature that probably had already been implemented at this time.
He's one of the persons who don't want to pay for software but want its developers to do what they want - immediately, of course.
To make a feature request is okay but a behaviour like his is simply arrogant and people like don't deserve any better treatment.
Additionally, if you ask me, he's no real person but a troll.
Gunter
PS: I dislike answers like "implement it yourself", too, but I even dislike Ali's behaviour.
Everyone is being critical of the person that posted the question, yet nobody seems to actually be able to READ the question! This person is ASKING if the kfind in version 2.2 has case insensitive search capabilities. If they are asking this, then they obviously haven't tried the 2.2 version.
Not everyone knows how to go about finding out if a feature has been added or a bug has been fixed. I certainly hope that some of you people don't work for actual software development companies, as I'd quickly drop your software product if I got responses such as this. I do work for one, and know that often times people are edgy for one reason or the other, and that simply ignoring this, and answering the question can go a long way. Yes, I understand that the developers aren't getting "paid" in money to write this code. There are other benefits to being an open source coder. If someone writes open source, and is bitter about things like this, then maybe they should stop?
Don't get me wrong, the tone of the original post was unnecessary. But that doesn't excuse the bashing that followed.
Oh, and to answer the question, based purely on other posts in this thread, I would guess that 2.2 has the feature, so no need to wait for 3.0 version.
> asking this, then they obviously haven't tried
> the 2.2 version.
I guess that if he had just asked if this feature is available in KDE 2.2 noone had reacted this way. He would simply have gotten the answer that this feature was available at least since KDE 2.1 and maybe in KDE 2.0, too. I'm not saying that I like the way some people answered the question, I just say Ali could not expect any other reaction. I'm really sure he's just a troll so let's stop that thread.
Gunter
I believe for as long as I've used kfind (1.1 or so) it's done case insensitive searches by unchecking the 'case sensitive' box.
End of question, end of story!
Thank you for all the hard work. KDE 2.2 will be released next week .. cool, more time to fix .. more stable KDE is ...
Don't know if the decision of going to KDE 3.0 early next year is a good idea .. but all the best ..
you did it again .. KDE team ..
YOUR DIED HARD FAN
Tom
I'm not sure about going straight to KDE 3, also. From reading the mailing lists, the idea is to port to QT 3 (which is a good idea), and then sit there for ages because they can keep binary compatibility. The problem is that GCC 3 and GCC 3.1 (which will be out in April 2002) will not be binary compatible. So, as long as KDE 3 comes out after GCC 3.1, everything will be fine.
We rewarded this issue in the discussion. But the point is that Qt 3 is the platform that development outside of KDE is going to move to right away and it solves so many technical problems that given the time GCC needs, we will provide a complete platform that offers everything. If GCC causes an incompatibility lateron, it is mainly the distributions that need to take care of this. Offers of binary packages of third-party KDE applications will be done by them anyway or appear on apps.kde.com for the particular distributions. But sourcecodewise, you can still compile the tarball on any system like before. To really use the gcc 3.1 compiler on a distro for everything, the whole thing needs to be recompiled, not just KDE (which I think wouldn't be a problem either as the distributions usually provide the compiler as a binary, so they will provide re-compiled packages of KDE as well and what else is needed). Someone who compiles gcc himself can be expected to recompile KDE as well IMHO. The advantages of KDE 3 over 2.2 will be so tremendous that for the little number of people that will run into problems with gcc 3.1 because the want to have the latest stuff but are not able to recognise how their system works codewise, they can always join irc.kde.org #kde to ask for advice whats going wrong on their system by then.
Hi Ralf,
Just out of curiousity, what technical problems does porting to Qt3 solve?
Thanks,
Jason.
you will be able to use data-aware widgets and the other cool new stuff in qt3.
What's a data-aware widget?
Jason.
a data-aware widget is a field which 'knows' that that data it contains comes from a database. so when you press the next record button, the field changes to the next record.
This will make building a database frontend much easier.
You will have:
-database support
-component support (see the tutorial from M.Ettrich, other news)
-the styles are components which means pure Qt programs will look like KDE apps
-QSettings works like KConfig that you have a universal way to store settings in Qt apps
-bidirectional language (bidi) support
Ralf
I'm not clear about what you're saying.
Do you mean that GCC 3.0 and 3.1 will not be binary compatible with each other, or are you referring to the fact that 2.95 and 3.0 are binary incompatible?
Also, what versions of KDE are, or will be, able to be compiled with GCC 3.x. I understand that people have experimented with compiling the 2.2 beta under 3.0, but have run into "issues".
Yes, GCC 3.0 and GCC 3.1 will not be completely binary compatible.
Don't you guys ever sleep ? :-P
No. definetly not. Weekends mean 50 hours KDE coding minimum, workdays mean relax after 3am until you finished thinking about the code of the next feature, then implement.
50 hours on weekends? Please quit being such slack bastards. I want my desktop now damnit, and you owe it to us to produce results!
No,seriously, if this is for real, take a vacation! Hell, I bet if you start a PayPal account called the "KDE Vacation Pool" you'd be surprised what you'd get. :)
Cheers,
Jason.
Ralf: what about your preparations for your exams?
Greetings,
Tackat
Nitpicker ;)
damn nitpicker, to be precise. That's my dad's job, not yours :)
Hallo Ariya! Glad to see, that you are still around here. :) Did you get my Email about Netraider? Can't check it now, cause I'm at work.
I hope you are the Ariya that I think you are. ;)
Sorry if not. =)
Yep, who else ? :-P
Who knows, maybe there are a lot of Ariya Hidayat's in the World. ;)
Well, at least Google says it's only me :-P
Amen to that. You guys rock. (not worthy)
it rocks! Thank you, guys. I downloaded & installed the rpm's (not a hacker, haha) and showed it to my wife and said "this is the first real threat to Windows", speakin from a notahacker-point of view. Vamos arriba!
Where did you get the RPMs? I found nothing on ftp.kde.org and other pages...
easy:
go to http://www.kde.org/mirrors.html and pick a mirror, go to "unstable",
then "2.2beta1" (or sth. like that), then choose your distro etc. pp.
For you in Germany here is one of many mirrors:
ftp://ftp.archive.de.uu.net/pub/kde/unstable/2.2beta1/
have a lot of fun... (haha) and you'll see: IT ROCKS!
Stephan
I meant 2.2 final ;)
BTW: The dot.kde.org server seems to have problems (again). It took >10 minutes to load the page...
I think your server is suffering the slashdot effect.
I think your server is suffering the slashdot effect.
easy:
go to http://www.kde.org/mirrors.html and pick a mirror, go to "unstable",
then "2.2beta1" (or sth. like that), then choose your distro etc. pp.
For you in Germany here is one of many mirrors:
ftp://ftp.archive.de.uu.net/pub/kde/unstable/2.2beta1/
have a lot of fun... (haha) and you'll see: IT ROCKS!
Stephan