Hi Lantz,
-
Below is the script we suggest our clients used.
1. Each single person can have his/her own folder. when the first hit comes to the page, CuteEditor control will check for the needed folder, and as it won't be there, it will create the folder.
void Page_Load(object sender, System.EventArgs e)
{
...
string visitor_name = Context.User.Identity; //get the personname
Editor1.ImageGalleryPath = "/upload/" + visitor_name ;
} |
2. Each access level can have its own folder.
void Page_Load(object sender, System.EventArgs e)
{
...
AccessLevel accesslevel = ...//get from somewhere
Editor1.ImageGalleryPath = "/upload/" + accesslevel.ToString();
} |
I hope it helps.
Image manipulation/control is very important issue for the end users and developers. If you use the version 2.0, you will find that we add a new insert image button.
We also plan to post a code example in a few days to show the developers how to handle the images when they store the image's URL in the database.
I agree Chris got a good point.
There are two situations we should handle in the next version:
1. end users upload the large file size
2. end users upload the large screen size
The CuteEditor control should have the ability to compress and resize the image into a web-friendly JPEG. That will make the developers job much easier.
Welcome any input.
Adam
asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx