[10:34] <aquarius> nisshh, heya; would you rather have my incomplete desktopcouch developer manual chapter now so that there's *something*, or wait until it's finished?
[10:34] <nisshh> aquarius, that depends how complete it is and when you plan to have it done by
[10:35] <aquarius> well, the first 60% or so is basically complete (might tweak wording, but hey ho); the latter part remains to be written
[10:35] <aquarius> but Belinda dropped me a mail to say "how are you getting on"
[10:35] <nisshh> right
[10:35] <aquarius> and the answer is: I haven't just ignored it :)
[10:35] <nisshh> i assume its just plain text with no latex formatting at this point?
[10:36] <aquarius> nope, it's latex
[10:36] <nisshh> oh ok
[10:36] <nisshh> heh, i was about to say chuck it in the branch so i can latexify it
[10:36] <nisshh> but nvm now :)
[10:36] <nisshh> well
[10:36] <aquarius> although the extent of my latex is wrapping inline code in \code{}, wrapping lines of code in \verbatim{}, and having \{section}s and \{subsection}s :)
[10:36] <nisshh> chuck it in the branch and just keep working on it from there, tbh
[10:37] <nisshh> ah ok
[10:38] <nisshh> plenty more could be done, like glossary entries, index entries, rewording, editing, etc <- aquarius
[10:38] <aquarius> ya, that's what I thought :)
[10:38] <nisshh> yeah
[10:38] <aquarius> so, I'll push a branch.
[10:38] <nisshh> yeah
[10:38] <nisshh> or you could put it in trunk
[10:38] <nisshh> that way i can jump in and add some latex stuff for you
[10:38] <aquarius> um, I have the rights to commit to trunk?
[10:39] <nisshh> yeah
[10:39] <nisshh> everyone in the launchpad team does
[10:39] <aquarius> blimey. you lot are pretty trusting. :)
[10:39] <nisshh> well
[10:39] <aquarius> if you'd rather I just pushed to trunk, then OK
[10:39] <nisshh> its pretty hard to break the branch
[10:39] <nisshh> hehe
[10:39] <aquarius> true, but then I can't test it because I don't have the upgraded latex packages (see discussions previously), so I'll just have to take it on trust, but OK :)
[10:40] <nisshh> ah ok
[10:40] <nisshh> thats fine
[10:40] <aquarius> so if I push broken latex, I'll break trunk for everyone until that's fixed. You're OK with that?
[10:40] <nisshh> no it wont
[10:41] <nisshh> itll only break make if you link it in and problems occure
[10:41] <nisshh> a simple .tex file not linked in will cause no problems
[10:41] <nisshh> aquarius, can i suggest you grab the latest trunk and inside create a dir called 'desktopcouch' or something
[10:42] <nisshh> and put your chapter in there
[10:42] <nisshh> much cleaner that way
[10:45] <aquarius> ah, OK, so I shouldn't link it in. No worried :)
[10:46] <nisshh> aquarius, yeah, its probably just safer if you dont link it in until one of us who knows latex better can check it over and make sure it has everything it needs.
[10:49] <aquarius> have pushed revno 92 which contains the chapter thus far (not linked anywhere else)
[10:50] <nisshh> ok
[10:50] <nisshh> ill have a look
[10:51] <nisshh> aquarius, see stuff like the double quotes? that has to be latexified :)
[10:52] <nisshh> that would have cause problems during make
[10:52] <nisshh> caused*
[10:52] <aquarius> what? god almighty.
[10:53] <nisshh> aquarius, yeah, in latex a pair of double quotes has to be like this: ``''
[10:53] <aquarius> hahaha party like it's 1985
[10:53] <nisshh> otherwise latex chucks a fit
[10:53] <nisshh> yeah
[10:54] <nisshh> aquarius, there are various symbols and chars that latex doesnt like, for example: _ $ &
[10:54] <aquarius> I also have a question. The app I'm building in the chapter has a bunch of stuff that isn't actually relevant to desktopcouch, so there's little point in putting the source code for the whole app in the book, since it'd waste space. So...what should I do? Should the book just reference a branch on LP?
[10:54] <nisshh> for thos a backslash before them is required
[10:54] <nisshh> those*
[10:55] <nisshh> hmmm
[10:55] <ChrisWoollard> Morning, aquarius. I was actually going to ask you how it was going this morning. But you weren't one when i thought about it. Well done for beating me to it.
[10:55] <nisshh> aquarius, which code sections were you thinking of that werent relevant?
[10:56] <aquarius> nisshh, the app is a very (very very very) simple DVD cataloguer. It's a quickly app. So everything that displays a window, that does gtk, that displays the about box, etc, is totally irrelevant to the chapter. All the desktopcouch code is in one file called "backend.py", which is the one discussed in the chapter
[10:57] <nisshh> ah i see
[10:59] <nisshh> aquarius, i would say exclude the Quickly generated code and just present it as if your adding your code into a vanilla Quickly app
[10:59] <nisshh> know what i mean?
[11:00] <nisshh> so at the start just tell the user to create a new Quickly app and reference that chapter for that and then tell the reader that all the following code is to be added to the existing stuff
[11:00] <aquarius> nisshh, sort of, but then there's the glade file, etc. If I put enough of the app into the book that you can build the app using nothing more than the book and quickly itself, there'll be a bunch of code in the chapter which is irrelevant and will bulk out the chapter unnecessarily, in my opinion.
[11:00] <nisshh> true
[11:01] <aquarius> people shouldn't have to type a glade file in; I should not have to write a whole thing instructing them what to do in glade :)
[11:01] <nisshh> thats very true
[11:02] <nisshh> aquarius, can i suggest you post to the list about this? i think we need others input on how to tackle this issue
[11:03] <aquarius> sure thing
[11:03] <nisshh> as far as i can think, there is no easy way of getting the user to use Quickly *and* teach them desktopcouch in the same chapter without telling them exactly what to do in glade
[11:03] <aquarius> unless we say: bzr branch lp:ubuntu-developer-manual/desktopcouch-dvd-thingy
[11:03] <aquarius> which I think is reasonable, myself.
[11:04] <aquarius> and having the code for all the apps in LP is a godo idea anyway!
[11:04] <aquarius> but I will lay this out in the mail.
[11:04] <nisshh> yeah
[11:05] <nisshh> aquarius, a good idea, but it would force a rearranging of the chapters (again) because the bzr/launchpad chapter is currently after yours :)
[11:06] <nisshh> and tbh, the bzr/launchpad chapter *needs* to be last
[11:06] <nisshh> since its all about releasing your app,etc
[11:06] <aquarius> I really think that explaining a bunch of glade bollocks in my chapter is not a valuable use of space. :)
[11:07] <nisshh> agreed
[11:07] <aquarius> we don't need to explain the bzr stuff. Just tell people "type this command to get the code for this app. You don't have to care what it means. If you do care, read the bzr chapter."
[11:07] <nisshh> but i for one, cannot easily think of a way around that
[11:07] <nisshh> true
[11:07] <nisshh> maybe just reference the bzr chapter when doing that stuff then
[13:05] <aquarius> nisshh, email sent as requested, so we'll see what else comes of it :)
[13:56] <nisshh> aquarius, ok, cool
[23:52]  * jasono is away: I'm busy