Forums

YUI does not, at this time, appear to be intending a separate 'Mobile' version of the library, though on Mobile you'll want to be a bit more selective about module imports than you might be on the desktop. I expect guidelines to aid with this will be forthcoming, possibly even from myself since I have a mobile project on the near horizon.

However, there is support for touch events since 3.2 (I believe) and 3.3 is adding an event-gestures module which works equally well with touch and mouse events.

At YUIConf this year there were several presentations on YUI Mobile, but those videos are not online just yet.

Hi,

We don't currently intend to treat the mobile space as a separate "branch". I've tried to highlight some of the reasoning behind this in my recent talk for YUIConf: "A phone, a tablet and a laptop walk into a bar...; YUI's take on mobile development.", which should be available pretty soon.

We wanted to address it in terms of specific features (touch/gestures, css transitions, offline caching, single page history/state management, etc.) and constraints (tighter kweight requirements, tighter runtime performance, alternate UIs) - which are rolled into a common library so they can be used in any environment (because most, if not all of them, can apply to any environment).

The idea is to have a consistent set of features and a shared API which can be used across environments (which now also includes the server. See http://yuilibrary.com/gallery/show/nodejs). For example, the ability to leverage touch and gestures on the desktop when they become available, or the ability to leverage CSS transitions on the desktop - in short, the ability to use any piece of the library, regardless of which device you're targeting.

3.2.0 was our initial step in this direction, with the addition of some features which are generally grouped under the "mobile" tag such as:

a) Touch/gesture support:

http://developer.yahoo.com/yui/3/event/#touch
http://developer.yahoo.com/yui/3/exampl ... sture.html

b) A ScrollView widget:

http://developer.yahoo.com/yui/3/scrollview/

c) CSS based transition support

http://developer.yahoo.com/yui/3/transition/

d) Refactoring DD to be built on top of gestures so it works with mouse and touch based input.

http://developer.yahoo.com/yui/3/exampl ... -drag.html

This in turn means things like Slider, built on DD, work on a touch device (for free, if you will):

http://developer.yahoo.com/yui/3/exampl ... clean.html

The same applies to the rest of the library's utilities and widgets - they work in both "desktop" environments, and "mobile" environments, across the A-Grade browsers. You can hit the examples above on your mobile device as well as your laptop (which is kind of mobile too really), or your desktop.

On the "constraint" side of things, to try and address the much tighter kweight constraints of mobile devices, we also added conditional loading (and broke up some modules, such as dom-style, to use it) so that we wouldn't need to serve IE style normalization code for example, to non-IE browsers (Mobile Webkit or otherwise). I think there's further optimizations we need to make here to tighten the runtime and kweight metrics further.

Feel free to file requests for features (or constraints) you think need to be filled out moving forwards.

Regards,
Satyen

I think all the touch capability listed above is great .. but IMO it doesn't make it any easier (and so doesn't really get us any closer to) developing apps for the mobile space. I'd like a controller framework that realises different views as divs, that stacks them in the one page and manages the navigation between different views by sliding/transitioning them into the viewport as required (with standard navigation controllers). This is what Sencha/JQueryMobile/iUI does, and so lifts that development burden from me.

Without YUI providing such a controller, I have to either develop it from scratch or source it from a dedicated mobile framework. If I source it from another framework, am I then likely to use all the YUI goodness for it's touch capability? Probably not. I'd stick with the framework I'm using.

My guess is we have no mobile (as in phone) apps using YUI3 today, and a gizzilion sprouting from these other dedicated frameworks. I'd love to see YUI as a first choice candidate along side JQueryMobile.

Just wondering if this controller framework is still on the cards for 3.4.0, Q1?

Great - thanks Juan.