HasManyFileManager: New CMS module/extension. Testers/review needed

Digging into the code of the module, I just realized that the upload field used for an image is a FileField were is added a "special" preview if the file is an image. (at first it looks like a SimpleImageField ...)
I think it would be interresting to use for image the ImageField as you would be abble to add images that are already in the assets.
what do you think?

The reason for using the FileField is quite simple: You can use it (more or less) for Files of any kind, not only images. In addition it has no JavaScript dependencies whatsoever that i would have to load inside the iframe. I don't know how well a ImageField (that is inside a iframe afaik) would work inside another iframe (created by the HasManyFileManager module).

The idea of the HasManyFileManager clearly was to attach Files to a page. And to one page only. So there was no need to let the user choose from existing assets. Whenever a page is being deleted, the assets belonging to that page should be deleted as well...

It seems like there is a need for a solution, that allows attaching some sort of "Documents" to a Page instead of just "Files". Maybe i'll develop a more general and multi-purpose solution than it is now. I'd really like to get rid of that iframe too :)