• PUDN用户
    了解作者
  • Java
    开发工具
  • 13.8MB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • 1 积分
    下载积分
  • 11
    下载次数
  • 2019-07-18 09:55
    上传日期
专门为kettle这款优秀的ETL工具开发的web端管理工具。 kettle作为非常优秀的开源ETL工具得到了非常广泛的使用,一般的使用的都是使用客户端操作管理,但问题是当投入生产环境使用时,动辄上百或几百个job需要管理,这时在使用客户端管理已经很难完成了。我所知道的解决方案有用命令行的调用的,操作麻烦,总之还是很难用啦,还有就是开发web端管理工具,kettle自带了一个web端管理工具,界面极其简陋不说,还很难用,基本无法投入生产环境使用,其他没留意到还有没有较好对众多job进行管理的工具。
kettle.zip
内容介绍
# 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" / rel='nofollow' onclick='return false;'> ### 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" / rel='nofollow' onclick='return false;'> ### 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" / rel='nofollow' onclick='return false;'> ### 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" / rel='nofollow' onclick='return false;'> ### 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 c
评论
    相关推荐