Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JQuery Mobile Framework Announced

jquerymobile.com

Post reply on HN
Print view View original

41–50 of 61 posts

Re: JQuery Mobile Framework Announced

#41

Post by newman314 »

mortenjorck wrote: post #18
jsdalton wrote: post #16

The initial designs look outstanding: http://jquerymobile.com/designs/

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.

Re: JQuery Mobile Framework Announced

#42

Post by patrickaljord »

mixmax wrote: post #39
patrickaljord wrote: post #36

Earlier quoted context omitted.

Youtube and other google apps don't support IE6, not to mention many other big traffic web apps and web sites (including 37signals apps).

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.

Re: JQuery Mobile Framework Announced

#43

Post by dcurtis »

mrkurt wrote: post #27
dcurtis wrote: post #21

Earlier quoted context omitted.

"jQTouch and Sencha Touch are doing mobile web development a great disservice by only supporting the latest-and-greatest WebKit platforms." How is focusing on the future doing a disservice to anyone? We're at the very beginning of the mobile-optimized web, and the future is still unclear. There's still room to define it. Supporting the equivalent of IE6 on mobile devices seems like a waste of time to me, especially a…

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.

Re: JQuery Mobile Framework Announced

#45

Post by Encosia »

raganwald wrote: post #9
jeresig wrote: post #3

To 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…

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...

jQTouch has a great looking website/demo and was very exciting a year or so ago, but I'll be happy to see a robust alternative. After having used jQTouch to implement iPhone-specific views for a couple sites, I won't use it again.

jQTouch could have preempted the possibility of jQuery Mobile being viable in the first place, but it stagnated instead. The jQuery team can't be blamed for that.

Re: JQuery Mobile Framework Announced

#46

Post by detst »

raganwald wrote: post #40
voidfiles wrote: post #17

Earlier quoted context omitted.

Besides what jresig has already said, it's okay for there to be many answers to the same question. It's just like having two open source rendering engines, at least, Mozilla, and Webkit, that don't cannibalize one another. I don't think two approaches to mobile using jQuery will cannibalize one another.

I did not say that there shouldn't be multiple answers to the question, however if you're starting a new project today, you don't have a choice between A and B, you have a choice between something here today and something else promised Real Soon Now. Naturally, the one promised Real Soon Now is extremely shiny, it supports every browser, and it hasn't made any compromises to do so. This kind of situation forces peopl…

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.

Re: JQuery Mobile Framework Announced

#47

Post by julianz »

aaronbrethorst wrote: post #7

This 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/ )

Wow - in Chrome on Windows 7, that Sproutcore sample page uses 40% of one core of an i7 just sitting there doing nothing. Hopefully that doesn't carry over to a mobile Webkit browser as well...

Re: JQuery Mobile Framework Announced

#48

Post by toddheasley »

raganwald wrote: post #9
jeresig wrote: post #3

To 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…

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)?

Re: JQuery Mobile Framework Announced

#49

Post by toddheasley »

Encosia wrote: post #45
raganwald wrote: post #9

Earlier 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...

jQTouch has a great looking website/demo and was very exciting a year or so ago, but I'll be happy to see a robust alternative. After having used jQTouch to implement iPhone-specific views for a couple sites, I won't use it again. jQTouch could have preempted the possibility of jQuery Mobile being viable in the first place, but it stagnated instead. The jQuery team can't be blamed for that.

I'm guessing that jQTouch maybe never had any ambition to address the need that jQuery Mobile is hoping to address. It was clever, and it was first. Credit where due. But it was always a toy. Modern mobile JavaScript frameworks can't ignore the need for a true touch event model. Thank god John and his team are writing one, because (1) we pretty much know it will be good and (2) I sure as he'll wasn't going to write one.

Re: JQuery Mobile Framework Announced

#50

Post by raganwald »

detst wrote: post #46
raganwald wrote: post #40

Earlier quoted context omitted.

I did not say that there shouldn't be multiple answers to the question, however if you're starting a new project today, you don't have a choice between A and B, you have a choice between something here today and something else promised Real Soon Now. Naturally, the one promised Real Soon Now is extremely shiny, it supports every browser, and it hasn't made any compromises to do so. This kind of situation forces peopl…

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. It has no performance trade-offs. It is effortlessly compatible with mobile devices back to the Radio Telephones of the 1970s. And its programming model is intuitive, flexible, and powerful with no learning curve.

How can you resist waiting? What project is so urgent that you take a chance targeting jQTouch when it will obviously be made extinct by jQUery Mobile? So an announcement has a chilling effect on framework use, that's what I meant.

Alas, no way around it, you can't drum up support for it without perturbing the environment a little.

Post reply on HN