. I have to hurry an intergrate it into all my projects before people start moving en massse to flash player ten and no one can upload multifiles anymore.I am much happier with the new version and I learned a lot. Like how much MXML application suck for tiny things. The smallest I could get it as an MXML application was about 150k which is so freakin lame considering it is just a bttton. I didn't even think to look at the size until I was done and I was so pissed. There was no way I was going to add a 150k button to pages.
So I scapped where I was at and build one form scratch as and Actionscript 3 project in Flex and used the flash drawing API to draw the button states etc. Its nice with an actionscript project you can really get the project size so tiny. I ended up managing to get it all under 10K which is a lot more reasonable. You can style everything bou tthe button from javascript and all the event handlers are the same as the old surebert multifile uploader ones so implementation should be easy. I commented the javascript API but no so much the flex code. The Javascript is here
and assumes you are using the surebert toolkit although you could adapt it to run on anything else. Anyways, the flex code is here if you are interested 
Oh ya, I realized that. I use that technique for the Flex embedded apps on the intranet I am developing but this upload button is only a button and should not require anything beside sthe code required for the upload which is like 5k. I am much happier with the Actionscript version as even though I was limiting what I was loading by very specific, it seemed like the smalled Flex MXML based app I could get was like 150k.
You can make smaller Flex apps if you use --static-link-runtime-shared-libraries=false. It's a tradeoff- the user's first download ever will be much larger, since they'll need to fetch the entire Flex library [~500k] in addition to your program code. [Whereas if you statically link, you get the program code plus only the parts of the library they use.] But subsequent requests for Flex apps that link against the same framework version, regardless of which domain they're from, will be much faster since they'll only have to download the program code. The library is stored in a special Flash cache separate from the browser cache, so it's very rare that they'd need to download it again.
:::link:::
:::link:::
- Z
My Flash was probably messed up from have half a dozen beta's of various adobe products and sdk's installed.
Thanks god, I was surprised because I developed it on the mac and tested safari, IE, and firefox. I was ready to kill myself if it didn't work. I have spent so much time on this crap after Adobe made they decision to not allow for FileReference.browse to be called from a non flash interface. I am still mad at them.
I reinstalled Flash (same version as in my last comment) and the problem went away. So nevermind :)
I'm having trouble uploading images with either Safari or Firefox, with version: MAC 9,0,124,0
If I click on the upload multiple images button, I get the spinning beachball and then am forced to quit out of the browser after a few minutes of no activity.
I'll try updating flash and seeing if that fixes it.
I tried it out. Very cool! :) I left you something on the surebert site. :D