[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [Announce] KPDF2-0.3.0 released
From:       jos poortvliet <jos () mijnkamer ! nl>
Date:       2007-02-07 17:47:40
Message-ID: 200702071847.43631.jos () mijnkamer ! nl
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Op Wednesday 07 February 2007, schreef Krzysztof Lichota:
> BTW. I think by requiring improvements to KDE 3.5 branch to be first
> tested in trunk you are losing some manpower. I, for example, would be
> willing to work on some features for KDE 3, but burden of working on
> develoment branch (which will not be used by people for a long time), is
> not appealing to me. I guess I am not the only one.

afaik you can just write a kde3 patch, put it on kde-apps so ppl can test it, 
and try to get it in KDE 3. but you will also have to take care of porting it 
to KDE 4, which makes sense, right?

> >> If this bug could not be solved in current KDE3 architecture, then I
> >> think there would be something seriously wrong with KDE3 architecture.
> >> And I don't think this is the case.
> >
> > in the case of PIM storage and retrieval in KDE3, you're wrong. there are
> > lots of great things in KDE3, this isn't one of them. it doesn't suck,
> > but it's not great either.
>
> Has anyone tried to fix it? Can you point me to the discussion or tell
> me which part of code is the problem? I would like to take a look at it.

i hope a KDE pim developer can help you here. i'm pretty sure you are more 
than welcome to help fix it, as they are seriously under-(wo)manned.

> 	Krzysztof Lichota


grtz
-- 
Disclaimer:

Alles wat ik doe denk en zeg is gebaseerd op het wereldbeeld wat ik nu heb. 
Ik ben niet verantwoordelijk voor wijzigingen van de wereld, of het beeld wat 
ik daarvan heb, noch voor de daaruit voortvloeiende gedragingen van mezelf. 
Alles wat ik zeg is aardig bedoeld, tenzij expliciet vermeld.

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]