Hi,

 

I thought I'd reword for clarity. As mentioned before we are trying to use Cute Editor as a email body editor. Cute Editor will be part of a email composition program so users can benefit from Cute Editor's friendliness and polish during their email composition tasks. I read the two CHM files documenting Cute Editors and understand what the Templating, File Upload, and Image Uploads can do.

At the moment I am assuming all Templates, Images, and Files are uploaded to the same folder within a ASP.NET Server. You and I can both see each other's files. And the file names are as named when uploaded.

Our system need to maintain security and privacy for each registered users and this scheme of referencing files may not serve. We thought it would be nice if

1) It would be nice if the file names are made semi-random by prepending some random characters Example: "#DATE#-#random#-Filename.xml like 20060216-X285F154-Filename.xml". 

Result: By providing all of these customizations one user shouldn't accidentally stumble across another's uploads. And the file names are still reasonably english-like that the user won't be confused.

Provided there are no such hooks, I have the following idea: A windows daemon that watches the upload folders and rename files accordingly.

2) It would be nice if each user has a separate folder.

3) It would be nice if we can hook the authentication to our application. So our database can tell Cute Editor which Upload folders (be it for templates, images, or files) to make visible to the user.

Are there any docs or help we can get regarding this?

-- David