I would do a profile run, problem is that I stupidly forgot to fetch the power supply for this notebook, so it will take up to 2 weeks to get it back into working condition, and I don't have any way to test (install) it easily anywhere else (no DSL at my current home).
Possibly adept is doing relatively complicated package dependency checks (via a backend?) when toggling a checkmark? In that case a 6 second delay would be more understandable, although still far from "joyful". Doing a profiling run is not too hard, just install oprofile (see e.g. linux/Documentation/basic-profiling.txt) and check events such as unhalted clock, cache misses, branch mispredictions. Meanwhile I'll keep concentrating on kernel optimizations ;) (I don't think *I* should be the one to delve into adept optimization, since I'm very far from hacking on it on a daily basis) Oh, and if it doesn't get fixed for Dapper, then bad luck, but it'd be nice to see it fixed at all, and then if at all possible still in Dapper. Anyway, adept seems to be a new and exciting app, so it's just normal that people will oncentrate on the basic things (read: bare functionality) first before actually making it truly usable. -- adept is incredibly bloaty https://launchpad.net/bugs/39809 -- kubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
