You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

readme.md 9.0 KiB

4 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147
  1. # Plupload
  2. Plupload is a cross-browser multi-runtime file uploading API. Basically, a set of tools that will help you to
  3. build a reliable and visually appealing file uploader in minutes.
  4. Historically, Plupload comes from a dark and hostile age of no HTML5, hence all the alternative fallbacks,
  5. like Flash, Silverlight and Java (still in development). It is meant to provide an API, that
  6. will work anywhere and in any case, in one way or another. While having very solid fallbacks, Plupload
  7. is built with the future of HTML5 in mind.
  8. ### Table of Contents
  9. * [Backstory](https://github.com/moxiecode/plupload/blob/master/readme.md#backstory)
  10. * [Structure](https://github.com/moxiecode/plupload/blob/master/readme.md#structure)
  11. * [File API and XHR L2 pollyfills](https://github.com/moxiecode/moxie/blob/master/README.md)
  12. * [Plupload API](https://github.com/moxiecode/plupload/wiki/API)
  13. * [UI Widget](https://github.com/moxiecode/plupload/wiki/UI.Plupload)
  14. * [Queue Widget](https://github.com/moxiecode/plupload/wiki/pluploadQueue)
  15. * [Demos](https://github.com/jayarjo/plupload-demos/blob/master/README.md)
  16. * [Building Instructions](https://github.com/moxiecode/plupload/blob/master/readme.md#build)
  17. * [Getting Started](https://github.com/moxiecode/plupload/wiki/Getting-Started)
  18. * [Options](https://github.com/moxiecode/plupload/wiki/Options)
  19. * [Events](https://github.com/moxiecode/plupload/wiki/Uploader#wiki-events)
  20. * [Methods](https://github.com/moxiecode/plupload/wiki/Uploader#wiki-methods)
  21. * [Plupload in Your Language](https://github.com/moxiecode/plupload/wiki/Plupload-in-Your-Language)
  22. * [File Filters](https://github.com/moxiecode/plupload/wiki/File-Filters)
  23. * [Image Resizing on Client-Side](https://github.com/moxiecode/plupload/wiki/Image-Resizing-on-Client-Side)
  24. * [Chunking](https://github.com/moxiecode/plupload/wiki/Chunking)
  25. * [Upload to Amazon S3](https://github.com/moxiecode/plupload/wiki/Upload-to-Amazon-S3)
  26. * [FAQ](https://github.com/moxiecode/plupload/wiki/Frequently-Asked-Questions)
  27. * [Support](https://github.com/moxiecode/plupload/blob/master/readme.md##support)
  28. * [Create a Fiddle](https://github.com/moxiecode/plupload/wiki/Create-a-Fiddle)
  29. * [Contributing](https://github.com/moxiecode/plupload/blob/master/readme.md#contribute)
  30. * [License](https://github.com/moxiecode/plupload/blob/master/readme.md#license)
  31. * [Contact Us](http://www.moxiecode.com/contact.php)
  32. <a name="backstory" />
  33. ### Backstory
  34. Plupload started in a time when uploading a file in a responsive and customizable manner was a real pain.
  35. Internally, browsers only had the `input[type="file"]` element. It was ugly and clunky at the same time.
  36. One couldn't even change it's visuals, without hiding it and coding another one on top of it from scratch.
  37. And then there was no progress indication for the upload process... Sounds pretty crazy today.
  38. It was very logical for developers to look for alternatives and writing their own implementations, using
  39. Flash and Java, in order to somehow extend limited browser capabilities. And so did we, in our search for
  40. a reliable and flexible file uploader for
  41. our [TinyMCE](http://www.tinymce.com/index.php)'s
  42. [MCImageManager](http://www.tinymce.com/enterprise/mcimagemanager.php).
  43. Quickly enough though, Plupload grew big. It easily split into a standalone project.
  44. With major *version 2.0* it underwent another huge reconstruction, basically
  45. [from the ground up](http://blog.moxiecode.com/2012/11/28/first-public-beta-plupload-2/),
  46. as all the low-level runtime logic has been extracted into separate [File API](http://www.w3.org/TR/FileAPI/)
  47. and [XHR L2](http://www.w3.org/TR/XMLHttpRequest/) pollyfills (currently known under combined name of [mOxie](https://github.com/moxiecode/moxie)),
  48. giving Plupload a chance to evolve further.
  49. <a name="structure" />
  50. ### Structure
  51. Currently, Plupload may be considered as consisting of three parts: low-level pollyfills,
  52. Plupload API and Widgets (UI and Queue). Initially, Widgets were meant only to serve as examples
  53. of the API, but quickly formed into fully-functional API implementations that now come bundled with
  54. the Plupload API. This has been a source for multiple misconceptions about the API as Widgets were
  55. easily mistaken for the Plupload itself. They are only implementations, such as any of you can
  56. build by yourself out of the API.
  57. * [Low-level pollyfills (mOxie)](https://github.com/moxiecode/moxie) - have their own [code base](https://github.com/moxiecode/moxie) and [documentation](https://github.com/moxiecode/moxie/wiki) on GitHub.
  58. * [Plupload API](https://github.com/moxiecode/plupload/wiki/API)
  59. * [UI Widget](https://github.com/moxiecode/plupload/wiki/UI.Plupload)
  60. * [Queue Widget](https://github.com/moxiecode/plupload/wiki/pluploadQueue)
  61. <a name="build" />
  62. ### Building instructions
  63. Plupload depends on File API and XHR2 L2 pollyfills that currently have their
  64. [own repository](https://github.com/moxiecode/moxie) on GitHub. However, in most cases you shouldn't
  65. care as we bundle the latest build of mOxie, including full and minified JavaScript source and
  66. pre-compiled `SWF` and `XAP` components, with [every release](https://github.com/moxiecode/plupload/releases). You can find everything you may need under `js/` folder.
  67. There are cases where you might need a custom build, for example free of unnecessary runtimes, half the
  68. original size, etc. The difficult part of this task comes from mOxie and its set of additional runtimes
  69. that require special tools on your workstation in order to compile.
  70. Consider [build instructions for mOxie](https://github.com/moxiecode/moxie#build-instructions) -
  71. everything applies to Plupload as well.
  72. First of all, if you want to build custom Plupload packages you will require [Node.js](http://nodejs.org/),
  73. as this is our build environment of choice. Node.js binaries (as well as Source)
  74. [are available](http://nodejs.org/download/) for all major operating systems.
  75. Plupload includes _mOxie_ as a submodule, it also depends on some other repositories for building up it's dev
  76. environment - to avoid necessity of downloading them one by one, we recommended you to simply clone Plupload
  77. with [git](http://git-scm.com/) recursively (you will require git installed on your system for this operation
  78. to succeed):
  79. ```
  80. git clone --recursive https://github.com/moxiecode/plupload.git
  81. ```
  82. And finalize the preparation stage with: `npm install` - this will install all additional modules, including those
  83. required by dev and test environments. In case you would rather keep it minimal, add a `--production` flag.
  84. *Note:* Currently, for an unknown reason, locally installed Node.js modules on Windows, may not be automatically
  85. added to the system PATH. So, if `jake` commands below are not recognized you will need to add them manually:
  86. ```
  87. set PATH=%PATH%;%CD%\node_modules\.bin\
  88. ```
  89. <a name="support" />
  90. ### Support
  91. We are actively standing behind the Plupload and now that we are done with major rewrites and refactoring,
  92. the only real goal that we have ahead is making it as reliable and bulletproof as possible. We are open to
  93. all the suggestions and feature requests. We ask you to file bug reports if you encounter any. We may not
  94. react to them instantly, but we constantly bear them in my mind as we extend the code base.
  95. In addition to dedicated support for those who dare to buy our OEM licenses, we got
  96. [discussion boards](http://www.plupload.com/punbb/index.php), which is like an enormous FAQ,
  97. covering every possible application case. Of course, you are welcome to file a bug report or feature request,
  98. here on [GitHub](https://github.com/moxiecode/plupload/issues).
  99. Sometimes it is easier to notice the problem when bug report is accompained by the actual code. Consider providing
  100. [a Plupload fiddle](https://github.com/moxiecode/plupload/wiki/Create-a-Fiddle) for the troublesome code.
  101. <a name="contribute" />
  102. ### Contributing
  103. We are open to suggestions and code revisions, however there are some rules and limitations that you might
  104. want to consider first.
  105. * Code that you contribute will automatically be licensed under the LGPL, but will not be limited to LGPL.
  106. * Although all contributors will get the credit for their work, copyright notices will be changed to [Moxiecode Systems AB](http://www.moxiecode.com/).
  107. * Third party code will be reviewed, tested and possibly modified before being released.
  108. These basic rules help us earn a living and ensure that code remains Open Source and compatible with LGPL license. All contributions will be added to the changelog and appear in every release and on the site.
  109. An easy place to start is to [translate Plupload to your language](https://github.com/moxiecode/plupload/wiki/Plupload-in-Your-Language#contribute).
  110. You can read more about how to contribute at: [http://www.plupload.com/contributing](http://www.plupload.com/contributing)
  111. <a name="license" />
  112. ### License
  113. Copyright 2013, [Moxiecode Systems AB](http://www.moxiecode.com/)
  114. Released under [GPLv2 License](https://github.com/moxiecode/plupload/blob/master/license.txt).
  115. We also provide [commercial license](http://www.plupload.com/commercial.php).