'new style' External Image Input, solution to "A Fly in the Ointment"

Hello!
Appreciate your great work on such beatiful and flexible app, I found about filter forge not so long time ago and I'm very sad that external image inputs are gone now. As a c++ programmer I know that sometime implementation of a feature can ruins all application architecture, but it is alaways a hit about some design problem, a possibitily to make things better.

Idea is following. Why do you have special category for filters that use no external image input and one image input(and one greyscale as a selection)? May be you should make special category for 2 external images filter or 3 then?
So, What I'm trying to say that image input is just one of the filter component that reads external image, it is not a color control as it was previously hacked. One only input that this component needs is a path to image on a hard drive (or an id for a build-in preview image). That's it.

Sugestion: Make External Loading Component that just take an path input and output an image map. Path input new special data flow that can be hard disk path, host application input or build-in previes.

This way of doing thigs is much more clear. If application go this way it wouldn't be one and only 'Image' and 'Selection' like two angry singletons and overrided color controls, it would be loading components with different inputs that I can ajust anyway I want.
It is also a step to make application more professional with clear data flows and scripts that use it. Hope Filter Forge will become 'must have' program for any 3d/2d professional designers and animators.

Thanks for reading! ))

P.S. Tha one of the ways I actually want to try FF multiply inputs is to use bombing on 3d rendered picture with rendered depth map (as a particle size) and rendered normal map (as a particle direction). I hope it will be very interesting.

ooo really it is... great..., I was in sort of panic about this )), then what was really changed then?