[00:01] <Quintasan> PROGRESS
[00:01] <Quintasan> :D
[00:01] <Quintasan> argh, why the hell there is a SEGV in there?
[00:02] <apachelogger> doesnt like you
[00:03] <Quintasan> apachelogger: that's not a reason to spew SEGV's at me :S
[00:03] <Quintasan> apachelogger: http://dl.dropbox.com/u/69524/troll.tar.gz
[00:03] <Quintasan> :P
[00:03]  * Quintasan is going to regret this
[00:04] <apachelogger> hm
[00:04] <apachelogger> valgrind talks about memleaks in X and fontconfig \o/
[00:04] <apachelogger> with a qt hello world app
[00:05] <apachelogger> also still getting loads of possible losses regarding eventdispatcherglib
[00:05] <Quintasan> apachelogger: btw. I've asked this, if I'm doing (inside a constructor) QPushButton *problemButton = new QPushButton(somecraphere, [wtf to put as a parent?]
[00:06] <Quintasan> this?
[00:06] <apachelogger> jefferai: http://people.ubuntu.com/~apachelogger/tmp/valgrind.log should you ever get example files, maybe this helps too :)
[00:06] <apachelogger> it's from a hello world example
[00:06] <apachelogger> http://doc.trolltech.com/4.3/tutorial-t1.html
[00:06] <jefferai> apachelogger: tell thiago this
[00:06] <jefferai> :-)
[00:06] <jefferai> or tzander
[00:06] <Quintasan> apachelogger: 60mb of memory?
[00:07] <apachelogger> Quintasan: yup
[00:07] <jefferai> but don't tell them I told you
[00:07] <Quintasan> wth
[00:07] <jefferai> heh
[00:07] <Quintasan> hey don't tell me that my TrollFace app steals even more @_@
[00:07] <apachelogger> hm
[00:07] <apachelogger> jefferai: you shouldn't have said that
[00:07] <jefferai> heh
[00:07] <jefferai> where do you see 60mb?
[00:08] <Quintasan> megabytes :P
[00:08] <Quintasan> possibly lost: 59,018 bytes in 970 blocks
[00:08] <JontheEchidna> that's 5.9 kb
[00:09] <jefferai> no
[00:09] <Quintasan> 0.45 megabyte
[00:09] <jefferai> that's 59 kb
[00:09] <JontheEchidna> yeah, woops
[00:09] <Quintasan> :O
[00:09] <JontheEchidna> not MB though
[00:09] <jefferai> nobody can do math
[00:10] <Quintasan> okay, everything is fine, apart from the whole app throwing SEGV's all around
[00:12] <Quintasan> omfg, it's not the image's fault that the app i crashing
[00:12] <Quintasan> is*
[00:17] <apachelogger> Quintasan: did I just break it or is the resource file empty?
[00:17] <Quintasan> ...
[00:18] <Quintasan> it's empy here too
[00:18] <Quintasan> wtf
[00:18] <apachelogger> well
[00:19] <apachelogger> need I say more
[00:19] <Quintasan> hah
[00:19] <Quintasan> apachelogger: even if you add the trollface it still fails to display it
[00:19] <Quintasan> dunno why :S
[00:20] <Quintasan> apachelogger: fixed tarball -> http://dl.dropbox.com/u/69524/App1.tar.gz
[00:20] <Quintasan> though it still spews crap at me :(
[00:23] <apachelogger> well
[00:24] <apachelogger> Quintasan: I would use QPixmap to begin with
[00:24] <apachelogger> "The QPicture class is a paint device that records and replays QPainter commands."
[00:24] <apachelogger> that does not sound like you want that :P
[00:25]  * Quintasan hugs apachelogger
[00:25] <Quintasan> works
[00:25] <Quintasan> :DDD
[00:26] <Quintasan> argh
[00:27] <Quintasan> apachelogger: one more thing
[00:27] <Quintasan> apachelogger: void TrollFace::Troll()
[00:27] <Quintasan> apachelogger: when I put there trollImage->show(); and then click on the button the whole app segfaults
[00:27] <Quintasan> :S
[00:31] <apachelogger> ohm
[00:35] <apachelogger> ah
[00:35] <apachelogger> uh
[00:35] <apachelogger> lol
[00:35] <apachelogger> rofl
[00:35] <apachelogger> hahahha
[00:35]  * apachelogger needs to check something
[00:36] <apachelogger> ^^
[00:36] <apachelogger> well then
[00:36] <apachelogger> how do I put this
[00:36] <apachelogger> Quintasan: what would "QLabel *trollImage = new QLabel(this);" do?
[00:37] <apachelogger> outside the context of your app
[00:37] <apachelogger> in general
[00:37] <apachelogger> what would that line do
[00:37] <Quintasan> create a pointer to QLabel object with...
[00:37] <Quintasan> omfg
[00:37] <apachelogger> ah ^^
[00:37] <apachelogger> what scope does that object have :P
[00:38] <apachelogger> class scope?
[00:38] <Quintasan> :S
[00:38] <Quintasan> so what should I put as a parent in that constructor?
[00:38] <apachelogger> also mind the live time
[00:38] <apachelogger> see
[00:38] <apachelogger> trollImage = new QLabel(this);
[00:38] <apachelogger> !=
[00:38] <apachelogger> QLabel *trollImage = new QLabel(this);
[00:39] <apachelogger> with the former you asign the member pointer trollImage a QLabel object on the heap
[00:39] <apachelogger> with the latter you create an entirely new pointer of local scope and life time
[00:39] <apachelogger> the member however stays untouched
[00:39] <Quintasan> argh
[00:39] <apachelogger> and that is why you get a segfault, because obviously the member will point to some random junk
[00:40] <apachelogger> that said it would be much more sensible to initialize member pointers to 0 IMHO :P
[00:40] <Quintasan> apachelogger: I see it now :S
[00:40] <apachelogger> also makes tracking of the issue easier
[00:40] <apachelogger> if you init to 0
[00:40] <apachelogger> and then you get a segfault because you are trying to access 0
[00:40] <Quintasan> apachelogger: still, what I
[00:40] <apachelogger> well, then obivously the assignment went wrong
[00:41] <apachelogger> btw
[00:41] <apachelogger>     trollImage->setPixmap(QPixmap(":/img/troll.png"));
[00:41] <apachelogger> that is how I would load the pixmap ;)
[00:41] <apachelogger> + problemButton and trollImage need ot be parented
[00:42] <apachelogger> + IMHO you need to revise your member var names ;)
[00:42] <Quintasan> 4th time I ask this
[00:42] <apachelogger> + you will have to update the widget size once the image is shown
[00:42] <Quintasan> hngh
[00:42] <Quintasan> those are minor thng
[00:42] <Quintasan> crap
[00:42] <Quintasan> I'm having problems with typing :S
[00:43] <apachelogger> also, IMHO you should only create the qlable and load the pixmap in Troll()
[00:43] <apachelogger> otherwise it sits in mem for no good reason
[00:43] <Quintasan> apachelogger: Sput told me to parentize my widgets because I will not remember to delete them later, what should I use as the PARENT when I'm declaring things in CONSTRUCTOR?
[00:44] <apachelogger>     trollImage = new QLabel(this);
[00:44] <apachelogger> as per documentation there is this constructor that expects at first arg a pointer to a qwidget
[00:45] <apachelogger> since TrollFace's base class is QWidget, and since this is a builtin pointer you just use this
[00:45] <apachelogger> same for the qpushbutton
[00:45] <apachelogger>     problemButton = new QPushButton(tr("problemButton", "Problem, officer?"),
[00:45] <apachelogger>                                                  this);
[00:45] <apachelogger> oh, actuall
[00:45] <apachelogger> Quintasan: inside a qobject you can use tr() ;)
[00:45] <apachelogger> another intersting thing to remember
[00:46] <Quintasan> awesome
[00:46] <apachelogger> Quintasan: and finally ... you dont necessarily need to parent the members, but if you dont you need to create an appropriate dtor
[00:46] <Quintasan> dtor?
[00:46] <apachelogger> so usually you want to parent them ;)
[00:46] <apachelogger> Quintasan: destructor
[00:46] <Quintasan> oh
[00:46] <apachelogger> ctor = constructor; dtor = destructor
[00:47] <Quintasan> I still don't entirely get the "Trollface::Trollface(QWidget *parent) : QWidget(parent)" line
[00:47] <Quintasan> especially the : QWidget(parent)
[00:47] <apachelogger> you initialize a QWidget using the parent pointer you got
[00:48] <Quintasan> I understood like this
[00:49] <Quintasan> Trollface::Trollface(QWidget *parent) needs a pointer to QWidget, right? So we create a QWidget and pass it to Trollface :P
[00:49] <Quintasan> maybe that's why I don't get it somehow
[00:52] <Quintasan> apachelogger: http://www.cprogramming.com/tutorial/initialization-lists-c++.html is that what I'm looking for?
[00:52] <apachelogger> ehm
[00:52] <apachelogger> how do I put that
[00:53] <apachelogger> well
[00:53] <apachelogger> Quintasan: TrollFace _is a_ QWidget
[00:53] <apachelogger> right?
[00:53] <apachelogger> it is a special kind of QWidget, but still a QWidget
[00:53] <Quintasan> yeah
[00:54] <apachelogger> the idea of polymorphism is that you can address it as QWidget even though it is a specific QWidget
[00:54] <apachelogger> i.e. the QWidget is the base class of TrollFace
[00:54] <ScottK> Polymorphism makes my head hurt.
[00:55] <apachelogger> now the thing is, in order to work with TrollFace as if it were a QWidget (i.e. access it members and all) it needs its very own instance of QWidget
[00:55] <apachelogger> hm
[00:55] <apachelogger> imagine it like a matrjoschka
[00:56] <apachelogger> outside you have TrollFace, and inside is a QWidget
[00:56] <apachelogger> and IIRC inside the QWidget is a QObject
[00:56] <apachelogger> so you create a TrollFace and the TrollFace creates a QWidget and the QWidget creates a QObject
[00:56] <apachelogger> !
[00:56] <apachelogger> but
[00:57] <apachelogger> say you dont define no constructor
[00:57] <apachelogger> then the compiler will make a rather crappy one for you
[00:57] <apachelogger> called default ctor
[00:57] <imbrandon> dont define no :)
[00:57] <apachelogger> that thingy takes absolutely no arguments is the biggest crap evar
[00:58] <apachelogger> additionally that thingy will call the default ctor of QWidget
[00:58] <apachelogger> and so on
[00:58] <apachelogger> until everything is one way or another constructed
[00:58] <Quintasan> apachelogger: so and default constructor for TrollFace would be TrollFace() which calls QWidget() which calls QObject() and each and everyone is empty?
[00:59] <apachelogger> if you define a ctor but do not explictly initialize an instance of the base class as you do with : QWidget(parent) the compiler will still be fancy and automatically use the default ctor of QWidget
[00:59] <apachelogger> we do not want that
[00:59] <apachelogger> we want to allow ourselfs (or maybe a user of our class) to define a parent
[01:00] <apachelogger> i.e. maybe is trollface a child of another QWidget because TrollFace gest embedd in Amarok or something
[01:00] <apachelogger> so you implement a default constructor that can (but doesnt need to) access one argument
[01:00] <apachelogger> of the type QWidget*
[01:01] <apachelogger> now, earlier I said that a default ctor is one that does not accept nor arguments (<= imbrandon :P)
[01:01] <apachelogger> and this is archived by making 0 a default for that QWidget*
[01:02] <apachelogger> so if I want a TrollFace I can do TrollFace() or TrollFace(randomQWidget*)
[01:02] <apachelogger> both will use the same ctor
[01:02]  * Quintasan saves that for later
[01:03] <apachelogger> and in order to pass the latter on to the base of TrollFace (i.e. QWidget) we init QWidget ourselfs
[01:04] <apachelogger> finally please note that, would you not do that, the compiler would call QWidget() and you affectively would end up without parent, because the parent magic is implemented somewhere beyond QWidget, so since the compiler calls QWidget(), your base will not know anything about the parent...
[01:04] <apachelogger> if that makes any sense ^^
[01:04]  * apachelogger should have gone to bed 2 hours ago
[01:04] <apachelogger> o/
[01:04] <apachelogger> nini
[01:04] <Quintasan> nini
[01:04]  * Quintasan goes to bed too
[01:05] <apachelogger> Quintasan: oh, btw, the dtor will thanks to the same magic call the default dtor of the base class, so any memory the base class uses is freed again ;)
[01:05] <apachelogger> unless you use glib :P
[01:08] <Quintasan> apachelogger:  I don't get anything you say to me but it's because lack of sleep :P
[01:33] <ScottK> Tm_T: In ~75 minutes there will be new clamav packages in lucid-proposed.  Could you install them and verify clamav-daemon works (doesn't segfault on start)?
[01:33] <ScottK> It's a powerpc specific fix.
[01:38]  * genii slides Tm_T a super-caffeinated coffee
[01:44] <ScottK> Not a great rush in any case since it has to properly age in -proposed before it can move to -updates.
[02:55] <ScottK> nixternal: Done with powerpc for a while so you can turn it off again if you didn't already.
[03:41] <imbrandon> hum ok so i want to use a gst pipe in pyqt directly instead of phonon, anyone played with that ?
[03:48] <nixternal> http://www.gtmf.us/
[03:49] <nixternal> http://tinyurl.com/2fj6lzv
[03:50] <JontheEchidna> heh
[03:51] <imbrandon> nixternal: bleh
[03:51] <nixternal> I have always wanted to do that to someone
[03:51] <JontheEchidna> This is a personal favorite of mine: http://imagemacros.files.wordpress.com/2010/01/rtfm_noob.jpg
[03:51] <nixternal> finally, and go figure, it is the hillbilly that I get it with :)
[03:51] <nixternal> haha, nice
[03:52] <imbrandon> LOL
[03:53] <nixternal> wish my cycling clothes would hurry up and finish washing...i need sleep!
[04:11] <nixternal> and they are done...good night all!!!
[04:13] <ScottK> nixternal: You should probably 'dent your laundry status before you go to sleep.
[04:15] <imbrandon> lol
[04:48] <JontheEchidna> whoa, these are seriously neat: http://leogg.wordpress.com/2010/05/05/ubuntu-ids-2/
[05:53] <maco> JontheEchidna: ooh shiny
[07:11] <Tm_T> ScottK: will try
[07:12] <Tm_T> apachelogger: no I didn't have that dependency issue, I'm on 386
[07:20] <Tm_T> ScottK: starts just fine
[08:38] <agateau> apachelogger: ping
[08:47] <Tm_T> ScottK: and runs and stops fine
[08:50] <Tm_T> Riddell: http://www.kubuntu.org/news/kde-sc-4.4.3 gives 403
[08:50] <Tm_T> although it's mentioned in http://kde.org/info/4.4.3.php
[09:50] <Riddell> Tm_T: published now
[09:54] <Quintasan> \o
[09:55] <Tm_T> Riddell: thanks (:
[09:59] <Mamarok> hm, I still have 8 kdebase and plasma packages not updating,  do you have a ETOA for those packages?
[09:59] <Tm_T> Mamarok: amd64?
[10:00] <Mamarok> since those are kdebase, workspace and plasma-worksapce packages it seems rather essential...
[10:00] <Mamarok> yes, 64bit
[10:00] <Mamarok> but I have an Intel 64bit, why do you guys insist on calling it amd?
[10:01] <Tm_T> Mamarok: it's the architecture name
[10:01] <Tm_T> Mamarok: I think it's done under one hour now, https://edge.launchpad.net/~kubuntu-ppa/+archive/ppa/+build/1717912
[10:02] <Mamarok> finally :)
[10:02] <Riddell> I don't know why the buildds are so busy :(
[10:04] <Tm_T> i386  14 builders  1153 jobs (14 hours)
[10:04] <Tm_T> everybody updating their ppas to lucid era?
[10:05] <Mamarok> yeah, the week after release is usually heavy load
[10:06] <Mamarok> but why does that affect the building process?
[10:06] <Mamarok> and project PPAs should defnitely have higher priority over individual ones
[10:10] <Tm_T> should, yes
[10:18] <Tm_T> Mamarok: some 5 minutes now is my uneducated guess
[10:18] <Tm_T> as it's building docs now, almost done
[10:20] <Tm_T> ...if that log can be trusted
[10:47] <ghostcube> o/
[10:52] <Quintasan> ghostcube: hi there
[10:52]  * Quintasan is installing lucid on KVM to close some bugs
[10:53] <ghostcube> hi Quintasan :)
[11:11] <Quintasan> hey
[11:11] <Quintasan> WTF
[11:11] <Quintasan> Why slideshows on CD are not in Polish? I'm sure I have translated all of them.
[11:13] <dpm> Quintasan, did you finish the translations before the non-language-pack deadline -> https://wiki.ubuntu.com/LucidReleaseSchedule? As far as I know, all translations were exported from Launchpad and integrated into the package correctly
[11:15] <Quintasan> dpm: I'm pretty sure that I've done it before the deadline. Maybe I missed it because of timezones :P
[11:16] <Quintasan> dpm: well, it's not someone is going to cry but having the main title in Polish and then the rest in English looks sill
[11:16] <Quintasan> silly*
[11:17] <Quintasan> I'm still missing the words @_@
[11:19] <dpm> Quintasan, I fully agree, but the best thing now would be to investigate why that happened, so that it is not repeated. I'd suggest opening a bug against the Ubuntu Slideshow being as much detailed as possible (i.e. which particular strings are missing translations, if you did the translation before deadline, screenshots, etc.) -> https://bugs.launchpad.net/ubiquity-slideshow-ubuntu/+filebug
[11:31] <Quintasan> dpm: seems it's my fault
[11:31] <Quintasan> dpm: some translations were not accepted somehow in Launchpad
[11:38] <Quintasan> KPK is really useless
[11:46] <dpm> Quintasan, no worries. You might want to contact the Ubiquity Slideshow developers to ask them if they could be added perhaps in 10.04.1 once they are accepted. Btw, don't you have a translation mailing list to coordinate Polish translations and avoid these misunderstandings?
[11:47] <Quintasan> dpm: we have but most of the dudes do Ubuntu things and Kubuntu is left partly untranslated.
[11:47] <dpm> oh, I see :(
[11:47] <Quintasan> dpm: I can accept translations myself but I must've missed them or something went wrong
[11:48] <dpm> Quintasan, bummer. But yeah, get in touch with the Ubiquity Slideshow guys, as I say, perhaps they can be put in Kubuntu 10.04.1, since unfortunately those translations cannot be updated in language packs
[11:51] <apachelogger> agateau: pong
[11:51] <apachelogger> Tm_T: oh, k ^^
[11:51] <Tm_T> apachelogger: what did I do now?
[11:52] <Tm_T> apachelogger: oh, yeah, all is fine now both 386 and 64bit
[11:52] <Tm_T> or atleast should be
[11:57] <agateau> apachelogger: what's the status of the KDE client for U1?
[11:57] <agateau> apachelogger: (oh, and hi!)
[11:57] <apachelogger> agateau: in planing stage
[11:58] <agateau> apachelogger: ok, thanks
[13:30] <ofirk> Riddell: any news about the website?
[13:30] <Riddell> ofirk: no, sigh, I guess the sysadmins are at the UDS location already doing stuff there :(
[13:31] <Riddell> so I'll need to hassle them in person next week
[13:33] <ofirk> I am wondring, what is our relation with canonical? it seems that they don't care about kubuntu public relations
[13:34] <Riddell> to be fair, www.ubuntu.com hasn't changed either
[13:36] <ofirk> yeah, but that is because they weren't ready for the change
[13:37] <ofirk> we are ready
[13:45] <ScottK> Tm_T: Would you please comment in Bug #574906 on clamav working on powerpc.
[13:47] <ScottK> apachelogger: Would you please give us the benefit of your expertise in Bug #571286.
[13:47] <ScottK> Good $TIMEOFDAY everyone.
[13:47]  * apachelogger falls over
[13:47] <Riddell> Good 13:47 to you too ScottK
[13:47] <apachelogger> I should go get something to eat :P
[13:48] <ScottK> Riddell: How goes the battle against tryranny and foreign opression?
[13:49] <Riddell> the polling booths are open I hear, I'm due at the counting centre later tonight to make sure there's no corruption going on
[13:49] <apachelogger> oh my
[13:49] <apachelogger> 7 people want something from me
[13:50] <ScottK> apachelogger: Yes, but I pinged last, so by definition it's the most urgent.
[13:51] <apachelogger> interesting defintion
[13:51] <apachelogger> hm
[13:52] <ScottK> It's correct because it's the one that works best for me.  ;-)
[13:52] <apachelogger> ScottK: akonadi does use free-form addresses IIRC
[13:52] <Sput> and it worked, ScottK!
[13:52] <ScottK> apachelogger: Would you please check and say "It's good, bad, don't care" in the bug as applicable.
[13:52] <apachelogger> well
[13:53]  * apachelogger dislikes the idea of making fdo follow crap someone else invented for no good reason
[13:53] <apachelogger> gotta look into it a bit more though
[13:53] <ScottK> If that SRU goes in we'll be pretty much stuck with it.
[13:53] <ScottK> Thanks.
[13:54]  * ScottK was tempted to write "Web service bought a proprietary thing that's incompatible with FOSS is not on the list of allowed reasons for SRU", but refrained.
[13:55]  * apachelogger finds that sensible though :P
[13:55] <apachelogger> anyhow
[13:55] <apachelogger> just so I get this right
[13:55] <apachelogger> evolution uses free-form street field
[13:55] <apachelogger> so does the fdo spec
[13:55] <apachelogger> so does akonadi
[13:56] <apachelogger> so does legacy KDE stuff, which probably follows what vcd supports
[13:56] <Sput> ah yeah. good old U1 :>
[13:56]  * ScottK thought people would find it's absence in Kubuntu a feature and was a bit suprised to be found wrong.
[13:56] <apachelogger> and they are seriously proposing that we change all of that because they feel that using some prop crap is a viable option for a company that is supposed to make money using floss?
[13:57] <Sput> fwiw, afaik Akonadi's SyncML support use(d|s) Funambol as well
[13:58] <Sput> at least last year's GSoC project for SyncML support required libfunambol
[13:58] <ScottK> apachelogger: I don't mind if they use proprietary stuff in their server.  I do mind if they create a permanent diff between (K)(U)buntu and the rest of the world over it.
[13:58] <Sput> no idea if/hpw that relates :)
[13:59] <apachelogger> Sput: well, looking at akonadi alone it is no problem eitherway
[14:00] <Sput> apachelogger: yeah, but if the real reason for this behavior is phone syncing support...
[14:00] <ScottK> apachelogger: Will kmail consume the data either way?
[14:00] <apachelogger> because especialy in context of the couchdb resource definition @ fdo, the resource needs to map akonadi data to match the spec
[14:00] <apachelogger> ScottK: akonadi abstracts that pretty nicely, yes
[14:00]  * ScottK hopes this is going into the bug.
[14:00] <Tm_T> ScottK: will do
[14:01] <ScottK> Tm_T: Thanks.
[14:01] <apachelogger> Sput: that is reason to disobey an established standard?
[14:01] <freeflying> kmail should provide an option for not using akonadi as backend
[14:01] <apachelogger> maybe we should make ooo default to MS office doc format after all
[14:01] <freeflying> maybe more reasonable
[14:01] <apachelogger> seeing as it improves interoperability
[14:02] <apachelogger> oh oh oh
[14:02] <Sput> apachelogger: from reading the bug, the established standard has already been adapted :)
[14:02] <apachelogger> ScottK: I see trouble emerging eitherway
[14:02] <Tm_T> ScottK: is my comment sufficient?
[14:02] <ScottK> Sput: It's not clear if that's an adopted change or a proposed one.
[14:02] <apachelogger> so
[14:02] <Sput> ah. tenses.
[14:02] <apachelogger> we have address1
[14:02] <apachelogger> and address2
[14:03] <apachelogger> and the user creates an entry using both on a phone
[14:03] <ScottK> Tm_T: Fine.  Thanks.
[14:03] <apachelogger> so that gets synced into U1
[14:03] <apachelogger> from U1 we sync into akonadi
[14:03] <apachelogger> and now!!!
[14:03] <apachelogger> akonadi/kaddressbook uses free-form address data
[14:03] <apachelogger> so, either akonadi/kaddressbook is changing its behaviour
[14:04] <Sput> I was just wondering about how it'll work once Akonadi speaks with phones directly, disregarding U1 (and it'll probably use Funambol as well), in which case maybe adapting the standard to match reality wouldn't be that bad
[14:04] <apachelogger> OR the akonadi-couchdb resource needs to dump address2 (more like not add it to the akonadi entry)
[14:04] <ScottK> Seems to me more sensible for their web app thingy to be smart enough to convert free form address data to the format needed by funabol instead of imposing that on the user.
[14:05] <Sput> ... or that, if it can be done sensibly :)
[14:06] <apachelogger> well
[14:06] <apachelogger> IMHO the only solution here is
[14:06] <apachelogger> a) serverside abstracation, to somehow squeeze the client form-free address into funabol
[14:06] <apachelogger> or
[14:07] <apachelogger> b) get a revised version of vcard spec and implement that across floss to come up with a non-form-free addresss field
[14:07] <apachelogger> making every u1 client implementation follow funabol, just because they are too stupid and ugly to follow a freaking standard is just not sensible
[14:08] <Sput> as long as the standard isn't adapted to what appears to be reality (or not?), it's not
[14:09] <apachelogger> Sput: that funnyball is not reality
[14:09]  * apachelogger thinks vcard is much more established :P
[14:10]  * Sput wonders what SyncML does natively
[14:11] <Sput> "Any client that supports SyncML contact sync, MUST use vCard 2.1 to convey contact information."
[14:11] <Sput> that looks quite clear :)
[14:11] <Sput> that's from an Apple spec though :>
[14:12] <apachelogger> apple only knows the word MUST anyway :P
[14:12] <Sput> in any case, looks like SyncML uses vCard and vCal to exchange data, which is also the only sane thing to do
[14:12] <Sput> most notably is doesn't have address1 and address2
[14:14]  * apachelogger finds the couchdb-glib stuff increidbly confusing -.-
[14:15] <Sput> so yeah, I take back what I've speculated before and agree that the only sane thing to do is honoring existing well-established standards
[14:16] <apachelogger> hm
[14:17] <apachelogger> aha
[14:17] <apachelogger> http://library.gnome.org/devel/libebook/stable/EContact.html
[14:17] <apachelogger> apparently evolution does not use free-form streets
[14:17] <apachelogger> but also uses that street + ext stuff
[14:18] <Sput> that's what the guy said in the bug
[14:18] <apachelogger> oh, must have overread that
[14:18] <apachelogger> hm
[14:19] <apachelogger> interesting is that EContact dervies from EVCard
[14:20]  * apachelogger fires up evo
[14:22] <apachelogger> ehm
[14:22] <apachelogger> I dont get it
[14:23]  * apachelogger also finds that documentation rather useless
[14:23] <apachelogger> but in evo I have a free-form text field for the address
[14:23] <apachelogger> no clue where it gets ext from
[14:24] <Quintasan> wth
[14:24] <Quintasan> I'm getting disconnected all the time :S
[14:28] <ScottK> sebas: Reading kde-devel it seems it's time to have the "What version of Qt will KDE support with KDE SC 4.5" discussion.  I suspect we'll be going to 4.7 and most distros will too, so it'd be nice to have a discussion about it and get everyone in agreement.  I seriously never want to have to deal with the Qt 4.5/KDE 4.2 mismatch we had in Jaunty again.
[14:33] <Tm_T> ScottK: agreed
[14:38] <Tm_T> theres plenty of Qt 4.7 dependencies in trunk already
[14:38] <apachelogger> Sput: http://paste.ubuntu.com/428952/ anything youd add?
[14:40] <Sput> apachelogger: b) is weirdly put, also misses a verb
[14:41] <Sput> b) as far as we (that is me and a KDE gentoo developer) can see, akonadi will support phone sync via syncml (an established standard), and syncml enforces exchange of contact data via vCard (an established standard). (that said I wonder why the fdo spec cant implement vcard to begin with)
[14:41] <Sput> maybe?
[14:41] <apachelogger> bought
[14:42] <Sput> or "an even more established standard" :)
[14:42] <apachelogger> that sounds like fun ^^
[14:44] <Sput> also, all mail clients I know of support exchanging contact data via vCard, so do the groupware servers I know
[14:44] <Tm_T> even phones
[14:45] <sebas> ScottK: good point, let me think about that
[14:45] <ScottK> sebas: Thanks.
[14:45] <Sput> Tm_T: and phones.
[14:48] <Sput> now that I think about it, forcing the street information to be 1-2 fields makes no sense - there's address schemes that require more fields
[14:49] <apachelogger> as I understand it address1 is still free-form
[14:49] <apachelogger> just that ext is somehow supposed to enhance it
[14:49] <apachelogger> no clue how or for what
[14:49] <Sput> O_o
[14:49] <Sput> MAH BRAINZ!1!
[14:50] <apachelogger> kubotu: order brain for Sput
[14:50]  * kubotu shouts: OMG!!!!! RED ALERT! We lost a brain. Get me a medic, NOW!
[14:50] <apachelogger> !!!
[14:50] <apachelogger> omg
[14:50]  * apachelogger posts comment and starts reviewing some C code
[14:50] <ScottK> apachelogger: Thanks.
[14:51] <apachelogger> also I find it concerning how quickly they are on changing the spec
[14:51] <apachelogger> ...what if a company internally implemented that couchdb stuff using the spec...
[14:52] <ScottK> Right, well now's your chance to speak up.
[14:52]  * apachelogger adds that comment too
[14:52] <ScottK> Just be glad I decided to review that unaccepted queue yesterday for potential SRUs.
[14:52] <apachelogger> *nod*
[14:53] <apachelogger> kubotu: order cookie for ScottK
[14:53]  * kubotu slides one of world's finest cookies down the bar to ScottK.
[14:53] <ScottK> Thanks.
[14:55] <Sput> order steak for ScottK
[14:55] <Sput> kubotu: order steak for ScottK
[14:55]  * kubotu slides steak down the bar to ScottK
[14:55] <ScottK> hmmmm.  Steak for breakfast.  Wonderful.
[14:55]  * Quintasan hands ScottK a glass of water
[14:55] <Quintasan> You'll need it. :P
[14:56] <ScottK> Thanks, but I've got coffee brewing already (2nd pot)
[15:12] <rgreening> oh my... two more sleeps.. then no sleep for a week.
[15:12] <rgreening> :)
[15:13] <rgreening> I don't know how persia does it all year round. it's hard enough to stay up all night for one week, let alone 52 :P
[15:13]  * persia sleeps sometimes
[15:13] <rgreening> on the odd rare occaision...
[15:13] <rgreening> ;)
[15:18] <ScottK> apachelogger: I read your comments.  Thanks.
[15:28] <jussi> are any of the KC about?
[15:29] <rgreening> jussi: ya
[15:29] <rgreening> sup
[15:30] <jussi> rgreening: pm ->
[17:37]  * ScottK adds up http://design.canonical.com/2010/05/menu-bar/ and the number of Qt people coming to UDS and thinks distro patches for Qt.
[17:38] <Tm_T> hrrr
[17:38] <apachelogger> ohm
[17:38] <apachelogger> ok
[17:38] <apachelogger> it is getting silly
[17:38] <apachelogger> seriously
[17:39] <apachelogger> ubuntu is so innovative
[17:39] <apachelogger> look how they are ahead of windows in copying osx
[17:39] <apachelogger> that is so sad
[17:39]  * maco snorts
[17:39] <ulysses> some people said KDE copying Windows too
[17:39] <apachelogger> ehm
[17:39] <maco> i for one think win7's notifications are better than notify-osd
[17:40] <maco> and knotify
[17:40] <apachelogger> they accidently moved the buttons to the left
[17:40] <maco> because win7's are more like growl :P
[17:40] <apachelogger> and now they accidently make this move they invisioned for 30 years
[17:40] <apachelogger> and their wallpaper does not look like a osx one either
[17:40] <apachelogger> if ubuntu is not becoming one almost free osx clone, then I dont know what is going on
[17:41] <maco> apachelogger: hey does plasma desktop have a "slideshow" wallpaper setting?
[17:42] <apachelogger> maco: not by default I think
[17:42] <maco> i see gnome users in #ubuntu ask for a way to have the wallpaper change automatically. i /thought/ kde had that setting, but i know for-sure that windows does (which probably explains the sudden interest in that feature)
[17:45] <maco> wow, there's an ubuntu mirror at liberty university?
[17:45] <apachelogger> maco: I think that would only make plasma even crashier
[17:45] <apachelogger> so
[17:45] <apachelogger> now that I worked off the highlights I could probably go find something to eat
[17:46] <maco> internet says kde had it in 2005! hehe
[17:51] <ScottK> maco: There are things I like about notify-osd, but no actions and it getting behind make it unusable from my perspective.
[17:51] <ScottK> There are things I think could be better about KDE's too.
[17:51] <maco> win7 notifications come back from fading when you mouseover and they have actions. not multiple-button actions that ive seen but onclick()
[17:52] <maco> the thing i dont like in kde is the GIANT WALL when you get a bunch because they dont queue
[17:53] <ScottK> There needs to be something between the wall and one ... at .... a ... time ... no ... matter ... how ... long ... it ... takes.
[17:54] <ScottK> apachelogger: Don't worry.  Now that Android runs on iPhone, Apple will be busy sueing themselves.
[17:54] <JontheEchidna> the good news is that there's less of a wall in 4.5: http://www.youtube.com/watch?v=1Z31MLWMOuU
[17:56] <ScottK> JontheEchidna: Nice.  Progress at least.
[17:56] <JontheEchidna> I doubt notify-osd will ever progress much
[17:56] <ScottK> Now if only recently completed jobs wouldn't pop back up with new notifications, we'd be getting somewhere.
[17:57] <JontheEchidna> Help us obi-wan kenobi, you're our only hope
[17:57] <ScottK> BTW, that recent notifications thing is the doom of using persistent notifications for updates availalbe and restart required.  If you cancel it, those go away.
[17:57] <Sput> maco: in KDE trunk, the notifications don't stack up anymore
[17:58] <Sput> generally, the whole notification thing has been muchly improved with the new notifier
[17:58] <ScottK> So the persistent notifications are not at all persistent in the traditional sense.
[17:58] <ScottK> Cool.
[17:58] <JontheEchidna> In that they aren't monoliths constantly presenting themselves, yes
[17:58] <maco> yay!
[17:58] <Sput> hmmm... don't they still hake the (i) show a number?
[17:58] <Sput> and when you click on it, they pop up again?
[17:59] <ScottK> Sput: Nope.  They are gone (at least in 4.4)
[18:01] <ScottK> apachelogger: You got more noise to deal with in that bug.
[18:02] <Sput> ScottK: humm. I need to check that out.
[18:06] <maco> oh wow
[18:06] <maco> installing kubuntu in vmware, vmware asks for user/pass/fullname and then just boots straight to the "installing system" part of the installer O_O
[18:06] <JontheEchidna> apachelogger: you got mentioned in a dot.kde.org story
[18:08] <ScottK> JontheEchidna: Which one?
[18:09] <JontheEchidna> The choqok one, at the top
[18:09]  * ScottK looks again
[18:10] <ScottK> Right.  There it is.
[18:23] <maco> hm well *this* is problematic
[18:23] <maco> so any of you tried lucid in a vmware vm yet?
[18:24] <maco> kdm is taking no keyboard input whatsoever. text login works fine though
[18:29] <maco> ScottK: check this out 2010
[18:29] <maco> er
[18:29] <maco> copy and paste in windows is weird
[18:29] <maco> http://newcolumbiaheights.blogspot.com/2010/05/scooter-commuter.html
[19:02] <apachelogger> Sput: any opinoins on the noise, Ill not get to reply until tomorrow I suppose
[19:03] <apachelogger> JontheEchidna: cool
[19:03]  * apachelogger is famous again ^^
[19:28] <maco> how do i get an onscreen keyboard on kdm?
[19:42] <pascalFR> humm kde SC 4.4.3 works again ;)
[20:08] <apachelogger> maco: I think kvkbd's readme explains
[20:12] <maco> apachelogger: ossi says need 4.5 or to modify Xsetup scripts
[20:12] <maco> however i found http://communities.vmware.com/thread/261454
[20:13] <rgreening> that would be cool. I need Ubuntu with that for my Archos 5it touch screen
[21:08] <maco> goodness, you all weren't kidding about big kubuntu fonts
[21:09] <maco> (at uds barcelona, when someone... a few of you.... were saying theyre huge and that its Riddell's thing to have huge fonts)
[21:09] <maco> first time ive looked at a clean install in a while
[21:11] <JontheEchidna> I always bump all of them down one notch, but I believe we're following upstream in this regard
[21:39] <maco> JontheEchidna: i just changed the dpi and that helped though it seems 96 and 120 are the only options. my screen is 94
[23:11] <ari-tczew> could someone check enforceability of change in package cmake? I want to drop it because this change is involve to upgrading from jaunty to lucid, but we're tracking now maverick development. more info on https://launchpad.net/ubuntu/+source/cmake/2.8.0-5ubuntu1
[23:19] <JontheEchidna> I don't think I would have personally been so forgiving to people who tried the upgrade :P
[23:23] <ari-tczew> JontheEchidna: so to drop, or not to drop? :>
[23:23] <JontheEchidna> I'd drop it
[23:23] <ari-tczew> I'd like to drop, because I think that this is not necessary change
[23:24] <JontheEchidna> Not worth the diff with debian imo