jQuery Forum

Hello again all,

I'm building a search-box at the top of a dynamically-generated list. Users need to have the option to search by First or Last name, so I envisioned a search bar inline with a horizontal 'checkbox/button pair' like this:

( First | Last | ? ___________________________________________________ )

Not my best ASCII art, I know :) But the general idea here is that there would be two jQM-style checkbox/buttons displayed INLINE with the text input as one contiguous item.

What is the best way to acheive this effect? Can it be done with just markup+css without destroying the cross-browser compatibility jQM provides? If I DO need to do some JS work, what procedures will I need to override, or what triggers do I need to hook to preempt/'post-empt" the normal styling done by JQM?

Thanks,

-Matt Ebel

Hello!

I'm working on a custom web-app which (I think) is going to require some modifications to our changePage() functions, and I'm hoping for a little friendly advice/best-practice suggestions/etc. Here's what I've got going on:

Our mobile suite is to consist of a 'root' page, a 'start-menu', and a 'sub-program' page. On login, users are presented with alerts/notifications/etc on their 'root' page. From here they're able to slide out a tray-style 'start menu' with collapsible sets containing the 'subprograms' available to them.

When a user selects a 'sub-program' to run, an AJAX POST is made to a specific program-module on our server, which generates a response consisting of a pre-page() data-role='page' container and its contents. Currently, I parse the response, extract the HTML data, run page() on it, and transition to the new page. (there's also potential js-code to be imported on a per-program basis, but that's a can of worms I'll open in a different thread)

Here's where the questions pop up:

Since this entire 'suite' is presented under a single url, I understand that I'll need to use some, but not all, of the functionality of jQMs hashChange and changePage() functions to maintain browser-initiated 'back' and 'forward' functionality. Also, I'd like to be able to re-create a user's 'state' (i.e. which sub-program they were in, its passed parameters, etc) from the URL alone. (I imagine "//mysite.com/mobile.html#subprog?param=p" would be a valid url+hashtag, signalling my root module to transition to the page returned by server-side execution of 'subprog.html' with one passed parameter: param=p) Problem is, I'm still relatively new to JQ/JQM, and surfing this code can be intimidating to say the least.

So, experts, chime in please: Is this a situation where I can (relatively easily) continue to use changePage(), overriding the default action taken when a link is clicked, IDing if the clicked link is part of our suite, then slightly altering the jQM defaults to bring the page into its 'sub-program' container? Or is this a situation where I'm going to need to completely bypass jQM's changePage() system and write my own code from the ground up? And what's your recommendations / suggested best-practices when it comes to overriding/modifying these functions - maybe js code at the top of my 'root' / mobile.html module? before or after loading jQM, etc?

Another question that's haunting me involves cross-platform compatibility: Are hash history changes supported in all / most modern mobile browsers? This suite is designed specifically for newer-model mobile devices, so I dont care if my BB Pearl from '08 has issues, but losing support for a major platform might scuttle the project ;)

Either way, any advice (links to threads would also be great) you can offer which will help me navigate this maze of code to produce a working solution would be much appreciated!

Thanks again for the lib, and keep up the great work!

-Matt Ebel

Hello again!

I'm trying to implement a menu system for my site using collapsible sets. The example on this page looks exactly like I want.

When I view the same page from my local copy of the v1.0 demos, this is what I see:



... Different, huh? All 4 corners of each entry are rounded!

What's going on here? Why does the same HTML markup enhanced with the same version of JQM display differently on JQMs site vs local copies of the docs?

Thanks,

Matt Ebel

Hello All,

I've been working with the JQM framework to develop a mobile version of a large web-based software package. HTML is dynamically generated by our server-side code, and I'm responsible for expanding the server-side framework to generate mobile content, as well as writing client-side javascript and css from the ground up to render/animate transitions, interactions, pop-ups, etc.

Since most of the content is generated from the server side, I get the feeling that a lot of the post-markup styling that's done by JQM could be hard-coded into my server-side framework, thereby reducing the client-side overhead...

The main thing that attracted me to the JQM framework, however, is the cross-platform compatibility - I don't want to devote the rest of my life to patching platform-specific bugs ;)

... So are there specific sub-components to jQueryMobile that could be readily removed, easily enough that it could be repeated as each new version is released? A lot of the CSS transitions won't be needed for my application, and if I can Identify the platform-specific changes that JQM makes, I can use our relatively robust server-side framework to respond to a given platform and generate the markup changes as needed.


Experts, what do you think?

Thanks again for the great work, keep it up!


-Matt Ebel


PS: I've even considered just using the css side of JQM, and writing my own code for transitions, etc... Is this a total waste of my time?

Hello,

I'm considering using jQueryMobile for a larger, dynamically created web-app. After experimenting with the various styling options provided by jQuery mobile, I have come across several specific issues which I feel could be easily resolved if I just had a list of all the API styling elements/options (i.e. data-role, data-position, etc), where they may be applied, and how.

So, where can I find the actual API -reference- for jquery mobile? The "docs/demos" does not seem to provide complete lists of all the options available, and I know this information -has- to be out here somewhere... (it -has- to! ... doesn't it?)

Thanks!

Matt Ebel