Can we all admit this project is dead?

[snoopiesnax]

And update the website and README accordingly?

[jtara]

What can be done to get a stable Version 1.5?

Didn't you just answer your own question?

Everbody has to decide what he is doing in this state on his own.

Horse-and-buggies live on, too. Among the Amish, Mennonites, and in Colonial Williamsburg... The horse-and-buggies serve those purposes well.

[jtara]

What can be done to get a stable Version 1.5?

If you just mean to ask about the mechanics of obtaining the most stable available 1.5, there is a tag for it.

https://github.com/jquery/jquery-mobile/tree/1.5.0-rc1

[ppetree]

"I have my use case. I'm not about to drop JQM unless there is something compatible." Right and therein lies the problem. JQM is not being maintained.

The JQM widgets and controls are dated and there are better widgets and controls out there so the question becomes what purpose does JQM actually serve?

For me, it's the page and swipe management and the familiarity with jQuery.

The page management, for simple apps, is good enough. For more complex apps JQM falls apart. If you have too many .js and .css files your app will end up providing such a horrible user experience as to render the app useless. Personally, I've monkeyed around with it so much that I now have an "engine" that loads the .js and then calls the pages onload handler with something like this.

case "onboardPage": $.getScript("js/onboard.js", function( data, textStatus, jqxhr ) { onOnboardPageReady(); }).fail(function(xhr, textStatus, error) { jsLoadError(xhr, textStatus, error, "onboarding"); }); break;

Then you have the whole startup issue. What page do you show first? That too has to be "rolls royce engineered" or the entire UX goes out the window.

JQM doesn't allow you to easily manage any of these things.

Next you have the touch/swipe events. Try implementing drag/drop with JQUI and JQM. Not gonna happen unless you add in an external library and when you do that you break other things.

