[08:38] <bobweaver> 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] <bobweaver> thanks for you tme /
[08:39] <bobweaver> please disregard line 17 to the end sorry
[14:42] <Amoz> cjohnston: is it supposed to use 960.gs or the canonical grid?
[14:53] <cjohnston> Amoz: 960 is for the wide viewed schedule
[14:54] <cjohnston> it has a specific use and I don't think it needs to be messed with
[14:59] <Amoz> cjohnston: okay
[14:59] <Amoz> now I've imported the css files like this instead
[15:00] <Amoz> core-reset, core-grid,core,default,django_extras
[15:00] <Amoz> then I'll change selectors in grid, and if something needs manual editing, that will take place in default.css
[15:02] <Amoz> if that's okay with out
[15:02] <cjohnston> ok
[15:02] <Amoz> you*
[15:02] <cjohnston> we can try it..
[15:02] <Amoz> hopefully we can use a lot from the canonical base and remove stuff from default.css
[15:18] <Amoz> cjohnston: the 960 is overriding styles from core.css :(
[15:19] <Amoz> I need to move the css imports after the 960 import in that case
[15:19] <cjohnston> Amoz: whick ones? 960 is supposed to make the header the full width of the page on certain pages
[15:20] <Amoz> cjohnston: header#page-header
[15:20] <cjohnston> I'm on my cell phone right now so I dont have the files to look at
[15:20] <Amoz> oh
[15:20] <cjohnston> on all pages Amoz or just certain ones
[15:21] <Amoz> well "all" there is in the summit menu
[15:22] <cjohnston> hrm.. its only supposed to do it on a couple pages
[15:29] <Amoz> 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] <Amoz> cjohnston: what other sites are using the django-theme?
[15:35] <cjohnston> ltp, jono's thing and I don't know what else
[15:35] <cjohnston> mhall119:  nigelb i deas?
[15:39] <cjohnston> any ideas
[16:23] <cjohnston> Amoz: if you want to push it, I'm on the computer now, I can take a look
[17:35] <Amoz> cjohnston: https://code.launchpad.net/~fougner/+junk/light-django-theme-new-design
[19:05] <cjohnston> Amoz_: it look correct to me
[19:05] <cjohnston> Amoz_: the issue that I see is the link in the main nav look wrong
[19:06] <cjohnston> Amoz_: although that could be because the html changes werent applied to summit/common/base.html
[19:07] <cjohnston> Amoz_: and it looks like in your website_base.html the <ul> for the subnav is never closed
[19:12] <cjohnston> Amoz_: I modified the base.html and its still a little off... but better
[19:13] <cjohnston> Amoz_: for some reason, there isnt the padding on the right side of the header links
[19:43] <josephmills> could I try to help with the css ?
[19:59] <cjohnston> josephmills: speak to Amoz_ and see what he may need
[20:00] <cjohnston> we are trying to update summit to the new guidelines
[21:33] <cjohnston> josephmills: ping
[21:44] <bobweaver> 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] <Amoz_> cjohnston: the ul is closed here
[22:07] <Amoz_> oh, you wrote subnav.. nvm
[22:07] <cjohnston> :-)
[22:07] <Amoz_> cjohnston: but that's closed as well it seems
[22:08] <cjohnston> Amoz_: it doesnt look like it on the LP view
[22:08] <Amoz_> LP?
[22:08] <Amoz_> you mean in the code?
[22:08] <cjohnston> 85                <ul class="clearfix"> 86                           {% block sub_nav_links %} 87                        <li class="active"><a class="sub-nav-item" href="javascript:void(0)" title="Indice">Indice</a></li> 88                        <li><a class="sub-nav-item" href="javascript:void(0)" title="FAQ">FAQ</a></li>
[22:08] <cjohnston>  89                       <li><a class="sub-nav-item" href="javascript:void(0i)" title="Regolamento">Regolamento</a></li> 90                        <li><a class="sub-nav-item" href="javascript:void(0)" title="Ricerca">Ricerca</a></li> 91                        <li><a class="sub-nav-item" href="javascript:void(0)" title="Accedi">Accedi</a></li> 92                        <li><a class="sub-nav-item" href="javascript:
[22:08] <cjohnston> 9493                {% endblock %}
[22:09] <cjohnston> Amoz_: how much is left to be done? It's looking pretty awesome
[22:10] <Amoz_> cjohnston: basically, I just took the new canonical css files and imported them
[22:10] <cjohnston> right
[22:10] <Amoz_> changed the main-nav selectors in the css
[22:10] <Amoz_> then replaced all img paths with 'images'
[22:11] <Amoz_> that's about it
[22:11] <Amoz_> I'm still under the impression that I have no clue what I'm working on
[22:11] <Amoz_> I mean, what goes where
[22:11] <cjohnston> wi see that they used inner-wrapper, what does that do?
[22:12] <Amoz_> the common-dir vs. the ubuntu_website dir
[22:12] <Amoz_> there are templates in both
[22:12] <cjohnston> right...
[22:12] <Amoz_> the what?
[22:12] <Amoz_> inner-wrapper?
[22:12] <cjohnston> core-grid.css
[22:12] <cjohnston> let me see if I can find a high level overview of templates
[22:13] <cjohnston> heres the django doc on templates https://docs.djangoproject.com/en/dev/topics/templates/
[22:14] <Amoz_> cjohnston: I'm not sure it's used
[22:14] <cjohnston> basically, website_base.html is the highest level template
[22:14] <cjohnston> it is on their index.html file, but i dont know what it does and if we need it
[22:15] <cjohnston> website_base.html contains blocks.. main-nav block, sub-nav block, content block, etc
[22:15] <cjohnston> those blocks then become editable on other pages.. for example.. website_base.html contains dummy main nav links...
[22:16] <Amoz_> yeah I'm with you so far
[22:17] <Amoz_> I know the templating stuff for DJango
[22:17] <Amoz_> but in this specific case
[22:17] <Amoz_> I'm a little confused about the different directories with templates etc.
[22:17] <Amoz_> but nvm
[22:17] <Amoz_> you can use my branch as a base if it looks good
[22:18] <cjohnston> its for the different apps
[22:18] <Amoz_> and the "common" dir?
[22:18] <cjohnston> base.html extends website_base.html  so website_base.html will be the default template for all of our django sites
[22:18] <Amoz_> sounds like stuff spanning multiple sites
[22:18] <Amoz_> standard stuff
[22:18] <cjohnston> and base.html customizes the website_base.html for the specific site
[22:19] <cjohnston> common is just where the stuff goes that isnt sponsorship related and isnt schedule related
[22:19] <cjohnston> i.e. base.html is both and index.html is neither
[22:19] <Amoz_> sponsorship... schedule..?
[22:20] <cjohnston> Amoz_: summit is a scheduling webapp that runs the schedule for Ubuntu Developer Summit and Linaro Connect (and more coming soon)
[22:20] <cjohnston> For UDS the ability exists to get sponsored to the event
[22:21] <cjohnston> teh sponsor app is where you apply for sponsorship, and then the applications are reviewed and voted upon
[22:21] <cjohnston> the schedule app is where everything related to the schedule lives
[22:21] <cjohnston> so each summit, each meeting, each attendee, etc
[22:22] <Amoz_> schedule for UDS
[22:22] <Amoz_> a calendar thingy
[22:22] <cjohnston> UDS, Linaro Connect, whatever the event is, yes
[22:22] <Amoz_> sort of
[22:22] <cjohnston> y
[22:22] <cjohnston> ya
[22:22] <Amoz_> i c
[22:22] <Amoz_> sponsorship, what is that?
[22:22] <cjohnston> Amoz_: http://summit.ubuntu.com/uds-p/2011-10-31/   <-- that days schedule in an agenda view
[22:23] <Amoz_> just tell me to google if questions are answered on the interwebz
[22:23] <cjohnston> 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] <Amoz_> holy cow
[22:24] <cjohnston> Amoz_: UDS allows for non-employees to attend at Canonicals expense.. or sponsored....  uds.ubuntu.com
[22:24] <Amoz_> i see rainbows
[22:24] <cjohnston> yup
[22:24] <Amoz_> I see
[22:24] <cjohnston> each different color represents a track
[22:24] <cjohnston> track is kinda like a topic
[22:24] <Amoz_> have you been there? at the UDS?
[22:24] <cjohnston> yes... 4
[22:24] <cjohnston> Two of them were here in Orlando
[22:25] <cjohnston> I will be attending the next one in May also
[22:25] <cjohnston> 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] <Amoz_> cool
[22:28] <cjohnston> 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] <Amoz_> some stuff to do then
[22:29] <cjohnston> Ya..
[22:29] <cjohnston> theres quite a bit of work to do.
[22:31] <cjohnston> 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] <cjohnston> 2400 lines of code
[22:32] <Amoz_> oh my
[22:32] <cjohnston> Think of maintaining two different themes that work with one code base.. thats enough of a headache
[22:33] <cjohnston> Amoz_: https://blueprints.launchpad.net/summit/+spec/linaro-q212-requirements is what we hope to accomplish by mid April
[22:33] <Amoz_> well that's cool
[22:33] <cjohnston> which is why any help is awesome
[22:34] <Amoz_> hopefully I can do some
[22:34] <cjohnston> :-)
[22:34] <cjohnston> theres that list, one other blueprint and a whole bunch of bugs..
[22:34] <cjohnston> heh
[22:36] <Amoz_> fortunately, web stuff is quite straightforward compared to the advanced architecture stuff the kernel hackers do for example..
[22:36] <Amoz_> my god I feel lost when I look at all decisions they make
[22:37] <cjohnston> agreed
[22:37] <cjohnston> let me pull the theme back up and see if I find issues and I'll let you know what I see
[22:37] <Amoz_> yeah my branch wasn't really supposed to be "finished"
[22:38] <Amoz_> I barely begun coding
[22:38] <Amoz_> but if you think it looks good that's great
[22:38] <cjohnston> what else do you need to do with it?
[22:38] <cjohnston> if you have more, by all means
[22:38] <Amoz_> gee, I don't know ^^
[22:38] <cjohnston> it needs to follow the guidelines as close as possible
[22:39] <cjohnston> lol
[22:39] <Amoz_> it just felt... to shabby
[22:39] <Amoz_> I threw it all in there and expected to do some coding
[22:39] <cjohnston> lol
[22:39] <Amoz_> and now you're saying everything looks good
[22:39] <Amoz_> you disappoint me son
[22:39] <cjohnston> 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] <cjohnston> I saw atleast one issue
[22:39] <cjohnston> but I just glanced
[22:40] <Amoz_> look again and you will find a dozen more
[22:40] <cjohnston> ok
[22:40] <Amoz_> :P
[22:40] <Amoz_> but yeah
[22:40] <Amoz_> we could try merging it, and see what we get
[22:40] <Amoz_> then we'll take it from there
[22:40] <Amoz_> if it's good enough for merging, that is
[22:41] <Amoz_> it's midnight here by now
[22:41] <cjohnston> I have a few things that once I get it fired up I'll show you screenshots of
[22:41] <Amoz_> sure
[22:41] <Amoz_> just mail me or put U1 links here
[22:41] <Amoz_> you dont use dropbox?
[22:41] <cjohnston> i use u1 and dropbox
[22:42] <Amoz_> nice
[22:46] <Amoz_> cjohnston: so have you tried precise yet?
[22:47] <cjohnston> I've been running it since before a2
[22:48] <Amoz_> wat?
[22:48] <Amoz_> like primary?
[22:49] <cjohnston> yup
[22:49] <cjohnston> all three machines
[22:57] <cjohnston> Amoz_: http://ubuntuone.com/3J7pjP8d94o7z1h9noMJD3
[22:58] <Amoz_> yep, I've got the same one here, basically
[22:58] <Amoz_> which browser are you on?
[22:59] <cjohnston> chromium
[22:59] <cjohnston> for some reason the sub-nav stuff isnt showing up where it should
[22:59] <cjohnston> its not showing up at all
[23:00] <Amoz> okay
[23:00] <Amoz> is there a way for me to see the subnav somewhere?
[23:01] <cjohnston> the code or in the browser
[23:01] <Amoz> both
[23:02] <Amoz> I mean the html/css
[23:02] <cjohnston> i think i figured out why
[23:02] <Amoz> so, mostly browser I guess
[23:02] <cjohnston> summit/schedule/templates/schedule/summit.html
[23:02] <cjohnston> http://127.0.0.1:8000/uds-q/
[23:02] <Amoz> cant see that one
[23:03] <Amoz> -q doesnt exist for me
[23:03] <Amoz> -p does though
[23:03] <cjohnston> that works
[23:03] <cjohnston> the sub-nav stuff it outside of the header
[23:03] <cjohnston> so thats part of it
[23:03] <cjohnston> but it doesnt seem to be fixing it
[23:04] <cjohnston> Amoz_: would it be #sub-nav li {
[23:04] <cjohnston> ?
[23:05] <cjohnston> or .sub-nav li {
[23:05] <Amoz> I'm kind of shutting down for tonight, but the subnav was something I didn't check
[23:05] <Amoz> hold on
[23:05] <cjohnston> dont worry about it
[23:05] <cjohnston> see ya later.. i gotta go anyway.. at work
[23:09] <Amoz> how can you stay on IRC when you're on work? :P
[23:13] <Amoz> cjohnston, hmm, I think the <li> elements are missing in the subnav
[23:13] <Amoz> at least they are for me
[23:13] <Amoz> that would explain a lot
[23:14] <Amoz> anyway, I changed all the .nav-secondary to #sub-nav in core.css
[23:14] <Amoz> that should remap the subnav styles to the correct elements
[23:14] <Amoz> anyway, gotta go, cya!