well, you could look at it as a simplification

hopefully this won't come across as annoying but i thought i would try one last ditch effort to make my case
adding support for external applications doesn't make trout more complex - in fact it allows trout to remain simple because trout wouldn't need any featured coded that can already be done by other software. an example of this is the built in tag editor. if you added support for helper applications, the tag editor would not even be necessary because any third party tag editor that accepts commandline parameters could be used instead. Such tools are plentiful and feature rich. This way, the user gets to choose only those functions they need and they get to choose their preferred program for that task. From my perspective, it helps out trout development because you don't have to worry about every little feature request (like mine) and it helps users out because they now have access to a ton of new potential features.
you wouldn't even need to make the filemover application (i'm a horrible newb but i'd try to make it). you could just add the ability to define helper applications in a dialog with the options:
- path to helper application
- arguments to use when launching helper application (%file% will pass on the path of the currently selected file)
- define a hotkey to launch this helper application
- toggle: when launched if file is playing, skip to next file in playlist (this unlocks the file for editing in the helper application)
- toggle: when launched remove current file from playlist
- toggle: show this helper application in the right click file menu
anyway, i'll shut up now!

thanks again for the great player!