Does anyone know if there's any source code in a public repo at the moment?
I've been asked to present a talk on this, and would like to get in early.
JQuery Mobile Framework Announced
51–60 of 61 posts
Re: JQuery Mobile Framework Announced
#52Earlier quoted context omitted.
While I laud your transparency, I lament the chilling effect this will have on existing libraries like JQTouch. jQuery Mobile isn't available today but this announcement will make a lot of people sit on their hands waiting to see how things play out in the hope that they won't invest in a dead-end platform. Oh well, not saying you shouldn't have chosen this path, just pointing out the consequences...
Is anybody using jQTouch now (before this announcement)?
Yes. "Wood & Stones" is a "Goban" for playing Go face to face with a friend on an iPad:
http://github.com/raganwald/wood_and_stones
I'm not even a novice player, so in addition to supporting Classic Go, Wood & Stones supports a number of Go variations that offer some learning benefit.
You can try it on Github Pages:
http://raganwald.github.com/wood_and_stones
It's based on jQuery, jQTouch, iGesture, and JQuery Combinators.
Re: JQuery Mobile Framework Announced
#53Earlier quoted context omitted.
A bit of iOS's proportions, a bit of WebOS's textures, a bit of Android's color – yet they've managed to keep it looking clean and unified instead of middling or compromised. Outstanding indeed.
Maybe it's just me but the inital designs still feel iPhone/iPad centric. The UI/UX for webOS are more gesture-like and I do not see that reflected here as an alternative. However, it's a good start and it is heartening to see that Palm has signed up for this.
This is great. I'm really looking forward to seeing how this is going to mesh with webOS.
Re: JQuery Mobile Framework Announced
#54To preempt a few questions that are bound to pop up: What about jQTouch? While jQTouch is a great framework and we're proud to have it as part of the jQuery community - we really wanted a mobile framework to exist that would truly support all the mobile platforms out there. We chatted with the jQTouch team and there wasn't really any interest on their end to head in that direction. It's obviously going to be a ton of…
To my knowledge jQTouch requires jQuery, which has a annoying loading lag.
Re: JQuery Mobile Framework Announced
#55Earlier quoted context omitted.
I made the point in another comment but, in the case of jQTouch, I would like to see some evidence of any real development to be stalled. It seems they've transfered focus to Sencha Touch. As for that, it's a commercial product; if anything, this announcement should accelerate their development.
Ah, I see the misunderstanding. I don't mean that it stalls framework development, I mean it stalls projects. If I'm starting a new project today for a mobile app, do I go with jQTouch today? Or do I wait and see how jQuery Mobile goes? This happens all the time in the industry. Familiarity breeds contempt, so it's easy to make a list of problems with jQTouch. But whatever is announced but not shipping has no bugs. I…
That makes more sense. I was interpreting it as getting others to contribute to those projects.
I buy that argument in theory. The problem I have is that there really isn't anything that comes close to what jQuery Mobile is trying to do. Something like this is desperately needed. Sure, Sencha Touch is trying to do something similar but I don't think it's really in any state at this point to have the effect you describe.
As for jQTouch, if it fits the requirements, I don't see people stalling projects for jQuery Mobile. If it doesn't, you're either hacking it to do what you want or rolling your own. Both will probably take considerable time.
As for me, since nothing else out there really does what I want, I decided to roll my own highly customized framework. I'll keep a close eye on, and perhaps contribute to, jQuery Mobile.
Re: JQuery Mobile Framework Announced
#56This is very exciting news, especially knowing that this significantly better-looking theme is coming to desktop JQuery UI. One of my biggest issues with JQuery UI has always been how goofy it looks in comparison to Aristo and Ace ( http://www.antipode.ca/2009/themes-sproutcore-vs-cappuccino/ )
Re: JQuery Mobile Framework Announced
#57To preempt a few questions that are bound to pop up: What about jQTouch? While jQTouch is a great framework and we're proud to have it as part of the jQuery community - we really wanted a mobile framework to exist that would truly support all the mobile platforms out there. We chatted with the jQTouch team and there wasn't really any interest on their end to head in that direction. It's obviously going to be a ton of…
This is the reason I like to use jQuery: I would never have time to take on all the headaches with supporting some of these platforms. I use jQuery so I don't have to worry about all that stuff and I can get my work done.
Re: JQuery Mobile Framework Announced
#58Earlier quoted context omitted.
I don't really relish a future where one browser engine dominates the way IE has in the past. I fully expect and hope for more viable mobile engines. Even still, jQtouch (at least, I haven't messed with the Sencha thing) is very iDevice slanted. There's "webkit" and then there's "webkit on iOS", and most tools are targeted specifically at "webkit on iOS".
The thing the differentiates WebKit from IE in a good way is that it's completely open source and it's used and built by several competing companies working together toward a common goal.
It's also behind both IE and Firefox in various ways. You're right that it would be a better dominant engine than IE was, but it's still not as good as having a nice three way competition for browser share.
Re: JQuery Mobile Framework Announced
#59Earlier quoted context omitted.
IE6 has around 7% marketshare according to this: http://www.w3schools.com/browsers/browsers_stats.asp Not supporting it is like telling one in fourteen of your customers you don't want their business. This seems like a bad idea, unless of course you have non-financial motives, such as wanting to kill off IE6 by not supporting it and driving it into oblivion.
Those are general stats, you need to look at your personal stats which might be at 0.5% or 65% and decide from there, not based on these kind of sites. Making your site work on IE will require tons of hour of work and therefor money. It'll also just not work for HTML5 apps, unless you have a second version of your site coded in flash. Make sure it's worth it.
You can't get meaningful stats unless you start out supporting IE.
Re: JQuery Mobile Framework Announced
#60To preempt a few questions that are bound to pop up: What about jQTouch? While jQTouch is a great framework and we're proud to have it as part of the jQuery community - we really wanted a mobile framework to exist that would truly support all the mobile platforms out there. We chatted with the jQTouch team and there wasn't really any interest on their end to head in that direction. It's obviously going to be a ton of…
Hi John. I work at Sencha. We haven't spoken yet, but I think I have to respond to the "disservice" comment because frankly it seems a little uncharitable (and uncharacteristic of your usual even-handed demeanor) given that Sencha is promoting jQuery use by funding Jonathan Stark's work on jQTouch including work to port jQTouch to Android.
We intend to continue to fund jQTouch work because we want to support all those developers (thousands at least) that have chosen jQTouch (and jQuery) as their platform. We will continue to support jQTouch ports to more phones and more browsers as additional browsers and platforms emerge (like the Blackberry Torch) that can support a minimal rich application experience.
As you've noted in the past, Sencha Touch takes a different approach than what you're planning to do with jQuery Mobile. It's ok to differ, but we wouldn't characterize it as a "disservice". Our belief (right or wrong) is that few people will use applications (and I emphasize that word) unless they can produce experiences that can compete with native. We've had ten years of mobile web sites with static, unresponsive, high latency user experiences that haven't interested or excited people. We want to move on from that.
Today, iOS, Android and the Blackberry Torch can support web apps that compete with native experiences (woohoo!), but by the end of the year, we'll see phones from Nokia (and more from RIM and maybe even some from Microsoft) with good HTML5/CSS3 support and fast processors and GPU's that allow everyone to have rich app experiences regardless of their choice of carrier or their geography. With the rise of $30 HTML5 Android phones from China, we see this as inexorable.
Our two projects are making different assumptions about what will most interest (and excite) end-users. I hope we can maintain an engaged (and polite) discussion as we walk these paths. Feel free to email me, would love to chat more to provide more context around our decisions. We'll also put together a blog post soon on why we're doing what we are.
Look forward to hearing from you.
-- michael