Closed groodt closed 5 years ago
On 09/05/2017 05:09 AM, Greg Roodt wrote:
Hi
Is there likely to be a release date available for the stable version of 1.5? I am aware the alpha is available, I'm just wondering if the 1.5 release has lost momentum.
I have been wondering the same thing. There hasn't been a commit on master since Jan 2, 2017: https://github.com/jquery/jquery-mobile/commits/master
An IRC jquery-mobile meeting is scheduled for tomorrow (Thursday 9/6) at 2:00 PM (Eastern Time). Can someone from the jquery-mobile development team please join in and provide an update?
Bob
Thanks Greg
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jquery/jquery-mobile/issues/8587, or mute the thread https://github.com/notifications/unsubscribe-auth/ABl-5VsqwcaLfwh_fQvHtMK-USU7_-gSks5sfQ--gaJpZM4PMp0V.
Yes there will be a new release very soon. There will also be a significant announcement about jQuery Mobile and its team either this week or next look out on both the mobile and UI blogs for more info
Yes there will be a new release very soon
Glad to hear things are still moving. I'll keep an eye out for an update in the coming week.
Was there any announcement?
Sorry we are still working on the blog post and some details that were discussed in meeting yesterday will be within next few days
will also be a significant announcement about jQuery Mobile
Excellent news!. Thanks Alex. Everyone is waiting to c the news!
I'm eagerly waiting too. I've not seen anything. Did I miss it?
@arschmitz Few days are passed, and still we have no announcement :-( How guys are you going to compete with other frameworks? Just look at Bootstrap, Polymer, ... - they have daily commits and active community.
@slavap as much as I love jQM my personal belief is that this project is on life support. It's simply not needed anymore, and I believe most devs know that. Say if you develop with Ruby on Rails, you already have turbolinks to replace the pagecontainer. Most other things in jQM you can easily do yourself with a little bit of JS/CSS, plus then you don't have to do custom builds to get rid of the endless list of widgets and excess CSS you'll never need (and which will just get in your way later down the road). The todo-list has also gotten so big that.. well, to some devs I guess it's just tempting to start fresh on something new instead. Again just my personal belief, jQM has been my girlfriend for years and will always have a special place in my heart. Thanks!
@frankie-loves-jesus For me situation is quite different, I'm using almost all widgets from jqm and that is not enough, so I have additional ones, like jquery datatables. And for example filterable selecmenu should be provided not as example, but core widget. What is really bothers me, that jqm has some "hacks" for ancient mobile browsers, like iOS5 Safari, and they have nothing to do with iOS10/11.
When will be available the blog post? ... just to understand what is happening
I started rewriting a project I did a couple of years ago and I was surprised to see jQuery Mobile hasn't been updated since. Now I'm wondering if I should move to something different. Ugh. I was at least familiar with jQuery Mobile and I'm not looking forward to learning a new framework.
Should we consider the delay of one month from the blog post announcement in a positive or negative way? What has happened in the meantime in the organisation of the project?
<bump>I have an old project that I would prefer to update rather than moving to a new framework. Any word on this? The use of earlier versions of jQuery increases this project’s attack surface.</bump>
Hi there, just wondering if very soon in weeks is relative to month or year :D (just kidding) when will it likely to release and what about "significant announcement" I know that it's a free framework and efforts are and have been made but can we please have some news even if it's bad, because other dev-teams depend on it ? thanks.
Such a shame to see JQM dying like this. We have an app based on it, and everyone who uses it loves it, but we're finding it really hard to keep it relevant when all the other frameworks are moving on so quickly. Non-native form inputs (like dropdowns/radios etc.) is where it really excels for us - it keeps the look and feel consistent across all devices - nothing comes close. We'd love to get it migrated to 1.5 but with very little documentation, no ongoing announcements and no questions being answered, it's a fruitless exercise.
An honest question; how can we (the developer community) help get it moving again?
Hi, We are in process of revamping the structure, first we are moving to slack (join here). Further, we have 1.5 ready, you can consider it to be in beta version. I have been working on updating documentation here which is mostly complete.
You can help us by opening up the issues by testing the 1.5 and opening up PR with fixes if possible. I believe that through slack it would easier to connect, discuss and fix issues that come up in testing of PR.
About blog post, @arschmitz had it ready, so he should post it soon (he is probably busy with lot of other work). It would be great if community can help us in maintaining the project by fixing existing bugs or implementing new features.
i wait the new version sooooooooooooooooooooooooooooooooooooooooo loooooooooooooooooooooooooooooooooooooooooooooooooooooooooog
Sneh
Hi, does anyone have any news on this? I have a JQM 1.45 web app that needs to be upgraded to jQuery 3.3.1.
Noticed the 1.5.0-rc1 was released in Sept, does it mean the stable 1.5.0 is impending?
@cheehow use jQuery Migrate 3.0.1 https://code.jquery.com Jqm 1.4.5 works with it, the only problem was popup, but it's not hard to fix.
Patched popup:
// See https://github.com/jquery/jquery-mobile/issues/7579
$.widget( "mobile.popup", $.mobile.popup, {
// See https://github.com/jquery/jquery-mobile/commit/d34c86ae14d4ea603357be5e326de1fb8c31dbf9#diff-1d5adb10249a8b87ebe274787293060e
// On jQuery 3.3.1 popups don't close without this fix.
_createPrerequisites: function( screenPrerequisite, containerPrerequisite, whenDone ) {
var prerequisites,
self = this;
prerequisites = {
screen: $.Deferred(),
container: $.Deferred()
};
prerequisites.screen.done( function() {
if ( prerequisites === self._prerequisites ) {
screenPrerequisite();
}
});
prerequisites.container.done( function() {
if ( prerequisites === self._prerequisites ) {
containerPrerequisite();
}
});
$.when( prerequisites.screen, prerequisites.container ).done( function() {
if ( prerequisites === self._prerequisites ) {
self._prerequisites = null;
whenDone();
}
});
self._prerequisites = prerequisites;
},
// See https://github.com/jquery/jquery-mobile/commit/a61d152a21008f3c7edc7f2415710553d625bb95#diff-1d5adb10249a8b87ebe274787293060e
_closePopup: function( theEvent, data ) {
if ( ( theEvent && theEvent.isDefaultPrevented() ) || $.mobile.popup.active !== this || !this._isOpen ) {
return;
}
this._super( theEvent, data );
},
// See https://github.com/jquery/jquery-mobile/commit/3572a655b5de1fa2bc752059b0df610b353fd67d#diff-1d5adb10249a8b87ebe274787293060e
_handleWindowResize: function(/* theEvent */) {
if ( this._isOpen && this._ignoreResizeTo === 0 ) {
if ( isOutOfSight( this._ui.container, getWindowCoordinates( this.window ) ) &&
( this._expectResizeEvent() || this._orientationchangeInProgress ) &&
!this._ui.container.hasClass( "ui-popup-hidden" ) ) {
// effectively rapid-close the popup while leaving the screen intact
this._ui.container
.addClass( "ui-popup-hidden ui-popup-truncate" )
.removeAttr( "style" );
}
}
}
});
@slavap this dint work for me. I am also using jquery 3.3.1 and jqm 1.4.5 even after applying your changes it is giving the "e.preventDefault is not a function " error but the screen is not hanging now
Hi, does anyone have any news on this? I have a JQM 1.45 web app that needs to be upgraded to jQuery 3.3.1.
Noticed the 1.5.0-rc1 was released in Sept, does it mean the stable 1.5.0 is impending?
Did you get a solution ?
The 1.5.0-rc1 didn't change the operating source code. So it is still the alpha version.
"amin007 commented on Nov 24, 2017" i wait for two year ...
@slavap @sachinya Do you know how to correct the "e.preventDefault is not a function " error?
The 1.5.0-rc1 didn't change the operating source code. So it is still the alpha version.
mmm
In the meantime there were several security fixes, but if you want to use then you have to build from source since the download builder isn't working. Adventitious, there isn't an update guide and @arschmitz doesn't want contributors to help with this.
In the meantime there were several security fixes, but if you want to use then you have to build from source since the download builder isn't working. Adventitious, there isn't an update guide and @arschmitz doesn't want contributors to help with this.
are they losing interest in continuing?
Hi
Is there likely to be a release date available for the stable version of 1.5? I am aware the alpha is available, I'm just wondering if the 1.5 release has lost momentum.
Thanks Greg