shadeslayeranyone around? :D00:16
shadeslayerapachelogger: ok, so that parser is complete, just one problem, DTSTART and DEND don't work for some reason00:19
shadeslayerplz fix00:19
shadeslayerapachelogger: QDateTime issue fixed as well00:44
shadeslayeryer parser is ready00:44
shadeslayernight guys00:45
* afiestas is close to tarball // tag 1.2.100:57
afiestastogether with a patch for libbluedevil (one line patch)00:57
Quintasanshadeslayer: http://vladimirputin.soup.io/post/154482096/Image07:16
valoriebooooooo Quintasan!07:26
apacheloggershadeslayer: woohoo, if you give me access I can improve it a bit :P10:20
* apachelogger only got up so did not yet look at it in detail10:20
shadeslayerapachelogger: you already have10:52
apacheloggershadeslayer: btw     Q_ASSERT(iCalFile->open(QIODevice::ReadOnly | QIODevice::Text));  I'd not call the thing a library with something like that :P10:52
shadeslayerapachelogger: there's one thing that needs doing, handling \n characters at the end of a descriptio10:52
shadeslayerapachelogger: huh? why not? ( i'm relatively new to library development )10:53
apacheloggershadeslayer: because a library must never ever go down10:53
apacheloggerunless there is an issue that it can definitely not prevent or recover from10:53
apacheloggerI mean, for internal libs it makes no difference but for public shared ones it does10:54
shadeslayerbah, that \n is for vjournal10:54
shadeslayerso nvm that :P10:55
apacheloggereven so10:55
apacheloggerreadline would simply come up with an empty line10:55
apacheloggershadeslayer: another thing: it is very uncommon to do all the work in the ctor10:55
apacheloggershadeslayer: one would provide a static function for that most of the time10:56
shadeslayerok, we could just move stuff into a static function10:56
apacheloggerplus we need that anyway since I also need a ctor for QBA10:56
apacheloggeronly the on-disk cache is read from file, incoming updates form remote are processed from the networkreply directly10:57
apacheloggershadeslayer: qbytearray10:57
shadeslayerah ok10:57
shadeslayerah kewl10:57
shadeslayerQuintasan: hahah :D10:57
apacheloggershadeslayer: so, two options... a) one ctor and multiple parse(QFile), parse(QBA) ... b) multiple ctor and one parse10:58
apacheloggerformer seems bettar10:58
apacheloggerQuintasan: ping10:58
Quintasanapachelogger: pong10:58
shadeslayerapachelogger: btw how fast is this yer device10:58
apacheloggershadeslayer: what device?10:59
shadeslayerapachelogger: N95010:59
apacheloggerwhat kind of fast?10:59
shadeslayerhow fast does it process the ical file10:59
shadeslayerbecause it was insanely fast on my machine10:59
shadeslayerbut since we need it to be fast on a ARM device ...10:59
apacheloggerparsing is not so much the problem...11:00
apacheloggerproblem is that currently I have multiple lists which in JS means multiple memcopies11:00
apacheloggerIIRC the main oneiric ical had something like 220 sessions11:01
apacheloggerso that means like 3*220 memcopies or so11:01
apacheloggerand memcopies are evil!11:01
apacheloggereven so it only hung for like 1 second11:02
apacheloggerso for ondisk cache reads actually starting the app is slower than parsing11:02
apacheloggerand for remote updates the actual file transfer was slower than parsing11:02
shadeslayerapachelogger:  btw is the QBA going to contain the entire iCal starting with BEGIN: VEVENT ... or just one particular field like DESCRIPTION11:03
apacheloggershadeslayer: the ical as read from UDS11:03
apacheloggeryour parser will trip over that11:03
apacheloggerical files have a sort of manifest section before the first event11:04
shadeslayerapachelogger: i ignore that :P11:05
apacheloggeroh yeah11:06
apacheloggersorry misread the code there11:06
shadeslayeralthough i shouldn't, but seeing how i couldn't figure out what i should do with that, i left them11:06
apacheloggerbad code...11:06
apacheloggerI shall refactor :P11:06
shadeslayerfeel free too :P11:06
apacheloggershadeslayer: you should const the read line IMHO11:06
apacheloggermore compiler love + no changes by accident11:06
shadeslayerhmm ... yeah, we don't want to change the values11:06
shadeslayerapachelogger: are you  refactoring the entire thing right now?11:07
shadeslayeralright i'll wait for you to push yer changes11:08
apacheloggershadeslayer: another thing ...the event class is likely to be derived, whereas the parser is less likely to11:09
Quintasanshadeslayer: Any news about the touchpad or I missed it?11:09
apacheloggerso former needs a virtual dtor and latter does not11:09
shadeslayerQuintasan: nothing so far11:09
shadeslayerQuintasan: they're going to take some time and i'm pretty sure it won't be available before another month11:10
shadeslayerand as soon as they make it available its going to be gone11:10
shadeslayerthey've said they can't even gurantee pricing11:10
shadeslayerwtf dbus is taking all my cores11:11
apacheloggershadeslayer: some thought on formartting btw ... functions always before members in the header11:11
shadeslayeri'll keep that in mind :)11:12
shadeslayerapachelogger: does the event even require a dtor?11:13
shadeslayeri'm not allocating memory manually anywhere in the event , which is why i didn't have a dtor there11:13
apacheloggershadeslayer: a library class *always* needs a dtor :P11:14
shadeslayereven if its empty? :P11:14
apacheloggerthe compiler has free hand at where he puts the dtor and what it makes of it11:14
apacheloggerif you do not declare a dtor the compiler might make a virtual one because one of your classes derives the class internally11:15
apacheloggersuddenly stuff starts segfaulting for no apparent reason11:15
shadeslayerapachelogger: we could make it a bit more faster by using  continue in parseICalBlock11:18
shadeslayeras soon as it finds the field, it sets stuff in the event and then proceeds to the next line instead of checking it again11:19
apacheloggershadeslayer: you should fix your copyright line btw :P11:22
apacheloggereverywhere, year misisng11:24
shadeslayerah 11:24
apacheloggerthat loop needs help11:27
shadeslayerdone 11:27
apachelogger        } else if (line.startsWith(QLatin1String("DTSTART:"))){11:27
apachelogger           event->setStartDate(QDateTime::fromString(line, "'DTSTART:'yyyyMMdd'T'hhmmss'Z'"));11:27
apacheloggerformatting fail :P11:27
shadeslayeryes? what about it?11:27
apacheloggerget a proper editor 11:27
shadeslayeri'm using qtcreator11:27
apacheloggerlearn to use it then11:27
shadeslayerheh :P11:28
apacheloggerthat loop needs to go away11:29
apachelogger1 if that checks for dtstart, dtend and categories, any other value that is end:vevent is then parsed as key:value and insertered into the property map11:30
apacheloggerthat said11:30
apacheloggerinstead of having hard coded properties the event should probably use a property map11:30
apacheloggerso it is easily enhancable11:30
shadeslayeryou broke something11:37
shadeslayeri can't parser anymore11:37
shadeslayer[~/projects/libqcalparser/build]$ ./qcalparser /tmp/uds-p.ical 11:37
shadeslayer[~/projects/libqcalparser/build]$ 11:37
apacheloggeryour library was badly designed11:38
apachelogger    QCalParser *parser = new QCalParser(file);11:38
apacheloggerthat now passes for QCalParser(QObject*)11:38
shadeslayerah ok11:38
apacheloggerso you need to change that to construct and then parse11:39
apacheloggershadeslayer: how do we do property management?11:39
shadeslayerapachelogger: QVariantMaps ?11:39
apachelogger2 options: dynamic property injection via QtMetaObject OR QVariantMap11:39
shadeslayerbecause QML has better support for QVariants than other Qt classes i hear11:39
apacheloggerformer is again bettar11:39
apacheloggershadeslayer: qml also expects properties11:39
apacheloggerso if we use a QVM we need to manually declare the properties in the header still11:40
apacheloggerwe need to declare them and write getters11:40
apacheloggerso dynamic injection via the metaobject might in fact be the only sane solution11:40
* apachelogger tests this for a bit11:41
* shadeslayer tries to understand what apachelogger just said11:41
apacheloggerI'll show you code :P11:41
shadeslayerthat would actually be better :P11:41
apacheloggershadeslayer: http://paste.kde.org/123079/11:43
apacheloggerthe qtmetaobject of the qobject already has a QVM for the properties11:43
apacheloggerso you can inject new properties by simply setting a new property11:43
apacheloggerwithout having to declare ANYTHING11:43
apacheloggerevery time I tell people about this a jahava kitten dies11:44
shadeslayerapachelogger: so, we just inject new properties in our QCalEvent11:45
shadeslayerwhen the setters are called11:46
shadeslayerand change getters to return that property11:46
apacheloggerif it were working :O11:48
shadeslayerits not ? :O11:49
apacheloggernot in qml11:49
shadeslayeraw :(11:49
* apachelogger tries to debug11:52
apacheloggerNote that dynamic properties are added on a per instance basis, i.e., they are added to QObject, not QMetaObject.11:59
apacheloggershadeslayer: so we can use the dynamic properties, but we still need to provide Q_PROPERTY macros and reader functions12:00
apachelogger(latter can be put into a macro too though12:00
apacheloggerwe could write our own metaobject which allows for this use case ^^12:01
apacheloggershadeslayer: we could just not use properties12:03
apacheloggerQ_INVOKABLE QVariant getValue(QString key)12:04
apacheloggerscratch the get12:04
* apachelogger has used too much crappy qtmobility api12:04
shadeslayerapachelogger: and we could just reuse the current API to deal with that12:04
apacheloggerdeal with what?12:05
apacheloggershadeslayer: we'd still setProperty()12:05
shadeslayerQ_INVOKABLE QVariant getValue(QString key)12:05
apacheloggeronly that we provide a Q_INVOKABLE which gives access12:05
shadeslayeri get it12:05
apacheloggerQ_INVOKABLE QVariant value(QString key) { return getProperty(key); }12:05
* apachelogger did it again12:05
shadeslayerdid i mention KCombBox is weird12:07
apacheloggerbecause of the K12:07
apacheloggershadeslayer: well, make a choice on the event matter... either is fine with me12:07
apacheloggeractually having Q_PROPERTY hardcoded props allows for easier use in qml as qtcreator will autocomplete ^^12:08
apacheloggerfor ultimate scalability one will need a value() function anyway12:08
shadeslayerok, lets go with Q_PROPERTY then12:08
apacheloggershadeslayer: btw     QDateTime eventStartDate();12:12
apacheloggerthat is a C func name, not a cpp one :P12:12
apacheloggerQDateTime startDate()12:13
apacheloggerwe know that it is a event because it is an Event class :P12:13
shadeslayerah heh12:13
apacheloggerthat reminds me12:13
apacheloggershadeslayer: scope is broken there12:13
apacheloggerthe event is held by the parser12:13
shadeslayeri think everything is currently using eventFoo 12:13
apacheloggeryeah, well, fixing12:14
shadeslayerheh :P12:14
apachelogger    Q_PROPERTY(QDateTime dtStart READ dtStart)12:14
apachelogger    QDateTime dtStart() const { return getProperty("DTSTART"); }12:14
apacheloggersomething is not cool about this12:15
shadeslayerthat does not look right12:15
shadeslayerlooks weird tbh12:16
apacheloggerbut why?12:16
shadeslayerhow does it know to return the dtStart property 12:16
shadeslayerwhen we call it with getProperty("DTSTART")12:17
apacheloggerdoesnt work12:35
apacheloggerno idea why12:35
apacheloggerit works for a qstring but not for a datetime12:35
apacheloggerthis sucks12:37
apacheloggershadeslayer: so either we make our own QVM OR we create our own metaobject which allows this stuff OR we simply do not use Q_PROPERTY12:37
apacheloggeractually, this is a bit weird12:38
shadeslayeryou could return a datetime string12:38
apacheloggerno, I need actual date objects in qml12:38
shadeslayerQML can parse thos?12:39
apacheloggerfor no good reason12:39
* apachelogger tries with own QVM12:43
shadeslayeri'll bbl12:45
apacheloggerI know what is wrong12:46
* apachelogger is a bad maco coder12:47
apacheloggerworky worky \o/12:47
debfxfabo: Check_for_buffer_overflow_in_Lookup_MarkMarkPos_CVE-2011-3193.patch is already part of qt 4.7.412:55
ubottu** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3193)12:56
shadeslayerapachelogger: new API done?13:45
shadeslayerand/or want my help?13:45
apacheloggerrewriting parseBlock righ tnow13:46
apacheloggerQString is a right PITA 13:46
shadeslayerwhat s the problem with parseBlock13:46
shadeslayeror are you changing it to use the new API13:47
apacheloggernew api13:49
shadeslayerthat is wrong13:50
shadeslayer            event->setProperty(key, QDateTime::fromString(value, "'DTSTART:'yyyyMMdd'T'hhmmss'Z'"));13:51
shadeslayerwhat about poor DTEND13:51
shadeslayeryour forgot about him13:51
shadeslayerotherwise ... this new API will handle other keys as well, awesome13:52
apacheloggershadeslayer: take a closer look at the if13:53
shadeslayeri did13:54
shadeslayerapachelogger: how would it work for DTEND13:54
apacheloggernow I see13:54
apacheloggeryour code was rubbish :P13:54
shadeslayerbut it worked :P13:54
apachelogger            event->setProperty(key, QDateTime::fromString(value, "yyyyMMdd'T'hhmmss'Z'"));13:54
shadeslayerwont work13:55
apacheloggeror maybe13:55
apacheloggershadeslayer: why not?13:55
shadeslayercuz you don't ignore DTSTART ... uh ... maybe it will13:55
shadeslayernot sure13:55
shadeslayerneed to look at docs again13:55
shadeslayerah ok, i understand now13:57
shadeslayerapachelogger: value is just the part after DTSTART: right?13:57
shadeslayernot the entire line itself13:57
apacheloggerhence there is a key and a vlue14:00
shadeslayerright, didn't read closely14:01
* shadeslayer should probably blog about the stuff he did over the weekend14:01
* apachelogger thinks he is happy with the event now14:33
apacheloggershadeslayer: pushd14:36
apacheloggerplease have a look 14:36
nikolahi kubuntu devs. gtk2-engines-oxygen doesn't work for all gtk apps in oneiric. please fix it :)14:51
shadeslayerapachelogger: looks good, but, you don't need #include <QtCore/QDebug> in qcalparser.cpp14:51
apacheloggeryeah, noticed that14:51
shadeslayernikola: got a patch?14:51
apacheloggermore worrying is that it does not work14:51
nikolabugreport: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/85326414:51
ubottuUbuntu bug 853264 in gtk2-engines-oxygen (Ubuntu) "gtk2-engines-oxygen doesn't work for all gtk apps " [Undecided,New]14:51
nikolashadeslayer: no sorry14:51
shadeslayerapachelogger: it doesn't work?14:52
apacheloggerI get an undefined qlist in qml14:52
shadeslayermaybe we need to export our QCalEvent as a property or sth?14:53
shadeslayerso that QML recognises it14:53
apacheloggereven when I just use a qobject14:53
apacheloggerfile:///home/me/src/git/uds-build-desktop-Qt_4_7_4__System__Release/src/qml/ubuntudevelopersummit/main.qml:65: TypeError: Result of expression 'model[0]' [undefined] is not an object.14:54
apachelogger"A list of QObject* values can also be used as a model. A QList<QObject*> provides the properties of the objects in the list as roles."14:56
shadeslayerpossibly different versions of documentation ?14:57
apacheloggerI have been using qobj* list before14:57
apacheloggermost confusing14:58
shadeslayerapachelogger: btw instead of using a deliminatorPosition we could also use QString::section15:00
shadeslayerno point, i'm just saying :)15:02
apacheloggerI mean, section() has to seek the string to find the seperator and consequently a section15:03
shadeslayerand, shouldn't that be a QLatin1Char15:03
apacheloggerso since we need lhs and rhs it makes more sense to find the seperator position within the string15:03
apacheloggerand then take everything left and right of that15:04
apachelogger(since we know the exact position of seperator qstring will not have to seek for the seperator anymore)15:04
apacheloggerI think qml is just bugged again15:06
shadeslayerapachelogger: use a C++ backend to set data in the QML app?15:07
apacheloggerI am emitting it15:07
shadeslayerusing setContextProperty or whatever15:07
apacheloggerand apparently qml it to stupid to convert to declarative type in a handler15:07
apacheloggershadeslayer: setcontextproperty? what is this? kindergarten?15:07
apacheloggeryou do not set stuff like that as a context property15:08
apacheloggera KDE i18n handler you could set ther15:08
shadeslayerheh :P15:08
apacheloggershadeslayer: I think I know what to do15:19
apacheloggerbut first I need a break15:19
shadeslayeri'm off to dinner myself15:19
shadeslayerapachelogger: oh btw, one thing that we can extract form the ical file is the time zone15:20
shadeslayerthere's a field for that in the  15:21
=== yofel_ is now known as yofel
shadeslayerapachelogger: upload digikam already15:52
ScottKdebfx: There were two security issues that fabo was working on.  One is already fixed in 4.7.4, the other is not.15:54
shadeslayerapachelogger: see email if you're around16:20
apacheloggerI am at war16:21
shadeslayerapachelogger: just do it16:21
apacheloggerwhat mail16:22
apacheloggerYour Amazon.co.uk order has dispatched 16:22
apacheloggershadeslayer: how did you know that? :O16:22
shadeslayernot that16:22
shadeslayerapachelogger: see the one from wordpress16:23
* shadeslayer needs to start prepping for his US visa16:23
apacheloggerthat must wait16:24
apacheloggerbecause I need booze16:24
* shadeslayer switches apachelogger's booze with coffee16:24
apacheloggerSTUPID qdeclarativelistproperty16:25
apacheloggercant use qsharedpointers16:27
Quintasanapachelogger:  That's why I find school absolutely exasparating. I just learned we have a test on thermodynamics tomorrow16:29
QuintasanI mean what the f...16:29
apacheloggerI do not even know what that is16:29
* apachelogger wonders if one could store it in a sharedpointer so he does not need to know about it16:29
QuintasanNot really16:30
apacheloggerdang me running16:30
QuintasanIt's basically useless info so I am not entirely sure why would you want to store it anywhere16:30
shadeslayerQuintasan: up for reviewing me blog post?16:30
Quintasanshadeslayer: Send it this way, might take a break as well16:30
apacheloggershadeslayer: so.... I think I will have to do major refcktoring of the uds app to accomodate qcal16:31
shadeslayerQuintasan: alright16:31
apacheloggerparticularly to add threading into the picture16:31
apacheloggeroh it makes me sweat already16:31
shadeslayerQuintasan: done16:31
shadeslayerapachelogger: threading in QML ?16:31
* Quintasan goes reading16:31
apacheloggerbut no16:31
shadeslayerare you shitting me16:31
apacheloggerin cpp16:31
shadeslayerah ok16:31
shadeslayerthat makes sense16:31
apacheloggerthe data retrieval and storage becomes thread0red16:32
shadeslayerthreading in QML would probably make my mind implode16:32
apacheloggerQuintasan: so, actually thermodynamics is a very important thing16:32
apacheloggerif you have too fast intercourse you can start a fire, and no one wants that16:33
apacheloggerso I consider it in everyones interest that everyone knows about this and consequently does not cause accidential fires ever night16:33
shadeslayerQuintasan: also, review my digikam packaging at : https://code.launchpad.net/~rohangarg/kubuntu-packaging/digikam : if its alright, i'll upload to kubuntu-packaging and then someone can upload it16:33
apacheloggerit aint even merged16:33
apacheloggergood ld16:33
apacheloggerhowwas I supposed to do stuff16:34
shadeslayerapachelogger: you were supposed to review it, give me the OK and then i would i have pushed to kubuntu packagers :P16:34
apacheloggershadeslayer: you really want a different background for the presence screenshot16:34
apacheloggershadeslayer: did you do a merge proposal?16:34
shadeslayerapachelogger: hehe, i was thinking that too :P16:34
shadeslayerapachelogger: k i'll do that16:34
Quintasanshadeslayer: wptouch skin has broken feedback table :P16:36
Quintasan"i" should be uppercase when you are talking about yourself16:36
QuintasanAlso, use more sophisticated words so you sound cool and all intelectual16:36
QuintasanYou know, words like "splendid" or "superb" :P16:37
QuintasanThere is also "awesome" which can be used almost everywhere16:38
QuintasanAsk apachelogger if you don't believe in this one :P16:38
QuintasanOkay. I'm going back to physics16:39
shadeslayerhaha :D16:39
QuintasanSee you later or tomorrow, depending on results of my studying :P16:40
apacheloggersplendid comes right after fabulous16:40
apacheloggersuperb is when you cought a good bottle of wine16:40
apacheloggerwhich I did not16:40
* apachelogger gets whisky16:40
apacheloggerQuintasan: hf16:40
apacheloggerQuintasan: and remember the intercourse impact of it all16:40
shadeslayerapachelogger: review up16:41
* apachelogger wonders how to thread16:42
* shadeslayer hits publish16:51
muntiKubuwhich pkg has the add-apt-repository? tia17:06
muntiKubuapt-utils is installed but could not find command17:07
JontheEchidnamuntiKubu: dpkg -S add-apt-repository shows python-software-properties to be the package17:15
muntiKubuJontheEchidna: thanks17:15
bulldog98shadeslayer: where to find the telepathy-kde packages?17:33
* bulldog98 is doing some backporting17:35
bulldog98shadeslayer: what to install daily or stable?17:35
shadeslayerbulldog98: i use git master personally17:36
shadeslayeralong with neon17:36
bulldog98shadeslayer: oneiric or natty?17:39
bulldog98welcome in the club (I used it since development was opened)17:39
shadeslayersame here17:40
bulldog98nice :)17:41
bulldog98Quintasan: kde-config-telepathy-accounts-plugins : Depends: libkcmtelepathyaccounts4 (= 0.1.0+20110831-0~oneiric1) but 0.1.0+20110911-0~oneiric117:44
bulldog98shadeslayer: do you have the rights to add me to telepathy-kde?17:56
shadeslayernope, ask Quintasan 17:57
bulldog98Quintasan: could you please add me to the telepathy-kde group, so I can fix that?17:58
bulldog98btw why don’t we add kubuntu-members as default to that sort of groups?17:58
bulldog98or ninjas?17:59
* apachelogger ponder modelling18:00
apacheloggerbulldog98: more interesting why not use a kubuntu-ppa :P18:00
bulldog98apachelogger: for daily builds?18:00
apacheloggerwhy not?18:01
bulldog98we would end up having 200 PPAs for the dailys18:01
bulldog98apachelogger: I find it more convinient to have an group for that18:01
apacheloggerindefinitely less management overhead than all the rubbish teams growing out of each of launchpad's openings18:01
shadeslayerlol ^^18:02
apacheloggershadeslayer: hooray it is working18:05
apacheloggeralthough it all turned into a super hack18:05
apacheloggergood lawd18:05
apacheloggereven my qmake files are all messed up18:05
shadeslayerapachelogger: btw you forgot a continue18:08
shadeslayerin the parser18:08
shadeslayerfor CATEGORIES18:08
bulldog98apachelogger: maybe an kubuntu-dailybuilds would do?18:08
shadeslayeractually .. nvm18:09
shadeslayerapachelogger: whats the problem with QML and QList<QObject*> ?18:12
apacheloggeryou need to wrap it into a qdeclarativelistproperty18:13
apacheloggerfor which you need a qlist<T*> or you will get screwed over by having to implement qdeclarative stuff yourself18:13
apacheloggerincidentially enough that means one cannot use qsharedpointer which is usually a good idea for the stinky pim data18:14
* apachelogger sighs a bit18:30
shadeslayerapachelogger: btw see pm 18:33
apacheloggerno pm I have18:33
shadeslayeri sent it a couple of hours agon18:33
apacheloggerI probably saw and ignored it then :P18:33
BarkingFishyoda, you are?18:33
apacheloggerat times I am18:34
shadeslayerat times he's just apachelogger18:34
apacheloggergood scope18:35
apacheloggershadeslayer: this no qsharedpointer stuff is nothing but trouble18:35
shadeslayerapachelogger: we could use DBus18:36
shadeslayeroh but QML doesn't do DBus18:36
apacheloggerhow would that fix antyhing?18:36
shadeslayercan't use dataengines as well18:36
apacheloggerhow would they fix anything?18:36
apachelogger"put random shit into your software until it stops crashing"?18:36
shadeslayerapachelogger: you could read data from a data engine into a QML plasmoid18:36
apacheloggershadeslayer: yeah, how does that help with scope?18:37
apacheloggerbecause a dataengine is really nothing but a fancy model18:37
apacheloggerthat said18:37
apacheloggercould use a model18:37
shadeslayerthe scope of QList<QCalEvent*> ?18:37
apacheloggerthat way the events could be held within the model and all would be good18:37
apacheloggershadeslayer: yes18:38
apacheloggerparitcularly the ptr18:38
apacheloggerit has undefined scope when being passed to the Q18:38
apacheloggerthen apachelogger in his infinite wisdom likes to run multiple updates at once which might change a model while being accessed18:39
apacheloggermodel being the list18:39
apacheloggerworse yet, unless I run compares on the events they need to be all wiped and redone inbetween updates18:40
apacheloggermaking all previous invalid up until the new model arrives18:40
apacheloggercontext omnomonom18:50
shadeslayerhey yofel19:03
shadeslayerback from vacation?19:03
shadeslayeryofel: great, go check my digikam merge :P19:03
yofeljust wondering how to add the archive version to my repo stat page. I could a) take it from apt-cache b) do the same but update apt-cache on every update (10min) c) fetch version from launchpad19:04
shadeslayeryofel: btw the bug number is wrong in your current changelog which is in bzr :P19:04
shadeslayeruse lp lib i'd say19:04
yofelshadeslayer: the FFe didn't yet exist back then. 2.0.0 does fix *that* bug too19:04
shadeslayeryofel: but isn't that a Qt bug or sth?19:05
yofelwould also be my favorite way, but I'm wondering how to do that fast enought since I need to combine bash + python19:05
yofelshadeslayer: well, not sure, at least it's fixed19:05
shadeslayeryofel: create a new language combining the 2 :P19:05
shadeslayerlike QML xD19:05
yofelcurrently the page is created by bash, and there's a python script to fetch the existing repositories from LP19:06
shadeslayeralso look at the poll i sent you, add/remove questions etc19:06
yofelnow I'm wondering if I shouldn't just rewrite the whole thing in python19:06
shadeslayeryofel: store the stuff you get from LP into a file and read it into bash?19:06
shadeslayerbug 781128 << qt4-x11 bug19:07
ubottuLaunchpad bug 781128 in qt4-x11 (Ubuntu) "Tip of the day is missing "Did you know..."" [Undecided,New] https://launchpad.net/bugs/78112819:07
yofelshadeslayer: yeah, which I'll probably do for now and rewrite it at some point19:07
shadeslayerwhich is weird19:07
yofelshadeslayer: ah, didn't see that, thanks19:07
shadeslayerSourcePackage: digikam19:07
shadeslayerah right apachelogger explains why19:07
* shadeslayer got confused for a second there19:08
apacheloggershadeslayer: ok, I think a model19:44
apacheloggerthis is getting way out of hand here19:45
apachelogger7 models19:45
apacheloggerfor 7 days19:45
apacheloggermodels being qlists again19:45
shadeslayerthat is maddness19:45
apacheloggerplus the scope issue is still there anyway19:45
* apachelogger waves fist19:45
* bulldog98 thinks he found the issue with icecc not supporting i386 client when building on amd64 for i38619:45
bulldog98I need a crosscompiler for that, I’m currently doing a package for that19:46
apacheloggershadeslayer: loading is rather instant now19:47
shadeslayerapachelogger: with 7 models?19:47
shadeslayerare  you sure? :P19:47
shadeslayerdid you thread them?19:47
apacheloggerthey only do points19:47
shadeslayerbut then there's no point of threading19:47
apacheloggeronly parsing is threaded19:47
shadeslayeryou only have a single core19:47
apacheloggerthe tearing apart into models is not19:47
apacheloggerwhich causes lockup for about 0.5 secs19:48
apacheloggershadeslayer: sure there is19:48
apacheloggerfancy systems like to put excess load onto the gpu19:48
apacheloggerat any rate the OS will have an easier job knowing what to schedule when if you have logical unit threads19:49
apacheloggerparsing is fast19:49
apacheloggershadeslayer: you are awesome19:49
shadeslayerthank you :)19:49
apacheloggershadeslayer: thanks!19:49
shadeslayerhehe :)19:49
shadeslayerapachelogger: you fixed up the rest of the stuff :P19:50
apacheloggerI pretty much broke the app19:50
apacheloggerworking copy of qcal in git should be good to go though19:50
* apachelogger did some minor changes apparenlty19:50
apacheloggerah yeah19:51
apacheloggerparse are slots now19:51
apacheloggerthough I cannot recall why I made them slots19:51
apacheloggermight be a bogus change19:51
apacheloggeror not, because they probably should be slots as they represent actions19:51
apacheloggeryou could create a parser, move it to a thread and then invokemethod parse on it19:51
shadeslayersounds right19:52
* apachelogger has put it into a qrunnable though as he has to do more stuff after/before parsing19:52
shadeslayerapachelogger: re write the QML from the ground up to suit the parser :P19:53
apacheloggernothing to be rewritten19:53
* apachelogger is a good software designer :P19:53
shadeslayerah, problem of scopes :P19:53
apacheloggerthe qml stuff knows no nothing about no parser19:53
apacheloggerit knows about a model provider19:53
apacheloggershadeslayer: I'll just have to migrate to a proper abstractitemmodel19:54
shadeslayer 42 files changed, 1689 insertions(+), 154 deletions(-)19:54
apacheloggerwhich ought to be supported in QML IIRC19:54
apacheloggereven better than qobject* models19:54
apacheloggerthen the qml items would not have to work with the pointers directly but only get the data from the model19:55
apacheloggerso the ptr scope is under control then19:55
apacheloggerplus I can get rid of the 7 models19:55
apacheloggershadeslayer: where is that from?19:55
shadeslayeryer git repo19:56
shadeslayeri hadn't updated 19:56
apacheloggerI also implemented the raw stuff for maemo5 :P19:56
* apachelogger looks up19:56
shadeslayerhaha i can see that19:56
apacheloggerI think my app is the only qml app on maemo5 that actually implements the stacked window system19:57
apacheloggeri.e. you can stack a window ontop of another window and the blue X in the top right corner turns into a back icon19:57
apacheloggertheir impl is entirely based on the window manager19:58
apacheloggercompletely horrible really19:58
apacheloggerI mean, not in Qt, but if you look at the GTK code necessary19:58
apacheloggerno idea how they ever thought that maemo would be a success19:58
apacheloggerdoctor who19:59
* apachelogger completely forgot19:59
apacheloggerquestion is20:01
apacheloggerwhat sort of model is my data20:01
* apachelogger always fails to asses this correctly20:01
shadeslayeri'm sleeping guys20:20
bulldog98apachelogger: what is the trivial way to get a cross compiler compiling for amd64 on i386?20:36
BarkingFishi know you can do it the other way round using a wrapper script, bulldog98 - whether it works backwards I don't know.21:12
BarkingFishthere's bits of info on debian's wiki21:12
bulldog98BarkingFish: main problem is that crosscompiler should be used in icecream21:13
bulldog98but thx anyway21:13
BarkingFishno problem21:13
BarkingFishsorry for butting in :)21:13
yofelbulldog98: icecc-build-native is what packages the compiler IIRC, can't you adjust that?21:15
yofelnot sure how it works21:16
bulldog98yofel: I looked into that but it’s some obscure stuff21:16
bulldog98and I don’t know if i386 gcc can build amd64 out of the box21:16
bulldog98seems like I have to rebuild binutils and gcc21:17
* bulldog98 will create i386 packages for crosscompiling to amd6421:17
* bulldog98 gives up, cause it’s to late to manage that stuff21:28
bulldog98I’ll build that stuff by hand21:28
bulldog98and not package an deb21:28
bulldog98apachelogger: how do I access the people.ubuntu.com page (I want to upload a icecc cross compile tarball)21:34
apacheloggergo there21:34
apacheloggerit tells you how21:34
bulldog98apachelogger: I get Permission denied (publickey). with the key that is register in lp since ever21:44
apacheloggermaybe not synced yet21:44
apacheloggeror you are in fact using the wrong key21:44
bulldog98apachelogger: that’s the key that works for pushing to lp, so it’s the right one21:45
apacheloggernot synced I guess21:45
apacheloggeror dolphin is broken21:45
apacheloggerI have seen weird key issues with sftp21:45
yofelbulldog98: using ssh or sftp? there's no shell on people.ubuntu.com21:55
bulldog98yofel: both22:01
apacheloggerditch the code from your knownhosts and try again22:03
apacheloggerwith sftp22:03
apacheloggerin dolphin22:03
apacheloggeras first try22:03
bulldog98it says something about timeout22:10
bulldog98sftp://people.ubuntu.com/~bulldog98/ is in my bar is that ok?22:11
bulldog98ah ok22:12
bulldog98still the same error message22:13
bulldog98hm ok works now strange22:15

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!