[00:50:49] uGoMobi: morning [00:51:04] morning frequent [00:51:20] I guess I still need to wait for my first Travis pass :-( [00:51:37] lol [00:51:48] yeah I saw that [00:51:57] frequent: thanks for the PR [00:52:16] np. Broke my application, too, so I needed an urgent fix :-) [00:52:32] should I also look into the dynamic column adding, issue.... [00:53:37] frequent: I guess we also have to look at making it still work after toggling a column via the input [00:54:28] so to revert back to "normal" untoggled-state? [00:55:35] frequent: I mean that if I load the test page and hide and show a column via the menu, that column won't be hidden anymore on resize [00:56:09] yup. [00:56:21] we could set another on/off attribute, so manually hiding (ON) and showing (OFF) would remove the setAttribute and all would be back to normal CSS [00:58:41] I would have to take a closer look at the code to say something useful about this [00:59:21] but if that resolves it... go for it :) [01:00:07] about the dynamic column.... maybe that's something that should wait until 1.4 [01:01:24] uGoMobi: ok. II will add "on/off" plus check into regarding dyn columns [01:01:24] great if you want to work on that, but be aware that we are going to make changes to the table widget for 1.4 [01:01:44] yes, I saw the NEXT widgets do look a little different ;-) [01:02:43] uGoMobi: so for 1.4 if I work with the code in NEXT, I should be ok? [01:02:46] yeah, but what I meant was making the table modes extensions [01:02:54] for the time being [01:03:12] frequent: no no [01:03:23] (full stop) [01:03:36] frequent: branch "next" is only about buttonMarkup and theming [01:04:07] frequent: actually I didn't touch table in the "next" branch [01:04:24] well, only the markup of the column toggle button [01:04:53] frequent: we will be working on the table widget on master or in a new branch [01:05:10] uGoMobi: so I just work with the code in... latest? [01:05:18] frequent: yes [01:05:30] ok. perfect. thx [01:05:49] frequent: but for the table it's a bit complicated [01:06:17] frequent: because we added the refresh method in the 1.3-stable branch only [01:07:06] frequent: that's why I really think we should first take care of making the modes extensions and then add a new refresh method on master [01:07:14] IC [01:08:07] So I will just update my fix for 1.3.2 (on/off) [01:08:22] frequent: I think that's best yeah [01:08:36] and we can merge it in 1.3-stable [01:08:40] uGoMobi: ok. [01:08:47] so you picked the right branch for the PR :) [01:08:58] (celebrates) [01:09:19] (but leaves the Travis-pass champagne in the fridge) [01:09:25] lol [01:09:56] ok. talk to you later. have a date with r.optimizer... [01:10:05] frequent: ok later [01:13:09] _|Nix|_: Ping! [01:13:26] <_|Nix|_> uGoMobi: What's up? [01:13:37] morning _|Nix|_ [01:13:54] _|Nix|_: I was looking at checkbox disabled [01:14:28] _|Nix|_: it's broken, but I can't get it fixed for some reason [01:14:49] <_|Nix|_> uGoMobi: Lemme check ... [01:15:11] _|Nix|_: wanted to change it so it toggles the ui-state-disabled class of the label [01:15:33] <_|Nix|_> uGoMobi: OK. [01:15:48] <_|Nix|_> Then you should widget: function() { return this.label; } [01:16:18] <_|Nix|_> That will give the label to the widget factory and the widget factory's default processing will add ui-state-disabled and ui-checkboxradio-disabled to that element. [01:17:11] _|Nix|_: but in _create we have $.extend( this, { label: label }); [01:17:45] _|Nix|_: ok I understand that solution [01:17:58] _|Nix|_: just don't understand why this didn't work [01:18:23] _|Nix|_: I also see some differences between how we do it for selects and checkbox/radios [01:18:56] _|Nix|_: like the select does have enable and disable methods while checkboxradio hasn't [01:19:48] <_|Nix|_> uGoMobi: ... that's because we haven't gotten around to removing them. [01:19:53] <_|Nix|_> uGoMobi: It's part of the widget review. [01:19:56] _|Nix|_: ah ok [01:20:46] _|Nix|_: shouldn't widget return the outer element (the ui-checkbox div)? [01:21:34] Returns a jQuery object containing the original element or other relevant generated element [01:21:39] I guess I was wrong [01:21:50] could be the label [01:50:21] 01[13jquery-mobile01] 15uGoMobi pushed 3 new commits to 06next: 02http://git.io/JrbMIg [01:50:21] 13jquery-mobile/06next 14fe21742 15Jasper de Groot: Checkboxradio: Fixed the disabled state. [01:50:21] 13jquery-mobile/06next 14e81f81e 15Jasper de Groot: Core: No icon pseudo element for the loader. [01:50:21] 13jquery-mobile/06next 14014aae6 15Jasper de Groot: Controlgroup: Fixed the width of button elements in horizontal controlgroups. [02:07:06] Good morning! uGoMobi Are you going to Portland? [02:07:21] agcolom: morning Anne [02:07:24] agcolom: yes [02:07:32] Excellent! Have you booked yet? [02:07:42] agcolom: yeah I did [02:07:50] which airline? [02:08:06] agcolom: actually going to have little vacation there afterwards [02:08:14] agcolom: US Airways [02:08:34] ok. Do you know is united airlines is ok? [02:08:52] (they're so much cheaper than all the other ones) [02:09:05] agcolom: I don't really know [02:09:16] Like half price compared to British Airways... [02:09:26] When do you arrive? [02:10:02] I believe US Airways and United Airllines are planning a merger [02:10:09] ok [02:10:14] for me US Airways was way cheaper [02:10:30] I arrive that tuesday in the evening [02:10:47] and staying two weeks [02:11:02] nice! [02:11:07] yeah :) [02:11:14] going to Seattle and Vancouver [02:11:32] I'm still debating whether to arrive the sunday eve or monday eve (I'll have the board meeting on the tuesday) [02:11:44] ah ok [02:12:15] Ok, I'll check with the US people this afternoon... [02:12:36] yeah, I am sure they can tell you about UA [02:12:46] I believe it's one of the biggest airlines [02:13:25] yes, I think so too, but weird how the prices change from one airline to the other... [02:13:48] yeah big difference [02:14:14] Project jQuery Mobile Phantom Master jQuery Git build #335: STILL FAILING in 9.7 sec: http://swarm.jquery.org:8080/job/jQuery%20Mobile%20Phantom%20Master%20jQuery%20Git/335/ [02:14:14] it also depends a lot on which day you fly I think [02:15:01] my flight is cheaper than returning right after the conference because I return on the same day of the week [02:15:23] (return flight is on tuesday as well) [02:23:37] yes, with BA if I return on the sunday then it's a lot cheaper as well [03:22:30] 01[13jquery-mobile01] 15uGoMobi pushed 2 new commits to 06next: 02http://git.io/sBgQbQ [03:22:30] 13jquery-mobile/06next 14d805e62 15Jasper de Groot: Removed calls to getInheritedTheme(). [03:22:30] 13jquery-mobile/06next 14aec315a 15Jasper de Groot: Dialog: Added ui-corner-all for close button. [04:01:35] _|Nix|_: I just realized that we do not only add class ui-btn-left|right to the first two links in a header, but any type of button [04:02:33] _|Nix|_: so the code that adds those classes should probably stay in .page.sections.js and not in the button widget or buttonMarkup.js [04:12:30] [13jquery-mobile] 15uGoMobi opened issue #5933: Deprecate auto-enhancement of links in toolbars 02http://git.io/4yaQRw [05:30:07] [13jquery-mobile] 15maxleiko opened issue #5934: Broken links in Listview demo (1.3.1) 02http://git.io/8KYKsA [05:30:32] uGoMobi: _|Nix|_: either of you around? [05:30:48] arschmitz: I am [05:31:16] saw you guys talking about buttons in header and button markup [05:31:29] arschmitz: yeah [05:31:43] you dont need to worry about that in the new toolbar widget it takes care of it and removes it from button markup selector [05:31:57] arschmitz: ok great [05:32:20] it calls button markup it self and is isolated in its own private method [05:32:24] arschmitz: I actually made a ticket to deprecate the feature [05:32:49] arschmitz: we have to see what $.fn.buttonMarkup will become [05:32:53] so whatever you end up doing for classes can just be added in that method [05:33:24] right i just isolated it in a private method so that method can be changed to do whatever it needs to when you finish [05:33:36] arschmitz: awesome [05:34:35] but anyway only point was dont worry about any special handeling because toolbar will take care of it [05:34:51] uGoMobi: arschmitz: can I join the discussion? [05:34:53] <_|Nix|_> arschmitz: OK. I'll remove the special handling. [05:35:01] frequent of course [05:35:02] frequent: NO! [05:35:05] <_|Nix|_> frequent: No! It is forbidden! [05:35:05] ha ha [05:35:06] lol [05:35:09] ah well... [05:35:09] ;-) [05:35:09] BAN [05:35:14] <_|Nix|_> :) [05:35:18] OPERATOR [05:35:23] (circumvents BAN) [05:35:35] <_|Nix|_> I'm'na go remove that special casing now. [05:35:41] nice [05:35:53] frequent whats up? [05:35:55] frequent: still want to say something? ;) [05:35:56] so I was wondering why there is ui-btn-left & ui-btn-right in the header. only [05:35:57] <_|Nix|_> ... and it's gone. [05:36:04] can't that be containers? [05:36:08] to hold more than one button [05:36:10] ? [05:36:31] frequent: it also works if you set that class on a controlgroup for example [05:36:43] so it can be a container [05:36:48] I'm always using a container [05:36:58] yeah header and footer just apply the classes all auto magic for you [05:37:01] or do you mean outside the header? [05:37:12] because on smartphone 1 button each looks ok, but on tablet and pc [05:37:21] it can be quite lonely on [05:37:27] ui-btn-left and ui-btn-right [05:37:58] frequent: those class only set absolute positioning [05:38:02] yup [05:38:06] s/class/classes/ [05:38:49] I guess I'm only fussing about ui-BTN-left and ui-BTN-right, when I'm adding anything inside. [05:39:28] http://jsbin.com/amozef/96 [05:40:02] uGoMobi: yup, like that [05:40:50] frequent: there are some issues with margins on the buttons [05:41:02] but I think I fixed that in branch "next" [05:41:08] tell me... [05:41:23] took me a while to fix that on my app :-) [05:41:42] in that JS bin there is an inline style on the mini controlgroup [05:41:55] to unset the margin [05:42:25] hmm (taking a note) [05:43:00] I also like switching to iconpos=notext for all buttons in the header below xyz pixels [05:43:20] real-estate-management [05:43:34] frequent: that will be really easy in 1.4 (branch "next") [05:43:49] cool. [05:44:03] although I didn't test on many platforms yet [05:45:56] frequent: then you can just add a media query with this rule for ui-btn-icon-left|right|top|bottom: text-indent: -9999px; white-space: nowrap; [05:46:19] oh and padding: 0; [05:47:08] nice. You may have to add a CSS reference to "JQM" eventually ;-) [05:48:22] CSS reference? [05:48:49] well you are replacing plenty of JS with CSS [05:48:54] teasing [05:49:07] ah ok [07:11:08] good morning [07:11:19] Morning toddmparker: [07:11:26] just remembered, we should swap in core 2.0 into next and probably master to [07:11:27] too [07:11:33] hey arschmitz - how goes? [07:11:37] good [07:11:42] its allready in master [07:12:12] toddmparker: problem with core 2.0 is it no longer works with ie8 which we still support [07:12:52] toddmparker: any idea how ui is handling this? [07:13:22] arschmitz: true, more thinking that we should live with 2.0 for a while to see if any issues come up [07:13:33] we should support 1.9 and 2.0 for a while [07:13:43] yeah i think we need to support both for sure [07:13:51] just wondering what the best way to do that is [07:14:48] toddmparker: to me it almost seems like 1.9 would be the one in the library and 2.0 we should test against like we do git or any other version? [07:16:20] there are unit tests but i think there is a chance we'd uncover other issues if 2.0 was the library in next [07:16:37] we might want to switch back and forth as we go [07:16:48] yeah i was more talking about master [07:16:56] sure [07:17:09] we could use 2.0 in next and when we merge next into master, maybe switch back to 2.0 [07:17:23] you mean back to 1.9> [07:17:25] ? [07:17:32] sorry, yeah [07:17:40] yeah i think that makes a lot of sense [07:25:04] toddmparker: have lots of toolbar goodies ready to show off today [07:25:19] trying to see if i can finish tabs up enough too [07:49:50] toddmparker: arschmitz : branch next is already on core 2.0 [07:50:05] I merged master into next a couple days ago [08:01:10] [13jquery-mobile] 15AdoWebDesig opened issue #5935: Dynamic Select empty when opening second time. 02http://git.io/Sslqaw [08:07:28] 01[13jquery-mobile01] 15arschmitz created 06page-sections (+1 new commit): 02http://git.io/vUDA7A [08:07:28] 13jquery-mobile/06page-sections 147abc720 15Alexander Schmitz: First pass at toolbar widget [09:17:28] [13jquery-mobile] 15SeanBannister opened issue #5936: Bug in documentation example "Making the panel responsive" 02http://git.io/bFBaiA [09:22:51] 01[13jquery-mobile01] 15arschmitz created 06tabs (+1 new commit): 02http://git.io/2bzX1w [09:22:51] 13jquery-mobile/06tabs 14404a8da 15Alexander Schmitz: Tabs: First pass at ui-tabs integration [09:59:44] <_|Nix|_> Cool ... I got fully reusable buttonMarkup using only string processing of classNames. [10:00:02] _|Nix|_: Nice! [10:00:35] <_|Nix|_> uGoMobi: Basically, when you call buttonMarkup it checks what classes are present, and it calculates what buttonMarkup options/values those represent. [10:01:29] _|Nix|_: that sounds good [10:25:25] uGoMobi: sorry to bother you with this... I have booked my flight, but this time, there was no mention of ESTA. I'm not sure whether this is because I'm using a different airline. Can we reuse the old ESTA form (seem to remember it was valid for 1y) [10:25:35] (or do we need to update it? [10:25:38] thank you [10:25:45] hey agcolom [10:26:03] you always need ESTA but I think it was even valid for 2 years [10:26:13] oh really? [10:26:23] that's even better! [10:26:28] didn't check yet, but I think we are good :) [10:27:18] agcolom: which airline did you book? [10:27:25] united [10:27:32] ok [10:27:36] only £750 return! [10:28:03] I think I paid something like 750 euro [10:28:18] oh that's good! [10:28:27] I am cheap ;) [10:42:28] Crap! babulina.go-nix.ca just gave up the ghost. [10:43:18] <_|Nix|_> That was me saying that ... [10:43:30] toddmparker: is there an agenda link floating around [10:43:37] I have actual meaningful things to add today o.O [10:43:43] <_|Nix|_> arschmitz: I really hope it's not the Western Digital that crashed. I'm hoping it's the power supply. [10:43:44] oh oh [10:44:00] WD doesn't crash [10:44:09] <_|Nix|_> uGoMobi: I hope not. [10:45:04] _|Nix|_: yikes [10:45:19] <_|Nix|_> *sigh* ... yeah ... and I had a lot of photos of my daughter on there :( [10:45:27] was it that drive? [10:45:35] <_|Nix|_> Yep :( [10:45:56] oh no! is it totally unrecoverable? have you checked it out yet? [10:45:58] _|Nix|_: hope your data is still fine [10:46:11] <_|Nix|_> Basically it doesn't spin up - AFAICT. [10:46:25] <_|Nix|_> Now, this may be because the power supply gave out. [10:46:30] <_|Nix|_> It was in an enclosure. [10:46:39] ah ok well fingers crossed [10:47:08] because if it wont spin up it *is* recoverable but you will need to do some serious work to get it [10:47:48] <_|Nix|_> arschmitz: I'm inclined to contact professionals. [10:47:58] oh for something like that i would [10:48:13] thats way way beyond what the average person can or should do lol [10:48:27] <_|Nix|_> arschmitz: However, I will first buy a new enclosure to rule out the possibility that it is the power supply. [10:48:42] yeah for sure you can get an enclosure for like $10 [10:49:00] <_|Nix|_> arschmitz: Yeah. I think I'll go right after the meeting. [10:49:12] hi all, just got out of my meeting [10:49:17] will make an agenda... [10:49:21] <_|Nix|_> Fortunately there's a 24h shop that sells stuff like that. [10:49:36] nice there deffinitly is not one of those around here [10:49:38] lol [10:58:32] agenda doc - https://docs.google.com/document/d/1yrVEKJuEZa4gaM_bJkwPDm49zzdnLX6LrTYhLNq_HP4/edit# [11:02:06] toddmparker: you have to +m -meeting [11:02:42] cannot send to channel [11:03:18] or -m it is I think [11:05:32] hmm [11:05:33] ok [11:05:39] wondered why it was so quiet :p [11:07:01] 01[13jquery-mobile01] 15arschmitz pushed 1 new commit to 06tabs: 02http://git.io/_VRBKQ [11:07:01] 13jquery-mobile/06tabs 141bb6905 15Alexander Schmitz: Tabs: styling [11:16:13] 01[13jquery-mobile01] 15gabrielschulhof pushed 2 new commits to 06next: 02http://git.io/c0lALg [11:16:13] 13jquery-mobile/06next 14c1ca96c 15Gabriel Schulhof: Button: Remove selectors that should really be buttonMarkup. [11:16:13] 13jquery-mobile/06next 141e2ba6f 15Gabriel Schulhof: buttonMarkup: Re-implemented to work without any $.data/setAttribute. [11:19:36] 01[13jquery-mobile01] 15arschmitz pushed 1 new commit to 06page-sections: 02http://git.io/GmuSUQ [11:19:36] 13jquery-mobile/06page-sections 14d333e8c 15Alexander Schmitz: Toolbar: add missing file [11:39:40] 01[13jquery-mobile01] 15arschmitz pushed 1 new commit to 06tabs: 02http://git.io/Gz3JFg [11:39:40] 13jquery-mobile/06tabs 14a59a0d9 15Alexander Schmitz: Tabs: Fix Content tabs demo [12:14:51] 01[13jquery-mobile01] 15johnbender pushed 5 new commits to 06content-widget: 02http://git.io/0P21DQ [12:14:51] 13jquery-mobile/06content-widget 14b44e068 15John Bender: move initial content default to _handleDestination [12:14:51] 13jquery-mobile/06content-widget 14b141b3c 15John Bender: move scrolling into content widget [12:14:51] 13jquery-mobile/06content-widget 14f3c9307 15John Bender: unify scroll bindings under navigate [12:29:54] we're going commit CRAZY around here [12:30:12] lol [12:30:33] a lot of big things being worked on [12:30:43] 3 new widgets plus all the next work [12:34:05] impressive [12:36:10] btw, if anyone is writing faq or docs and you want someone to double check, please email me. I may miss things that are committed, but I'll always be happy to check for typos or missing words :) [12:36:21] (or double words) [12:37:08] I can also check that things are ok to understand for non-native speakers [12:38:13] agcolom: awesome ill take you up on that when i get the demo and widget pages im working on finished [12:41:45] arschmitz: Excellent :) [12:47:13] 01[13jquery-mobile01] 15uGoMobi pushed 1 new commit to 06master: 02http://git.io/d-H_Cg [12:47:13] 13jquery-mobile/06master 146064163 15Jasper de Groot: Demos: Updated responsive panels CSS example. Fixes #5936. [12:47:15] Project jQuery Mobile Git build #5096: FAILURE in 15 sec: http://swarm.jquery.org:8080/job/jQuery%20Mobile%20Git/5096/ [12:47:58] 01[13jquery-mobile01] 15uGoMobi pushed 1 new commit to 061.3-stable: 02http://git.io/1DROhA [12:47:58] 13jquery-mobile/061.3-stable 14d5f995b 15Jasper de Groot: Demos: Updated responsive panels CSS example. Fixes #5936. [12:48:18] Project jQuery Mobile Git build #5097: STILL FAILING in 31 sec: http://swarm.jquery.org:8080/job/jQuery%20Mobile%20Git/5097/ [12:49:48] 01[13api.jquerymobile.com01] 15uGoMobi pushed 1 new commit to 06master: 02http://git.io/Ed3W5Q [12:49:49] 13api.jquerymobile.com/06master 141e098f1 15Jasper de Groot: Panel: removed superfluous class from responsive panel CSS example. [13:00:24] you always know when it's a commit from uGoMobi because it says "superfluous". [13:00:41] :) [13:00:57] ok that was the last time I used that word [13:01:26] redundant? [13:02:30] superfluous is my second favorit English word after flabbergasted :) [13:03:24] nice. [13:03:25] [travis-ci] jquery/jquery-mobile#334 (master - 6064163 : Jasper de Groot): The build was broken. [13:03:25] [travis-ci] Change view : https://github.com/jquery/jquery-mobile/compare/94b59a339228...6064163fdb97 [13:03:25] [travis-ci] Build details : http://travis-ci.org/jquery/jquery-mobile/builds/6640781 [13:03:35] no, it's the perfect word [13:03:54] but i can never spell it so... [13:04:19] haha [13:05:35] talking about superfluous.... _|Nix|_ arschmitz : can I remove this in "next" https://github.com/jquery/jquery-mobile/blob/next/js/widgets/forms/button.js#L69 ? [13:06:00] yes [13:06:04] ok cool [13:06:17] 01[13jquery-mobile01] 15johnbender pushed 3 new commits to 06content-widget: 02http://git.io/nAEIVg [13:06:17] 13jquery-mobile/06content-widget 146b85d78 15John Bender: move external refs to methods [13:06:17] 13jquery-mobile/06content-widget 14a1bcf42 15John Bender: move pagechange scroll enable binding to method [13:06:17] 13jquery-mobile/06content-widget 14ea0eb23 15John Bender: test _recordScroll [13:14:52] uGoMobi: about the links in toolbars, is the proposal to deprecate in 1.4 and remove in 1.5? [13:15:03] agcolom: yes [13:15:48] can people use the "new" (or future) code now and it will be fine? [13:16:42] 01[13jquery-mobile01] 15uGoMobi pushed 1 new commit to 06next: 02http://git.io/kgFJpQ [13:16:42] 13jquery-mobile/06next 14aeaec3d 15Jasper de Groot: Button: removed code for buttons in headers. buttonMarkup enhances them as buttons and the new toolbar widget will set the mini and inline options. [13:16:42] agcolom: yes [13:16:55] Perfect! Thanks! [13:18:18] Hey, I just saw a bit of the scrollback in #jquery-meeting (saw a mention while I was gone). [13:18:27] If people want to be writing 1.4 docs now, you can start. [13:18:32] Just create a 1-4 branch. [13:18:51] We can get the infrastructure setup later. [13:19:11] We do this with UI all the time. [13:19:13] scott_gonzalez: ok great, thanks! [13:19:19] johnbender: ^^^ [13:19:27] For example: https://github.com/jquery/api.jqueryui.com/tree/1-11 [13:19:44] But there's no infrastucture for 1-11 right now since it hasn't been released. [13:20:09] scott_gonzalez: got it [13:20:10] But the 1-8 and 1-9 branches are "live" branches. [13:21:36] thanks scott_gonzalez [13:22:45] [travis-ci] jquery/jquery-mobile#335 (1.3-stable - d5f995b : Jasper de Groot): The build is still failing. [13:22:45] [travis-ci] Change view : https://github.com/jquery/jquery-mobile/compare/5ba1d42ec132...d5f995bb4877 [13:22:45] [travis-ci] Build details : http://travis-ci.org/jquery/jquery-mobile/builds/6640843 [13:23:46] ls [13:23:49] :/ [13:32:22] Yippie, build fixed! [13:32:23] Project jQuery Mobile Git build #5098: FIXED in 1 min 2 sec: http://swarm.jquery.org:8080/job/jQuery%20Mobile%20Git/5098/ [13:32:23] mail: Demos: Updated responsive panels CSS example. Fixes #5936. [13:47:13] <_|Nix|_> arschmitz: I don't want Murphy to take notice, but the drive booted up with the new SATA connection. [13:47:30] <_|Nix|_> arschmitz: Siphoning stuff as fast as I can ... [13:51:37] _|Nix|_: nice yeah prioritize and get stuff off [13:52:18] <_|Nix|_> arschmitz: Step 0: /var/www/ :) [13:55:14] ha ha [15:29:54] question: https://github.com/jquery/jquery-mobile/issues/5570#issuecomment-17040014 [15:30:05] has this moved to 1.4? [15:51:58] agcolom: no it has been fixed in 1.3.1 [15:52:40] I will comment [18:36:38] [13jquery-mobile] 15jwatkin opened issue #5937: JQM Docs - 404 Not Found? 02http://git.io/9VUaRg