[15:09:49] hey adam_miller [15:09:56] hey hannes-_- [15:09:59] I just sent u two mails [15:10:00] got both those emails [15:10:09] thanks for the feedback [15:10:17] are u still the one who is working on that? [15:10:36] Trevor is doing some work on the capsules now [15:10:42] well....I d like to add that it s a awesome work! [15:11:10] looks like all I do is critizing it - but those are really details [15:11:19] ha thats your job [15:11:33] some of these things are easy changes, others not so much [15:11:47] like the baseline alignment....not so easy to do [15:11:57] hmm too bad [15:12:07] but that doesn't mean we're not trying [15:12:29] did u do the page vacuuming stuff as well? [15:12:30] just don't expect to see that fixed in the next two hours [15:12:39] or was it nimish baby? [15:12:43] initially yes, has there been more work done on it? [15:12:52] i don think so [15:12:54] i havent touched it in a few months [15:13:00] but I was on my way to review iot [15:13:03] review it [15:13:34] ok - so maybe it s a good thing if I review it and give you some feedback [15:13:46] yeah that'd help me get started back into that again [15:14:45] also...if you need any help with graphical stuff or anything else I can do: feel free to fire work at me ;) [15:15:26] (didn t work at all last week - so I have to catch up) [15:17:11] hey RoanKattouw [15:17:31] Hey hannes-_- [15:18:01] *RoanKattouw wonders which of elephant and elephant2 are active [15:18:03] @trusted [15:18:03] --elephant-- [c-67-170-206-100.hsd1.ca.comcast.net, wikimedia/Catrope, adsl-70-137-172-57.dsl.snfc21.sbcglobal.net] [15:18:03] [c-67-170-206-100.hsd1.ca.comcast.net, wikimedia/Catrope, adsl-70-137-172-57.dsl.snfc21.sbcglobal.net] [15:18:07] Ha [15:20:30] hannes-_-: what do you mean by new buttons exactly? [15:21:11] we designed our own buttons for "save" "cancle" etc.... [15:21:45] currently we use the jquery buttons in the dialogs and system-buttons for "save" and "cancle" in the editor [15:22:25] I remember you were almost done with that [15:22:36] and you even had rounded corners [15:23:05] remember? [15:24:32] yeah i do, but i thought those did go live [15:24:45] where are you doing your review? [15:24:57] on prototype? [15:25:12] S7 [15:25:16] wrong? [15:25:36] s-7 may be out of date [15:25:41] I'm not sure when it was last updated [15:25:52] and your not seeing the rounded buttons on there? [15:26:23] they look exactly the same to me as the buttons I have locally [15:26:58] hannes-_-: if you're not happy with the buttons on s7, send me some changes then because I thought those were our final version [15:27:47] adam_miller: I see windows systems buttons on s7 [15:27:54] in the dialogs? [15:27:54] you don t? [15:28:03] no on the editor [15:28:11] oh beneath the editor [15:28:25] right [15:28:42] yeah on dialogs I can see our buttons [15:29:15] I ll resend a mockup to you for the buttons beneath and above the editor [15:29:26] we wanted to habe a gray and a blue button [15:29:34] to emphasize the save-button [15:29:44] hi there [15:29:50] we could use that for the dialogs as well [15:29:59] hi guillom [15:31:05] so adam_miller and RoanKattouw is s7 up to date? how can we find out? [15:31:26] i'll update it [15:31:31] to make sure [15:31:37] cool [15:31:38] thx [15:31:58] adam_miller: Please update it on tesla (208.80.152.248) as well in that case [15:33:18] RoanKattouw: do i have access to tesla? i only half payed attention to that change [15:33:49] Yes [15:34:10] Excpet that there's no external DNS alias yet, so you need to use the IP [15:34:54] Aw crap [15:35:01] do i need to update it on prototype.wikimedia.org as well? [15:35:06] I just spent half an hour writing what I thought was a performance update [15:35:07] Yes [15:35:16] *performance improvement [15:35:36] Turns out that the case where it harms performance is much more common (thousands to one) than the case where it helps [15:37:16] *RoanKattouw destroys all his local changes [15:38:12] hannes-_-: UP TO DATE. [15:38:20] adam_miller: brilliant [15:40:00] uhh what happend to the ntoc on s7 [15:40:10] hmm nevermind....that s not what 27 is about [17:19:10] I need to create a pop-up in which users can upload an image, previewx it, and provide a caption. Is there any MW stuff I could use for this purpouse? If not, anyone aware of some awesome jQuery plugin that would be well suites for this? [17:20:48] hi JeroenDeDauw. have you tried add-media-wizard gadget michael dale created? [17:20:58] you can enable it from user preferences [17:22:47] weird, template wrapping is not happening after my latest update [17:25:04] pdhanda: that's a good thing no? [17:27:08] no i mean when you type a template the little widget does not appear any more [17:27:13] i think it broke in r63530 [17:27:38] it works in r63526 [17:27:39] oh [17:32:42] nkomura: No I have not - any docs on that? [17:34:21] both michael and I blogged about it [17:34:32] i can walk you through how to enable it or send a link to the blogs [17:35:27] nkomura: Is this widget available on wikimediafoundation.org? [17:36:05] yes, the gadget is available through any Wikimedia projects [17:38:02] nkomura: Awesome. Links to the relevant blog posts would be great. [17:38:57] one sec, let me look it up [17:39:36] adam_miller: some of these changes that hannes mentioned - I did yesterday [17:39:43] some of them i'm unsure I agree with [17:39:49] i thought you might say that [17:39:58] which one did you change yesterday? [17:40:24] the baseline thing is solved - that was never intended afaik - i just took on this work so it was an artifact of whoever set it up before me [17:40:39] the alignment with the bottom is solved for good afaict [17:40:53] i got failry creative coming up with a way to get that done right [17:41:22] oh? it looked pretty broken when i updated this morning so i just committed another fix for baseline stuff [17:41:24] I cleaned up the icons allot in the past few days [17:41:31] really? [17:42:04] yeah man, things were all disconnected and misaligned [17:42:15] what were you testing it in last night? [17:42:17] might have been commits after me? [17:42:18] lookin [17:42:22] localhost/prototype [17:42:36] browser, i mean [17:43:18] FF3 [17:43:21] my understanding is that FF3 is our target right now, so i was judging it based on that [17:43:24] the only browser we need to worry about right now [17:43:35] k cool [17:43:42] FYI wikiEditor.highlight.js Comment out lines 315 through 317 for new template wrapping to work again. Added a comment to code review [17:43:54] yeah, now there's a problem, the capsule moved when you click it [17:44:28] and it's taller than the line-height so when it is in a body of text, it make the line it's on taller [17:44:45] pdhanda: What's on those lines? [17:44:58] *RoanKattouw has to run out and has local changes, just wants to know real quick [17:45:04] TrevorParscal: send me a screenshot [17:45:15] it looks perfect for me in FF3.6 [17:45:42] JeroenDeDauw: i've got distracted by email and other IM [17:45:48] RoanKattouw: [17:45:49] if(cBreak){ [17:45:49] return; [17:45:49] } [17:45:53] looking up the link for you now [17:46:09] after var ca1 = startNode, ca2 = endNode; [17:46:10] if ( ca1 && ca2 && ca1.parentNode ) { [17:48:04] Oh Nimish's new code [17:48:06] I didn't even look at that yet [17:48:15] I have some nice performance improvements in there now [17:48:24] (there = highlight.js and wikiEditor.js) [17:48:30] I'll commit them when I get back [17:50:54] good timing nimish_g [17:51:25] http://www.mediawiki.org/wiki/Special:Code/MediaWiki/63530#c6177 [17:51:39] ^ for nimish_g [17:52:02] k [17:52:08] TrevorParscal: http://i44.tinypic.com/nmn41i.jpg and isnt the moving of the capsule a result of it's display being changed from inline-block to block? [17:52:40] adam_miller: one sec - sorry [17:56:29] adam_miller: basically, your changes make it break in my browser [17:56:40] what version of ff? [17:56:45] do you have local changes? [17:57:03] no, and 3.5.8 [17:57:04] JeroenDeDauw: here are the links to the blogs [17:57:15] when I revert you changes to jquery.wikiEditor.html everything starts working again as it should [17:57:22] http://techblog.wikimedia.org/2009/10/new-media-features-gadget/ [17:57:25] could it be that different between 3.6 and 3.5.8? [17:57:31] http://blog.wikimedia.org/2010/01/26/multimedia-usability-project-underway/ [17:57:51] nkomura: Thanks [17:57:55] *JeroenDeDauw looks at them now [17:58:19] adam_miller: it's possible, I know it's not perfectly aligned in chrome (a couple px off) [17:58:56] what's the deal with taking the gradient out of the expand image? [17:59:02] why is that better / a good idea? [17:59:16] ask hannes_away [17:59:29] hannes_away: ??? [17:59:50] TrevorParscal: why dont you email him and cc me since he's not here [18:00:23] and paru as well [18:00:32] this can be our new closed tabs vs. open tabs [18:00:53] JeroenDeDauw: this blog about subtitles by michael dale may interests you too [18:00:54] http://techblog.wikimedia.org/2009/11/fun-with-subtitles/ [18:08:17] TrevorParscal: I just downloaded FF3.5.8 and it's rendering the capsules the same way as 3.6 was for me. Not seeing any brokenness [18:09:09] nkomura: The gadget is totally awesome. Unfortunately, it's not quite doing what I need. I have a submission for looking like this [18:09:10] http://upload.wikimedia.org/wikipedia/meta/e/e0/Wikimedia-storyboard-mockup02.png [18:09:10] When a user hits an upload button there, he/she should get a similar pop-up, but with simple upload from the user's machine (this is for avatars). [18:09:10] Any way to re-use stuff of what the gadget is doing? [18:09:28] adam_miller: what kind of test page are you using? [18:09:50] Boeing 787 [18:11:13] TrevorParscal: i can send you the wikitext if you want. Is anyone else seeing brokenness after my last commit? [18:12:01] JeroenDeDauw: i think re-use is of AMW (add-media-wizard) is a possibility [18:12:19] michael (mdale) usually hang around in this room [18:12:47] he hasn't appeared yet [18:13:02] adam_miller: pastebin it [18:13:23] nkomura: So you're saying I should ask him about the technical details? [18:13:45] JeroenDeDauw: yes. you can also email michael at mdale at wikimedia dot org [18:14:20] JeroenDeDauw: you must be working on the storyboard project [18:14:30] i heard about it from erik [18:14:33] nkomura: Yeah [18:14:48] TrevorParscal: http://pastebin.com/uq4aUUKs [18:17:53] JeroenDeDauw: the storyboard project sounds awesome [18:18:16] adam_miller: in the Production section [18:18:22] that template that's on it's own line [18:18:33] nkomura: It is. It's my first WMF project though, so I hope I don't mess up to much things :) [18:18:43] when you expand and contract it, in your browser does it move vertically a few pixels? [18:18:48] k car is ready, will be back soon [18:19:29] JeroenDeDauw: no worries, mediawiki developers will help you out [18:19:57] TrevorParscal: totally. i misunderstood you before. is that the only issue you're seeing? [18:20:04] yes [18:20:18] if you revert your change it doesn't do that [18:20:26] however, I'm sure there's other things you change fixes [18:20:30] I'm just looking at the diff now [18:21:06] using vertical-align with pixels is very likely the problem [18:21:20] ooh [18:21:27] no, i'm changing the bottom margin on expansion [18:21:29] margin bottom - that probably doesn't work how you think [18:21:42] nkomura: Who are you anyway? :d [18:21:55] yeah, it should in theory bring content rendered after it up/down [18:21:57] if I disable that and instead change the top margin on the wikitext it fixes it [18:22:13] My name is Naoko Komura, i lead user experience programs at Wikimedia Foundation [18:22:38] instead, because it's inline, it adjusts the box up/down within the line [18:22:41] i report to erik moeller. that's why i heard about the project [18:23:26] adam_miller: cool - just commit that then [18:23:48] Jeroen, she is a wonderful lady :) I respect her a lot [18:24:36] *nkomura blushes [18:25:04] TrevorParscal: done. [18:25:05] adam_miller: maybe use this as a test page as well -> http://pastebin.com/zQxMM2i5 [18:25:10] thats what I've been using [18:25:17] I have your test page on my wiki as well [18:25:48] aweome [18:26:12] it's still making the line 1px too tall - but I'm totally fine with that for now [18:26:21] we need to focus on the bigger fish at this point :) [18:26:41] nkomura http://stats.m.wikipedia.org/ mobile is taking off [18:28:11] 20 million page views yesterday - am I reading that correctly? [18:28:13] amazing! [18:28:54] isn't it tomsz showed it to me last week [18:29:14] i'm really curious to see the origin of the traffic [18:29:16] that is more then the Dutch Wikipedia and less then the Portuguese on the basis of Februaru [18:29:20] origins i mean [18:29:36] I am working hard to grow mobile traffic [18:29:45] but this is beyond my wildest dreams [18:30:02] this is aggregate of currently available languages right? [18:30:07] yes [18:30:42] the number of languages supported by an adequate localisation is growing fast [18:31:11] so i heard, thanks to your and siebrand effort [18:31:24] and translatewiki contributors [18:31:47] ..the big problem is support for fonts in for instance the Indian languages [18:32:15] also the Japanese mobile main page is not configured ... so the room for growth is huge [18:32:57] (Japanese being the second biggest in traffic with a mobile crazy country :) ) [18:34:27] yeah [18:38:12] TrevorParscal and RoanKattouw, can we chat a little about Citron staging, QA and the release? [18:38:47] Sure [18:38:48] ... [18:38:50] On IRC or on the phone [18:38:51] sure [18:39:02] IRC should be fine [18:39:05] Bleh, is Danese in the office? [18:39:12] no [18:39:17] Grr [18:39:26] Is the also sick? [18:39:29] *she [18:39:51] probably just at a meeting of some sort [18:40:09] so i'm still holding us accountable for deploying Citron on March 15th [18:40:29] working the schedule backward, we need to be in the QA state [18:41:07] i do understand that we are still facing major issues with templates and our focus has been making that component work for the usability study [18:41:41] *RoanKattouw looks up which features Citron consists of again [18:41:53] citron also accomplish one more important objective, which is to restore dialogue feature for beta users who opted in for that feature [18:42:23] Yes [18:42:37] basically we took away features at the end of babaco enhancements release and we still have not stored back [18:42:42] So those dialogs are ready for QA, just get Calcey going on them [18:43:01] I need to make one fix so it won't turn on the iframe when dialogs aren't enabled [18:43:05] it is important that existing beta users have experience with dialogues as this feature is slated for "go default" feature [18:43:11] Totally [18:44:06] my suggestion is to start testing dialogue without iframe in the next couple of days [18:44:30] and deploy the changes even if the template work is not ready [18:44:52] Yes [18:44:55] TrevorParscal: how do you feel about that? [18:44:58] That was my thinking as well [18:45:22] Yes, we should be testing the dialogues with textarea [18:45:34] So I suggest Calcey test all three dialogs with the textarea [18:45:51] Where the priorities are 1. link, 2. table, 3. search&replace [18:45:52] all three? or just links and tables? [18:46:03] And if we discover s&r is broken we'll split it out [18:46:10] k [18:46:13] It'd become its own preference too [18:46:25] so S&R does not work well with text area? [18:46:31] Or we just move the dialogs from the dialogs pref to the toolbar pref [18:46:37] I have no idea how well it works, I didn't try [18:46:40] k [18:46:55] It's just that the table dialog is a bike, the link dialog is your car, and S&R is a truck [18:47:06] RoanKattouw: will you stage the build on all prototypes? [18:47:08] And old bridge will definitely hold the first two [18:47:09] Yes [18:47:22] *An [18:47:42] users of S&R do not mind driving druck [18:47:47] they adore it [18:47:48] ;) [18:47:50] I know [18:48:00] But the old bridge they're driving on has to hold [18:48:41] we'll build the new wide and fast bridge soon [18:49:22] although the switch over to tesla is completed, we are serving prototypes from two hosts right now [18:49:41] RoanKattouw: so will you make sure that both hosts are updated? [18:50:16] RoanKattouw: please write test instruction to bhagya and 'cc trevor, mangala and me [18:50:17] Yes [18:50:22] OK [18:50:32] they should go through all babaco test cases for regression [18:50:42] First I need to make some final tweaks, I'll probably have that e-mail out by lunch [18:50:50] great [18:56:12] RoanKattouw: the code that got rid of the extra line breaks was 295 in highlight, correct? [18:56:22] Ask Trevor [18:56:27] He did that [18:56:39] TrevorParscal: same q =) [18:56:44] what about it? [18:56:58] those conditions that check for


