« cascading filetype demultiplexing on windows | Main | payment systems blogroll »

cascading filetypes - proof of concept

Following on from my proposal for a cascading filetypes demultiplexer, I've hacked up a quick and dirty 'proof of concept' implementation. The zip file is here, which also includes a readme and the C# source code.

Comments

good work jonno.
what i had in mind, apart from microsoft integrating this into the os, would be to write a windows explorer context menu enhancement. i've seen some context menu extensions from this guy:

http://codecruncher.blogsome.com/peeker

i was considering writing to him and asking him to implement it, until i saw you'd done some work on this already.

cheers
lb

Leon,

I don't really have the time to take this any further, I just wanted to see how it could work. So if you find someone else willing to take it to the next level that'd be sweet.

BTW after I got this version done, I realised that instead of creating a static binding on the .cfd extension, you could add a popup context menu to the 'folder' object (e.g. as described in http://www.theserverside.net/tt/articles/showarticle.tss?id=ShellExtensions ) and in the context menu handler, you could extract the name of the file being right clicked on and create a menu that looked like:

open
-------->Snapper
-------->(an XML editor)
-------->Notepad
edit
-------->(an XML editor)
-------->Notepad
print
-------->Notepad

i.e. it extracted all the file extensions in the name, looked in the registry for all the apps that could handle each extension, and all the verbs those apps where configured for, and then built a menu tree with every verb at the top level and then all the apps that implement each verb.

excellent! thanks for the serverside link too!

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)