Any and all code samples that are authored by me and posted on the Ext forums or website are hereby released into the public domain and I release anyone or entity of liability by using said code samples unless explicitly stated otherwise.

Opinions are mine and not necessarily endorsed by Ext, LLC. Please do not contact me directly for assistance unless requested by me.

Also you could just do flash for everything except linux and then degrade to ajax. that would be an awesome module.

Ryan

Hi Ryan,

there is already stable version of flash 9 for linux and that is what I use, about:plugins says Shockwave Flash 9.0 r48, and it crashes anyway (segfault).

I'll think about integrating flash/non-flash functionality to one component. For the first glance it seems too much work as they use totally different events/callbacks, they differ in progress calculation and even the UI is slightly different. I'll see...

Questions on Beta2

Hi,

Was wondering if you were/are going to making any changes to the non-flash file uploader code? Seems pretty good, but I am curious.

Also, quick question on the code. The input element with type = file, generates a browse button, which is hidden by the css. The "add" button triggers this browse. Is that due to event bubbling? I cannot see how the Add button triggers the browese event.

Was wondering if you were/are going to making any changes to the non-flash file uploader code? Seems pretty good, but I am curious.

The code needs a revision, cleanup and removal of hard-coded texts to class variables for purpose of localization. Also, I'm going to implement a method to get progress information.

Also, quick question on the code. The input element with type = file, generates a browse button, which is hidden by the css. The "add" button triggers this browse. Is that due to event bubbling? I cannot see how the Add button triggers the browese event.

Thanks!

Dave

Add button is fake. The actual <input type="file"> is above it with opacity:0.

i don't think you should stop developing the one w/ swfupload just because some users can't use it. the amount of linux ff users is pretty small. You could have a clause that checked for swf, if it's not there, then you use the other method.

i don't think you should stop developing the one w/ swfupload just because some users can't use it. the amount of linux ff users is pretty small. You could have a clause that checked for swf, if it's not there, then you use the other method.

Well, number of Linux users grows at least in my environment and I'm just not going to develop for Win-only or Mac-only. Either it works for Firefox@All-platform or I just "don't sign under it".

I'm writing in another post about degrading when there is no flash of in incompatible environment it's quite huge task and I don't develop these extensions for living but because I need them.