Brad, it sounds like the best and easiest way to go about this is to make fileList a property, rather than an attribute? What do you think? I can have the attribute shadow the property, but otherwise you'd be able to directly manipulate the property like a regular array.

Hey Allen sorry for the delayed response - I am just getting to this now. I am very close to replacing my previous HTML4/CSS2/POJO solution with the YUI 3.5pr2 HTML5 uploader control (with Flash fallback).

As for your suggestion I think that could work. Would be nice to have a method you can call to basically just say "remove element with fileID X" or maybe include a simple file number attribute that could be referenced similarly?

The requirement I am struggling with is that if before a user submits a batch for upload, if they decide they want to remove one of the files in the list this is not easily accomplished. It would be very nice if there was a built in facility to accomplish this - right now the only thing that's easy to do is clear the array entirely:

// clear file list array
fileList = [];
// clear file list
myuploader.set("fileList", fileList);

But perhaps I just need to look into handling this within my own code but not sure how to reference the file list object directly... I assume there is a corresponding get method that I can call, copy to an array var, work with it, and then use the set method again.

I also find myself using the before/after list change function to perform validations (i.e. iterating through to count number of total files, parse extensions, file sizes). I don't think this is the proper / most efficient way to go about this...

This will become either a property instead of an attribute, or we'll add convenience methods for managing the attribute (removeFiles, get items at index, etc.).

Awesome! Here is what I ended up doing to implement this:

// clear a single file
function clearFile(position) {
// clear POST variable array element
postVars = [];
// declare an array for the temporary (working) file list
fileList = [];
// get the file list from the uploader
fileList = myuploader.get("fileList", fileList);
// delete the selected file from the array
fileList.splice(position, 1);
// set file list back
myuploader.set("fileList", fileList);
// redraw new file list
drawFileList();
// remove "Clear All" button
if (fileList.length < 1) {
Y.one("#clearAllButton").hide();
Y.one("#clearAllBtn").hide();
}
}

// draw file list
function drawFileList() {
out.setContent("");
// clear POST variables array
postVars = [];
var showClearAll = false;

// clear file list output
out.setContent([
'<table ID=UploadPageSelf width=100% border=0 cellspacing=0 cellpadding=0>',
' <tr>',
' <td>',
' <br />',
' </td>',
' </tr>',
' <tr>',
' <td>'
].join());

Y.each(myuploader.get("fileList"), function (value, fileNum) {
fileId = value.get("id");
fileName = value.get("name");
fileSize = Math.floor(value.get("size") / 1024);
out.append([
' <div class=fileNum id=', fileId, '>',
' <label for=file>File', (fileNum + 1), ':</label></div>',
' <div class=fileName>', fileName, '</div> ',
' </td>',
' <td width=50%>',
' <a href=# class=clearLink id=', fileNum, '>Clear</a>',
' <div class=fillerFive> </div>',
' <div class=fillerTen> </div>',
' </td>',
' </tr>',
'</table>'
].join());
// set showClearAll button flag
showClearAll = true;

// TO DO: consider adding TOTAL filesize
});
myuploader.set("postVarsPerFile", postVars);
// run validate files function to prevent illegal files from being added and provided instant user feedback
validateFiles();
}

//// event listeners

// event delegate for "Clear" link
out.delegate('click', function (ev) {
var position = ev.target.get('id').replace('Clear', '');
clearFile(position);
}, 'a.clearLink');

There's now a private property _fileList which, if strictly necessary, can be manipulated directly. It's still recommended to retrieve the fileList by calling get("fileList"), manage it directly as an array, and then set("fileList") back, but a direct manipulation option is also available. Additional array manipulation helper methods will be added in future releases.

Shipped in 3.6.0. Marking closed/fixed.