[00:00]  * flan kinda liked having all the apt commands grouped under one utilitiy.
[00:00] <flan> -i
[00:36] <humphreybc> Hi everyone
[00:36] <Muscovy> Hello.
[00:36] <humphreybc> time to see if I can pull a fresh branch and test our installation instructions
[00:36] <humphreybc> because I have totally forgotten how to use bzr :P
[00:37] <Muscovy> It took me a while to discover a few vital features.
[00:37] <Muscovy> Like bzr add. :P
[00:37] <humphreybc> godbyk: are you there? how can I check if I have the correct version of latex installed?
[00:39] <Muscovy> I think the pkgs/install-pkgs.sh does that.
[00:39] <humphreybc> in the branch?
[00:39] <humphreybc> okay
[00:39] <humphreybc> and we're still working in lp:ubuntu-manual?
[00:39] <humphreybc> not lp:ubuntu-manual/maverick or something?
[00:40] <Muscovy> Maverick branch is lp:ubuntu-manual.
[00:40] <humphreybc>  great
[00:40] <humphreybc> so it is :D
[00:40] <humphreybc> I've got my coffee and last night's pizza ready to be re-heated for lunch
[00:41] <humphreybc> some nice music playing, all ready to start working through these 172 pages of text :D
[00:43] <humphreybc> hey banshee gapless playback is working all of a sudden
[00:49] <humphreybc> mint!
[00:49] <humphreybc> took like 10 seconds to branch
[00:49] <humphreybc> everything installed except one thing which the script installed :D
[00:49] <humphreybc> this is better than I remember :D
[00:49] <Muscovy> Just in case you didn't know, manual doesn't compile currently.
[00:49] <Muscovy> So if you try, it's probably not your edit.
[00:50] <humphreybc> okay
[00:50] <humphreybc> cool
[00:50] <humphreybc> thanks :)
[00:51] <godbyk> humphreybc: yeah, I'm here.
[00:51] <humphreybc> sweet
[00:52] <humphreybc> i've got the latest branch
[00:52] <humphreybc> going to burn through these open bugs firstr
[00:52] <godbyk> run "xelatex --version".  It should say "XeTeX 3.1415926-2.2-0.9995.2 (TeX Live 2009)".
[00:52] <humphreybc> then I'll start making edits for maverick
[00:52] <humphreybc> yup, all good
[00:53] <Muscovy> Does Maverick have the right version of Tex, anyone know?
[00:54] <godbyk> Muscovy: I'm not sure if it does or not.
[00:54] <flan> I'm installing it now.
[00:55] <humphreybc> THANK GOD Launchpad has fixed a heap of things so overlays come up when changing bug details instead of loading new pages!!
[00:57] <godbyk> looks like the PPA glossary entry hasn't been defined.
[00:57] <godbyk> Someone misspelled \marginnote.
[00:58] <flan> xelatex --version looks correct, numerically.
[00:58] <flan> The string devates a little, though, saying TeX Live 2009/Debian.
[00:59] <humphreybc> godbyk: could you do us a favour and fix the compile errors so it will compile for me to test?
[00:59] <godbyk> I'm working on it.
[01:00] <humphreybc> okay
[01:00] <humphreybc> i'm going to push my changes
[01:00] <humphreybc> let me try and remember how :P
[01:00] <godbyk> flan: I think that the Lucid packages were missing some required TeX Live packages. I don't know if they're in the Maverick packages now or not.
[01:00] <humphreybc> walk me through so I don't cock it up
[01:00] <godbyk> humphreybc: don't push your changes yet.
[01:00] <godbyk> gimme just a sec.
[01:00] <humphreybc> kay
[01:00] <flan> godbyk, is there a simple command sequence I could use to test?
[01:01] <Muscovy> flan: compiling lucid-e2 might be a good trial-by-fire.
[01:01] <flan> Muscovy, I've never compiled the manual before, so I'm not sure where to start.
[01:02] <humphreybc> guys, have a look at this bug report and the comment I added and tell me what you think
[01:02] <humphreybc> https://bugs.launchpad.net/ubuntu-manual/+bug/584537
[01:02] <manualbot> Launchpad bug 584537 in ubuntu-manual "notification area is/will be obsolete" [Low,Confirmed]
[01:05] <Muscovy> I think that looks good.
[01:05] <Muscovy> Besides, other than intended phasing out, not much is really happening yet.
[01:06] <Muscovy> flan: Have you run pkgs/install-pkgs.sh?
[01:06] <Muscovy> Once you do that, and you're theoretically all set up, compiling is just make ubuntu-manual-en_US.pdf (in the main directory).
[01:06] <godbyk> humphreybc: Okay, the PDF should build okay now.
[01:06] <humphreybc> okay
[01:06] <godbyk> humphreybc: you'll have to run bzr pull to grab the changes.
[01:06] <humphreybc> let me pull
[01:07] <godbyk> then you can commit and push your changes.
[01:07] <flan> Muscovy, which branch do I need?
[01:08] <humphreybc> what the bzr shortcut to mark bugs as fix committed?
[01:08] <humphreybc> --fixes-bugs or something?
[01:09] <godbyk> humphreybc: I never remember.
[01:09] <humphreybc> darn
[01:11] <Muscovy> flan: lp:ubuntu-manual/lucid-e2 for a compile test.
[01:11] <nigelb> humphreybc: --fixes=1234
[01:11] <Muscovy> Since the main branch doesn't compile right now.
[01:11] <humphreybc> nigelb: how do I do multiple bugs?
[01:11] <humphreybc> godbyk: main branch still not compiling
[01:11] <humphreybc> unless I broke it
[01:12] <nigelb> no clue :D
[01:12] <nigelb> ideally, one commit should be fixing one bug (commit often?) :D
[01:12] <humphreybc> godbyk: what does the \gls command do?
[01:12] <flan> Bazaar's spewing host key validation errors at my Maverick box.
[01:12] <godbyk> humphreybc: Creates a cross-link to the glossary entry.
[01:13] <humphreybc> ah, that's why it wasn't working
[01:13] <Muscovy> flan: Have you got your/an SSH key?
[01:13] <humphreybc> takes a while to compile nowadays huh :P
[01:14] <humphreybc> https://bugs.launchpad.net/ubuntu-manual/+bugs :D
[01:14] <flan> Muscovy, of course. The only thing I can think of is that I'd need to be a member of the manual project itself to be able to pull this branch.
[01:14] <humphreybc> can we get the remaining four bugs sorted today?
[01:14] <flan> (I'm associated through Quickshot)
[01:15] <Muscovy> To be honest, I didn't know people needed to login at all to get branches.
[01:15] <humphreybc> great
[01:16] <humphreybc> who's got the link to that etherpad?
[01:16] <flan> Neither did I.
[01:17] <humphreybc> http://pad.ubuntu-uk.org/ump-maverick
[01:22] <Muscovy> Gah, my inbox is filling with the manual's bug reports. XD
[01:23] <humphreybc> :D
[01:30] <humphreybc> anyone recently installed maverick?
[01:30] <godbyk> I haven't installed it at all yet.
[01:31] <humphreybc> you should :)
[01:33] <Muscovy> I've got a partition.
[01:33] <Muscovy> I use it on and off.
[01:33] <Muscovy> It's temping to just use it, but beta wackiness drives me nutty.
[01:35] <humphreybc> I've been using maverick since alpha (a dodgy upgrade from Lucid no less!) and it's been stable as a rock
[01:36] <flan> I installed the beta in VirtualBox today.
[01:37] <flan> (So I can test Quickshot functionality tomorrow)
[01:37] <humphreybc> great
[01:37] <humphreybc> flan: is the clock indicator default?
[01:37] <flan> The what now?
[01:37] <humphreybc> go to the clock in the panel
[01:37] <flan> And do what?
[01:37] <humphreybc> is it an indicator (ie, left click opens it up, consistent with the memenu, shutdown and shit)
[01:38] <humphreybc> right click should display a menu saying "remove from panel" and other crap
[01:38] <flan> Left-click brings up the calendar view, same as it's always done.
[01:38] <flan> Same as I hope it always does.
[01:38] <humphreybc> right click?
[01:38] <humphreybc> can you "scroll" through all of the indicators (like volume, messaging, clock, memenu, session menu) ?
[01:38] <humphreybc> if you open one and move across
[01:39] <flan> No. The clock is different from the rest.
[01:39] <flan> It still uses Karmic-style colours.
[01:39] <flan> It's the same docklet as it's been for years.
[01:40] <humphreybc> :(
[01:40] <humphreybc> I guess they're not putting it on the desktop till Natty then
[01:41] <godbyk> Shouldn't manualbot tell us when things have been committed to the repository?
[01:47] <humphreybc> it should
[01:47] <humphreybc> back in about an hour, getting lunch
[01:48] <godbyk> k
[01:48] <daker> godbyk, have you installed django on the server ?
[01:49] <godbyk> daker: I think I have an old version on there.
[01:49] <daker> which one ?
[01:50] <godbyk> Let me look
[01:54] <daker> godbyk, food time
[02:37] <flan> Muscovy, the Maverick TeX Live packages seem to be unable to find things like xifthen.sty and xkeyval.sty.
[02:41] <Muscovy> Someone really ought to update it. :|
[02:42] <Muscovy> Actually, I'm surprised the manual doesn't have a Tex PPA or something.
[02:49] <humphreybc> https://launchpad.net/ubuntu-manual/+milestone/ubuntu-manual-maverick-alpha
[02:49] <humphreybc> https://launchpad.net/ubuntu-manual/+milestone/ubuntu-manual-maverick-rc
[02:49] <humphreybc> https://launchpad.net/ubuntu-manual/+milestone/ubuntu-manual-maverick-final
[02:59] <godbyk> Muscovy: We do have a TeX PPA.  But I think it's offline at the moment.
[03:02] <Muscovy> Offline as in outdated or as in Launchpad is moody?
[03:03] <godbyk> I think the latter two.
[03:04] <godbyk> jenkins is the one to ask about it. He's the one who set up the PPA.
[03:04] <Muscovy> Both?
[03:05] <humphreybc> godbyk: I assigned a few bugs to you btw :)
[03:05] <godbyk> humphreybc: Gee, thanks!  :-)
[03:05] <humphreybc> when you install Maverick (which will be very soon hopefully) can you take notes on the new installer?
[03:05] <humphreybc> it hasn't landed just yet though
[03:05] <humphreybc> http://dylanmccall.blogspot.com/2010/09/new-installer-slideshow-for-ubuntu.html
[03:05] <godbyk> Yeah, I can do that when the installer lands.
[03:06] <humphreybc> lp:ubuntu-manual-website is working, right?
[03:07] <godbyk> humphreybc: should be.
[03:07] <humphreybc> y'know, it's not actually the end of the world if we release the manual AFTER Maverick comes out
[03:07] <humphreybc> of course it's ideal to coincide with the release
[03:08] <humphreybc> but manuals for OSes usually come out long after the OS is released
[03:08] <humphreybc> (probably because other OSes are proprietary)
[03:08] <godbyk> we may have to depending on when all the UI updates finally land.
[03:08] <godbyk> (They won't stop changing things on us.)
[03:08] <humphreybc> yeah
[03:08] <humphreybc> so much for the UI freeze
[03:08] <Muscovy> I think we should aim for as-close-as-possible.
[03:09] <humphreybc> I'm struggling to actually figure out what needs to be changed text wise
[03:09] <humphreybc> for bugs like this
[03:09] <humphreybc> https://bugs.launchpad.net/ubuntu-manual/+bug/630548
[03:09] <manualbot> Launchpad bug 630548 in ubuntu-manual "MeMenu, sound menu and messaging menu changes" [High,Confirmed]
[03:12] <godbyk> you'll have to read through that section of the manual and see if anything no longer holds true with the new menus.
[03:17] <humphreybc> fixing the f-spot / shotwell thing atm
[03:35] <humphreybc> godbyk: how do I do bullet points again?
[03:36] <godbyk>  \begin{itemize} \item blah \item blah \end{itemize}
[03:37] <humphreybc> thanks
[03:38] <humphreybc> how would you explain "tint" for an image?
[03:38] <humphreybc> Saturation is "how colorful the image is"
[03:38] <humphreybc> tint is...?
[03:39] <humphreybc> what's the command for bold?
[03:39] <godbyk> humphreybc: bold for what, specifically?
[03:39] <humphreybc> and for an emdash?
[03:39] <godbyk> dash is \dash
[03:40] <humphreybc> i'm listing the options under "Adjust" - levls, exposure, saturation, tint, temp etc etc. I want to bold the names of each thing and then have a very short description beside them
[03:40] <godbyk> Use \begin{description} \item[Levels} blah blah \item[Exposure] blah blah \end{description}
[03:41] <humphreybc> huh?
[03:41] <humphreybc> oh ok
[03:41] <humphreybc> description for tint?
[03:42] <godbyk> you're on your own there.
[03:42] <Muscovy> General colour scheme maybe?
[03:42] <humphreybc> http://trac.yorba.org/wiki/UsingShotwell0.7
[03:43] <Muscovy> I'd image that means basically adding a really page colour overlay.
[03:43] <Muscovy> Like saturation but not just greyscaled?
[03:50] <humphreybc> okay
[03:50] <humphreybc> if someone wants to go through the shotwell stuff and have a look at the changes, i'd be grateful
[03:51] <Muscovy> Just make a list or something?
[03:51] <humphreybc> comment on the bug report
[03:51] <Muscovy> Ah.
[03:51] <humphreybc> :)
[03:51] <humphreybc> or alternatively, just make changes
[03:52] <Muscovy> I could help, but I don't feel like using Shotwell for an hour.
[03:53] <humphreybc> neither do I, but has to be done :D
=== zkriesse__ is now known as zkriesse_
[03:53] <godbyk> This project is hard work. Who's dumb idea was this anyway?!  ;-)
[03:53] <humphreybc> heh
[03:54] <humphreybc> https://bugs.launchpad.net/ubuntu-manual/+bugs?search=Search&field.importance=High&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed
[03:54] <Muscovy> It must be cool to look back at when it was just an idea.
[03:54] <humphreybc> those are the most important
[03:54] <humphreybc> Muscovy: you should see the original manual from open office :P
[03:55] <Muscovy> I've assigned myself to Software Centre stuff, since I've already been working on that.
[03:56] <humphreybc> yay
[03:57] <Muscovy> I'll stick to the Software Centre for now, but I'll probably play with Shotwell tomorrow.
[03:57] <humphreybc> :)
[03:57] <Muscovy> It's evening here and nearing reading time.
=== Zeike is now known as brandonj
[04:04] <humphreybc> can we get manualbot telling us when people have pushed to the branch and their commit message?
[04:04] <humphreybc> it would be immensely helpful
[04:09] <godbyk> humphreybc: there's apparently a supybot bzr plugin.
[04:26] <godbyk> humphreybc: dude, you gotta stop adding revision.tex and screenshots.log files. :)
[04:27] <humphreybc> my bad :P
[04:28] <Muscovy> Is someone working on the cover?
[04:29] <godbyk> Muscovy: thorwil handles the covers.
[12:11] <dutchie> rev 10
[12:11] <manualbot> http://bazaar.launchpad.net/ubuntu-manual/revision/10 | http://bazaar.launchpad.net/ubuntu-manual -r 10
[12:11] <dutchie> hmm
[17:01] <jenkins> flan: in glade id you go help > about > credits they have the e-mail's click able any idea how to do that with a normal text box/lable ?
[17:04] <flan> It might be a Pango markup property. I'm really not sure.
[17:04] <flan> I wouldn't worry too much about that detail.
[17:04] <flan> Figure it out if you have time.
[17:05] <jenkins> k I will look into it
[17:07] <jenkins> apart from adding the people into the credits windows is there anything elese you would liek me to do?
[17:07] <flan> Once credits and licence are done?
[17:08] <flan> Uh...
[17:08] <jenkins> I am trying to find one or two settings for to get those pages pefect
[17:09] <flan> Well, we're going to need much better logging coverage... And documentation...
[17:09] <jenkins> documentaion on how to use it?
[17:09] <flan> Think you can write good-sounding text that may be exposed to other developers?
[17:09] <flan> No, documentation of the code itself.
[17:09] <flan> We've got a lot of it.
[17:09] <flan> I was planning to do that after we have 0.9.x ready.
[17:10] <flan> BEcause of the crunch.
[17:10] <jenkins> I don't know what alot of the code does but I can have a read and see what makes sense
[17:10] <flan> If not, then environment_details contains a number of bugs.
[17:10] <flan> Like commands being expressed as strings, rather than sequences.
[17:11] <flan> Would you be comfortable wrapping, testing, and revising those functions?
[17:11] <flan> I should have screen-captures working again very soon.
[17:11] <flan> So we'll also need to test stuff.
[17:12] <jenkins> have you implimented the resolution changing stuff?
[17:12] <flan> No, not yet.
[17:12] <flan> I'm going to work backwards.
[17:12] <jenkins> k just wondering if it was failing for me :)
[17:13] <flan> If you want to write some basic functions thatll change and roll back the resolution and put them inot a new package inside of lib/, that would work.
[17:13] <flan> mkdir lib/resolution/
[17:13] <flan> touch lib/resolution/__init__.py
[17:13] <flan> Put stuff in there.
[17:13] <jenkins> ok I will do some work into how to get the origianl resolution. i must be stored some where
[17:13] <flan> No, it's not failing. I just wanted to make sure I had callbacks working from that window.
[17:14] <flan> So it'd behave the way the user would expect.
[17:14] <jenkins> yea cool
[17:14] <flan> The resolution library will need to provide the current resolution and change resolutions. It shouldn't need any other externally accessible functions.
[17:15] <flan> It should internally handle everything currently done by environment_details.
[17:15] <flan> So move all the grapgics-card-checking stuff into that module and make it completely isolated from the rest of the code.
[17:16] <flan> get_resolution() -> tuple(x, y); set_resolution(x, y) -> any number of possible exceptions, grouped under a common Error class. See the server modules for examples on how to do this.
[17:16] <flan> -s
[17:22] <jenkins> ok I will have a read i need to work out how to get the current resolution first
[17:22] <flan> Of course.
[17:22] <flan> I've got lots to do, so there's no rush.
[17:23] <flan> Getting it right is more important than just getting something.
[17:23] <jenkins> ok makes sense
[17:40] <thorwil> jenkins: hi! http://www.foopics.com/showfull/1827bc02f1d99e1d27108dd08590e84b
[17:42] <jenkins> hey thorwil i like the lower one, what would it look like with different colour text to the  large  Q
[17:42] <jenkins> also what contact details/e-mail would you like to have next to your name in the credits window?
[17:44] <thorwil> jenkins: i'd like a link to http://thorwil.wordpress.com/
[17:44] <jenkins> cool will do :)
[17:45] <thorwil> jenkins: if others appear with email address, t_w_@freenet.de is ok (known to every spammer one earth since long)
[17:46] <jenkins> I am happy with the website, I will bear that in mind thanks
[17:47] <thorwil> jenkins: so it's all about color tweaks for the logo now?
[17:47]  * thorwil -> dinner
[17:47] <jenkins> for me yes
[17:47] <jenkins> i like the bottom one over the top
[17:49] <jenkins> have a nice dinner thorwil
[18:16] <jenkins> be back later
=== Zeike is now known as brandonj
[20:36] <thorwil> jenkins, flan: http://www.foopics.com/showfull/98ddcd8128b519d7bf110ea9c5f80c53
[20:38] <jenkins> I am not sure about the use of the background color and how it would look in the program. I prefer the colours on the left
[20:39] <flan> I'm okay with whatever.
[20:39] <flan> I don't think we can really go too wrong.
[20:42] <jenkins> I am just putting it in the app to see what it looks like
[20:42] <thorwil> jenkins: not sure about what to do with the logo for in-app use, would have to see ...
[20:43] <Muscovy> That's a _nice_ set of logos.
[20:44] <thorwil> ty
[20:44] <jenkins> http://imagebin.org/112804 apart form the over streched window i am unsure. what about swapping the bacground colour and the white?
[20:44] <thorwil> btw, did ben say anything about the earthquake in christchurch?
[20:45] <jenkins> erm he is ok thats all i konw
[20:45] <jenkins> ok now I like the bottom right. what about making the background white and changing the text to the background color on that one?
[20:46] <jenkins> white/see through
[20:46] <thorwil> guess there will have to be 2, one for use on bright ground
[20:46] <thorwil> the other as intended for the website
[20:47] <thorwil> the idea behind the color and contrast is a camera flash
[20:48] <jenkins> I see they are great! btw
[20:48] <jenkins> *see,
[20:48] <thorwil> glad you like them :)
[20:50] <jenkins> I was looking at colour choices earlier using agave and could not come up with anything. its very hard, you have made a good choice on that.
[20:52] <jenkins> I think the bottom left one and do it with white/transparent on the outside with current background where white is for one version .then as it is for the other one. would that look right ?
[20:54] <flan> jenkins, are you good with visualizing 2D geometry in discrete co-ordinates?
[20:54] <flan> I'm trying to redo the sub-rect logic and I'm starting to lose concentration.
[20:55] <jenkins> do you mean take a screenshot of the panel only stuff?
[20:55] <jenkins> I should be good with 2d cordinates
[20:55] <flan> Uh... Sure.
[20:55]  * jenkins is sure flan thinks he is mad :)
[20:55] <flan> I mean more like "Given this cropped section of the screen, take this other rectangle and reduce the area to only the overlapping parts"
[20:56] <thorwil> jenkins: i found tools like agave to be more of a distraction than a help, as colors depend on their surrounding so much
[20:56] <flan> You're an engineer. I'd expect you to be better with numbers.
[20:58] <jenkins> I am good with numbers, i just have to make sure i right them down correctly. what do you mean by overlapping parts?
[20:58] <jenkins> thorwil: makes sense why i could not get any where with it
[20:58] <Muscovy> Quickshot uses PyGTK, right?
[20:59] <flan> Yes, Muscovy, it does.
[21:00] <Muscovy> Are there any tutorials you'd recommend? I mean to learn it, but it looks frighteningly complicated.
[21:00] <flan> It's actually quite easy.
[21:00] <flan> The reference documentation is excellent.
[21:00] <Muscovy> Phew.
[21:01] <flan> Are you comfortable with Python in gneeral?
[21:01] <flan> general*
[21:01] <Muscovy> Fairly.
[21:01] <Muscovy> I just know "general Python".
[21:02] <jenkins> nissh recomended http://learnpygtk.org/pygtktutorial/index.html to me it does not cover everything but is usefull
[21:02] <flan> Are you intimidated by the Python module index?
[21:02] <jenkins> yes
[21:02] <jenkins> flan: which bits overlap that what i don't get
[21:05] <Muscovy> Thanks jenkins, I'll bookmark that.
[21:07] <thorwil> enough for today, good night! :)
[21:11] <flan> jenkins, I just wrote a summary. I'll commit it in a moment.
[21:11] <jenkins> ok ty
[21:12] <flan> I basically just need you to write a function that takes some base geometry and a pair of flags and returns potentially altered geometry.
[21:12] <jenkins> I am trying to work out how gnome-display-properties works out the current screenset up
[21:12] <flan> (A tuple of four numbers)
[21:13] <jenkins> ok cool I will take a look
[21:13] <flan> There's a much easier way than that.
[21:14] <jenkins> I have gained memories of wnckd or something
[21:15] <flan> wnck can do it easily, yes.
[21:15] <flan> >>> import gtk
[21:15] <flan> >>> gtk.gdk.screen_get_default().get_width()
[21:15] <flan> 2880
[21:15] <flan> >>> gtk.gdk.screen_get_default().get_height()
[21:15] <flan> 900
[21:15] <jenkins> how would you tell if there are two screens?
[21:15] <flan> Do you need to?
[21:16] <jenkins> well people can have some strange setups
[21:17] <flan> Fair enough.
[21:18] <jenkins> we can use your way for now but it would be good to do it properly
[21:19] <jenkins> I will have a play with dgkscreen
[21:19] <flan> I've just got my monitors merged into a single massive screen managed by X viewports.
[21:20] <flan> I think that's pretty common.
[21:20] <flan> Resizing it would look terrible, of course.
[21:20] <jenkins> its how nvidia twin view is handled. last release i cloned the display on the outputs for dual screens
[21:27]  * jenkins starts using gnome shell to see how he gets on
[21:38] <flan> Math issue worked out.
[21:39] <jenkins> coolio
[22:05] <jenkins> night all
[22:11] <flan> Hi, brettalton.
[22:12] <brettalton> heyya
[22:12] <flan> It's so rare that people will apply and actually drop by.
[22:12] <Muscovy> Apply for what?
[22:12] <flan> The Quickshot team.
[22:13] <brettalton> well I wanted to get workin :)
[22:14] <flan> Are you familiar with PyGTK or should I try to force some library tasks on you?
[22:14] <flan> Though I've actually finished all the major PyGTK reworking...
[22:14] <flan> And I'm going to be connecting pieces pretty quickly, so trying to work in the GUI right now might be an exercise in futility.
[22:15] <brettalton> flan: you talking to me? I'm just the (new) website guy :(
[22:15] <flan> Oh.
[22:15] <brettalton> in time I would like to learn PyGTK though
[22:16] <flan> Well, then, in that case, you'll probably want to speak to daker.
[22:16]  * flan approves application.
[22:17] <Glorfindel> lol
[22:17] <brettalton> Ya, I've got what I need, I just want to download the website branch so I can submit some changes here
[22:17] <brettalton> flan: excellent, thank you
[22:17] <flan> I dunno if we're still using that branch...
[22:17] <flan> I'm not sure what's going on witht he website.
[22:18] <flan> I've been too busy trying to get the application itself ready for the 10th.
[22:18] <brettalton> flan: don't worry, I've been talking with humphreybc and he got me on path
[22:23] <flan> I'll leave it to you, then. Not that I had any intention of building the site myself or anything.
[22:23]  * flan is not a designer.
[22:25] <brettalton> hey, we all have our skills. If it wasn't for you, what would the quickshot 1.0 release be?
[22:25] <flan> 0.0.8 with, like, more numbers.
[22:25] <flan> Which would be *awesome*.
[23:05] <brettalton> daker: you there?
[23:39] <daker> hey brettalton
[23:39] <brettalton> hey daker
[23:39] <daker> yep
[23:51] <daker> brettalton, need help ?