slimCODE

I like your program, but when I installed it, I noticed that the memory it used was around 50mb.  I'm curious to know if you plan to reduce that at some point or if that is an anticipated memory usage.  Help me understand if this is an acceptable consumption.  Thanks.

Hi, sorry for the late reply...

.NET applications do look like they use more memory, but this is not really "used" memory, but "reserved" by the .NET Framework memory management. If the system needs more memory, it will reacquire that memory, which is not really holding data. A good portion of those 50 megs would never get swapped to the disk pagefile (this is costly), and can be allocated to other processes by the system if needed.

I do have memory usage in mind when working on slimKEYS. Currently, the single place where I'd like to put some more effort on memory usage, but foremost CPU usage (on slimKEYS start-up only) is with slimLAUNCH.FileSystem. Another version could see an improved caching system, and I definitely want to support the Windows Desktop Search API with another similar plug-in.

Hope this helps.

Excellent utility! Does so much of what I've wanted in Windows! I'm using most of the plugins.

slimcode:

I definitely want to support the Windows Desktop Search API with another similar plug-in.

Any word one how this is coming along? I'm interested in replacing the big Windows Search toolbar on the taskbar with something more elegant...

It was on my list for 2008, but I'd lie saying I still believe in a 2008 release, so first half of 2009 is more probable. Now, two important questions on the subject:

a) Would it be bad if it targetted only Windows Search 4.0?

b) Is it a must that it becomes a slimLAUNCH extension? I may not be able to apply my own name matching algo to Windows Search results. Thus, it may become a slimSEARCH extension instead.

Great to hear it's still coming. My answers:

a) No

b) No