JQM 1.5 does nothing to address any of these issues (or at least not that I've found).

As for the business case. My business model is simple: I find new markets, I write an app to serve that market, I launch the app and then once I have a few paying customers (usually corporate or government) I sell the app off to a bigger company. I've done this 8 times.

A part of the sales process the app and server code has to go through a "code review" and buyers are becoming more and more reluctant to purchase an app that's based on what they see as "dead code" however they do like to purchase apps that are easy to maintain by their existing development staff and jquery certainly fits that requirement. So jquery giveth and JQM taketh away.

All of that brings us full circle. What do we do?

P.S. Syntactic Sugar? I've not heard that one in decades... Just wait, @ShamimIslam will bring up Hungarian Notation next! ;-)

[nhinze]

I've recently converted a fairly complex mobile app from JQM to Framework7. It was fairly painless. I had tried to get into other frameworks, but only F7 felt essentially as natural as JQM. https://framework7.io/

[ppetree]

Here it is... read the last paragraph from watusiware... https://forum.jquery.com/topic/map-and-autocomplete-only-work-after-refresh

[Bachstelze]

No hints about how to get a stable release.

[zipzit]

It drives me crazy that the jQuery Mobile tooling is dying. I too, have a whole lot of time and customers invested. I've been reviewing alternatives for my existing code... I'm having lots of trouble with menu hang at odd times. Really doesn't make my customers happy.

My use case is Progressive Web Apps (PWA), served from a single Nodejs/Express server. Single page app with 'pagination' functioning. Open Source tooling. And repos with lots of recent activity.

For me, I'm thinking Bootstrap with a pagination add-in makes a whole lot of sense...

ref:

https://github.com/twbs/bootstrap / 
https://getbootstrap.com/
https://getbootstrap.com/docs/4.3/getting-started/introduction/

https://jsfiddle.net/solodev/yw7y4wez/
https://www.solodev.com/blog/web-design/adding-pagination-to-your-website.stml
https://www.solodev.com/_/assets/pagination/jquery.twbsPagination.js

https://github.com/josecebe/twbs-pagination
http://josecebe.github.io/twbs-pagination/

Edit: Turns out that the pagination thing didn't really work well, but Bootstrap Tab navigation offers a solid opportunity for a simple replacement for existing jQuery Mobile projects. See the Vertical Pill Tab Navigation example at https://getbootstrap.com/docs/4.0/components/navs/ for more details

[ShamimIslam]

Menu hang? From what?

On Fri, Jul 19, 2019 at 7:18 PM Zip notifications@github.com wrote:

It drives me crazy that the jQuery Mobile tooling is dying. I too, have a whole lot of time and customers invested. I've been reviewing alternatives for my existing code... I'm having lots of trouble with menu hang at odd times. Really doesn't make my customers happy.

My use case is Progressive Web Apps (PWA), served from a single Nodejs/Express server. Single page app with 'pagination' functioning. Open Source tooling. And repos with lots of recent activity.

For me, I'm thinking Bootstrap with a pagination add-in makes a whole lot of sense...

ref: https://github.com/twbs/bootstrap / https://getbootstrap.com/ https://getbootstrap.com/docs/4.3/getting-started/introduction/

https://jsfiddle.net/solodev/yw7y4wez/https://www.solodev.com/blog/web-design/adding-pagination-to-your-website.stmlhttps://www.solodev.com/_/assets/pagination/jquery.twbsPagination.js https://github.com/josecebe/twbs-paginationhttp://josecebe.github.io/twbs-pagination/

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jquery/jquery-mobile/issues/8612?email_source=notifications&email_token=AAXKQTVN6X6O2HV2ZOOCDLDQAJDUHA5CNFSM4EPWIU52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2NABTA#issuecomment-513409228, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXKQTTXLT7D36RTVKYW6MDQAJDUHANCNFSM4EPWIU5Q .

[zipzit]

Menu hang? From what? …

I have absolutely no idea. I've got similar code out there with multiple customers. Once in awhile, when using a mobile phone, the menu jams. Tends to be worse on iPhones. No matter what you do the menu just hangs. In both cases, I'm using a Single Page application, with <div data-role="page"... navigation. Authentication via Ajax call to Google Auth, and confirmation via node server. Remember I'm using a Progressive Web App, so you can't really see the jqm # url in display.

I've got a hamburger menu icon that pulls out a left hand drawer with five menu selections. Sometimes the whole thing just hangs. Edit: I'm able to reproduce the failure on desktop emulator. Select each of the five menu selects in order. Then reverse. When I get to my sixth menu select (item # 4) the whole thing hangs. Home-2-3-4-5-4-lock-up. Most other combo's work just fine. I've been unable to figure out what is causing it. There are no error messages. Not seeing anything in the tail logs on server. Sometimes you can clear the menu by dragging from left of screen. Generally you have to clear Safari (iphone) or Chrome (Android) storage to clear the issue. Note: I'm using a file I picked up from JQM demos, jqm-demos.js, to manage the # menu choices... Without that file, the whole thing just hangs.

Happy to show you the details (send me an email) I don't want to hijack this issue with my troubles....

[ShamimIslam]

Have you considered using the closure transpiler to compile to ECMA3 on the iOS devices or all devices for that matter?

Also, if it' a PWA, you can use a macOS VM and test it in safari or in chrome w/ the debugger.

What version of JQM?

On Sat, Jul 20, 2019 at 1:29 AM Zip notifications@github.com wrote:

Menu hang? From what? … <#m4298357630405760119>

I have absolutely no idea. I've got similar code out there with multiple customers. Once in awhile, when using a mobile phone, the menu jams. Tends to be worse on iPhones. No matter what you do the menu just hangs. In both cases, I'm using a Single Page application, with <div data-role="page"... navigation. Authentication via Ajax call to Google Auth, and confirmation via node server. Remember I'm using a Progressive Web App, so you can't really see the jqm # url in display.

I've got a hamburger menu icon that pulls out a left hand drawer with five menu selections. Sometimes the whole thing just hangs. Not when I'm using the site in a browser, but only on a phone. I can repeat the failure on mobile devices, but I've been unable to figure out what is causing it. Generally there are no error messages. Not seeing anything in the tail logs on server. Sometimes you can clear the menu by dragging from left of screen. Generally you have to clear Safari (iphone) or Chrome (Android) storage to clear the issue.

Happy to show you the details (send me an email) I don't want to hijack this issue with my troubles....

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jquery/jquery-mobile/issues/8612?email_source=notifications&email_token=AAXKQTTWLRRHNXBJPJ2ID2DQAKPDRA5CNFSM4EPWIU52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2NHBQY#issuecomment-513437891, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXKQTTRXLZVGEZUSWOJWE3QAKPDRANCNFSM4EPWIU5Q .

[zipzit]

Oops.
1) I don't want to hijack this thread on "Can we admit this project is Dead?" with my woes and code issues. 2) Send me an email. Hint: Click on my name, you will IMMEDIATELY see an email address. Send me an email. I will immediately send you a link to the online version of my program. I don't want to place a customer's website link here in public forum.
3) I've spent a whole lot of time in Chrome debugger tools analyzing front end woes, including some heavy duty animation issues. This one has me baffled. Not sure what to look at. There is not much feedback. Edit: I'm able to reproduce the fault on desktop / chrome dev tools / toggle device tool bar icon for emulator. Select menu three bar icon. Select "Home", then second menu choice, then third menu choice, then fourth menu choice, then fifth menu choice, then fourth menu choice. At that point you will experience menu lockup. 100% repeatable.
4) No go on ECMA3 (wasn't that something from the Ghostbusters movie?) I know how to use macOS to get to iPhone via cable and use Safari tools. Not sure that is necessary.
5) I'm not trying to be ungrateful or unpleasant... I'm very appreciative of your input. I just don't want to hijack this thread too far off topic. Many thanks.

