[08:38] Hello there I am trying to configure Single SignOn options with one of my sites for members to log in. I was wondering where I could get information about the following http://paste.ubuntu.com/877191/ [08:38] thanks for you tme / [08:39] please disregard line 17 to the end sorry [14:42] cjohnston: is it supposed to use 960.gs or the canonical grid? [14:53] Amoz: 960 is for the wide viewed schedule [14:54] it has a specific use and I don't think it needs to be messed with [14:59] cjohnston: okay [14:59] now I've imported the css files like this instead [15:00] core-reset, core-grid,core,default,django_extras [15:00] then I'll change selectors in grid, and if something needs manual editing, that will take place in default.css [15:02] if that's okay with out [15:02] ok [15:02] you* [15:02] we can try it.. [15:02] hopefully we can use a lot from the canonical base and remove stuff from default.css [15:18] cjohnston: the 960 is overriding styles from core.css :( [15:19] I need to move the css imports after the 960 import in that case [15:19] Amoz: whick ones? 960 is supposed to make the header the full width of the page on certain pages [15:20] cjohnston: header#page-header [15:20] I'm on my cell phone right now so I dont have the files to look at [15:20] oh [15:20] on all pages Amoz or just certain ones [15:21] well "all" there is in the summit menu [15:22] hrm.. its only supposed to do it on a couple pages [15:29] cjohnston: as it is now, the 960 is included after everything else, and the header#page-header is the selector in the 960 and the summit html [15:30] cjohnston: what other sites are using the django-theme? [15:35] ltp, jono's thing and I don't know what else [15:35] mhall119: nigelb i deas? [15:39] any ideas [16:23] Amoz: if you want to push it, I'm on the computer now, I can take a look === bobweaver is now known as josephmills [17:35] cjohnston: https://code.launchpad.net/~fougner/+junk/light-django-theme-new-design [19:05] Amoz_: it look correct to me [19:05] Amoz_: the issue that I see is the link in the main nav look wrong [19:06] Amoz_: although that could be because the html changes werent applied to summit/common/base.html [19:07] Amoz_: and it looks like in your website_base.html the

Amoz_: I modified the base.html and its still a little off... but better [19:13] Amoz_: for some reason, there isnt the padding on the right side of the header links [19:43] could I try to help with the css ? [19:59] josephmills: speak to Amoz_ and see what he may need [20:00] we are trying to update summit to the new guidelines [21:33] josephmills: ping [21:44] pong sorry cjohnston I missed the ping but I have to go to a clients server right now will be back in like 2 or 3 hrs take care [22:05] cjohnston: the ul is closed here [22:07] oh, you wrote subnav.. nvm [22:07] :-) [22:07] cjohnston: but that's closed as well it seems [22:08] Amoz_: it doesnt look like it on the LP view [22:08] LP? [22:08] you mean in the code? [22:08] 85

