JQuery Tools 1.2 with new form builder | Hacker News Reader

JQuery Tools 1.2 with new form builder

flowplayer.org

64 pointssant0sk123 comments

To quote the license clause:

NO COPYRIGHTS OR LICENSES. DO WHAT YOU LIKE. This is the new jQuery Tools license.

Copyrights and patents are evil. They block the natural progress of development. We all know it: if people start sharing instead of owning the world would be a better place. Today money is king. This results in closed systems and poor quality and in many cases people are even seriously exploited. For businessmen nothing is enough.

That's a pretty strong statement.

And flowplayer is still GPL3/Branded

Yes! And I liked it. I'm don't 100% agree with them, but I like people/companies capable of making strong statements like that.

Releasing with this so-called license is a risky move. They should explicitly release the work into the public domain, using the words "public domain". Otherwise it's not clear (from the perspective of software licensing, which will eventually come up in the life of every project) what they mean by 'No copyrights or licenses'.

Surely it means they don't care.

This looks pretty amazing ... in Firefox. I tried Chrome, but no luck. Is that because Chrome doesn't support HTML5 as completely as Firefox?

I was wondering about browser support myself, and found this to be informative: http://www.deepbluesky.com/blog/-/browser-support-for-css3-a...

It worked pretty much most of the time in Chrome for me. There were a couple of demos that didn't work.

But this thing looks really nice. I love the website design, as well.

Interesting. Are you using Chrome for Windows, perhaps? I'm using Chrome for Mac (5.0.375.29), and all that happens when I click "See it in action" is that the page is scrolled to the top.

Yes, I am. 5.0.342.9 beta for windows

edit: Actually now I'm using 5.0.375.29 beta (I just upgraded)

and it's still pretty much working the same way

Doesn't work for me (Chrome nightly build on the Mac). Didn't work in the Chrome mac production build either.

For anything web related, no matter how slick it is, if it doesn't work on a few browsers, it won't get adoption unless you run a website that only caters to specific browsers on a specific platform (like a website that can only be accessed on an iPad device).

I get "Uncaught Error: INVALID_STATE_ERR: DOM Exception 11" in Mac Chrome 5.0.375.17. (Uh, wait...we're using HN for bug reports now?)

WebKit (Safari, Chrome etc.) has more complete and more robust HTML5 support than FF. What you're seeing is a Chrome-specific issue, as it works just perfectly in Safari.

Safari on the desktop perhaps.

All the demos I've tried so far are broken on the iPad and iPhone. Has anyone had any success with Android?

I tested it on Android 1.6. It's broken alright.

Looks like this will be awesome once the compatibility issues are fixed. Right now it's a no-go on iPad. Works well on Mac Safari and Mac FF latest versions.

I wonder if it has dependencies on mouse-overs that are killing it for iPad right now?

Disappointing to see that these don't work (seemingly at all, for me) on the iPad.

Doesn't work in Chrome either. The interesting thing is that they claim that it works everywhere: "The form works on all major browsers even in IE6"

Note to developers: If you're going to make a claim that it works everywhere, something that works with IE6 won't necessarily work on newer browsers. I think web developers will often check to make sure it works in their current browser, then check IE6. And if it works in both browsers, make the claim that it works everywhere.

Yeah I've learned the hard way that to say something works in a browser you have to test it in that browser. That version too. And with http and https (the latter sometimes behaves differently due to caching differences).

Works fine for me in Chrome on Windows, 4.1.249.1064. Mac might be on an older release or have a platform-specific issue.

I'm guessing platform specific... because the chromium builds don't work either and the nightly builds are built off of the chrome trunk. But since it doesn't work on any of the mobile browsers, I'm guessing the code might have other issues too.

Doesn't work for me in Chrome on a Mac. That's a deal-killer.

Disappointed that the "date input for humans" did not include typing a date.

Reply on news.ycombinator.com