Plasma Meeting: Sat 9 Feb 2008

Topic The channel topic is "Plasma: KDE4 desktop, panel and application widgetry. Devel wiki @ http://techbase.kde.org/Projects/Plasma | Plasma IRC Meeting This Saturday - 13:00 UTC: http://techbase.kde.org/index.php?title=Projects/Plasma/20080209 | gobby server for the meeting: ruphy.org:5555".13:13
richmoore2http://techbase.kde.org/index.php?title=Projects/Plasma/20080209 <-- here is the agenda for those who've not read it13:13
aseigook, everyone here? jpwhiting: have you joinged the boggy document?13:13
aseigoer, gobby13:13
aseigooh, there's jpwhiting in the gobby doc, yes13:14
aseigorichmoore2: moin13:14
richmoore2hey aseigo13:14
Lurewill the chat go on in this channel or on gobby chat or both?13:16
aseigoLure: in here, but we use gobby to record the minutes and findings13:16
Chaniyay13:16
aseigook, let's get started if all is well13:16
Chanithis window is prettier :)13:17
Lureaseigo: good, as it is hard to follow two chat windows at once ;-)13:17
aseigoso i'd like to rip through the process bits as fast as possible so we can get to fun stuff (design)13:17
jpwhitingChani: yes, apparently those files are gone13:17
* aseigo was surprised when he logged into the gobby and it said someone was already using my pink =/13:17
annmaouch, sorry13:17
tmskeannma: I think I fixed it, i forgot to uncomment some lines13:17
spstarrlol13:17
jpwhitingno worries, I'll select everything and be able to see maybe...13:17
aseigo=)13:17
aseigoso...13:17
aseigofirst item: review board.13:17
Chaniaseigo: I wanted green, but there were several greens alerady in use13:18
spstarraseigo: funny thing is.. konversation ALWAYS makes you pink on my client13:18
aseigoshould we keep, it what's people's thoughts on it?13:18
aseigospstarr: see, it knjows13:18
annmatmske: yup, the config initialization ;)13:18
spstarrhaha13:18
richmoore2i think having the review board to collect patches is good, but it seems a bit slow13:18
Chanireview board. hrm.13:18
dirk|homeruphy: yes :)13:18
ruphyok :-)13:18
richmoore2is the host it's on on an adsl link or something?13:18
Chaniit's certainly a nice idea, I just get really annoyed at the web2.0 stuff and having to boot up firefox to use it13:19
richmoore2if so i could put it on my server (100 meg link)13:19
aseigorichmoore2: it's not so much that ... apparently mattr kicked over his apache last week and then it was really fast for a while13:19
ruphyrichmoore2: 100MB/s unlimited13:19
ChaniI like the python script13:19
aseigorichmoore2: i wonder if it is something to do with another app he's running, or if it is some brainddamage in r-b that starts bogging down?13:19
Chanithing is, review board is new, and needs a fair bit of work done on it.13:19
aseigoyes13:20
spstarryeah it seems slow ;/13:20
aseigoi'm not overly happy with the speed either, but then most of the review work is done client side13:20
Chaniare we gonna end up putting a lot of effort into review board to make it less annoying?13:20
aseigoand posting is done with the script13:20
ChaniI haven't noticed speed13:20
ChaniI'm too busy being annoye at the interface n'stuff :)13:20
aseigoChani: well, i don't have time / energy / desire for that.. i don't mind hacking on the post-review script here and there, but that's about it13:21
richmoore2i agreed that the interface could use some work too13:21
spstarrwe need like a 'gobby' patch reviewer13:21
* aseigo doesn't mind the interface, actually.13:21
spstarrwhere people can modify it :)13:21
ruphywell, I don't use the scripts, but think review-board is great13:21
aseigoheh.. oh lord =)13:21
Quit nihui has left this server (Read error: 104 (Connection reset by peer)).13:21
ruphyspstarr: I think we should try collaborative coding instead ;-)13:21
spstarrruphy: Kdevelop 4.x has this no?13:22
hardloopdirk|home: the patch fixed the problem. thanks again :)13:22
aseigoas long as its clear to everyone that it's for those non-totally-obvious patches to core things ... i do want to avoid bogging people down in process, but i think this is better than losing patches on the mailng list13:22
dirk|homehardloop: thanks. sorry for not getting around testing it13:22
richmoore2i've not seen how i can add a comment to a patch with iyt13:22
ChaniI like tossing things up on review board with hte python script, but after that I tend to let them rot there for a while...13:22
Join cgoncalves has joined this channel (n=carlos@cr-217-129-232-159.netvisao.pt).13:22
aseigorichmoore2: it doesnt'work in konqi, only firefox13:22
richmoore2aseigo: that could be the problem13:22
Chaniit is quite useful for seeing whta uncommitted patches are still around. I like not having to wonder about that13:23
jpwhitingrichmoore2: and you can only comment from the view that shows the diff also13:23
aseigorichmoore2: you view the diff, then you can click in the margin and add notes... then you click "review" and it gathers up all your notes for the various lines and you can provide a summary13:23
aseigorichmoore2: that part is *really* slick13:23
spstarraseigo: it doesnt seem to be Web 2.0 'enough'13:23
aseigoin fact, that's my favourite part of it: easy per-line or per-block annotation13:23
richmoore2cool, i've been using it as a patch viewer then using irc to give feedback so far13:24
ruphyyeah, for me too13:24
Chaniper-block?13:24
Chanihow do you do per block? I couldn't figure that out13:24
aseigoChani: you can click and drag in the margin to select multiple lines13:24
Chaniagh13:24
Chaniah13:24
aseigorichmoore2: ah.. hehe.. yeah, it's a little less fun that way ;)13:24
aseigospstarr: agreed...13:24
notmarti also have never discovered how to do per block (probably too lazy)13:24
Quit hardloop has left this server ("Verlassend").13:25
spstarraseigo: maybe define the use of the patch viewer to be for 'core' changes and or for new people to get their hands dirty in?13:25
aseigomaybe we should pop an email to them and see what their devel roadmap for r-b is, if nay13:25
ruphyok, so speed seem the only problem, right?13:25
Quit ereslibre has left this server (Remote closed the connection).13:25
spstarrsince you mentioned that a moment ago, i dont think people knew13:25
richmoore2aseigo: that sounds like a good plan13:25
dirk|homecan it send emails? does it have a rss feed?13:26
dirk|homeis it possible to script it via a rich client (e.g. a pyqt app?)13:26
spstarrrss feed would be really nice (then plasma can use it)13:26
annmait can send emails13:26
aseigoyeah, rss feeds would be very nice13:26
Join ereslibre has joined this channel (n=rafael@84.76.213.0).13:26
Chaniit already emails the list13:26
Chanithose emails seem to get kinda long sometimes13:27
annmaa bit too much13:27
dirk|homelynx cannot handle it at all though :)13:27
Join nihui has joined this channel (n=nihui@58.34.80.2).13:27
aseigodirk|home: it has a json interface13:27
annmaso there are things that would need to be fixed but do we want to keep using it?13:27
* ruphy says yea13:27
annmaI do13:27
aseigodirk|home: we already use a pythong cli script to post patches directly from the svn13:27
richmoore2i'd say yes13:27
jpwhitingI think so, yes13:28
Chaniyeah, it's certainly better than plain email13:28
annma5 for13:28
Topic spstarr sets the channel topic to "Plasma: KDE4 desktop, panel and application widgetry. Devel wiki @ http://techbase.kde.org/Projects/Plasma | Plasma IRC Meeting IN PROGRESS NOW - http://techbase.kde.org/index.php?title=Projects/Plasma/20080209 | gobby server for the meeting: ruphy.org:5555".13:28
ruphyany proposal for how to speed it up?13:28
aseigodirk|home: that in particular is *very* nice as i never have to touch a web browser to post a patch13:28
aseigomattr: ping?13:28
aseigooh, he's probably sleeping13:28
aseigobecause he's not insane like me ;)13:28
ruphy:P13:28
jpwhitingaseigo: yes, probably13:28
dirk|homewe could move it to a faster server though if anyone asks sysadmin@ I guess13:28
aseigoruphy: i'll bring that up with mattr13:28
ChaniI think I'm gonna get annoyed about all hte things that aren't done though. blah. especially since nobody has time/ability to make it work in other browsers13:28
richmoore2aseigo: is the lack of sleep cause or effect? :-)13:28
spstarrwell i went to sleep 2am and got up 8am :) so can mattr :P13:29
* aseigo notes that jpwhiting is similarly affected ;)13:29
jpwhitingaseigo: is he in our or even worse, west coast timezone?13:29
aseigorichmoore2: hm. that's a question best left unasked, i think ;)13:29
jpwhitingaseigo: luckily I'm a morning person13:29
aseigojpwhiting: texas.. so same13:29
ChaniI'm tempted to dig into this python script myself13:29
ruphynotmart: please, use a slightly less saturated and lighter color =)13:29
jpwhitingKO13:29
aseigoChani: it's not the most beautiful thing in the world.. but i've seen worse13:29
notmartruphy: ok :)13:29
ChaniI don't know much python, so the chances of me actually making it work better aren't high :)13:30
* ruphy encourages everyone to have a look at what he writes in the summary, from time to time ;-)13:30
ruphyChani: personally I'm more than happy with the web interface13:30
aseigopython is very straight forward.13:30
richmoore2ruphy: is there an export of some kind that is viewable without a gobby client?13:30
richmoore2you can pick up the basics of python in a hour or so13:30
* spstarr thinks konversation needs a gobby plugin :)13:30
Chaniaseigo: yeah, I've done a few little things and often it just worked how I wanted it to work13:30
ruphyrichmoore2: I can do that!13:31
spstarrthen you wouldn't need two chat areas13:31
ruphyprobably, wait a sec13:31
Join nogden has joined this channel (n=nick@p54993D2A.dip.t-dialin.net).13:31
aseigook... let's move on then.13:31
Chaniok13:31
aseigobackporting policy13:31
* aseigo is taking the easy topics first to get us rolling ;)13:31
ruphyrichmoore2: no, sorry... but for nex time I'll be able to do that =)13:31
aseigoruphy: that was your agenda item i think?13:31
richmoore2ruphy: ok, thanks13:32
richmoore2aseigo: next on the agenda was libplasma to kdelibs13:32
ruphyspstarr: if eveyone had a gobby client I would have suggested to just have the meeting there13:32
ruphyeasier13:32
ruphyaseigo: what makes you think that? ;-)13:32
spstarr:)13:32
aseigorichmoore2: yeah, i rearranged stuff13:32
aseigoruphy: heh.. it wasn't? =)13:33
ruphyno, well, I just want a policy defined, and maybe let's decide a list of features to be backported13:33
Join Riddell has joined this channel (i=jr@kde/jriddell).13:33
ruphyto me the things are:13:33
spstarrwell, no bic/abi changes would be the big one for backport changes :)13:33
jpwhitingand adding new strings13:34
jpwhitingno need to piss off translators ;-)13:34
richmoore2actually, i'd suggest we do a big backport immediately prior to adopting 4.413:34
ruphy- dashboard (+ the new animation)13:34
ruphy- panel config13:34
ruphy- systray (if it's not already)13:34
Beineriruphy: how about no "list of features to be backported" but some intermim Plasma release soon? :-)13:35
richmoore2Beineri: yes, that's what i'd prefer13:35
aseigorichmoore2: yes, that seems the least insane thing... however, it'll be harrd on translators, etc13:35
ruphyanything else?13:35
aseigoah, Beineri beat me to it13:35
jpwhitingand it's on the agenda ;-)13:35
ruphy- oh, and taskbar plasmoid improvements13:35
aseigohm, why don't we pull those two items together, because they do overlap13:35
rabaukeruphy: panel config seems to be already backported by opensuse13:35
aseigorabauke: but not to the branch, just to their patches really13:36
richmoore2rabauke: yes, it's in some distros but not in our svn13:36
ruphyexact13:36
aseigoright now backporting is easy: svn merge13:36
ruphyBeineri: that'd be cool, but actually this is more crucial =)13:36
ruphyBeineri: plus, it's BC13:36
aseigobut it's hard on translators, and it's not binary compat13:36
Beinerirabauke: well, panel config is for me also span optoin and amount of panels ;-)13:36
rabaukewell then use their patch13:36
ruphyaseigo: (for /me is easier... git-cherry-pick <commit-nr>) :D13:36
aseigo;)13:36
rabaukeBeineri: is that available in trunk?13:36
Beinerirabauke: and left/center/right13:36
richmoore2aseigo: i think having a single big day of pain rather than a drip feed would probably be better for them13:37
aseigorabauke: not yet13:37
richmoore2we'll be able to backport much less when we go to 4.413:37
ruphyagreed13:37
* aseigo notes he doesn't plan on copying kicker's left/center/right approach as it was very limiting...13:37
dirk|homewhen is the interim plasma release planned?13:37
rabaukeso there is no backporting possible yet... :) I was talking about the things that are already backported by someone and using those patches to get them into kde svn13:37
ruphyso, anyone has any other important feature to add to the backport list?13:37
dirk|homea week, a month? a quarter of a year?13:37
aseigorichmoore2: yes, one big day of pain would be better13:37
spstarryeah, i want my panel diagonal :P13:38
aseigodirk|home: we haven't gotten to that point on the agenda yet =)13:38
ruphy(in the taskbar improvements there's also the 2-rows layout thing)13:38
aseigooh... it would be more like this month13:38
Beineriruphy: some features have to exist first at all :-)13:38
aseigopersonally, i think backporting should be limited to important bug fixes13:38
ruphyBeineri: those do... the panel config is at least already decent =)13:38
ruphycontainments config and a plasma kcm would be great either, agreed13:38
ruphybut at least it's something13:39
randomguy3if we have an interim release, then we can limit backports13:39
aseigoi don't really want to see us spend too much time trying to do big feature merges.. both because of the time involved and that it rather violates the idea of the branch13:39
aseigoright13:39
ruphyagreed13:39
aseigoso.. interim release.13:39
aseigosomething that works with 4.0 libs13:39
ruphyrandomguy3: the only thing the worrries me a it is bc...13:39
Beinerifor me the interim release should have the basic features KDE 4.0.0 should have had actually13:39
aseigoit will require bundling up workspace/libs and workspace/plasma at a minimum13:39
Chanihmm. do we have stuff that would *not* work with 4.0?13:40
ruphyand, just backporting commits assures us that no BiC changes go in13:40
aseigoBeineri: an interim release can only have the features that are in trunk/ ;)13:40
aseigoChani: not yet, no13:40
Beineri(plus the backfixes like behaving plasmoid well with vertical panel and other than 48 point size)13:40
randomguy3something to consider for the interim release is that there are one or two applets in other modules that would break13:40
rabaukeChani: every clock that uses the new clock-lib13:41
dirk|homehow do you plan to make distros swallow an interim release?13:41
Beineriaseigo: in trunk at what time? :-)13:41
aseigopersonally, i'd like to see us do a release every 2 months or so .... even after we're out of this "feature critical" phase13:41
dirk|homeits the desktop shell itself..13:41
Chanirabauke: but te clock-lib would be part of hte interim release13:41
dirk|homepersonally, I'd like to see updates being pushed into 4.0.x (violating feature freeze) rather than done yet another way13:41
aseigodirk|home: i'm not sure i'm overly concerned about that.. should i be?13:41
dirk|homeaseigo: yes13:41
richmoore2aseigo: that's going to be hard if we're using woc instead of plasma::widgets13:41
ruphywhy 'only important bugfixes'? I'd say that the mofe bugfixes go in, the better13:41
rabaukeChani: ah ok, if that is the case they will, I thought you asked about curent 4.013:42
aseigodirk|home: the goal would be to simply make it easy for people to access the latest plasma...13:42
spstarrrichmoore: Plasma::Widgets aren't 'going away' they become legacy13:42
dirk|homeaseigo: because if the distributors cannot package it properly, users will have a problem getting/installing it, which means that in return you'll get a lot of bugreports13:42
Beineriaseigo: for me 4-6 weeks features work, and 2 weeks stabilizing would be fine if 4.0.3 has some string freeze lift eg13:42
dirk|homeaseigo: we have those monthly kde releases, anything easier than that? :)13:42
richmoore2spstarr: yes, but i suspect most applets etc. will switch pretty quickly13:42
notmartrichmoore2: i think all the important backportings should be done before qt4.2, after that it will be really painful13:42
aseigoruphy: important bugfixes are a sort of "must", while detail stuff is up to the time/effort/etc of the individual imho13:42
ruphydirk|home: agreed. and you have the problem of c++ plasmoids (almost all for now) and BC13:42
spstarryeah, they could, I already have begun the process :)13:42
randomguy3and if plasma-interim is BIC with the kget plasmoid in kdenetwork, for example, what do packagers do about that?13:43
dirk|homewell, binary compatibility gaines another dimension with another plasma release13:43
dirk|homebecause then it has to be checked against 4.0, 4.1 and that other branch13:43
dirk|homeor something like that13:43
aseigodirk|home: those are for branch, right? i'd love to see us do regular tarballs of trunk/ too, but am to afraid of the overhead that would cause to suggest it =)13:43
ruphyaseigo: ok, in case you need to backport something, just ask me, it's a one-liner for me to do that13:43
Lurerandomguy3: distros should rebuild (not an issue if they know that they have to)13:43
dirk|homeit also makes the release team look silly, because they're doing a hard time planning releases and releasing, and then thhhe core component of KDE just decides to go another way13:43
aseigorandomguy3: yes, that's the big rub indeed.13:44
dirk|homeaseigo: we're doing regular tarball releases of trunk!13:44
aseigodirk|home: ah, we are? that's great, i missed that somewhere...13:44
dirk|homeI guess I didn't blog about it :)13:44
randomguy3Lure: so distros would have to make a once-and-for-all choice, and this would assume no source incompatibility (which I'm not sure we can guantee)13:44
aseigodirk|home: hehe.. evidently not ;)13:44
randomguy3I think some symbols have already moved13:44
aseigorandomguy3: yes, they have13:45
ruphyrandomguy3: they do....13:45
dirk|homeI really need a secretary that knows how to blog13:45
Join jaguilera has joined this channel (n=opsi@unaffiliated/opsidao).13:45
aseigoBeineri: since the interim release was your agenda item, maybe you could say something about what you'd like to see (process-wise)13:45
randomguy3so we'd have kdenetwork-4.0.x is either incompatible with kdebase-workspace-4.0.x or with plasma-interim13:46
aseigodirk|home: oooh... now *that's* a good idea13:46
aseigorandomguy3: perhaps we could package up kget-interim along with plasma-interim...13:46
richmoore2aseigo: and kdeedu's applets?13:46
Beineriaseigo: backport of the most important features into some 4.0.x release? :-)13:46
randomguy3aseigo: and quickly get throttled by the packagers :-P13:47
notmartso if it's big there will be the need of a separate kdenetwork-plasma package, if it's source incompatible, well,.. :(13:47
dirk|homesorry, I missed the kget point?13:47
notmarts/big/bic13:47
dirk|homewhat is the issue with kget?13:47
randomguy3dirk|home: kget has a plasmoid in kdenetwork13:47
dirk|homeand thats a problem because..?13:47
rabaukedirk|home: there is a plasmoid in the package that might not work after the iterim release13:47
* ruphy fears that is going to be a whole mess13:48
Beineriwhy must be there 4.0 BIC changes to have panel config? isn't the base system good enough and just the gui missing?13:48
randomguy3dirk|home: if we release a source incompatible plasma, then kdenetwork-4.0.x will be incompatible with it13:48
rabaukeso there would have to be a fixed knetwork package13:48
Lurerandomguy3: but if we include bic changes to plasma in 4.0.2, then kdenetwork for 4.0.2 can include changes to new plasma13:48
ruphyBeineri: that can be easily done13:48
dirk|homeso thats yet another reason for doing sic changes not inside an interim release,but as part of 4.0.x13:48
spstarrChani: you didnt attend? (add yourself on gobby ;-)13:48
ruphyBeineri: without breaking anything actually13:48
Chaniwhat?13:48
aseigoLure: that's generally not how x.y release happen =)13:48
Chanispstarr: someone else added me13:48
ruphyspstarr, she's there ;-)13:48
spstarroh13:49
spstarr:)13:49
Beineriruphy: same for moving applets on panel and dnd between desktop & panel?13:49
ruphyBeineri: the problem is with an ad-interim release, which will push in also other changes happened in the lib13:49
aseigoBeineri: ok, so that's different then.. backport vs release13:49
dirk|homeis it really necessary to break source backward compatbility btw?13:49
aseigoBeineri: that gets us back again to the issue that we'd be backporting string changes ...13:49
Lureaseigo: we could make exception for 4.0.x series for plasma (if benefits of new plasma features are bigger than pain), right?13:49
* ruphy would say no13:49
ruphyaseigo: for string changes we could request an exemption I think...13:50
notmartshittyshit: i'm away for a moment hope to get back in a moment :(13:50
notmartseeya13:50
aseigoBeineri: we can probably avoid BIC changes, hopefully... though it does mean backporting changes to the boxlayout at a minimum, and there have been BIC changes there13:50
Beineriaseigo: ask the translators if they have problems with some strings if they have 3-4 weeks to translate them between to 4.0.x...13:50
Beineritwo even13:50
richmoore2it's sounding impractical to do an interim release to me, backporting some feature improvements seems possible though13:50
ruphyit's 3 or 4 strings I think, not that big issue...13:50
ruphyrichmoore2: agreedx13:51
Beineriruphy: the panel config dialog alone has more ;-)13:51
ruphywell, the problems are just with panel config and taskbar config13:51
* aseigo hates that dialog, but that's another matter13:51
Beineriaseigo: well, you have 4+ weeks to write something better ;-)13:51
aseigoso ... to backport massively ... or to do a full scale interim release13:52
Beinerior 8+ for 4.0.x+113:52
ruphyaseigo: if we backport just the single commits, I think we can keep the boxlayout bic...13:52
aseigoyou mean BC =)13:52
jpwhiting:)13:52
ruphyyeah, bc13:52
ruphyspstarr: please change the blue... make it lighter13:52
Beinerithis shouldn't delay 4.1 development more than required but IHMO there should be something more advanced released before August13:52
Join riccardo has joined this channel (n=riccardo@85-18-136-80.fastres.net).13:53
ruphyriccardo != me, for the records ;-)13:53
ruphyspstarr: danks shön =)13:53
spstarr:)13:53
Nick riccardo is now known as goric.13:53
goric:-)13:54
ruphyok... so? what are we going to do? /me votes for just backporting13:54
Beineriand the feature list should also be not unlimited, something like suggested in http://lists.kde.org/?l=kde-panel-devel&m=120228833517668&w=2 (for those without gobby :-)13:54
Nick jaguilera is now known as opsiAway.13:54
spstarrWOC is going to cause a split in 4.0.x with 4.1 though13:54
* ruphy would really love to do the next meeting entirely on gobby13:55
Chanithe backporting argument sounds persuasive13:55
ruphyok then, let's do that. agreements/objections?13:55
dirk|homethats why I asked when you want to do an interim release?13:56
* jpwhiting agrees13:56
dirk|homebecuase qt 4.4 will be introduced probably within 2 weeks for trunk13:56
spstarrwoot13:56
aseigodirk|home: are we doing that before 4.0.2 is out then?13:57
Quit nihui has left this server (Read error: 104 (Connection reset by peer)).13:57
Beineridirk|home: nobody is forced to start using its feature immediately for Plasma, or?13:57
Chanibtw, I'm probably going to be away from the 17th to the 7th13:57
aseigodirk|home: maybe it would be good to time those two events together...13:57
ruphyspstarr: the things you wrote are the reasons for backporting, not for interim release ;-)13:57
Chaniaseigo: sounds smart13:57
aseigoBeineri: we'll need to start using those new features asap though to be able to make the development window of 4.113:57
aseigowe have 10 weeks of feature devel left13:58
Chanionce woc hits, I expect things are going to get very BIC :)13:58
Quit longh has left this server (Remote closed the connection).13:58
jpwhitingyes, probably...13:58
spstarrruphy: er, they are for things you cannot do for backporting13:58
richmoore2sounds like having a backport day would be a good idea - no changes, just backports13:58
dirk|homeBeineri: nobody is forced to, but it might happen13:58
aseigos,day,weekend,13:58
ruphyspstarr: hmm?13:58
richmoore2ok, weekend13:59
dirk|homeBeineri: I can set up dashbot to check for qt 4.4 dependencies crawling in if anyone asks for that though13:59
ruphyspstarr: translation, stabilizing... those are backportings13:59
aseigoor maybe it'll only take a day.. hm.. yeah, maybe if we're dilligent13:59
dirk|homeaseigo: which two events exactly ?13:59
dirk|homeaseigo: 4.0.2 release and qt 4.4 switch?13:59
spstarrruphy: not BIC though13:59
aseigodirk|home: 4.0.2 being tagged and movign to qt 4.413:59
Chaniremember, in kdeland a "day" takes 48 hours at least :)13:59
dirk|homethe current plan is to go with qt 4.4 beta1 as soon as it is released13:59
ruphyspstarr: yeah, and that's pretty bad!13:59
Chanilike bic mondays... :)13:59
dirk|homewhich is being delayed already for several weeks due to that nokia thing13:59
BeineriChani: so a month has 1440 hours? :-)13:59
spstarrruphy: but WOC will begin new bic changes13:59
begertmorning :P14:00
dirk|homeaseigo: hmm, to make sure that you can backport trunk to 4.0.x branch without breaking something?14:00
aseigodirk|home: ok...14:00
aseigoheh.. "That nokia thing" yeah.. those details =)14:00
richmoore2the scripting stuff will be bic due to 4.4 - the trolls fixed a bic in qt14:00
dirk|homeaseigo: or why exactly should those two events be synced?14:00
ruphyspstarr: htat's why we should have it in 4.114:00
aseigodirk|home: to keep people writing easily backported changes until then? =)14:00
aseigoanyways.. ok, so backporting major changes seems to be the consensus14:01
aseigothat means:14:01
aseigoa) enumerating which changes to backport (probably not that hard =)14:01
Beinerijust for the record, plasma trunk already uses kdelibs trunk api ;-(14:01
spstarrruphy: well, we will14:01
ruphyjust commit small and I'll take care to cherry-pick the commits ;-)14:01
aseigob) getting blessing from the i18n teams so they don't send hit men out after me14:01
aseigoBeineri: oh, the animations thing. yeah14:01
aseigofor one14:02
richmoore2lets put a page on techbase listing the features to backport14:02
Beineriaseigo: no, the drag to panel uses something KConfigGroup.regroup() or alike14:02
Beinerireparent iirc14:02
cb400faseigo: at least one translator is very much for lifting feature/string freeze for plasma :-)14:02
annmarichmoore2: yes14:02
aseigoc) scheduling a day or two where we keep plasma in trunk/ static so we can concentrate on backporting stuff14:02
dirk|homeaseigo: b) is not a problem if done reasonable time before the actual tagging day14:02
spstarrheh14:02
aseigodirk|home: yeah, i don't think it'll be a problem. i just want to be sure we give them a heads up... just out of respect for them if nothing else14:03
dirk|homeaseigo: d) testing that trunk plasma works against 4.0 kdelibs14:03
dirk|homeas in.. compiles14:03
dirk|homecan be done by dashbot though14:03
ruphyI'm writing what I propose for a) in the gobby doc14:03
aseigoso... giving them two weeks to translate would mean by the 13th14:04
aseigofor 4.0.214:04
aseigowe could instead try for 4.0.3 which would give us mroe time to pick up some of the other panel related features everyone wants14:05
Beinerithat doesn't no/not much time to implement the missing 'important' features, or?14:05
* aseigo hates how this is turning, yet again, into "make a traditional desktop, fuck the future" development cycle14:05
cb400fyes, no need to rush.. the important thing is the major distro releases with 4.0 in the spring/early summer14:05
ruphyI've written in the gobby doc what I propose14:06
aseigocb400f: my only concern is the timing with qt 4.4 landing..14:06
Beineriaseigo: traditional? drag and drop between desktop and panel and vice versa is the future I thought ;-)14:06
* ruphy encourages everyone to have a look14:06
aseigoif we go for 4.0.3 then it needs to be *before* we commit too hard to any qt 4.4 specific stuff in the code base for things we'd like to backport14:06
begertaseigo: don't h8, retaliate!14:06
aseigobut after 4.0.2 is tagged14:06
dirk|homeaseigo: why not going with 4.0.2 and with 4.0.3 ?14:06
dirk|homeaseigo: only want to do the backporting work once?14:06
aseigoBeineri: the other things are ;)14:06
Quit ereslibre has left this server (Remote closed the connection).14:07
Join ereslibre has joined this channel (n=rafael@84.76.213.0).14:07
rabaukewhat about creating a separate branch for "internal backporting use" which does not use qt 4.4?14:07
Beineriruphy: add moving plasmoids on the panel, very missing14:07
aseigodirk|home: yes, we could do it twice.. once early next week, then again after 4.0.214:07
Join apol has joined this channel (n=apol@84.78.178.63).14:07
aseigodirk|home: as long as people are fine with us breaking all the rules multiple times =)14:07
spstarrwe need to all use git and cherry-pick it seems ;p14:08
ruphyBeineri: added, but you can do that yourself too ;-)14:08
spstarr(not that i've used cherry pick before)14:08
* aseigo gives plasma a leather jacket, a motorcycle and some cigarettes ... 'cause it don't play by your rules. ;)14:08
ruphyspstarr: eheh, I told you. ;-)14:08
spstarrlol14:08
ruphyspstarr: anyway, I can do that, just give me the rev number14:08
richmoore2aseigo: i think given how people are complaining about the lack of some features we'll need to do that14:08
aseigoso .. two backport days? one for 4.0.2, one for 4.0.3?14:09
ruphyunless hard conflicts show up I can do the merge quite easily14:09
richmoore2yes14:09
spstarrdid the Plasma::Dialog change get merged to branch?14:09
dirk|homeaseigo: well, I think its the least painful way, so I'm in favor of breaking the rules14:09
* aseigo checks for spstarr 14:10
aseigospstarr: Plasma::Dialog is in there, yes...14:10
spstarrok14:10
dirk|homeaseigo: but only as long as we don't run into serious regressions ;)14:10
dirk|homethe problem with the 4.0.x releases is that they're not well tested before release14:10
aseigodirk|home: heh. indeed. well, things are pretty happy in trunk/ right now14:10
* aseigo nods14:10
Join maxx_k has joined this channel (n=max@p57A7CAD4.dip.t-dialin.net).14:10
ruphyif you guys give me a hand to find all the rev numbers that need to be backported, I can do all the backports tomorrow, or even tonight14:11
aseigotomorrow is more sane for me, as i'll be sleeping much of the rest of the day today ;)14:11
aseigobut yeah..14:11
begertdirk|home: I would think 4.0.x releases would have more focus on bug/security fixes, and not feature releases14:12
spstarraseigo: has the plasma resizing code been fixed? or you planning to revert/refactor (or you did this already and it got absorbed into one of my trunk builds :-)?14:12
annmamaybe we need to send a mail about that to the list ruphy14:12
ruphyit's ok, just remain a bit more, and help me find all the commits for a given element14:12
aseigoso we need to identify all the features to backport, get it done before the 13th, and then schedule another day for 4.0.314:12
ruphy'find-the-commit' marathone14:12
aseigospstarr: resizing code?14:12
spstarrfor panel14:12
aseigoagain, resizing code?14:12
Beineriaseigo: so that's about 4 weeks for 'missed features'?14:12
spstarrchanging the size/resizing the panel14:12
aseigoBeineri: for those that aren't in trunk/ already14:13
aseigospstarr: i wasn't aware that it was broken14:13
spstarrI remember you disliking the dialog popup or something?14:13
ruphyannma: we can ask for permissions later, after all, for me I have to 'git svn dcommit' to get all the changes in svn, but before locally I've got everything14:13
CIA-3103tcoopman * r772716 10applets/trunk/extragear/plasma/applets/frame/frame.cpp: set the default config entries.14:14
annmaruphy: I thought to help you identify the ones to be backported14:14
ruphyoh, ok =)14:14
* ruphy announces the 'spot-the-commit-marathone'14:14
aseigoannma: that would be awesome14:14
spstarrI'll assume whats in trunk then is blessed :)14:14
aseigohey! who's writing code instead of at the meeting! ;)14:14
spstarrheh14:14
Chanihrm.14:15
Chaniaseigo: do you have plams to work on the panel in hte near future?14:15
tmske:)14:16
dirk|homeBethat is true14:16
dirk|homebegert: that is true, thats why we talk about bending the rules a little14:16
begertgotcha14:16
annmaOK, shall we move to next point?14:18
jpwhitingI think so14:18
ruphyyup14:18
annma=> a libplasma to kdelibs strategy14:18
aseigobegert: btw, flow layout -> commit at will =)14:18
* ruphy writes a summary on the gobby doc14:18
begert:)14:18
Quit boom1992 has left this server (Remote closed the connection).14:18
aseigoyeah, so that one scares the living daylights out of me ;)14:18
jpwhitinghehe14:18
aseigoas it means hard BC requirements and making sure all our crazy changes work for apps in general14:19
ruphyaseigo: just 1 sec, why is c) needed?14:19
jpwhitingaseigo: would it be easier after WoC?14:19
aseigonot that we aren't doing the latter and have the former as a goal for 4.114:19
aseigoruphy: if you don't need it, then we don't have to... just figured it would be easier14:19
Join boom1992 has joined this channel (n=lukas@pD9E1938F.dip.t-dialin.net).14:19
aseigojpwhiting: impossible before really14:19
begerthttp://matt.rogers.name/r/96/s/6/   it loks good with tasks14:20
Quit boom1992 has left this server (Remote closed the connection).14:20
begert*looks14:20
aseigothat's also when we will want to look at whether we wish to move things like Plasma::Package into GHNS214:20
jpwhiting:)14:20
ruphyaseigo: I'll need it just if people are more concentrated on helping me spotting the right revs ;-)14:20
annmayes!14:20
jpwhitingI'd better get that cleaned up soon then...14:20
ruphyspstarr, can I cut the "reasons for interim release to be part of 4.0.x release series" part?14:21
spstarrdo what you like :)14:21
aseigojpwhiting: which cleaned up? ::Package?14:21
aseigoor GHNS2? oh right you're working ont hat14:21
jpwhitingaseigo: no, knewstuff214:21
jpwhiting:)14:21
jpwhitingaseigo: yes, and I could  definitely use a core dev to bounce some design ideas off of some time if you get a spare minute... ;-)14:22
aseigoright.. so the big question is do we go for a move into kdelibs for 4.1 or for 4.2 and i'm really hesitant to commit to 4.1 for that out of general conservatism14:23
dirk|homeruphy: I wrote that btw14:23
richmoore24.214:23
aseigojpwhiting: absolutely14:23
mattr4.214:23
spstarraseigo: 4.214:23
aseigoyay!14:23
spstarrwe're way to hot of code right now14:23
aseigo4.2 it is ...14:23
Chaniok, moving alongthen14:23
aseigospstarr: agreed14:23
jpwhitingdoes that mean amarok 2.0 will not be possible until after 4.2? ;-)14:23
rabaukewhat benefits does a user have from going into 4.1?14:23
leinirjpwhiting: Yes, it does14:23
jpwhitingmeh, ok14:23
dirk|homeruphy: was there a reason for removing it? it is a good idea to document the reasons that where foudn for a given decision14:23
leinir(well, without a kdebase dependency at any rate)14:24
richmoore2jpwhiting: they can use a local copy14:24
jpwhitingas long as I can build it locally before then :)14:24
aseigoso 4.1 will be our "if we were in kdelibs" dry run, still in workspace.. and we'll shift to kdelibs with everyone's blessing once 4.1 is out14:24
jpwhitingrichmoore2: exactly!14:24
spstarraseigo: you think 4.1 will be enough time to get in all the functionality? including media centre stuff etc14:24
dirk|homewhat does that have to do with amarok?14:24
aseigoleinir: why can't you do what you're doing now and just ship with a version of libplasma included? e.g. the 4.1 v?14:24
dirk|homeamarok can (and should) build against workspace14:24
aseigodirk|home: they are using it.14:24
jackrabbitaseigo: that sounds right, because I think we'll need the time14:24
jpwhitingdirk|home: ah, true14:24
ruphydirk|home: oh, you wrote that, sorry14:24
dirk|homenot everything has to be in kdelibs14:24
ruphydirk|home: I thought it was spstarr :\14:24
jackrabbitaseigo: if we rush it then we're stuck with what we got until kde514:25
aseigospstarr: i have several meetings this month re: MCE stuff... so, we'll see it14:25
dirk|homeit is just that if its in workspace, it should be optional (because of windows/mac)14:25
spstarrgood stuff14:25
dirk|homebut there is no reason whatsoever for not building against workspace14:25
leiniraseigo: It's not really an optimal solution, but sure, it works :)14:25
dirk|homeso amarok2 is not concerned with 4.114:25
dirk|homenot having libplasma in kdelibs14:25
ruphydirk|home: I removed it because it was quite confusing, especially given that we didn't write reasons for the backporting strategy14:25
aseigojackrabbit: i'm less concerned about that and more cncerned about not getting something solid for app devs14:25
jpwhitingdirk|home: but amarok2 is concerned with mac/windows ;-)14:25
Join boom1992 has joined this channel (n=lukas@pD9E1938F.dip.t-dialin.net).14:25
aseigowin/mac is fine. we build and work there14:26
jpwhitingok, sorry, moving on...14:26
ruphyaseigo: I'd really like to finish off the GUIs before merging Package into kdelibs...14:26
* aseigo notes that the new locolor detection is x11 only though. would need someone to port that to other platforms for him if anyone cares too14:26
dirk|homeaseigo: but it doesn't make sense to build workspace on windows ;)14:26
spstarrahh yes....14:26
randomguy3dirk|home: which is why amarok currently holds a copy of libplasma internally14:26
jpwhitingdirk|home: but they can build workspace/lib/plasma fine currently14:26
ruphyaseigo: also because it needs some more love... which I'm pretty confident will be BC, but better not to rush on such things :-)14:27
spstarrruphy: we need oxygen love for Plasma ;P14:27
* Mek is btw working on porting lots of plasma/workspace stuff to OSX :)14:27
* jpwhiting hugs Mek14:27
spstarrMek: we didnt forget about that :-)14:27
ruphyspstarr: everything needs my love :-)14:27
spstarrhaha14:27
aseigobegert: hm. woudl be nice if flowlayout kep things top aligned, even if there is tons of space?14:27
aseigook.. roadmap...14:28
aseigohm.. actually, no..14:28
aseigoapril sprint first.14:28
ruphylol  :D14:28
aseigowhat's the status on that?14:28
jpwhitingI'll try to attend remotely if needed14:28
* aseigo , honestly, hasn't been keep up with the planning on that14:29
jpwhitingI'm trying to do less and less plasma stuff so I can focus on khns more...14:29
CIA-3103begert * r772729 10workspace/trunk/KDE/kdebase/workspace/libs/plasma/layouts/flowlayout.cpp:14:29
CIA-31Re-work of the relayout() function so that it actually works.14:29
CIA-31screenshot of using flowlayout with tasks applet: http://matt.rogers.name/r/96/s/6/14:29
dirk|homerandomguy3: why are they doing that?14:29
begerttop aligned?14:29
dirk|homerandomguy3: do they want to run plasma on mac/windows?14:29
dirk|homerandomguy3: or just integrate with plasma on mac/windows?14:29
jpwhitingdirk|home: they run plasma inside amarok14:29
ruphyme and sebas are working out the last details, I'm waiting to have concrete dates to get in touch with the hotel14:30
ruphyhow many days do we want?14:30
leinirdirk|home: amarok 2's context browser is a plasma view14:30
richmoore2given the distance some people are travelling i'd say 3-5days14:31
* spstarr will attend from IRC :)14:31
dirk|homeleinir: okay.. tough issue ;(14:31
ruphyah, btw, we should probably want to rent a car to ease the transports... if annma (or darktears) come with one, and we rent one (5 places should be ok) we should be fine =)14:31
ruphyfor obvious reasons I don't have mine yet ;-)14:31
aseigopublic transit that bad?14:31
ruphynow, dates... how many days do we want it to last?14:32
annmanot sure I can get a suitable car14:32
* aseigo doesn't drive abroad14:32
Chanioh yeah, it'd be nice to know dates. I'm in the awkward position of not being able to use my credit card online for some raeson, so I have to get my dad to buy plane tickets for me, and I think he might be off in england or something14:32
aseigo(personal policy_14:32
spstarrruphy: can you pull north america closer to Europe? k, thanx, love shawn. :p14:32
* Chani can't drive at all14:32
Quit cgoncalves has left this server ("Konversation terminated!").14:32
aseigospstarr: lol14:32
jpwhitinghehe14:32
aseigoyes, we need firm dates. that's the #1 thing here14:32
Join rui has joined this channel (n=rui@e180042206.adsl.alicedsl.de).14:32
annmaruphy: what dates are you looking for with sebas?14:32
aseigoi'll need to book tickets as well, we need to ask the e.V. board for financial aide (and they can be completely pricks ;)14:33
annmalol14:33
ruphyaseigo: unfortunately it's bad to reach milano14:33
aseigoruphy: hm.. ok...14:33
aseigoruphy: where would people fly into then?14:34
ruphy(we will be at the external part of it... and unfortunately it sucks there :( )14:34
ruphyaseigo: milano malpensa14:34
* aseigo notes that more remote place are actually great for these events... even it's a bit more post-fight travel, the lack of distraction == focus14:34
ruphyaseigo: from there the transportation is pretty good14:34
Chaniruphy: airport code?14:34
ruphythere's a train directly from the airport to a station which is 2-3 mins from my house14:35
ruphyChani: MXP14:35
Chaniah, good.14:35
Chanithe cheap flight I saw goes to that one14:35
Chaniiirc14:35
ruphyanyway, after we get into milano, at night, (10-15 min by car) there public transportation is very good14:36
spstarrruphy: stream the event :)14:36
* annma has to go, will someone log the rest for me please?14:36
aseigoruphy: ok, so it's pretty easy for me to get there14:36
jpwhitingannma: if I have to... ;-)14:36
annmathanks jpwhiting14:36
ruphyannma: sure, we'll send the summary to the panel-devel ml =)14:36
annmaOK14:36
annmathanks, sorry about that14:37
aseigostraight through frankfurt... ~830 euro14:37
ruphyannma: btw, to answer your question...14:37
ruphyannma: ~14 of april14:37
annmayes14:37
annmaOK14:37
Chaniok, so.. dates?14:37
aseigoruphy: hm. if it's only 10-15 min, can we take a taxi for that part?14:37
ruphyaseigo: the house is on three floors, + a small garden but with a very nice gazebo... we can have smaller groups working closer toghether if we want to14:38
aseigoruphy: great =)14:38
aseigoyeah, dates are useful... if we don't know them yet, that's the part we'll need to get asap14:38
aseigoannma: see you =)14:38
Chaniyeah. can't book flihts without dates :)14:38
* annma was waiting for the dates14:38
richmoore2yes, i have to give a seminar on security some time in march, so dates would be very useful14:39
* spstarr notes it would be nice if KDE e.V could get google to pay for videoconferencing for people not able to attend sprints ;)14:39
mattryeah, good luck with that. ;)14:39
Quit annma has left this server (Remote closed the connection).14:39
ruphyaseigo: it's way better if we rent a car, maybe a big one... cheaper and easier ;-)14:39
Quit rawicki has left this server (Remote closed the connection).14:40
spstarrI will be @ aKademy 2008 so, more plasma discussions will occur then im sure also.14:40
ruphyplus, we are more free to go in there... and I can choose good resturants to go into also for lunch =)14:40
Chaniis this gonna be over the weekend? how many days?14:40
aseigoruphy: hm.. ok.. i am somewhat sceptical of cheaper if it's 15 min drive there, and nothing's easier than catching a cab ;) though yes, certainly not as convenient for other driving around.14:40
aseigospstarr: absolutely14:41
spstarr:-)14:41
aseigospstarr: as for vid conf.. that would be great. we could probably set something up ad-hoc over the 'net... but "real" vid conf would be nice14:41
richmoore2spstarr: no, akademy 2008 will be a plasma free zone :-)14:41
aseigohaha14:42
aseigoyes, NO PLASMA PLEASE! signs everywhere14:42
ruphyaseigo: not that easy, italy, or europe in general, is not that good for that... except if you live in the downtown14:42
jpwhitingright14:42
spstarrthough, how much does KDE e.V pay for in terms of assistance? hotel/plane? im curious14:42
dirk|homehow about an audio conference for a start? ;)14:42
ruphylol :D14:42
aseigoruphy: hehe. you've not been to n. america then? ;) we put the meaning into the phrase "need a car"14:42
ruphy:D14:42
aseigodirk|home: that's much easier with skype, e.g. yes14:42
jpwhitingspstarr: http://ev.kde.org/rules/reimbursement_policy.php14:42
ruphywell, in sf it was extremely easy and cheap to get one14:42
spstarri dont mind splitting a hotel room with 4 people, just get cot beds etc14:42
aseigospstarr: 80% is standard, more in case of need14:43
spstarrjpwhiting: looking14:43
spstarr80% is more than generous !14:43
aseigoruphy: s.f. is an odd place ;)14:43
jpwhitingyep14:43
ruphyi see ;-)14:43
* notmart is back, woo14:43
aseigoanyways.. ok.. dates <-- harping14:43
aseigoruphy: when might we have solid dates to work with here?14:43
* richmoore2 will have to leave in 15 (looking at a flat)14:43
aseigowhich days almost doesn't matter. just having them is important14:43
ruphywe can decide that now if we want14:44
jpwhitingwe want!14:44
aseigosure. for me: any time in april.14:44
ruphyagreed ;-)14:44
Chaniare the dates gonna be 11th-14th or something? I saw someone say "~14" up there and I'm not sure what that meant14:44
ruphyso.... good dates seem to be between 10 and 18 of april14:44
ruphyif the google doc says the truth14:44
* ruphy checks it back14:44
Chaniyeah14:45
ruphyok14:45
Chanihmm. the jetlag is gonna suck14:45
ruphybad dates are 10 and 1914:45
Quit hdevalence has left this server ("Konversation terminated!").14:46
spstarrvery nice, with 80% that is more than enough to help me go to aKademy 2008, now i just need to hack more libplasma ;p14:46
Join tue has joined this channel (n=tue@port351.ds1-ly.adsl.cybercity.dk).14:46
aseigoChani: welcome to my world14:46
* aseigo says "nice" http://lists.kde.org/?l=kde-commits&m=120256037907209&w=214:46
ruphyplus, I want to give some time to chani and annma, which are the ones who have those bad dates...14:46
Chaniruphy: my dates are only suggestions14:46
ruphyok14:46
aseigoruphy: want to do it over the weekend then? often easier for people to make that...14:47
ruphyaseigo: agreed, easier for me too14:47
spstarr+*** New widget independent image canvas concept and implementation    :))))))))14:47
aseigoruphy: and then we can fly in/out mid-week, which tends to be cheaper14:47
ruphyhow many days?14:47
aseigo4?14:47
aseigoarrive thursday, fri-mon, leave tue/wed or something like that14:47
ruphyok, 4 full days + 2 of travel14:47
Chaniwhat's the usual amount of time between arrival and things starting?14:47
Chaniah14:47
aseigoChani: personally, i aim for one night's sleep. but some people need more than that14:48
* aseigo will die early for all this, he is sure14:48
Chanihehehe14:48
ruphyaseigo: ah, I'd say 4 full days...14:48
Chaniaseigo: at least it's for a good cause ;)14:48
ChaniI'm not entirely sure why I'm shortening my lifespan by being here in china...14:49
spstarrerm, shouldn't we move onto the roadmap now? :)14:49
Chanianyways. hmm.14:49
ruphyChani: eheh :D14:49
Chani11-14 it is then14:49
Join nf2 has joined this channel (n=norbert@vie-062-116-122-020.dsl.sil.at).14:49
richmoore2Chani: because it's the only country that's an anagram of your name14:49
aseigogreat. ruphy, can you announce that on the list then? =)14:49
ruphyok, 11-14... arrivals 10, departures 1514:49
ruphyok14:49
aseigook.. so: http://techbase.kde.org/Projects/Plasma/4.1_Roadmap14:49
ruphyanything special that we need setup?14:49
spstarrruphy: well, wireless for those who are attending? ;)14:50
dirk|homea magnetic field to contain the plasma14:50
spstarrLOL14:50
ruphylol :D14:50
aseigohonestly, i don't see anything on there that causes concern14:50
ruphywell, like... I have a projector we can use, or, a shared folder...14:50
aseigoi'm sure we'll get much more than that done too14:50
ruphyspstarr: obvious ;-)14:50
richmoore2in addition to the stuff on the roadmap so far, i'll be adding support for the rest of the script engine api to the qtscript support14:50
aseigodirk|home: heh.. yeah, that's the whole joke behind the Plasma::Containment class, actually ;)14:50
jpwhitingaseigo: I will also try to get the background wallpaper setup stuff pulled out into a widget for frame applet to use in it's config14:51
aseigoplasma: architected for humour14:51
* Chani has already bought a power adaptor thingy for italy14:51
jpwhitingwhich means default desktop will also get picture-of-the-day for free hopefully in the process :)14:51
aseigojpwhiting: that'll also be important for providing a generic background config (e.g. one that also lets people switch containments)14:51
richmoore2ruphy: one thing we're always short of is plug sockets14:52
* aseigo has 4 of those power adaptor things.14:52
Beineriaseigo: all from Trolltech? :-)14:52
aseigoyes, plugs and network.. we're brutal on both14:52
aseigoBeineri: hehe.. no, only 214:52
jpwhitingaseigo: containment choice is wanted in that dialog?14:52
spstarrhmm, i guess i need a power converter for aKademy also...hmm maybe a new laptop battery too..14:52
aseigoBeineri: i like NOT getting electrocuted, so i have other, safer ones14:52
ruphyrichmoore2: need foreign->european adaptor??14:52
aseigoBeineri: i like my guests use the tt ones ;)14:52
richmoore2ruphy: i have 214:52
jpwhitingaseigo: you'll have to explain how that will look to me later14:52
ruphyok, what do you need then? ;-)14:53
aseigojpwhiting: no, that dialog will end up inside the other one14:53
aseigojpwhiting: sure =)14:53
ChaniI don't seem to be follwing my raodmap stuff so well. I'm avoiding the applet browser, just got back into twitter, and now I'm distracted by svg weirdness...14:53
jpwhitingah, ok14:53
aseigojpwhiting: but we can discuss that later on14:53
jpwhitingyep14:53
richmoore2ruphy: generally we have so many people pluging stuff in that we need lots of extension cables so there are enough sockets14:53
* spstarr distracts Chani with shiny objects14:53
Quit goric has left this server ("using sirc version 2.211+KSIRC/1.3.12").14:53
richmoore2ruphy: and the adaptors mean that often stuff can't physically fit14:53
Chaniooooh... shiiiiny....14:53
spstarrhah14:54
* mattr helps14:54
mattrspstarr: quick! hold up larger shiny objects. ;)14:54
spstarrhehe14:54
* richmoore2 points at the moon applet14:54
ruphylol :D14:54
Chanirichmoore2: and we need to get the good grounded ones, not those dangerous ones that take a grounded plug but aren't grounded themselves14:54
mattrlol14:54
ruphylol^2 :°°D14:54
aseigoif there are going to be other n. americans there i can bring a n. american power bar and we can plug it in using an adaptor.. anyways14:54
* Chani has found out the hard way that they're bad14:55
ruphysorry, what have we agreed on for the libplasma->kdelibs? not to rush?14:55
richmoore24.214:55
mattrruphy: 4.2 is the consensus14:55
Chaniaseigo: well, too late for me14:55
aseigook, i don't see anything really discussing worthy on the roadmap. we have another 6 weeks or so before it has to be finalized anyways14:55
Chaniok14:55
Chanidata engines then?14:56
* mattr notes there are 6 patches in review-board that could use reviewing14:56
aseigowell, we've been at this for almost 2 hours now14:56
spstarrDesign time14:56
CIA-3103begert * r772740 10workspace/trunk/KDE/kdebase/workspace/libs/plasma/layouts/flowlayout.cpp: Top Align...let items be as large as they can be.14:56
ruphyhtanks14:56
Chanidamn14:56
mattr(7 if you count toma's mailody test patch)14:56
Chaniok, so only aseigo and spstarr have seen my thoughts on dataengines14:56
aseigoif people are cool with continuing ... i'd like to suggest a break, come back at 10 past...14:56
ruphymattr: btw, sorry for the predefined-letter way of closing bugs, but that's what kbugbuster provides ;-)14:56
spstarrbreak for breakfast :)14:57
Chaniaseigo: sure14:57
jpwhitingyes14:57
* aseigo makes coffee.14:57
* begert scrambles eggs14:57
Nick spstarr is now known as spstarr_breakfas.14:57
* Chani wishes there was caffiene in the room14:57
* ruphy calls the hotel14:57
Chaniok, I'm gonna go get some of that dodgy hot water, make tea, and hope it doesn't kill me ;)14:57
aseigomattr: my older patch there is just waiting for monday as it's highly BIC14:57
mattrruphy: you should learn to be creative. :)14:58
Chaniit'll be less dodgy than the 6-month-old fruits tea14:58
mattraseigo: ah, ok14:58
ruphymattr: you're telling an oxygen artist that he's not creative?!? :P14:58
aseigoand my runner patch seems to be a bit on the esoteric side for people ;)14:58
* aseigo will just commit that one14:58
tmskeok. I'll have to go, but I have some quick remarks for if you have some more time: shouldn't kde-apps have a plasmoids category and kde-look plasma themes?14:58
mattrruphy: just because you're creative with paint and ink and digital pixel does not mean you are also creative with words. :)14:59
ruphythis is the hotel, btw: http://www.hotellatorretta.it/Italiano/NF-home_ntorretta_01.htm14:59
ruphyyou probably want the english version ;-) http://www.hotellatorretta.it/Ing/Inglese/NF-home_ntorretta_01.htm14:59
CIA-3103aseigo * r772741 10workspace/trunk/KDE/kdebase/workspace/libs/plasma/abstractrunner.cpp: automatic rate limiting of runners: mark ill performing runners as slow, but let speed runners marked as slow back into the main thread pool.14:59
aseigomattr: and i think i've peer reviewed all the other patches there15:00
Join litb has joined this channel (n=litb@p54AED6FA.dip.t-dialin.net).15:00
litbhello all15:00
mattraseigo: cool.15:01
mattraseigo: everything still working ok for you then?15:01
Quit rabauke has left this server ("Konversation terminated!").15:04
* richmoore2 is late, see you later guys15:04
ruphyok, great15:04
ruphyhotel is ok15:04
Quit leinir has left this server (Remote closed the connection).15:06
* aseigo waves to richmoore2 15:06
aseigomattr: yeah, it's back to being a bit slow at times though.. *shrug815:06
jackrabbitare we still talking about the plasma-dev sprint?15:06
Chanijackrabbit: we're having a break15:07
jpwhitingjackrabbit: it's a break15:07
aseigojackrabbit: we're in a meeting break, so you can talk about whatever =)15:07
* aseigo thinks we have consensus that it's a break15:07
Chanihehehe15:07
jpwhitingaseigo: btw, handles annoy me15:07
Chanioh yeah15:07
jackrabbitall opposed? :)15:07
Chanidamn, I forgot to put that on the agenda15:07
jpwhitingI think they need a quadrant detection?15:07
Chanithere are several thinga about handles that are driving me nuts.15:08
jpwhitingso when you put an applet in the top-left quadrant of the screen, the handle buttons should show on the bottom-right instead of top-right15:08
Join leinir has joined this channel (n=leinir@amarok/usability/leinir).15:08
jpwhitingor top-left sometimes...15:08
Chanithe placement of the buttons and the z-order, basically15:08
aseigojpwhiting: yes, that's been discussed a few times...15:08
jpwhitingthought so15:08
aseigoit would also be great if the handle resized itself rather than applied the transform matrix to itself15:09
aseigoand only applied the temporary transform matrix to the applet15:09
Chaniz-order is retarded, somehow when I mouseover an applet it *sinks* below anything it overlaps, which often means I can't reach those buttons15:09
jackrabbitChani: I get that too15:09
aseigoyes, z-order is another item that needs fixing...15:09
Chanihmm.15:09
aseigoright now we z-order everything consistenly ..... except active applets ;)15:09
aseigoso fixing it should be relatively easy15:09
Chanisomewhere I had a patch for more complicated button placement, but I think it's bitrotted too much now15:09
Chanido we?15:10
jackrabbitI think icons should have the lowest z-order15:10
Chaniit doesn't feel consistent :)15:10
* ruphy invites everyone to read mail15:10
aseigoChani: yes.. containments, toolbox, applets, etc all get consistent z order values15:10
Nick spstarr_breakfas is now known as spstarr.15:10
ChaniI think icons should die, but that's just me ;)15:10
ruphysee you richmoore215:10
aseigoChani: we just don't do it for active/selected/dragged widgets so it's all for nothing ;)15:10
spstarr<-- reads /scroll15:10
aseigojackrabbit: they should be treated as any other object15:10
* aseigo notes his coffee is just about done... which means it must be nearly break time over15:11
Quit miga_ has left this server (Remote closed the connection).15:11
spstarr:-)15:11
Join hdevalence has joined this channel (n=harry@bas9-toronto12-1088716929.dsl.bell.ca).15:11
Chani23:1115:11
Chaniyup15:11
ruphyaseigo: it would be nice if handles would appear from the transparent border of the default bg that just expands15:11
notmartChani: i think they should survive, but oly as a mean to launch app, not to be a desktop view15:11
spstarr10:11am15:11
jpwhitingaseigo: except we have these silly desktop actions that apply only to icons (align vertically, horizontally, etc.)15:11
ruphyaseigo: it would actually even make it have some sense ;-)15:11
ChaniI've been avoiding any attempts at a folder plasmoid, hoping I could wait for woc15:12
aseigoruphy: of course, not all items have the background, but yeah...15:12
aseigoChani: ditto15:12
jpwhitingk, back on task?15:12
notmartruphy: si it means that a "normal" default background and a different one with borders expanded would be needed?15:12
ChaniI'm concerned about that panel config thing getting backported. didn't someone say that it'll introduce incompatible config file stuff?15:13
aseigoruphy: i'm RSVP'ing to your email  with a "yes, need a room"15:13
* Chani checks emnail, sees nothing15:13
* aseigo bangs the gavel15:13
aseigoChani: it's still going through the censors ;)15:13
spstarrhehe15:13
Chanigot it15:14
Chaniok. dataengines15:14
aseigoi think we only have time for a couple of items15:14
Chanidarn15:14
jpwhitingyes, probably15:14
aseigoso ...15:14
aseigowe can come back to the other items in less formal meets (the process stuff was most important for this meeting imo)15:15
jpwhitingyes15:15
aseigoso let's take two fairly easy ones, and one hard one15:15
ruphyChani:15:15
jpwhitingand almost all the implementation ones can be just small (the devs involved) meetings15:15
aseigokeyboard shortcuts, menus in containments and mutable dataengines15:15
aseigojpwhiting: yep15:16
* aseigo "mmmmm"s over his coffee .. 15:16
Chanihehe15:16
aseigoso .. keyboard shortcuts. this is pretty important.15:16
Chaniyes, it is15:16
jpwhitingok, keyboard shortcuts we are trying to achieve accessibility15:16
Chaniand I forgot to prepre for that one. damn.15:16
aseigopeople are asking for "alt-f1" which obviously is completely broken w/respect to the plasma model if we just copied kicker15:16
jpwhitingmake everything usable without a mouse, correct?15:16
aseigoright15:16
* spstarr notes not all keyboard have a Windoez logo key ;p15:16
aseigoso, my proposal is this:15:17
spstarr(which annoys me in kwin effects since i cant change some!)15:17
Chaniwith my laptop mouse dying, I'm very aware of the lack of keyboard stuff15:17
jpwhitingso applet selection, shortcuts for moving, resizing, etc.15:17
aseigo- a shortcut manager in libplasma15:17
aseigo- each applet can register a shortcut15:17
ruphythat'd be lovely15:17
aseigo- the user can define the shortcut for that applet15:17
jpwhitingand handles have shortcuts for their methods also15:18
aseigothe challenge is:15:18
ruphyand... bang! top-level-window ;-)15:18
aseigojpwhiting: yes..15:18
aseigothere are very few global accels available15:18
* jpwhiting continues to kick the dead horse...15:18
aseigoso ... we'll probably also need a two-stage system15:18
aseigowe can accomodate alt-f1 type stuff, but plasma will also need a "application global" shortcut that gives focus to the libplasma application (seli will hate us for that one, i'm sure ;)15:19
aseigoand then we can use local shortcuts from there15:19
aseigoso one might assign alt-f5 for instance...15:19
jpwhitinghehe, yes, probably15:19
aseigoand then ctrl+p for panel15:19
ChaniI've discovered a little keyboard issue: applets in the panel cannot get text focus. try adding a note, you can't type in it15:19
jpwhitingaseigo: ah, but which panel?15:19
aseigoand getting to the panel by the keyboard would then be alt+f5, ctrl+p15:19
aseigojpwhiting: whichever one you assign it to15:20
* jpwhiting is just playing devils advocate15:20
Chaniaseigo: ctrl-f12 should also focus plasma desktop, I assume15:20
begertI might be way off base here, but we will need an applet equivalent of Alt-Tab ?15:20
hdevalencethanks for the help15:20
aseigoonce picked, then we can provide other shortcuts for things like the handles, etc15:20
hdevalenceerr15:20
jpwhitingbegert: yes, probably15:20
aseigobegert: i think we will need to allow one to tab through widgets yes..15:20
Chaniyes15:20
begertcool15:20
aseigoso, e.g. alt-f5, p, tab tab tab15:21
aseigothat's an a11y requirement, actually15:21
Chanialt+f5 is very close to alt+f415:21
notmartmaybe pressing altf1 a toplevel window is opened similar to alt tab that says what every shortcut is and is also clickable?15:21
Chanigiven the number of typos I', m making right now, I don't like f5 :)15:21
aseigoChani: sure, it's jsut an example15:21
randomguy3but we need to distinguish between tabbing through applets and tabbing through widgets contained in applets15:21
jpwhitingChani: you can change it on yours, don't worry15:21
* aseigo decides to make the windows key the plasma key.15:22
spstarrnoooooooo15:22
aseigo;)15:22
jpwhitinglol15:22
spstarrI dont have one :P15:22
aseigospstarr: no keyboard for you then ;)15:22
jackrabbitaseigo: isn't it already the amarok key?15:22
* Chani has done alt-f4 instaed of ctrl-f4 many times while global shortcuts were stuck15:22
jpwhitingaseigo: or use that meta key that none of us NA'ers have15:22
Chanihmm15:22
spstarraseigo: unless i can map a Fn key to a letter15:22
spstarrFn + P for Plasma :P15:22
aseigohehe.. we'll arm wrestle for it ;)15:22
jpwhitingok, back on topic, sorry...15:22
Chaniaseigo: I thought the windows key is used as a meta key?15:22
* aseigo phones up logitech and suggests they start shipping keyboard with a cashew key15:22
spstarrhaha15:22
jpwhitingrofl15:22
Join fred84 has joined this channel (i=fred79@host76-139-dynamic.60-82-r.retail.telecomitalia.it).15:23
spstarr"Press the cashew"15:23
Chaniwin+p? :)15:23
spstarrif i can map Fn + P im good15:23
notmartwe need to begin to sell keyboards with a key with the plasma logo on it :D15:23
jpwhitingaseigo: we can just ship stickers of cashews for ppl to put on their windows key ;-)15:23
aseigowin+p is cool...15:23
aseigonotmart: yes...15:23
aseigoabsolutely...15:23
jpwhitingcashew+p is cooler ;-)15:23
Chanijpwhiting: get some orange nail polish and mod it ;)15:24
begertI would think ctrl-f12 to show desktop, then tab, tab, tab to cycle applets?15:24
aseigomac has the flower (i miss open/closed apple, btw), window has the flag, we'll have the cashew15:24
jpwhitingChani: can't stand the stuff15:24
aseigobegert: doesn't work for panels, doesn't work for multiple containments, etc15:24
dani_lokay, let's take the default amarok global shortcut :) (which is win+p)15:24
* ruphy still can't believe that the thread "KDE being misspelled as KD in transcript of Linux Foundation interview with Linus Torvalds" got more than 20 answers O_O15:24
aseigoruphy: yeah, but they were all light hearted =)15:24
jpwhitingdani_l: seriously?15:24
ruphyaseigo: eheh, yeah ;-)15:25
aseigokraft dinner!15:25
Chaniok, back on topic! :)15:25
* ruphy is still wondering what the heck i that15:25
aseigook.. so no one has issues with that proposed plan? great15:25
jpwhitingruphy: at least it wasn't asking for the global replacement of the letter K to some sanscrit thingy ;-)15:25
aseigoruphy: macaroni and cheese in a box15:25
* Beineri can't believe ruphy is talking here about not public threads15:25
leinirdani_l: No it's not! It's [super][p] - just because your dialogue says it's [win][p] doesn't make that our choice ;)15:25
Chaniaseigo: yeah, your proposal is generally what I was thinking15:25
* jpwhiting agrees15:25
dani_lleinir: lol15:25
* ruphy agrees too15:25
spstarr:P15:26
aseigook.. menu handling in containments15:26
jpwhitingum, the ui for picking shortcuts wont that just go into the keybindings kcm?15:26
aseigothis one's fun15:26
* ruphy , being italian, would rather not imagine how that would taste like15:26
Chanimenu handling?15:26
ruphyBeineri: c'mon dude ;-)15:26
aseigoso someone *finally* requested it: they wanted "the k menu on left click, and window list on right click"15:26
aseigough15:26
Chaniahh, that15:27
aseigothe bigger problem here, of course, is that we have code in DefaultDesktop that really needs to be shared, but does not belong in Containment15:27
ChaniI used to use that feature a lot on my desktop. one menu per button15:27
aseigo(for menus that is)15:27
leinirAbout that amarok shortcut, mind, i do believe we could be convinced to select another one as default for amarok 2 - since the p meant playlist, and that is not exactly true any longer, we need really to find another shortcut for showing/hiding the amarok window... thus leaving [super][p] free for plasma :)15:27
ruphywoot :D15:27
jpwhitingaseigo: yes15:27
aseigoso my proposal is this:15:27
aseigoPlasma::Menu15:27
Chaniaseigo: have you seen the BR that proposes a floating mini-containment that can pop up by the mouse?15:28
ruphyaseigo: hmm... what would it do?15:28
aseigowhich will let us write plugins that either the contianment or the user can pull in an associate with left/middle/right/etc (gesture?)15:28
ruphyChani: top-level window plasmoids? I already have the design15:28
aseigoChani: yeah...15:28
jpwhitingaseigo: similar to windows shell extensions?15:28
aseigoruphy: no, she's talking about replacing menus with a plasmoid thingy15:29
aseigojpwhiting: sort of...15:29
spstarrhmm15:29
ruphyoh15:29
jpwhitinghmm, interesting15:29
ruphyaseigo: hmm.... don't we want to mix that up with extenders?15:29
ruphyereslibre: ping, btw ;-)15:29
aseigoi'd like to avoid putting any UI assumptions in it15:29
aseigoessentially just a "show at (x,y)" along with a loading mechanism15:29
Chaniaseigo: not exactly replacing, because you wouldn't need the desktopp showing to summon it15:29
ruphyok15:29
aseigooh, and some context information that it can use (e.g. which containment, applet, etc015:29
aseigoso that if people want they can make little pie menus15:30
aseigoor popup entire windows15:30
aseigoor whatever15:30
ruphyaseigo: how would that relate with extenders? extenders will be a subclass?15:30
Join wirr has joined this channel (n=wirr@i59F5C297.versanet.de).15:30
jpwhitingah15:30
ereslibreruphy: pong15:30
aseigoruphy: extenders are a completely different idea15:30
notmartuhm, so different?15:31
aseigoruphy: those are for applets to get more space temporarily to show information (e.g. the clock's calender, the device notifier's device listing, etc015:31
ruphyaseigo: ah, right, they probably are more related to Plasma::Dialog, right?15:31
aseigoruphy: the applet populates those15:31
aseigoright15:31
ruphyok15:31
aseigoonce we have WoC i'll be adding a generic interface to a standardize form of Plasma::Dialog in Applet15:31
aseigoso you can just request "your" Extender and populate it15:32
Join whitman_ has joined this channel (n=whitman@host86-128-208-57.range86-128.btcentralplus.com).15:32
ruphyereslibre: nothing, I thought you would have been interested... you know, extenders...15:32
aseigoand everything is handled for you otherwise (including how it shows up, where it shows up, etc)15:32
ruphyok15:32
ereslibreruphy: hehe yeah... is a pity i cannot concentrate... tuesday statistics exam :(15:32
crazyaseigo: are there any plans to make kickoff themable ? and a bit more 'plasma style' ?15:32
ruphyereslibre: good luck! =)15:32
ereslibreheh thx :)15:32
notmartso Applet will draw in a toplevel window that it would have drawn if it would have more space15:32
ruphycrazy: yeah, raptor :P15:33
Quit apol has left this server (Remote closed the connection).15:33
spstarr:)15:33
aseigocrazy: i don't have any such plans. the suse people (e.g. Beineri) have a number of nice patches that can make it a lot better15:33
Join apol has joined this channel (n=apol@84.78.178.63).15:33
ruphywhich actually still needs a maintainer...15:33
ruphymandriva is pretty interested in making that better too15:33
* aseigo wants to see the bold text headings go away and get replaced with the same "line with text under, right justified" they have in kickoff in opensuse 10.315:33
Beineriaseigo: are you thinking of something other than the bottom bar? :-)15:33
crazyruphy: be sure once raptor work I won't ven build kickoff ever again =) ( I hate it that much you can't imagine that :P )15:34
hdevalencei was asking about something the other day and I was told that it was one of the topics. I have a 128px vertical panel [widescreen++] and unfortunately the stuff like battery icon etc scaled to 128x128 :( is there a way to make them go side-by-side?15:34
Quit whitman has left this server (Nick collision from services.).15:34
Nick whitman_ is now known as whitma.15:34
* Chani ywans15:34
Nick whitma is now known as whitman.15:34
* aseigo puts "build time dependency on kickoff in raptor" on his todo for crazy ;)15:34
aseigook... so no objections there, moving on to the Annoyingly Hard One15:35
crazyaieeee =)15:35
aseigomutable data engines15:35
Chaniok :)15:35
spstarrthe dirty truth about dataengines15:35
ruphyouch!15:35
spstarr;)15:35
* ruphy would love an xmlrpc dataengine15:36
spstarrwarning! this is ___ SENSORED ___15:36
ruphy.... so? :D15:37
aseigospstarr: Chani: wish to air your desires?15:37
* Chani looks at aseigo 15:37
aseigohaha15:37
Chanioh, I thought you were typing15:37
aseigoit's a mexican standoff15:37
Chanilol15:37
Chaniok, so15:37
spstarrDesires15:37
ChaniI had a big long email about this but I was shy and didn't send it to the list15:38
spstarrParameterization of dataengines15:38
spstarrinstead of "foo|bar|goo"15:38
spstarrneed a sane way to pass data back and forth between dataengine <-> applet15:38
Chaniwhat I'd like most of all is a function in DataEngine that takes a qvariant or something, so that I can shove data at the engine15:39
aseigolet's define that a bit better before things get confusing15:39
spstarrconnectSource cannot set [datasource, key, value]15:39
aseigo"pass data" ==> pass query data15:39
aseigospstarr: nore should it *Ever* be allowed to15:39
notmartyeah: a little bit lost :D15:39
Chaniyeah, there's also this issue that source names are starting to turn into long strings of information15:39
spstarraseigo: well, the abusure of Q_PROPERTY is fugly15:40
aseigospstarr: that would, seriously, fuck things up so badly i'm not even going to consider allowing direct manipulation of DataEngine data from outside the engine15:40
aseigowe can provide a way to request changes, maybe, but not directly15:40
aseigothat's not the only other choice15:40
spstarrso, then what do you propose? :) this is the meeting for that15:40
Join apol_ has joined this channel (n=apol@84.78.178.63).15:40
notmartChani: so it's needed a way to separate the source name and the actual query, that it's a little bit blurred now15:40
Join Eren has joined this channel (n=eren@88.231.191.127).15:40
aseigowe really should avoid encouraging engines to abuse the *data store* as a way to get data from the applets as well15:40
aseigobecause, again, that really fucks things up. how do you map that to the "one data, many visualizations" pattern? answer: you can't15:41
ChaniI see this as two distinct cases: wanting to send an engine info for internal use (like a password) and wanting to send an engine data for it to pass on to hte outside world, so that the apllet doesn't need to know how15:41
spstarraseigo: thats difficult for online services applets15:41
aseigospstarr: not at all15:41
spstarri can confine the 'type' of data which the ions do right now15:41
aseigospstarr: "online service" is the right start though15:41
notmartaseigo: so dataengine will be always read only?15:42
aseigopersonally, i think we should add a generic (e.g. hidden behind API) mechanism for applets to pass additional query information to a source request15:42
* aseigo ponders why people see things in binary when it's computers that are stuck in 0s and 1s15:42
aseigonotmart: is that the only other choice?15:42
notmartuhm, don't know :)15:43
aseigothat mostly solves the weatherengine issues15:43
jackrabbitaseigo: the subject is mutable dataengines but has the *problem* been defined?15:43
Chaniaseigo: are you thinking of passing such information at the same time or something that can be done whenever?15:43
* begert wishes I did not try and move my panel around :(15:43
aseigojackrabbit: yes, there are two sets of use cases:15:43
jackrabbitI'm not sure what we're trying to do here15:43
aseigoa) a source being requested needs a phrase, not just a word. so ... "validate Calgary"15:44
* ruphy points out that for the meeting... in the lowest floor there's a sauna we can use, 3-4 at time... ;-)15:44
aseigowhich means that there is a syntax, which is the annoying part:15:44
aseigo- each engine needs to implement a tokenizer15:44
* Chani just created a new document on gobby with her email15:44
aseigo- each visualization needs to know how that engine expects it to be formatted15:44
Chaniruphy: oooh15:45
aseigosauna!15:45
Chaniruphy: is there a hot tub too? :)15:45
aseigob) there is some desire to have data sinks15:45
aseigopersonally, i don't think (b) belongs in DataEngine15:45
aseigoso, e.g. a way to generically write a new twitter15:45
freglI'd like to have a data sink ;)15:46
ruphyChani: not in that house :(15:46
Chaniaseigo: the reason I want it in dataengine is that my engine already understands how to deal with this kind of data, so it's a tiny extra bit of code for me there15:46
freglanswer vocabulary question → evaluate15:46
aseigo_personally_ i think that should be exposed via another interface completely...15:46
Chaniaseigo: a separate DataSink class?15:46
* spstarr really, really dislikes tokenization handling 15:46
jackrabbitDataFuelTank15:47
Chaniaseigo: why?15:47
* ruphy would love to see an easy way for plasmoids to query web services via XML-RPC and SOAP15:47
ruphythat would dramatically increase the number of plasmoids15:47
randomguy3aseigo: one that can be implemented by the same class as the data engine, if that makes sense?15:47
notmartso for instance twitter would have a data engine to download the updates and a DataSink to post updates.. hmm15:47
aseigofregl: could that be done with paramaterized sources though? sort of like how a web service would do it?15:47
freglaseigo: how do web services do it?15:47
freglI'm just getting started with plasma...15:47
aseigoruphy: well, if we do a nice simple sourcename + query impl for data engine, then that becomes rather easy15:48
Quit apol has left this server (Nick collision from services.).15:48
Chaniaseigo: what sort of interface are you thinking of?15:48
Nick apol_ is now known as apol.15:48
freglI would like to get the string from say a text edit to be able to provide a response, so I guess possible15:48
aseigothe *challenge* with adding query to sourcename is this: do we allow one to modify the query?  that's going to be the natural desire... if so ... how do we maintain the "one data, many visualizations" pattern15:49
spstarraseigo: it gets messy when you have to keep track of *more* than one datasource at a time , keeping them unique etc15:49
aseigothat's essentially what fregl wants: a data source, that can react to changes based on updated queries15:49
aseigospstarr: precisely15:49
spstarrwhich is where im ripping my hair out :)15:49
aseigospstarr: well, it's not so much trakcing the multiple sources, it's tracking their relationship to visualizations15:50
spstarryes15:50
aseigotracking multiple sources is actually fairly trivial15:50
aseigodetail oriented, but trivial15:50
Chaniaseigo: when i was pondering this, I first wanted to be able to reconfigure and existing source, but after writing code I decided it was better to ditch the source and reconnect with different setttings15:50
Quit uwolfer has left this server (Remote closed the connection).15:50
aseigoChani: writing code on which side.. engine or applet?15:50
spstarrwell, yes/no, my madness of ions makes that not so trivial :)15:50
aseigoChani: because for the applet, it'd be nice to just interact with the source...15:51
spstarrsince im the only crazy one to do it so far15:51
Chaniaseigo: engine iirc15:51
Nick apol is now known as apol_.15:51
randomguy3so: are we considering whether adding query parameters to a source changes all instances of that source, or only the ones with those parameters?15:51
* randomguy3 is slightly lost15:51
Chaniaseigo: the applet just does a disconnect/reconnect when anything changes15:51
aseigoChani: right.. if it's added to engine properly, though, maybe it's not so bad.. e.g. you get an updateSource with both the source and the current query params15:51
Nick apol_ is now known as apol.15:51
Chanithe function has a horrid name though. downloadSomething15:52
aseigoChani: which sucks for applet developers15:52
ChaniI forget uit15:52
randomguy3applet1 connects to source115:52
aseigothe trivial thing for applet developers would be to just respond to incoming dataUpdated calls15:52
randomguy3applet2 connects to source1 with parameter foo=bar15:52
spstarrrandomguy3: not so simple :)15:52
randomguy3does that change applet1's source1?15:52
spstarrapplet1 connects to mainsource which connects to source1.15:52
Chaniaseigo: then the engine will have to intelligently handle two source connections with different params. maybe kinda like it handles different update intervals, I dunno15:52
aseigoas for actual sending of data, e.g. twitters, that really does need its own class.. and that needs to be though out a bit more than i've put to it i think15:52
Join uwolfer has joined this channel (n=uwolfer@kde/developer/uwolfer).15:53
aseigoe.g. we may end up havng a sort of specialized class of problems that can be summarized as, "send this data here to that service there"15:53
Chanirandomguy3: that's why I changed my mind and wanted separate sources for such things15:53
ruphythis meeting is so fucking long... o.o15:53
aseigoin which case, we may go for a completely different scheme than with engines, where we have a centralized registry of services that accept data (a sort of switchboard)15:54
spstarraseigo: I need to disconnect 'dead' sources though and its not too trivial when im generating so many different sources :)15:54
Chaniaseigo: but I don't understand why you think it should be separated out so much15:54
aseigospstarr: from the applet side?15:54
spstarryes15:54
ChaniI haven't thought through the DataSink idea well enough myself15:54
aseigoChani: because the design pattern is *incompatible*15:54
notmartbut maybe some times the query and an update could be very blurred, if querying modifies something in the server would be considered a query? an updated?15:54
Quit cheko has left this server (Remote closed the connection).15:54
aseigoseriously, look at the entire concept behind DataEngine:15:54
aseigo* simplified, generic access to varied data sets15:55
Quit uwolfer has left this server (Remote closed the connection).15:55
aseigo* one source, multiple visualizaitons15:55
aseigo* no assumptions on what the visualization is15:55
aseigo* timing, resource allocation, etc all handled for you15:55
Join uwolfer has joined this channel (n=uwolfer@62.48.114.50).15:55
aseigothat just gets completely raped as soon as you start adding write services into it15:55
randomguy3so, what doesn't fit this pattern:15:56
spstarrmultiple sources <-> multiple visualizations ;p15:56
notmartbut if two visualizations asks for slightly different data it would be kept one source? made two sources?15:56
ChaniI guess I've been looking at it as a small extra feature of engines15:56
randomguy3(1) sending updates (eg: twitter)15:56
aseigothere's no reason to add a jumble of crap to that when we can have a nice, clean separate interface15:56
randomguy3(2) sending commands (eg: nowplaying - play/pause etc)15:56
aseigohave you ever considered that there may be data sinks that have no need for a dataengine?15:56
Chaniaseigo: I don't understand how adding one little function is so bad :)15:56
Chanino, I haven't, that's a very valid point15:56
Join apokryphos has joined this channel (n=francis@opensuse/board/apokryphos).15:56
aseigoChani: it's not one little function, though.15:57
spstarraseigo: we need some sort of method in DataEngine to pass 'internal' query information to engines, but that really is 'writing' though15:57
aseigoChani: it's quite a bit of code to do it right15:57
Chaniaseigo: why not?15:57
aseigothere's nothing that says you can't meld your engine/sink at the hip and share code and what not15:57
aseigohell, your sink could request the engine, or vice versa if need be15:57
Chanihmm.15:57
aseigospstarr: no, it's not writing15:57
freglso engine and sink would communicate in which way?15:57
aseigospstarr: it's parameterization15:57
aseigothose are very different things15:58
jackrabbithaving a datasink would be a great feature for the soliddevice engine15:58
aseigoone is actually passing data, the other is defining how the response should look like15:58
spstarraseigo: an example is when i pass WINDFORMAT to the engines they 'adjust' themselves accordingly and return different data back to the applet.15:58
Chanifregl: well, the sink can *get* info from the engine quite easily15:58
spstarrper source15:58
Chanigiven its nature15:58
freglChani: right15:58
Chanijackrabbit: how so?15:58
randomguy3spstarr: but couldn't the engine provide both and allow the applet to select the appropriate one?15:58
aseigospstarr: personally i think WINDFORMAT is crackrock ;) you should just put multiple wind sources and visualizations can connect to the one they want15:59
spstarrrandomguy3: I'd overflow the dataengine source limit15:59
aseigowhat limit is that?15:59
Chanispstarr: why don't you offer a sorce for each wind format?15:59
jackrabbitChani: it would allow you to use solidcontrol to control things, like eject a optical disc15:59
aseigos,source,data key,15:59
Chanioh15:59
spstarraseigo: well, at this right I might have 100 keys just for _one_ place :)15:59
Chanithere's a limit?15:59
aseigojackrabbit: right15:59
aseigospstarr: and?15:59
notmarti'm a little bit lost: if two applets will asks for thw weather of two locations it would still required to create two souces, right?15:59
spstarrwell, it adds memory usage?16:00
Chanijackrabbit: mmmm16:00
spstarrnotmart: they are independent of one another16:00
jackrabbitChani: and the possibilities are much greater once we get to solidnetwork[control]16:00
aseigospstarr: that's where you have to sit down and ask yourself: "what data really matters? what data should be split out into separate sources all together?" etc.16:00
notmartspstarr ok :)16:00
Chanispstarr: do you really need to have all sources existing all the time?16:00
spstarraseigo: im fine with killing Q_PROPERTY fuglyness and 'exporting' all the wind formats in the datasource16:00
aseigoand we are, after all, talking 100s of bytes here, not even Ks16:00
aseigoer, KBs16:01
Join apol_ has joined this channel (n=apol@84.78.178.63).16:01
spstarrChani: well, yes16:01
spstarrbecause users can dynamically change their minds :)16:01
Chaniaseigo: mmkay, so what does DataSink need, other than the ability to accept data?16:01
Chanispstarr: but sources can be created ondemand, just by connecting to them16:01
aseigoChani: need to define the service (e.g. Twitter) just as we do with engine16:01
* aseigo notes that there's probably no real reason one couldn't MI engine and sink16:01
aseigowell, no.. because sink will also be a qobject16:02
ChaniMI?16:02
aseigoso.. composition then. anyways16:02
Chanioh, n/m16:02
aseigomultiple inherit16:02
jackrabbitsendQuery(QString function, QVariant param1 . . .)16:02
spstarrok i will drop the Q_PROPERTY stuff in trunk.. which will break my ABI/BC but thats fine, nobody uses these parts yet :)16:02
aseigoso... sth like ...16:02
spstarrbut i still think we do need a way to pass additional query information to a source request16:03
Join sebbar has joined this channel (n=sebbar@p5B1573B4.dip.t-dialin.net).16:03
aseigoPlasma::Service *twitterService = service("twitter");16:03
Chaniaseigo: ok. so the DatSink has a name, like the data source. gotta have that to call it up from the manager (can hte engine manager manage these too?)16:03
jackrabbittwitterService->sendQuery("Post", QString("We had a Plasma Meeting today."))16:03
spstarroh yes aseigo: we also discussed the fuglyness of my KConfigGroup nastyness also16:03
aseigotwitterService->setProperty("username", "foo")16:04
ChanisetProperty?16:04
aseigotwitterService->send( ...) <-- something16:04
spstarraseigo: you mean use Q_PROPERTY in this case?16:04
Chaniaseigo: nonono, how do you know there's only one username?16:04
spstarror setProperty becomes a Plasma API method?16:04
aseigoChani: ah, here, you see, is why i used Service and not Sink16:04
jackrabbitspstarr: setProperty becomes a plasma method16:04
Chanialso, you need a password :)16:04
aseigoDataSink will provide a factory for Service16:04
spstarrok16:05
jackrabbitor DataService16:05
Chanibut that's just a detail16:05
aseigoso each caller gets their own Service16:05
spstarrwe should document this on gobby?16:05
Chaniso... hmm...16:05
aseigoand DataSink manages those Services that belong to it16:05
spstarrif we're going to have Plasma::Service etc16:05
Chaniyeah, someone start copying this stuf for us :)16:05
ruphyaseigo: they shouldn't be all QString. e.g. rpcService->sendQuery("methodName", QList("arg1", "argn"));16:05
aseigoat least, that's my first draft thoughts from earlier in the week16:05
aseigoso just like DataEngine, we DataSink has multiple "sources"16:06
aseigocalled Services16:06
spstarrweatherService->sendQuery("Validate" , "Calgary, AB"); <-- but i cant deal with chained dataengines16:06
aseigobut in this case they are one-to-one with the visualization16:06
Chaniaseigo: so... one Sink, and then one Service per user (or other configuration thing)?16:06
aseigospstarr: your sink could use your ion engines16:06
spstarraseigo: i'll need to see how Sink will work16:06
* aseigo realizes that that line probably sounds more like a bit of Star Trek dialog than coding16:06
spstarrhaha16:07
Quit begert has left this server ("Konversation terminated!").16:07
aseigoChani: one Service per visualization16:07
aseigoe.g. per applet16:07
Chanihehehe16:07
Chanihmmmm.16:07
aseigoso each twitter applet would end up with its own Service16:07
Chaniaseigo: okay16:07
aseigowell, actually, that would be up to the Sink at the end of the day, but likely it'll just hand out a new Service on each request16:07
ChaniI'm not 100% that's good, but... hmm16:07
Join begert has joined this channel (n=bill@cpe-74-74-217-64.rochester.res.rr.com).16:07
spstarrshould sendQuery have ([source], key, value); ?16:07
spstarrsince you need to distinguish which source?16:08
aseigothis allows us to keep the simplicity of display only widgets16:08
ChaniI imagine things like jackrabbit's solid cd-eject idea would only need one service to do that :)16:08
aseigoit also makes it trivial to do things like have multiple applets updating the same service without banging into each other16:08
aseigoChani: right16:08
* Chani already has them not banging into each other16:08
ruphyhow do you get the data back? the usual way?16:09
aseigoand most importantly: it avoid tempting engine writers to write engines that only work with one account or visualization at a time16:09
aseigoChani: yeah, but it's ugly and frustrating, isn't it?16:09
Chanibut with the horrif hackl of setProperty("status", "user:message")16:09
jackrabbitruphy: I would think through the dataengine16:09
Chaniyep16:09
spstarraseigo: and then there is 'this problem:16:09
aseigoruphy: i think we'll probably do just as with engines and have a generic update slot... serviceUpdated or somesuch16:09
litbhello all16:10
aseigoChani: and it's that pain i want to relieve without screwing widget writers over16:10
aseigolitb: yo16:10
litbi consider porting kima with ken16:10
Chaniaseigo: originally I thiought I was just gonna quickly fix up the twitter engine so that it could handle >1 user, and here I am now...16:10
litbis this teh right time, and what engine should we look at?16:10
spstarr[Containments][1][Applets][20][Configuration][Calgary]16:10
spstarrdata=http://feeds.bbc.co.uk/weather/feeds/obs/world/0262.xml16:10
spstarrion=bbcukmet16:10
aseigoso ... DataSink -> Service .. and a way to pass query specifications to DataEngine::connectSource16:10
spstarrthe uglyness of metadata16:10
ruphyaseigo: just brainstorming... what about getting an id back and then QVariant getResultFor(id)?16:10
litb(it's a monitoring plasmoid for temperatures, speed and so on)16:10
Chaniaseigo: wait... generic update slot? eh?16:10
aseigoruphy: like Phase .. well, if you have the Service kicking around, you should be able to just do service->result()16:11
ruphyno idea if it's better, just throwing the idea i16:11
ruphyyeah, like phase16:11
freglhm, getting data from a sink feels wrong...16:11
jackrabbitservice-result(id)16:11
aseigohopefully i'll make Applet do nice trickery like manage the services associated with the applet automatically16:11
* Chani feels her brain slowing down16:11
jackrabbitif you wanna have multiple queries16:11
aseigoso you can just call service("foo") multiple times and keep getting the same one until you say your done with it16:11
Chanifregl: yes it does16:11
spstarrthis is a fundamental shift in dataengines aseigo :-)16:11
spstarrwell, apiwise16:12
aseigofregl: return values are a fact of life with such things16:12
Quit apol_ has left this server (Remote closed the connection).16:12
Chaniso16:12
Join apol_ has joined this channel (n=apol@84.78.178.63).16:12
freglbut then there is no reason for engines to exist... they are just reduced sinks then...16:12
aseigospstarr: not really. it adds another connectSource method, and another sourceRequested method (or an overload.. but i think i prefer the latter)16:12
Chaniaseigo: feedback on async stuff... how would that work? right now my dataengine has sources beginning with Error to tell the applet when things go wrong16:13
spstarrserviceRequested() ??16:13
aseigospstarr: so engines that care about parameterization implement those methods for parameterized requests, and everyone else ignores it16:13
aseigospstarr: that's not for engines16:13
aseigoChani: engines are naturally async...16:13
aseigoChani: the source is created on demand, but the engine decides when data actually gets shipped back16:13
Chaniaseigo: yes.16:14
spstarrso Plasma::Service is for setting up 'metadata' to the Engine?16:14
aseigoChani: that's why you can return false from sourceRequested16:14
aseigospstarr: no.16:14
aseigospstarr: that's for sending data / commands to services, and has NOTHING to do with engines16:14
Chaniaseigo: it is? I thought false meant "no, we're never creating this source"16:14
* aseigo notes this is also why he wants to separate these things, because everyone gets confused about the differences 16:14
spstarrhehe16:14
aseigospstarr: parameterization will be for setting up metadata to the engine16:14
* randomguy3 urges everyone to make sure what he's dumping into gobby makes sense16:15
spstarri think im gonna need to see an example as to how this all works so i can blow up code16:15
Join hydrogen has joined this channel (n=hydrogen@ignorance.campus.alfred.edu).16:15
jackrabbitrandomguy3; looks right to me16:15
spstarraseigo: that I got :)16:15
aseigoChani: ah, sorry.. right.. reading the api docu it says:16:15
aseigo         * If the source can not be populated with data immediately (e.g. due to16:15
aseigo         * an asynchronous data acquisition method such as an HTTP request)16:15
aseigo         * the source must still be created, even if it is empty. This can16:15
aseigo         * be accomplished in these cases with the follow line:16:15
Quit apol has left this server (Connection timed out).16:15
aseigoso you just create an empty source16:15
Chaniaseigo: ok, so say I send a twitter update to a DataSink, and 30 seconds later the http bit times out. how do I tell the applet?16:16
jackrabbitthrough the data engine16:16
randomguy3serviceUpdated()?16:16
spstarrok then what *is* a Plasma::Service if it's not a dataengine?16:16
Chaniaseigo: ok good, that's what I've been doing, create empty source and return true, but have updateSource always return falssee16:16
aseigoChani: that's why we need to get data back from DataSink, despite fregl's iinitial queasyness ;)16:16
Chanispstarr: it's a data *sink*16:16
spstarror would my WeatherEngine actually be the Service and the ions are the dataengines?16:17
aseigospstarr: it's a place to send data to places, such as a twitter update16:17
Chaniaseigo: if we need to get data back from it, how do we avoid reimplementing 90% of DataEngine?16:17
aseigospstarr: don't think about Service and Engine at the same time =)16:17
randomguy3spstarr: I'm not sure why your weather engine would need a sink at all16:17
randomguy3spstarr: weather info is read-only16:17
aseigoChani: because it has a one-to-one relationship with the visualization, has not timing updates, etc16:17
Chanispstarr: I don't think data sinks are any use to your plasmoid16:18
aseigoChani: it's a much simpler use case.16:18
spstarrrandomguy3: its read-only but you can adjust the 'metrics' of that data only.16:18
freglaseigo: sure, but then I'd like to be able to have multiple applets being notified by the same sink (just to add to that queasyness :p )16:18
Chaniaseigo: ok16:18
randomguy3spstarr: that's just a case of getting different data, not sending it anywhere16:18
aseigoChani: they *might* be useful for validating place names in the weather applet.. dunno yet though16:18
Chaniaseigo: so really we just need some kind of result-thing to connect to?16:18
aseigofregl: that's why Sink provides Service16:18
randomguy3spstarr: it's "passive", in the sense that requesting a service is passive16:18
freglI think maybe subclassing engine would make sense then??16:19
aseigono, that would be silly16:19
randomguy3spstarr: it may create a service, but you don't care whether it has any real effect or not16:19
spstarrrandomguy3: the WeatherEngine itself is pretty small, it merely forwards the applet requests to the ion plugins and passes their data back to the applet16:19
aseigofregl: ok, if you are trying to pass data to multiple sources, that's an engine16:19
aseigofregl: if you are trying to provide interactive data flow, that would be a sink16:19
aseigothe latter is inherently 1:116:19
spstarrrandomguy3: the reason is to keep the 1 : 1 ratio :)16:19
aseigothe former coudl be either, but for reasons that should be obvious at this point, we opted for 1:many16:19
Chaniaseigo: if it just sends out a signal when it's got a result... that could be pretty simple.. just gotta assicoate it with the Service properly16:20
randomguy3spstarr: but my point is that it's a passive mechanism - the applet just asks for data and reads it, so there are no "sinks" involved16:20
spstarrone applet for one weatherengine [multiple data backend sources to choose from]16:20
aseigoChani: right.16:20
freglwell, I imagine one user input effects multiple applets16:20
spstarrrandomguy3: correct16:20
aseigofregl: ok, real world case: twitter16:20
aseigoso ... you have two applets watching two different twitter accounts16:20
aseigoA and B16:20
randomguy3spstarr: but you could, in theory, have two applets displaying the same info, and they would use the same source16:20
freglyes, I see that case16:20
aseigoB's account is set to watch A's updates16:21
spstarrrandomguy3: and they do16:21
freglthen it goes to twitter and back...16:21
Chanifregl: say I send a tewwt to twitter. sure, that'll affect my timeline: but the twitter server will tell the engine about it16:21
freglsure16:21
aseigoapplet A uses a Service to send a tweet16:21
aseigothe engine picks it up when it is available ...16:21
aseigoand both applets show it16:21
spstarrexcept the Q_PROPERTYs of each collides with one another being the same 'unique' key both applets would adjust their properties at the same time16:21
aseigoif we wanted to be extra cute ...16:21
* randomguy3 shrugs, as he has lost track of what he and spstarr were discussing16:21
aseigowe could allow Services to kick Engines to update16:21
spstarrheh16:21
freglaseigo: yes, that's what I want16:22
* hydrogen waves16:22
randomguy3spstarr: oh, yes, changing the metric in one shouldn't change the metric in the other16:22
aseigofregl: can you think of a situation that isn't a specialization of the above A & B, A updates scenario?16:22
aseigohydrogen: at what hertz?16:22
spstarraseigo: actually I *do* need a Service if people would be writing different weather applets16:22
randomguy3spstarr: because that makes it "active"16:22
fregluser enters a word, one applet shows some feedback and another shows that feedback in a different way16:23
randomguy3spstarr: for why?16:23
Chaniaseigo: that would be mildly useful to me: sending a tweet already kicks all hte sources, but hte problem is that the twitter server is usually too slow for it to be useful :)16:23
spstarrrandomguy3: i cant keep track of the differences though, im encountering this now16:23
hydrogenaseigo: a 47 hertz sine wave, to be precise16:23
freglfor example one applet showing a box with 3/20 vocabulary, one giving a sentence liek "your anwer was good" ...16:23
aseigoChani: yes.. another reason i want separation.. it actually makes that *easier* to accomplish in the code16:23
spstarrunless i added  applet ID to the connectSource()16:23
spstarrthen i could keep track of duplicate sources being displayed at once16:24
freglbut if sinks are able to update engines, it sounds perfect to me16:24
Chanispstarr: oh god no16:24
aseigofregl: in particular, i'd want source level resolution16:24
ruphyomg16:24
spstarrso if I load 6 weather applets with Calgary and I wanted to see them all, 'each' one would be unique16:24
ruphystill that prob :D16:24
aseigofregl: so a Service request can kick a specific source16:24
aseigoruphy: it's non-trivial =)16:24
Chanispstarr: why? why?16:24
spstarrChani: i didnt say it was a sane thing :)16:24
hdevalenceI had an idea that might be wrong, but I think it might be interesting.16:25
aseigohdevalence: shoot16:25
Chanispstarr: how about we discuss the weather engine tomorrow?16:25
Chanispstarr: I'd like to chat about it but my brain is turning to slush16:25
spstarrna, im gonna blow things up after this meeting :)16:25
hdevalenceone min, let me type it up16:25
* aseigo notes that the weather engine needs will also be met.. we just need parameterization16:25
Join maxk has joined this channel (n=max@p57A7CAD4.dip.t-dialin.net).16:25
spstarri only bring up my applet cause its the craziest one in Plasma :)16:25
Quit maxx_k has left this server (Connection reset by peer).16:25
aseigo.. and that that is _different_ from services =)16:26
spstarryes that is different16:26
hydrogenaseigo: wrt reviewing.. paleo came across this stuff that we are going to play with for Amarok... it is software that allows fairly in depth code review after commiting, basically a websvn viewer with integrated review stuff16:26
Chaniaseigo: ok, so I think I mostly Get the DataSink thing now. I just hopew someone wrote it up 'caiuse I'll forget by morning16:26
hydrogenhttp://www.atlassian.com/software/crucible/16:26
hydrogenThey give out licenses to open source projects for free16:26
* jackrabbit notes that with this it would be possible to implement knetworkmanager as a dataengine/sink/applet combo16:26
Chaniso, parameterization?16:26
spstarrhydrogen: yes we use their software16:26
spstarrhydrogen: just never used the code reviewer, just the bug/wiki stuff16:26
spstarri didnt know about their code reviewer!16:27
Chanijackrabbit: awesomesauce!16:27
aseigoChani: it's in my head. i'm happy. i'll write it up next week (as in code)16:27
Nick leinir is now known as leinirAWAY.16:27
spstarraseigo: that looks SO nice16:27
Chaniaseigo: sweet :)16:27
Quit Eren has left this server (Remote closed the connection).16:27
spstarrdanke aseigo :)16:27
spstarrbut i will begin removing Q_PROPERTY and that will drop LOC16:28
Chaniaseigo: I have another twitter refactor planned Real Soon Now, so once I've done that I'll start using hte datasink16:28
aseigohydrogen: i met one of the guys who works there at l.c.a16:28
aseigohydrogen: he said he could get us full licenses for free16:28
Chaniaseigo: your australia presentation made me realise why I hated my userimage handling and how to solve it16:28
spstarraseigo :) we can get it cause KDE is FLOSS.16:28
aseigohydrogen: ah, i see you noted that already16:28
randomguy3does my description of the distinction between services and engines look right?16:29
hydrogenmm16:29
hdevalencewe make a bunch of applets that are simple, generic visualizations -- stuff like line graph, chart, bar graph, pies, etc etc. then we have a set of 'intermediate' things that process stuff and then we connect it all to to data engines with a gui. So the user connects the dataengines to the ``processors'' and then set some kiund of simplified rules to process it, and then connect that to the visualizations. Kinda like pipes on a16:29
hdevalenceunix shell, but easier to use.16:29
hydrogenI was playing with it yesterday.. It is fairly impressive16:29
* Chani wanders over to goobby16:29
aseigohdevalence: yes, we'll eventually need to go there.. with engine and visualization you already get much of that if there was a gui designer16:30
ruphyChani: ?16:30
aseigohdevalence: processors would simply make it even nicer to do post-processing / amalgamation / etc of data16:30
Quit rui has left this server (Remote closed the connection).16:30
aseigohydrogen: my only real concern with it is that it is non-free...16:31
Chaniruphy: what?16:31
aseigohydrogen: honestly, i'd prefer to stick with Free software options as long as they exist16:31
Quit dirk|home has left this server (Remote closed the connection).16:31
hdevalencei for one would rather not have another blowup like what happened with (bitkeeper?) and the linux kernel16:32
* Chani finishes her tea16:32
Chaniare we gonnna talk about this parameterization thing?16:33
Quit nogden has left this server (Remote closed the connection).16:33
jackrabbithdevalence: there is a big difference between this and bitkeeper though16:33
Quit hydrogen has left this server ("Konversation terminated!").16:33
Chanior is the meeting over?16:33
aseigoyes, i think so..16:34
* aseigo can't go on at thi spoint.. needs to go..16:34
* aseigo bangs the gavel again, just to be officious16:34

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