I'll just write up some notes about image management as I'm very interested in that aspect.

The way I've been doing it so far is:

I provide a page visible only to a content manager role that is not a DNN Administrator. On that page I have a File manager module that duplicates the core file manager. I also have another third party module that does image uploading and resizing. Both these modules have proven to be buggy, but together they provide the only means of image management that isn't integrated in another module for a specific purpose only.

If the file manager can be made to be reliable and provide thumbnail view of image files, then that will provide a very workable means of removing and organising images on the server.

The image upload tool I currently use does the following:

It allows one to specify a new name for the uploaded image. This is handy as people are often uploading digital camera files that have DSC_0001 style names and they should be encouraged to provide friendly names.

It also allows one to select a series of size presets off a dropdown list. The provided list was too short, but it was easy enough to change the ascx and language files to create my own custom list. I made a list of named sizes to suit the site, such as "Thumbnail-90" "Gallery-640" as well as a series that goes "XSmall, Small, Medium, Large, XLarge, XXLarge" and so on. My medium size is set at 240 wide as that is the size most suited for use in typical text and image pages on the site. Users find it dead-simple to pick from the list like that.

A further option allows one to specify a custom image size instead of selecting a preset. This has a box that lets one set either a maximum width, maximum height, or maximum of whichever is biggest.

I've posted screengrabs of my version of the module to the support ticket tool here so you can see what it's about.

What I'm hoping for in the Access Manager is something that does that or even improves on it. One improvement would be to be able to set a maximum size at admin level for any uploaded image.

Another significant improvement would be a quality resizing option - the usual methods people use tend to be overloaded with artifacts. I harassed Scott over at Ventrian quite a while back to provide a quality option in his gallery module as everyone I had showed it to thought the quality of the resized images was pretty awful. My clients are generally photographers and they care about how their images look.

This is the site I found at the time that has code for a quality resizing option, and it is what has ended up in the gallery module to great effect: http://www.glennjones.net/Post/799/Highqualitydynamicallyresizedimageswithnet.htm

And finally.. I think another fantastic improvement would be resizing on the server. Imagine if one could select an image file on the server, set a size, and a new name and away it went.

This is all just food for thought in any case.. and I'm sure others will have different things that are important to them. so whatever you can manage is bound to be a vast improvement on what is currently available for DNN.

Regards,
Rob

The code you linked for quality resizing of the images, appears to be very similar to code I have been using in a couple other projects.
I know I had a project where the "defaul" .net resize-image methods were unacceptable, and found this solution.  I don't have my particular resize code in front of me at the moment, but I'll probably compare a bit before integration into the module.

At the moment, I am leaning toward an admin-folder-level setting to resize images on upload (admin will set the max width/height).
Related to what I wrote in response to your support ticket, perhaps another setting to optionally keep the original-uploaded file.
In addition, options at the module-level (in addition to move/copy/delete files), we could have an image resizer?

If you were able to create an image resizer that worked directly on files on the server, then I believe it would be ok to resize images to an admin-fixed size upon upload.

Then the user could upload images without having to think about it and they would all end up at say 800x600 - a typical maximum. Once on the server, could they then select one and select a size preset and click go. If it then created the new file and named it, for example by simply adding the new size to the end of the file name, then that would be simple and powerful.

However, in reality, the number of times that any single image is published more than once in more than one size on any of my sites is nearly nil. That usually only happens in a purpose built module such as an image gallery.

Even so, If one could do as I described further up, then my users would certainly make use of the option to insert small images into text, and then link those to the larger ones as a full view.

However, the main thing I'm after here is to let content creators easily convert the digital image files on their hard drives into files suitable for inserting into the rich text editor... and do this without an external application.

The idea is that content creators are the ones who decide how big they want the images in their documents to be and therefore it's a must that they can either specify the image size or select from a range of presets.

Whether this happens during upload or afterwards on the server is a matter of what you would be able to accomplish.

I'm not 100% sure we're on the same wave-length with image management, so just bear with me if I'm off-track and let me know what is possible and what isn't.

Rob