[11:01:13] Hi everyone [11:01:16] <_|Nix|_> Hey! [11:01:20] hello [11:01:27] The jQuery Mobile Team meeting is now starting [11:01:37] Hi! [11:01:44] hi [11:01:44] Hi all [11:01:49] chime in if you're here [11:02:34] will john bender be joining? [11:02:38] Hello [11:02:40] oh he will [11:02:44] hi! [11:02:45] lol [11:03:11] cool [11:03:14] gang's all here [11:03:26] Ok, I'll start with some general project updates [11:03:45] People have been asking about stats of use for jQuery Mobile [11:03:47] Web stats for jquerymobile.com [11:03:47] Monthly: ~1 million pageviews/month, 750 unique [11:03:48] Last 2 years: 14 million views, 10m unique [11:03:56] so we have some solid traffic [11:04:03] lots of international traffic: Japan, Germany, China, etc. [11:04:18] That is most interesting [11:04:38] our broad compatibility really helps us internationally [11:05:07] Next: Todd to work on device donation page - not done [11:05:11] (sorry) [11:05:16] <_|Nix|_> toddparker: 750 unique? You must mean 750k unique, right? [11:05:23] heh, yes [11:05:28] New jQM site re-design to fit into the new jQuery template - had walkthrough with Richard Worth, need access and training for Anne and Todd at a minimum. Who else wants to help with new site? [11:05:53] Let me know if you want to help with the site re-work [11:06:10] goal is to launch by SF conference in the new look and feel [11:06:11] would like to help with that [11:06:23] yeah? great! [11:06:34] Richard will get us details on the workflow [11:06:40] toddparker: nice [11:06:50] it all happens in GitHub and it published via Wordpress [11:06:55] much better template [11:07:00] is it markdown [11:07:01] ? [11:07:04] nevermind [11:07:09] I can find out for myself later [11:07:10] proceed [11:07:20] * johnbender prevents himself from bogging down the meeting [11:07:34] it can be markdown [11:07:54] ultimately, each page/post must be HTML + some meta data in JSON [11:08:16] we can use markdown and transform [11:08:40] Richard will get us access to repos and they hope to import existing content from WP for cleanup [11:08:46] will need a lot of CSS love [11:08:53] more on this soon [11:09:09] Lastly - Can we do affiliate books sales for project cash? [11:09:18] that was me [11:09:21] I will ask around for details. [11:09:27] seems like a no brainer but I don't know how to set it up [11:09:40] that is, the decision is a no brainer [11:09:44] the setup is not [11:09:53] I know the jQ project is planning on having a place to store info on all books [11:10:08] sure there will be affiliate stuff baked in there, part of the new design [11:10:14] will check that [11:10:22] sorry my browser is super slow... just to let you know the new docs site is in XML and transformed to HTML using XSLT (like UI and Core) [11:10:22] cool [11:10:35] shweet [11:10:59] yeah, anne [11:11:00] is this one and the same project? [11:11:10] want to give an update on docs? [11:11:19] So all components have to conform to a strict standard [11:11:22] uGoMobi2: separate, but related [11:11:25] ok [11:11:49] <_|Nix|_> Who's next? [11:11:56] go for it [11:11:58] Yes, this is I understand for widget/elements [11:12:10] <_|Nix|_> OK ... so: [11:12:28] <_|Nix|_> I rolled back the previous fix for the initial-page-has-dialog-hash and made a cleaner one [11:12:36] <_|Nix|_> It supports dialogs and popups off the start page. [11:12:56] sweet [11:13:06] I've started with dialogs. For each we need description , options, events, methods and theming [11:13:08] is there a PR or a change set I can check out? [11:13:09] <_|Nix|_> I implemented lazy-updating for the slider input ( max once / 100 ms ) but it doesn't seem to improve performance. [11:13:23] i think Anne was still updating us on docs [11:13:36] was the slider fix an attempt to make it slide smoother, esp on android [11:13:47] * johnbender defers to anne [11:13:55] <_|Nix|_> johnbender: Yeah ... 09232df7abcac8c673dc955c4c098f9723fe384f 659e936f0030ce69521562647b53f24fa19fe423 [11:13:58] sorry agcolom, thought you might be done :) [11:14:16] <_|Nix|_> toddparker: Yeah, but man ... it's really slow. [11:14:38] <_|Nix|_> toddparker: Even a simple absolute div dragged across the page is slow - nm a slider, with aria-data and input data and all that. [11:14:45] on the docs, we are essentially going to be taking our static html docs and porting them into a well structured XML format so people can do whatever they want with 'em [11:15:07] we can then use this XML to re-create something like the current docs, but hopefully much better [11:15:30] ok so we can pull that into the new wordpress site as well [11:15:33] starting with the dialog to get the kinks worked out sounds good to me [11:15:56] there will be a separate api "site" like api.jquerymobile.com [11:16:09] it will be linked up from the jQM site and feel integrated [11:16:10] <_|Nix|_> I'd like to talk about a few things, if we have time: 1. Do we want buttons to be able to change theme on-the-fly? #4317 2. #4340 It seems we can comment out the blur-all-other-buttons-line to improve list performance, because sloppy highlights were not found in an extensive test. [11:16:20] sort of how the jQ core API docs are now [11:16:26] ok clear [11:16:30] hold on _|Nix|_ - still finishing up docs [11:16:30] <_|Nix|_> I'm done. [11:16:35] heh [11:16:46] so…any other Q's about docs? [11:16:59] looking for help here too. lots of work to port these over [11:17:26] we might be able to use some Filament interns to help a bit [11:17:32] just if someone has time to give me info on events and methods for dialogs (see basecamp post) [11:17:47] that would be great :-) Thank you :-) [11:17:57] anyone able to help with that? [11:18:15] I can lend a hand between prs and issues [11:18:30] ok, thanks johnbender [11:18:36] ok, next! [11:18:42] _|Nix|_: back to your updates [11:19:01] <_|Nix|_> toddparker: I'm done. [11:19:09] did you land initial-page-has-dialog-hash in master? [11:19:16] <_|Nix|_> toddparker: Yep. [11:19:21] <_|Nix|_> toddparker: ... and in 1.1-stable. [11:19:25] cool [11:19:43] on lazy-updating for the slider input - was this to smooth out the drag responsiveness? [11:19:58] <_|Nix|_> toddparker: Yeah, but not much good. [11:20:03] sounds like the input updating wasn't the cuprit then? [11:20:06] <_|Nix|_> toddparker: I couldn't notice a difference ... [11:20:10] <_|Nix|_> toddparker: I don't think so. [11:20:38] might just be android's events are yucky [11:20:41] <_|Nix|_> toddparker: A page with an even slightly non-trivial layout has abysmal performance under a tight mousemove sequence. [11:20:44] anyone seen a smooth slider on android? [11:21:03] (crickets) [11:21:12] not that i recall [11:21:21] _|Nix|_: if you post a short URL we can test here on a few devices [11:21:21] <_|Nix|_> toddparker: The native one, maybe :) [11:21:24] to compare [11:21:39] <_|Nix|_> toddparker: OK ... I'll whip up the commit and put it up on babulina. [11:21:46] but otherwise, we can abandon this approach if it's not better [11:21:50] <_|Nix|_> toddparker: oK. [11:22:33] any other slider issues worth looking at while you're heads in there? [11:22:47] might be worth a quick search, esp if there are 1.1.1 or 1.2 issues tagged for slider [11:23:24] let's talk about your other 2 items in a follow up after this [11:23:26] <_|Nix|_> toddparker: Haven't really looked, and now I'm into doing the unit tests for the initial-page-has-dialog-hash ... [11:23:30] <_|Nix|_> toddparker: OK. [11:23:32] ok [11:23:36] who's next? [11:23:44] I can go [11:24:07] Decoupled events code [11:24:28] and started re-organizing the code [11:24:36] created js/events [11:24:52] had to fix the builder service to handle that [11:25:08] Discovered a circular dependency [11:25:11] yeah? [11:25:16] * johnbender raises his hand! [11:25:17] which was causing the builder service to crash [11:25:22] that was me [11:25:24] :D [11:25:36] nice one johnbender [11:25:38] congrats :) [11:25:38] fixed the service so that doesn't happen again [11:25:48] bender-proofed [11:25:50] and fixed the circular dependency [11:26:03] yah it was a hold over from the refactor [11:26:05] :D [11:26:05] :( [11:26:24] so gseguin - do you foresee any ripples with moving the JS into folders? [11:26:29] just curious [11:26:40] not anymore [11:27:00] because of the builder fixes? [11:27:04] besides people not being happy with the new directory structure [11:27:10] who? [11:27:30] I don't know, raise your hand if you don't like having subdir under js [11:27:42] http://d24w6bsrhbeh9d.cloudfront.net/photo/2989804_700b.jpg [11:27:54] :) [11:27:56] lol [11:27:57] bueller? [11:28:13] no objections? [11:28:20] guess it's unanimous [11:28:20] alright I guess no one is ferociously opposed to it [11:28:24] heh [11:28:34] so I'll continue doing that [11:28:44] i am very much in favor of it [11:28:45] for transition and forms widget [11:29:12] yeah, too many files [11:29:14] ok [11:29:16] great [11:29:20] all i was wondering is what happens with open PR's [11:29:21] then we may have to do it for css, we'll see [11:29:29] so the download builder is now 100% and just needs extra testing? [11:29:31] conflicts when trying to merge? [11:29:35] to match the directory structure [11:29:37] good point [11:29:54] is that a problem? [11:30:03] toddparker: it's definitely in a very testable shape [11:30:09] thought johnbender cleared out every last PR [11:30:11] cool [11:30:17] lol [11:30:18] all - please test [11:30:22] not quite [11:30:28] yes [11:30:28] what's so funny johnbender? [11:30:33] every last pr [11:30:44] hey, you promised [11:30:50] hopefully we'll get there [11:30:54] worst case we'll have some manual merging to do [11:30:56] issue list is still getting smaller BTW [11:30:58] talk to wilt to and scott [11:30:59] ?:D [11:31:00] http://i.imgur.com/HNXTm.jpg [11:31:02] I'm not too worried about that [11:31:04] ok, if you're not worried about it [11:31:05] lots of css/style related prs [11:31:11] <_|Nix|_> http://babulina.go-nix.ca/nix/jqm-lazy-slider/slider.html [11:31:34] yeah, uGoMobi2 hopefully can give those a look. he is thorough. [11:32:17] just let me know which ones you want me to review [11:32:31] that's it for me [11:32:40] thanks _|Nix|_ [11:32:43] uGoMobi2: any assigned to scott or wilto [11:32:46] :D [11:32:49] where should we add comments on that URL? [11:32:52] ticket? [11:32:53] my own PR's are ;) [11:33:02] yerp [11:33:06] yeah, uGoMobi2 = scott + mat [11:33:13] assigned to them i mean [11:33:21] toddparker: we need someone to get another set of eyes on his prs too though [11:33:25] they are slammed right now unfortunately. their boss is a jerk [11:33:27] (me) [11:33:31] fully realizing that you guys have a business to run [11:33:35] uGoMobi2's? [11:33:39] yah [11:33:50] my turn? [11:33:53] yep, we're going to test the heck out of his epic button PR today [11:33:58] yay! [11:33:59] actually, testing now [11:34:10] horray for interns and adobe shadow [11:34:15] sure uGoMobi2 [11:34:18] yeah well thats what i have been working on [11:34:27] that is some amazing work [11:34:35] http://ugomobi.github.com/buttons-form/ [11:34:36] select unit test gives one error btw [11:34:39] will check that [11:34:51] those test pages and the ability to quickly compare with master is very helpful [11:35:00] in my first pass, the changes look great [11:35:07] ok, thanks [11:35:13] very nice uGoMobi2 [11:35:17] if this looks ok, we'll green button it [11:35:19] and i have been reading the open PR's and issue thread regarding updatePagePadding / fixed toolbars [11:35:31] right, and... [11:35:34] thanks [11:36:17] you're just digging into that stuff now, right? [11:36:20] any Q's for us? [11:36:30] i think half can be fixed by css [11:36:47] seems like at a minimum, we can set the static default padding to line up better with the default toolbar. seems off by a few px [11:36:54] then there are all the other issues [11:36:58] good to hear [11:37:01] not yet... going to start some test with proposed fixes [11:37:02] the less JS, the better [11:37:06] see how far i get [11:37:08] ok, cool [11:37:12] we're here to test [11:37:16] just hit us with URLs [11:37:18] and then come back to you guys [11:37:19] ok [11:37:40] thats it for me [11:37:50] ok, thanks [11:37:50] scott - Slow lists issue - Scott suggested a fix in the issue, Kin will review tonight [11:38:01] don't think kinblas had a chance to look at it [11:38:14] this is the issue _|Nix|_ mentioned earlier [11:38:24] right? [11:38:59] <_|Nix|_> toddparker: IIRC he did, and he thought that it might be worth commenting out the line. dcarrith tested the commented out version on a bunch of devices - all clear. [11:39:17] <_|Nix|_> toddparker: That's why I'm thinking we might want to comment out that line, and see if the world collapses. [11:39:31] seems like this we should make the change [11:39:34] <_|Nix|_> toddparker: We can always put it back in if any smoking guns appear on the horizon. [11:39:38] scott seemed to think so too [11:39:40] yeah [11:39:54] if it's landed in master, we will see if something crops up easier [11:40:01] i say land it [11:40:01] <_|Nix|_> Yeah ... [11:40:10] and pick it into 1.1-stable [11:40:14] ?shipit [11:40:14] http://wil.to/_/button.gif [11:40:56] what is the link to that issue/PR [11:41:20] <_|Nix|_> toddparker: https://github.com/jquery/jquery-mobile/issues/4340#issuecomment-6119281 [11:41:21] ★ Issue #4340 on jquery-mobile (mruffolo; 3w, 6d ago): slow response when clicking item in large listview on mobile devices [11:41:58] _|Nix|_: can you easily benchmark the list perf for clicks on the "list perf page" with 300+ items for 1.0.1, 1.1.0 and master post this change [11:42:07] i want to see if we're back to where we were [11:42:18] <_|Nix|_> toddparker: OK ... I can give it a shot. [11:42:33] _|Nix|_: we have existing perf stuff [11:42:40] but it's in the website repo [11:42:47] for the list perf [11:42:48] yeah, mind pointing him to the tools johnbender [11:42:54] sure [11:43:05] <_|Nix|_> Alright ... tools! [11:43:06] <_|Nix|_> :) [11:43:07] this is the biggest issue for 1.1.1 [11:43:17] so be good to know if we're ok again for sure [11:43:26] _|Nix|_: don't get too excited they are fairly rudimentary [11:43:38] <_|Nix|_> :) [11:43:59] heh [11:44:03] alrighty [11:44:11] JasonDScott: want to go? [11:44:20] https://github.com/jquery/jquery-mobile/issues/2159 - working on a fix that is not specific to BB [11:44:20] https://github.com/jquery/jquery-mobile/issues/4001 - Still working on solution for all platforms [11:44:21] ★ Issue #4001 on jquery-mobile (jasondscott; 1m, 3w ago): Page flashes after transition is complete on BlackBerry 7.1 [11:44:25] _|Nix|_: https://github.com/jquery/jquerymobile.com/tree/master/speed [11:44:25] ★ Issue #2159 on jquery-mobile (robberry; 10m, 1w ago): Navbar wrapping on Blackberry OS 5 [11:44:37] Both of these issues are BB specific [11:45:03] boo [11:45:12] I have fixes that work on the BB but break other platforms so I am still trying to find the right fix for all [11:45:16] kidding [11:45:33] https://github.com/jquery/jquery-mobile/issues/2159 [11:45:33] ★ Issue #2159 on jquery-mobile (robberry; 10m, 1w ago): Navbar wrapping on Blackberry OS 5 [11:45:37] box model tomfoolery [11:45:51] JasonDScott: #2159 navbar issue is same as IE7 i think [11:45:51] ? [11:46:10] uGoMobi2: maybe you can work with JasonDScott on this when you finish up those other CSS items [11:46:15] I will look into the IE7 one too [11:46:42] widths are calculated wrong for some reason on BB5? [11:46:44] i references the related issues there (#2159) [11:46:53] toddparker: we talked about not putting in the backface visibility in css, could we do it bb specific in js [11:46:53] ? [11:47:00] grids don't have padding or margin so I have no ideas why the float would break [11:47:12] subpixel problem [11:47:22] ah, fun [11:47:25] It is odd, adding a border fixes the problem [11:47:32] and it is not an issue in the header [11:47:33] round up the % width of the grid block [11:47:56] its an issue everywhere where you use the navbar [11:47:59] so 50% rounds up to... [11:48:18] depends on total available width [11:48:27] seems like BB needs it to sum to less than 100% [11:48:29] if that is an odd number of pixels [11:48:35] gotcha [11:48:40] on BB5 because a 5px scrollbar maybe [11:49:16] so it the screen is 401 pixels, it calculates the width to be 201 x 2 = 402 = broken float? [11:49:28] exactly [11:49:33] smart [11:49:51] so this is a Q in general [11:50:02] and all other browsers leave a gap because they prevent the wrapping [11:50:02] i don't want to add JS like this ticket suggests [11:50:08] thats another open issue :) [11:50:11] http://www.filamentgroup.com/examples/charting_v2/visualize.jQuery.jsFailed to load resource: the server responded with a status of 403 [11:50:14] toddparker: ^ [11:50:15] boo! [11:50:18] no JS and no tables! [11:50:41] i was thinking of using a pseudo selector that BB5 and IE7 dont understand [11:50:41] we can consider adding a class somewhere for BB% that would allow styles to be scoped like this [11:50:47] to make adjustments [11:50:48] but it's pretty tacky/ugly [11:51:00] that would be ideal uGoMobi2 [11:51:10] :last-child for example [11:51:20] <_|Nix|_> johnbender: I get that file ... [11:51:23] JasonDScott: can you see if there is something we could scope against that would only work in BB5? [11:51:30] orly [11:51:43] actually, what uGoMobi2 said is better [11:51:58] so we set the core styles to be on the small side [11:52:06] _|Nix|_: very very odd [11:52:11] JasonDScott already had a look at BB developers site at what css selectors BB5 supports [11:52:16] then "fix" it to the correct widths in newer/better browsers [11:52:16] but its not complete [11:52:27] you have complete list? [11:52:30] :/ [11:52:46] just concerned about adding a lot of cruft here for old browsers [11:52:52] so we should tread lightly [11:53:18] i agree [11:53:19] though I wonder if we could just set this to be a bit small across the board and it would round up on better browsers? [11:53:28] worht trying [11:54:07] if you want to make a test page JasonDScott that sets the widths of the various grids to be as close to the whole number while still not wrapping in IE 7 and BB5, I can test [11:54:30] we need a text page that lets us easily see if there is 1px left of on the right [11:54:32] Ok [11:55:39] cool [11:55:41] last item [11:55:44] the issue with the gap after last button can be solved with negative margin on the button (not the grid block) maybe [11:56:03] https://github.com/jquery/jquery-mobile/issues/4001 [11:56:03] ★ Issue #4001 on jquery-mobile (jasondscott; 1m, 3w ago): Page flashes after transition is complete on BlackBerry 7.1 [11:56:16] good idea uGoMobi2 [11:56:36] on the flashing issue, this still needs a look across the board to see if we can improve this [11:56:50] hoping to get scott jehl's eyes on this and the fixed toolbar jumping issue soon [11:56:59] let's wait on this for now [11:57:18] you can add the note about back face to the docs if you haven't already jason [11:57:30] but let's wait on and CSS/JS changes for now [11:57:40] maybe we can fix this for everyone by giving it a fresh look [11:57:46] Ok, which page on the docs? transitons? [11:58:02] yes, think that's the best place for it [11:58:21] find a place halfway down for a H2 and sentence or two [11:58:45] Should it be BB specific or to fix the flash in general [11:58:47] ? [11:58:50] this can be stated broadly - this may improve smoothness or flashing across browsers, but test for memory issues [11:59:03] Ok [11:59:08] you could even create a demo page that copies the transition page and adds that style rule to the head [11:59:23] you'd need to link to it via rel=external [11:59:29] to force the rule into play [11:59:44] link to that from the blurb for easy testing/demoing [12:00:13] ok, looks like we used a full hour but this was a great checkin everyone [12:00:48] i'll look thru the 1.1.1 issues to see if we need to hunker down on any specific ones [12:01:04] let's shoot to have 1.1.1 in good shaper in a week if we can [12:01:06] <_|Nix|_> toddparker: The only outstanding thing for me is #4317 (make theme work on-the-fly for buttons). [12:01:15] i may move some issues forward to winnow the list down [12:01:15] johnbender no update from you? [12:01:23] ah, sorry johnbender [12:01:26] no worries [12:01:36] <_|Nix|_> toddparker: Can you please milestone that issue? [12:01:36] I'm just doing the junit grunt plugin [12:01:40] then moving on to prs and issues [12:01:46] nothing worth noting [12:01:56] very useful though :) [12:01:58] _|Nix|_: for 1.2? [12:02:10] ok, well that all good stuff [12:02:10] <_|Nix|_> toddparker: For whichever you think is appropriate ... [12:02:22] 1.2 at the soonest [12:02:27] <_|Nix|_> toddparker: So be it. [12:02:32] toddparker: _|Nix|_ is not in basecamp group [12:02:58] for email notifications [12:02:58] oh! and I'm going to clean out the branches today [12:03:07] so speak now or forever loose the remote branch [12:03:08] hehe great [12:03:14] (obviously you have local copies) [12:03:59] tagged that _|Nix|_ [12:04:08] oh, i'll add you _|Nix|_ [12:04:10] sorry [12:04:16] <_|Nix|_> toddparker: NP. [12:04:18] clean away johnbender [12:04:25] ok [12:04:32] before we sign off, any Q's from the community? [12:05:07] ^^^^^^ [12:05:08] ^^^^^^ [12:05:08] ^^^^^^ [12:05:28] while we wait for that... ok if I pull this one? https://github.com/jquery/jquery-mobile/pull/4385 [12:05:29] ★ Pull request on jquery-mobile by uGoMobi (2w, 6d ago): Link styling (theme.css) [12:06:18] yes, i think so uGoMobi2 [12:06:25] that is a good defensive move [12:06:31] i'd do it only for 1.2 (master) [12:06:42] just because it's a bigger change [12:06:47] to the theme css [12:07:08] ok, sounds like no questions. anything else before we sign off? [12:07:18] <_|Nix|_> I'm good. [12:07:47] alright, thanks everyone. awesome progress! [12:07:55] thanks for all your hard work. [12:07:59] <_|Nix|_> Alright - L8R d00ds and d00dettes! [12:08:03] heh [12:08:07] signing off [12:08:08] He ;-)