On Sat, Feb 25, 2012 at 12:44 AM, Ian Wadham <iandw...@gmail.com> wrote: > Yes I do (have a Macbook). The search function is a small magnifying > glass icon at the top right of the screen (equivalent to a "systray" item). > It drops down to single line-edit type field with the label "Spotlight".
Yeah, that's the one. I don't have one myself but I recently had a chance to work on one and they sure are terriffic. That spotlight field is simply something you have to learn to rely on. > Within a day or two of acquiring the Macbook I tried it out and found > that it had already indexed all my old KDE emails. No fuss, no bother, > no using up the whole of one core continuously. It just gets on with the > job. Like a Google search. I do not use it a lot, but it is nice to have. It takes some time and change in behaviour but if you really give it a shot it's a good thing indeed. But as you said, most people really try that only once. If it doesn't do as expected the first times, they will simply deactivate it and stick to the old ways. Semantic Desktop nil, dusty old ways score. So I think accessibility and simplicity is key here and has to be done right. > I am surprised too that Nepomuk, Strigi et al. require so much CPU > power and space. This is not at all what was claimed at Akademy > 2007, akademy2007.kde.org/conference/slides/strigi.pdf See the > slide entitled "Speed Comparison". What went wrong? Well, I have to correct my initial rant about that a little. There was one problem here I could fix. During the upgrade from 4.7 to 4.8 there are some temporary files left in /tmp. When you start 4.8 and those files are still there, it causes problems in virtuoso-t. So I stopped KDE, deleted everything in /tmp and restarted KDE. This caused some initial reindexing and resource demand but it actually stopped after a while and isn't present all the time anymore. Most of the time though it still is top - 10:11:52 up 16:34, 4 users, load average: 0,67, 0,69, 1,02 Tasks: 130 total, 2 running, 128 sleeping, 0 stopped, 0 zombie %Cpu(s): 3,4 us, 8,3 sy, 61,4 ni, 26,1 id, 0,9 wa, 0,0 hi, 0,0 si, 0,0 st Kb Mem: 1919532 total, 1889468 used, 30064 free, 114448 buffers Kb Swap: 5927948 total, 93216 used, 5834732 free, 457912 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 31309 sm 39 19 295m 209m 5020 S 142,5 11,2 37:53.38 virtuoso-t 2910 sm 20 0 912m 334m 17m S 4,7 17,8 8:21.21 firefox 3002 sm 20 0 663m 69m 6836 S 1,7 3,7 10:16.31 plugin-containe 2404 root 20 0 172m 29m 16m R 0,7 1,6 3:13.28 X 31223 sm 20 0 1782m 106m 39m S 0,7 5,7 0:37.76 kontact 2656 sm 20 0 555m 22m 10m S 0,3 1,2 1:50.51 kwin But anyway, my bottom line is, that just needs to be more accessable and maybe no-one will complain about such things anymore because there's plenty gain for the pain. Cheers, Stephan >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
