[09:34:52] [WikipediaMobile] jdlrobson pushed 4 new commits to master: http://git.io/uCT6qg [09:34:52] [WikipediaMobile/master] Added GET as default type of a request and removed whitespaces - 4ndreaSt4gi [09:34:52] [WikipediaMobile/master] Merge remote-tracking branch '4ndreaSt4gi/asyncsearchbr' into tmp - Jon Robson [09:34:52] [WikipediaMobile/master] post merge styling changes for search.js - Jon Robson [09:35:15] Project WikipediaMobile - Nightly builds build #209: SUCCESS in 11 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/209/ [09:35:15] * stagi.andrea: Now search uses network [09:35:16] * stagi.andrea: Removed console log calls used during debug [09:35:16] * stagi.andrea: Stop the current request if performSearch is fired [09:35:17] * stagi.andrea: Added GET as default type of a request and removed whitespaces [09:35:17] * jdlrobson: post merge styling changes for search.js [09:35:18] * jdlrobson: provide dataTypes for api calls [11:19:03] [WikipediaMobile] jdlrobson pushed 2 new commits to master: http://git.io/OUfkOQ [11:19:03] [WikipediaMobile/master] Merge remote-tracking branch 'yuvipanda/map-fixes-1' into tmp - Jon Robson [11:19:03] [WikipediaMobile/master] minor adjustments to line length / readability - Jon Robson [11:19:18] Project WikipediaMobile - Nightly builds build #210: SUCCESS in 8.1 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/210/ [11:19:18] * yuvipanda: Never clear markers. And fix bug with flickering popups [11:19:19] * yuvipanda: Show spinner when moving from nearby view to article [11:19:19] * jdlrobson: minor adjustments to line length / readability [11:31:16] jdlrobson, have we figured it out what to do with expandable sections on older app versions? [11:37:36] No... without that header being sent by the app there doesn't seem to be a nice solution [11:39:10] so... revert the removal and push aggressively app versions that rely on API, then revisit it in a couple months? [11:39:39] i think so :/ [11:39:45] just seems a bit nasty [11:41:38] priorities, priorities, priorities - I could have created the API before 1.0 release had I been given this task instead of what I did in the beginning of my contract [11:41:46] who could have known? [11:42:43] jdlrobson, how many of your subsequent commits rely on this removal? [11:43:16] i don't need to do a complete revert [11:43:28] i should be able to mimic the behaviour with minor disruption to rest of code [11:44:26] will do that now and send you a patch to review (since i need to change php code) [11:44:37] okay [11:53:15] the Mobile application never uses the beta version of MobileFrontend does it? [11:53:39] dunno [12:16:17] MaxSem - http://pastebin.com/jSYwasYf - seemed to be the simplest fix - i'm not too sure about my php coding style though [12:16:21] going to test in android app now [12:17:15] got what you want [12:17:28] the fix is not nearly as easy [12:17:48] it has to be conditional [12:18:32] conditional on what? [12:28:31] we don't want to output those buttons to API users [12:28:47] here's my PHP changes: http://dpaste.com/711880/ [12:30:23] i see thanks MaxSem [12:33:21] does it work with your JS changes? [12:35:30] it looks like it [12:35:34] just trying on the android app [12:35:41] (with my localhost) [12:39:51] mmm there be weirdness [12:47:45] MaxSem I think your if statement is wrong - if ( $this->expandableSections ) { body is same as else [12:58:33] ??? [12:59:25] http://dpaste.com/711880/ L57 is the same as L61 [12:59:41] it's a refactoring artefact [13:01:42] the function itself gets called depending on $this->expandableSections [13:01:55] the artefact remains from Patrick [13:04:43] i think the if body is meant to have ", 'onclick' => $h2OnClick" in the array of arguments to open element [13:08:26] so MaxSem - http://pastebin.com/MuYbzg5a - going to push this if no complaints [13:09:08] okay [13:14:58] k pushed bbl [15:50:36] hey jdlrobson [15:50:42] is there a reason to prefer ternary? [15:51:18] I usually avoid it for reasons of clarity + it feels awkward with long conditions [15:51:42] i find it more readable in certain cases [15:51:50] it was just a suggestion [15:52:04] feel free to disagree :) [15:52:30] heh :D [15:53:03] jdlrobson: that particular code was ternary a long time ago, and spanned 3 lines [15:54:17] you could do disabled = currentHistoryIndex > 0 ? true : false [15:54:33] just makes it clearer what the if statement effects [15:54:54] (imagine setMenuItemState took 10 arguments and only the 2nd one was effected by the if statement) [15:54:59] would be hard to grep [15:55:14] ah [15:55:16] that makes sense [15:55:30] but why disabled = currentHistoryIndex > 0 ? true : false [15:55:36] the part after the ? could be dropped no? [15:57:03] true [15:58:06] alright. let me do that [15:58:17] sweet [15:58:27] also while you are here [15:58:48] i keep experiencing situations where items in the menu correspond to different tasks. it seems to be random though ... have you ever experienced that? [15:58:57] for example I'll click 'nearby' and i'll get the share page [16:00:47] also i looked at this pull request -> https://github.com/wikimedia/WikipediaMobile/pull/137 but i'm not sure we want to that right? it shows 1 article for zoom level less than 4, 2 for levels 4-8, 3 for 8-12 and 4 for 12-14 - seems very very restrictive and i dont feel it addresses https://bugzilla.wikimedia.org/show_bug.cgi?id=31891 which is more about allowing the user to control messy maps [16:01:29] hmm [16:01:55] jdlrobson: primarily that was more a proof of concept done during the Pune Hackathon [16:02:18] closed it [16:02:21] thx [16:02:22] jdlrobson: that's interesting [16:02:27] jdlrobson: on android? [16:02:30] yup [16:02:57] the Android menu code is a complete mess, and causes race conditions that you could possibly be seeing [16:03:11] the plugin used was apparently taken from an example article which was not exactly 'good' code [16:03:24] the 'fix' is to rewrite the damn thing, but I'm not sure if I can do that before 1.1 [16:03:47] there was another race condition I worked around with a hack (noUpdate parameter in setMenuState) [16:03:52] jdlrobson: can you tell me repro steps for this? [16:04:10] this is the thing.. i cant accurately reproduce [16:04:29] it seems to happen more often if i quickly press the menu as soon as the app has loaded [16:04:35] *usually* it happens whenever updateMenuState is called twice fast. [16:04:46] * jdlrobson looking at https://github.com/wikimedia/WikipediaMobile/pull/135 [16:06:01] jdlrobson: not a fan of $("#content").show() [16:06:15] we have showContent plus that won't apply cleanly [16:06:22] and I'm not sure that we need a divider there [16:06:36] jdlrobson: your call :) [16:06:47] im just loading up a tablet to understand better the bug [16:07:03] bug/problem [16:07:06] okay. IIRC it is just adding a divider line between the sidebar and content [16:07:07] okay [16:09:30] heya yuvipanda jdlrobson [16:09:36] heya Astagi! [16:09:39] how you doing? :) [16:09:44] hey astagi [16:09:57] what's happening with request 135? let me know if I can help :) [16:10:09] sure i'm just trying to boot up an emulator at the moment [16:10:35] :) nice [16:12:12] mmm i cant see what the layout problem is - im on a samsung galaxy tab [16:12:29] try to open the about [16:12:37] this is the about us page with the wikipedia logo underneath? [16:13:17] should be overriden by the content [16:13:44] it's also an old pull request, I ignore newer changes :) [16:15:18] it doesn't look wrong at all [16:15:22] can you send me a screenshot? [16:16:17] let me try with the new master, give me a moment :) [16:16:44] no worries [16:19:30] also yuvi any thoughts on this - > https://github.com/wikimedia/WikipediaMobile/pull/136 (i also notice debloper's made his changes on his master branch) [16:20:00] oh damn! [16:20:05] no power on my transformer [16:20:19] try to charge a little to make it work for a screenshot [16:20:26] jdlrobson: closed [16:20:30] it's impossibile to charge during debug [16:20:45] :/ [16:21:11] I think cause I don't have usb 3 [16:21:27] give me 15 minutes jdlrobson [16:21:28] :) [16:21:43] no worries - i need to pop to the post office quickly anyway so that suits me perfectly! [16:22:56] :) [16:23:02] maybe is just a problem of my device [16:37:31] jdlrobson here it is https://p.twimg.com/AnPKz8MCAAAyOtw.png [16:37:53] mm [16:37:55] how strange [16:38:00] * jdlrobson looks again [16:38:04] :) [16:38:30] is it only in landscape mode? [16:39:18] tried [16:39:31] no, happens in portrait mode too [16:40:29] did you try to test the patch to see if it's working on galaxy? [16:40:41] maybe could be a general workaround [16:42:35] well the galaxy doesn't have the problem at all (before the patch) [16:42:59] lets see if i can find an Asus Transformer emulator [16:50:34] ok [16:50:39] astagi - i think you the about page is suppose to open on the left tab [16:50:43] so i didnt manage to find an Asus [16:50:51] but when i open in safari the web view [16:51:02] i notice that opening the about page when i have a large window opens as in the screenshot [16:51:14] whether that's right i don't know [16:51:41] * yuvipanda peeks out [16:51:51] the about page *is* supposed to open in the left pane [16:51:58] same space as search results, history, etc [16:51:59] really? [16:52:03] seems ugly [16:52:24] an about page should be opened full screen :) [16:52:45] there are css rules for that [16:52:59] see app.css L565 [16:54:31] ok [16:54:43] but as -i specified my patch was old [16:54:52] before that about page was broken [16:55:05] anyway I think that should be better a full width page [16:55:18] :) [16:59:13] Astagi: particular reason? [17:02:12] i suspect the athena redesign would make this redundant [17:03:01] +1 [17:03:24] jdlrobson: http://www.mediawiki.org/wiki/Glaucus comes before athena [17:03:27] Astagi: ^ [17:05:25] jdlrobson, https://bugzilla.wikimedia.org/show_bug.cgi?id=34986 :P [17:05:43] arghsafadadad [17:06:50] ok [17:06:53] np [17:07:33] Astagi: seen the glaucus page? [17:10:39] yep but what this means with the actual version? [17:11:33] this will be the future version of the app, right yuvipanda? [17:11:59] I just consider ugly an about page on the side for the actual one, just it :) [17:12:11] Astagi: yes, we'll have to figure out which parts of this go into 1.2, and which into later versions [17:14:12] jdlrobson: https://bugzilla.wikimedia.org/show_bug.cgi?id=34986 has been closed by brion :D [17:14:26] yeh ^ [17:14:26] ok sorry, as I said this is an old patch :) close it if you don't want about full width and a vertical separator :) [17:14:32] not sure how :S [17:15:15] heya Debloper! [17:15:22] seen http://www.mediawiki.org/wiki/Glaucus [17:15:22] ? [17:15:26] hey yuvipanda! [17:15:33] i think we should close this pull but we should certainly make sure this sort of thing gets highlighted in the Glacus discussions [17:15:48] * Debloper checks... [17:16:11] yuvipanda: ahh... cool ;) [17:17:10] yuvipanda: just saw https://github.com/wikimedia/WikipediaMobile/pull/136#issuecomment-4325836 that snapped me back that I have some pending work undertaken. [17:17:14] jdlrobson: true, Glaucus doesn't really have tablet-ized versions [17:18:26] * jdlrobson will add a comment to #135 [17:18:36] I made a comment on Glaucus' talk page [17:22:04] Debloper: thoughts on glaucus? [17:22:58] yuvipanda: is the design direction (almost) similar for Android (cause I see iOS specific screens mostly) [17:23:24] Debloper: it's in early concept stage right now [17:23:37] afaik the concepts would be similar, but the UI adopted for Android 4.0 level design guidelines [17:26:42] * Debloper likes having the easy access l10n selection, but dislikes it taking some vertical pixels persistently. Can it be a selectable option under W-menu? @ yuvipanda [17:27:19] [WikipediaMobile] jdlrobson created csslint (+1 new commit): http://git.io/ZFZ4NA [17:27:19] [WikipediaMobile/csslint] app.css cleanup - Jon Robson [17:27:33] whoops [17:27:35] Debloper: IIRC that's the idea - doubt its going to be persistent [17:27:38] Project WikipediaMobile - Nightly builds build #211: SUCCESS in 11 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/211/ [17:27:45] Debloper: put up comments in the talk page? [17:27:47] fail [17:28:07] sure. [17:29:06] jdlrobson: you pushed to a branch [17:29:14] yeh hence the fail :/ [17:29:30] i need to find a way to stop confusing myself about where im working [17:29:44] :_ [17:29:45] :) [17:29:53] i find remotes named origin and official good [17:29:56] * jdlrobson renames folder [17:30:25] i keep two folders - one for jdlrobson/WikipediaMobile and one for the actual branch [17:31:09] but.. why? [17:31:19] any reason why that over multiple remotes? [17:31:57] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/G3lY9g [17:31:57] [WikipediaMobile/master] Merge pull request #155 from wikimedia/csslint - Yuvi Panda [17:32:02] im not sure. maybe i should rethink that. [17:32:05] i cant remember my reasoning [17:32:11] Project WikipediaMobile - Nightly builds build #212: SUCCESS in 7.9 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/212/ [17:32:11] jdlrobson: app.css cleanup [17:32:26] :D [17:36:28] yuvi - were you going to make any changes to https://github.com/wikimedia/WikipediaMobile/pull/153/files [17:36:55] jdlrobson: yes [17:36:59] am doign it right now and testing [17:37:02] cool ping me when you want me to merge [17:37:04] yes [17:37:11] i need some more lemsip [17:37:28] lemsip? [17:38:04] jdlrobson: also, thoughts on jshint on pre-commit? [17:41:29] jdlrobson: pushed. [17:41:29] use the settings at the top of here - http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/MobileFrontend/javascripts/application.js?view=markup [17:41:38] thx [17:42:06] lemsip = cold (http://en.wikipedia.org/wiki/Lemsip) :( [17:43:23] aha! [17:43:36] my cold remedies seem to be 'curse until it goes away' [18:01:47] jdlrobson: do you know if it is possible to trigger opening a select from javascript in mobile browsers? [18:02:10] my experiments with android (https://bugzilla.wikimedia.org/show_bug.cgi?id=32244) were a failure, but I may be missing a trick [18:02:53] greetings all [18:03:14] * MaxSem grabs his mic [18:03:20] k, lets start in 2 min [18:05:05] preilly: philinje lets head to R32 [18:06:06] (yuvipanda - thinking about it) [18:13:38] tfinc_: philinje can you guys poke legal about this? [18:13:46] about mapquest - I can poke leaflet [18:14:38] yuvipanda: about how much we have to show to honor their attribution ? [18:14:40] on the footer? [18:15:03] no, about if they explicitly mention having it shown along with the map [18:15:06] or just 'in the application' [18:15:19] if it is the latter about page would do, if it is the former we'd need to keep it down there [18:16:02] tfinc_: ^ [18:21:01] preilly - do you want to confirm a bug for me? http://localhost/w/index.php/PageDontExistHere [18:21:06] get text 'There is currently no text in this page. You can search for this page title in other pages, search the related logs, or edit this page.' [18:21:12] click edit - > [18:21:20] still in mobile view [18:21:35] yuvipanda: ahh, philinje what came up in our talks with legal about this ? [18:21:36] hmm [18:21:41] that seems like a bug [18:22:06] tfinc: what exactly? [18:23:02] what we need to show for Mapquest is the attribution, exactly like in the beta [18:23:21] philinje: question is is the attribution required to be shown *along* with the Map [18:23:23] or just in the application [18:23:33] i see [18:23:37] that bug is a valid concern - on smaller screen devices that two liner will take a *lot* of space [18:23:44] let me check [18:23:46] right. as in can we just put it in the about screen [18:24:29] i've poked the leaflet guys about it as well [18:25:02] tomaszf: I also believe you have an email from blobaugh that legal might be interested in [18:26:03] preilly :( - i raise a bug or is there a quick fix we can do? [18:26:12] yuvipanda: yeah i saw [18:26:22] i'm not really interested in a lets change the license of the app game [18:27:29] grabbing food from upstairs and then i'll be back [18:29:28] tomaszf: what? you changed you nick you tricky little man [18:31:32] it says in a corner of the map: http://wiki.openstreetmap.org/wiki/Legal_FAQ#I_would_like_to_use_OpenStreetMap_maps._How_should_I_credit_you.3F [18:32:00] however, i can ask Mapquest and see what they think if we move it to the About box [18:32:40] philinje: those are for OSM tiles [18:32:43] we're using Mapquest tiles [18:32:44] different [18:35:35] yuvipanda: ? I thought we were using the OSM tiles from Mapquest? [18:36:08] oh, i see - Mapquest put a link to the OSM legal FAQ on their page [18:36:20] philinje: true, so http://developer.mapquest.com/web/products/open/map is what you should be looking at [18:36:28] the link you had was for tiles served from openstreetmap.org itself [18:37:14] yes, but at the bottom of the Mapquest page the first link is to the OSM FAQ [18:37:29] so I guess we need to ask OSM also [18:38:13] yes [18:38:18] asking them is probably the best bet [18:44:28] philinje: you should also update https://bugzilla.wikimedia.org/show_bug.cgi?id=34910 [18:46:02] * yuvipanda pokes tfinc for list of people to poke [18:46:20] yuvipanda - im not seeing a back button command in your back-button-fix-ios [18:46:36] not seeing a back-button command as in? [18:46:57] well index.html doesn't have one - only a forward button [18:47:09] jdlrobson: check ios/platform.js [18:47:18] jdlrobson: index.html is only for android. [18:47:23] as I said, menu code is mostly a mess [18:47:47] post 1.1 work would be to 'unify' it into a single plugin [18:47:55] ahh [18:48:03] the phonegap devs have been promising us that they'd do that in a release 'just around the corner' [18:48:05] yuvipanda, jdlrobson are you guys seeing the prob i'm seeing with section collapse/expand stuff being missing? [18:48:11] but its been just around the corner for too long :( [18:48:38] brion: nope? [18:48:43] weird [18:48:44] works fine, but its a simulator [18:49:17] have you cleared your apps cache? [18:49:17] i'm... seeing the same problem on android 4 :( [18:49:59] few users will know how to do that [18:50:05] i certainly don't know how to do that on ios :) [18:50:53] Uncaught ReferenceError: MobileFrontend is not defined at file:///android_asset/www/js/chrome.js:314 [18:50:56] interesting [18:50:59] ahhh [18:51:01] run make remote [18:51:14] gah. yes. [18:51:17] * make remotes [18:51:21] jdlrobson: ant :) [18:51:26] yeh... [18:52:34] where does MobileFrontend.init() call to? there seems to be nothing defining it [18:53:05] when you run make remotes it pulls http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/MobileFrontend/javascripts/application.js into assets/www/js/application.js [18:53:19] and that defines MobileFrontend.init [18:53:25] urgh [18:53:32] that sounds super fragile [18:54:14] brion: i'd want to push that into ant. plus for 1.2 we're moving completely to MaxSem's api, so that wouldn't be needed [18:54:28] * tomaszf notices that todays is all meetings [18:55:06] tomaszf, what have you done to tfinc? [18:55:12] haha [18:55:34] * tomaszf silences tfinc some more [18:55:38] MaxSem: he's grown wider :) [18:55:45] must be all the non-shitty beer [18:57:31] ok show/hide works again after running 'make remotes' and rebuilding [18:58:14] essentially trying to get to a point where the code for MobileFrontend for toggling is the same as the app [18:58:42] jdlrobson: i still think we should pull from perhaps deployed code instead of from svn [18:58:47] possibly at runtime rather than build time [18:59:26] that's fine. I agree the Makefile is not the best solution here [19:00:04] jdlrobson: thoughts on loading that at runtime? [19:00:30] well - you'd need an internet connection [19:00:38] which means cached pages running offline would break no? [19:01:04] hmm [19:01:21] how often do you expect the toggle code to change? [19:01:29] very rarely if at all [19:03:21] jdlrobson: okay, I suppose 1. moving to ant/xcode's build 2. pulling from version in production than from svn should do? [19:03:49] yep that sounds good to me [19:04:25] brion: ^^ [19:05:12] * yuvipanda pokes tfinc to give me list of people to poke [19:05:14] yuvipanda - whats the quickest way to build to test on my ios simulator... ive only done android up to this point? [19:05:27] jdlrobson: do you have xcode installed? [19:05:31] yup [19:05:40] with 5.0 sdk? [19:05:55] possibly.. [19:05:57] that would be xcode 4.3, IIRC [19:06:02] jdlrobson: http://www.mediawiki.org/wiki/Mobile/PhoneGap/iOS_build_instructions [19:06:12] it's much 'simpler' than getting the android bit done [19:06:13] perfect that was the link i was looking for [19:06:39] yuvipanda: tfinc is in a meeting [19:06:43] philinje: okay [19:06:52] yuvipanda: are you ok with a v1.2 meeting this week? [19:07:11] philinje: yes! just let me know when [19:07:27] jdlrobson: Jon, what is your schedule this week? [19:08:11] meaning, do you have a preference for any day at 6pm your time (10am here)? [19:08:41] it's flexible except tomorrow 7pm GMT-11pm and Thur 6pm-> I can't do [19:08:52] I'm planning to work late Wed (till maybe 2am GMT) [19:09:14] and im planning to go to bed soon tonight as i'm not feeling very good [19:09:40] sorry tomorrow should be 6.30pm->11pm [19:13:38] Ok thanks. No we need to see when Arthur surfaces from his move to Arizona [19:14:26] jdlrobson: currently it's an 8 hr difference, right? [19:14:32] yup [19:15:46] yuvipanda - i have xcode 3.2.6 and am currently on snow leopard ... do i really have to upgrade to lion to get this working? [19:16:11] apple hates supporting old versions of their os, don't they :) [19:16:17] you definitely need the 5.x SDK, IIRC [19:16:38] jdlrobson: apparently you can? http://stackoverflow.com/questions/7798382/can-i-get-the-ios-5-sdk-on-xcode-3-2-6 [19:17:02] yuvipanda: just noticed a minor detail in the OSM attribution: we don't have the last bit right now, "…contributors, CC-BY-SA" [19:17:12] dafaq? You need to pay for it if you want an older release? [19:17:13] o_O [19:17:47] well you need to pay to run on a device, too [19:18:43] i'm waiting for the day some other company makes a nice enough laptop so I can actually not have to put up with this [19:19:23] ah but you'll still need osx to test the osx/ios stuff. *shakes fist at vendor lock-in* [19:19:51] dang, my android tablet ran out of power and won't charge from my laptop [19:19:57] grrrrrr [19:19:59] [19:21:14] they dont seem to be supplying a download anymore yuvi.. :/ [19:21:37] although saying that i dont have a paid developer account [19:21:56] jdlrobson: yes, so apparently they do supply a download [19:22:02] only if you have a paid developer account [19:22:17] * yuvipanda smashes face into a bowl of grapes at this retardedness [19:33:44] greetings chrismcmahon [19:34:15] brion: need a power plug ? [19:34:28] one that connects to a wall outlet [19:37:24] tomaszf, oh if you have yours i'll borrow it sure [19:37:26] thx [19:39:37] chrismcmahon: http://wikimediafoundation.org/wiki/RFP/Mobile_QA [19:40:29] yuvipanda: jdlrobson : chrismcmahon is our new qa lead and I've been talking to him about our mobile qa rfp [19:40:35] and in general our qa infrastructure [19:40:49] * jdlrobson waves [19:41:00] he's going to connect us with some established mobile QA folks [19:41:09] * yuvipanda waves at ChanServ [19:41:10] err [19:41:14] tabcompletefail [19:41:16] haha [19:41:18] * yuvipanda waves at chrismcmahon [19:41:18] fail [19:41:22] :) [19:41:31] hi! [19:42:19] :) [19:42:33] * yuvipanda wonders if chrismcmahon can magically give us more android/iOS beta testers [19:42:36] sigh [19:42:56] yuvipanda: http://www.utest.com/ :D [19:43:22] yuvipanda: "With uTest, iPhone app developers can eliminate delays associated with UDIDs, App Store acceptance and other common problems." [19:43:27] from: http://www.utest.com/iphone-app-testing [19:44:15] 'call us so we can figure out how much we can milk you for' always feels weird to me [19:44:23] but it is possible that I'm too young :) [19:44:32] yuvipanda: we've used them in the past .. its not horrible [19:44:34] but yet .. its lame [19:44:49] but only for desktop [19:44:54] i'm eager to try them for mobile [19:45:32] i do hate having to register to read reports like this though http://www.utest.com/landing-interior/forrester-google-analyst-report [19:45:50] for some reason whenever I hear 'forrester' I just tune out [19:52:06] yuvipanda: "@WikimediaMobile Take the gloss off the icon... UIPrerenderedIcon #phonegap pic.twitter.com/gjW05tSm" @RandyMcMillan [19:52:45] ew [19:52:46] w [19:53:52]