Instead of having a crazy API within the SWFUpload module, just provide the SWFUpload module as a facilitating module for other modules, like Image Fupload. Right now, Image Fupload just asks the user to place SWFUpload in a subfolder. Would be cool if Image Fupload depended on the SWFUpload to just facilitate the installation of SWFUpload.

Comments

skilip’s picture

Hey Rob,

I see your point. However I'm not convinced yet. I haven't installed image fupload yet, but I assume when swfupload is ready for CCK, it has several features image fupload hasn't got. A form element to name one. And does it allow you to upload files instead of just images? Hmm, need to install and test the modele.

ufku’s picture

Yeah, just like the jQuery UI module.

Let swfupload module become a tiny module that checks swfu library existance and includes it.
(current functionality may be moved into a separate module which is included in the same package)

So, one can code something like this:

//include the library by executing swfupload_on (or some other function name)
if (module_invoke('swfupload', 'on')) {
  ...making sure swfu is on, here we include our swfu handling script.
}
skilip’s picture

Status: Active » Closed (won't fix)