**** BEGIN LOGGING AT Wed Aug 14 02:59:59 2013
Aug 14 05:27:57 <morphis> morning
Aug 14 05:28:00 <morphis> JaMa: http://bpaste.net/show/8vXAYm9QyHBt618FSIhP/
Aug 14 06:24:25 <JaMa> morphis: sorry about that, looks good
Aug 14 06:24:55 <JaMa> morphis: I've added the same file in .bbappend and only just before pushing I've noticed that I forgot to edit UID_MIN
Aug 14 06:40:48 <morphis> :)
Aug 14 06:45:01 <morphis> JaMa: you know wether qtbase requires gstreamer 0.10 or 1.0?
Aug 14 06:48:28 <morphis> JaMa: and it seems to be not important for us to enable gstreamer in qtbase but we need it for qtwebkit
Aug 14 06:55:55 <JaMa> morphis: IIRC it supports both and it should prefer 1.0 when both are available, but I think that configure detection for 1.0 doesn't work
Aug 14 06:56:16 <JaMa> morphis: because in my test-dependencies.sh build it never picked dependency on 1.0 even when it was available
Aug 14 06:56:23 <morphis> hm
Aug 14 06:56:46 <morphis> afaik qtbase doesn't use gstreamer in anyway and it's only a leftover in the configure script
Aug 14 06:57:10 <morphis> qtmultimedia should be the one which uses gstreamer
Aug 14 06:57:13 <morphis> and qtwebkit does
Aug 14 06:57:57 <morphis> JaMa: there is no virtual provider for gstreamer, right? just gstreamer (0.10) and gstreamer1.0?
Aug 14 06:57:58 <JaMa> true e.g. openal auto-detection in qtmultimedia sucks
Aug 14 06:58:26 <JaMa> right, in most cases they aren't interchangable, so nobody created provider
Aug 14 06:59:34 <morphis> ok
Aug 14 06:59:41 <morphis> then lets blacklist gstreamer 0.10
Aug 14 07:00:04 <morphis> I would like to avoid having the error case when both are installed
Aug 14 07:00:21 <morphis> they can be installed in parallel but thats not required for us
Aug 14 07:04:06 <JaMa> sounds reasonable
Aug 14 07:04:25 <JaMa> maybe I can add another PACKAGECONFIG with 1.0 dependency (but same config options as 0.10)
Aug 14 07:04:58 <morphis> https://github.com/webOS-ports/meta-webos-ports/commit/c5512ebb82bb1a0b7cd362acc02921eea02713e4
Aug 14 07:14:47 <JaMa> morphis: please blacklist also all 0.10 plugin recipes
Aug 14 07:15:13 <JaMa> it will show much clearer error when something will depend on them
Aug 14 07:15:24 <morphis> JaMa: oh yes
Aug 14 07:18:12 <JaMa> morphis: I'm sorry I remember it incorrectly, qtbase is checking only for 0.10, I've seen 1.0 detection in some other qt5 package, probably webkit or multimedia
Aug 14 07:18:36 <morphis> JaMa: qtwebkit has an explicit check for it
Aug 14 07:18:49 <morphis> and qtmultimedia should have it too
Aug 14 07:19:41 <JaMa> Source/WebCore/WebCore.pri
Aug 14 07:19:57 <JaMa> qtmultimedia has only auto config.test
Aug 14 07:20:01 <JaMa> IMHO
Aug 14 07:20:43 <morphis> JaMa: ok
Aug 14 07:22:50 <morphis> JaMa: updated blacklist pushed, will check wether things are building fine now
Aug 14 10:17:28 <JaMa> morphis: luna-service2 should depend on systemd, right? | --   package 'libsystemd-daemon' not found
Aug 14 10:48:17 <morphis> JaMa: ah yes
Aug 14 10:48:49 <morphis> JaMa: will add the dependency
Aug 14 10:50:23 <JaMa> I already did
Aug 14 10:50:55 <JaMa> Only issue in builds now is that libhybris as well as mesa are built for qemuarm
Aug 14 10:51:01 <JaMa> built and installed
Aug 14 11:04:25 <morphis> hm
Aug 14 11:04:39 <morphis> what is pulling libhybris in for qemuarm?
Aug 14 11:05:51 <morphis> JaMa: and please tell what you think about: http://bpaste.net/show/bPlmhqgb4N7DYLm4xEhR/
Aug 14 11:07:41 <JaMa> morphis: we need to explicitly disable config.test for them when they aren't added in DEPENDS, but can be already staged in sysroot
Aug 14 11:07:57 <JaMa> see qtmultimedia openal check, it's ugly but seems to be working
Aug 14 11:10:16 <morphis> JaMa: yeah, I didn't implement this yet
Aug 14 11:10:48 <morphis> was just a quick add to the recipe but the config.test modification needs to be added
Aug 14 11:13:11 <morphis> JaMa: we can't mark two PACKAGECONFIG options as conflicting, right?
Aug 14 11:13:31 <JaMa> no, only by comment in .bb
Aug 14 11:22:58 <morphis> JaMa: hm, does it make sense to offer support for gstreamer 0.10 for qtwebkit anyway?
Aug 14 11:24:12 <JaMa> yes if it isn't too much work, some people are using meta-qt5 master with oe-core dylan
Aug 14 11:25:35 <morphis> ok, let me find a good way for i
Aug 14 11:25:43 <morphis> s/for i/for it/
Aug 14 11:35:10 <morphis> JaMa: http://bpaste.net/show/epJmQ1tHtg1UZsl5gpLw/
Aug 14 11:35:19 <morphis> need to test it but should work
Aug 14 11:38:38 <morphis> JaMa: <morphis> what is pulling libhybris in for qemuarm?
Aug 14 11:49:36 <JaMa> morphis: sorry I'm still waiting for build to finish to use bitbake -g
Aug 14 11:49:46 <morphis> ok
Aug 14 12:15:32 <JaMa> morphis: quite a few http://bpaste.net/show/122976/
Aug 14 12:16:02 <morphis> hm but those are seem related to libEGL/libGLES
Aug 14 12:16:39 <JaMa> looks like qtbase is root cause for that
Aug 14 12:17:04 <morphis> yeah
Aug 14 12:17:08 <JaMa> qtbase is the only one having buildtime dependency
Aug 14 12:18:04 <JaMa> interesting that yesterday I was debuging oposite issue, no dependency on virtual/libgl when it's added through PACKAGEGROUP :)
Aug 14 12:18:07 <JaMa> PACKAGECONFIG
Aug 14 12:27:22 <morphis> :)
Aug 14 12:27:56 <JaMa> testing if setting PREFERRED_PROVIDER_virtual/egl for qemu is enough
Aug 14 12:28:10 <JaMa> load average: 20.66, 15.99, 13.41
Aug 14 12:28:18 <JaMa> will take a while even for -g to finish :)
Aug 14 12:34:19 <JaMa> seems to be working
**** BEGIN LOGGING AT Wed Aug 14 16:42:31 2013
Aug 14 17:43:00 <ka6sox> morning
Aug 14 17:43:25 <Herrie> ka6sox: Morning ;)
Aug 14 17:44:13 <ka6sox> okay time to see if I can get anything done today
Aug 14 17:49:11 <Herrie> Dodm
Aug 14 17:49:25 <Herrie> Didn't get much done today, was a bit busy, but reordered this one :) http://webos-ports.org/wiki/Contributors
Aug 14 18:41:15 <Garfonso> morning
Aug 14 18:41:54 <morphis> Garfonso: hey
Aug 14 19:13:10 <WhiteBee> Hello
Aug 14 19:13:37 <WhiteBee> someone can tell me if OWOS apps has the same UI as webos 3?
Aug 14 19:13:46 <WhiteBee> or is it a different one?
Aug 14 19:15:26 <morphis> WhiteBee: you mean the same application framework?
Aug 14 19:16:37 <morphis> OWO and webos 3.x both have enyo1
Aug 14 19:52:16 <WhiteBee> morphis: I want to start writing the contacts app, which will be replicating the existing OWO one in enyo2
Aug 14 19:52:38 <WhiteBee> but I want to play with it first, and I don't want to comiple luna
Aug 14 19:52:43 <WhiteBee> compile*
Aug 14 19:53:01 <WhiteBee> so I guess if they have the same UI I'll get myself a webos 3 emulator
Aug 14 19:53:39 <morphis> WhiteBee: yes that would be a good start
Aug 14 19:54:15 <morphis> for recreating the app in enyo2 you can take https://github.com/webOS-ports/org.webosports.app.calendar as good reference
Aug 14 19:54:29 <WhiteBee> thing is I want to use it
Aug 14 19:54:42 <WhiteBee> without compiling luna
Aug 14 19:54:53 <morphis> WhiteBee: you can also recreate the contacts app and use it in webOS 3.x
Aug 14 19:55:28 <WhiteBee> morphis: no, no got me wrong. Before I recreate the app, I want to use it
Aug 14 19:55:42 <morphis> ok
Aug 14 19:55:57 <WhiteBee> but if the one in 3.x is outdated I will have to compile luna to try the new app that comes with open webos
Aug 14 19:56:06 <morphis> JaMa: with libhybris not pulled in anymore can we reenable the build for qemux86?
Aug 14 19:56:09 <WhiteBee> but if its not - great, I'll get an emulator
Aug 14 19:56:21 <morphis> emulator should be fine
Aug 14 19:56:34 <WhiteBee> ok. next question - where can I get the 3.x emulator P=
Aug 14 19:57:30 <JaMa> morphis: yes that's my plan :)
Aug 14 19:58:34 <morphis> JaMa: ok, could we run a qemux86 build in vbox for example?
Aug 14 19:59:45 <JaMa> it should work the same as in upstream Open webOS builds, maybe I'll have to enable .vmdk format, IIRC I've disabled it because it was taking a lot spaces
Aug 14 19:59:56 <morphis> JaMa: what I thinking about is having a target which is not a device to run our wayland based compositor
Aug 14 20:00:07 <JaMa> I'll look after first successfull qemux86* build
Aug 14 20:00:13 <morphis> ok
Aug 14 20:00:35 <morphis> that would make it easier for people like WhiteBee to develop apps based on the current UI
Aug 14 20:00:54 <JaMa> agreed, I'm also using qemux86-64 SHR images, because it's faster to "reflash" and test new image then reflashing phones
Aug 14 20:01:28 <morphis> yes
Aug 14 20:01:41 <morphis> that could improve our development workflow a lot
Aug 14 20:02:03 <morphis> JaMa: btw. I will drop the android-audiosystem soon
Aug 14 20:02:16 <WhiteBee> Ok, so I didn't actually get anything XD
Aug 14 20:02:21 <JaMa> np, I was fixing it only because it was trippng my dependency tests :)
Aug 14 20:09:03 <morphis> WhiteBee: we're doing our best to get this out :)
Aug 14 20:10:29 <Garfonso> WhiteBee: the sdk download links disappeared form the official HP webpage some weeks ago. There is a post in the webos nation forums that has the links (the files are still on the server, only the webpage is gone).
Aug 14 20:11:19 <Garfonso> do you know the emulator? Important buttons: pos = up swipe, esc = back gesture (more important for phones ;))... and sometimes the right shift does not work for me.
Aug 14 20:12:01 <Garfonso> if you work only on GUI parts you can run the app also in a (webkit)-browser. Makes development a bit easier.
Aug 14 20:16:03 <Garfonso> btw: got rid of the node.js module for xml => json conversion and now using webos internal stuff.. :)
Aug 14 20:16:57 <morphis> Garfonso: yeah :)
Aug 14 20:17:11 <morphis> Garfonso: we're need a enyo2 rewrite of the accounts app too :)
Aug 14 20:18:00 <Garfonso> I suck very much on GUI... still struggling with preware 2 settings :(
Aug 14 20:18:06 <morphis> :)
Aug 14 20:28:23 <WhiteBee> Garfonso: yes, there it is http://forums.webosnation.com/webos-development/325645-looks-like-you-cant-get-sdk-anymore-almost.html
Aug 14 20:28:45 <WhiteBee> thanks
Aug 14 20:30:54 <morphis> Garfonso: as you're doing some application and js work:
Aug 14 20:31:23 <morphis> I am currently rework the webappmanager and need to recreate the several specific webOS API's
Aug 14 20:31:57 <morphis> my current approach will require every app to include a js file provided by the system
Aug 14 20:32:14 <morphis> without it the app can't access the PalmSystem or connect to ls2 services
Aug 14 20:32:38 <morphis> do you see any problem with having an additional webos specific script include?
Aug 14 20:34:03 <Garfonso> what kind of file/script?
Aug 14 20:34:48 <Garfonso> would be good if it would be easy stuff.. ;)
Aug 14 20:41:37 <JaMa> morphis: I wonder why last master builds are all failing with | ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored.
Aug 14 20:41:57 <JaMa> it's working for me locally only jenkins has this issue
Aug 14 20:42:21 <morphis> Garfonso: will look like this: http://bpaste.net/show/H1VrFeiErdas8UzLdXZM/
Aug 14 20:43:00 <morphis> Garfonso: it will handle the communication between the app process (we're using webkit2 so every app gets its own process) and the webappmanager
Aug 14 20:45:20 <morphis> Garfonso: without having this nothing of the webOS specific API's will work
Aug 14 20:47:51 <Garfonso> does that require changes for every app? Or will it mostly stay constant?
Aug 14 20:52:11 <morphis> Garfonso: only every app as to include one line like: <script src="/usr/palm/frameworks/webos/webos.js"/>
Aug 14 20:52:14 <morphis> nothing more
Aug 14 20:52:22 <morphis> s/app as/app has/
Aug 14 20:55:37 <morphis> Garfonso: injecting the script is hard work which I would like to avoid
Aug 14 20:56:55 <Garfonso> oh, that's fine I think. :)
Aug 14 20:57:17 <WhiteBee> emulator up and running, thanks guys.
Aug 14 20:57:25 <Garfonso> WhiteBee: great. :)
Aug 14 20:58:24 <morphis> Garfonso: ok
Aug 14 20:58:37 <morphis> Garfonso: just wanted to hear another opinion about this :)
Aug 14 21:46:38 <morphis> JaMa: hm, I have it too:  ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored.
Aug 14 21:47:00 <morphis> WhiteBee: when you have any questions, just ask :)
Aug 14 21:47:15 <WhiteBee> morphis: cool, will do
Aug 14 21:47:31 <morphis> we should mostly be able to answer any questions :)
Aug 14 21:48:52 <WhiteBee> morphis: When I think about it, I actually have some
Aug 14 21:49:15 <WhiteBee> first one - the enyo1 app is tablet only, right?
Aug 14 21:49:29 <WhiteBee> (contacts)
Aug 14 21:49:33 <Garfonso> probably yes
Aug 14 21:49:43 <WhiteBee> ok
Aug 14 21:49:46 <Garfonso> maybe it is possible to run it on the phone also..
Aug 14 21:50:01 <Garfonso> enyo 1 got transfered to the phones mostly...
Aug 14 21:50:06 <WhiteBee> yeah, but it's not responsive in any way, right?
Aug 14 21:50:13 <WhiteBee> you'll still get tablet layout
Aug 14 21:50:20 <Garfonso> but apps need a bit of careful design to work on the smaller screen.
Aug 14 21:51:10 <Garfonso> let me have a look.. hm.. it got two panels.. might work on a phone.
Aug 14 21:51:21 <WhiteBee> ok
Aug 14 21:51:36 <WhiteBee> second question - why enyo?
Aug 14 21:51:44 <Garfonso> usually the apps then only show one of the panels in full screen and you navigate via selection / back gestures
Aug 14 21:52:02 <WhiteBee> oh, just like onyx.
Aug 14 21:52:14 <Garfonso> e-mail app from the tablet definitively works on phones. ;)
Aug 14 21:52:25 <morphis> Garfonso, WhiteBee: the apps works on the galaxy nexus it's just not scaling for the different form factors
Aug 14 21:52:40 <Garfonso> ah. :)
Aug 14 21:53:27 <Garfonso> WhiteBee: what do you mean by "why enyo"?
Aug 14 21:54:43 <WhiteBee> Garfonso: well, there are a lot of great web frameworks which work great on phones, and enyo is lacking a bit behind
Aug 14 21:54:52 <WhiteBee> especially with data handeling
Aug 14 21:55:14 <WhiteBee> handling*
Aug 14 21:55:55 <morphis> WhiteBee: in general it's historic
Aug 14 21:56:10 <morphis> enyo was the new big thing which came with the touchpad and 3.x
Aug 14 21:56:30 <morphis> and then the story goes still on with LG refining things within enyo2
Aug 14 21:57:12 <morphis> I like enyo2 pretty much as you don't have to care about html with it
Aug 14 21:57:24 <morphis> but I am really not the web or UI boy :)
Aug 14 21:57:28 <Garfonso> yeah, that's true.
Aug 14 21:57:35 <WhiteBee> lol, I'm in for angular P=
Aug 14 21:59:02 <Garfonso> actually, there is no real need for enyo2... but I think we should keep a consistent look and feel as much as possible (and keep it similar to the old days, so people get that nostalgic feeling ;))... I guess that's easier using enyo. But if you can resemble that with something else, might be fine, too.
Aug 14 21:59:02 <morphis> angular?
Aug 14 21:59:18 <WhiteBee> angularjs.org
Aug 14 21:59:22 <WhiteBee> www.angularjs.org
Aug 14 21:59:46 <morphis> as long as the code keeps maintainable and understandable by others it's really irrelevant for me in which framework the apps are written
Aug 14 21:59:47 <WhiteBee> writing an app that has two panels and shows contacts from a json file will take about an hour to do
Aug 14 21:59:56 <morphis> but I would like to have a consistent way for the core apps
Aug 14 22:00:27 <morphis> WhiteBee: I doubt thats no problem with enyo2 too
Aug 14 22:00:37 <WhiteBee> you just write the html for how it looks and add about 10-20 LoC
Aug 14 22:00:42 <morphis> the real problem for the contacts app comes with the access to the data storage etc.
Aug 14 22:00:55 <WhiteBee> right, that's the thing
Aug 14 22:01:07 <morphis> WhiteBee: you looked through the source of the already existing webos-ports enyo2 apps?
Aug 14 22:01:28 <morphis> WhiteBee: but I am fine with having an app with stubed data for the first time
Aug 14 22:01:39 <morphis> or an abstracted interface to access the storage
Aug 14 22:02:17 <Garfonso> ok, really need to go to bed now. good night. :)
Aug 14 22:02:20 <morphis> but I still see enyo2 the way to go for the core apps to have them consistent
Aug 14 22:02:24 <morphis> Garfonso: n8
Aug 14 22:02:31 <WhiteBee> morphis: Nope, just read the enyo2 docs a while ago and the enyo1 app
Aug 14 22:02:35 <WhiteBee> Garfonso: good night
Aug 14 22:03:10 <WhiteBee> morphis: ok, will write using enyo
Aug 14 22:03:28 <morphis> WhiteBee: ok
Aug 14 22:03:47 <morphis> WhiteBee: Garfonso might be a good help with accessing the contacts storage
Aug 14 22:04:45 <WhiteBee> morphis: I think I'll just have the ui first and then add the data, so for now just building the front end
Aug 14 22:05:46 <morphis> great
Aug 14 22:05:56 <morphis> that should be easy doable inside a normal browser
Aug 14 22:06:05 <morphis> and maybe until then we have a emulator working
Aug 14 22:07:56 <WhiteBee> fantastic
Aug 14 22:09:08 <morphis> WhiteBee: when you have something just provide a PR against the repo on github
Aug 14 22:09:40 <morphis> and as often as possible so your work doesn't get lost
Aug 14 22:10:01 <morphis> and once there is something visible I will integrate the app into the build
Aug 14 22:11:43 <WhiteBee> morphis: this: https://github.com/webOS-ports/org.webosports.app.contacts?
Aug 14 22:12:08 <morphis> exactly
Aug 14 22:12:13 <WhiteBee> ok
Aug 14 22:13:20 <morphis> WhiteBee: https://github.com/webOS-ports/webos-ports-lib might be worth to look at too
Aug 14 22:15:09 <morphis> ok, too late for me
Aug 14 22:15:12 <morphis> gn8
Aug 14 22:15:30 <WhiteBee> morphis: gn, I'll take a look
Aug 14 22:26:03 <Herrie> WhiteBee: THere's a sample contacts app on Enyojs.com let me look it up
Aug 14 22:26:37 <Herrie> Written in Enyo2. THe good thing of Enyo2 is that it's properly cross browser, cross platform, auto scaling for different formats etc
Aug 14 22:26:51 <Herrie> http://enyojs.com/sampler/lib/layout/list/samples/ListContactsSample.html
Aug 14 22:27:13 <Herrie> That should be at least 30% of a proper contacts app already out of the box :P
Aug 14 22:28:32 <Herrie> For UI development Ares 2 is in the works, that should sort the UI part of apps. Not sure what the current status is, I couldn't run it on my Windows 7 machine last week, but it should work from what I heard from other people
Aug 14 22:28:44 <Herrie> https://github.com/enyojs/ares-project
Aug 14 22:30:27 <Herrie> Ares 2 is Enyo 2 based, browser UI developer tool for Enyo 2 ;) Quite cool :D
Aug 14 22:32:08 <Herrie> Contacts app on 2.2.4/2.2.5 = Mojo still
Aug 14 22:33:08 <Herrie> Contacts app on 3.0.5 is still Mojo it seems'
Aug 14 22:36:10 <Herrie> Anyone noticed the new avatar for Open webOS on Github? https://i1.wp.com/identicons.github.com/28b5bf3dc4b8421180f7f8e33b3d94c5.png?ssl=1
Aug 14 22:39:50 <Herrie> WhiteBee: There's also https://github.com/openwebos/core-apps/tree/master/com.palm.app.contacts It's Enyo 1.0 but should be quite easy as a starting point for converting to Enyo 2 with webos-ports-lib ;)
Aug 14 22:57:27 <WhiteBee> Herrie: thanks for the heads up! this sample is great
Aug 14 22:58:04 <WhiteBee> and yeah, my base right now is the enyo1 app
Aug 14 22:58:27 <Herrie> It should be possible to convert Enyo1 into Enyo2 quite easily
Aug 14 22:58:39 <Herrie> Some kinds might be missing, but I believe some guys wrote a convert from Enyo1 to Enyo2
Aug 14 22:58:44 <Herrie> Let me search a bit again ;)
Aug 14 22:59:01 <WhiteBee> sure P=
Aug 14 22:59:58 <Herrie> https://github.com/ArthurThornton/enyo1-to-enyo2-kinds
Aug 14 23:00:07 <Herrie> https://github.com/mbessey/DragFromList
Aug 14 23:02:19 <WhiteBee> Herrie: thanks, I will look into this tomorrow
Aug 14 23:02:23 <WhiteBee> now it's sleep time P=
Aug 14 23:02:29 <WhiteBee> gn
Aug 14 23:04:28 <Herrie> Same here, gn all ;)
**** ENDING LOGGING AT Thu Aug 15 02:59:59 2013