[18:57:01] I'm doing all kinds of things at the moment, I'm halfway a massive performance improvement in the highlighter and now I'm poking at dialogs first [18:57:15] yeah [18:57:24] i was thinking it's possible to have

text
text

and that condition still be met [18:57:58] we should check to see that .text() doesn't contain any non-whitespace characters [18:59:24] It won't [18:59:33] $('

foo
bar

').text() --> 'foobar' [18:59:49] Oh NON-whitespace, nm [18:59:52] :) [19:07:07] hey TrevorParscal [19:07:15] hi [19:07:29] I kind of agree with u - the problem is that the expanded area looks like it is above the capsule [19:07:53] so that s a conflict [19:08:09] above? [19:08:18] like, rendering bug? [19:08:29] no it s a gr4aphical thing [19:08:33] let me try to explain [19:08:36] shoot [19:08:55] the capsule has a gradient - the template is flat (pure #f5f5f5f) [19:09:26] but the gradient fades to that color [19:09:33] no [19:09:35] which is the middle color [19:09:38] no? [19:09:41] for the normal capsule it doesnt [19:09:57] for the new down-status it does [19:09:58] in the image I sent in my email [19:09:59] right? [19:10:19] the shaded version, the depressed expand/collapse button has a shaded background [19:10:30] it goes from the darker gray to the middle gray [19:10:35] right [19:10:42] the middle gray is the gray we are using for the editable area [19:10:48] but for the normal status the gradient is the otherway around [19:10:50] right? [19:10:55] thus, it fades to a middle (flat) shade [19:11:04] thus, it's depressed [19:11:22] i know i know... my point is a bit somewhere else [19:11:32] the dark color indicated the surface is at a downward angle (the light coming from the top) [19:11:40] if you take a look on it without the arrow-area [19:11:54] only the capsule with the gradient from light to dark [19:12:01] the middle gray is a surface which is perpendicular to the vewer (flat with the screen) [19:12:09] and underneath the template with flat gray [19:12:24] than it looks like the capsule is rounded [19:12:29] and the template is flat [19:12:40] which is intended [19:12:45] what's wrong with that? [19:12:56] thats intended, right [19:12:59] yes [19:13:02] and the bottom of the capsule is a bit deeper than the template [19:13:09] agree with that? [19:13:30] deeper? well no, it ends up at the same depth as the template [19:13:53] it's just that the vertical center of the capsule is closer to the viewer [19:14:07] and at a similar angle as the editable area [19:14:08] but it is darker - so for me that indictes that it is deeper [19:14:11] thus they are the same color [19:16:43] i ll do a screenshot to explain [19:21:20] nkomura, TrevorParscal: After fixing two obvious flaws, S&R actually seems to work quite nicely (in FF3 at least) [19:21:43] RoanKattouw: great to hear that [19:22:18] hannes-_-: http://img521.imageshack.us/img521/4022/lightq.jpg [19:23:04] A has a postive angle, the second B (oops, I meant C) has a Negative angle to the light [19:23:07] so typing out new templates is still broken [19:23:15] the first B and D have the same angle [19:23:19] thus, they should be the same shade [19:23:23] A should be lighter [19:23:28] nimish_g: How? [19:23:30] C should be darker [19:23:56] make sense? [19:24:06] not the best illustration - sorry, I'm trying to be really quick [19:24:56] so your point is that the depressed state should be all the color B/D [19:24:57] flat [19:25:04] RoanKattouw: I was trying to detect whether a 'realchange' is a change where the user is typing inside an existing template or not. I figure that means the start position will already exist and the end position would change. I look for anything where the start position is the same and I just don't touch it, which works fine [19:25:12] which could physically make some sense [19:25:27] BUT that also means that if you're typing a brand new template it won't get wrapped [19:25:32] nimish_g: Ah that, yeah I'm behind on CR, I haven't looked at anything committed after lunch yesterday [19:25:44] my point is that I want it to look more depressed and stand out a bit more so I wanted to use shading to make it more dramatic [19:25:49] Right so you need to accommodate for that use case [19:26:14] OK so at least this breakage isn't my fault :) now I can continue my dialogs work without guilt [19:26:31] RoanKattouw: ya pdhanda left a msg on one of the code commits about how it breaks wrapping newly created templates. it also broke the old 'enter' behavior...I'm working on getting bindings to stay when you hit enter now [19:26:37] lol yeah, not *this* time =) [19:26:49] :) [19:27:27] I see pdhanda is trying hard to replace me as the light-speed code review hawk :) [19:28:26] nono i would not dream of that.. i am too much of a slacker ;) [19:30:06] TrevorParscal: good graphic. i used it and sent it back to u to explain what I mean [19:32:39] when you say B you mean the first B (sorry about that typo) [19:32:46] http://img85.imageshack.us/img85/1228/profilesf.jpg [19:33:54] I'm proposing using B in this illustration for the name and dialog button in the capsule and C for the expand/contract button [19:34:07] hmm ok I see the difference about you and me sight if it [19:34:19] it does not look like B to me [19:35:36] Well, the name and dialog button of the capsule when expanded are < light - middle - dark >|< middle > [19:36:16] so? [19:36:31] we are just deciding if the expand/contract button should be < middle > | < middle > or < dark - middle > | < middle > [19:36:43] I think we both have some points [19:36:57] actually your graphic is right. but it does not look like the profile you made [19:37:21] yes I think so too.... I know what you mean - but I just can t look at it like you mean it [19:37:32] it s linke one of those switch-view-imgaes [19:37:52] oh, an optical illusion? [19:37:52] ha ha [19:38:15] RoanKattouw: we don't have a method to let us know what element the cursor is in, do we? [19:38:43] No [19:38:54] And be careful writing one, it needs to be O(1) not O(n) [19:39:00] That requires different approaches in different browsers [19:39:07] hannes-_-: it would be a little better if the editable area was white [19:39:14] http://rlv.zcache.com/young_woman_or_old_lady_optical_illusion_flyer-p2449584234590172452mcvz_400.jpg [19:39:25] Stuff like getCaretPosition() -> getOffset() will be O(n) in Firefox or IE (don't remember which offhand) [19:39:31] yes, optical illusions are fun - ha ha [19:40:17] if I want to throw up random technical notes for the benefit of mostly internal users, where would that go? [19:40:28] i.e. which wiki [19:40:33] hannes-_-: we can just leave it be for now [19:40:42] I think we've discussed it plenty [19:40:49] agreed [19:40:52] I'm not THAT worried about it :) he he [19:41:07] no me neither [19:41:07] flat is a-ok with me [19:41:44] btw - the line above the buttons is on all dialogs now, and there's a cancel button the template dialog [19:41:52] I'm pretty sure all of your notes are implemented at this point [19:42:09] great [19:42:16] we need to update the sandbox on the new server [19:42:26] flipzagging: an example would be helpful [19:42:35] TrevorParscal: s-6 and s-8? On it [19:42:39] I was just updating stuff anyway [19:42:48] RoanKattouw: thanks! [19:42:53] can we use the URLs yet? [19:42:57] domain names I mean [19:43:06] are the DNS records all updated? [19:43:08] Type ping prototype.wikimedia.org in your shell [19:43:14] If the IP starts with 208.80 , it's updated [19:43:20] It is for me at least [19:43:30] nkomura: I was going to write up some notes on how we want to develop the backend, after the usability test is done [19:43:47] yup [19:43:49] sweetness [19:43:52] nkomura: and more specifically why we aren't doing that before the usability test [19:44:21] I'm updating the regular prototypes now [19:44:30] I'm starting s-6 and s-8 [19:44:35] After that I'll do the deployment prototypes [19:44:42] cool [19:44:54] nkomura: I started to write you an email but it turned into an epic novel, so I figured I might as well make a wiki page [19:45:02] hannes-_-: thanks for hashing out gradient contours with me :) [19:45:15] not many people like to talk about stuff like that :( [19:45:38] flipzagging: it can live in multimedia hub of the usability wiki [19:45:54] mediawiki wiki, or office wiki [19:46:12] officewiki = private = evil for anything that doesn't need to be private [19:46:14] nkomura: unfortunately I can't log into that wiki. It blocks me because "NeilK" is taken in the unified login system, but doesn't let me log in. :( [19:46:35] RoanKattouw: any luck on performance btw? [19:46:40] nkomura: who manages that wiki? [19:46:42] which wiki are you blocked from? [19:46:56] nkomura: usability.wikimedia.org [19:47:08] flipzagging: You do own NeilK in SUL? [19:47:20] RoanKattouw: yes, which is the weird bit [19:47:25] most of us within the UX team are admin [19:47:30] RoanKattouw: tried clearing cookies, logging in and out several times. [19:47:36] RoanKattouw: btw - some of the FF people told me that the uber-performance stuff in the JS engine turn off when firebug is on [19:47:45] so profiling is "unrealistic" [19:47:49] Right [19:47:50] Seems dumb to me [19:47:54] but makes sense [19:48:08] but it still helps find the slow parts [19:48:09] I heard try-catch turns off uber-performance stuff [19:48:16] And Firebug probably will use try-catch [19:48:38] As well as doing other evil stuff to set breakpoints and the like [19:49:00] but they were saying that the optimizer has profound effects on certain kinds of closures and that a function you think is really slow in profiling is actually really fast - also the optimizer does some inlining type stuff [19:49:01] flipzagging: Probably an empty password field in the DB, will poke [19:49:09] Right [19:49:12] RoanKattouw, nkomura: never mind, I seem to be able to log in with Chrome. Something wrong with FFox. [19:49:12] but I'm getting slow results with or without firebug [19:49:14] :( [19:49:22] Yeah I optimized a lot [19:49:25] And am doing even more [19:49:28] awesome [19:49:30] flipzagging: that is concerning [19:49:33] Right after I wrap up this dialogs thing, which should be really soon now [19:49:37] will you file a bug about that? [19:49:45] s-6, s-8 and regular prototypes are now up to date [19:50:00] Probably something wrong with his cookies or something [19:50:17] nkomura: it's probably some weird cookie issue, but if I find it is a bug I'll log it [19:50:23] nkomura: who file a bug about what? [19:50:26] oh [19:51:15] TrevorParscal: flipzagging found the log-in worked in chrome but not in FF [19:51:30] it is not specifically our stuff, but it will be good to keep record [20:06:24] Hm, I need to move elephant's logging from the old Linode to tesla [20:06:37] It's still logging but the logs are no longer accessible on the web [20:08:05] RoanKattouw: good catch [20:13:29] TrevorParscal: It seems our checks disallowing specific versions of FF2, e.g. 2.0.0.0 - 2.0.0.4, have disappeared [20:15:55] RoanKattouw: TrevorParscal stepped out for lunch [20:16:03] Ok [20:16:32] I'll just tell Calcey FF 2+, and I'll correct that if it turns out we do want to blacklist 2.0.0.4 and friends again [20:19:10] it will be best not to confuse calcey folks [20:20:20] RoanKattouw: hmm [20:20:35] well when the dialogs were pushed to FF3, that check was not needed [20:20:40] it was a jquery-ui issue [20:20:51] Ah [20:20:52] so now we have to restore it for the dialogs [20:20:55] Right [20:21:00] Could you go do that in SVN? [20:21:22] yes [20:21:25] one sec [20:21:29] So I'll tell Calcey FF 2.0.0.5+, that's correct, right? [20:21:59] nkomura: By what time/date do you want Calcey do be done with (the most important parts of) these tests? [20:23:02] by 9am PST so 5pm UTC? [20:23:15] Tomorrow? [20:23:20] yup [20:23:34] they may not complete it as we want them to run all regression [20:23:47] TrevorParscal: how important is it to prevent users from entering multiple \n in the template editor dialogs? parsing them out on update was easy, ensuring they're not entered in the first place is not so much. [20:24:02] but we are free to make a wish [20:24:14] "Please try to get the highest priority tests (link and table dialogs for the highest versions of each browser) done by 17:00 UTC on Thursday March 11" [20:24:59] sounds good [20:25:24] adam_miller: actually - i realized the other day that that is not a requirement [20:25:38] a template can have any number of empty lines in it and it won't break [20:25:44] we should remove that line [20:25:52] alright, i'll get it out of there then [20:26:13] Such lines have the potential to cause dirty diffs, which are evil in their own right [20:26:19] RoanKattouw: it is important to mention that confirming copy-paste issues do not crop up with dialogues [20:26:25] http://spreadsheets.google.com/ccc?key=0AsH79AXxmoh-dEhRZ0JFVmtaOTFEeVFvano2cTk5ZHc&hl=en [20:26:26] Right [20:26:45] it'd be good to exercise copy-paste matrix [20:26:59] So what does that mean? You do or don't want them to verify copy-paste bugs? [20:27:34] Since we're talking about a textarea rather than an iframe, the chance of getting CP bugs is pretty much zero, and if they do happen they're the browser's fault [20:28:14] mdale: I have some questions about the add media wizard widget. Do you have some time? [20:28:14] are you confident about that? [20:28:25] Yes [20:28:33] And I bet TrevorParscal will agree [20:28:36] no need to spot check? [20:28:49] TrevorParscal: Do you agre that checking for copy-paste bugs in an iframe-less situation would be unnecessary? [20:29:09] what i want to avoid most is re-introduce copy-paste bugs with this release [20:29:14] yes [20:29:15] Oh also, if they magically do happen, they'll also happen without our software [20:29:24] exactly [20:29:34] So not only am I confident they won't happen, if they do happen, I'm confident it won't be our fault [20:29:48] JeroenDeDauw:sure [20:29:52] k [20:29:53] the textarea we use will have the same good/bad qualities as the textarea without our software [20:30:24] i'm fine with asking calcey to focus on dialogue features then [20:30:42] RoanKattouw: did you see my commit? r63572 [20:30:45] OK [20:30:47] Sending e-mail [20:30:52] and please let them know that NTOC is still being disabled so they should not file a bug about that [20:30:55] TrevorParscal: I didn't see anything that was committed in the last 24 hrs [20:31:00] I'm way behind on review [20:31:07] yeah, me too [20:31:20] nkomura: I told them to enable dialogs&toolbar and disable NTOC in their prefs before running these tess [20:31:23] I started in on it today but I have allot of pressure to push forward on some of these bugs [20:31:36] *and* to double-check their prefs before filing bugs [20:31:43] lol, way behind = 24h for me [20:31:46] aka, we're now sacrificing quality control for development speed [20:31:59] Temporarily [20:32:03] Hm it's only 98 e-mails [20:32:13] yes, it needs to be temporary [20:32:36] E-mail to Calcey sent, also sent to usability alias [20:32:44] but what's very common is that once a team shows a certain pace of development, that pace is expected to be maintained even as other variables change [20:32:56] Yeah [20:33:01] it needs to be well noted that this pace of development is basically irresponsible [20:33:13] and that we are only doing this because we are in a tight spot [20:33:14] Not that much, actually [20:33:20] Because you guys don't commit code over the weekend [20:33:30] ? [20:33:31] mdale: I'm working on the Soryboard extension. It has a form via which users can submit stories, which has a button that, when clicked, should show a popup enabling the user to upload an image, preview it, and add a caption. This is very similar to what your gadget is doing. Can it somehow be used for this purpouse? [20:33:32] And I do work on weekends, so that's when I can catch up on review :) [20:33:56] JeroenDeDauw: sure ;) [20:33:59] yeah, we're not supposed to have to work on weekends [20:34:36] Well I don't /have/ to work on weekends either, but I choose to so I can slack/sleep/study during the week [20:34:54] right on [20:34:55] And generally work fewer hours per day [20:35:09] yeah, if I worked a weekend it would really cause allot of problems in my family life [20:35:39] but when I was without children I used to work weekends all the time [20:36:38] RoanKattouw: good summary [20:37:08] Of course [20:37:21] If I would catch you working in the weekend I'd slap you [20:37:51] ha ha [20:51:49] nkomura: Thanks [20:52:01] OK I'm gonna disable logging for 5-10 mins now as I move it to tesla [15:54:38] @trusted [15:54:38] --elephant-- [c-67-170-206-100.hsd1.ca.comcast.net, wikimedia/Catrope, adsl-70-137-172-57.dsl.snfc21.sbcglobal.net] [15:54:58] Move done [15:58:06] fun [16:07:11] nimish_g… sorry to keep bugging you but after r63566 i get a javascript error... [16:08:58] this[0].innerHTML is undefined [16:08:58] http://localhost/deployment/skins/common/jquery.min.js?268 [16:08:58] Line 44 [16:10:25] actually i am not sure it is that commit… let me poke around some more [16:10:45] pdhanda: Would be helpful if you could break on that error, trigger it again and record 1) the function call stack and 2) what kind of node this[0] is [16:11:00] I recognize that error but I don't completely remember what causes it [16:20:07] k let me try thatr [16:20:21] omg she turned into soup [16:20:51] parutron_soup my brain feels like soup also [16:31:13] so the error stack says it is happening on the call from jquery.wikiEditor.templateEditor.js?268 line 80 the node is span.wikiEditor-highlight [16:32:06] WTF [16:32:12] How does a span not have a .html() [16:32:17] Wait, is this Internet Explorer? [16:32:22] FF3 [16:32:26] :O [16:32:32] on sec [16:32:35] let me make sure [16:32:35] Is this[0].parentNode defined? [16:32:49] What about this[0].childNodes ? this[0].nodeName? [16:33:31] nodename is #document [16:34:13] span may not be right i may have caught it before it errored :P [16:35:14] Aha [16:35:37] Can you trace back to the first level in our code and see what the jQuery call is? [16:39:06] so node is null the call is function is onSkip() [16:39:49] Ha [16:39:53] markers[i].onSkip( anchor ); in highlight.js [16:39:57] It's calling onSkip(null);? [16:40:16] Nimish's fault [16:40:17] appears that way [16:40:18] if ( !anchor && !cBreak ) { //cBreak prevents a new span from being created which stops cursor jumps [16:40:31] That used to be if ( !anchor ) { code } else { onSkip(anchor); [16:40:53] dang [16:41:11] You'll have to ask nimish_g what the expected behavior is for !anchor && cBreak [16:41:26] TrevorParscal: mind if i start working on rebinding template events after an undo/redo? [16:41:32] I have no idea what went on there, I'm behind on code review [16:41:41] adam_miller: I have some input about that [16:42:29] pdhanda: nimish_g has also acknowledged that typing in new templates is broken [16:43:30] RoanKattouw I'd love to hear it unless Trevor has something else for me to be working on [16:43:48] Well I'm still kinda pondering it [16:44:02] RoanKattouw I was going to start by extracting the event binding from the wrapTemplate function [16:44:13] I would like it to hook into the existing highlight API, i.e. the afterWrap, onSkip, beforeUnwrap functions [16:44:20] adam_miller: That's a good start, needs to happen anyway [16:44:55] do those events make callbacks we could listen for? [16:44:57] Problem is we probably won't have a marker object attached (as we presumably lose .data() as well) [16:45:10] They're not events, they're functions inside marker objects [16:45:21] grep for either of those names and you'll see [16:45:38] Problem is that given a node, we need to figure out which module is responsible for binding it [16:45:55] We normally do that through a marker object attached with .data(), but I expect .data() will be gone as well [16:46:40] I was imaging we'd fire a htmlChange event or something whenever we call html('blah') on the iframe and each module could handle the event in it's own way [16:48:07] Hmmm [16:48:09] Or... [16:48:26] Presumably delayedChange fires after an undo [16:48:41] Inside the highlighter's delayedChange handler, onSkip() will be called [16:49:02] (onSkip means I'm visiting this already-wrapper wrapper and not gonna unwrap it, update what you need) [16:49:15] We could have our modules' onSkip functions check whether the bindings are still there [16:49:51] The easy way to do that would be to add like .data( 'bindingsStillHere', true ); when adding the bindings [16:54:10] It's only a matter of time before RoanKattouw speaks perfect San Francisco English, complete with 'hella' and other weirdness [16:54:13] then we'll all be doomed. [16:54:37] My Californian is pretty good alraedy [16:54:53] But it's been nearly two months since my last visit so it's degrading :) [16:55:12] It freaks me out to hear Californian English with a Dutch accent. [16:55:24] haha [16:55:27] *RoanKattouw takes offense to any suggestions he has a Dutch accent [16:55:40] Presumably you've heard Gerard talk [16:55:40] Well, you do still have one :p [16:55:43] or you did at Wikimania [16:55:47] well yes, it's not strong. [16:55:56] But it's very difficult to get rid of the last vestiges of an accent. [16:55:59] I have Californized significantly since then [16:56:22] Speak to me when I've just spent a week in SF, and you'll probably hear it much less [16:56:52] i am told my Indian accent becomes stronger after a few drinks [16:56:55] I think nkomura will attest to the fact that my accent is "loud" [16:56:59] Actually it's scary how impressionable my accent is [16:57:45] After hanging out with a group where the only native English speaker was Liam for a night, I had to stop myself from sounding too much like him [16:58:48] Liam Wyatt? [16:58:50] Yeah [16:58:54] When did you hang out with Liam Wyatt? [16:59:18] Last year in Berlin [16:59:46] oh speaking of which, I think it's possible for me to skip a week of classes for Berlin. Whether I want to or not is something I'll have to figure out quickly [16:59:51] Liam, Dror, Lodewijk, Erik Z, possibly others, and myself hung out that night [16:59:55] ah [17:00:07] Yes, Daniel says spots are running out [17:00:40] well, only half gone [17:00:48] and they did open a week or so ago [17:00:56] so I reckon I can wait until the weekend if I have to [17:01:27] werdna: what are you talking about? You speak lovely. [17:02:12] nimish_g http://www.mediawiki.org/wiki/Special:Code/MediaWiki/63566#c6183 :/ sorry I am being such a pain [17:03:18] nkomura: but loudly :) [17:03:34] pdhanda: annoy him some more! [17:03:36] get him! [17:03:46] salut basile [17:04:16] RoanKattouw: I'll need to check with Erik that he's still interested in sending me, etc. [17:04:23] Right [17:04:41] I hear that's not as much of a no-brainer as it once was [17:04:52] what do you mean? [17:05:07] Well last year they sent like every staff dev [17:05:40] It seems they're not gonna do that this year, and AFAIK it's not known who's gonna go and who's not [17:06:11] Erik's already said he's interested in sending me, it's just that I said I probably wouldn't be able to make it -- and I don't want to sign up for it without knowing for sure that somebody doesn't mind flying me there :p [17:06:20] :) [17:06:37] *werdna should start getting ready for uni [17:06:53] Yeah you didn't go last year, that's a pretty good argument for sending you this time [17:07:14] I'm naturally gonna be there, and I think Mark is as well, since we're pretty close to Berlin [17:23:30] ugh, brain feels like mush today [18:10:01] stupid Roan having to sleep...how silly [18:11:06] pdhanda: essentially I think I need Roan to look at those changes I made b/c they weren't made in a logical way, I just had them break on marking at the point that they caused cursor jumps [18:11:11] adam_miller: so the footer cleanup stuff [18:11:30] yes? [18:11:50] hmm [18:11:57] Roan said to talk to you [18:11:59] how do I play with that [18:12:14] i turned it on, nothing seemed to change [18:12:24] i'm working on the Redmine stuff this afternoon.. i'll follow up tomorrow on Usability stuff [18:13:02] nevermind [18:13:46] changed the wrong setting [20:05:13] TrevorParscal and nimish_g [20:05:15] are you around? [20:05:21] sup? [20:05:23] yes [20:05:33] scheduling this study is unendingly worrisome [20:05:46] :-( [20:05:47] before i lock down any dates, want to get your concerns [20:05:49] *TrevorParscal feels for parutron [20:06:13] *guillom hands some hot chicken soup [20:06:25] i'm trying to juggle our deadline, guillaume's study schedule, and our teams schedule. [20:06:35] first off nimish_g will you be staying on for the stanton extension? [20:06:36] my concern is getting the code done... [20:06:40] until april 30th? [20:07:26] thanks guillom, hot soup is the cure for everything ;) [20:07:31] nimish_g: [20:07:32] héhé [20:07:37] parutron: not unless I can work from Nepal...my mom's leaving in a week and her dates in Nepal are pretty fixed...I can stay here upto the April 20th at the latest [20:07:49] k. [20:08:34] if we have the study the week of march 22nd (as we last discussed), we'd basically need the banner up by next monday [20:08:37] *pdhanda is gone for the next 2 weeks [20:08:44] not that i'm much help anyway [20:08:50] you are?? [20:09:09] I'm moving between March 24th and March 28th [20:09:11] yeah next week and the week after that [20:09:15] lol [20:09:24] does that mean those copy paste iframe thingies will be worked on after you return? [20:09:39] the 24th, 25th and 26th are a Wednesday, Thursday and Friday respectively [20:09:53] i am working on them now… and yeah I'll pick up after i return [20:09:57] I want to take at least SOME of that time off [20:10:05] *TrevorParscal is being held captive against his will [20:10:10] tee hee [20:10:28] i'm less worried about you being available for the actual study dates than before them. [20:10:54] do you think that between the two of you, you'd be able to handle the banner + recruiting over next week? [20:11:21] yeah [20:11:41] we're running the same things as before but with different %agess right? [20:11:59] yup. i imagine it should be straightforward? [20:12:05] i mean, it's going to happen durring our heads-down-develop-code-faster-or-else time period anyways [20:12:19] but still requires time away from what i know is already a push for you guys... [20:12:20] yeah [20:12:21] jinx [20:12:23] and when is that? [20:12:31] which part of that time period is largely irrelevant [20:12:49] from now until ... probably ever [20:12:56] :) [20:13:00] or March 15th, whichever comes first [20:13:01] by the way, it would be helpful to know how you handle this banner thing, 'cause I have to put mine online too, and from what I understand there's little documentation about this [20:13:21] tee hee. [20:13:28] and how is the March 15th release looking? [20:13:33] guillom: well, it's actually just turning on a central notice notification, something the fundraising folks do allot [20:13:47] wait copy/paste iframe issues are going out in April right? [20:13:52] there's some other considerations, but nothing a 1 hour meeting with neil and I can't solve [20:13:56] TrevorParscal, oh, good, I was afraid it was more complicated that Centralnotice [20:14:01] great [20:14:10] thanks [20:14:17] guillom: nah, it is just centralnotice =) [20:14:34] guillom: ethnio gives you a cute little link to embed in said central notice. [20:14:47] but march 15th - looking good? [20:14:47] pdhanda: pdhanda depends - they are still trying to get us to make templates + iframe available to anyone who turns it on in their prefs on March 15th [20:15:05] ooooh [20:15:08] crap [20:15:20] March 15th is …Monday! [20:15:26] parutron: well - we sort of rebuilt - you know, i'll just hash it out with neil when the time comes [20:15:34] dude, seriously! [20:15:36] how far back would you guys have to push against march 15th to make said release (i.e. templates + iframe available to anyone that turns on their prefs) [20:16:03] I'm leaving for Mexico on Saturday…. [20:16:18] well, we're just going to release it as is [20:16:22] I mean, what else can we do [20:16:44] there's no flexibility in the release shedule and we're working as hard/fast as we can [20:16:53] yeah. (sympathies) [20:17:05] i'm going to stop work on this redmine stuff then… i wanted to leave it in a usable state before i left [20:17:21] if we did push back the study by a week, it doesn't do much for you guys? [20:17:29] how long will you be in mexico? [20:17:29] esp. with pdhanda out in mexico.... [20:17:58] parutron: no because we also have to switch gears to get the "going default" stuff ready [20:18:06] 2 weeks March 13th through 27th [20:18:35] huh. [20:18:38] and there's still bits of code that haven't really been reviewed / are very immature and need to be iterated on like the footer cleanup [20:18:39] this is madness! [20:18:46] it's really quite bad still [20:19:08] parutron: agreed [20:19:13] tee hee [20:19:19] no wonder i'm sick! [20:19:26] and a wonder that you two aren't! [20:19:33] and not in a "ahh, let's gripe about work" way - more in a "OMG, are we really attempting this?" way [20:19:39] yeah [20:20:00] well i'm weighing pushing out study, but it doesn't really seem to give us anything. [20:20:07] if I get sick... Let's not talk bout that [20:20:10] beside making guillom happy [20:20:25] when is his study? [20:20:32] long story. [20:20:36] :D [20:20:44] basically, my study is "after yours" [20:20:51] tee hee. sorry guillom [20:20:53] :( [20:20:55] np [20:20:56] :D [20:21:03] I understand your constraints [20:21:13] if we *did* have a reason to push ours, we could keep your days in tact [20:21:15] but i don't think we do. [20:21:27] so i talked to nash and there are two options. [20:21:37] as I said, our time constraints are way less critical than yours [20:21:49] i don't know about you, but i'm anxious (for my and my teams and hell, everyone's sake to lock down the dates) [20:21:52] what are the not pushed back days? [20:22:24] for our project - the week of the 22nd [20:23:02] guillom: if we do that, your study should be a-ok for the week of the 29th, provided goto can get the smaller room rates for you. [20:23:30] ok [20:23:51] i told nash i was gonna confirm by end of day. [20:23:54] I don't see that pushing it back will help anything [20:24:10] am tempted to hold off until we can all be in the same place, but i don't know what [20:24:12] will change. [20:25:28] *guillom contemplates working for 2 or 3 more hours to finish his paper, although his day is actually over [20:25:46] considering it's either that, or working this week-end, I'll probably choose the former :) [20:26:11] don't work on it over the weekend! [20:26:35] I did it last week-end, I don't intend to do it again! [20:28:15] slightly offtopic TrevorParscal http://spreadsheets.google.com/ccc?key=0AsH79AXxmoh-dEhRZ0JFVmtaOTFEeVFvano2cTk5ZHc&hl=en under sopy-paste-matrix [20:28:40] i don't see the double line breaks when i paste from a text editor into the iFrame [20:29:15] the toc highlight does not work, but I can fix that [20:35:25] pdhanda: dude, I said that in the meeting, and everyone was saying "nope, double line breaks dude!" [20:35:39] maybe it depends on how cool the user is... :) [20:37:26] i swear i used to see it [20:37:35] maybe it does not happen on a mac [20:37:58] i'll try tomorrow on my linux desktop [20:38:15] >cool< [20:38:21] meanwhie I'll try to reparse pasted content [20:38:32] right on [20:38:40] yall got my *&*@&# in a bunch with all this timeline talk [20:41:17] let's all remember this experience next time somebody start talking about how long it takes to develop something [21:03:56] tee hee. sorry i think i started it [21:03:56] i'm off [21:04:00] hope you feel better pdhanda [21:04:06] good luck with the paper guillom [21:04:10] go team TrevorParscal [21:04:23] hope you get better, parul [21:09:48] any beos fans out there?