slimCODE

Is this possible at all? For example if I wanted to open a .mp3, video, or even html file I don't necessarily want to have it open in their default player or even a browser. It would be nice to have an ability to choose an application the file will be launched with, e.g. via a context menu or from another slimlaunch window somehow.

 I'm loving slimkeys so far, though. Keep up the good work =)

(now that I think about it, is there anyway to 'skin' this asides from just swapping colors? if not, will there be?)
 

Thanks! 

"Verb" support has been on my TODO list for some time now. I have a few possible designs:

• "Verb" selection option: I'm currently using the default verb (generally "open"), but I could look at possibles verbs and show them. Would "Open with" be included, I don't know.
• Windows Explorer context menu: I could allow opening the usual Windows Explorer context menu, where among other options, you have the "Open with..." option.
• Custom-made "open with" option: I could implement my own "open with" option in the extended launch options, remembering the last selection per file or per extension. More powerful, but you have to browse again for apps even if verbs already exist for them.

I can't promise something soon though. Version 1.0.4 is already in tests.

As for skinning, I doubt I'll introduce such a functionality. Localization would come before that. If I make a Vista-specific version (WPF, thus could work on XP with .NET 3.0), it would be skinnable (themeable).

-"Verb" selection option sounds interesting.

-Context menu doesn't sound bad, depending on the keyboard it might still be accessible with a keystroke.

-I'm liking the custom-made "open with" if it opens a slimLaunch or something similar. Granted it seems like an extra step or two simply because of the additional windows and typing, but I believe it's marginally shorter and more powerful than the above options (if we had to choose between which of the three you would work on/prioritize).

"...can't promise something soon..." --- No worries, better no promise than a "1.x.x is coming out... NEXT WEEK!" ... ::3 months pass by along with balls of dust and hay::

It's quite comforting to hear these things are already in your mind. This would probably imply you've already an idea or three of how to approach this in terms of whipping out the code, too. 

What does 1.0.4 have in store for us atm?

 Ok. Yeah you have your work cut out for you not going to push for skinning, it's not that important (I see the slimlaunch size as an issue was already brought up).
 

trying to inform ppl about slimkeys. it's incredibly useful and it's only going to get better =)
 keep up the good work =)
 

versatil:

::3 months pass by along with balls of dust and hay::

One of the first albums I listened when I was young was "The Good, the Bad and the Ugly". q;-)

versatil:

What does 1.0.4 have in store for us atm?

Here's the draft "release notes" I keep up, but it may change.

What's new in version 1.0.4
===========================

TODO:
  --> Revise default slimSIZE hotkeys.
  --> Use native calls in slimPASTE.
 
General:
  * Removed splash screen.
  * Fixed focus problem with some forms when displayed directly via a hotkey.
  * Fixed unregistered icon not hidden until closing and reopening main window
    when entering a new license key.
  * Clicking the unregistered icon now opens the slimKEYS configuration.
  * Renamed the default hotkey description to "Open the slimKEYS main window".
  * Added a config button to the main window, which does the same thing as
    activating the default Win-K hotkey.
  * Fixed main window's empty title.
 
slimLAUNCH:
  + You can now add a single file as a source, with an optional forced launch
    command.
  + You can toggle an option to remember only the first launch command used per
    item.
  * Fixed creation of new slimLAUNCHthis hotkeys.
  * Fixed initial selection when selecting source type.
 
slimLAUNCH.Passwords:
  + The password tree view is now sorted.

slimSEARCH:
  * Pressing ESC in the search selection window did not close the window.
   
slimSIZE:
  + Added "Window State" option to change the target window's state to either
    maximized, normal or minimized, or to leave it as is (default).
  * Fixed regular expression caption matching. Regular expressions must either
    start with a ^ or end with a $ (or both).

versatil:

I see the slimlaunch size as an issue was already brought up.

Can you elaborate, just to make sure it is?

slimcode:

  + You can toggle an option to remember only the first launch command used per
    item.

so if we launch something with alt+enter the first time it will remember that?

slimcode:

Can you elaborate, just to make sure it is?

ok maybe I was mistaken/confused. The verbose views was referring to something else. Not entirely sure what I was thinking at the time but it was probably along the lines of having a smaller view in slimlaunch, a closer semblence to list/detail view in windows explorer (having the items draggable would be nice, too). Taking a closer look now I'm thinking the size of everything is fine, forgot that the icons come in specific sizes hence they're not entirely scalable so presenting the information (Name | Path) on seperate lines would make it look awkward or too small. 

By default each launch item should always remember the last launch command used to open them, no matter if it's via Enter or Alt-Enter. The new option will enable you to make items only remember the first time they are launched, again no matter if open via Enter or Alt-Enter.

In other words, if the item already has a command displayed between brackets in the launch window (e.g. "[foo]"), if you launch it with another command (e.g. "bar"), the next time you'll browse for it, the initial command (e.g. "foo") will remain its last command. Foremost, this will useful for explicitly added files, where an initial launch command can be forced, and you don't want other commands to replace them.

As for the launch window, I don't want to link it too much with explorer, nor put too much "look customization" code in there, as it would slow things down.