=== Zeike is now known as brandonj [07:45] good morning! [07:45] hey thorwil :) [07:46] * thorwil starts to work on the quickshot logo [10:10] Mmm.. strawberries are delicious. [10:10] And I have two pounds of 'em.. all to myself! [10:11] lol [10:11] what's up? [10:12] Not much. [10:14] not much is good [10:14] I should amend that: not much *at the moment*.. other than eating strawberries and watching hulu. :) [10:27] hehe, for a sec i thought thorwil was gonna choke someone when they mentioned using a meerkat ;p [10:28] vish: how would you know i didn't? ;) [10:28] thorwil: I dint say i know you dint.. i thought you would ;p [10:29] vish: lol. [10:29] thorwil: true.. they haven't replied on that thread since... Hmm... [10:32] vish: actually, the meerkat was nothing compared to turning "at least 3" into a definitive change after 3 [10:34] yeah.. if I remember correctly, the 'at least three' meant that we'd stick with the same design for the whole set from LTS until the next. (changing at each LTS) [10:34] ? [10:35] thorwil: well, i never knew when the plan was to have a new cover every release.. when i had done the alpha version, the plan was to just change the color at the tip alone every release.. and i thought that a single cover of sometime was the basis for rejecting wolter's design.. the sometime being for every LTS [10:35] godbyk: heh, it was really just 3 in the sense of one more than a pair. you know the way you would put at least 3 elements into an icon, if you mean a group [10:36] apart from thorwil's fear of the lynx ;p [10:36] thorwil: ah, okay. [10:36] vish: heh.. yeah. no one wanted to take on the task of drawing the new mascots each time. [10:37] godbyk: if we some how convinced thorwil to use a meerkat .. pretty sure wolter will get pissed ;p [10:37] godbyk: not just that. lynx would have been cool, though not hitting the desired posture/tone. meerkats would be ok. but a narwhal? catastrophe [10:37] vish: ha! so true. [10:38] thorwil: Hey, now. Don't diss narwhals! [10:38] NARWHAAAAAAAAALLSSSSS rule! [10:38] yaya, they're awesome [10:39] jedi unicorns of the sea [10:39] http://weebls-stuff.com/songs/Narwhals/ [11:35] vish: you must be banned :p you're getting more people addicted :D :D :D [11:49] addicted? i went 2 weeks without and only started to shiver a little bit [12:03] thorwil: lol === bilalakhtar_ is now known as bilalakhtar [15:06] zkriesse: i didnt know you ran the Youth Team :) === mrjazzcat-afk is now known as mrjazzcat [15:34] http://chipx86.github.com/gtkparasite/ I fully intend to use this in my next GTK project, if only because of the artwork. [15:35] flan: that project looks awesome, im going to check it out some more :) [17:23] Lemme know if you find any really cool uses for it. [17:23] I'm thinking it'll allow for better testing of procedural workflow designs. [17:24] Like what we're doing with Quickshot. So we can bypass my whole insistance on making every window individually runnable. [17:24] If a console can hijack the current window at any point, everything would become super-easy. [17:25] Heck. I'm gonna switch modes and start using it tonight. [17:25] It looks like a much cleaner approach. [17:26] Aww... He died. :( [17:26] His brain was eated by cute. [17:30] 10:24 < flan> Like what we're doing with Quickshot. So we can bypass my whole [17:30] insistance on making every window individually runnable. [17:30] 10:24 < flan> If a console can hijack the current window at any point, [17:30] everything would become super-easy. [17:30] 10:25 < flan> Heck. I'm gonna switch modes and start using it tonight. [17:30] 10:25 < flan> It looks like a much cleaner approach. [17:30] 10:25 -!- nisshh [~ryan@ubuntu/member/nisshh] has quit [Ping timeout: 258 [17:30] seconds] [17:30] 10:26 < flan> Aww... He died. :( [17:30] 10:26 < flan> His brain was eated by cute. [17:31] * flan spams. [18:02] flan: my net crapped itself at that point [18:02] everything just went *pop* and dissapeared [18:02] :) [18:14] Nope. Brain eated by cute. [18:14] True statement. [18:15] End of discussion. [18:19] lol flan :) [19:08] flan: ping [19:33] ping [19:33] thorwil: that was a sad little piggy, err. ping! ;p [19:34] vish: well, it worked, without addressee ;) [19:35] but i fully support a pong for jenkins [19:36] hey thorwil and vish how are you? [19:36] thorwil: no worries,i'v got your 6! ;) [19:36] jenkins: hey.. sleepy ;) [ just about to hit the sack :) ] [19:37] flan: http://imagebin.org/112298 what is the purpose of the bits circled in red? [19:37] jenkins: good, self? [19:37] sleep well vish [19:37] I am good thanks thorwil [19:38] jenkins: i would suspect custom widgets to fill those gaps [19:38] I suspect so as well but I just want to double check as the window is not organised as I would expect [19:39] as far as glade goes [19:39] got 2 artwork requests today, still a lack of those willing to pay, though [19:39] thats not good, out of interest whats the going rate? [19:39] I am a poor student :P [19:40] jenkins: varies a lot. from 200 for like a full week to 450 per day, so far :} [19:41] nice :) [19:41] jenkins: recommendations say one should take at least 60 € per hour as freelancer [19:42] there are recomendations for that sort of thing [19:43] of course [19:43] whats that page that ben added the projects to that tells you its worth if we paid everyone [19:44] if i wouldn't live for cheap as it is already, i would have to move to some place in asia, or something [19:44] ohloh? [19:44] jenkins, they're just spacers. You'll see when you run it. [19:45] http://www.ohloh.net/p/ubuntu-manual [19:45] i thought they were any objections to removing them and reorganising the boxes flan? [19:45] In the meantime, Parasite. I'm gonna drop the every-window-can-run-itself push in favour of using that. It looks awesome. (Google Parasite + Gnome) [19:45] You can do whatever you feel looks good. [19:45] I just provided my idea. [19:46] Just make sure it's completely obvious. Like, that the user can't possibly get confused and fill in more information than they have to to complete any specific step. [19:46] (To that end, I feel that a unique button is necessary for each path) [19:46] thanks thorwil that was it [19:46] * flan AFKs for 1.5 hours. [19:46] flan: i want to keep the idea just reduce the boxes used etc [19:46] later flan === mrjazzcat is now known as mrjazzcat-lunch [19:54] godbyk: ping [20:08] jenkins: hey! [20:08] hey bilalakhtar I was about to contact you [20:09] what would you like to help with? [20:09] jenkins: yes! I have branched the quickshot source, looking at it its clear it isn't running on maverick [20:09] jenkins: I am using maverick , can fix bugs [20:09] flan: Thanks for the memo! [20:10] cool well it should work up to the first screen opening and that is as far as the gui goes at the moment [20:10] yes it does work to the full screne [20:10] then tells me I should be using lucid [20:10] I can easily solve that [20:11] really what branch have you got i am using mavrick and do not have that? [20:11] what revison is it? [20:11] jenkins: ah, I misused the word 'branch' [20:11] jenkins: I apt-get sourced from the PPA [20:11] * bilalakhtar branches it off now [20:11] jenkins: Actually I wanted to look at the deps [20:12] are thats why its not working, we are rewrting from scratch at the moment so the old version is rather obsolete [20:12] http://imagebin.org/112304 is the new first page [20:12] jenkins: cool! === Zeike is now known as brandonj [20:13] i wrote the lucid thing as a fail safe for the manual team to avoid people taking screenshots on other versoins of ubuntu [20:13] you will need to install quickly [20:13] jenkins: really? [20:14] hmm, ok [20:14] well the project started as a quickly project and we have not worked out / had time to work out how to open the glade files with out doing "quickly design" [20:15] jenkins: Ah, that isn't difficult at all! [20:15] builder = gtk.Builder() [20:15] builder.add_from_file('PATH_TO_UI_FILE') [20:15] that's it! [20:15] is that how to open them in glade to edit them? [20:16] jenkins: to open them in glade a double-click works [20:16] jenkins: you mean for the quickly UIs? I don't know about that [20:18] yea me nether thats the only reason we are still using quickly o and quickly run but i expect there is an equivalent to that as well [20:19] jenkins: Project QStream on LP started off as a quickly project; in the middle I transitioned it away from Quickly because I don't like quickly [20:19] jenkins: and it appears I am not interested in quickshot any more, sorry [20:19] jenkins: I would contribute to the Ubuntu Manual rather [20:20] jenkins: may i suggest "Welcome to Quickshot! Capture screenshots in a variety of languages, under specific conditions, to submit them to documentation projects." as short is better [20:20] jenkins: you are free to decline me from the team [20:20] how come whats worng with quickly. I do all the release stuff? [20:20] thanks for the suggestion [20:21] jenkins: I will see tomorrow; I have experience with Python and can definitely help; okay I will work [20:21] you should give feed back to didrocks in #quickly he always want its. thanks that would be great [20:21] look forward to talking to you tomorrow [20:23] Thanks jenkins ! [20:23] no problem thank you have a good evening/day (depending on time zone) [20:24] jenkins: I have decided; just managed to run quickshot, looks good, don't have a good bandwidth right now so cannot install quickly, I will surely help now, starting from tomorrow. its late night in here [20:25] cool, I will try and find out a way of not using quickly run and quickly desgin so you don't need to use them [20:26] bye, going [20:27] flan: for some reason now the .ui files open in glade by clicking them [21:06] I removed the legacy dependencies from the files. [21:06] Their broken-except-by-opening-in-Quickly-ness bothered me. [21:08] hey flan i tried to assign the start from url to the button but I could not get the button to do anything how do I get it to import into the bin/quickshot file? I tried the normal way [21:08] I don't like Quickly, either, for the record. [21:08] Like, at all. [21:09] I think it embodies the same things I hate about using IDEs. [21:09] And Glade over GTK calls. [21:09] But I'm a control freak. === mrjazzcat-lunch is now known as mrjazzcat [21:11] well as the .ui files now open by clicking. what is the quickly run eqivilent command and we can stop using it [21:11] It should just be ./quickshot [21:11] Open the script in Python. [21:12] You can continue using quickly run and quickly design, if you want. [21:12] I've servered the core dependencies on Quickly. [21:13] (I broke them all last night 'cause I didn't install Quickly before getting into my dad's truck, aos I had to develop stuff offline) [21:13] I would like to know the equivlients as I would like to stop using quickly as i do all the release stuff and thats the hard bit [21:13] Don't worry too much about wiring the buttons for now. I'll implement the main page tonight, to give you a working model for further development. [21:13] sc source [21:14] cd source #* [21:14] bin/quickshot [21:14] It should "just work". [21:14] o right we can stop using quickly [21:15] But a better solution would be to move quickshot out of bin/ and add a file-specific rule to the Debian path information. [21:15] * jenkins does sudo apt-get remove quickly [21:15] We still want the quickshot/ package in python-shared. But we also want to avoid import-path-mangling. [21:15] Which using bin/ requires us to do. [21:15] I'd advise against that. [21:16] Keep using Quickly until we've got this working for the Maverick launch. [21:16] Then we'll remove all legacy references to it in time for the official 1.0 release. [21:16] well i can soon change the rules file so that the bin/quickshot file is some where else in the source [21:16] Maverick will likely be server:1.0.0-preview and client:0.9.x. [21:17] cool [21:17] installed quickly again [21:17] We'll fix bugs in each as they appear. [21:17] And simultaneously commit non-critical enhancements to get the client up to 1.0.0 around the same time we release the manual. [21:18] So, for now, getting it working's the biggest thing. [21:18] sounds good. anything else I cna do [21:18] I see you didn't like my separators. =P [21:18] * flan has a habit of using

