First off, thanks for writing Keka. Of the 2-3 7zip compression tools available for OSX, Keka is by far one of the better ones.
Secondly, I have a few questions regarding Keka v0.1.4.2 working with files on a MacbookPro3,1 (Core 2 Duo 2.4GHz/6GB RAM) + OSX v10.5.8:
- Is it normal for Keka to not use any CPU at all?
When I began decompressing and testing (t option) a 32 x 1GB (-m0) spanned archive on an NTFS v5 volume, it consistently only uses 1-3% of the CPU  even though the rest of the machine is idle. Normally if I were multitasking this would be a good thing but it'd be nice if the application used more resources if the machine was just sitting there idle.
I looked into using "renice" and bumped up Keka, keka7z (and even ntfs-3g)'s priority to "51" , but it didn't seem to make any difference at all when I observed the CPU usage for keka* in Activity Monitor.app. I've heard priority control via (re)nice is broken in OSX v10.5.8+ though. If so, how can I speed up Keka?
- Any idea when Leopard support will be added for v >= 1?
I know we're up to Snow Leopard and now even Lion, but a lot of things (ex: rEFIt) break so I don't think I can upgrade at the moment. I ask because I've read that v1+ will now show you estimates of how long a compression / decompression ( / test?) run will take VS just the total elapsed time in the progress bar .
 Actually, Keka.app used up to 3% CPU and keka7z would normally only use ~1%, even after re-niceing
 I'm assuming higher values = higher priority based on the fact that things like daemons and SystemUIServer have values > 31, but I tried going in both directions anyway with no visible performance changes.