[00:26] French team just likes to be different I think [00:26] paultag: awesome news [00:28] mhall119: what's up [00:28] paultag: just read about ~locoteams being a delegated team, so loco teams can go back to being open [00:29] oh dur, right [00:29] mhall119: yeah, I'm stoked [01:17] Woo! I got our Natty Narwhal design artwork back from an artist friend. [01:17] [01:17] [01:17] [01:17] http://ubuntuone.com/p/ie0/ [01:17] Now to design CDs. :D [02:51] good morning [06:30] good morning [06:34] YoBoY: good morning [06:47] mhall119: french team is old. When I look at my community and how many ubuntu events we have in march, I think being different is good ;) [06:47] hi aakshay [06:48] hi yoboy :) [07:02] YoBoY: where all the files for css are stores in loco_directory? i need to access them.. [07:04] aakshay: most of them come from the ubuntu-website project [07:05] aakshay: but try in media directory [07:05] YoBoY: media directory in ubuntu-website folder? [07:06] this one, and the other one [07:06] ok. thanks.. :) [07:06] you can't directly modify files in ubuntu-website, this files have to be modified in the ubuntu-website project [07:07] YoBoY: ok.. and i would like to ask one more thing that [07:07] how can i access the comment id from the database? [07:08] or what is the primary key they use to uniquely identify wach comment? [07:09] don't know ^^" [07:09] You have to wait and ask to one of the LD devs [07:10] its ok.. thanks :) [08:16] good morning [09:52] good morning [09:53] hey daker [09:53] mhall119, Ronnie file a bug and assigned to me [09:58] morning [10:00] hey aakshay, back again [10:02] how can i access the comment id from the database? [10:02] Comment.objects.get(pk=commentId) [10:02] aakshay: ^ [10:03] K'day all [10:03] Ronnie: hey... :) [10:04] Ronnie: yes.. i am facing the problem doing this.. [10:04] if you need to edit CSS, think first is the changes should go to the whole ubuntu-theme, or just loco specific. If the latter, then you can add css to the newstyle.css in /media/css otherwise you have to change the ubuntu_website/media/css/default.css and merge it into ubutnu_website first [10:04] Hi Tm_T [10:05] aakshay: what bug are you trying to solve? [10:05] Ronnie: 616383 Needs ability to directly link to a comment [10:05] the above bug [10:06] oke [10:06] in this, i need to print the complete comment on the new web page. but i am not getting how to access the required comment from the database? [10:07] there are 2 ways to do that. make a separate page with only that comment or work with hashes (name="myname" and url#myname) [10:07] which of the two ways do you want to make [10:07] Ronnie: i am planning to make a new page [10:08] Ronnie: but then i need to declare "url" and many more things which i am confused in [10:08] :( [10:08] the disadventage i usualy have, it that the context and latter comments are not visible [10:09] i will lead you trough the process, but first we need to have to same "plan" [10:09] yes.. [10:09] i have spent all these days deciding the plan only.. :D [10:09] can we start by today itself?.. :) [10:11] so whats your plan? [10:12] Ronnie: my plan is to add a "view" label instead of "#1" as in "https://bugs.launchpad.net/ubuntu/+bug/1/comments/1" in the grey portion on the right most side [10:12] Launchpad bug 1 in tilix (and 20 other projects) "Microsoft has a majority market share (affects: 621) (dups: 1) (heat: 2890)" [High,New] [10:13] then link this "view" to the new designed page [10:14] Ronnie: Then on the new designed page, we will acess the required comment from the database and print as shown in the above demo web page. :) [10:14] oke [10:14] Ronnie: thats my plan but i dont know whether its efficient or not.. :p [10:15] not sure about it. i guess its more work that adding a #mylabel to an url [10:15] Ronnie: adding to which URL?.. :p [10:15] and you dont have the ability to see other comments, thats why i dont like the LP comment style [10:16] Ronnie: yes it is... [10:16] for example: http://loco.ubuntu.com/events/team/825/detail/#comment1 [10:17] Ronnie: but i dont get one thing that we need to display the above comment on the different web page as in demo or we can do as per our choice? [10:17] :) [10:19] aakshay: its pretty easy. all comments we need to add a name= tag in the template, and make a link to the name= tag, thats all we need to do [10:19] if we want to, we can highlight the comment with javascript [10:19] Ronnie: ok. its like making "href" on the same page.. :) [10:19] aakshay: yes [10:20] Ronnie: ok.. that will be nice then [10:20] if the url caontains a #, the browser will scroll down the page, till it meets the corresponding name= tag [10:21] then one more thing, do i need to change the look of the comment display pattern? mans adding some CSS to it?. [10:21] you can add the 'highlight' part [10:21] we need to add some jQuery for that i guess [10:21] i will lead you trough that too [10:22] Ronnie: ok thanks beacause i dont know about jquery [10:22] :) [10:22] first you need to find the template responsible for the comment part [10:22] can you find these? [10:22] yes.. [10:23] its in event/team_eevnt_comment.html [10:23] Ronnie: and also in team_event_detail_comments.inc.html [10:24] *its in event/team_eevnt_comment_new.html [10:24] yes, the team_event_comment_new is to create a new comment [10:24] the team_event_detail_comments.inc.html is the include to view the comment [10:24] yes.. so i am editing the later one [10:24] indeed [10:25] yes [10:25] any idea how to start? [10:26] hmm.. i will add "view" label on the right side [10:26] with anchor tag with it [10:27] yes, an anchor tag (thats the word i was looking for all the time) [10:27] is it fine? [10:27] :D [10:27] but the "name= " wil be tough to design [10:28] because in for loop we need to name it and need unique names for that [10:28] i hope u got me.. :D.. i am making it all a mess [10:28] :) [10:29] i can still follow ;) [10:29] so need a comment id or so to append in name of every commenr [10:29] right [10:29] *comment.. :) [10:30] this is the point where i am stucked.. :( [10:30] do you know in which part of the HTML you need to add the id? [10:31] yes.. please wait for 1 minute.. let me tell you the exact line [10:33] Ronnie: after line 17 "{{comment.commenter_profile.realname}}:" [10:33] we cann add the required anchor tag with "view" label [10:33] *can [10:33] and there we add this unique id while defining the name [10:34] the view-label should be after line 18 i think [10:34] the unique name can be defined in line 16 [10:35] yes.. we can define "view" after 18 also [10:35] ok, lets do that, [10:36] we need to add another TD [10:36] yoo [10:36] :) [10:36] yes [10:36] in that td we need an [10:37] yes [10:37] with a href to .... [10:38] i need to look the syntax. :p. i forgot it... :) let me see on W3C.. [10:38] :) [10:39] got it [10:39] :) [10:39] * Ronnie loves w3schools [10:39] lets first add the href to comment for its unique naming [10:39] :) [10:39] me too.. [10:39] :) [10:42] Ronnie: added name only yet :D ... new line 17 is " Ronnie: i worte "name=" [10:43] <== line 16 [10:43] sry [10:43] *"name="#comment....." " [10:43] now what to add to these dots to make it unique? [10:44] is perfectly valid in XHTML 1.0 Strict. id may normally be preferred, but name is not deprecated until HTML5. – bobince Jan 31 '10 at 10:50 [10:44] ^ quote from http://stackoverflow.com/questions/2171237/how-to-create-named-anchors-in-django-for-getting-down-to-specific-parts-of-the-p [10:45] i think we better use id instead of name [10:45] yes.. so where can i find the syntax? w3schools? [10:46] good question, but somehow name= does not work here, so i want looking for a solution [10:47] Ronnie: we can use id as .. :D [10:47] let me aslo check [10:49] we can do both, id= and name= [10:49] let me aslo check"http://www.w3.org/TR/html401/struct/links.html#h-12.2.3" [10:49] it may help us [10:49] sry [10:49] please check http://www.w3.org/TR/html401/struct/links.html#h-12.2.3" [10:50] http://www.w3.org/TR/html401/struct/links.html#h-12.2.3 [10:50] ok.. if we can do then its fine [10:50] :) [10:52] When both attributes are used on a single element, their values must be identical. [10:53] so were safe [10:53] i think IE6 wont support id= but others will [10:53] yes.. [10:53] o/ [10:53] :) [10:54] Ronnie: we really need to think a lot before taking every step.. :P [10:54] so we can go with name attribute also [10:54] :) [10:54] we do, but thats good [10:54] so how does your line 16 looks like? [10:55] we are editing line 17 [10:55] i think so [10:55] and it is after editing " now what to add to "#comment" to make it unique in every run of the loop? [10:57] :) [10:57] ok [10:57] line 15: {% for comment in comment_date.list %} [10:57] ok.. so we can use this date? :P [10:58] this means we can use the variable "comment" now [10:58] u can use variables {{ var_nane }} [10:58] then it wil become "name="#comment{{comment}}"" [10:58] ? [10:59] almost [10:59] with {{ comment }} [10:59] we get the whole comment object [10:59] we only needs it "id" [10:59] yes [10:59] any suggestions? [11:00] we can move to database primary ker or so?? [11:00] :P [11:00] *key [11:00] we need the pk (primary key) or id (identifier - which is the same as pk) [11:00] of the comment object [11:01] like for the "comment" object we can access the database like comment.id [11:01] yes [11:01] the same [11:01] can it be possible? [11:01] its that easy just use {{ comment.id }} [11:02] ok.. then its the solution.. :) [11:03] Ronnie: but i have doubt.. how "comment" is an object to access the database? [11:03] we have declared it [11:03] :P [11:03] we have declared it in the models.py and views.py [11:03] okiez.. :) [11:04] you not need to worry about that when doing templates [11:04] :) [11:04] Ronnie: so now line 17 is done [11:05] now its time for line 19 [11:05] (means added it pressing enter) [11:05] :) [11:05] :D [11:07] Ronnie: new line 19 is "View" [11:07] [11:07] ye. basically i wrote in line 20.. :D [11:07] oh [11:08] you can give the TD a class to have the same styling: "form-item-value" [11:09] in line 19? [11:09] yes [11:09] ok. [11:09] :) [11:10] can u please check the new file once.. if it is working correctly or not? [11:10] sure [11:10] paste.ubuntu.com ? [11:10] Ronnie: thanks.. :) [11:11] ok.. let me paste it and send the URL [11:11] oh, i got to eat in a minute [11:11] this is what i got: http://paste.ubuntu.com/583279/ [11:12] :) [11:12] http://paste.ubuntu.com/583283/ <== diff [11:13] its mine "http://pastebin.com/2BRxU9Ta" [11:13] i done many mistakes... :p [11:14] not that much ;) [11:14] its pretty good [11:14] some minor differences [11:15] i did put the name and id in the TR instead of th, because its easier to see in the short line [11:15] Ronnie: yes.. :) [11:16] so it will work now.. [11:16] you need to add the id= too on your part [11:17] yes.. thats the error i found.. i thought only name will work.. :p [11:17] the extra spaces before the View can be better with CSS styping [11:17] and the View text need to be translateble [11:17] therefore we use {% trans "translatable text" %} [11:18] sorry but what this translatable means? [11:18] :P [11:18] so other loco's can translate "View" into their own language [11:19] okiez. language translation [11:19] so its done [11:19] :) [11:20] i have to eat now [11:21] sure.. enjoy the food..i am also goin to have lunch [11:21] :) === daker_ is now known as daker [12:10] Ronnie: are you back?.. :) [12:11] bakc, but nedd to do other thing, am sorry [12:11] see you later [12:12] its ok.. see you.. [14:46] that Global Jam map sure is looking nice [14:48] need to get some more in USA though [14:54] where can i find the code of CSS for the grey strip of global events under "upcoming events in " "http://loco.ubuntu.com/" [14:54] ? [14:58] hey aakshay, im back (for a couple of minutes) [14:58] i advisse you to install firebug addon for firefox [14:58] thanks Ronnie :).. [14:58] this will help in? [14:59] there you can easily see what style is applied on what element, en where the stylesheet comes from [14:59] ok... thanks.. :) [14:59] one more thing, do i need to add any Css to the work we did? [15:00] you need to add a margin to the left of the link [15:00] margin-left: 8px should do just fine [15:00] link means "view" [15:00] ? [15:00] yes [15:00] ok.. i will do it.. thanks.. :) [15:01] maybe we need to change "view" to {{ comment.id }} too? [15:01] ya i will do like "#{{comment.id}}" eg. #64 [15:01] yes, same like LP [15:02] yes.. but in that the counting will not start by "1".. it will start by some value from database [15:02] if it is fine then i will make it [15:02] aakshay: rigth about that [15:02] but its a bit harder to do i guess [15:02] yes [15:02] altough.... [15:02] not really [15:02] ok [15:03] you can use {{ forloop.counter }} [15:03] okiez.. in plave of "view"? [15:03] yes [15:03] *place [15:03] ok [15:03] i will do this also [15:03] :) [15:05] you can even use the forloop.counter as the href=, id= and name= [15:07] ok.. this will serve the purpose.. :) [15:08] im thinking how we could do an non-javascript highlight [15:08] but nothing comes to mind [15:09] highlight? can you please elaborate little.. may be i can tell something [15:10] Ronnie: you can do CSS highlight [15:10] give the comment which is 'selected' by the # and other background color or something, so its clear which comment is 'selected' [15:14] if you can get the number or id of selected comment [15:15] i can only think of an javascript method [15:15] but are there ppl who's not using javascript? [15:16] Ronnie, then we can add [15:16] this is CSS [15:16] may help somehow.. :P [15:16] yes, but how to get the number? [15:17] i think ppl who dont use javascript should look at the number [15:17] yes they will [15:18] i am getting something very long way of getting number [15:19] Ronnie, you can use name attribute in anchor tag and then somehow append the name to the URL and extract from there [15:19] this will not use javaScript but may serve the purpose [15:19] :) [15:20] how to extract from the url? [15:21] if the number can be appended to URL then append it like after "?" and extract it from URL by separating the previous string [15:21] before and with "?" [15:22] have to go [15:23] ok.. :D [15:23] bye.. [15:51] aakshay: back [15:51] any ideas came up? [15:51] Ronnie, no :( [15:52] then well do javascript [15:52] but what about the idea i told u? [15:52] ya.. that would be better n easier.. [15:53] have you written javascript? [15:53] no.. :( [15:53] sorry [15:54] we need to use location.hash to get the number [15:55] ok.. then you can use if(location.hash...) then style="background-color:grey [15:56] $('[name=' + location.hash.slice(1) + ']').attr('background-color', '#f7f7f7'); [15:56] or something [15:57] or even easyier $(location.hash).attr.... [15:57] ya $(locatio.hash).attr.. [15:58] i suggest you to go with if() [16:05] aakshay: try to add this http://paste.ubuntu.com/583360/ into team_event_detail.html [16:05] after: {% block title %}{% trans team_event_object.name %} | {% trans "Ubuntu LoCo Team Directory" %} {% endblock %} [16:05] without console.log() [16:05] ok [16:08] done [16:09] does it work? [16:10] sorry but what to choose means what to select? :P [16:11] aakshay: speak to you later [16:11] Ronnie, ok.. let me see this meanwhile [16:11] i even improved it a bit: http://paste.ubuntu.com/583363/ [16:12] and http://paste.ubuntu.com/583365/ [16:12] good luck with it [16:13] :D.. thanx.... [16:44] YoBoY: pong [16:44] err ping [16:44] YoBoY: *ping [16:44] pong :) [16:44] YoBoY: I'm guessing you guys have done several awesome global jams? [16:45] YoBoY: I was wondering if you want to help with a classroom event (a small one) about global jams and how to make it rocking [16:46] when ? [16:46] how does 28th March sound to you? [16:47] Since the event itself is in planning stages, I can move it around a bit [16:47] we'll have about 3 to 4 sessions [16:47] one about the general planning (which I'm hoping youd do) [16:47] monday ? it's good :) [16:47] awesome, what time is good for you? [16:47] does 1600 UTC sound okay? [16:48] need to convert that ... wait :) [16:48] YoBoY: = 17:00 GMT+1 [16:49] yes ^^" [16:49] aakshay: im back [16:49] YoBoY: awesome, I'll put you down for a session, thanks! [16:49] nigelb: a bit later if it's possible [16:49] YoBoY: how much later? [16:49] (my yes is for Ronnie :p) [16:49] ah [16:49] 1800 UTC ? [16:50] sure :) [16:50] you're the first recruit, you get to pick :D [16:50] Ronnie, hey [16:50] ^^ [16:50] i dint find anything good out of it [16:50] aakshay: didn't it work? [16:50] if i selest any comment there is no change in color [16:50] no [16:50] :( [16:51] have you checked it once [16:51] ? [16:51] nigelb: in #ubuntu-classroom ? [16:51] YoBoY: yup :) [16:52] Ronnie, WORKED!!!! [16:53] aakshay: it did worj here [16:53] its changing the color [16:53] yes [16:53] nigelb: subject ? [16:54] YoBoY: "General tips to having a rocking Jam" :) [16:54] ok :) [16:54] Ronnie: but its just highlighting the first selection only [16:54] :P [16:54] aakshay: did you use the new code, here it works [16:55] ping me when you have the other topics before, to adapt my presentation :) [16:55] yes i used the new one [16:56] no problem it worked there.. then fine... :) [16:56] aakshay: can i look into your code? [16:56] sure [16:56] 1 min [16:57] its here http://paste.ubuntu.com/583390/ [16:58] Ronnie: btw it's monday 28 it's UTC +2 we change to the summer hour sunday 27 ;) (it's why I needed to look this) [16:58] YoBoY: ah, forget. Yay summertime :D [16:59] * Ronnie likes summertime [17:01] aakshay: line 39-47 should be in team_event_details_comment.inc.html [17:02] Ronnie: err.. that is what i was thinking.. :p [17:05] Ronnie: where to add in team_event_details_comment.inc.html? [17:06] most of it should be there alraedy [17:09] Ronnie: yo.. worked... :) [17:09] o/ [17:09] :) [17:09] Ronnie: which bug is it? [17:10] bug 616383 [17:10] Launchpad bug 616383 in loco-directory "Needs ability to directly link to a comment (affects: 1) (heat: 5)" [Wishlist,Triaged] https://launchpad.net/bugs/616383 [17:10] ok.. its the same :D [17:11] so do i need to merge the changes we made in morning? [17:11] you need to: [17:11] bzr commit -m "message of the changes" [17:12] bzr push lp:~yourusername/loco-directory/fixes-616383 [17:12] ok... i will do it later because i have not completed it yet.. :P [17:12] and then on launchapd page you can create the merge request [17:12] ok.. then [17:12] other developers will look at it and provide feedack of approve the code [17:13] ok and what about the coding u have done? [17:13] Ronnie: as it is also the same bug [17:13] its totally yours ;) [17:13] same bug [17:13] i was just helping you [17:14] oh.... :)... its totally ours... :) [17:14] o/ === dholbach_ is now known as dholbach [17:14] Ronnie: than which one should i commit? one we did in morning or this one? [17:15] i think the latter one is the best [17:15] yes.. :) thanks for the help.. :) [17:15] but you need the lines between to put in the newstyle.css [17:16] your welcome [17:16] :) [17:16] were happy to see new loco directory developers [17:16] Ronnie: in which file ? [17:16] /media/css/newstyle.css [17:26] +1 Ronnie [17:37] daker: there is already a bug report for it: https://bugs.launchpad.net/loco-directory/+bug/712440 [17:37] Launchpad bug 712440 in loco-directory "twitter, picasaweb, flickr, pixie should be a separate .js file (affects: 1) (heat: 4)" [Low,Confirmed] [17:37] ah ok thanks Ronnie [17:38] ill assinged it to you [17:38] have you any experience in writing jquery plugins? [17:38] will try :) [17:39] you can have a look at the twitter script, and twidenash script. [17:39] yes ok [17:39] and im available for help too [17:39] i think twitter is done ? [17:39] twitter is done [17:40] and jslint is my friend too [17:40] WARNING: JSLint will hurt your feelings. [17:40] http://www.jslint.com/ [17:40] hehe [17:41] when i think my code works good, jslint can find 20-50 errors in it ;) [17:42] daker flickr does have a script too i guess [17:42] you mean a jquery plugin ? [17:43] yes [17:43] ok [17:47] Ronnie: i have committed the change and pushed it. now what will the address to aceess the merge on launchpad? [17:48] aakshay: this page is created: [17:49] https://code.launchpad.net/~akshaytayal/loco-directory/fixes-616383 there is a link " craete merge propsal" [17:49] uhm, "propose for merging" [17:49] you can also link it to the bug report [17:50] ok.. how to link to bug report? [18:03] itnet7: ping [18:05] aakshay: with the link "link to bugreport" [18:10] done.. :).. thanks a lot... :) [18:32] good night.. [18:51] thank you aakshay [18:51] gone, I know... [18:51] Ronnie: you rock for walking him through the process [18:52] thx mhall119, i did it eith pleasure [19:12] nigelb: pong [19:15] itnet7: hey, I was looking for someone to take a session about ornaizing ugj. Youup for it [19:15] bah, spelling :( [19:15] nigelb: When would this be? [19:16] inmonday 28th at either 1700 or 1900 utc [19:16] *on monday [19:18] nigelb: Let me see if I can get off of work early on Monday, and if I can I will [19:18] nigelb: pm? [19:18] itnet7: sure :) [19:21] 5/45 [19:21] uggh [19:21] cjohnston: 42 [19:22] hush [19:22] mhall119: any progress on the django openid auth bug? [19:46] cjohnston, mhall119: quick one line code review https://code.launchpad.net/~nigelbabu/summit/fix-735633/+merge/54258 [19:48] Daviey: you too ^^ [19:54] nigelb, I think it is safe, but are you sure it doesn't modify the db? [19:55] Daviey: yes, it only makes the form validation change. [19:56] oh wait, what's that coding uft8 thing [19:56] * nigelb removes [19:58] Only a few more days left for the applications to close, but you might want to get it live nevertheless [20:00] I guess I should just subscribe to summit bugs [20:00] Ronnie: I finished my test cases and enhancements over the weekend, waiting for new reviews [20:00] mhall119: do you have to link to the merge> [20:01] https://code.launchpad.net/~mhall119/django-openid-auth/fixes-642132/+merge/54193 is for renamed users [20:02] https://code.launchpad.net/~mhall119/django-openid-auth/strict-username-requirements/+merge/54065 is for enforcing that we get a launchpad username [20:02] ill have a look tomorrow i guess [20:06] Ronnie: thanks, I'll try and get one of the maintainers to look over it too