I have been wanting to learn about 3D printing a long time so I really want this site to succeed but I have no previous experience with the subject.
\n", "\n", "I was wondering how can I help the site at this early stage. I thought about asking about how to get started with 3D printing but SE explicitly discourages \"easy\" questions in the private beta.
\n", "\n", "What can newbies like me do for the site at this stage besides voting questions and answers?
\n" ], "text/plain": [ "Looking at the library code, seems all events are renamed removing 'fileupload' ... so 'fileuploaddone' becomes just 'done'. It is valid for all other callbacks.\n", "look at this section:
\n", "\n", " // Other callbacks:\n",
" // Callback for the submit event of each file upload:\n",
" // submit: function (e, data) {}, // .bind('fileuploadsubmit', func);\n",
" // Callback for the start of each file upload request:\n",
" // send: function (e, data) {}, // .bind('fileuploadsend', func);\n",
" // Callback for successful uploads:\n",
" // done: function (e, data) {}, // .bind('fileuploaddone', func);\n",
" // Callback for failed (abort or error) uploads:\n",
" // fail: function (e, data) {}, // .bind('fileuploadfail', func);\n",
" // Callback for completed (success, abort or error) requests:\n",
" // always: function (e, data) {}, // .bind('fileuploadalways', func);\n",
" // Callback for upload progress events:\n",
" // progress: function (e, data) {}, // .bind('fileuploadprogress', func);\n",
" // Callback for global upload progress events:\n",
" // progressall: function (e, data) {}, // .bind('fileuploadprogressall', func);\n",
" // Callback for uploads start, equivalent to the global ajaxStart event:\n",
" // start: function (e) {}, // .bind('fileuploadstart', func);\n",
" // Callback for uploads stop, equivalent to the global ajaxStop event:\n",
" // stop: function (e) {}, // .bind('fileuploadstop', func);\n",
" // Callback for change events of the fileInput(s):\n",
" // change: function (e, data) {}, // .bind('fileuploadchange', func);\n",
" // Callback for paste events to the pasteZone(s):\n",
" // paste: function (e, data) {}, // .bind('fileuploadpaste', func);\n",
" // Callback for drop events of the dropZone(s):\n",
" // drop: function (e, data) {}, // .bind('fileuploaddrop', func);\n",
" // Callback for dragover events of the dropZone(s):\n",
" // dragover: function (e) {}, // .bind('fileuploaddragover', func);\n",
"If you have some doubts about what's happening, just look at the code inside. This library is not compressed so it is easy to see. for example
\n", "\n", "// start: function (e) {}, // .bind('fileuploadstart', func);\n",
"start callback is implemented. fileuploadstart is not.
Looking at the library code, seems all events are renamed removing 'fileupload' ... so 'fileuploaddone' becomes just 'done'. It is valid for all other callbacks.\\nlook at this section:
\\n\\n // Other callbacks:\\n // Callback for the submit event of each file upload:\\n // submit: function (e, data) {}, // .bind('fileuploadsubmit', func);\\n // Callback for the start of each file upload request:\\n // send: function (e, data) {}, // .bind('fileuploadsend', func);\\n // Callback for successful uploads:\\n // done: function (e, data) {}, // .bind('fileuploaddone', func);\\n // Callback for failed (abort or error) uploads:\\n // fail: function (e, data) {}, // .bind('fileuploadfail', func);\\n // Callback for completed (success, abort or error) requests:\\n // always: function (e, data) {}, // .bind('fileuploadalways', func);\\n // Callback for upload progress events:\\n // progress: function (e, data) {}, // .bind('fileuploadprogress', func);\\n // Callback for global upload progress events:\\n // progressall: function (e, data) {}, // .bind('fileuploadprogressall', func);\\n // Callback for uploads start, equivalent to the global ajaxStart event:\\n // start: function (e) {}, // .bind('fileuploadstart', func);\\n // Callback for uploads stop, equivalent to the global ajaxStop event:\\n // stop: function (e) {}, // .bind('fileuploadstop', func);\\n // Callback for change events of the fileInput(s):\\n // change: function (e, data) {}, // .bind('fileuploadchange', func);\\n // Callback for paste events to the pasteZone(s):\\n // paste: function (e, data) {}, // .bind('fileuploadpaste', func);\\n // Callback for drop events of the dropZone(s):\\n // drop: function (e, data) {}, // .bind('fileuploaddrop', func);\\n // Callback for dragover events of the dropZone(s):\\n // dragover: function (e) {}, // .bind('fileuploaddragover', func);\\nIf you have some doubts about what's happening, just look at the code inside. This library is not compressed so it is easy to see. for example
\\n\\n// start: function (e) {}, // .bind('fileuploadstart', func);\\nstart callback is implemented. fileuploadstart is not.
Check if the server-side uploading script returns a JSON reply - in my case it didn\\'t work when the reply was empty, but file was uploaded successfully.
\\n\\nSo, below is working for me with jQuery 1.9.1 and the newest version of the \"jQuery File Upload Plugin\" - 5.21.3
\\n\\n$(\"#fileupload\").bind(\"fileuploaddone\", function (e, data) {\\n console.log(\"fileuploaddone event fired\");\\n});\\n