[00:00:14] in its present state, it will be undesirable in the core because libxml sucks and DOM parsing would add extra complexity level. it would better be implemented as a parser option [00:02:09] preilly, I had mobile cookies on mw.org - now I can't disable them by switching to desktop site and always getting redirected to the mobile [00:10:06] there does seem to be some bug relating to mobile/desktop view [00:10:34] we've gotten a few complaints and I just saw it when opting into the beta [00:12:14] I've set up a mobile main page: https://m.mediawiki.org/wiki/MediaWiki [00:12:29] guess it doesn't need a download link? :P [00:18:06] For all those users trying to download MediaWiki to their phone. [00:22:54] philinje: Include the component name in the bug summary, please. [00:27:46] philinje: this still needs an update http://www.mediawiki.org/wiki/Mobile_design/Wikipedia_navigation [00:28:17] Brooke: ok [00:28:44] philinje: i need a monthly summary so that i can include it in the eng report [00:29:04] If you're curious why: https://www.mediawiki.org/wiki/User:MZMcBride/Bugs#Style [00:29:25] tfinc: i replied earlier that the last update was good until today, meaning this meeting, and it makes sense to update the status now - i will make it monthly [00:29:42] philinje: thanks [00:43:13] preilly: what did you find out from asher about GeoData ? [00:44:00] tfinc: he never had the time to talk about it [00:44:10] tfinc: but we are planning on talking about it first thing tomorrow [00:44:33] liar. [00:44:57] jorm: ? [00:45:12] oh. i wasn't talking to anyone in particular. [00:45:21] that was my "troll tourettes" kicking up. [00:45:27] jorm: ? [00:45:40] jorm: you back from portland ? [00:46:28] jah, got back to the office just before noon. [03:21:28] jrobson: I replied to you on wikitech-l. You're welcome. [03:21:54] Though some part of me still thinks I'm misunderstanding the issue, as your solution is so bad and obviously wrong... [12:33:45] Change abandoned: MaxSem; "Not the cause." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13277 [13:44:09] Hi, I'd like to have an answer to a design question about wikimedia mobile. [13:44:30] Why are the section titles used in title="..." ? [13:45:24] I find this quite invasive when browsing with a desktop browser with the tooltip that follows the mouse. [13:45:49] nobody knows for sure:) you can include your haeading in a title-less div though [13:47:22] What do you mean? The thing is that currently on WP:fr everybody is annoyed: the desktop users because of this requirement and the mobile users because the section titles aren't currently shown. [13:48:10] what do you mean by "section titles aren't currently shown"? [13:48:12] So I asked the admins to remove this title="..." stuff and no one wants to do it, because no one understands it properly. [13:48:35] Browse fr.m.wikipedia.org with a mobile. On mine, there is no section heading. [13:49:23] And I'm using the official wikipedia app. [13:49:39] you don't see "Lumière sur", "Actualités et évènements" etc? [13:49:54] yuvipanda, he said app! [13:49:56] :P [13:50:42] yes, when I use the official WP application, no such thing as the terms you mention. [13:52:23] Well, I just tried with a mobile browser, it works properly. But anyway, the whole title="..." is quite annoying on WP:fr with a desktop browser. [13:53:15] So if I understand well, the suggestion should be to make something like
_actual content_
? [13:53:53] * yuvipanda pokes his head out [13:54:01] which title="" stuff? [13:54:40] * yuvipanda is confused [13:54:42] This one: http://meta.wikimedia.org/wiki/Mobile_Projects/Mobile_Gateway#Global_Prefix [13:55:35] yeah, the title fiasco needs to be fixed [13:56:56] Fror: bug in the app's 'special' handling of the mobile main page. let me file one. [13:58:16] orrr.... [13:58:27] MaxSem: so, problem is the api is scrubbing headings when i'm passing in noheadings [13:58:30] even for the main page [13:58:37] which I don't think is the right behavior [13:58:41] since the main page is never 'sectionized' [13:58:56] and hence noheadings doesn't make sense - the heading info is never exposed anywhere! [13:59:08] well, you said you don't want them. I'm dumb, I doe what I'm told [13:59:13] Okay, so there are two unwanted behaviors. 1. The mobile app doesn't show titles properly. 2. The WP:fr has that tooltip annoyance because of the mobile integration. [13:59:35] MaxSem: can you make noheadings not touch main pages/ [13:59:36] ? [13:59:38] I'm already working on 2 [13:59:44] #1 is a bug, but what about #2? [14:00:13] yuvipanda, that would be yet another indiscriminate condition suited for just our needs [14:00:32] Fror, also a bug [14:00:35] Ok [14:00:41] fixeeeng [14:01:13] Where can I follow that bug ? [14:01:25] If it's already filed. [14:02:22] MaxSem: https://bugzilla.wikimedia.org/show_bug.cgi?id=38025 [14:02:32] MaxSem: I don't think so. [14:03:10] MaxSem: The Main Page is being treated 'specially', which means it will have behavior not consistent with every other page. [14:03:57] Then we should return error if noheadings and minpage are used together [14:04:49] Thanks for the link. [14:04:50] MaxSem: we return only one section in main page, so noheadings should control weather that section has a heading or not [14:05:17] if 'Main Page' as that 'section''s heading is rendered or not [14:05:30] not affect internal s that aren't really 'section' headings [14:05:55] We never add page title to mobileview output, so this point is moot [14:06:37] MaxSem: we're treating a full 'page' as a section, so by definition this is an 'exception' [14:06:59] MaxSem: noheadings is meant to scrub headings of the sections it is giving us, not unrelated in the content [14:10:00] MaxSem: https://www.mediawiki.org/wiki/Special:ApiSandbox#action=mobileview&format=json&page=User%3AYuvipanda%2Ftest§ions=all&prop=text%7Csections§ionprop=toclevel%7Clevel considers all sections, even if they weren't actually sections [14:17:08] New patchset: MaxSem; "Remove title attribute from main page divs" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13333 [14:22:55] yuvipanda, but you should also remove noheadings from your MP calls, cause I'm gonna serve you warnngs about your reckless usage of parameters:) [14:25:22] MaxSem: noheadings -> 'no section headings repeated in the body', not 'get rid of all tags' :P [14:26:24] so if the page accidentally begins with a heading, you permit me to strip it?;) [14:27:28] MaxSem: no, i expect you to find out that that isn't a heading and leave it alone :P [14:28:09] sure, you're the one who'll train the neural network [14:28:35] MaxSem: /w/api.php?action=mobileview&format=json&page=User%3AYuvipanda%2Ftest§ions=all&prop=text%7Csections§ionprop=toclevel%7Clevel&noheadings= [14:28:38] err [14:28:42] MaxSem: https://www.mediawiki.org/wiki/Special:ApiSandbox#action=mobileview&format=json&page=User%3AYuvipanda%2Ftest§ions=all&prop=text%7Csections§ionprop=toclevel%7Clevel&noheadings= [14:28:57] MaxSem: that

