[00:11] <flan> Just one page left for the server. Yay.
[00:11] <flan> (But it's a big one and I'll have to write at least one support page to feed it information)
[00:42] <godbyk> daker: pong.
[00:42] <godbyk> daker: Is that from a TeX Live installation?  If so, you may want to try a different mirror.
[01:08] <Muscovy> Does the Maverick writing freeze mean it's just editing from then on?
[01:10] <godbyk> Muscovy: Basically, yeah.
[01:11] <Muscovy> I'd better get writing then.
[01:11] <Muscovy> :P
[01:11] <godbyk> Yeah, I know. We don't have a lot of time. :)
[01:13] <Muscovy> Yeah, let's not do this again for Natty.
[01:15] <godbyk> It's always a bit of a race since we're try to release the manual at the same time as Ubuntu is released.
[01:15] <godbyk> And it's hard to start writing and taking screenshots until after the UI freeze.
[06:09] <vish> hrm...
[14:47] <thorwil> i wonder if a green-screening like approach could be applied to the wallpaper for screenshots
[14:47] <nisshh> thorwil: what do you mean>
[14:48] <nisshh> ?
[14:49] <thorwil> nisshh: suppose the default wallpaper will change before release, but we start taking screenshots now. could one switch to seldomly used solid color or a pattern as background, to later on replace all parts of it shining through with the final wallpaper?
[14:50] <thorwil> but that was just a quick thought, partial transparency willmake that non-trivial
[14:50] <nisshh> thorwil: hmm, yea its doable, but that would take AGES since each one would most likely have to be done individually
[14:51] <nisshh> it would be different for each screenshot so its probably not automagical
[15:49] <flan> Well, a lot of screenshots won't expose any part of the wallpaper at all.
[15:50] <flan> So we could define all of those on the Quickshot server once I finish its base implementation in a few hours and start capturing those.
[15:50] <flan> Then define the rest once we know what the final wallpaper will look like.
[15:50] <flan> start capturing them*
[15:51] <flan> Or define everything and just keep the wallpaper-exposing ones disabled until we're ready for them.
[15:52] <flan> The hold-up will be the QS client, which, though I'm sure it's getting close to being done, won't be available much before the freeze.
[15:52] <flan> I'll be switching focus to help Jenkins with it starting tomorrow.
[16:38] <flan> Any web-designer-types around right now?
[16:38] <thorwil> hmm
[16:39] <flan> (Simple question related to DOM-ordering, 'cause my mind's not working right at the moment)
[16:40] <thorwil> flan: that's not my thing, but how about you just ask? :)
[16:40] <flan> Because I'm not thinking right. =P
[16:41] <flan> <span id="x">Hello!</span> <!--How could I change the value of that element without innerHTML?-->
[16:41] <flan> I can't remember which node I need to tweak.
[16:41] <flan> And my code's not close enough to complete to just try it.
[16:43] <flan> Oh. .data.
[16:43] <flan> Issue resolved.
[16:43] <thorwil> glad i could be of help ;)
[16:45] <flan> Quite. =P
[19:29] <jenkins> flan: ping
[19:44] <jenkins> nisshh ping
[19:46] <flan> Hi.
[19:46] <jenkins> hey flan can you have a look at lp:quickshot please
[19:46] <flan> What do you want me to look for?
[19:46] <jenkins> quickly run does not work giving and error
[19:47] <jenkins> *an
[19:47] <jenkins> http://paste.ubuntu.com/485544/
[19:48] <jenkins> but the folder is there, i moved everything to do with the program to the "source" folder and now it will not run. I am not sure if it has something to do with a missing package in mavrick as I have jsut changed to it. I thought I had it working again
[19:50] <flan> quickshot.py
[19:51] <jenkins> that error comes form the quickshot file in the source/bin folder
[19:52] <flan> I realize that. But Python expected a .py, .pyc, or .pyc file to match the name of the provided module, unless working with C extensions or doing something low-level with the import engine.
[19:52] <flan> expects*
[19:53] <flan> You're going to be breaking that monolithic file into smaller pieces anyway, so you might as well start separating it now.
[19:53] <flan> I should be (effectively) done with the server in about two hours.
[19:54] <jenkins> i am not following completly, that line (that is causing the error) worked before whats wrong with it?
[19:54] <flan> From what I can see of your paste, it's that it can't find a module named 'quickshot'.
[19:55] <flan> Which is where it expects to find the class you defined.
[19:55] <flan> When the 'quickshot' executable file is run directly, its module-name is '__main__', not 'quickshot'.
[19:56] <jenkins> I always read that line ( from quickshot import AboutQuickshotDialog ) to be from the folder quickshot import the file AboutQuickshotDialog
[19:57] <flan> Nope.
[19:57] <flan> From the file 'quickshot.py'.
[19:57] <flan> (Or pyc or pyo)
[19:58] <flan> It expects to find it either in the current package or in the process's root path, by default.
[19:58] <jenkins> well the file AboutQuickshotDialog is in a folder called "quickshot" :/ so has that bit of code always been screwed?
[19:58] <flan> import sys; print sys.path to see its search targets and order.
[19:59] <flan> Where's the file that holds the definition?
[19:59] <jenkins> the path is imported before the line from....
[20:00] <jenkins> http://paste.ubuntu.com/485549/ is the file
[20:00] <flan> ...An insert into sys.path?
[20:01] <flan> Did you write that or was it Simon?
[20:01] <jenkins> I don't know who wrote it may have been tommy
[20:01] <flan> Eew...
[20:01] <jenkins> http://imagebin.org/111924 is the file layout
[20:01] <flan> Not Tommy. But that code.
[20:01] <jenkins> lol
[20:02] <flan> Looks like this is gonna be a busy week.
[20:03] <jenkins> yea I have to start learning stuff, I have reached my limit on knoledge
[20:03] <flan> That import's going to fail because 'quickshot' isn't resolvable.
[20:04] <flan> First, you'll need to define an __init__.py in quickshot/ so Python will recognize the directory as a package.
[20:05] <flan> Second, you'll need to make that "import quickshot.AboutQuickshotDialog as AboutQuickshotDialog", unless you're like me and prefer infrequently used references to be explicit.
[20:05] <flan> In that case, you'd drop 'as' and refer to the full dotted path every time.
[20:06] <jenkins> ok I will have a go at the __inti.py
[20:06] <flan> touch __init__.py && bzr add __init__.py
[20:06] <flan> It can be empty.
[20:06] <jenkins> o it turns out that is just a file :P
[20:07] <jenkins> just worked that out
[20:07] <flan> It probably should be empty, until you're comfortable with writing packages as libraries.
[20:08] <flan> (We won't need to do that here, since you're writing application-level code)
[20:10] <jenkins> adding the init file makes it all work again I wonder if I removed it accedently
[20:19] <jenkins> yey got it working again fixed another problem
[20:19] <flan> Yay.
[20:21] <nisshh> jenkins: sorry, i was afk for a while, did you want something?
[20:21] <jenkins> hey nisshh I was just going to say i will try and finish my chapter off for the manual. I have been real busy with work lately
[20:22] <nisshh> jenkins: cool, i was going to do some work on the dev manual today, but i didnt get home till later so it didnt really work out
[20:23] <jenkins> just have to wait for another day then :)
[20:23] <nisshh> hehe
[20:23] <jenkins> flan: what would be the best way to make a spinner from http://imagebin.org/111925
[20:23] <nisshh> jenkins: anyway, im off to bed its nearly 4am here
[20:23] <nisshh> night
[20:23] <jenkins> night
[20:25] <jenkins> I have the gkt spinner source code but it is not in python http://paste.ubuntu.com/485557/
[20:26] <flan> That should be in pyGTK somewhere.
[20:27] <jenkins> i can use it in pyhton but it gives an awful spinner that looks weedy
[20:27] <flan> Can you provide a screenshot?
[20:27] <flan> It might not be bad as a placeholder.
[20:28] <flan> We don't have much time left, and a spinner's less important than having a clean codebase.
[20:28] <flan> Making that one work wouldn't be hard, but it'd take time that might be better spent elsehwree at this point.
[20:29] <flan> (It'd basically be a matter of loading the image, splitting it into pieces, and blitting those to a widget at regular intervals)
[20:29] <jenkins> I will post a screenshot when I can make the spinner work again :) I lost the file with it in
[20:30] <flan> If it's not hyper-critical, leave it aside and focus on functionality.
[20:30] <flan> We can pack a widget into the box during the pre-Maverick cycle.
[20:30] <flan> We'll be using that period as a buffer for testing and polish anyway. (unfortunately)
[20:30] <flan> (Stupid me-moving)
[20:32] <jenkins> http://imagebin.org/111927
[20:33] <flan> Looks fine to me. Until we have time to do something better.
[20:33] <flan> But that one has the advantage of improving authomatically.
[20:33] <flan> As GTK gets better (or the user gets better themes for the engine), the spinner should look better, too.
[20:34] <jenkins> I need to work out this whole inheritance thing. Can i use the inheritance thing to import a spinner and a text box into the space of the tables whilst the data is being downlaoded?
[20:34] <flan> Re-inventing the wheel (literally) may be counter-productive here.
[20:34] <jenkins> well there is a better spinner in evolution and other programs
[20:34] <flan> Y...es... but probabky not the way you're imagining it.
[20:35] <flan> You'll probably want a library of UI eyecandy for that.
[20:35] <flan> With functions you can call that return appropriate GTK objects to pack into boxes.
[20:35] <flan> Data's going to download pretty fast now.
[20:36] <jenkins> ok I will leave them out for now
[20:36] <flan> The whole bzr layer's gone and it's running in SQLite/filesystem stuff.
[20:36] <flan> It should be no slower than the time it takes to ping, plus a millisecond or ten.
[20:37] <flan> http://flan.uguu.ca:5000/ump/10-04/en_CA/_progress However long it takes for you to download this is how long the user'd need to wait to get data from the network.
[20:37] <jenkins> cool that is fast so how do i get the data into the program?
[20:39] <flan> http://pastebin.com/PvJiGeKv
[20:39] <flan> It'll be faster once I turn off debug mode ont he server.
[20:40] <flan> Just create a session using one of the two profvided functions and then call query_progress().
[20:40] <flan> It returns data in much the same way as the old system.
[20:40] <flan> (needed, pending, accepted)
[20:40] <flan> The main difference is that you'll get both a localized friendly name and the internal system name.
[20:41] <flan> The user needs to see the friendly name, while the server needs to get the system name in any upload/download requests.
[20:42] <jenkins> which provided functions?
[20:42] <flan> client/__init__.py They're near the bottom.
[20:42] <flan> Everything's documented.
[20:43] <flan> Put client/ into a lib/ directory and import it as 'lib/client'.
[20:43] <flan> You can rename it if you want.
[20:43] <flan> Er...
[20:43] <flan> lib/client*
[20:43] <flan> lib.client*
[20:43]  * flan eats keyboard.
[20:44] <jenkins> ok thanks I will have a read and paly
[20:44] <flan> Usage samples can be found in r142 on the server branch.
[20:45] <flan> It'll provide details like screen resolution, too.
[20:45] <flan> It's worth playing around with the library from an interpreter.
[20:46] <jenkins> will do
[21:28] <jenkins> night all, thanks for you help flan
[21:28] <flan> G'night~
[21:28]  * flan pushes support for rejecting screenshots.
[21:28] <flan> Just two more features left~
[21:29] <flan> Aww... He left too quickly. :(
[23:03] <flan> QS server's effectively done. Yay.
[23:04] <flan> Just need to comment it all (hundreds of functions!) and get feedback from real users... which, unfortunately, won't happen until it's actually needed.
[23:04] <flan> Hooray for moving!
[23:08] <flan> godbyk, it seems I have no trouble hosting it from home, and I still need to write a couple of support scripts and document how to host it on something common, like mod_wsgi, so I'll probably just run the site through this cycle. It'll make it easier to fix any bugs that might come up, too.
[23:10] <flan> If hosting from home becomes an issue, I'll move it to my webhost or put it on one of my Debian boxes at work and bounce DNS from my host.
[23:11] <flan> (Or let you set up a DNS record for it)
[23:11] <flan> (Which we could also do for hosting from home, if you want things to look consistent)
[23:11] <flan> (Just cname against hamsterx.homelinux.org, since my home IP is technically dynamic)