[11:15] <thorwil> flan, nisshh, vish: http://www.foopics.com/showfull/cb9b56043d6a15f0c3e3cef29f89b63b
[11:26] <vish> thorwil: interesting.. but i seem to have forgotten what we wanted for quickshot..
[11:26] <vish> an icon?
[11:28]  * vish should stop being everywhere , and start to FOCUS! :(
[11:49] <thorwil> vish: well, this is an icon ;)
[11:49] <thorwil> vish: why? it feels familiar everywhere because you are already there!!
[11:49] <vish> ;p
[13:03] <nisshh> thorwil: whats that picture about?
[13:04] <thorwil> nisshh: i could bet you saw a draft, that you would have to ask puzzles me
[13:05] <nisshh> thorwil: im talking about the link you pinged me about 2 hours ago
[13:05] <nisshh> i was afk
[13:08] <thorwil> nisshh: quickshot icon
[13:09] <nisshh> thorwil: ah, ok
[15:12] <flan> Works for me, thorwil.
[15:12] <thorwil> cool
[15:13] <flan> Once you've finalized it, can I get a favicon version, too? (It can probably be the samea s the icon for window managers)
[15:14] <flan> I can just generate one myself from the full-size reference, if needed, though.
[15:15] <flan> Oh. And the server needs a logo. It could, if this is aesthetically acceptable to you, be that, with "Quickshot" written in a neutral font to the right. Maybe. (I dunno. I'm not a designer)
[15:15] <flan> http://flan.uguu.ca:5000/ump/10-04 Just something to sit in the top left corner so it doesn't seem so bland.
[15:16] <flan> I'll be tweaking the CSS based on feedback from users during the Maverick run, so the colours and sizing aren't finalized or anything.
[15:17] <thorwil> ok
[16:36] <daker> godbyk, ping
[19:06] <jenkins> hey flan
[19:06] <flan> Hi.
[19:06] <jenkins> am i ok to push stuff to the branch
[19:07] <flan> Yep. I won't be making any changes until I get home anyway.
[19:07] <flan> And, even if I were, I could just pull before committing.
[19:07] <flan> You shouldn't ever need to ask.
[19:07] <flan> Oh. I've got someone who's willing to help rewrite and test the library functions.
[19:08] <jenkins> cool who?
[19:08] <flan> So I'll probably invite him to join until we're at 1.0.
[19:08] <flan> Just a friend I know from other venues. He's new to Python, but he's pretty meticulous about quality.
[19:09] <jenkins> ok cool sounds good
[19:09] <flan> He's just gonna write the user-status-screening and WM-integration stuff while I work on the UI-to-library bindings and event logic.
[19:09] <flan> While you work on the layout and appearance stuff.
[19:10] <thorwil> jenkins: hi! http://www.foopics.com/showfull/cb9b56043d6a15f0c3e3cef29f89b63b
[19:10] <jenkins> thorwil: looks great! can we play with the back ground colours? 3 different ones may be
[19:11] <jenkins> be back in 10 mins being called to dry up
[19:12] <thorwil> jenkins: ty. better not. i think of the 3 shots as being in one series, so theme doesn't change, just windows
[19:13] <flan> Ia gree.
[19:13] <flan> Iagr ee.
[19:14] <jenkins> k makes sense
[19:15] <jenkins> but can you make the arrows and the camera more distinct?
[19:15] <jenkins> I am really pleased with thoses thorwil
[19:16] <thorwil> jenkins: i could. maybe i will. though i made them subtle to not distract and also because the smaller sizes don't have those details at all
[19:18] <jenkins> I see your point it, I think it depends on the angle of my laptop screen, I will print it out tomorrow and have a look.
[19:19] <jenkins> can you e-mail/put in the branch a 48px one please ?
[19:19] <flan> Are we replacing the existing logo with this one? Or using them side-by-side?
[19:20] <flan> (The existing one is heavily pro-Ubuntu, but it *is* pretty)
[19:20] <flan> (This one is nice and neutral and clean)
[19:22] <jenkins> I think this is the icon not a logo . iirc
[19:22] <flan> Sorry. That's what I meant to imply by "side-by-side".
[19:22] <jenkins> well we need to come up with a logo basically
[19:24] <thorwil> jenkins: https://code.launchpad.net/~t-w-/+junk/quickshot_art
[19:26] <jenkins> thanks thorwil
[19:26] <jenkins> pidgin crashed
[19:39] <jenkins> flan: how do i get a url to appear like the one here imagebin.org/112417
[19:39] <jenkins> http://http://imagebin.org/112417
[19:40] <jenkins> http://imagebin.org/112417
[19:40] <flan> http://www.pygtk.org/docs/pygtk/class-gtklinkbutton.html
[19:40] <flan> Glade should have it in its toolbox.
[19:41] <flan> Note that the project's URL will not always be displayable.
[19:41] <flan> And there may be up to three URLs.
[19:41] <flan> How you present them is up to you.
[19:41] <flan> (If you even want to present all of them)
[19:42] <flan> Quickshot project URL (not exposed if the project isn't public), version homepage (may not be defined), project homepage (may not be defined)
[19:42] <jenkins> I thought I would just but quickshot.org there?
[19:42] <flan> Oh. Yes, you can do that, too.
[19:43] <jenkins> thanks flan i had found that button but not the setting to make it look like a noraml window but have now
[19:44] <flan> Where are you packing it? (On the welcome screen, I presume, but where?)
[19:45] <jenkins> i am doing the about window :P the most un important one
[19:45] <flan> As fro project/progress URLs, just give me a vbox on the screenshot-list window with two panels in it. I'll rip them out and put URLs in their place, if they're defined.
[19:45] <flan> Ah.
[19:45] <flan> That works.
[19:46] <flan> Rip them out in code*
[19:46] <flan> Part of the reason why GTK's box model is so useful.
[19:46] <flan> And why I'll nag you about the importance of using it to group related content.
[19:46] <jenkins> I know its not an important window but I had the urge to do it. I saw your changes and I can see why it makes sense
[19:47] <flan> The about window is important.
[19:47] <flan> It's just not crucial.
[19:48] <jenkins> I will do the resolution ones as well just can't decide on how to improve over last time
[19:48] <flan> Embed the progress bar in the page itself.
[19:48] <flan> Instead of making a pop-up.
[19:48] <flan> Just put a GTK progress bar in it (one of the "I dunno how long this'll take" ones.
[19:49] <flan> We can show it dynamically once the process begins.
[19:49] <flan> Assuming the process takes long enough to warrant the use of the bar.
[19:49] <flan> I can't remember if it was fast or slow before.
[19:51] <flan> In any case, it's basically just going to say "This project, <name>, requires that screenshots are captured at a resolution of XxY. Something, something. We change things now!"
[19:51] <flan> Oh. I remember what the delay was.
[19:51] <flan> Installing disper.
[19:51] <flan> Are we making that a dependency of the .deb to avoid it?
[19:51] <jenkins> it was slow last time but it will be fast as I have changed the way the graphics driver is detected. i would like to make it a dependency
[19:51] <flan> Until we can look at its code and find the right stuff to run ourselves.
[19:52] <jenkins> yep
[19:52] <flan> If it's fast, no progress bar.
[19:53] <flan> See if you can prototype that window and the user details window by the end of today. I'll try to get the UI flow advancing to the screenshot list.
[19:53] <jenkins> that window is there already
[19:53] <flan> I mean so that it has only the buttons and stuff that we need.
[19:54] <flan> It's kinda hard to go back once that point's been passed.
[19:54] <jenkins> and the screenshot list one is done and the screenshot detail one
[19:54] <flan> It really just has "Okay" and "Bail".
[19:54] <jenkins> I wil adjust them
[19:55] <flan> Screenshot details may get some tweaking once I get there, since there are more/different/stuff options than before. I won't get to it until this weekend, though, so we can probably discuss changes and work on its pieces concurrently.
[19:55] <jenkins> http://imagebin.org/112420 is what I was going to use for the user to comfirm that the change has been made correctly so it is standard gnome stuff.
[19:55] <jenkins> cool sounds good
[19:56] <flan> Same with the username-change. Once the user's been created, Quickshot will have to close before the user can continue. It's a window that kinda creates a dead end if it ever appears.
[19:56] <flan> Looks good.
[19:56] <flan> Probably just tweak the wrap-points.
[19:56] <flan> But I like it.
[19:56] <flan> Is Maverick going with orange to indicate active buttons?
[19:56] <jenkins> yep
[19:57] <flan> active/selected/default
[19:57] <flan> Kinda ugly, but whatever.
[19:57]  * flan isn't an art guy.
[19:57] <flan> Wait... Wait...
[19:57] <flan> Is that dock standard?
[19:58] <jenkins> no thats awn
[19:58] <flan> 'Kay.
[19:58] <flan> The dock is one of the things I like least about using my Mac.
[19:59] <flan> (Not because it's impractical, but because it's an inefficient use of space)
[19:59] <jenkins> i auto hide it
[19:59] <flan> Same.
[19:59] <Muscovy> I like to switch between dock and window buttons every few months.
[19:59] <flan> But then I lose the ability to see what I have open at a glance.
[19:59] <Muscovy> Docks are better for when I'm working with a lot of applications, I find.
[20:00] <flan> It's a very intuitive design, but it's not well-suited to my mindset.
[20:00] <Muscovy> You seen Gnome 3 yet? :P
[20:00] <flan> I've been avoiding it.
[20:00] <Muscovy> I've been using it, after I got over my initial shock.
[20:01] <flan> I mean I've been avoiding all news of it.
[20:01] <flan> I want to be surprised.
[20:01] <Muscovy> Ah. XD
[20:01] <thorwil> flan, jenkins: playing around with logo ideas: http://www.foopics.com/showfull/456df83df6c2d6df882e2af8261ba970
[20:01] <Muscovy> I won't spoil it then.
[20:01] <Muscovy> Those are neat logos.
[20:01] <Muscovy> I like the first and third.
[20:01] <jenkins> I like the third one :)
[20:02] <flan> The second one's brilliant, but I'd go with the third.
[20:02] <jenkins> I can't decide on gnome 3 I am waiting untill it is nearer reles
[20:02] <jenkins> *release
[20:03] <jenkins> third one has got me excited
[20:03] <thorwil> ok, so i will tweak the 3rd on another day
[20:03] <flan> The second'd be my pick if it weren't just a tad too subtle.
[20:04] <flan> But I can't see a way to un-subtle it.
[20:04] <flan> Short of moving the hybrid to the right.
[20:05] <thorwil> using 2 colors and no split on the S should help the 2nd
[20:06] <flan> Yeah... that might work.
[20:06] <flan> Except it'd be three colours, wouldn't it?
[20:07] <flan> Unless the Q becomes an outline.
[21:14] <daker> flan, ping
[21:45] <flan> Hi.
[21:45] <flan> daker, pong.
[21:46] <Muscovy> What's with the pingpongs?
[21:46] <daker> it's fine, just want to ask question how we can login to qs board
[21:47] <daker> so i used my lp openid
[21:47] <flan> I'd just need to add you as a project owner.
[21:47] <flan> I'll add everyone who's interested after I reset the database.
[21:47] <flan> (In preparation for 10.10)
[21:48] <daker> we should ask humphreybc to design something for the qs board
[21:48] <flan> Wait... Which board?
[21:48] <flan> I thought you meant my staging site.
[21:48] <flan> Which will probably be used for the next manual release.
[21:49] <daker> yes
[21:49] <flan> (I doubt I'll be ready to hand it to godbyk until after 1.0.0)
[21:49] <daker> & for other projects :)
[21:49] <flan> There's not really much to design... It's a backend to the client.
[21:49] <flan> Again, it's not intended for public perusal.
[21:49] <flan> It's just meant for administrators to approve and download screenshots.
[21:50] <daker> ah oki
[21:50] <flan> It's a very utilitarian concept.
[21:50] <flan> The quickshot.org page will be a lot more general-user-oriented.
[21:50] <daker> but it's should provide other things
[21:50] <flan> My server's basically justa  glorified database with a special protocol.
[21:51] <daker> project activity, how many screenshot has been taken by hour, by day for each user
[21:52] <flan> ...But why? It's not a social networking system.
[21:52] <flan> It's just a filesystem + database, intended to facilitate the execution of a task.
[21:53] <flan> Can you identify a benefit of indicating project activity levels?
[21:54] <daker> i don't know it's just an idea :)
[21:57] <daker> if i understand what you said, the stagging site will be just a backend for the projects owners ?
[21:58] <flan> Yep.
[21:58] <flan> It'll have some degree of public visibility, but only as much as is needed for people to decide which languages need their attention.
[21:58] <flan> And then only if the project is public.
[21:59] <flan> For all we know, someone might set up a project to so they have a checklist of things they need to capture for a school project.
[21:59] <flan> just so*
[21:59] <daker> i understand
[22:00] <flan> Whatever you see at http://flan.uguu.ca:5000/ump/10-04 is about as much as I can imagine a contributor ever needing to see.
[22:00] <flan> The system is flexible, so we can add more later.
[22:01] <flan> But, from my ancient mindset of minimalism-is-good-so-build-stuff-as-a-component-that-can-be-harnessed-by-other-stuff, this seems like the right way to do things.
[22:02] <flan> An aggregator, like the quickshot.org site, can get enough information from the backend servers to calculate activity levels, general rates of completion, and user helpfulness to display it in a more engaging manner.
[22:02] <flan> The quickshot.org site won't need to host any of the data itself, aside from deltas, because it's essentially all offered as a service by any known suppliers.
[22:03] <flan> The backends retain their one simple purpose, the aggregators layer on top of them, and then a super-aggregator could be built on top of the aggregators.
[22:03]  * flan likes layers.
[22:06] <flan> Note: Suppliers of information could be resolved by indexing/scanning the .qsproj files that are submitted to the site's bulletin board. The model's design allows for easy information-scraping.
[22:06] <flan> (I don't like proprietary or undiscoverable anything)
[22:07] <flan> </rant?
[22:08] <jenkins> flan: please let me know what else you would like me to do tomorrow night
[22:08] <flan> Can do. Mostly, it's just a matter of getting the usability logic of the GUIs out of the way.
[22:09] <jenkins> please make a list and I will do anything needed
[22:09] <flan> Then (re)building the basic libraries behind them (which is what Wetbox^3 will help me with), and then binding everything together (which is what I'll do).
[22:09] <flan> I'll just keep memo-spamming you.
[22:09] <jenkins> yep sounds good spam!
[22:09] <flan> Yay for spam!
[22:09] <flan> G'night~
[22:10] <jenkins> thnaks flan night
[22:58] <daker> dutchie, ping