is lost, despite it not being the 'beginning' of a section [14:29:33] MaxSem: no way to differentiate between from wikitext = syntax vs plain html? [14:30:31] nope. as you can see, the parser treats almost like == these headings ==, just doesn't add the edit links [14:31:05]

starts a new section, so it gets stripped [14:38:44] New patchset: MaxSem; "Ignore noheadings on the main page" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13335 [16:42:41] hey philinje [16:46:33] yuvipanda: hey [16:46:43] how's the app looking? [16:46:47] philinje: are you sure elka has an android phone? :) [16:46:51] yes [16:46:57] philinje: ah, sweet then. [16:47:20] philinje: looks pretty good, making minor(ish) fixes. When do you want to take a look? [16:47:32] any time [16:47:55] philinje: okay! [16:48:18] Brion is here too, so he could take a look [16:48:52] philinje: sweet! Making a build. [16:49:16] :) [16:49:56] philinje: https://dl.dropbox.com/u/8768784/WLMMobile-debug.apk [16:52:05] awesome [16:53:02] philinje: has a few known issue (no feedback on 'progress', map tiles loading only on edges, nearby not well integrated) [16:53:16] philinje: plus 'upload later' not yet implemented, so is settings. but the core's all there :) [16:53:49] oh wait, that link is not working for me [16:55:02] can you post it on a regular page, or just attach it to an email? [16:55:52] philinje: try again [16:55:54] just fixed it [16:58:24] got it [16:58:38] is there any way to see a button has been pressed? [16:59:01] philinje: yeah, adding fastclick + active now. The native implementation was wildly off. [16:59:30] heading bar is a little off to the right [17:00:05] philinje: webkit bug I need to find a workaround for. It occurs intermittently. [17:00:20] philinje: kill the app and get it back up, should 'fix' it? [17:00:26] philinje: also what phone are you testing this on? [17:00:46] Nexus One, Android 2.3.6 [17:01:35] philinje: okay! [17:02:34] not fixing the position [17:02:52] philinje: is it off by a few pixels or off by, like, half a screen? [17:03:13] is there a min zoom level, and is clustering implemented? [17:03:14] greetings all [17:04:08] philinje: no clustering yet. As I said, it's at a basic look and feel + workflow stage. [17:05:12] Sure. Back from nearby goes to campaign list [17:05:23] tfinc, is http://etherpad.wikimedia.org/API-blog-post what you had in mind? [17:05:36] MaxSem: let me take a look [17:05:45] yuvipanda: philinje how do we look for the showcase today? [17:06:10] testing the app [17:12:04] yuvipanda: http://dumps.wikimedia.org/android/ needs android 1.2 and 1.2.1 [17:12:10] i don't have the builds [17:12:57] tfinc: okay, I'll email you them in a bit [17:13:14] yuvipanda: where can i find the wlm apk? [17:13:19] philinje: i've fixed the 'header offset' bug and uploaded a new build. Same URL [17:13:22] tfinc: d20badc1493dfb0d16c34f9039e3e947ec311345 [17:13:22] err [17:13:25] wrong paste [17:13:26] wait [17:13:32] tfinc: https://dl.dropbox.com/u/8768784/WLMMobile-debug.apk [17:16:46] thanks [17:24:30] preilly: do you need anything from me for todays presentation ? [17:26:44] tfinc: I don't think so [17:26:48] tfinc: I think that [17:26:48] i [17:26:50] k [17:26:51] 'm all set [17:26:54] argh [17:32:04] yuvipanda: login screen is showing a spinner [17:32:40] philinje: before you try to login? [17:32:52] yuvipanda: yes, just when the login screen comes up [17:33:06] * yuvipanda hadn't tested on Android 2.x, only on device. [17:33:19] philinje: yeah, I see it. Will take care of it. [17:33:27] sorry missed your earlier question: the top bar is off to the right by maybe 10 pixels [17:34:02] most important change is fast click + active, in terms of the demo [17:35:28] philinje: redownload and try it again now? I've re-enabled the native active highlight and fixed the other issues you reported [17:35:45] philinje: same URL [17:36:18] ok [17:37:15] not seeing any click action [17:37:51] it remembered my login info and did an auto-login - nice [17:38:00] philinje: is the offset in the top bar gone? [17:38:29] yes [17:39:34] * yuvipanda checks for tap actions again [17:39:37] they worked on the emu [17:39:43] list/map view switch is not obvious - did you need graphics for that? [17:40:33] philinje: I need to redo it - I don't think I can use a combobox there. I don't think bringing up the list like how it does now is how it is meant to be. [17:40:36] preilly: did you make it out to google i/o yesterday? [17:40:50] no problem [17:40:56] philinje: i'll just put lines on it for now, will figure out graphics when I start redoing it. [17:41:06] tfinc: yes [17:41:31] tfinc: but I didn't get a phone or tablet or anything [17:41:43] if you think there is a quick fix for fast click, then that may be worth squeezing in, but otherwise I will send an email to Elke in 10 minutes [17:41:44] preilly: did you manage to snag one of the nexus 7 ? i'm eager to tinker with it. its getting really positive reviews [17:41:57] preilly: where they already out? [17:41:57] tfinc: but I did talk to Sergey Brin for 10 minutes [17:42:08] preilly: did he have his glasses on? [17:42:20] yuvipanda: yes that is what we talked about [17:42:27] tfinc: yes [17:43:14] philinje: I see an 'active' response when I touch [17:43:19] philinje: both on my device and on my emulator [17:43:57] ah it is there, for some reason it didn't appear earlier [17:44:23] philinje: yes, it's a bit inconsistent, which is why I removed it earlier to replace with our own implementation. But that's gonna take a bit of time, so put it back in [17:44:33] ok [17:45:08] will send an email soon and I guess you can update the apk any time before 11 [17:45:39] philinje: okay! I'm just going to make monuments search a bit more reliable. Is there anything else you'd want me to look at instead? [17:46:27] no, sounds like you changed the list/map button look for now (minor point) [17:46:54] looking good overall [17:47:19] philinje: yup, just did. Will make a build in a bit (testing) [17:47:42] ok [17:48:36] philinje: so how is this going to work? Skype conf call with you leading it? Giving over the app to elka and having her try it out? [17:50:04] yes [17:50:08] philinje: ok [17:50:22] i will email the link shortly and then conference everyone on Skype [17:53:10] New patchset: MaxSem; "Fix tests" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13354 [17:53:41] yuvipanda: lindsey is seeing lots of issues on ICS [17:53:51] i imagine you are not testing on ICS currently [17:54:56] philinje: I *am* testing on ICS. what issues? [17:55:11] linSmith: ? [17:55:18] icons are not appearing, browse by campaign doesn't seem to work [17:55:31] which phone? [17:55:39] they work fine on my ICS nexus s... [17:56:53] philinje: linSmith ^ [17:56:55] pchang__: ^ [17:57:02] pchang__: which phone? They work fine on my nexus s ics [17:57:04] galaxy nexus [17:57:13] I'll send you some screenshots [17:57:36] could be screen size/layout issues? [17:58:29] brion_: nah, I *think* it is bug in how I do image substitution. I think galaxy nexus is reporting its device pixel ratio as 2 instead of 2.0, causing issues [17:58:48] hm [17:58:54] well 2 and 2.0 should be the same [17:59:57] brion_: they're strings, so aren't. I should've normalized it, of course. [17:59:59] no Jon today? [18:00:03] urgh strings! [18:00:27] linSmith: Download and try again? I think I fixed that [18:00:41] brion_: this is a lot of unreviewed code :( [18:01:09] ok, I'll try it again [18:04:05] brion: philinje also, in case you are wondering - current apks are from https://github.com/yuvipanda/WLMMobile, which is significantly ahead of wikimedia/WLMMobile [18:04:48] yuvipanda the graphics are showing, but they are too large or scaled up I think? they are really fuzzy and almost larger than the action bar [18:04:48] ok, i gave elke the dropbox URL, is that ok? [18:05:23] linSmith: Just a heads up I'm going to need you later on today to look at the revised language stuff [18:05:33] sure [18:06:12] I'm working remotely today [18:06:32] yup I saw. I cursed the sky when I saw your mail ;-) [18:06:45] I'll send you a labs link [18:07:03] ha, okay [18:07:05] https://dl.dropbox.com/u/8768784/WLMMobile-debug.apk [18:07:26] linSmith: looks like i've the wrong size for them. Will investigate. [18:07:36] linSmith: calling [18:08:02] yuvipanda: did we remove the change that loaded the choose country page instantly? [18:08:19] map isn't loading for me either [18:08:26] jrobson, any thoughts on the language selector issue? if no, I propose to leave the the wording as it is for now, move it to the bottom and merge [18:08:26] jrobson: it was causing problems with the map jrobson so I removed it. [18:08:32] If I click Andorra there is a massive delay and I end up clicking it again :-( [18:08:36] there are pins, just on a white background [18:08:43] What was going wrong with the map? [18:08:55] jrobson: no idea yet. ICS seems to be a problem. [18:09:06] jrobson: tiles not loading. [18:09:32] I'm sure we could have fixed that without removing the auto load :P [18:09:34] the campaign list does work for me, just extremely slow to load [18:09:50] jrobson: no that wasn't the problem :) [18:11:07] note that multichill have removed the maximum geosearch area limit, so if you want to view all the landmarks on the continent it will melt the server and your connection but will be served to you. probably [18:11:28] http://etherpad.wikimedia.org/WLMshowcase [18:11:33] jrobson: I forgot what it was, but it was caused by having monuments be a empty array [18:11:55] We still should have fixed that separately rather than reverting :) [18:12:59] jrobson: I reverted it because I anyway needed to include some sort of 'loader' in there anywhere [18:13:28] tfinc, when the WLM app is supposed to launch? [18:13:43] MaxSem: WLM itself is in Sept [18:13:52] were targeting final testing and launch of the app in august [18:14:18] tfinc, do we have plans to host in on WMF by then? [18:14:34] the API I mean [18:17:56] yuvipanda what is the settings screen supposed to be right now? [18:18:16] MaxSem|android, https://dl.dropbox.com/u/8768784/WLMMobile-debug.apk [18:18:56] MaxSem: yes. we'll be setting the plan after this showcase is done [18:19:19] i wanted to make sure that we were on the right track with the app before we started moving backend infrastructure [18:20:18] mmm, I can't choose any campaign from the list. tapping simply does nothing [18:21:42] MaxSem: are you sure. mine doesn't show an immediate response but it loads after 1-2 secs [18:22:03] trying again [18:23:24] linSmith: user account reset + language UI [18:23:38] linSmith: but I'm unsure about language UI - perhaps it should just stick to the phone's UI [18:24:00] yuvipanda all I get is a white screen [18:24:06] tfinc, yeah - the delay on my connection is astonishing [18:24:38] I'm trying to upload a photo, it's been sitting at the starting upload dialog for a long time [18:25:09] linSmith: aah, 'currently' it is a white screen :) [18:25:32] ok cool [18:27:56] philinje: https://test.wikipedia.org/wiki/Special:RecentChanges [18:29:24] ugh android emu draws incorrectly on retina display… http://code.google.com/p/android/issues/detail?id=33383 [18:29:30] i got first world problems man [18:30:42] brion: ha ha ha ha [18:35:34] omg https://test.wikipedia.org/wiki/File:Woning,_breedhuis_1340908463521.jpeg [18:35:44] lolz [18:50:45] http://android-developers.blogspot.co.uk/2012/06/android-sdk-tools-revision-20.html [19:03:30] yuvipanda: hi, we are going into a meeting but can we chat in about an hour? [19:03:58] ugh, power cut. and i've bugs all over me. [19:04:04] eek [19:04:33] at least no ants yet [19:05:52] anti-insect power shield is down? [19:09:05] MaxSem: yes, it is called the 'ceiling fan' [19:09:21] MaxSem: and since the only source of light around now is my display... [19:10:28] exit light [19:10:32] enter night [19:11:06] take my hand [19:11:14] off no never ever land [19:11:27] typo, fail [19:13:01] MaxSem: :P [19:18:48] MaxSem: so, search should cover both the address and the name. What do you think is the best way to expose this? [19:19:55] mmm [19:20:24] address currently consists of 4 fields [19:20:59] MaxSem: are you counting the 'admin' type fields? [19:21:47] oh, there's a separate address field [19:22:18] I'm tempted to join everything that needs ful--text search into one big fat field [19:22:26] thoughts? [19:23:15] MaxSem: and call it what? [19:23:59] MaxSem: I'd also like to discriminate - show the results where the name matched before showing the results where the address matched, for example [19:25:54] if you want two separate queries, fine [19:27:10] MaxSem: actually, I think just joining everything makes sense. [19:27:30] MaxSem: don't think sending out two requests is a good idea, plus I can always differentiate on the client side [19:28:03] MaxSem: also, sort orders? currently everything's unsorted, so some way of specifying sort orders would be great! [19:28:38] actually, everything's sorted, otherwise query-continue wouldn't have worked [19:29:22] MaxSem: mmm sorted by what? [19:29:36] for most queries, the order is ( 'country', 'lang', 'id' ) [19:30:08] for kml it's ('image', 'id') [19:30:20] for html it's ('country', 'municipality', 'address') [19:31:13] MaxSem: hmm, can it be ('country', 'municipality', 'name') for queries? [19:31:13] for name full-text search it's ( 'name', 'country', 'lang', 'id' ) [19:31:17] (API) [19:31:22] name first? [19:31:25] hmmm [19:31:40] because alphasort makes most sense [19:31:58] bleh, this schema is a mess [19:32:33] indeed :| [19:33:13] MaxSem: i'd want something consistent between normal queries and fulltext [19:33:49] why? [19:34:28] I suggest you to list the queries you're going to send along with preferred sorting [19:34:29] err, so that the first list is consistent in ordering with the list they get when they search? [19:34:38] MaxSem: I can do that. [19:34:49] then we could figure this stuff more reasonably [19:37:41] MaxSem: https://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application/Queries [19:37:44] 3 queries i'm making for now [19:38:37] MaxSem: i think having everything ordered by (name, municipality) should do [19:38:44] use full-text search for name pretty please [19:39:46] yuvipand1, not unique: the same monument could appear in different languages. hence the weird 4-column order [19:40:07] cause only primary key can guarantee anything [19:40:28] MaxSem: ( 'country', 'lang', 'name', 'municipality' ) then? [19:40:40] MaxSem: ( 'country', 'lang', 'name', 'municipality', 'id' ) even, (guarantees uniqueness) [19:41:34] what for is municipality here? [19:43:21] MaxSem: same name, different municipalities? [19:43:22] and what's the point of sorting by name in the middle of other columns? [19:43:32] how's that? [19:43:52] MaxSem: i was working on india list a few days back, a lot of them were just 'ganesha temple' and stuff [19:44:00] but municipality *after* name makes no sense, yes [19:44:09] the primary key aka the uniqueness constrint is 'country', 'lang', 'id' [19:44:20] MaxSem: it is a sort key, does it need to be unique? [19:44:32] yes it has - for paging [19:44:54] ah [19:44:56] well [19:45:06] ( country, lang, name, id ) is unique [19:45:24] and since we're not using lang anywhere, and country is what we'll search for, i think it boils down to (lang, id) [19:45:28] err [19:45:30] (name, id) [19:48:16] well, _you_ are not using it. but the DB disagrees [19:48:47] yuvipand1, I could just give you the dump so you could look at this stuff yourself [19:49:44] MaxSem: is there any problem with having (country, lang, name, id ) as sort order for API search queries? [19:50:02] no [19:50:14] causee it's filesort either way:P [19:51:11] c'mon Germany! [19:51:37] I will not survive the finals with tournament's two most boring teams [19:57:04] MaxSem: okay :) [19:57:30] MaxSem: then can you make that change or do you want me to try my hand at it? [19:59:43] which one? you suggested a dozen o'them [19:59:54] (country, lang, name, id ) [20:00:40] I'll take a look at its performance implications [20:00:49] okay! [20:00:58] MaxSem: thanks! [20:03:53] there's a kid crying a few houses down. Grrr [20:10:54] yuvipand1: hey, can you chat in 10 min? [20:11:05] philinje: yup [20:11:09] cool [20:17:55] MaxSem: why does https://toolserver.org/~erfgoed/api/api.php?format=json&action=search&srcountry=us&srname=~w give me an empty list? [20:19:04] because there are no names containing word "w" [20:19:29] try ~w* [20:21:21] MaxSem: that works. [20:21:30] sssslowwwwly [20:22:27] second time seems a bit faster - but it might just be my local cache :P [20:22:40] MaxSem: this seems as slow as prefix search? [20:23:12] no, it's just a filesort of results. %foo% is full-table scan [20:23:46] though you really shouldn't search for just one character [20:25:47] also, toolserver is a wreck [20:26:49] MaxSem: how much of this is because toolserver is a wreck vs inherent design limits? [20:27:33] multichill once observed SHOW TABLES taking 6 seconds [20:28:13] .... [20:28:19] yuvipand1: hey [20:28:35] hey philinje [20:28:51] how did you feel about the showcase? [20:29:17] philinje: murphy's law hit upload but otherwise I think it accomplished what it was meant to [20:29:41] yes, the upload issue was a surprise [20:30:00] it was working for me earlier in the week and before the call [20:30:15] it was working during the call too :) [20:30:27] needs to be ironed out, however. [20:30:30] yes, and after the first try it worked for me during the call [20:30:44] what's left to do on that? [20:31:08] philinje: on uploads? [20:31:18] yes [20:31:33] philinje: uploads I need to figure out how to get progress. I haven't even started on it yet. I might have to write a plugin for that. [20:32:00] philinje: but it is sufficiently isolated that I can fix the other issues before heading there. [20:32:10] philinje: so I'd want to fix all the other issues before taking on upload [20:32:37] are you planning to do a lot of work going forward? [20:33:16] philinje: yes I am :) [20:33:33] might not be on SF timezone, however. [20:33:37] wow, I thought you would hand this over to Jon going forward [20:33:55] well, I think 'officially' jon will [20:34:15] but I'll still be writing code, etc. Not going to disappear anywhere :) [20:34:21] hmm, should we carve up the tasks between you and Jon? [20:34:29] philinje: that sounds like a good ide! [20:34:30] *idea [20:34:51] philinje: can you convert notes from today into bugzilla bugs? [20:34:54] i think that'll make it easier [20:35:06] i think we're at a stage now where using bugzilla makes sense [20:35:15] yeah, i was thinking of updating the ToDo list first [20:36:00] philinje: I just updated it with {{done}} items. I think the ToDo list is a tad too high level for some of the bugs, and i think they should go to bugzilla [20:36:05] the map issue, for example [20:36:12] ok [20:36:48] do you want to enter bugs, and I'll add the high-level stuff to the ToDo list? [20:37:16] philinje: in the middle of doing some of the search stuff, I can add it tomorrow if you want [20:37:55] ok, I'll make a tracking bug [20:38:25] one question on uploads: is that using the chunked data API? [20:38:37] philinje: it isn't. It needs to [20:38:48] philinje: it's just uploading in one go. [20:39:02] that will help with progress and error recovery, right? [20:39:11] philinje: yes, very much. [20:39:29] is that something Jon or Max could tackle? [20:40:28] philinje: so, I am unsure if it *can* be done in Javascript. [20:40:33] philinje: might have to be done in java as a plugin [20:40:46] ah, i see [20:40:54] in which case me or brion_ should pick it up. [20:41:07] let's ask Brion [20:41:25] philinje: jon could do the UI stuff - he's definitely much better at that than me :) [20:41:40] Tomasz thought upload was our biggest priority [20:41:44] to use chunked data with current cordova FileTransfer i think we:d need to make temporary split files [20:41:50] not rocket science to do though [20:41:53] just annoying +~ [20:41:59] ahhh my keyboard layout is funny [20:42:07] *tweaks back to english* [20:42:32] brion_: so is that something you could work on? [20:42:47] sure [20:42:53] cool! [20:42:53] brion_: yes, but we'll probably need to subclass their filetransfer class and do chunked - plus expose progress [20:43:21] brion_: and by chunked you mean http://firefogg.org/dev/chunk_post.html right? [20:45:56] yuvipand1: not exactly the same as that i think but similar [20:46:08] http://www.mediawiki.org/wiki/API:Upload#Chunked_uploading [20:50:25] philinje: sorry, shitty internet [20:50:36] ok [20:51:20] brion: it is the same, I got that link from the lead of https://www.mediawiki.org/wiki/API:Upload :) [20:51:27] \o/ [20:52:10] brion: also, do you think you're up for some CR? I've a lot of changes at https://github.com/yuvipanda/WLMMobile that aren't in wikimedia/WLMMobile yet [20:52:23] jrobson couldn't find the time, so wondering if you could [20:52:36] yuvipanda, yeah i'll poke over those next couple days [20:52:53] brion_: sweet [20:53:31] yuvipanda: so roughly speaking, how would you carve out the tasks between you and Jon [20:53:34] sorry yuvipanda [20:53:35] :( [20:53:47] keen to get out the language stuff in the beta [20:53:48] it's annoying me [20:54:05] yuvipanda: was the version we used at the showcase built off of wikimedia master or your own branch [20:54:06] ? [20:54:55] tfinc: my branch. there were quite a few commits stuck in pull reqs so I merged them into mine and buil tthem [20:55:09] ok [20:55:22] tfinc: also, http://www.buzzfeed.com/jwherrman/the-problem-with-chrome-for-ios [20:55:40] same problem as we're suffering from [20:55:52] on iOS, that is [20:57:36] linSmith: there? [20:58:19] try Lindsey on wikimedia-design [20:58:25] yuvipanda: thanks for that article [20:59:21] yuvipanda: agreed. not having access to the same underlying performance boosts that safari gets blows [20:59:24] and hurts us a lot [20:59:40] tfinc: we're getting only 25% of the perf that apple gest. [20:59:42] *gets [20:59:43] not fair [20:59:53] but more noise will now be made about it [20:59:58] since Chrome is going to suck balls too [21:00:21] that's how Apple wants it [21:00:26] Yuvi: back to my question: how would you roughly break out tasks between you and Jon? I assume Jon will get the higher priority ones [21:01:39] and assuming Brion handles chunked data upload [21:01:56] philinje: i'm happy to handle the task assignment here if you can curate the backlog [21:02:03] philinje: I think 1. getting them on bugzilla 2. assigning them off is the best way to do it. [21:02:10] we're at a point when things are easily breakable into bugs [21:02:19] ok [21:02:31] but we have to get the issues into bugzilla first [21:02:39] i can help with that too. just let me know which batch needs it [21:03:36] tfinc: i think getting the ones from the etherpad in would be a good start. there's already a product created for this [21:03:36] ergg is labs broken? [21:04:13] yuvipanda: i know. i was asking philinje to triage them and let me know which ones he couldn't get to so that i could add those bugs [21:04:32] so we don't need a tracking bug? [21:04:58] ah, okay! [21:05:48] philinje: lets file bugs for the issues first. then we can worry about racking bugs [21:05:52] tracking* [21:11:25] Bugs listed under Bugs on the etherpad can be input as bugs, enhancements and UI need to be organized a bit on the wiki page [21:12:05] i will focus on the wiki page for now, tfinc, if you want to enter the bugs under Bugs [21:12:27] philinje: just let me know when the wiki page is stable and i'll start adding bugs [21:19:35] yuvipanda, where's the commit that fixes the 2.0 and 1.0 imnages? [21:22:00] brion_: 7493abb6e29b7b940fd803a24d0e39b8abaa2863 renames it [21:22:02] hm, also on ldpi phones you'll have 0.75 [21:22:28] brion_: ebd204a2af79610dbb58a7cb36f6d91471621477 adds 1.0 [21:22:32] i don't see that commit in your master [21:22:52] so 1.0 won't work either afaik [21:23:00] brion_: yup, will need to be 1 [21:23:11] brion_: forgot to push. now pushed [21:23:18] brion_: do we want to support ldpi? [21:23:26] too low res, etc? [21:23:37] i'm gonna assume if the program runs, why not [21:23:57] easy enough to just load the 1x assets though and let browser scale them :) [21:24:07] brion_: either way, let me figure out the correct set of sizes for all of them and email linSmith again. [21:24:12] ok [21:24:14] brion_: well, it's a simple resize, so doesn't matter, I guess [21:24:32] brion_: you're testing on your gnexus? [21:24:39] brion_: how bad are the sizes? a size too large? [21:25:05] haven't run it yet, but i'm guessing i would see no images at all [21:25:27] lindsey said the icons were roughly 2x too big [21:25:49] do the tags all have width and height attributes on them? [21:26:00] if not, they will definitely show up scaled wrong at anything but 1x [21:26:49] brion_: I'm on 1.5 and they were properly sized for me? [21:27:18] ok i see blue boxes with question marks in them [21:27:21] running from yuvi/master [21:27:28] should i poke another branch or is that right? [21:27:34] yuvi/master is right [21:27:43] blue boxes -> wrong path [21:27:49] did you fetch again? what commit is it at? [21:27:56] yeah [21:27:59] aha there's more changes [21:28:00] now lemme try [21:28:50] yuvipanda: ok now on galaxy nexus i see icons but they are too large [21:29:23] i'm guessing on 1.5 those images are being scaled up but come out to a size you expect [21:29:37] and on 1.0 they'll look tiny [21:29:42] brion: hmm, so I *think* I might've done two mistakes which sortof cancelled each other out and made things work on 1.5 for me [21:29:47] hehe [21:31:05] brion: so, I'd have to either set widths in css and use background-image or go around setting width and height attribs on all images [21:31:14] or find a way to do this from the dpr plugin itself... [21:32:10] you could also set width/height with CSS but use dpr for the image src url, i think [21:32:32] but _something_ needs to be labeled with your expected size [21:32:47] otherwise it'll happily assume that 1 image pixel == 1 css pixel [21:32:55] what, no magic? :D [21:33:16] brion: so, you can i think swap out the 1.5x images into the 2 folder and continue working on your gnexus while I figure out a solution for this [21:33:39] oh i'll just live with big icons for now, i know you'll fix it :) [21:33:52] magic would be SVG support :P :P :P [21:34:29] :D [21:34:36] on android 2.x devices as well! :P [21:35:08] i seriously just wanna drop a magic bomb that upgrades all android 2 devices to 4 [21:37:03] yuvipanda: check your pm [21:37:29] oh - i preordered a nexus 7 tablet [21:37:45] brion: well, https://xkcd.com/989/ would be that magic bomb :P [21:37:48] looks like it's going to be 1.5x hidpi display from the specs [21:38:06] hahahah too true [21:42:00] yuvipanda, choose: fast unsorted queries with unlimited number of results vs. slower sorted queries capped at 1000 results total? [21:42:26] (for full-text search) [21:42:45] uh oh [21:43:06] MaxSem: how much slower? [21:43:20] unpredictable [21:43:29] well, an approximate order of magnitude? [21:43:30] 10x? [21:43:31] 100x? [21:44:13] depends on lots of things. say, at least 5x when there are a lot of results [21:46:45] MaxSem: and absolutely no way to have my cake and eat it too? [21:48:35] MaxSem: if it is just for fulltext, i'd take the latter [21:48:59] assuming I can get fast, sorted queries with unlimited number of results *without* fulltext search and with pagination [21:50:00] brion: what do you call the API you created for grabbing the campaign config info? [21:50:08] uploadcampaign [21:50:13] thanks [21:50:18] yuvipanda, MediaWiki's native search engine doesn't sort, for example [21:51:33] Change abandoned: Jdlrobson; "Completely rethinking this now after discussions with Phil and Lindsey" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/10452 [21:51:47] MaxSem: I think this needs further discussion with philinje and perhaps linSmith. [21:52:09] jrobson, o_0 [21:52:12] MaxSem: or, better yet, let me use the thing for a while and see if I find the lack of sorting in search disturbing [21:52:22] haha MaxSem [21:52:35] we're dropping it from settings completely [21:53:09] yuvipanda: can we sort in the app? [21:53:13] yuvipanda, how many search results are you going to display at once anyway? [21:53:29] it was 100, then get more [21:54:10] MaxSem: ~25 [21:54:19] so i'm unsure if sorting is *that* important [21:54:35] philinje: it depends - if there are 1000 results, and we get back 25, sorting makes no sense. Sorting makes sense with pagination [21:55:17] MaxSem: can we get sorting for normal queries? Ones that don't invoke full text search? [21:55:30] yes we can [21:56:00] can someone specify the search filter with the search string, on a particular field? [21:56:07] MaxSem: I think that's enough. Search results - I can sort them locally. Small enough number, plus I'm not going to paginate. [21:56:35] philinje: i think that'll be too complicated on a mobile, no? Just 'free text', currently searches only names, and can be expanded to include name + address [21:56:37] within reasonable limits, e.g. ideally sort order should corellate with WHERE conditions in order to use indexes [21:58:28] MaxSem: action=search srcountry=(user-input) is the primary one I want sorted by name (which isn't on the where) [21:58:51] that's going to be the primary way for people to 'browse' [22:00:44] * yuvipanda should get to sleep shortly [22:00:56] yuvipanda: yes, that's what I meant, you got it [22:01:03] and yes, get some sleep [22:01:24] thanks for getting us to this point [22:02:53] MaxSem: so if I got sorting just for that, good enough :) [22:03:00] philinje: I'll still be around :) [22:03:41] jdlrobson: even though were missing http://events.jquery.org/2012/sf/ .. it gives me plenty of names of people to follow up with :D [22:04:38] brion_: https://github.com/wikimedia/WikipediaMobile/pull/262 is an interesting pull req on Wikipedia app you might want to look at when you've the time :) [22:04:44] tfinc: jrobson i'm off! gnite! [22:04:50] yuvipanda: night [22:05:03] ooh nice [22:05:09] night yuvi :) [22:05:26] brion_: very :) If that gets merged I'll roll it out the beta channel pretty quick :) [22:05:29] brion_: night! [22:05:41] * MaxSem erases that long post. good night yuvi [22:05:44] yuvipanda: night man! [22:06:24] this should be a good one > http://lanyrd.com/2012/an-event-apart-san-francisco/ [22:09:00] How was the showcase? [22:09:21] multichill: you missed out on a good time [22:09:40] multichill: it was a good first pass at showing the app [22:09:52] and gave us confidence that we were heading in the right direction [22:10:11] Good to hear [22:10:13] yay [22:10:35] there are bugs to be sure but the core features all have their plumbing in place [22:10:41] Couldn't beat my hockey, bbq and beer of tonight ;-) [22:10:53] brion_ & philinje can give you their take [22:11:13] Just in for a quick peak [22:11:19] many bits looking good :D still some work to go tho [22:11:26] alright i'm gonna go home, take a nap, and review yuvi's app updates when i'm not wanting to fall asleep on my keyboard [22:11:31] Should probably going to bed. Alarm goes in 6 hours. To Berlin again tomorrow [22:11:35] my sleep pattern's all fucked up and i didn't even travel out of my timezone [22:11:42] multichill: didn't know you played hockey - i did once upon a time [22:12:02] multichill: Elke will show you the demo in Berlin [22:12:07] For 22 years already [22:12:11] wow [22:12:41] multichill: she will ask you about the admin levels in the DB - how we get the data in there [22:13:09] We had a mixed evening tonight. We do that in summers. About 60 people both men and women from different teams play a small competition for four nights [22:13:11] It's fun [22:13:18] Yes, the adm0-4 [22:13:22] sounds great! [22:13:40] any idea where the data will come from? [22:14:06] From the wikipedia's? What do you mean exactly? [22:14:52] for the monuments, wherever the city/municipality info would come from [22:15:30] It's embeded in the lists [22:15:54] ah, so they just need tables, etc. [22:15:57] So for the Netherlands, nl is hardcoded, the provinces are in the lists and the municpalities too [22:16:24] is that manual effort or just some automated pass on the data? [22:18:32] Just like all other data. See for example https://en.wikipedia.org/wiki/National_Register_of_Historic_Places_listings_in_Jackson_County,_Missouri [22:18:44] |state_iso=us-mo|county=[[Jackson County, Missouri]] [22:18:51] That will be used for all entries on that page [22:19:49] ok [22:20:03] by the way, I've never seen women hockey players [22:21:18] http://www.knhb.nl/oranje/nationale+teams/selectie+oranje+dames/cDU903_Olympische+selectie+Nederlands+Elftal+Dames+2012.aspx [22:21:44] The ladies who are going to win olympic gold (I hope) [22:22:04] thanks, they look tough [22:22:21] philinje: http://en.wikipedia.org/wiki/Manon_Rh%C3%A9aume [22:22:23] * jrobson looks at MaxSem  [22:22:27] philinje: she even played in the NHL [22:22:42] * jrobson takes a deep breath [22:22:49] New patchset: Jdlrobson; "allow user to switch site-wide language from the MobileOptions/Language page" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13417 [22:22:50] ^ MaxSem [22:22:52] wow. [22:22:52] :P [22:22:59] multichill: so adm0-4 is already functional and we can use that now? [22:25:06] aaaaaaaaaaaaaaaaaa! [22:25:18] Hockey is quite big here. The association has 230.000 members [22:25:38] (on a total of 16M people) [22:25:49] multichill: just average folks? [22:27:00] Sure. NHL? That's ice hockey, don't confuse that with real hockey [22:27:45] multichill: are you talking about skating, or field hockey? I assume skating [22:28:09] I'm talking about hockey, not ice hockey [22:28:24] in the US that's called field hockey [22:28:32] Oh, but you're from the country where they talk about soccer..... [22:28:52] skating is big in the Netherlands too, from what I hear [22:29:21] Speed skating that is [22:30:22] [22:30:32] i have a Dutch friend who talks about the waterways freezing and then you can skate really long distances [22:34:45] even in poland we just call it hockey ;) i know almost no one who calls it ice hockey [22:39:18] tfinc: That's because the Poles aren't very good at it [22:39:34] (inkoppertje, Google translate that ;-) [22:39:52] Time for bed, see you later [22:40:25] its the same for any slavic country i've gone too ;) [22:51:09] New patchset: Jdlrobson; "hide sections where toggling hasn't been loaded yet (bug 37619)" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13419 [23:17:33] MaxSem: any chance you can look at https://gerrit.wikimedia.org/r/13417 today? I wanted to get it in for the beta monday… and tomorrow is my 20% day and I think yours? [23:17:40] guess it's late for you now though :) [23:17:54] yep [23:18:38] yep * 2 or no + yep ? :P [23:18:50] As long as I can fix any changes first thing tomorrow and get it merged no rush [23:19:02] I just want it merged before the weekend ! [23:21:44] I can't merge it myslef cause I participated in writing it [23:22:27] understood MaxSem - will poke preilly tomorrow [23:22:40] thanks a bunch - just keen to get your input since it's undergone some big changes :) [23:23:11] New review: MaxSem; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 0 C: -1; - https://gerrit.wikimedia.org/r/13417 [23:41:22] MaxSem: > Post to it /Language should be handled in a separate function, not in submitSettingsForm() [23:41:33] Bit confused.. there's no post whatsoever now… it's just links [23:41:57] ah, I didn't notice that it has changed so much [23:42:17] guess I'll need to look closer tomorrow [23:43:53] no worries do it after some sleep :) [23:44:14] New patchset: Jdlrobson; "allow user to switch site-wide language from the MobileOptions/Language page" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13417