Thanks Ray. I have some follow-up questions in https://stackoverflow.com/questions/27760867/tapestry-implementation .
On 4 Jan 2015, at 5:58 am, Ray Nicholus <rnicho...@widen.com> wrote: > I’ll chime in as I’ve been maintaining Fine Uploader since mid-2012, and my > employer uses it in a few of our products, each of which also use Tapestry. > > Our setup is fairly simple. We register a servlet to handle any requests > from Fine Uploader (such as the upload and delete requests for traditional > endpoints or the signature & success requests for S3 and Azure endpoints). > > > We then create a component to render the uploader and a JavaScript stack to > load the necessary client-side files. In the component’s TML, we define and > customize our Fine Uploader UI template (assuming we are using Fine > Uploader’s UI). Generally, this is done in a script tag with a type of > “text/template”, but Tapestry seems to interfere with this script tag (can’t > remember what the issue is) so we have used a hidden div for our template in > Tapestry projects. > > > The Java class associated with the component is pretty simple: just a render > method to pass any server-determined Fine Uploader options to our Fine > Uploader “glue” script that initializes the library when the component loads. > We have a few Java endpoint handler examples in our server integration > github repo for reference > (https://github.com/FineUploader/server-examples/tree/master/java) > > > > > Regarding the licensing portion of this thread: Fine Uploader is free to use > for non-commercial products. If you are developing a commercial product with > the help of Fine Uploader, we require you to purchase a commercial license > from us. This seems fair given the amount of time we put into developing and > supporting the library. Also, the licensing in no way restricts distribution > of solutions that use it. It's as simple as sharing a gist or repo on > GitHub, for example. > > > Blueimp's jquery file upload is probably ok for very basic use, but you'll > find the complete lack of support and baked in convenience methods > frustrating when you attempt something a bit more complex, such as uploading > directly to S3 from the browser, or generating scaled images client side, or > sending multiple chunks of the same file concurrently, to name a few. > > > If you have any further questions, we monitor the fine-uploader tag on > stackoverflow and respond to questions there pretty quickly. Bugs are > handled in our github project issue tracker though, of course. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
