watusiware, I appreciate the quick responses! but I think you're missing what I'm getting at.
I am already using plenty of manual ajax and I am dynamically refreshing jquerymobile widgets throughout my app (and am well aware of the inconsistencies you speak of, particularly around popups :D).
The goal I am trying to achieve, is to in some cases refresh manually using my own ajax calls, but still actually change the browser navigation url. jQueryMobile has internal functionality for handling navigation changes. Their functionality is built around handling multiple browsers and devices, and I wanted to tap into that.
During our mismatched responses, I decided to dig a bit deeper into their internals (I've done a fair bit of debugging of the src) and I'm now wondering if $.mobile.urlHistory might allow me to do this. I'll take a look at that.
For me, I see jQuery Mobile as having some great virtues, but trying to do too much in one place. I see a widget framework, router, and interaction layer all wrapped into a tightly coupled package. I really want aspects of the widgets + interactions, but I want to manage some of the routing myself. I am trying to see if I can pull some of that out today (and hope that some of it gets more split out in the future).