s in web pages, too. [21:18] I am going to redo the about window when I get the time. I could not decide on the separators I decided against them in the end [21:18] It looks good without them, though. [21:19] For now, an error-reporting window is a must. [21:19] I don't care if we just use GTKDialog (if you think it looks good) or subclass it or create a totally new window. [21:20] But we need to be able to tell the user that a problem occurred, that details are available, and ask them to tell the program what to do to recover. [21:20] how much do we want to display to the user? can we just say "an error occured pleas click "file a bug" to tell us what went wrong" ? [21:21] I have no clue how they would recover the program but as we have apport support the bug stuff should be easy as it pulls in the last three logs [21:23] "Oops! Something went wrong." "The gist of the problem is <...>" "The gory details follow." ("This error is non-recoverable", [send bug report] [make the developers guess at the problem] | "You can try contacting the server again" [Do it] [Nah] | "Your system's messed up beyond repair" [that sucks]) [21:23] Not every problem will need a bug report. [21:24] If the Qs server crashes mid-op or the user's network connection drops, we don't really care, from a bug-fixing standpoint. [21:24] If it's an unhandled exception, then we'll need to ask for a report/let apport handle that/however whatever works. [21:25] I think a gtk dialog is fine [21:25] 'Kay. [21:25] We can just use TextWrap to make it multi-line, as necessary. [21:25] yep [21:26] I'll write the convenience class behind it tonight, too. [21:27] So, then, I guess the next thing you'll need to do is prototype the "Okay, the server's up and it told me I need to be a user named 'Juan Giseppe'. Why is this important and how can I set it up?" window. [21:27] Should the user be given the option to skip this step? [21:28] so the manual user case of a consitant user name on the pc or they need to give us details to do the project [21:29] The manual user for consistency. [21:29] also can we remove the http://imagebin.org/112311 bit please. alot of our windows are fixed dimensions so do not/can not be resized [21:29] k'ay [21:29] We can't collect contributor details this early, since they may need to change to another user. [21:29] And then ~/.quickshot will change. [21:30] If we let them skip this, there should be a warning that'll tell them that the project administrators may not be able to accept all uploaded screenshots. [21:30] If we don't let them skip it, then, obviously, there won't be a warning. [21:31] well we should only show it if the project needs it and not allow skiping [21:31] That thing you pointed out is actually a status bar. I always find them a good way of providing background information to users about what's going on. [21:31] For example, "Attempting to contact server..." [21:31] Okay. No skipping. [21:32] username = details['config'].get('username') [21:32] if username: [21:32] if not-current-user: [21:32] show_window [21:33] Probably also if it is the current user, but the Common attribute differs from what's expected. [21:33] This is normally the user's "real name". [21:33] ok can we remove the right hand dots form the status bar? [21:34] I think so. I'll look into that tonight. [21:34] it makes sense to keep the status bar. kay thanks [21:34] I'm kinda surprised that calling set_resizable(False) leaves them enabled. [21:34] I don't know its strange [21:34] Oh. [21:34] That's easy. [21:35] In base.py, add the following: [21:35] (Anywhere that makes sense after self._sbr... has been declared) [21:35] Actually, no. [21:35] Don't do it there. [21:35] project_selection.py [21:36] Find the code that says "self.set_resizable(...)" [21:36] Immediately below that, add this line: self._sbr_<...>.set_has_resize_grip(self.get_resizable()) [21:37] Where <...> is whatever I called the status bar in base.py. [21:37] Replicate that through all the new .py files. [21:37] ok thanks will do [21:38] Reference: http://www.pygtk.org/docs/pygtk/class-gtkstatusbar.html#method-gtkstatusbar--set-has-resize-grip [21:39] yep that works, There is one window that is allowed to be expanded so i will not take it off of that [21:39] Add the code anyway. [21:39] It only disables it if the window is itself unresizable. [21:40] If the window's resizable, the code's a no-op, effectively. [21:40] It's just more consistent and it leaves full control in the Glade layer. [21:41] (In case you ever want to make the window fixed-size-y. [21:41] done, i will do a very rough user account set up window and tidy it up tomorrow. [21:41] 'Kay. [21:42] The next step after that is screen-resolution. [21:43] (Probably) [21:43] (Maybe it's uploader details) [21:43] (But we can inject uploader details later) [21:45] I will look at those tomorrow I need to go to bed soon. uploader one is there already [21:45] 'Kay. [21:46] I'll probably retouch all the Glade files today to make sure all the objects have conventional names. [21:46] btn_whatever [21:46] I probably won't mess with layout. [21:46] I'll just get the welcome screen working and move some logic into modules/comments in appropriate modules. [21:47] And get an error-reporting system in place. [21:47] And the recent-projects system. [21:51] cool I have done a rought window that looks awful but will do fine for if you want to impliment it will push it in about 10 mins [21:52] 'Kay. [21:52] I'm leaving aesthetics to you. [21:53] Hopefully, we'll be able to maintain pace with each other until we're ready for the next UMP burst. [21:55] we should be able to if i can get all the windows you want implace with all the boxes etc in it I can paly with the lay out untill my heart is content [21:55] <3 [21:56] right night flan and all [21:56] G'night~ === mrjazzcat is now known as mrjazzcat-afk === mrjazzcat-afk is now known as mrjazzcat