After specifying common upload settings, it is required to set at least one Converter. Each Converter configures one converted file (original file, thumbnail created from original image file, icon associated with original file, or original file compressed into ZIP archive) which will be uploaded for each of user-selected files.
For example, you configure Image Uploader to send an original file and a downsized copy of image (if the original file is an image) or an icon associated with the original file. It means that if a user selects two files (a JPEG image and a PDF document) Image Uploader will send four files:
The following samples demonstrate this configuration.
<aur:Uploader ID="Uploader1" runat="server">
<Converters>
<aur:Converter Mode="*.*=SourceFile" />
<aur:Converter Mode="*.*=Thumbnail;*.*=Icon"
ThumbnailHeight="120"
ThumbnailWidth="120"
ThumbnailFitMode="Fit" />
</Converters>
</aur:Uploader>
$uploader = new Uploader("Uploader1");
$converters = &$uploader->getConverters();
$converter = new Converter();
$converter->setMode("*.*=SourceFile");
$converters[] = $converter;
$converter = new Converter();
$converter->setMode("*.*=Thumbnail;*.*=Icon");
$converter->setThumbnailWidth(120);
$converter->setThumbnailHeight(120);
$converter->setThumbnailFitMode("Fit");
$converters[] = $converter;
var u = $au.uploader({
id: 'Uploader1',
converters: [
{mode: '*.*=SourceFile'},
{mode: '*.*=Thumbnail;*.*=Icon', thumbnailFitMode: 'Fit', thumbnailWidth: '120', thumbnailHeight: '120'}
]
});
The way you retrieve and save converted files on the server side depends on the platform you use. Find the detailed instructions in the Saving Uploaded Files in ASP.NET and Saving Uploaded Files in PHP topics.
Consider the Converter properties in detail below.
The Mode is the most prominent property of the Converter class. It specifies what will be uploaded for each file selected for upload (i.e. the original file, a downsized copy of the image, an icon, or a ZIP archive). One Converter instance can specify different types of converted files for various types of files selected for upload client-side. For example, you can configure the Converter to send downsized copies of images for JPEG images and original files for files of other types. It can be done using the aforementioned Mode property.
The Mode property accepts a format string consisting of masks=mode pairs
separated by a semicolon. Each pair includes a set of file masks separated by commas and a corresponding mode. In general, this string has the following syntax:
mask11,mask12,...=mode1;mask21,mask22,...=mode2;...
Here is the list of supported modes:
When Image Uploader prepares the upload request, it extracts masks=mode pairs.
It checks whether the name of the current file fits the file mask specified in the pair. If it fits the current pair, Image Uploader sends an item specified in the pair to a server. Otherwise, if no appropriate file mask is found or Image Uploader is unable to create a downsized copy of the image (if mode is specified as Thumbnail and the
current file is not an image), Image Uploader checks the next pair in the same way.
If there is no file mask corresponding to the original file extension or no appropriate mode, then Image Uploader does not send this converted file.
If you specify the Mode property to send a thumbnail, you can also set the following thumbnail parameters:
ThumbnailFitMode specifies how the thumbnail is to be resized. The following values are supported:
[0, 100] range. If you specify 0, the file size will be extremely small, and the quality will be very low (almost always unacceptable).
Alternatively, if you specify 100, the file size will be quite large, but JPEG artifacts will be almost invisible.0 value is
specified, the original image resolution is used.