[Kde-pim] knode features and RFE's?

[Olivier Trichet]

Le samedi 09 janvier 2010 13:36:04, Ingo Klöcker a écrit :
> On Friday 08 January 2010, Matthew Woehlke wrote:
> > Ingo Klöcker wrote:
> > > On Thursday 07 January 2010, Matthew Woehlke wrote:
> > >> So I am looking (yet again) to see if kdepim is at a point that I
> > >> can switch to it from Thunderbird, but I'm still missing several
> > >> "must have" features from knode:
> > >>
> > >> - side by side view

This should be available as of KDE SC 4.4.1 with your patch :-)

> > >> - colors that aren't broken
> > >> - tags

Tags and the possibilities they enable will not appears until the porting to 
Akonadi. At least not by me; I avoid touching the current backend of Knode.

> > >
> > > Apart from the missing UI this will automatically happen when/if
> > > KNode is ported to Akonadi/Nepomuk.
> >
> > I assume you mean "tags", not "all of the above". Hmm, but are those
> > tags in the sense of "I want this item to display differently in the
> > list" (different text color, especially), i.e. how TB uses "tags", or
> >  as in search aids? Nepomuk makes me think the latter, which I really
> >  don't care about, but maybe that includes the former also?
> 
> Yes, the latter. The color is more an issue of the view, but I guess
> certain colors could be assigned to certain tags.
> 
> > >> - automatic tagging via filters¹
> > >
> > > This is already present in KMail and it will be provided by
> > > Akonadi/Nepomuk. So, again, you just have to port KNode to Akonadi.
> > > ;-)
> >
> > Okay. Or... port NNTP to KMail methinks (see below).
> 
> There is already an NNTP Akonadi resource. I'm not sure about it's
> current status. So getting the news to be shown in KMail will be very
> easy. The problem is the newsgroup-specific workflows/functionality that
> is missing in KMail.

The NNTP Akonadi resource can not get the list of groups in a timely manner. 
It needs a few seconds to get it form the nntp server and around 10 min (100% 
of CPU used) to insert the list inside the akonadi server for a small server 
like gmane.org. 
I have not play with it any further, but it should be pretty ok if this is 
fixed.


> > >> (¹ For example, I have TB tag all my own messages 'personal' so
> > >> they are a different color in the message list. I have other such
> > >> filters, but so far they are all based on sender address. I also
> > >> apply tags manually.)
> > >
> > > Note that our master plan still includes merging of KMail and KNode
> > > (at least code-wise) resp. making both use the same code as much as
> > > possible.
> >
> > That sounds like a good idea.
> >
> > > Also note, that KNode currently has 0 developers AFAIK. Also, I
> > > guess Volker would be happy if you took over maintainership of
> > > KNode. ;-) Volker will correct me if I'm wrong.
> >
> > Oy, that's not so great. I don't think I'd make a very good
> >  maintainer, I don't get done half the things I should be, already,
> >  and taking over something the size of knode with an unfamiliar-to-me
> >  codebase doesn't seem a good idea.

If you want to help more, I would be glad to help you find the right place to 
look at.


> 
> I think I wasn't really right about KNode having 0 developers. Olivier
> Trichet does some work on KNode. In fact, Volker handed over
> maintainership to him a few month ago.
> 
> >  Probably better to just implement
> >  NNTP as an account type into kmail. I /might/ be able to help with
> >  that, but...
> >
> > If you or someone can give me an idea what would be involved in
> >  that...?
> 
> See above. Getting news to be shown in KMail 2 (i.e. in the Akonadi port
> of KMail which will very soon be merged to trunk) shouldn't be a big
> problem thanks to Akonadi. You might want to talk with Olivier to see
> whether he has any plans w.r.t. KNode and Akonadi.


Let's share the current (my) agenda for KNode, it will hopefully answer a few 
of those questions:
 - switch to KPIM::Identities. This means using/sharing the identities of 
KMail. Already done, not commited yet since it is mixed with the next topic
 - work on the composer. That was not scheduled but the previous topic forced 
me to do it. Mostly done, this should be commited next week.
Then once the akonadi-port branch is merged into trunk :
 - fix/work around the NNTP Akonadi resource to fetch group list quickly
 - move server account into Akonadi if it is *possible* to keep fetching 
articles directly with knode (that would require knode to be able to access 
server configuration stored inside the akonadi server. Quit unlikely)
 - use the messageviewer once it lands into trunk. Already started, I'm 
waiting the merge of the akonadi-port branch to start modifying it to suit 
usenet message display.
 - start to port the article backend to akonadi.
 - Add features that akonadi would allow to do more easily.

And also fix bug.


At the same time, I'm still evaluating the possibility to hack nntp support 
into KMail directly and drop KNode entirely! As Ingo said, the main difficulty 
here would be to add the nntp workflow to kmail.


Regards,
Olivier


_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/