[00:58] <bulldog98> Riddell: http://people.ubuntu.com/~bulldog98/blog/vids/tmp.ogv
[07:47] <pvivek> i have setup kde environment, i have downloaded the sources. now cs cb and cd commands work as specified. I have downloaded all the sources, which i am supposed to compile and run.
[07:47] <pvivek> I am doing it for the first time, i would be very glad if someone can point me the right way to do it.
[07:48] <pvivek> I mean i know i have to use make,cmake,cmakeinstall. Should i just browse to the folder which has the source and then execute those commands or should i shift to cs or something like that before doing it?
[09:13] <Riddell> pvivek: best to ask kde development questions in #kde-devel
[09:13] <Riddell> bulldog98: 2012-03-11 09:13:29 ERROR 404: Not Found
[09:25] <Riddell> ooh I got the message indicator to work with telepathy-kde
[09:59] <Riddell> agateau: hmm how hard would it be to kill the gtk bits from http://bazaar.launchpad.net/~ken-vandine/telepathy-indicator/trunk/view/head:/src/indicator-approver.c ?
[09:59] <Riddell> or better just to rewrite it in qt
[10:16] <MacSeal> in the future will have kubuntu this ? http://trueg.wordpress.com/2012/02/11/a-fun-release-nepomuk-tv-namer-0-2/
[10:17] <MacSeal> I compiled kde 4.8.1 on kubuntu 11.10 
[10:18] <Riddell> MacSeal: it just needs someone to package it
[10:18] <Riddell> and maintain the package
[10:19] <MacSeal> a ok
[10:53] <grmls> hi
[11:02] <bulldog98> Riddell: I’ll have a look at the nepomuk-tv-namer
[11:10] <bulldog98> Riddell: if I package a new lib should I use bzr dh_make for the initial packaging?
[12:35] <BluesKaj> Howdy all
[14:28] <cos^> hello. what would be the best way to install libraries in debian/rules so that they go to correct lib directory (/usr/lib or /usr/lib64 depending on system)?
[14:29] <cos^> or can you point me to a good example of a library package built with qmake?
[14:51] <CIA-42> [libtvdb] Jonathan Kolberg * 2 * (13 files in 3 dirs) Initial packaging
[14:54] <CIA-42> [libtvdb] Jonathan Kolberg * 3 * debian/ (control rules) Small packaging fixes
[15:44] <cos^> what should be in dbg package's debian/.install file, or should it exist at all?
[15:58] <tsimpson> cos^: -dbg are the debugging symbols for binaries, usually you create one per source package
[15:58] <cos^> yep. but withou .install i get a empty -dbg package
[15:59] <cos^> i'm a but confused what it should contain and how to build it using cdbs
[15:59] <cos^> i have this line in rules but it doesn't seem to help DEB_DH_STRIP_ARGS := --dbg-package=libsiilihai-dbg
[16:00] <cos^> it just builds a -dbg package with changelog, README and copyright
[16:01] <tsimpson> did you add the -dbg to debian/control?
[16:01] <cos^> yes
[16:01] <cos^> https://github.com/vranki/libsiilihai/tree/master/debian
[16:04] <tsimpson> you shouldn't have an .install for the -dbg (side-note)
[16:04] <cos^> ok, i'll delete it
[16:07] <cos^> it still builds a empty (except doc) debug package
[16:40] <tsimpson> cos^: think I figured it out, qmake strips symbols (in release mode) by default, so you need to add nostrip to CONFIG in your .pro
[16:55] <cos^> tsimpson: thanks.. i forced it to debug mode and got a debug binary in the package
[17:13] <yofel> hm, has someone tried to copy files onto a bluetooth device lately? Here it's not working
[17:13] <yofel> (tried to copy something on my n900 just to have dolphin show me an empty folder)
[17:14] <yofel> and refreshing it just results in "The device is busy, waiting..."
[17:20] <tsimpson> cos^: just don't ship a debug build
[17:40] <schnelle> yofel: copying to my sumsung android phone works but doesn't work with plain nokia phone
[19:14] <cos^> tsimpson: i'm not sure how could i release a release build but still have -dbg package available
[19:15] <cos^> most packages have -dbg's in repository so i suppose they are debug builds?
[20:49] <debfx> ScottK: could you have a look at the quassel branch? I guess I need a FFe to switch the apparmor profile to enforce mode and add a ufw profile?
[21:01] <tsimpson> cos^: no, you build in release mode but with debugging symbols. debug builds have no optimizations run on them, so always release debug+release builds
[21:17] <ScottK> debfx: If you're subscribed to quassel bugs and will tend to any regressions, FFe granted.
[21:49] <CIA-42> [nepomuktvnamer] Jonathan Kolberg * 2 * (8 files in 3 dirs) Updated the nepomuktvnamer stuff
[22:07] <debfx> ScottK: thanks, uploaded.
[22:48] <Riddell> abend
[22:56] <apachelogger> Riddell: evening
[22:56] <Riddell> apachelogger: is that what "abend" means?
[22:56] <apachelogger> yes
[22:57] <apachelogger> Riddell: do you think it is better to wait for sheytan to come up with an even better splash theme or do a ui freeze exception now and throw in what I've got?
[23:01] <Riddell> apachelogger: I think just throw in what you've got
[23:02] <apachelogger> ok
[23:05] <apachelogger> one of these days I'll have to teach sheytan to not paste me jpg's :S
[23:06] <apachelogger> Riddell: actually this has to wait till tomorrow or whenever sheytan is around, I need a logo for the low bit depth fallback
[23:06] <apachelogger> Riddell: or I push in the existing stuff with the unmodified logo for bit depth and add the new version whenever sheytan is around
[23:06] <Riddell> maybe best to e-mail him
[23:07] <apachelogger> yeah
[23:07]  * apachelogger pushes current data to bzr though
[23:12] <CIA-42> [kubuntu-default-settings] Harald Sitter <apachelogger@ubuntu.com> * apachelogger@ubuntu.com-20120311231200-41abny0s0hqh6voc * (8 files in 3 dirs) Add present logo artwork + make dots darker to match + match ksplash with ply spacing
[23:20] <apachelogger> bulldog98: libqtwebkit-qmlwebkitplugin (for viewing the slideshow) [tmp dep]
[23:20] <apachelogger> ah nvm
[23:20] <apachelogger> ^^
[23:20] <bulldog98> apachelogger: I just commited something to get rid of it
[23:20] <apachelogger> bulldog98: I guess you are going to do better effects when switching?
[23:21] <apachelogger> pages
[23:21] <bulldog98> apachelogger: just added it to the TODO list
[23:21] <apachelogger> you should talk to sheytan and/or nuno about that
[23:22] <apachelogger> surely they have a good idea how ot make it more snazzy ^^
[23:23] <bulldog98> apachelogger: I try to first make the mockup itself worktm, then integrate into ubiquity and finally more artwork maybe a bit threaded too
[23:23] <bulldog98> :)
[23:23] <apachelogger> threaded?
[23:24] <apachelogger> btw, about qml plugins, you can either symlink your kde stuff into the qt imports dir OR set an env var
[23:24] <apachelogger> though seeing as I don't recall the var the symlinking might be easier ;)
[23:26] <apachelogger> woah
[23:26] <apachelogger> timezonefun looks spooky :D
[23:27] <apachelogger> I am reasonable certain that you can inject a state in the Component.onCompleted handle
[23:27] <apachelogger> though I have been wrong before ^^
[23:28] <apachelogger> alternatively the code structure would need to change, where the transition is encapsulated in a generic component that has a property on the timezone
[23:28] <apachelogger> so it would probably have to manipulate its parent
[23:28] <apachelogger> just wildely guessing here though
[23:29] <apachelogger> bulldog98: also please make a main.qml :P
[23:29] <bulldog98> apachelogger: Ubiquity-mockup.qml is the main.qml :P
[23:29] <bulldog98> should be kind of obvious :-)
[23:29] <apachelogger> no
[23:29] <apachelogger> too much code for a main.qml :P
[23:30] <apachelogger> hm
[23:30] <apachelogger> KeyNavigation...
[23:30] <apachelogger> I am reasonable certain there is a better way to do this
[23:32] <apachelogger> e.g. put all navigational objects in an Array and set the index within that array on every object, then inside the object you can do a generic index access on the array
[23:32] <apachelogger> backtab: array[index-1] etc. etc..
[23:33] <apachelogger> bulldog98: I do suggest splitting that up in way more files btw
[23:33] <apachelogger> you are getting rather deep nesting already
[23:34] <bulldog98> apachelogger: I’ll just finish the slideshow and then I’ll have a look at that
[23:34] <apachelogger> really cool stuff though
[23:35] <apachelogger> bulldog98: btw, I'd introduce some generic components there
[23:37] <apachelogger> Wizard {} holds many Page {}
[23:39] <apachelogger> then you specalize the Wizard into Ubiquity and add the visual appearance
[23:39] <apachelogger> (i.e. wizard and page are both non-visual data components
[23:39] <apachelogger> )
[23:40] <apachelogger> then you can easily handle transitions and all that
[23:40] <apachelogger> oh you have a pagesmodel already
[23:41] <bulldog98> apachelogger: yes and this is the menu :)
[23:41] <apachelogger> that should be a separate file
[23:41] <apachelogger> really mostly everything there should be a separate file tBH
[23:41] <apachelogger> inline model declarations are evil
[23:42] <bulldog98> apachelogger: that is planned, but I’m bad at finding names
[23:42] <apachelogger> plus the ListElement you have there can be specifically generalized :P
[23:42] <apachelogger> PageModel.qml :P
[23:42] <apachelogger> so, the LEs
[23:43] <apachelogger> where is that stuff from anyway :O, really spooky
[23:44] <apachelogger> oh right, you can put arbitrary stuff in ListElements
[23:44] <apachelogger> my do I hate ListElements
[23:44] <apachelogger> PageListElement.qml... ListElement { active: false, finished: false, back: false, forward: false, install: false }
[23:44] <apachelogger> then in your model you do only set the values that need setting
[23:45] <apachelogger> but really
[23:45]  * apachelogger is getting confused
[23:45] <apachelogger> bulldog98: yeah, I'd not put all that information there to begin with!
[23:45] <apachelogger> the element should only have name and file as properties
[23:46] <apachelogger> everything else is situational
[23:46] <apachelogger> the fact that you cannot go back after the disk was formatted is something only the format page needs to know and can know
[23:47] <apachelogger> so that should be a property of the page itself
[23:47] <bulldog98> apachelogger: ok
[23:47] <bulldog98> I’ll do that in a minute
[23:48] <apachelogger> the fact that you cannot click back on the first page on the other hand has nothing to do with the page itself but the fact that it is the first page (that is an external condition to the page)
[23:48] <apachelogger> so that would probably be logic that should be put into the Wizard component
[23:50] <apachelogger> bulldog98: the code looks really good, rough around the code layout edges but otherwise very nice :)
[23:50] <bulldog98> apachelogger: thanks nice to hear
[23:50] <apachelogger> hm
[23:50] <apachelogger> PageStack
[23:50] <apachelogger> where is that from?
[23:51] <apachelogger> qtextracomponents?
[23:51] <apachelogger> because I fear that was stolen from Meego/Symbian and does not fit what you need
[23:52] <apachelogger> You can only push new stuff on a stack or unwind, that is however bad UX
[23:52] <apachelogger> if I am on the timezone page and select UTC, then go back the information I set on the timezone will be lost
[23:52] <apachelogger> so what you need is an ever growing stack or a simple array
[23:53] <apachelogger> (former would of course be better due to lazy instanication of the qml files and improved startup speed :))
[23:55] <apachelogger> actually that is nicely indicated by the designs ... on meego/symbian you only have a back button, whereas your ubiquity also has a forward button :)
[23:56] <apachelogger> bulldog98: btw, for reasons of maintainability it was deemd best to create "constants" in a special UI.js (or somesuch name)
[23:57] <apachelogger> e.g.                    font.pixelSize: 18
[23:57] <apachelogger> 18 would be FONT_TITLE_SIZE or something
[23:57] <bulldog98> apachelogger: atm I’ve got them in the Styling.qml
[23:57] <apachelogger> not the pixelsize :)
[23:58] <apachelogger> styling works too, though you always need to prefix with styling
[23:58] <apachelogger> also mind that importing an item is still more expensive than importing a stateless js file
[23:58] <apachelogger> (though I am too much thinking mobile phone I guess ^^)
[23:58] <apachelogger> hardly matters on a pc
[23:59] <apachelogger> (also another IMHO more reasonable approach is to make most of those things generic components)
[23:59] <apachelogger> TitleText { color: foo; font.pixelSize: 18 }
[23:59] <apachelogger> for example