[00:00] <godbyk> \hyperref[sec:nautilus]{Περιηγητή αρχείων Ναυτίλο} should work.
[00:01] <godbyk> So 'sec:nautilus' is the section to link to and 'Περιηγητή αρχείων Ναυτίλο' is the text that will be the link (colored, clickable, etc.)
[00:03] <c7p> thx godbyk :)
[00:05] <godbyk> np
[00:05] <godbyk> there's usually a way to do anything you want in latex.. it's just a matter of finding the trick. :-)
[00:06] <c7p> btw how was the latex conference ?
[00:07] <godbyk> It was awesome!
[00:07] <godbyk> I had a great time.
[00:07] <c7p> nice to hear that
[00:07] <godbyk> Got to chat with Don Knuth for a few minutes and even had him sign the book I won as a door prize. :)
[00:07] <godbyk> (Don Knuth is the guy who wrote TeX back in 1978.)
[00:10] <c7p> you are honored :P
[00:10] <c7p> is it ok http://pastebin.ubuntu.com/460013/?
[00:10] <c7p> http://pastebin.ubuntu.com/460013/ *
[00:11] <godbyk> c7p: Yep, that's better.  Thanks!
[00:11] <c7p> np
[00:12] <c7p> the extra spaces at "\noindent   Το " will affect the text on pdf?
[00:13] <godbyk> Nope, it won't have any effect.
[00:18] <godbyk> brb
[00:37] <godbyk> back
[00:39] <c7p> nice
[00:39] <c7p> what else do we have to do for the greek manual ?
[00:46] <c7p> godbyk: greek tex file sent
[00:49] <godbyk> c7p: thanks
[00:49] <c7p> np
[00:49] <godbyk> Once I get the glossary stuff fixed I think that about covers everything.
[00:50] <godbyk> I'll look at our list again to double-check.
[00:50] <c7p> great
[00:50] <godbyk> Is there anything else that you think we need to do?
[00:50] <godbyk> Once I make the final PDF, I'll have you guys look at it to make sure it's all okay.
[00:50] <c7p> good idea
[00:50] <godbyk> Then I'll give thorwil the page count and dimensions of the cover so he can finish that.
[00:50] <godbyk> Then we should be ready, I think.
[00:51] <c7p> finally :P
[00:51] <godbyk> If Launchpad would ever come back online, I'd build all the translations again. :-/
[00:51] <godbyk> c7p: I know!
[00:51] <c7p> hehe
[00:51] <godbyk> c7p: Thanks for putting up with me and my slowness. :-)
[00:51] <godbyk> Hopefully the other translations will go more smoothly now that we have a slightly better idea of what we're doing. :)
[00:51] <c7p> np you did what you could and you still do
[00:51] <c7p> yap
[00:52] <c7p> good night/morning/evening all
[01:07] <jenkins> godbyk: how much have you looked into doc book to latex?
[01:07] <daker> humphreybc: where is my design ?
[01:10] <godbyk> jenkins: not too much, but I think that docbook -> latex -> pdf is the normal path to generate pdf from docbook.
[01:11] <j1mc> actually, it's more docbook > xsl-fo > fop
[01:11] <j1mc> fop creates the pdf output
[01:11] <godbyk> and how does fop generate a pdf?
[01:12] <jenkins> godbyk: I tried a file for the ubuntu translators guide, it worked ok but dblatex added some custom stuff. we need to find a way to stop it doing that.
[01:12] <j1mc> godbyk: i don't have much experience with it, really.
[01:12] <godbyk> I found this http://wiki.docbook.org/topic/FOP which leads to http://xmlgraphics.apache.org/fop/
[01:12] <j1mc> i do know that the pdf output isn't great.  latex pdf output is much, much better
[01:13] <godbyk> In any case, I think going from docbook to latex to pdf will be easy enough.
[01:13] <j1mc> there is the proprietary "renderx" which does docbook -> pdf output.  opensuse uses that for their pdf's.
[01:13] <godbyk> yeah, we'll want to make sure the output uses our styles and not the ultra-lame default styles (which are just ugly as all get-out!)
[01:14] <godbyk> plus, having an intermediate .tex file means we can do any nit-picky typographic tweaking we want before generating the final pdf.
[01:14] <j1mc> did you all see this? http://mdzlog.alcor.net/2010/07/06/weve-packaged-all-of-the-free-software-what-now/
[01:14] <jenkins> I *think* dblatex allows you to create custom styles
[01:14] <godbyk> (and you know how I love nit-picky typographic tweaking!)
[01:16] <jenkins> http://dblatex.sourceforge.net/ is the docs page
[01:19] <godbyk> I just clicked on their Docbook example.. <shudder>
[01:21] <godbyk> whee! launchpad is back up.
[01:27] <jenkins> godbyk: are you able to spare some python knolegdge and get http://pastebin.com/SWn91Dkh to print "yey ubuntu" please
[01:28] <godbyk> jenkins: sure. one moment.
[01:30] <godbyk> jenkins: the "if 'Ubuntu' in content' line should use 'str(content)' instead of 'content') then it'll work.
[01:30] <godbyk> otherwise, it checks to see if one element in the list 'content' is equal to 'Ubuntu'
[01:30] <jenkins> thanks, i would not have thought of that
[01:31] <godbyk> np
[01:32] <godbyk> jenkins: y'know, the lsb_release command is a python script.
[01:32] <godbyk> jenkins: would be easier (cleaner) to 'import lsb_release' and get the info through there.
[01:33] <godbyk> import lsb_release
[01:33] <jenkins> I asked in #python and told it did not exist. I wll change it
[01:33] <godbyk> distinfo = lsb_release.get_distro_information()
[01:33] <godbyk> id = distinfo.get('ID', 'n/a')
[01:33] <godbyk> print id
[01:33] <godbyk> (or something like that.)
[01:34] <jenkins> is that module also there on other distros?
[01:35] <godbyk> absolutely no idea.
[01:35] <godbyk> let me check red hat real quick
[01:35] <j1mc> i think fedora does it differently.
[01:35] <godbyk> red hat uses a bash script
[01:36] <jenkins> does the lsb_release (in bash) still work in fedora/redhat?
[01:36] <godbyk> it's looking in /etc/lsb-release for info
[01:37] <godbyk> jenkins: yeah, red hat does it completely different.
[01:37] <godbyk> so it looks like checking the lsb-release output is best.
[01:37] <godbyk> er, lsb_release, rather.
[01:37] <jenkins> ok thanks i will stick with that then
[01:39] <daker> jenkins: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/lsbrelease.html
[01:39] <godbyk> jenkins: for what it's worth:
[01:40] <godbyk> $ lsb_release -i
[01:40] <godbyk> Distributor ID:	RedHatEnterpriseClient
[01:40] <godbyk> $ cat /etc/redhat-release
[01:40] <godbyk> Red Hat Enterprise Linux Client release 5.5 (Tikanga)
[01:40] <jenkins> thanks godbyk and daker
[01:43] <daker> jenkins: http://bugs.python.org/issue1322
[01:45] <jenkins> thanks daker it appears the bash command is avalible but python has some idduse using its equivlent
[01:46] <daker> yes
[01:56] <godbyk> Any translators in here?
[01:57] <jenkins> yes I do english usa to english uk :P
[01:57] <godbyk> jenkins: heh.  well, did the uk translation status change much in the past couple hours?
[01:58] <godbyk> I just got a notice from launchpad that a new translation template was imported.
[01:58] <godbyk> and I want to know if it marked previously-translated strings as needs-translated again.
[01:59] <jenkins> no if you look at the page and sort by last chnaged it was 6 hours ago on danish
[02:00] <godbyk> jenkins: yeah, I don't know that it modifies that timestamp.
[02:00] <godbyk> what happens is that some of the translated strings get flagged as suggestions.
[02:01] <jenkins> o well english uk is 100% still
[02:01] <godbyk> and the translators have to go through and approve the suggestions again.
[02:01] <jenkins> yea i am aware of the bug
[02:01] <godbyk> okay
[02:01] <godbyk> just making sure it's not wreaking havoc again.
[02:01] <godbyk> (wish they'd get it fixed already. it gives me such a headache.)
[02:03] <jenkins> I think it gives us all a headache
[02:04]  * jenkins is trying to work out how to write gtk menus manualy
[02:06]  * godbyk is trying to walk someone through fixing his messed up svn working directory.
[02:07] <daker> jenkins: menu = gtk.Menu()
[02:08] <daker> item = gtk.MenuItem(''BlaBlaBla)
[02:08] <daker> menu.append(item)
[02:09] <jenkins> thanks daker, what about making each item do something?
[02:10] <daker> item.connect("clicked", self.do_somthing)
[02:11] <jenkins> ok thanks
[02:11] <daker> menu.show_all()
[02:11]  * jenkins goes an plays
[02:14] <godbyk> brb
[02:20] <h00k> yes
[02:20] <h00k> tis me.
[02:20] <h00k> in the wrong channel.
[02:47] <daker> humphreybc: have you finished the design ?
[02:47] <humphreybc> almost, just waiting on some pictograms
[02:47] <humphreybc> daker: did you update the planet?
[02:47] <daker> not yet :)
[02:52] <daker> why do you asked that ? are you going to change them ?
[02:53] <humphreybc> no but I sent you an updated PSD file with some changes
[03:12] <daker> humphreybc, the interview is really awesome
[03:13] <humphreybc> which interview?
[03:14] <daker> ubuntu-uk
[03:14] <humphreybc> oh
[03:14] <humphreybc> thanks
[03:15] <daker> it means that you have made a lot of interviews ?
[03:15] <humphreybc> haha
[03:15] <humphreybc> yes i've done a few
[03:21] <humphreybc> daker: so you're still working on planet.ubuntu-manual.org?
[07:12] <nisshh> omfg, we have a support leecher in our loco channel
[07:27] <nisshh> urh, 2 support leechers now
[07:29] <vish> nisshh: hmm??
[07:29] <vish> support?
[07:29] <vish> nisshh: nvm , i missed the "loco" part of your line :)
[07:30] <nisshh> vish: meh, yea we keep getting people from other countries trying to bum support off of us
[07:30] <vish> nisshh: hehe, you guys must be too welcoming ;)
[07:31] <nisshh> we have to keep kickbanning them
[07:32] <nisshh> vish: lol, no i dont know why we seem to get alot of them, they must get kicked out of their own loco channel or something
[07:32] <vish> nisshh: alot ?  > http://hyperboleandahalf.blogspot.com/2010/04/alot-is-better-than-you-at-everything.html
[07:32] <vish> :p
[07:34] <nisshh> vish: oh, haha
[09:24] <jenkins> morning!
[09:34] <thorwil> o/
[11:03] <nisshh> jenkins: hey, i have sorted out the permissions stuff with Rick, do you still want to help me out and write a chapter?
[11:04] <jenkins> yea please nisshh
[11:06] <nisshh> jenkins: ok, can you join the team: https://edge.launchpad.net/~ubuntu-developer-manual
[11:06] <nisshh> and subscribe to the mailing list
[11:06] <jenkins> done
[11:07] <nisshh> ok
[11:08] <nisshh> ok, your approved
[11:08] <jenkins> thanks
[11:08] <jenkins> just let me know what i can do
[11:09] <nisshh> jenkins: you know that wiki page i gave you yesterday that lists all the chapters?
[11:09] <jenkins> yep
[11:09] <nisshh> pick one of the chapters you want to work on
[11:09] <nisshh> that can be your one
[11:10] <nisshh> unless you want to do more than one of course
[11:10] <nisshh> :)
[11:11] <jenkins> they all have people by them. are those people still doing them?
[11:12] <nisshh> jenkins: well, iv had a chat with aquarius, rick and didrocks, and they all agreed that if i/we/people wrote the chapters they would be happy to "mentor" us and make suggestions since they know what they are talking about
[11:13] <nisshh> jenkins: one of the main reasons i took this on is because they all also work on maverick, so they have very little time to spare for the manual
[11:13] <jenkins> ok thats cool, I can do Creating an application with Quickly or Building a User Interface with glade or both, I don't know what you had your eye on. there are others i can help with
[11:14] <nisshh> jenkins: i was going to do all of them anyway so go ahead and pick whatever you want, im not fussed
[11:14] <nisshh> whatever is easiest for you
[11:14] <jenkins> also what is the state of the app that we are doing for it. I will do both then
[11:15] <nisshh> jenkins: ok cool
[11:16] <nisshh> jenkins: i have a branch of the sample app on lp, gimme a sec
[11:16] <nisshh> https://code.edge.launchpad.net/~nisshh/ubuntu-developer-manual/udm-sample-app
[11:16] <nisshh> there
[11:16] <jenkins> I was thinking we should create the app, and leave it in lots of stages in the branch so a folder for each stage.
[11:16] <nisshh> currently you cant run that app
[11:16] <nisshh> jenkins: not bad thinking
[11:17] <nisshh> jenkins: we would want it to be runnable and useable at each stage though
[11:17] <nisshh> jenkins: its a little identi.ca reader
[11:18] <jenkins> so eveytime something major is done, make a new stage folder. yea it would work to some form at each stadge. full funtionality at the last stage. how hard will it be to make?
[11:18] <nisshh> jenkins: not hard
[11:18] <nisshh> jenkins: its mostly done already, all we need to do is break it up into the stages and make sure it runs ok
[11:18] <jenkins> also that app is not a quickly app
[11:19] <nisshh> its not?
[11:19] <nisshh> oh, i thought it was
[11:19]  * nisshh shrugs
[11:20] <nisshh> jenkins: looks like it to me
[11:20] <jenkins> well quickly run does not work, we should make it a quickly ap if we are explaining quickly in the manual. there is no .quickly file in it
[11:20] <nisshh> jenkins: no, that is a quickly app
[11:21] <nisshh> jenkins: ah i see what you mean yea
[11:21] <nisshh> jenkins: currently to run the app you will need the trunk code from quickly-widgets
[11:22] <jenkins> o I was about to add the package from synaptic
[11:23] <nisshh> jenkins: hehe, yea most of it will work except some new code
[11:25]  * jenkins gets quickly widgets
[11:26] <nisshh> jenkins: in order to run the current app you will have to get the trunk and modify your path
[11:27]  * nisshh hasnt been bothered to do that yet :)
[11:34] <jenkins> nisshh please let me know when you have the app working , I am failing at the moment
[11:35] <nisshh> jenkins: it should be working
[11:35] <nisshh> jenkins: are you making sure your using the trunk code for quickly-widgets?
[11:36] <jenkins> from quickly.widgets.url_fetch_progressbox import UrlFetchProgressBox is failing I have the new branch from launchpad and its linked in
[11:36] <nisshh> linked in how?
[11:37] <jenkins> there is no url_fetch_progressbox file in the branch. I linked /usr/share/pyshared/quickly with the correct folder in the branch
[11:38] <nisshh> jenkins: ah, no no, all you need to do is modify your path so that you are pointing at the trunk for quickly-widgets
[11:39] <jenkins> thats the same thing though surely
[11:39] <nisshh> not exactly
[11:39] <jenkins> what do i do then?
[11:39] <nisshh> you dont link quickly-widgets with quickly, its independant
[11:39] <nisshh> give me 1 minute to get it setup myself
[11:40] <nisshh> jenkins: which branch did you get from lp to get the quickly-widgets trunk code?
[11:41] <jenkins> i did bzr branch lp:ubuntu/quickly-widgets
[11:42] <nisshh> jenkins: ah, thats not quite right, thats the current code thats in the repos, youll need lp:quidgets
[11:42] <nisshh> quidgets is the old name for quickly-widgets
[11:42] <nisshh> hasnt been changed in lp yet
[11:44] <jenkins> right got the old branch now
[11:44] <jenkins> *right
[11:44] <nisshh> yea
[11:46] <jenkins> what now then, I like doing things wrong today :P
[11:46] <nisshh> lol, one second
[11:47] <nisshh> cant remember how to set my path right
[11:47] <jenkins> nither do it
[11:47] <nisshh> jenkins: sorry, iv got to do some digging
[11:48] <jenkins> no worries
[11:48] <nisshh> ok
[11:58] <nisshh> jenkins: argh, i cant get it working just right
[11:58] <jenkins> me neither glad its not jsut me :P
[11:58] <nisshh> jenkins: iv got to have dinner, but ill be back afterwards and ill figure it out
[11:58] <nisshh> lol
[11:58] <jenkins> kk
[12:07] <jenkins> nisshh: done it, I will explain after you have eaten dinner
[12:16] <nisshh> jenkins: omg! how did you do it? spill the beans!
[12:17] <humphreybc> daker: you there?
[12:18] <nisshh> humphreybc: enjoying your new membership? :)
[12:18] <jenkins> well it works for me as I don't use quickly widgets otherwise. in the folder of the branch do "debuild" . in the folder above you will get a package. unistall quickly-widgets in synaptic and install the new one. you also need to search BeautifulSoup in synaptic. ( nisshh )
[12:18] <humphreybc> nisshh: I haven't even done anything with it yet, need to set up my ubuntu email address and posting on the planet
[12:18] <nisshh> humphreybc: ah yes
[12:19] <nisshh> jenkins: ah thats how you did it
[12:19] <jenkins> well it makes sense and its easier to clean up afterwards
[12:19] <nisshh> yea
[12:19] <nisshh> ah yes got it
[12:20] <jenkins> the app is not very pretty
[12:23] <nisshh> no its not
[12:23] <nisshh> jenkins: we can always clean it up though
[12:23] <jenkins> also the "Dent" button appears to shuffle the list or find more dents.
[12:23]  * jenkins nods
[12:24] <nisshh> whats wrong with that?
[12:24] <jenkins> can you add in the .quickly file please then people can use quickly commands. I think "Dent" needs a better name
[12:24] <jenkins> on the button
[12:26] <humphreybc> daker, jenkins, i'm going to get quickshot.org very soon, so if daker could start working on the quickshot site asap then we can just move it over
[12:26] <jenkins> :)
[12:27] <nisshh> jenkins: ok, ill just be one xec
[12:27] <nisshh> sec
[12:27] <nisshh> jenkins: you know its an identica reader right? so its dent instead of tweet
[12:27] <jenkins> nisshh: no rush :)
[12:28] <jenkins> nisshh: yep
[12:28] <nisshh> ok
[12:31] <nisshh> jenkins: ah i see yes
[12:34] <nisshh> jenkins: ok i added the .quickly file: bzr pull
[12:35] <nisshh> jenkins: yea, quickly commands work now
[12:36] <jenkins> cool
[12:36] <nisshh> jenkins: so basically, each chapter should be teaching the user about that tool/lib as well as providing and explainging the code to them
[12:37] <nisshh> we dont want each chapter to be more that about 3-4 pages
[12:37] <nisshh> pdf-pages
[12:37] <jenkins> yea, i think the glade one will be quite long, there are alot of settings in it
[12:37] <nisshh> yea
[12:38] <nisshh> try and keep that down to just the necessary settings plus a quick explanation
[12:38] <nisshh> that should keep it < 5 pages
[12:38] <nisshh> hopefully...
[12:38] <jenkins> yep, :)
[12:39] <nisshh> jenkins: so your fine with the quickly and glade chapters for now?
[12:39] <jenkins> yea, i will see how much I can get done.
[12:39] <nisshh> ok
[12:39] <jenkins> have we got a latex code branch
[12:40] <nisshh> jenkins: i dont expect us to necessarily have a release out for maverick so we will have to see
[12:40] <nisshh> yep we do, hang on
[12:40] <jenkins> ok thats good, I have a few other things to do for maverick
[12:40] <nisshh> its pretty much our manual code without all the chapters really
[12:41] <nisshh> jenkins: yea, if we run late we will just re-target to 11.04 i guess
[12:41] <jenkins> I think we may do it a month after 10.10
[12:42] <nisshh> yea, maybe
[12:42] <nisshh> depends how much we can write and if we get other people helping i guess
[12:42] <jenkins> indeed
[12:44] <nisshh> jenkins: https://code.edge.launchpad.net/~nisshh/ubuntu-developer-manual/ubuntu-developer-manual
[12:44] <nisshh> i havent changed any of it yet
[12:45] <nisshh> ill add in files for each chapter once as we write them and ill get godbyk to teach me some tex
[12:45] <nisshh> i mean ASK godbyk'
[12:45] <jenkins> I know some tex, I have been working on the translators guide pdf. what do we need to know?
[12:46] <nisshh> jenkins: just some general stuff, linking in chapters, formatting, translations, etc
[12:46] <nisshh> i think we should have a different set of formatting to the other manual
[12:46] <jenkins> i can do some of those things, I am sure godbyk will help us along :)
[12:46] <nisshh> yea
[12:47] <nisshh> i think i know how to link chapters in, and i can manage the glossary index stuff
[12:47] <jenkins> what about screenshots?
[12:47] <nisshh> yea, screenshots i think would be good
[12:47] <nisshh> not as many as the other manual though lol
[12:47] <nisshh> maybe 10-15 tops
[12:48] <jenkins> how will we handle different languages as some of them may be harder to get than others
[12:49] <nisshh> jenkins: what do you mean?
[12:50] <jenkins> well obviously there is quickhsot, but i guess we would have to translate the app and then get the screenshots of it then? What about one of glade with the app half finished?
[12:51] <nisshh> jenkins: ah yes, hmmm, we will have to think about that i think
[12:51] <nisshh> but yes we could use quickshot just like we used it with the other manual
[12:52] <jenkins> yea, we will need to adjust is slighlty but we will have to think on it
[12:52] <nisshh> jenkins: the above is exactly why i dont think we will have a maverick release :)
[12:53] <nisshh> there is too much stuff like that :)
[13:00] <humphreybc> nisshh: could you do me a favour?
[13:03] <nisshh> humphreybc: depends...what is it?
[13:05] <nisshh> humphreybc: are you still there?
[13:07] <humphreybc> yes yes
[13:07] <humphreybc> could you add the meetings on saturday to the ubuntu fridge calender?
[13:08] <humphreybc> instructions here: https://wiki.ubuntu.com/Fridge/Calendar
[13:08]  * nisshh doesnt know how to do that
[13:08] <nisshh> ill try
[13:09] <nisshh> humphreybc: the collab meeting and the manual meeting?
[13:09] <jenkins> the fridge is only for the meetings in #ubuntu-meeting it thought
[13:09] <nisshh> dunno
[13:10] <jenkins> go to http://fridge.ubuntu.com/calendar and it says "It is used for #ubuntu-meeting"
[13:10] <nisshh> ah
[13:11] <nisshh> maybe ill just put the collab meeting there for now
[13:11] <nisshh> unless we are having that somewhere else
[13:11] <jenkins> it is in here #ubuntu-meeting is booked
[13:11] <nisshh> ah
[13:12] <nisshh> and so is our team meeting im guessing?
[13:12] <jenkins> so far only manual team people are on the "attendees" list. I do not know of a manual team meeting
[13:12] <jenkins> looking at http://pad.ubuntu-uk.org/collaborationmeeting
[13:13] <nisshh> oh
[13:13] <nisshh> humphreybc: what meetings are we having on saturday!
[13:14]  * nisshh is really confused now
[15:51] <jenkins> afternoon
[15:59] <daker> jenkins, <humphreybc> daker, jenkins, i'm going to get quickshot.org very soon, so if daker could start working on the quickshot site asap then we can just move it over
[15:59] <daker> ?
[15:59] <daker> he sent something ?
[16:01] <jenkins> daker: I don't think anything has been sent yet there was those mockups on his home server
[16:02] <daker> oh i think hi is just notifying us
[16:04] <jenkins> I don't have the link for his server, we will have tio ask him for the mock ups
[16:04] <jenkins> som eof the ext is wrong, like facebook links
[16:04] <jenkins> *text
[16:04] <jenkins> brb
[16:11] <jenkins> back
[16:12] <daker> jenkins, http://humphreybc.homeip.net/files/
[16:13] <jenkins> daker: http://humphreybc.homeip.net/files/quickshot-pngs.zip is waht we want
[16:13] <daker> there is no psd there
[16:13] <daker> just pngs
[16:13] <jenkins> yea, thats all we have at the moment
[16:14] <jenkins> I guess e-mail ben and ask for them
[16:48] <jenkins> daker do you know how to add keyboard shortcuts to gtk menus? Also do you know how to add a line going across?
[16:49] <jenkins> ops not here
[17:56] <abhi_nav> is Benjamin Humphrey is here?
[17:57] <abhi_nav> godbyk, ping
[18:02] <nisshh> abhi_nav: no he isnt, he is asleep right now and im about to go to bed as well
[18:02] <abhi_nav> nisshh, who? godby or Benjamin?
[18:02] <nisshh> abhi_nav: Ben isnt here
[18:02] <abhi_nav> nisshh, whats Benjamin's nick?
[18:03] <nisshh> abhi_nav: humphreybc
[18:03] <abhi_nav> nisshh, thanksyou.
[18:03] <nisshh> abhi_nav: no problem, try again in about 2-5 hours
[18:03] <nisshh> you might catch him then
[18:04] <nisshh> cya
[18:46] <jenkins> daker: do you know how to add the accelerator keys to gtk menu's. Like the ctnrl+Q one for quit
[18:47] <jenkins> I have Q but can't get "Ctrl+Q"
[19:03] <daker> jenkins, http://pastebin.com/inGzVKVP
[19:05] <jenkins> daker: what did you change?
[19:05] <daker> change what ?
[19:06] <daker> just create an accelgroup fro the current window : agr = gtk.AccelGroup()
[19:06] <daker> then add the accelgroup to the window
[19:06] <daker> self.add_accel_group(agr)
[19:07] <jenkins> ok thanks dak
[19:07] <jenkins> * daker
[19:07] <daker> key, mod = gtk.accelerator_parse("Q")
[19:07] <daker>         exit.add_accelerator("activate", agr, key,
[19:07] <daker>             mod, gtk.ACCEL_VISIBLE)
[19:07] <daker> then tell him what to parse
[19:08] <daker> then create the accelerator for each item you want
[19:11] <jenkins> o daker sorry i should have said I have done http://pastebin.com/XTUbQyFd but can't quite see whats wrong
[19:13] <jenkins> daker: got it thanks
[19:14] <jenkins> quit = gtk.ImageMenuItem(gtk.STOCK_QUIT, agr) should be line 25 thats what I have got wrong
[19:15] <daker> yep
[19:18] <jenkins> now I have to work out how to make it very simple to add the menu bar to every quickshot window automatically
[19:47]  * jenkins thinks quickshot looks good with out menu's cluttering things up, shame we need them
[20:00] <jenkins> flan: ping
[21:50] <flan> jenkins, pong.
[21:50] <flan> We don't need menus.
[21:50] <flan> Config files FOREVER.
[21:50] <flan> For. Ever.
[21:51] <jenkins> flan: do you know how I can add the menu bar to the top of every window? we need it for the file a bug menu and translate this aplication
[21:51] <jenkins> this is what i asked in #ubuntu-app-devel
[21:51] <jenkins>  I have my menu bar how I want it but how do I set it up in bzr branch lp:quickshot so it appears on every window. I can't work out where to put each bit. This is the menu bar http://pastebin.com/j7kM1L7y in a small sample window. I know I need to find a place for lines 15 -69 and a place for lines 70-71 and change it so that it works for the correct box "vbox1_welcome" . I would appreciate anyone who can spare a
[21:52] <flan> vbox1? That's not an approved prefix. =P
[21:52] <flan> It's actually a frame property, not a window element.
[21:53] <humphreybc> godbyk: you around?
[21:53] <jenkins> right.. so do you know how to add it to every window easily?
[21:54] <flan> Supposing the current frame is named, for lack of creativity, 'self', it would just be a matter of doing the following:
[21:55] <jenkins> I have a file with a little sample window in that it adds the menu to . I don't knwo how to do it in the scale of quickshot
[21:55] <flan> menu_bar = gtk.MenuBar(); self.add(menu_bar); <add every menu item>; menu_bar.show()
[21:55] <flan> You'd need to factor the menu-populating code into a common function or parent class.
[21:56] <flan> A parent may be the most elegant way to do it, really, since that'll offer a lot of convenience in the long run.
[21:56] <jenkins> yea thats where I am stuck
[21:56] <flan> Can you link to a working module's code?
[21:56] <flan> Your major is compsci, right?
[21:57] <jenkins> can you rephrase the question? No mechanical engineering, i am learning python as i go
[21:57] <flan> Ah.
[21:57] <flan> Okay, then.
[21:57]  * flan can't make assumptions.
[21:57] <jenkins> I have written my own module and i can get results out of it if thats what you mean
[21:57] <flan> It may be.
[21:57] <humphreybc> so, who knows about drupal vs wordpress?
[21:58] <flan> Basically, I want to see something that shows an example of a functioning window.
[22:00] <humphreybc> flan?
[22:00] <jenkins> http://pastebin.com/j7kM1L7y run that its a dummy window
[22:00] <flan> Bonjour.
[22:00] <flan> I'm familiar with Wordpress. Less familiar with Drupal.
[22:00] <humphreybc> You'd know about pros and cons for WP vs drupal, wouldn't you?
[22:01] <flan> I view them as tools for different purposes.
[22:01] <humphreybc> It's for http://omgubuntu.co.uk
[22:01] <humphreybc> we're currently on blogger
[22:01] <humphreybc> but want more customization and faster speed, less shit and grossness
[22:04] <jenkins> I could do the menus in glade but there is so many settings to find that this way they are guaranteed to be the same across the program. Useful if we change something, we don't have to do it loads of times
[22:16] <flan> I got called away.
[22:16] <flan> All I can do is that that Wordpress would handle what's currently on the site just fine, humphreybc.
[22:16] <flan> I don't know the first thing about using Drupal for blogging.
[22:17] <humphreybc> okay
[22:27] <jenkins> humphreybc: can you e-mail daker and i the photoshop files of the website please
[22:28] <humphreybc> the quickshot one?
[22:28] <jenkins> yep
[22:28] <humphreybc> sure thing
[22:28] <humphreybc> I'll get it to you later today
[22:28] <jenkins> ty
[22:32] <flan> jenkins, http://pastebin.com/GbZYzbFv
[22:32] <flan> I have no means of testing it right now, so it'll probably fail in some way, but it may give you a place to start.
[22:33] <jenkins> Thanks, I will have a play tomorrow morning
[22:34] <flan> The idea is basically that QuickshotWindow takes responsibility for setting up everything common to a bunch of windows, its "children".
[22:34] <flan> As well as providing any facilities they all need.
[22:35] <flan> The menubar stuff should be moved into its own function (or functions), since it's a lot of code and long strings of code complicate readability.
[22:35] <humphreybc> you should build quickshot with the global menu in mind :P
[22:36] <flan> We should design for OS X!
[22:36] <humphreybc> that too
[22:36] <jenkins> rigtht if i put it in a file called menu_bar how would I go about calling it? i have          from quickshot import menu_bar; call it with  menu_bar.<what goes here>
[22:36] <humphreybc> if you actually want some user interface design help, ask godbyk (but he's quite busy) or ask me and i'll ping the design team
[22:37] <jenkins> what goes where the <> are?
[22:37] <flan> from src.gui.common import QuickshotWindow
[22:37] <flan> Then create windows that inherit from that.
[22:37] <flan> Inheritance isn't an overnight concept.
[22:37] <flan> For most people.
[22:38] <flan> I wish I had time to show you a practical example.
[22:38] <jenkins> hmm.. ok I think i will give it some time. i have done all the other windows in gladee so I just need to add it to that.
[22:38] <jenkins> no worries thanks for your help
[22:43]  * jenkins wonders what happens to the global menu in gnome shell
[22:43] <humphreybc> gnome shell is going to die
[22:46] <jenkins> I think it has a way to go before they can release it
[22:46] <jenkins> not sure I will like it but I don't like kde either
[22:46] <humphreybc> bah, unity is going to kill gnome shell
[22:48] <jenkins> no sure I like the unity bar on the left, it needs a hide feture
[22:49] <jenkins> I only see the top panel all the time, desktop space is important.
[22:53] <jenkins> the gnome shell app menu system needs a sort out its just a mass of icons
[22:56] <jenkins> I do like that the design is different, not looking like mac as ubuntu is getting at the moment
[22:57] <dutchie> humphreybc: not quite
[22:57] <dutchie> different aims
[22:57] <dutchie> unity is aimed at people who want to do one thing at a time
[22:57]  * jenkins does lots at once
[22:57] <dutchie> gnome-shell is for people who like organising workspaces around complex tasks
[22:57] <jenkins> I also like workspaces
[23:15] <jenkins> night all
[23:41] <dutchie> oh god
[23:44] <dutchie> http://fonttest.design.canonical.com/
[23:45] <dutchie> they stole our idea!
[23:47] <jenkins> dutchie: how did they steal it? what idea?
[23:48] <dutchie> oh
[23:49] <godbyk> dutchie: where do we get the font to provide feedback on?
[23:52] <dutchie> you have to be an ubuntu member for now
[23:52] <dutchie> http://design.canonical.com/2010/07/the-ubuntu-font/