jQuery Forum

There is no good reason to put all pages in one file. I don't know why so many developers have a fascination with this feature. Because a feature exists does not mean it has to be used.

The problems with multi-page documents are multiple. On mobile devices, they might get bigger than the device's browser can handle. Your site will likely outgrow the single document. You cannot mix single-page documents with multi-page documents, unless you use data-rel="external", and when you do so, you have effectively broke-up your site into multiple JQM sites which completely re-load as you cross the boundary between single-page and multi-page.

There's really nothing good about this.

If your reason for wanting to do this is because you want the pages to be pre-loaded and/or cached, you can accomplish that using data-dom-cache="true" and/or data-prefetch.

but how to handle page in new activity in android or transitions ? will transition still work in data-rel=external ?

I'm afraid I can't really follow your question. Can you post an example? I don't know what you saw or where. Does the jQuery Mobile demo work as you expect or not?

No, transitions will not work if you use rel="external". I haven't suggested that you should use rel="external". Just the opposite, in fact. You should make your site multi-document from the start, so that you don't later try to break it up into chunks and then have to use data=rel="external" to link between the chunks.

It sounds like you are just doing too much coding. You don't need to tell JQM to change page if you have an anchor tag going to that page.

The thought actually came to my mind because in andreoid if i do href=2.html it opens in a new activity.

The thought actually came to my mind because in andreoid if i do href=2.html it opens in a new activity.

I don't know what you mean by this. That's why I asked you to post an example. Please post an example that others can try, or at least a screenshot.

I don't use an Android device. Neither do probably half the people here, and so none of them are going to understand what you are talking about either.

I gather Android devices have something called "activities", but can't imagine what this has to do with page transitions in the browser.

Do you mean that the page opens in a new browser window?

Why are you trying to change pages using window.location.href? Why not simply use a link <a href="blahblah.html"> or if you need to do it from Javascript code, $.mobile.changePage()?

Ok, Sorry for being unable to make the point across.

now when i go to 2.html from 1.html and click the href in 2.html to come back to 1.html. it acyually loads another 1.html.

so when i press android back button i again see 2.html and then 1.html buried underneath it. 

That is simply just how jQM Works. When you request a page, it gets loaded behind the scenes then transitioned to. The old page stays loaded in the background so that you can quickly go back to it when the back button is pressed. You should write your code with this fact in-mind.


-- Kevin