晋太元中,武陵人捕鱼为业。缘溪行,忘路之远近。忽逢桃花林,夹岸数百步,中无杂树,芳草鲜美,落英缤纷。渔人甚异之,复前行,欲穷其林。 林尽水源,便得一山,山有小口,仿佛若有光。便舍船,从口入。初极狭,才通人。复行数十步,豁然开朗。土地平旷,屋舍俨然,有良田、美池、桑竹之属。阡陌交通,鸡犬相闻。其中往来种作,男女衣着,悉如外人。黄发垂髫,并怡然自乐。 见渔人,乃大惊,问所从来。具答之。便要还家,设酒杀鸡作食。村中闻有此人,咸来问讯。自云先世避秦时乱,率妻子邑人来此绝境,不复出焉,遂与外人间隔。问今是何世,乃不知有汉,无论魏晋。此人一一为具言所闻,皆叹惋。余人各复延至其家,皆出酒食。停数日,辞去。此中人语云:“不足为外人道也。”(间隔 一作:隔绝) 既出,得其船,便扶向路,处处志之。及郡下,诣太守,说如此。太守即遣人随其往,寻向所志,遂迷,不复得路。 南阳刘子骥,高尚士也,闻之,欣然规往。未果,寻病终。后遂无问津者。
| DIR:/home/bolconlineco/www/assets/plugins/plupload/ |
| Current File : //home/bolconlineco/www/assets/plugins/plupload/readme.md |
# Plupload Plupload is a cross-browser multi-runtime file uploading API. Basically, a set of tools that will help you to build a reliable and visually appealing file uploader in minutes. Historically, Plupload comes from a dark and hostile age of no HTML5, hence all the alternative fallbacks, like Flash, Silverlight and Java (still in development). It is meant to provide an API, that will work anywhere and in any case, in one way or another. While having very solid fallbacks, Plupload is built with the future of HTML5 in mind. ### Table of Contents * [Backstory](https://github.com/moxiecode/plupload/blob/master/readme.md#backstory) * [Structure](https://github.com/moxiecode/plupload/blob/master/readme.md#structure) * [File API and XHR L2 pollyfills](https://github.com/moxiecode/moxie/blob/master/README.md) * [Plupload API](https://github.com/moxiecode/plupload/wiki/API) * [UI Widget](https://github.com/moxiecode/plupload/wiki/UI.Plupload) * [Queue Widget](https://github.com/moxiecode/plupload/wiki/pluploadQueue) * [Demos](https://github.com/jayarjo/plupload-demos/blob/master/README.md) * [Building Instructions](https://github.com/moxiecode/plupload/blob/master/readme.md#build) * [Getting Started](https://github.com/moxiecode/plupload/wiki/Getting-Started) * [Options](https://github.com/moxiecode/plupload/wiki/Options) * [Events](https://github.com/moxiecode/plupload/wiki/Uploader#wiki-events) * [Methods](https://github.com/moxiecode/plupload/wiki/Uploader#wiki-methods) * [Plupload in Your Language](https://github.com/moxiecode/plupload/wiki/Plupload-in-Your-Language) * [File Filters](https://github.com/moxiecode/plupload/wiki/File-Filters) * [Image Resizing on Client-Side](https://github.com/moxiecode/plupload/wiki/Image-Resizing-on-Client-Side) * [Chunking](https://github.com/moxiecode/plupload/wiki/Chunking) * [Upload to Amazon S3](https://github.com/moxiecode/plupload/wiki/Upload-to-Amazon-S3) * [FAQ](https://github.com/moxiecode/plupload/wiki/Frequently-Asked-Questions) * [Support](https://github.com/moxiecode/plupload/blob/master/readme.md##support) * [Create a Fiddle](https://github.com/moxiecode/plupload/wiki/Create-a-Fiddle) * [Contributing](https://github.com/moxiecode/plupload/blob/master/readme.md#contribute) * [License](https://github.com/moxiecode/plupload/blob/master/readme.md#license) * [Contact Us](http://www.moxiecode.com/contact.php) <a name="backstory" /> ### Backstory Plupload started in a time when uploading a file in a responsive and customizable manner was a real pain. Internally, browsers only had the `input[type="file"]` element. It was ugly and clunky at the same time. One couldn't even change it's visuals, without hiding it and coding another one on top of it from scratch. And then there was no progress indication for the upload process... Sounds pretty crazy today. It was very logical for developers to look for alternatives and writing their own implementations, using Flash and Java, in order to somehow extend limited browser capabilities. And so did we, in our search for a reliable and flexible file uploader for our [TinyMCE](http://www.tinymce.com/index.php)'s [MCImageManager](http://www.tinymce.com/enterprise/mcimagemanager.php). Quickly enough though, Plupload grew big. It easily split into a standalone project. With major *version 2.0* it underwent another huge reconstruction, basically [from the ground up](http://blog.moxiecode.com/2012/11/28/first-public-beta-plupload-2/), as all the low-level runtime logic has been extracted into separate [File API](http://www.w3.org/TR/FileAPI/) and [XHR L2](http://www.w3.org/TR/XMLHttpRequest/) pollyfills (currently known under combined name of [mOxie](https://github.com/moxiecode/moxie)), giving Plupload a chance to evolve further. <a name="structure" /> ### Structure Currently, Plupload may be considered as consisting of three parts: low-level pollyfills, Plupload API and Widgets (UI and Queue). Initially, Widgets were meant only to serve as examples of the API, but quickly formed into fully-functional API implementations that now come bundled with the Plupload API. This has been a source for multiple misconceptions about the API as Widgets were easily mistaken for the Plupload itself. They are only implementations, such as any of you can build by yourself out of the API. * [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. * [Plupload API](https://github.com/moxiecode/plupload/wiki/API) * [UI Widget](https://github.com/moxiecode/plupload/wiki/UI.Plupload) * [Queue Widget](https://github.com/moxiecode/plupload/wiki/pluploadQueue) <a name="build" /> ### Building instructions Plupload depends on File API and XHR2 L2 pollyfills that currently have their [own repository](https://github.com/moxiecode/moxie) on GitHub. However, in most cases you shouldn't care as we bundled the latest build of mOxie, including full and minified JavaScript source and pre-compiled `SWF` and `XAP` components, with the repository here. You can find everything you may need under `js/` folder. There are cases where you might need a custom build, for example free of unnecessary runtimes, half the original size, etc. The difficult part of this task comes from mOxie and its set of additional runtimes that require special tools on your workstation in order to compile. Consider [build instructions for mOxie](https://github.com/moxiecode/moxie#build-instructions) - everything applies to Plupload as well. First of all, if you want to build custom Plupload packages you will require [Node.js](http://nodejs.org/), as this is our build environment of choice. Node.js binaries (as well as Source) [are available](http://nodejs.org/download/) for all major operating systems. Plupload includes _mOxie_ as a submodule, it also depends on some other repositories for building up it's dev environment - to avoid necessity of downloading them one by one, we recommended you to simply clone Plupload with [git](http://git-scm.com/) recursively (you will require git installed on your system for this operation to succeed): ``` git clone --recursive https://github.com/moxiecode/plupload.git ``` And finalize the preparation stage with: `npm install` - this will install all additional modules, including those required by dev and test environments. In case you would rather keep it minimal, add a `--production` flag. *Note:* Currently, for an unknown reason, locally installed Node.js modules on Windows, may not be automatically added to the system PATH. So, if `jake` commands below are not recognized you will need to add them manually: ``` set PATH=%PATH%;%CD%\node_modules\.bin\ ``` <a name="support" /> ### Support We are actively standing behind the Plupload and now that we are done with major rewrites and refactoring, the only real goal that we have ahead is making it as reliable and bulletproof as possible. We are open to all the suggestions and feature requests. We ask you to file bug reports if you encounter any. We may not react to them instantly, but we constantly bear them in my mind as we extend the code base. In addition to dedicated support for those who dare to buy our OEM licenses, we got [discussion boards](http://www.plupload.com/punbb/index.php), which is like an enormous FAQ, covering every possible application case. Of course, you are welcome to file a bug report or feature request, here on [GitHub](https://github.com/moxiecode/plupload/issues). Sometimes it is easier to notice the problem when bug report is accompained by the actual code. Consider providing [a Plupload fiddle](https://github.com/moxiecode/plupload/wiki/Create-a-Fiddle) for the troublesome code. <a name="contribute" /> ### Contributing We are open to suggestions and code revisions, however there are some rules and limitations that you might want to consider first. * Code that you contribute will automatically be licensed under the LGPL, but will not be limited to LGPL. * Although all contributors will get the credit for their work, copyright notices will be changed to [Moxiecode Systems AB](http://www.moxiecode.com/). * Third party code will be reviewed, tested and possibly modified before being released. 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. An easy place to start is to [translate Plupload to your language](https://github.com/moxiecode/plupload/wiki/Plupload-in-Your-Language#contribute). You can read more about how to contribute at: [http://www.plupload.com/contributing](http://www.plupload.com/contributing) <a name="license" /> ### License Copyright 2013, [Moxiecode Systems AB](http://www.moxiecode.com/) Released under [GPLv2 License](https://github.com/moxiecode/plupload/blob/master/license.txt). We also provide [commercial license](http://www.plupload.com/commercial.php). |