Edit: As I think about it... perhaps this menu lock up issue is way better discussed in the open over at StackOverflow with [jQuery-mobile] tag... Even if we have to do so after the fact...

Edit #2: So I've created a stand alone [jquery-mobile] question over at StackOverflow... . It took awhile to create a simple app that displayed the issue. Appreciate any feedback on the issue... thx.

[zipzit]

Follow-up. For my use case, I'm jumping over to Bootstrap and a simple sidebar menu, ref: https://github.com/zipzit/Bootstrap-SPA-Sidebar-Menu This works well with no more menu lockup.

[sedexdev]

On the subject of whether JQM is active/dead can I ask people's opinion on the following. I am about to start a module on mobile app development in my third year of a CS degree and I have just learnt that JQM is the platform we'll be learning. Should I be concerned about this? From what I've read this is not a desired industry skill/not being properly supported/basically being deprecated. Should I challenge the university on this or do people think JQM is worth teaching/learning? Thanks

[joegrist]

While you are learning JQM you could look into other nostalgic skills like fighting using a halberd or leechcraft (.... I'd push back on them)

[ppetree]

In the JQM forums the moderators are advising people to not start any new projects using JQM. That’s as close to an official statement of death as the JQM people have the guts to give.

Learning jQuery is probably a part of that course so none of that time will be wasted.

Beyond that, challenging the instructors will do little as they are incapable of changing directions at this late stage however in your end of course review it would be wise to point out they’re teaching dead technology.

[boussou]

IMHO, for teaching purpose, it may be still relevant because when learning it is better to start on simpler examples. Learning should be like adding bricks to a wall. Other existing options often has a strong dependency on a JS framework (Angular, vue etc). So it avoid requiring learning those beforehand.

JQM has the folllowing properties:

• no strong dependency except jquery of course
• does not require a build tool, does not require npm hell
• the 2 above basically mean: you can just drop a Githubissues.
• Githubissues is a development platform for aggregating issues.