jquery-mobile multi-column layout possible using grids?

I'm trying to get a multi column layout working using Jquery Mobile.

First I tried using Jquery Mobile Grids. Example can be found here: link text

Since this didn't work, I tried to workaround using plain Jquery and JqueryMobile. Example here: link text

even worse...

Question: When a link is clicked, is there a way to only update the开发者_开发知识库 middle grid using Jquery Mobile = left and right content AND header should stay (persistent)? If there isn't, what would be a "working workaround"

Thanks for help,

Regards,

Frequent

EDIT 2011-11-24: I'm setting up my own JQM plugin for multi-panel and popup-panel layouts. See Github

---

Idea 3 jQuery Mobile links to 2 different solutions that work with current version. See:

[edit] doesn't work with current version anymore. I'm considering getting back to the game and creating something from scratch http://asyraf9.github.com/jquery-mobile/

or

http://www.stokkers.mobi/valuables/multiview/page2.html

Idea 2

Plugging into page* events.

not avaliable anymore http://jquerymobiledictionary.dyndns.org/dualColumn.html

The version 0.2 was released. Plugin now works without any JS coding.

Idea 1

.page() is obsolete, but the main idea should still work with .trigger('create')

My first idea that will work with current jQuery Mobile is to never use default methods of loading the content.

This way you will create a grid of your liking and load content via your ajax calls, put loaded data in chosen containers (MUST wrap data with a container that is newly inserted into DOM) and call .page() on it. see: http://jquerymobiledictionary.dyndns.org/faq.html

This will work, but will not ever be usable by non-javascript browsers. So it messes the whole progressive enchancement of jQuery Mobile. This shouldn't happen if you plan on creating a real-life application. I did such a thing in my jqureymobiledictionary page (dictionaries are loaded via ajax, inaccessible if one has JS turned off). The main purpose was to keep dictionaries in JSON format though. I don't recommend it for an application that doesn't have developers as a main target :)