RE: Re[3]: Scriptable Shell Extension

["John Hind" <john.hind@...>]

Yes, although this means your extension will get called a lot so it had
better return very promptly when it has nothing to do. My concern is more
about which process the Lua runtime and scripts run in - you have little
control as these extensions are in-process DLLs running in Explorer's
process. With some Windows configurations you will get one instance of your
add-in, with others one per Explorer window (plus do not forget the desktop,
IE and other places where these extensions get invoked).

I'm sure these issues can be surmounted, but like I say it may not be as
simple as it seems at first, particularly if you want to do a general
purpose extension system like FileMenuTools (which was the example that got
me thinking on these lines).

Good luck with it - I will be interested to see what you come up with!

-----Original Message-----
From: Bulat Ziganshin [mailto:bulat.ziganshin@gmail.com] 
Sent: 06 May 2009 13:52
To: Bulat Ziganshin
Cc: John Hind; 'Lua list'
Subject: Re[3]: Scriptable Shell Extension

Hello Bulat,

Wednesday, May 6, 2009, 4:20:44 PM, you wrote:

>> Problem I ran into with explorer extensions is that they expect to be in
>> small DLL files with a different DLL for each type of extension

if you mean filetype extension here - it's not necessary. just
register as '*' extension handler and then build menu depending on
filenames selected. it is how configurable Shell Extenders work (such
as Fast Explorer and FileMenuTools) - unfortunately these are not
scriptable

-- 
Best regards,
 Bulat                            mailto:Bulat.Ziganshin@gmail.com

Attachment: smime.p7s
Description: S/MIME cryptographic signature