<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knode on RESEARCHUT</title><link>https://researchut.com/tags/knode/</link><description>Recent content in Knode on RESEARCHUT</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>rrs@researchut.com (Ritesh Raj Sarraf)</managingEditor><webMaster>rrs@researchut.com (Ritesh Raj Sarraf)</webMaster><lastBuildDate>Sun, 07 Nov 2010 12:46:00 -0500</lastBuildDate><atom:link href="https://researchut.com/tags/knode/index.xml" rel="self" type="application/rss+xml"/><item><title>Icedove</title><link>https://researchut.com/post/5/</link><pubDate>Sun, 07 Nov 2010 12:46:00 -0500</pubDate><author>rrs@researchut.com (Ritesh Raj Sarraf)</author><guid>https://researchut.com/post/5/</guid><description>&lt;p>My recent experience with Mozilla ThuderBird, IceDove.&lt;/p>
&lt;p>With KDE 4.x, the KDE team took a radical step of ripping apart most of the
stuff and rethinking many of the designs. Quite a bold move. Many people
appreciated KDE&amp;rsquo;s efforts to start afresh while others moved away from KDE.
For some reasons, I decided to stick to KDE. Maybe it was because of the
awesome flexibility KDE provided provides to customize the DE to one&amp;rsquo;s
personal taste. Or maybe because I was too used to the KDE way of doing
things. I stayed with KDE while 4.0 was released and stayed with it up till
very recently.&lt;/p>
&lt;p>I started to lose my patience with the PIM Suite. I know the PIM team is also
going to some very radical changes which will bring very innovative stuff
later. But, at the moment, the KDE PIM suite is very broken. Broken not in the
first impress, but broken when you regularly use it. It leaks memory like
anything and keeps doing lots and lots of I/O. I hope some day the KDE team
decides that they do need a &lt;strong>core team&lt;/strong> , a core team that could take care
of important tasks, making sure that the imporatant tasks are &lt;strong>Continuously
Usable&lt;/strong>. It takes time to earn the reputation but it takes a lot lesser time
to lose it.&lt;/p>
&lt;p>Anyways, having been a KDE (PIM) user for long, I had been bearing the PIM
torments up until, I recently saw a colleague using IceDove. There was a time
when the Mozilla suite was in itself terribly slow. But things seem to have
changed a lot. Both, the browser and the PIM suite, have improved a lot lot in
terms of functionality and performance. Performance is very important. What
good is a feature if its performance is terrible and it hinders the usability.
Some of the things that really impressed me were:&lt;/p>
&lt;ul>
&lt;li>Indexing&lt;/li>
&lt;li>Organization&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Indexing&lt;/strong> : Nepomuk might be good one day but that day is yet to be seen. I
patiently wait for that day to come. Well, don&amp;rsquo;t have much choice. Have been
patiently waiting for it since KDE 4.0 was released. KDE has great ideas with
Nepomuk which is good. But realisticly, what all do you want to see indexed ?
There has to be a realistic line drawn. The browsers already have indexing for
the history. Amarok, the player, also does indexing. It can tell you when your
last favorite song was played. For pictures, I have the awesome KPhotoAlbum
that cannot be beaten by anything. But above all, the most important thing to
index is your conversation. Those emails that you send daily. And indexing is
no good if you can&amp;rsquo;t find the information you need, later. IceDove has filled
that place. It does an excellent indexing (in terms of performance) and
presents a very user intuitive way to narrowing it down to, when looking for a
particular information.&lt;/p>
&lt;p>&lt;strong>Organization:&lt;/strong> The other great thing about KDE PIM is its ability to break
down its applications into small parts and glue them together into a new, well
integrated application. Yes, Kontact. It is used to be the best PIM
application. Used common libraries to make the suite more efficient than the
rest. But all this was &lt;strong>used to be&lt;/strong>. Today, kpart itself might be Kontact&amp;rsquo;s
problem. We have different applications glued together that if built with a
common design, could have benefited a lot more. Take for example: kmail, knode
and akregator. They are all very important parts of the PIM suite. Yet all
three are different. The only thing common amonst them is is that they are
available from the same Kontact shell. kmail has a different navigation.
akregator has very nice aggregated folders but the same cannot be available in
knode and kmail. knode, while still okay, has been rotting for some time. So
it was time to see how IceDove performed when testing it up against this Use
Case. The good thing about IceDove is is that it has one single uniform
interface to most of the PIM needs. I can use the same window and the same
interface for all my rss feeds, my emails and my leafnode newsgroups. That has
a big benefit in itself. I have only 1 integrated interface to look at and
only 1 interactive method to learn. There aren&amp;rsquo;t different keystrokes for
different applications. All is one in IceDove.&lt;/p>
&lt;p>And I think one of the main reasons for Mozilla&amp;rsquo;s success is its plugin
architecture. It is very difficult to satisfy everyone&amp;rsquo;s needs. In the same
way, it is very difficult for one group of developer&amp;rsquo;s to be able to innovate
differently. This is where Mozilla rocked. They provided a solid foundation
with basic standard interface and let new fresh minds to do the rest of the
innovation. Turns out it has worked well.&lt;/p>
&lt;p>So, with my PIM needs satisfied, I thought KDE was serving as nothing but just
a mere shell. So, now was the right time to do the thing I always thought of
doing. Switch to GNOME. GNOME looks elegant at first look but that is it. I
wanted to take a screenshot of an application to report a bug. I fired up
PrntSc key to let the screen capture utility pop-up. It did not have the
opiton to select just the application window. Hmmm! Time to return back to KDE
and use the Mozilla PIM suite and hope the KDE PIM team learns and does the
right thing.&lt;/p></description></item><item><title>Evolution Newsgroup UI</title><link>https://researchut.com/post/22/</link><pubDate>Fri, 29 May 2009 05:34:00 -0400</pubDate><author>rrs@researchut.com (Ritesh Raj Sarraf)</author><guid>https://researchut.com/post/22/</guid><description>&lt;p>I&amp;rsquo;ve been using KDE for a while now, probably 9yrs. I&amp;rsquo;ve also been an early
adopter of KDE 4.x. While KDE 4 is still far way behind in proving its worth
of the radical core changes it made (take for example: &lt;strong>Nepomuk, Strigi,
Phonon, Decibel&lt;/strong> - I still wonder when they are going to be ready for the
&lt;em>user&lt;/em>), I still find KDE apps far far ahead of GNOME.&lt;/p>
&lt;p>Probably, many would disagree. Possibly, they might flame me too.I mean
everyone supports GNOME as the default - Red Hat/Novell/Ubuntu. And I always
wonder WHY.&lt;/p>
&lt;p>Was it the licensing ? I can&amp;rsquo;t think of anything else. Anyways, why I still
think that the GNOME design sucks, I&amp;rsquo;ll give an example.&lt;/p>
&lt;p>&lt;strong>Evolution&lt;/strong> : Many call it the real killer app for GNOME. Maybe. There&amp;rsquo;s one
small feature in Evolution, that I&amp;rsquo;ve tried many times and I just feel that it
is a UI design with stupidity at its best. The &lt;strong>NewsGroup&lt;/strong> plugin of
Evolution. Ever tried ? How fast can you subscribe to newsgroups there. Take
&lt;a href="http://www.ensode.net/evolution_newsgroups.html">these&lt;/a> [examples](http://www
.go-evolution.org/Newsgroup). I&amp;rsquo;d be interested to know how Evolution users
subscribe to newsgroups.&lt;/p>
&lt;p>I personally use leafnode to cache the news contents. In Kontact Knode, when
the Gmane newsgroup listing appears, it appears with thousands of newsgroups.
But KDE allows me to run a search on that list and find for the relevant
newsgroup that I need.&lt;/p>
&lt;p>Such a basic feature and I wonder what was there in the mind of the &lt;strong>GNOME
Evolution&lt;/strong> devs when they were designing that interface.&lt;/p></description></item></channel></rss>