Custom input plugins

[janwilmans]

This could be done by putting executables and/or .jar files in the same directory as debugview++

c:> plugin.exe --info fileextention: .log outputdebugstring: yes c:> plugin.exe --indentify # returns true if the file is positively identified as the correct binary format for this plugin c:> plugin.exe some.log # outputs the file in text format through the Win32 OutputDebugString API

c:> java -jar plugin.jar --info fileextention: .log outputdebugstring: no c:> java -jar plugin.jar --indentify # returns true if the file is positively identified as the correct binary format for this plugin c:> java -jar plugin.jar some.log # outputs the file in text format through stdout

we should also add similar syntax for .py files.

[janwilmans]

debugview++ could automatically detect plugins in the same directory by trying to execute any executable in the same directory with the --info argument, however we dont what debugview++ to go around executing .exe files just anywhere you happen to copy it; just think of the havok this would wreak if debugview++.exe would be copied in the c:\windows\system32 directory.

Therefore, I suggest to scan for executables only in a subdirectory called 'debugview++plugins' .