
TO INSTALL THIS PLUGIN 

1) drop the wsc and dll file into the Sleuth plugins directory 

2) Sleuth builds after july 10th 2003 have built in support to recgonize
   wsc files as plugins, so they can actually register it for you like a 
   normal plugin. If you have pre july 10th build, then you will need
   to use the fake dll file to have sleuth load the wsc plugin. because its
   a fake dll just there for the filename, you have to manually register the
   wsc file yourself with regsvr32.
   
   native wsc plugin support was added to both 1.36 and 1.4 (it works with
   all versions anyway..its just a matter of wether that fake dll was
   needed for the filename or not)

---------------------------------------------------------------------------------


This will show you how you can easily make sleuth plugins from the 
comfort of your favorite scripting language.

Basically any language that has a windows scripting engine, can
be used to make your very own plugin.

This includes PERLScript, PScript, Python as well as the standard
JScript, VBScript.

So how does this all work you ask?

The great guys at Microsoft have this cool thing call Windows Script
COmponents. Basically its an XML script file that the scripting
runtime can use as an on the fly COM object :)

The wscPlugin_2.wsc file included in this package is a sample
script written in VBScript that is an actual working plugin for
Sleuth. It implements the 2 default plugin functions Sleuth needs
to find and calls back to register itself with the main application
when it is created.

This wsc file was created with the Microsoft Script Component Wizard.

You can download it here:

http://www.microsoft.com/downloads/details.aspx?FamilyId=408024ED-FAAD-4835-8E68-773CCC951A6B&displaylang=en

A couple notes on creating your own components and getting this one to work.

1) If you jsut modify this one make sure to change one of the numbers in the clsid
   so that it does not conflict with other ones you make (if you make more thanone)

2) make sure that you end your progid = xxxxxx_2.plugin
   The classname has to be .plugin and the component name must end in _2

3) the dll file you see is just a blank text file named componentname.dll 
   this is because this is what sleuth looks for when looking for plugins

4) this may sound a little crazy, but you have to register the wsc file with
   regsvr32 to make sure the registry is setup right for it to work.
   to do this,
  
   goto start button -> run 
   type regsvr32 
   now drag and drop the wsc file from explorer into the textbox and its path will show up
   hit ok and it should give you a messagebox that it was registered ok. 

   note: using the wizard to create a new one didnt seem to register it, i still had to do
         it manually

   note2: once youhave registered the file, you cant move it, if you do..you will have to 
          reregister it to update its location in the registry

   note3: this is really cool technique :)

   note4: if you wanted to make a commercial plugin using this technique, you could use the
           script encoder and use vbe or jse for the script itself to keep others away from 
           the code...although I think somewhere people did figure out how to crack that.

   note5: one thing that is kind of annoyign is debugging, once sleuth is loaded, it already
          has the object in memory, so changes to the script file mean you have to reload sleuth
          but since they are just script commands, you can debug them for the most part in either
          sleuth script or jsconsole.





