<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
<br><br>> From: kevin.krammer@gmx.at<br>> To: kde-linux@kde.org<br>> Date: Mon, 29 Dec 2008 14:57:49 +0100<br>> Subject: Re: [kde-linux] kmail and kdewallet<br>> <br>> On Monday 29 December 2008, Jethro Tull wrote:<br>> > Does anyone know where can i get the logs of kwallet?<br>> > when i load it through a konsole session i don't get any log. kmail doesn't<br>> > output any relevant info about getting infos from kwallet.<br>> <br>> Probably $HOME/.xsession-errors<br>> <br>yeah, that's it!<br>...<br>> > So this problem is quite difficult to backtrace.<br>> > anyway, it looks quite like a benign problem, i don't understand how<br>> > developers could build such a bug and not be able to solve. it's been long<br>> > i first requested for help for this in this mailing list.<br>> <br>> My guess would be that, since it is a bug, it has not been specifically been <br>> built, <br>good guess; i just didn't find the right combination of words to tell my actual though.<br>...<br>...<br>> I read somewhere that this can be a bit tricky since applications do this <br>> synchronously, so the current KWallet maintainer and his GNOME counterpart <br>> have started to work on a new authentication storage which should, among <br>> other things like unifying authentication access, also address some of the <br>> access perculiarities.<br>> <br>good to know<br>> > it seems that kde has been being written for many years and <br>> > developers only add code when new ideas come but never try to get the<br>> > previous code to be more optimized and robust.<br>> <br>> Actually I think most time is spent on improvement rather than new <br>> functionality.<br>yes that's also what i think, i have already noticed that some things were a bit better every time i have upgraded my system.<br><br>When i wrote the above statement i was meaning that they seem to not to care that much about optimisation and stability.<br>KDE is still considered as a resource consuming environment. things are far not as smooth as in Windows and MAC: windows movements, cycling through open windows... things often appear in aggressive ways. I don't understand why a simple web page with some images cannot still not be scrolled smoothly with konqueror.<br>note that i'm using the default slackware 12.2 shiped with KDE 3.5.10. my graphics (ATI Radeon Mob. X300) is 2 and 3D accelerated with the radeon open source driver.<br>My cpu is an Inten Centrino 1.7GHz. I have already benchmarked it many times, it is quite a descent system even now.<br>What I'm noticing about KDE is something that i have noticed on ALL linux boxes running KDE.<br>anyway...<br><br>> New functionality is obviously more visible, since it usually changes <br>> application interfaces (e.g. new menu or toolbar entry), changes workflows, <br>> is highlighted in articles and reviews.<br>> <br>> Nicely demonstrated by all the many man-years of work gone into KDE4 libs and <br>> infrastructure, the replacing of hacks with clean implementations, <br>> reorganisations of code and dependencies, etc. being totally hidden by a <br>> couple of visual changes.<br>> <br>oh really? Sounds good! i have to check it. I usually wait some time enough that minor new releases are done when a big new thing comes out.<br><br>> > when a bug is declared then <br>> > it is not really eradicated but just hidden. as an example take the bug:<br>> > Bug 109773:<br>> ><br>> > 'Get New Wallpaper' ticks wrong item.<br>> > when this bug was soved a new complain came. it is Bug 126190:<br>> ><br>> > 'Get New Wallpapers' blocks while downloading<br>> ><br>> > in a few words the initial problem was as following:<br>> <br>> [snip]<br>> <br>> Well, the reported bug has been fixed.<br>huh...? >-|<br>> Probably not as elegantly as possible, but most likely the only viable way <br>> within resource limits.<br>><br>whew... not elegantly at all.<br><br>so multiple downloading is out of resource limits?????<br> <br>> Then there is a new report which is actually a wish item, i.e. the ability for <br>> background downloading, probably even multiple downloads.<br>> <br>since UNIX i think all ever developers have concentrated their efforts to make systems able to run any program while some are already running in the background.<br><br>> The associated developers might not have time to implement this new <br>> functionality or a feature freeze might block adding new features.<br>background downloads or multiple downloads do not sound to me as a new functionality. I don't understand why if konqueror can download many things at a time, "Get new wallpapers" implementation cannot.<br><br>> <br>> It sounds like a good idea to do the downloading in the background, but <br>> sometimes it is wiser to put some work into maintenance even if some users <br>> would rather have their wish item implemented.<br>> Unfortunately, once such a new features it gets implemented, it will get a lot <br>> more attention than any of the work done internally, resulting in other users <br>> complaining about new features being added.<br>I don't see what's so harsh in that feature.<br><br><br>> <br>> Cheers,<br>> Kevin<br>> <br>> -- <br>> Kevin Krammer, KDE developer, xdg-utils developer<br>> KDE user support, developer mentoring<br><br /><hr />Take your friends with you with Mobile Messenger. <a href='http://clk.atdmt.com/UKM/go/msnnkmgl0010000001ukm/direct/01/' target='_new'>Click Here!</a></body>
</html>