**** BEGIN LOGGING AT Wed Jul 24 02:59:59 2013 **** BEGIN LOGGING AT Wed Jul 24 05:27:42 2013 Jul 24 08:14:02 morning Jul 24 08:14:42 I'm just looking around quickly, I'm still on vacation :) Jul 24 08:15:04 Next 4 days without internet will be a challenge :p Jul 24 08:16:54 morphis: I'm still hesistating to put the normal/max/fullscreen transitions in the window container class; it just looks weird, don't you think ? Jul 24 08:18:17 I would like to put it in the compositor somehow, outside any specific window code, but right now I don't see how to write it with nice states and transitions. I'll work on that. Jul 24 08:18:27 (it the tofe/architecture-work branch) Jul 24 08:20:50 I saw you added a task for the swipe management in the gesture area; fine by me, but simply not that week, of course :) Jul 24 08:40:02 JaMa, morphis: My rm_work build went through yesterday with only a hack in ca-certificates Jul 24 08:40:23 So my earlier rm_work problems have indeed been something different Jul 24 08:40:51 still ca-certifcates is strange to my. Looked into it for some time but did not spot anything Jul 24 08:41:30 for now I wroked aorund it with do_install stub. Thus not doing the normal make install and it goes through. Jul 24 08:42:03 Will look into it again this evening. I suspect its something with my host system as it seems to work fine for you folks Jul 24 08:45:19 stefan_schmidt_w: whats the problem with ca-certificates? don't remember it :) Jul 24 08:45:51 morphis: do_install fails without any real error message in stdout or the log file Jul 24 08:46:20 maybe some of my autofoo things are to new in debian unstable Jul 24 08:46:32 Or are we building all that natively in oe by now Jul 24 08:46:44 It feels like something leaks in from my host Jul 24 08:47:11 its just hard to figure out because it gives no real error :) Jul 24 08:50:12 Not really a priority issue anyway. But I want to understand whats going wrong Jul 24 08:50:54 morphis: did you run those jenkins builds for me? :) Jul 24 08:53:15 queued now :) Jul 24 09:05:46 JaMa: oh, sorry Jul 24 10:17:42 morphis: Just beause it came up recently somewhere else. You folks run wayland (qtwayland) on libhybris, right? Jul 24 10:17:56 Any problems with that? Jul 24 11:38:52 stefan_schmidt_w: no, it's working quite fine Jul 24 12:21:34 anything special you did to set it up? Jul 24 12:25:17 morphis: ^ Jul 24 12:32:34 stefan_schmidt_w: in OE or in general? Jul 24 12:37:31 in general Jul 24 12:38:36 morphis: libhybris does provide the needed egl stuff to make wayland happy? Jul 24 12:38:42 yes Jul 24 12:38:51 in general you don't have to do that much Jul 24 12:39:04 compile libhybris with --enable-wayland and you should have everything you need Jul 24 12:39:29 for the compositor you have to set then either EGL_PLATFORM=fbdev or EGL_PLATFORM=hwcomposer and for a client EGL_PLATFORM=wayland Jul 24 12:39:30 ah, there is even a flag for it Jul 24 12:39:31 thats all Jul 24 12:39:33 yes Jul 24 12:39:40 cool, thx Jul 24 12:39:52 and I know some people already have it working with efl Jul 24 12:40:36 for more info just join #libhybris Jul 24 12:40:46 ah cool Jul 24 12:40:57 is this a guy called cedric? Jul 24 12:41:28 no Jul 24 12:41:34 heh, ok Jul 24 12:41:39 s/no/yes/ Jul 24 12:41:57 heh Jul 24 12:41:58 and groleo is working from the Intel site on Tizen Jul 24 12:41:59 ok Jul 24 12:42:14 why would they be interested in libhybris Jul 24 12:42:16 hmm Jul 24 12:42:23 maybe due to the PVR mess Jul 24 12:47:36 Hello Jul 24 12:48:13 morphis - you here? Jul 24 12:50:11 WhiteBee: yes Jul 24 12:50:32 stefan_schmidt_w: don't know but it offers a well defined solution to reused android drivers Jul 24 12:50:49 Hi, I was here about a month or two ago, asking to help with applications development Jul 24 12:51:13 can't remember who I spoke with. I didn't have time to do work, but I snooped around and have some questions Jul 24 12:51:15 WhiteBee: yeah, saw your talk with ka6sox-away tonight Jul 24 12:51:22 great Jul 24 12:51:31 morphis: yeah, sure. Was just wondering because Intel does all the graphics stuff internal and also are the driving force behind wayland Jul 24 12:52:04 WhiteBee: just ask Jul 24 12:52:11 so I was looking at the contacts app which I've been told needs coding Jul 24 12:52:37 and seeing other contacts/people apps, a lot are showing extended functionality like social network integration. Jul 24 12:53:09 should it have such features, or just be a copy of the original app? Jul 24 12:53:39 that's a good point. Jul 24 12:53:45 WhiteBee: maybe start small with a basic contact app Jul 24 12:53:53 And then improve it over time Jul 24 12:54:00 perhaps it could be modular? Jul 24 12:54:03 WhiteBee: yeah, just start with the basic features Jul 24 12:54:03 WhiteBee: you might check out #macdev Jul 24 12:54:12 Always to have some nice feedback in a short period of time Jul 24 12:54:30 ok. another question Jul 24 12:54:37 what's wrong with the enyo 1 app? Jul 24 12:54:45 no support for enyo 1 in owos? Jul 24 12:54:49 no Jul 24 12:54:55 enyo 1 is supported Jul 24 12:54:55 ok Jul 24 12:54:58 oh Jul 24 12:55:03 but it's outdated and will not be updated anymore Jul 24 12:55:21 so everything new has to be based on enyo 2 Jul 24 12:55:48 also the enyo1 app doesn't scale for different resolutions Jul 24 12:56:19 WhiteBee: but you can reuse a lot code if you want Jul 24 12:56:41 ok Jul 24 12:57:00 all in all it should be a drop in replacement Jul 24 12:57:23 so start small with further features in mind, replacing current functionality, then add features as time goes Jul 24 12:58:56 exactly Jul 24 12:58:57 I will do a little design and start actual code later. Will fork the enyo1 from webos-ports repo Jul 24 12:59:10 ok Jul 24 12:59:22 WhiteBee: sounds like a good plan to me Jul 24 12:59:23 WhiteBee: we can create a new repository on github for the app Jul 24 12:59:38 that'll be better - I'll fork that one Jul 24 12:59:41 WhiteBee: and for the structure you can just look at the other enyo 2 apps which are already there Jul 24 12:59:43 That way you get feedback way earlier Jul 24 12:59:57 yep Jul 24 13:00:11 WhiteBee: thank you for taking on this task. this is the only way webos will continue to survive and hopefully thrive again some day Jul 24 13:00:11 last question - what's a good irc client =P (windows and linux) Jul 24 13:00:15 And we have a contacts app earlier :) Jul 24 13:00:20 WhiteBee: i like quassel on linux Jul 24 13:00:26 on linux I use xchat Jul 24 13:00:27 WhiteBee: https://github.com/webOS-ports/org.webosports.app.contacts Jul 24 13:00:32 no idea under windows Jul 24 13:00:46 xchat2 in windows. or mirc, if you're feeling 1999-ish Jul 24 13:01:08 mirc, that brings up memories Jul 24 13:01:27 WhiteBee: just provide a PR once you have something to show Jul 24 13:01:27 ok, I'll download the client and be back Jul 24 13:01:36 ok Jul 24 13:01:47 thanks guys, ttyl Jul 24 13:01:53 cu Jul 24 13:02:05 good luck. make sure you leverage the resources in #enyojs if you have questions Jul 24 13:02:47 HaDAk: to late :) Jul 24 13:03:26 morphis: i turned off join/part because it was flooding out relevant chatter Jul 24 13:03:27 >.> Jul 24 13:03:37 :) Jul 24 13:06:06 morphis: thanks for that comment about PR server :) Jul 24 13:06:26 JaMa: just another voting voice? :) Jul 24 13:38:48 Tofe|Away: btw. you can now start to use features from qt 5.1.0 again Jul 24 13:45:09 :) Jul 24 13:45:33 JaMa: any plan when you will merge 5.1.0 to master? Jul 24 13:45:39 morphis: should I push that branch to master or wait a bit more for possible runtime issues? Jul 24 13:45:42 :))) Jul 24 13:45:42 (in meta-qt5) Jul 24 13:45:51 :9 Jul 24 13:45:58 s/:9/:) Jul 24 13:46:05 no it works fine for me at runtime Jul 24 13:46:11 there is conf-call tonight I'll probably merge it after that Jul 24 13:47:23 ok Jul 24 17:18:02 dkirker: hi Jul 24 17:18:27 dkirker: if I read the webosnations forum right you wanted to pick the carddav/caldav synergy connectors and put them on github Jul 24 17:18:34 dkirker: did that happen already? Jul 24 17:19:05 I might have some interest looking into these. Jul 24 17:19:13 Not sure if it will really happen tho :) Jul 24 17:21:33 JaMa: I made some progress with my OE webos setup here. rm_work is now working fine and thanks to your meta-qt update that part is also building fine Jul 24 17:21:59 Only problem left is the ca-certificates do_install problem. I still have no clue about that Jul 24 17:22:47 JaMa: Do we use a OE specific automake-native for these or could it be a problem with my host automake stuff Jul 24 17:23:08 stefan_schmidt: yeah you read it right Jul 24 17:23:21 stefan_schmidt: dkirker was asking on the forum once ago after we discussed it here Jul 24 17:23:32 Debian unstable is on 1.13.3 here and I wonder if other distros are behind Jul 24 17:23:49 as automake is somehow known for causing trouble with every new release Jul 24 17:23:56 morphis: ok, cool Jul 24 17:24:25 stefan_schmidt: ok, I have 1.11.6 of automake here Jul 24 17:24:31 with Ubuntu 13.04 Jul 24 17:24:38 jup Jul 24 17:24:44 so can be too new :) Jul 24 17:24:46 no distro really likes to update it Jul 24 17:24:49 breaks to much Jul 24 17:25:05 I'm just not sure if OE should have its own automake native avoiding that Jul 24 17:25:16 Could have changed since I worked with it the last time Jul 24 17:25:53 ah, wait Jul 24 17:26:08 IIRC debian has older version of it and I can switch. Jul 24 17:26:15 * stefan_schmidt goes and checks his theory Jul 24 17:27:30 stefan_schmidt: afaik our setup should be a automake-native Jul 24 17:28:39 morphis: hmm Jul 24 17:28:48 Going to test my theory anyway I think :) Jul 24 17:29:40 stefan_schmidt: Yes and no. They are in a private repo I created, I think just before asking. Need to make it public. Jul 24 17:30:02 dkirker: ok Jul 24 17:30:16 dkirker: personal private or owop? Jul 24 17:30:21 dkirker: no real rush. I was just going to chekc if there is a repo for it Jul 24 17:30:57 dkirker, stefan_schmidt: but if we have them and can make them public we should do know before anyone forgets about it :) Jul 24 17:31:16 personal private Jul 24 17:31:57 ok Jul 24 17:32:37 dkirker: I really have no idea when I have time for it. But it kinda is an important thing for me if I ever want to use Webos for something else then toying around Jul 24 17:35:04 dkirker: so whenever you find the time to make it public let me know. I think I will at least have a look at the code Jul 24 17:36:30 ok, automake to new theory did not work out :) Jul 24 17:36:40 I think I was also asking about another implementation that wasn't as complete, but more built out in terms of extensibility? That guy never responded, IIRC... Jul 24 17:37:09 morphis: When you have a moment could you check if you can really build ca-certificates. Not from sstate but really all on your system Jul 24 17:37:57 dkirker: Seems its the only stuff we have Jul 24 17:38:09 As I read it was mostly the contacts example Jul 24 17:38:22 gm Jul 24 17:38:34 stefan_schmidt: will check Jul 24 17:38:37 I was wondering what he used for the actual carddav part. Doing js on its own or some lib Jul 24 17:38:43 EricBlade: gm Jul 24 17:38:46 EricBlade: morning Jul 24 17:39:05 stefan_schmidt: This is the one that I have: http://forums.webosnation.com/webos-synergy-synchronization/284289-carddav-connector-very-very-very-alpha.html Jul 24 17:39:09 dkirker: There seem to be some carddav/calddav js libs but I really have no clue about them. Jul 24 17:39:20 stefan_schmidt: still researching? Jul 24 17:39:36 First time getting my hands dirty with js at all. Which is kinda why I hesitate :) Jul 24 17:39:52 dkirker: yes, thats the one I was talking about Jul 24 17:40:05 EricBlade: Just started again :) Jul 24 17:40:11 yeah, there are a few node carddav and caldav implementations. I think I have starred them and/or cloned them. Jul 24 17:40:21 EricBlade: Trying to get an idea what is out there and maybe useful Jul 24 17:40:25 if you're thinking about diving in with a node service, i'd like to suggest that maybe you should avoid using the formerly recommended "Futures" or other "Foundations" functions whenever possible. Strong likelihood that they will go the way of Mojo someday. Jul 24 17:41:04 stefan_schmidt: https://github.com/dkirker/webos-carddav Jul 24 17:41:15 dkirker: cool Jul 24 17:41:39 dkirker: thanks a lot! Jul 24 17:41:49 EricBlade: IIRC, Futures is not a proprietary thing. Right? Jul 24 17:42:09 probably can't avoid using Foundations for system calls right now, but there are certainly better/easier to work with implementations of futures-like things in the Node world Jul 24 17:42:49 I would imagine so. The futures complexity melts my brain every time.... Jul 24 17:43:23 so i'd suggest trying to avoid futures except when absolutely necessary (i think system calls use them, but that's not too terribly complex on their own) Jul 24 17:43:33 stefan_schmidt: This does CardDAV only, it seems. The reason I had left it private is because the code is still pretty dirty, and makes references to the old webOS example (so I think the app/service name and icons are wrong). Jul 24 17:44:27 "Silly rabbit, Futures are for witches and warlocks!" :P Jul 24 17:45:15 dkirker: yeah Jul 24 17:45:27 dkirker: I wonder what the license situation with this one is Jul 24 17:45:34 does the code have a license? Jul 24 17:46:13 stefan_schmidt: no idea. You'd have to ask. Apache I'd assume (or whatever SDK example code is), since it is based on code distributed from Palm. Jul 24 17:46:19 I'm not a lawyer.... Jul 24 17:46:35 sure sure Jul 24 17:46:43 I just wonder if he said anything Jul 24 17:46:52 the code from the sdk should be no problem anyway Jul 24 17:47:03 Was more thinking about the code he added for carddav Jul 24 17:48:58 I want to use this one: http://forums.webosnation.com/webos-synergy-synchronization/320711-carddav-caldav-connector.html Jul 24 17:49:04 can't seem to get a hold of Czo Jul 24 17:50:41 stefan_schmidt: OE's autoconf and automake Jul 24 17:50:45 try running it by hand and check exit code Jul 24 17:53:50 JaMa: going into the work dir and sourcing the run.do_install gives me a 0 as exit code Jul 24 17:54:37 hmm, should I be in the old dir or in one of the dirs beside the staged image structure at the end? Jul 24 17:54:49 I ended up in /etc/ssl/certs Jul 24 17:55:16 within the package workdir Jul 24 17:56:20 dkirker: that sounds also promising. Sad that no reply came back Jul 24 17:57:57 stefan_schmidt: I sent a PM again. doubt I'll hear back. We'll see. Jul 24 17:58:16 dkirker: ok Jul 24 19:57:54 stefan_schmidt: ah and ca-certificates build fine here Jul 24 19:58:11 morphis: *sigh* **** ENDING LOGGING AT Thu Jul 25 02:59:58 2013