This repository has been archived by the owner on Nov 20, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
3 - Allow a <canvas> to be passed in to the API for upload #1198
Comments
rnicholus
changed the title
Allow a <canvas> to be passed in to the API for upload
3 - Allow a <canvas> to be passed in to the API for upload
May 6, 2014
rnicholus
pushed a commit
that referenced
this issue
Jun 4, 2014
…ethod - Deprecated addBlobs. - Removed addBlobs from documentation. - Redirected unit tests that called addBlobs to use addFiles instead - addFiles now handles the work of addBlobs and, of course, addFiles - re-organized addFiles TODO: accept `<canvas>` #1198
2 tasks
rnicholus
pushed a commit
that referenced
this issue
Oct 3, 2014
rnicholus
pushed a commit
that referenced
this issue
Oct 3, 2014
TODO: - canvas to addFiles unit tests - manual canvas uploading tests #1198
rnicholus
pushed a commit
that referenced
this issue
Oct 6, 2014
rnicholus
pushed a commit
that referenced
this issue
Oct 6, 2014
This feature is now complete in the 5.1.0 pre-release branch (develop). |
Is there any documentation on how to implement this anywhere? (thanks) |
Yes, we've updated the addFiles API method documentation. http://docs.fineuploader.com/branch/master/api/methods.html#addFiles |
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This would essentially add an
addCanvases
API method. This would essentially turn the<canvas>
into aBlob
using the code in Scaling module. Since we already have anaddBlobs
and anaddFiles
, maybe we should just repurposeaddFiles
to accessBlob
or<canvas>
orFile
, or<input type="file">
and deprecateaddBlobs
.Inspired by my FedEx Day Project (code/docs still need polish), and this Stack Overflow question.
The text was updated successfully, but these errors were encountered: