<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for IT News Today</title>
	<atom:link href="http://www.itnewstoday.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.itnewstoday.com</link>
	<description>A site by an IT enthusiast FOR IT enthusiasts</description>
	<lastBuildDate>Mon, 06 Sep 2010 09:26:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on The War Against Jailbreaking by SHANNON</title>
		<link>http://www.itnewstoday.com/?p=1797&#038;cpage=1#comment-2301</link>
		<dc:creator>SHANNON</dc:creator>
		<pubDate>Mon, 06 Sep 2010 09:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1797#comment-2301</guid>
		<description>&lt;strong&gt;&lt;blockquote&gt;&lt;a href=&quot;http://cheaptabletsonline.com/&quot; rel=&quot;nofollow&quot;&gt;CheapTabletsOnline.Com. Canadian Health&amp;Care.No prescription online pharmacy.Best quality drugs.Special Internet Prices. No prescription drugs. Buy drugs online&lt;/a&gt;...&lt;/strong&gt;

Buy:Maxaman.Viagra Super Force.Viagra Professional.Cialis.Zithromax.Cialis Super Active+.Super Active ED Pack.Cialis Professional.Propecia.VPXL.Viagra Super Active+.Soma.Viagra Soft Tabs.Cialis Soft Tabs.Levitra.Viagra.Tramadol....</description>
		<content:encoded><![CDATA[<p><strong><br />
<blockquote><a href="http://cheaptabletsonline.com/" rel="nofollow">CheapTabletsOnline.Com. Canadian Health&amp;Care.No prescription online pharmacy.Best quality drugs.Special Internet Prices. No prescription drugs. Buy drugs online</a>&#8230;</p></blockquote>
<p></strong></p>
<p>Buy:Maxaman.Viagra Super Force.Viagra Professional.Cialis.Zithromax.Cialis Super Active+.Super Active ED Pack.Cialis Professional.Propecia.VPXL.Viagra Super Active+.Soma.Viagra Soft Tabs.Cialis Soft Tabs.Levitra.Viagra.Tramadol&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE SC 4.5 Falls Short by Volker Bause</title>
		<link>http://www.itnewstoday.com/?p=1803&#038;cpage=1#comment-2297</link>
		<dc:creator>Volker Bause</dc:creator>
		<pubDate>Sat, 04 Sep 2010 12:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1803#comment-2297</guid>
		<description>Just wanted to add some of my own spice.

I am a fairly faithfull OpenSUSE and KDE fan from Namibia. That said, I have recently upgraded to OpenSUSE 11.3 and KDE 4.5+ (Factory). I do use Windows and I have tried most Linux desktops at least once or twice. I don&#039;t like Gnome, a personal preference but I have never bad mouthed it. I prefer OpenSUSE because if it&#039;s tight integration if you may with KDE.

I for one from the beginning credited KDE developers for their decision to leave KDE 3 behind and start on a new road of development which in the long run serves everybody best. I have seen and read many negative views, reviews and finger pointing about KDE 4 developments and seen many appologies been made. While I also had my share of problems with KDE 4.0 (Which I never really used but fully understood why it had to be released), every other upcoming new release has been a fresh breath of air. Running the latest factory release most of the time, I did occasionally suffer negative side effects which required some intervention on my behalf, but which admitadly, comes with the territory (i.e. If you run factory,non stable or edge cutting versions or technology). I can fully appreciate those users who don&#039;t think or believe KDE 4 is up to standard with what KDE 3 had to offer but to be fair, it has many features KDE 3 never had. With that I am the last to say it is perfect. Perfection needs time. That said, a lot of features do still need to be re-implemented. 

Developing a new desktop is a tradeof between the implementation of new features, re-implementation of old features, performance and stability and a lot of time and effort to achieve this

Desktop developers need to be much more inovative than appliacation developers, something the KDE team definately is. A lot of new concepts, ideas and technologies need to be developed and tested. Not every idea or technology will be accepted. The development of a new desktop should be compared to the evolution of species (i.e. Species representing a new breed of Desktop Environment) 

Personally I can vouch that I am more than satisfied with what Novell and KDE have to offer and stability issues have been minimal and can mostly be contributed to lack of experience, knowledge and running factory versions on my part. KDE has been developing with leaps and bounds. 

Personally I use computers with Intel and Nvidia graphics cards and have very few problems besides those that may be experience  during an upgradeor implementation of new technologies. Each have had their own share of problems which in my case have been minimal, considering other products I have used (i.e. Microsoft Windows). If you want a 100% stable desktop, by all means stay with KDE 3 but don&#039;t talk badly about the efforts of developers. Give credit where it is due and if you don&#039;t like something, make a note of what you don&#039;t like and even better, make some suggestions as to how things could be improved upon.  Nobody and therefore nothing is perfect. I was brought up to believe that if you cannot say something good, rather say nothing. Doing so may come back to bite you in the back as is evident though some of the posts. It is much easier to say negative things than to acknowldge and speak about things that are positive. People tend to remember the negative things we hear or say. If you want Linux and OpenSource technologies to triumph, speak possitive and even better try to contribute.

From my perspective, I give thumbs up to all Linux and OpenSoucre developers and from my own experience, thumbs up for KDE and Novell. In my books you are doing a good job even if I think a lot of progress still needs to be made. I can fully acknowledge your achievements in the last 5 years or so and admire your quest to make Linux one of the most popular operating systems around. I can confirm that KDE 4.5 in my case is more stable and I am eagerly looking forward to what KDE 4.6 has to offer.</description>
		<content:encoded><![CDATA[<p>Just wanted to add some of my own spice.</p>
<p>I am a fairly faithfull OpenSUSE and KDE fan from Namibia. That said, I have recently upgraded to OpenSUSE 11.3 and KDE 4.5+ (Factory). I do use Windows and I have tried most Linux desktops at least once or twice. I don&#8217;t like Gnome, a personal preference but I have never bad mouthed it. I prefer OpenSUSE because if it&#8217;s tight integration if you may with KDE.</p>
<p>I for one from the beginning credited KDE developers for their decision to leave KDE 3 behind and start on a new road of development which in the long run serves everybody best. I have seen and read many negative views, reviews and finger pointing about KDE 4 developments and seen many appologies been made. While I also had my share of problems with KDE 4.0 (Which I never really used but fully understood why it had to be released), every other upcoming new release has been a fresh breath of air. Running the latest factory release most of the time, I did occasionally suffer negative side effects which required some intervention on my behalf, but which admitadly, comes with the territory (i.e. If you run factory,non stable or edge cutting versions or technology). I can fully appreciate those users who don&#8217;t think or believe KDE 4 is up to standard with what KDE 3 had to offer but to be fair, it has many features KDE 3 never had. With that I am the last to say it is perfect. Perfection needs time. That said, a lot of features do still need to be re-implemented. </p>
<p>Developing a new desktop is a tradeof between the implementation of new features, re-implementation of old features, performance and stability and a lot of time and effort to achieve this</p>
<p>Desktop developers need to be much more inovative than appliacation developers, something the KDE team definately is. A lot of new concepts, ideas and technologies need to be developed and tested. Not every idea or technology will be accepted. The development of a new desktop should be compared to the evolution of species (i.e. Species representing a new breed of Desktop Environment) </p>
<p>Personally I can vouch that I am more than satisfied with what Novell and KDE have to offer and stability issues have been minimal and can mostly be contributed to lack of experience, knowledge and running factory versions on my part. KDE has been developing with leaps and bounds. </p>
<p>Personally I use computers with Intel and Nvidia graphics cards and have very few problems besides those that may be experience  during an upgradeor implementation of new technologies. Each have had their own share of problems which in my case have been minimal, considering other products I have used (i.e. Microsoft Windows). If you want a 100% stable desktop, by all means stay with KDE 3 but don&#8217;t talk badly about the efforts of developers. Give credit where it is due and if you don&#8217;t like something, make a note of what you don&#8217;t like and even better, make some suggestions as to how things could be improved upon.  Nobody and therefore nothing is perfect. I was brought up to believe that if you cannot say something good, rather say nothing. Doing so may come back to bite you in the back as is evident though some of the posts. It is much easier to say negative things than to acknowldge and speak about things that are positive. People tend to remember the negative things we hear or say. If you want Linux and OpenSource technologies to triumph, speak possitive and even better try to contribute.</p>
<p>From my perspective, I give thumbs up to all Linux and OpenSoucre developers and from my own experience, thumbs up for KDE and Novell. In my books you are doing a good job even if I think a lot of progress still needs to be made. I can fully acknowledge your achievements in the last 5 years or so and admire your quest to make Linux one of the most popular operating systems around. I can confirm that KDE 4.5 in my case is more stable and I am eagerly looking forward to what KDE 4.6 has to offer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE SC 4.5 Falls Short by Jeremy</title>
		<link>http://www.itnewstoday.com/?p=1803&#038;cpage=1#comment-2293</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Thu, 02 Sep 2010 23:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1803#comment-2293</guid>
		<description>That trick does fix it, but I&#039;ve found it messes up the performance of my non-KDE games too.</description>
		<content:encoded><![CDATA[<p>That trick does fix it, but I&#8217;ve found it messes up the performance of my non-KDE games too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE SC 4.5 Falls Short by Jeremy</title>
		<link>http://www.itnewstoday.com/?p=1803&#038;cpage=1#comment-2292</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Thu, 02 Sep 2010 23:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1803#comment-2292</guid>
		<description>Reread my previous comments, as we&#039;re just running in circles. I stand behind my review. I did just as much research as is required for a review. KDE 4.4 works, KDE 4.5 doesn&#039;t. I troubleshooted my laptop, and found it&#039;s not the issue. I could restore my KDE 4.4 clonezilla image and upgrade to 4.5 an infinite number of times, it&#039;s not corrupted packages. It just doesn&#039;t work.

You cannot possibly expect a good review for KDE 4.5 when there are so many problems.</description>
		<content:encoded><![CDATA[<p>Reread my previous comments, as we&#8217;re just running in circles. I stand behind my review. I did just as much research as is required for a review. KDE 4.4 works, KDE 4.5 doesn&#8217;t. I troubleshooted my laptop, and found it&#8217;s not the issue. I could restore my KDE 4.4 clonezilla image and upgrade to 4.5 an infinite number of times, it&#8217;s not corrupted packages. It just doesn&#8217;t work.</p>
<p>You cannot possibly expect a good review for KDE 4.5 when there are so many problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE SC 4.5 Falls Short by Jeremy</title>
		<link>http://www.itnewstoday.com/?p=1803&#038;cpage=1#comment-2291</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Thu, 02 Sep 2010 23:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1803#comment-2291</guid>
		<description>&quot;Actually, I do that when someone gets it horribly, horribly wrong. It’s fine to criticize publicly, but when you do so you are committing yourself to also getting it right. When you spread misinformation in entries like that many people read, and usually trust as having been researched and written from a knowledgeable position, it’s a massive and unearned disservice.&quot;

Actually Aaron, what I&#039;ve noticed from you speaks differently. Every article I&#039;ve ever read on Linux Today and several other sites that speaks ill of KDE, you always follow with a page full of text and going off on a tirade. I can pretty much set my watch to it. I read a negative KDE article, and then I keep refreshing throughout the day because I know it&#039;s going to happen, and it always does. It could very well be a coincidence that you and I are reading the same articles, but it is what I&#039;ve noticed. I think that you should instead take what your users and reviewers say into consideration. You may not agree with most of them, but they _are_ your users, so you should at least try to compromise a bit rather than go off with the &quot;you&#039;re either with us or against us&quot; attitude I&#039;ve seen from you on several blogs.

&quot;In writing this piece you failed to do any real fact checking and decided to write a piece that really isn’t laced with much in the way of accuracy or balance. &quot;

What I said was completely accurate. KDE 4.4 works fine, and KDE 4.5 does not on my laptop, and a bunch of other peoples machines too. What more research is required? It doesn&#039;t matter what inside of KDE is the problem, the fact is that there is a problem and that is all I need to focus on, and all any reviewer would focus on. I of course made sure the problem wasn&#039;t my laptop (I have a KDE 4.4 Clonezilla image I can restore at will and double and even triple test) so as a reviewer, nothing else matters.

&quot;You are completely free to exercise your right to free speech and write poorly researched articles. I am also completely free to exercise my right to free speech and point out that your article is poorly researched.&quot;

Again, I did all the research that a review requires. KDE 4.4 works, KDE 4.5 doesn&#039;t. I troubleshooted my laptop and made sure it&#039;s not defective. No further research is required during a review, unless I was a developer, then I&#039;d be expected to know where in the code is the cause of the problem.

&quot;In the very blog entry by KWin developer Martin that you link to he explains with great detail that isn’t “some drivers don’t support those features” but that “some drivers lie about supporting those features”.&quot;

While I agree that drivers lying about what they support is bad, they are still drivers in our current day and age your software is forced to have to run on. You guys are deciding to just do what you want to do regardless of what might break and then blaming it on the drivers. While I do agree that from what I read the drivers are to blame, it does not change my opinion. Actually, it strengthens it. The drivers suck now days, I understand that, but it&#039;s no excuse. This is the technology that we have right now, and you have users that are expecting stable releases to in fact be stable releases. I understood perfectly when you guys released an unfinished KDE 4.0, but I didn&#039;t complain. Why? Because KDE 3.5.x was still being maintained and I understood the direction. KDE 3.5 is abandoned now, KDE 4.x is all us KDE users have. We expect it to work, because not all of your users are comfortable diving into the code and tweaking it until normal usability is restored. You guys have to work with what you have access too. I hope the drivers get fixed, but they&#039;re not fixed right now.

&quot;Again, reading Martin’s blog, which you linked to, it is evident this isn’t a case. Such misrepresentation is despicable.&quot;

Let&#039;s look at the facts. The problems mentioned in the blog were found during KDE 4.5&#039;s beta phase. The problems still exist in the stable version. The blog mentions possible downfalls of using the new filters. Therefore, it&#039;s a fact that it was a known issue and that the filters knowingly broke the release. Misrepresentation is not what it is at all, it&#039;s a truth you probably don&#039;t want made public.</description>
		<content:encoded><![CDATA[<p>&#8220;Actually, I do that when someone gets it horribly, horribly wrong. It’s fine to criticize publicly, but when you do so you are committing yourself to also getting it right. When you spread misinformation in entries like that many people read, and usually trust as having been researched and written from a knowledgeable position, it’s a massive and unearned disservice.&#8221;</p>
<p>Actually Aaron, what I&#8217;ve noticed from you speaks differently. Every article I&#8217;ve ever read on Linux Today and several other sites that speaks ill of KDE, you always follow with a page full of text and going off on a tirade. I can pretty much set my watch to it. I read a negative KDE article, and then I keep refreshing throughout the day because I know it&#8217;s going to happen, and it always does. It could very well be a coincidence that you and I are reading the same articles, but it is what I&#8217;ve noticed. I think that you should instead take what your users and reviewers say into consideration. You may not agree with most of them, but they _are_ your users, so you should at least try to compromise a bit rather than go off with the &#8220;you&#8217;re either with us or against us&#8221; attitude I&#8217;ve seen from you on several blogs.</p>
<p>&#8220;In writing this piece you failed to do any real fact checking and decided to write a piece that really isn’t laced with much in the way of accuracy or balance. &#8221;</p>
<p>What I said was completely accurate. KDE 4.4 works fine, and KDE 4.5 does not on my laptop, and a bunch of other peoples machines too. What more research is required? It doesn&#8217;t matter what inside of KDE is the problem, the fact is that there is a problem and that is all I need to focus on, and all any reviewer would focus on. I of course made sure the problem wasn&#8217;t my laptop (I have a KDE 4.4 Clonezilla image I can restore at will and double and even triple test) so as a reviewer, nothing else matters.</p>
<p>&#8220;You are completely free to exercise your right to free speech and write poorly researched articles. I am also completely free to exercise my right to free speech and point out that your article is poorly researched.&#8221;</p>
<p>Again, I did all the research that a review requires. KDE 4.4 works, KDE 4.5 doesn&#8217;t. I troubleshooted my laptop and made sure it&#8217;s not defective. No further research is required during a review, unless I was a developer, then I&#8217;d be expected to know where in the code is the cause of the problem.</p>
<p>&#8220;In the very blog entry by KWin developer Martin that you link to he explains with great detail that isn’t “some drivers don’t support those features” but that “some drivers lie about supporting those features”.&#8221;</p>
<p>While I agree that drivers lying about what they support is bad, they are still drivers in our current day and age your software is forced to have to run on. You guys are deciding to just do what you want to do regardless of what might break and then blaming it on the drivers. While I do agree that from what I read the drivers are to blame, it does not change my opinion. Actually, it strengthens it. The drivers suck now days, I understand that, but it&#8217;s no excuse. This is the technology that we have right now, and you have users that are expecting stable releases to in fact be stable releases. I understood perfectly when you guys released an unfinished KDE 4.0, but I didn&#8217;t complain. Why? Because KDE 3.5.x was still being maintained and I understood the direction. KDE 3.5 is abandoned now, KDE 4.x is all us KDE users have. We expect it to work, because not all of your users are comfortable diving into the code and tweaking it until normal usability is restored. You guys have to work with what you have access too. I hope the drivers get fixed, but they&#8217;re not fixed right now.</p>
<p>&#8220;Again, reading Martin’s blog, which you linked to, it is evident this isn’t a case. Such misrepresentation is despicable.&#8221;</p>
<p>Let&#8217;s look at the facts. The problems mentioned in the blog were found during KDE 4.5&#8242;s beta phase. The problems still exist in the stable version. The blog mentions possible downfalls of using the new filters. Therefore, it&#8217;s a fact that it was a known issue and that the filters knowingly broke the release. Misrepresentation is not what it is at all, it&#8217;s a truth you probably don&#8217;t want made public.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE SC 4.5 Falls Short by TheBlackCat</title>
		<link>http://www.itnewstoday.com/?p=1803&#038;cpage=1#comment-2290</link>
		<dc:creator>TheBlackCat</dc:creator>
		<pubDate>Thu, 02 Sep 2010 23:11:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1803#comment-2290</guid>
		<description>That would make be true if there was nothing else for them to work on, but seeing as there was a lot on their plate they didn&#039;t have time.</description>
		<content:encoded><![CDATA[<p>That would make be true if there was nothing else for them to work on, but seeing as there was a lot on their plate they didn&#8217;t have time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE SC 4.5 Falls Short by Jeremy</title>
		<link>http://www.itnewstoday.com/?p=1803&#038;cpage=1#comment-2289</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Thu, 02 Sep 2010 22:59:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1803#comment-2289</guid>
		<description>How does giving us an option to restore the feature take six months? Please explain. I find it hard to believe that in the same amount of time it took to add the arrow icon and remove the &#039;on hover&#039;, you guys couldn&#039;t have coded a simple check box and an if statement. You and the rest of the KDE developers are way too skilled for me to accept that statement.</description>
		<content:encoded><![CDATA[<p>How does giving us an option to restore the feature take six months? Please explain. I find it hard to believe that in the same amount of time it took to add the arrow icon and remove the &#8216;on hover&#8217;, you guys couldn&#8217;t have coded a simple check box and an if statement. You and the rest of the KDE developers are way too skilled for me to accept that statement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE SC 4.5 Falls Short by TheBlackCat</title>
		<link>http://www.itnewstoday.com/?p=1803&#038;cpage=1#comment-2288</link>
		<dc:creator>TheBlackCat</dc:creator>
		<pubDate>Thu, 02 Sep 2010 22:59:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1803#comment-2288</guid>
		<description>Wow.  I&#039;ve seen a number of complaints about removing the feature, but every one has agreed it was the right decision once people explained to them all the trouble others were having with the feature.  They all looked forward to having an option, but so far you are the first to suggest we should have just let all the people who were having serious problems with that feature suffer just so you could save a button a click.</description>
		<content:encoded><![CDATA[<p>Wow.  I&#8217;ve seen a number of complaints about removing the feature, but every one has agreed it was the right decision once people explained to them all the trouble others were having with the feature.  They all looked forward to having an option, but so far you are the first to suggest we should have just let all the people who were having serious problems with that feature suffer just so you could save a button a click.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE SC 4.5 Falls Short by TheBlackCat</title>
		<link>http://www.itnewstoday.com/?p=1803&#038;cpage=1#comment-2286</link>
		<dc:creator>TheBlackCat</dc:creator>
		<pubDate>Thu, 02 Sep 2010 22:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.itnewstoday.com/?p=1803#comment-2286</guid>
		<description>I am the one who implemented that feature.  The reason I did so is because the dialog was horribly broken in my opinion: there was no option at all for &quot;rename all&quot; in the old dialog.  It made it essentially infeasible to copy large numbers of files without deleting or skipping duplicates, especially considering every file you wanted to rename required two button presses at opposite ends of a long, dynamically-resizing dialog (suggest and rename).  

Yeah, we could have added yet another button, but that would have ended up with 6 buttons in a row.  The original 5 buttons was already too complicated, considering half of them are totally redundant.  It would also make things harder to interpret, since it would be unclear what, if anything, the &quot;suggest&quot; button or file name field would do in the &quot;rename all&quot; case&quot;.

So yes, I made the dialog two clicks instead of one for overwriting or skipping, in exchange for reduce the number of clicks during a renaming operation from potentially thousands or more down to two.  I thought making certain operations take one more click was worth it when it saved at least that many (and potentially orders of magnitude more) for another operations and made the dialog much quicker and easier to interpret.  The KDE developers agreed.

So my options were: make an already really complicated dialog with a bunch of redundant buttons even more complicated, continue to make life really difficult for people who don&#039;t want to delete their files, or do what I did.  I had nothing but positive feedback from everyone who looked at the idea (both developers and users), no one expressed any concern with adding another button press since they all thought the benefits far outweighed the detriments.

I should add that I am NOT a KDE developer, I am a user, but after my bug report on the subject sat there for several years I decided to do it myself.

But you can&#039;t please everyone.  At least this way something that was impossible is now possible.</description>
		<content:encoded><![CDATA[<p>I am the one who implemented that feature.  The reason I did so is because the dialog was horribly broken in my opinion: there was no option at all for &#8220;rename all&#8221; in the old dialog.  It made it essentially infeasible to copy large numbers of files without deleting or skipping duplicates, especially considering every file you wanted to rename required two button presses at opposite ends of a long, dynamically-resizing dialog (suggest and rename).  </p>
<p>Yeah, we could have added yet another button, but that would have ended up with 6 buttons in a row.  The original 5 buttons was already too complicated, considering half of them are totally redundant.  It would also make things harder to interpret, since it would be unclear what, if anything, the &#8220;suggest&#8221; button or file name field would do in the &#8220;rename all&#8221; case&#8221;.</p>
<p>So yes, I made the dialog two clicks instead of one for overwriting or skipping, in exchange for reduce the number of clicks during a renaming operation from potentially thousands or more down to two.  I thought making certain operations take one more click was worth it when it saved at least that many (and potentially orders of magnitude more) for another operations and made the dialog much quicker and easier to interpret.  The KDE developers agreed.</p>
<p>So my options were: make an already really complicated dialog with a bunch of redundant buttons even more complicated, continue to make life really difficult for people who don&#8217;t want to delete their files, or do what I did.  I had nothing but positive feedback from everyone who looked at the idea (both developers and users), no one expressed any concern with adding another button press since they all thought the benefits far outweighed the detriments.</p>
<p>I should add that I am NOT a KDE developer, I am a user, but after my bug report on the subject sat there for several years I decided to do it myself.</p>
<p>But you can&#8217;t please everyone.  At least this way something that was impossible is now possible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