base.html extends website_base.html so website_base.html will be the default template for all of our django sites [22:18] sounds like stuff spanning multiple sites [22:18] standard stuff [22:18] and base.html customizes the website_base.html for the specific site [22:19] common is just where the stuff goes that isnt sponsorship related and isnt schedule related [22:19] i.e. base.html is both and index.html is neither [22:19] sponsorship... schedule..? [22:20] Amoz_: summit is a scheduling webapp that runs the schedule for Ubuntu Developer Summit and Linaro Connect (and more coming soon) [22:20] For UDS the ability exists to get sponsored to the event [22:21] teh sponsor app is where you apply for sponsorship, and then the applications are reviewed and voted upon [22:21] the schedule app is where everything related to the schedule lives [22:21] so each summit, each meeting, each attendee, etc [22:22] schedule for UDS [22:22] a calendar thingy [22:22] UDS, Linaro Connect, whatever the event is, yes [22:22] sort of [22:22] y [22:22] ya [22:22] i c [22:22] sponsorship, what is that? [22:22] Amoz_: http://summit.ubuntu.com/uds-p/2011-10-31/ <-- that days schedule in an agenda view [22:23] just tell me to google if questions are answered on the interwebz [22:23] http://summit.ubuntu.com/uds-p/2011-10-31/display <--- the same days schedule in a grid view (used for display monitors located around the event) [22:24] holy cow [22:24] Amoz_: UDS allows for non-employees to attend at Canonicals expense.. or sponsored.... uds.ubuntu.com [22:24] i see rainbows [22:24] yup [22:24] I see [22:24] each different color represents a track [22:24] track is kinda like a topic [22:24] have you been there? at the UDS? [22:24] yes... 4 [22:24] Two of them were here in Orlando [22:25] I will be attending the next one in May also [22:25] Amoz_: here is the schedule for one of the days at the last Linaro Connect event: http://summit.linaro.org/lcq1-12/2012-02-06/ [22:25] cool [22:28] So far, we have 5 events scheduled this year for Summit.. Linaro Connect last month, UDS the beginning of May, Linaro Connect the end of May, Linux Plumbers in August, and a co-hosted UDS and Connect in November [22:28] some stuff to do then [22:29] Ya.. [22:29] theres quite a bit of work to do. [22:31] Amoz_: you can see an overview of what we did between mid-november and mid january: http://chrisjohnston.org/ubuntu/big-changes-to-summit [22:31] 2400 lines of code [22:32] oh my [22:32] Think of maintaining two different themes that work with one code base.. thats enough of a headache [22:33] Amoz_: https://blueprints.launchpad.net/summit/+spec/linaro-q212-requirements is what we hope to accomplish by mid April [22:33] well that's cool [22:33] which is why any help is awesome [22:34] hopefully I can do some [22:34] :-) [22:34] theres that list, one other blueprint and a whole bunch of bugs.. [22:34] heh [22:36] fortunately, web stuff is quite straightforward compared to the advanced architecture stuff the kernel hackers do for example.. [22:36] my god I feel lost when I look at all decisions they make [22:37] agreed [22:37] let me pull the theme back up and see if I find issues and I'll let you know what I see [22:37] yeah my branch wasn't really supposed to be "finished" [22:38] I barely begun coding [22:38] but if you think it looks good that's great [22:38] what else do you need to do with it? [22:38] if you have more, by all means [22:38] gee, I don't know ^^ [22:38] it needs to follow the guidelines as close as possible [22:39] lol [22:39] it just felt... to shabby [22:39] I threw it all in there and expected to do some coding [22:39] lol [22:39] and now you're saying everything looks good [22:39] you disappoint me son [22:39] well.. if you have other changes to make, go for it.. I'll work on the changes to lp:summit to make it all look right [22:39] I saw atleast one issue [22:39] but I just glanced [22:40] look again and you will find a dozen more [22:40] ok [22:40] :P [22:40] but yeah [22:40] we could try merging it, and see what we get [22:40] then we'll take it from there [22:40] if it's good enough for merging, that is [22:41] it's midnight here by now [22:41] I have a few things that once I get it fired up I'll show you screenshots of [22:41] sure [22:41] just mail me or put U1 links here [22:41] you dont use dropbox? [22:41] i use u1 and dropbox [22:42] nice [22:46] cjohnston: so have you tried precise yet? [22:47] I've been running it since before a2 [22:48] wat? [22:48] like primary? [22:49] yup [22:49] all three machines [22:57] Amoz_: http://ubuntuone.com/3J7pjP8d94o7z1h9noMJD3 [22:58] yep, I've got the same one here, basically [22:58] which browser are you on? [22:59] chromium [22:59] for some reason the sub-nav stuff isnt showing up where it should [22:59] its not showing up at all [23:00] okay [23:00] is there a way for me to see the subnav somewhere? [23:01] the code or in the browser [23:01] both [23:02] I mean the html/css [23:02] i think i figured out why [23:02] so, mostly browser I guess [23:02] summit/schedule/templates/schedule/summit.html [23:02] http://127.0.0.1:8000/uds-q/ [23:02] cant see that one [23:03] -q doesnt exist for me [23:03] -p does though [23:03] that works [23:03] the sub-nav stuff it outside of the header [23:03] so thats part of it [23:03] but it doesnt seem to be fixing it [23:04] Amoz_: would it be #sub-nav li { [23:04] ? [23:05] or .sub-nav li { [23:05] I'm kind of shutting down for tonight, but the subnav was something I didn't check [23:05] hold on [23:05] dont worry about it [23:05] see ya later.. i gotta go anyway.. at work [23:09] how can you stay on IRC when you're on work? :P [23:13] cjohnston, hmm, I think the

elements are missing in the subnav [23:13] at least they are for me [23:13] that would explain a lot [23:14] anyway, I changed all the .nav-secondary to #sub-nav in core.css [23:14] that should remap the subnav styles to the correct elements [23:14] anyway, gotta go, cya!