multi column layout with tablet devices

[abhisec]

currently the only means of creating a navigation column and a content column layout on tablet devices is by using custom CSS. This is error prone when using other libraries like drawing with raphael. There is splitview and multiview plugin but both modified core JQM code which makes it impossible to use latest rc1 unless we change the code. We should add multi column layout support to JQM for better handling tablet devices, rather than expanding the widgets to fit the screen size.

[frequent]

@abhisec - it's tricky to fiddle multi-column layouts into JQM, because with more than one active page on the screen at a minimum you need a changePage parameter telling JQM where to load pages on transitions and not to drop a page from the DOM when you are leaving it. Never mind hashchanges, proper browser back button support and deep-linking.

I started out with multiview, because I also wanted a plugin that did not modifiy JQM core. Let's say I'm not quite there yet,. but multiview is supposed to eventually be without any JQM-modifications :-)

[abhisec]

@frequent i did look at multiview and it is nice, but i had created this issue hoping this gets rolled into core JQM. Keeping track of page transitions is tricky but having an IPAD app with a form which just blows up in size to occupy the real estate on a tablet form factor is not the best solution.
That being said did you branch 1.1.0RC1 for multiview ? Good job on the plugin, but i still hope multiview or splitview is either rolled up in JQM or JQM implements its own custom logic for split layouts.

[frequent]

@abhisec - I'm working on the 1.1RC1 version plus some other improvements. Will take a little though. I guess the same holds for JQM rolling up their own solution.

[abhisec]

Any plans on picking this up for 1.2?

[frequent]

@abhisec - still sitting on the JQM 1.1 version. Tricky enough with all the fixed positoning... :-)

[abhisec]

Now that 1.1 is out of the way any plans on adding support for better layout handling in future jqm?

[frequent]

Sorry. I thought this was in another repo. I'm still working on the JQM 1.1. version of multiview. I'm rewriting parts of the navigation, so multiview can hopefully work without touching JQM core files. I also have some more features I'm adding. But I will need a few more days.

[jaspermdegroot]

@abhisec

Responsive layout for tablets has definitely high priority. It will probably be one of the first new features we are going to work on. I have added this post to https://github.com/jquery/jquery-mobile/wiki/Feature-Requests and we track this feature request by its label.

[frequent]

@uGoMobi: 1.Future sure sounds flexible :-D

[jaspermdegroot]

@frequent - LOL ... still better than no future, right? :-)

[abhisec]

Thanks for tracking this. Do we have any published roadmap with probable dates?

[abhisec]

Why was this issue closed and the one it links to is closed as well? Is this dropped?

[abhisec]

@uGoMobi @frequent why did we close all issues related to tablet layout support? This issue is the oldest one and should be kept open with others linked to it if needed, but i think we should still track this?

[toddparker]

@abhisec - No, it's not been dropped but we close all feature requests until we are ready to work on them to keep the clutter down in the tracker. We're going to work on this for 1.3 and 1.4.

[abhisec]

@toddparker @uGoMobi @frequent hey guys this should be bumped up in priority if we can as if we go for low hanging stuff like adding an extra class like ui-responsive we have an option of using JQM as a high level responsive css container similar to bootstrap with the added benefit of having jqm widgets. If there is a responsive flexible grid we don't have to look elsewhere and build nicer apps.

[frequent]

@abhisec: 1.3/1.4 is much better priority-wise, than 1.Future we originally had, don't you think ;-)

[jaspermdegroot]

@frequent - I like your positive view :)

@abhisec - just changed the milestone from 1.4 to 1.3

[abhisec]

this is much better. i am seeing a scramble where people are wanting to use JQM but the pseudo responsiveness is making people whip up a lot of glue media queries. addition of basic responsiveness will be huge.

[jaspermdegroot]

I might have to do a bit expectation management here.
What we planned for 1.3 is making the grid function a real widget, add some more grids (like 33/66) and responsive grids (see also #4955).
Multiple panes is something else we look into, but far more complicated. So don't expect that for 1.3.

[frequent]

@uGoMobi: And I was starting to think you had a panel-widget up in your sleeve :-D

[abhisec]

I think having more grids and responsive grids is a very good start. That being said is it possible to think on lines of pure grid model like bootstrap or zurb?

[jaspermdegroot]

We opened a new ticket for adding grids (#5164). We keep this ticket for multiple panes which is in the roadmap for 1.6.

[arschmitz]

closing this only because its a feature request 2 versions away and we have a policy of not keeping feature requests open