[15:07] <aquarius> cjohnston, mhall119, I don't suppose you're around? :)
[15:08] <cjohnston> nope
[15:08]  * aquarius laughs
[15:08] <aquarius> got a few minutes?
[15:08] <cjohnston> sure
[15:09] <aquarius> firstly, your thoughts on https://code.launchpad.net/~sil/summit/more-mobile-summit/+merge/90608 invited
[15:09] <aquarius> more importantly, I'm thinking about how to do offline-capable summit
[15:09] <aquarius> and I'd like to kick the ideas around a bit
[15:10] <cjohnston> probably a better discussion with mhall119, but I'll talk.. nigelb you around?
[15:11] <nigelb> gimme 30 mins? I'm headed for dinner
[15:11] <aquarius> OK. My plan is this: the daily pages (and only those) will be cached. When you visit one of the daily pages, it's loaded from the cache and the top of the page says "Schedule saved 1h43m ago". If, and only if, you are online *and* the schedule has been updated since then, that will also say "Schedule has been updated: [load new schedule]"
[15:12] <cjohnston> that'd be cool
[15:13] <aquarius> the issue is: if you're online and you never go offline (you're using a laptop and you're sat at UDS itself during the day), it'll still work like this: that is, you'll have to explicitly hit that [load new schedule] button to get updates, *even if* you refresh the page with F5
[15:13] <aquarius> is that too annoying?
[15:13] <cjohnston> yes
[15:13] <cjohnston> to me atleast
[15:14] <cjohnston> would it be possible to do "if viewed from phone cache and display info, else act normal"
[15:14] <cjohnston> ?
[15:14] <nigelb> aquarius: before I go, can we use localstorage?
[15:14] <aquarius> nigelb, we can, if we want to build a separate explicit version of summit that renders everything client-side, and make an API for it to talk to to fetch data. That seems like a lot of work for not much benefit to me
[15:15] <aquarius> cjohnston, it is, as long as you can decide "is this a phone" on the *server*. Which is hard -- how will you do it?
[15:15] <nigelb> that makes sense.
[15:15] <cjohnston> I've never done anything with phones, so I have no idea
[15:16] <aquarius> you can deetect *specific* phones (say, an iPhone, or Android), but that'll exclude people with blackberrys and windows phone 7 and n9 and so on
[15:17] <cjohnston> gotcha
[15:17] <aquarius> and then people will say: this is typical Ubuntu only caring about apple and google and not my FreedomPhone which is quite capable of enjoying this offline magic but you excluded me anyway because you hate freedom
[15:17] <aquarius> and they will say that to you and you will get tired of it :)
[15:18] <cjohnston> lol
[15:32] <aquarius> cjohnston, next question. I'd like to have some sort of identifying string which is "the state of conference UDS-P right now", such that that string will change if anything at all changes about the conference -- a session is rescheduled, a session's title changes, a session is deleted, etc
[15:32] <aquarius> where would I get such a thing?
[15:33] <aquarius> I could obviously do: for session in all_sessions: longstring += session.title + session.time + session.description; identifying_string = md5(longstring)
[15:33] <aquarius> is there an easier way? :)
[15:36] <cjohnston> aquarius: I don't believe we have anything like that
[15:37] <cjohnston> and the schedule changes so frequently.. thats why the display monitors refresh every 5 minutes & we added that little "the page was last refreshed
[15:37] <cjohnston> "
[15:38] <aquarius> ya
[15:38] <cjohnston> people showed up to work on the house, so im only partially here
[15:48] <aquarius> no worries
[15:48] <aquarius> would be interested in nigelb's thoughts on the caching stuff, too
[15:49] <nigelb> aquarius: I like your idea. I had this md5 thoughts a few months back to refresh only if there was a change.
[15:50] <aquarius> nigelb, aren't you having lunch? :)
[15:50] <nigelb> Dinner.
[15:50] <nigelb> I just got back
[15:50] <aquarius> yeah, the md5 thing is one way to do it, right enough, but computing it is fairly expensive :(
[15:50] <aquarius> which we don't want to do every time anyone requests a page...
[15:50] <nigelb> well, we could store the hash into memcached.
[15:51] <nigelb> and remove the key when something changes.
[15:51] <nigelb> we already do something of this sort.
[15:51] <aquarius> oh?
[15:51] <nigelb> render.py had something of this sort. Listening for changes is already there.
[15:51] <aquarius> problem with that approach is that it requires poking everything that writes to the DB to remove the cache
[15:51] <nigelb> Well, poking everything that matters.
[15:52] <nigelb> I'd argue only the sessions need poking.
[15:52] <nigelb> if a new person signs up, we don't need to update.
[15:54] <aquarius> agreed
[15:54] <aquarius> well... it might be *you* :)
[15:55] <nigelb> Let me take a look tomorrow morning :)
[15:55] <aquarius> but poking the DB writing stuff is a big faff that I'd like to avoid ;)
[15:55] <nigelb> I haven't touched summit in a while due to lack of time. I'll try to make time for this.
[15:57] <aquarius> is there a DB revision somewhere?
[15:57] <aquarius> can't remember whether django maintains that :)
[15:58] <nigelb> well, you can do ./manage.py migrate to migrate all the changes we've made.
[15:58] <aquarius> ah, no, not that sort of revision. I mean, one number somewhere which django increments every time the DB changes :)
[15:59] <nigelb> Nope
[16:00] <nigelb> this is when data changes right?
[16:00] <aquarius> yeah
[16:00] <aquarius> I thought that was a bit hopeful :)
[16:01] <nigelb> heh
[16:05] <cjohnston> nigelb: fwiw, there is one bug that needs to be fixed prior to looking at the offline stuff please... it needs to be fixed in the next couple days
[16:05] <cjohnston> prior to connect
[16:05] <cjohnston> aquarius: are you on and android?
[16:05] <nigelb> I'm not touching anything critical and time-bound.
[16:06] <aquarius> I am
[16:06] <nigelb> I know I won't finish it.
[16:06] <aquarius> cjohnston, having someone with an iphone test my mobile branches would be a good idea ;)
[16:06] <cjohnston> i have access to one
[16:06] <cjohnston> aquarius: download this: https://market.android.com/details?id=org.linaro.connect&feature=search_result#?t=W251bGwsMSwyLDEsIm9yZy5saW5hcm8uY29ubmVjdCJd
[16:06] <cjohnston> im going to attempt to make one for ubuntu prior to uds
[16:07] <aquarius> ah, OK. My intention with the mobile patches is to make it so you don't *need* a native app :)
[16:07] <cjohnston> ya..
[16:07] <aquarius> and then we support all phones without having to make fifty different mobile apps ;)
[16:07] <cjohnston> i know.. but that's kinda cool too
[17:58] <cjohnston> aquarius: your branch is merged
[17:58] <cjohnston> http://91.189.93.80:8000/uds-p/
[17:59] <cjohnston> I'd think maybe remove the topnav (login, ubuntu.com, community, support, partners)
[18:40] <aquarius> hey, cjohnston, sorry was afk
[18:41] <aquarius> I kept those bits on the summary pages just in case someone needs them (although they are reformatted a bit on narrow screens)
[18:42] <cjohnston> ok
[18:42] <aquarius> easy to remove if you think so -- they're removed on the daily pages, because those ones are specificallymobile-optimised
[18:42] <cjohnston> I just think those links are way too small.. I could be wrong, but i dont see anyone clicking partners on their cell phon
[18:42] <cjohnston> e
[18:42] <cjohnston> I'm ok with the orange bar.. im talking the white bar above it
[18:43] <aquarius> the earlier pages aren't really designed for mobile -- all I've done is made them a bit more sensible on a mobile :0
[18:43] <aquarius> so they don't start off zoomed out, etc
[18:43] <cjohnston> right
[18:43] <aquarius> and I kept log in 'cos... people need to log in ;) I've reformatted that on the daily page (and turned off the rest of that white bar)
[18:44] <cjohnston> theres a login link lower, below the summit info
[18:44] <cjohnston> lets get feedback from nigelb and mhall119
[18:46] <aquarius> sure -- that's why I proposed a merge, so you guys can decide whether you like it or not ;)
[18:46] <cjohnston> :-)
[18:46] <cjohnston> I'm off for a bit.. if you need something just poke and ill help when i get back
[18:47] <aquarius> no worries. I have totally failed to do any hacking today anyway :)
[18:47] <cjohnston> lol
[18:48] <cjohnston> we need to figure out this schedule display issue... and i dont have time to think about it