**** BEGIN LOGGING AT Fri Nov 29 02:59:58 2013 Nov 29 08:44:46 morning **** BEGIN LOGGING AT Fri Nov 29 09:18:38 2013 Nov 29 09:29:52 morning Nov 29 09:30:45 morphis: was it your intent to reworking webappmanager before doing a release ? Nov 29 09:31:01 because I think that will fix the issue we have with closing of apps Nov 29 09:31:34 which is caused by destroying the surface too soon, when the drawing queue in wayland was still not empty Nov 29 09:32:07 closing the client itself, on the other hand, will close it gracefully, and the surface will only be destroyed at the end Nov 29 09:55:27 Tofe: depends on how much time I have in the next days/weeks Nov 29 09:55:51 I would like to have it soon Nov 29 09:58:23 morphis: another way to fix it would be to force the unstream of queued wayland events in QWaylandExtendedSurface::extended_surface_close, but I'm not sure to know how to do that in a clean way Nov 29 09:59:55 hm Nov 29 10:00:02 I think doing it the other way would be a lot cleaner Nov 29 10:00:11 Tofe: how much time do you have in the coming days? Nov 29 10:00:21 you might can help me with doing the rework Nov 29 10:01:19 The week-end should be quiet, and the next two weeks seem ok too -- but mostly only the evenining, ofc Nov 29 10:01:22 Tofe: ah and the application is moving in from the bottom too fast Nov 29 10:01:45 ok, let me summarize what we have to do: Nov 29 10:03:09 we need to rework https://github.com/webOS-ports/luna-sysmgr/blob/webOS-ports/master/Src/base/application/ApplicationManagerService.cpp and https://github.com/webOS-ports/luna-sysmgr/blob/webOS-ports/master/Src/base/application/ApplicationManager.cpp to not use the WebAppMgrProxy class but a reimplementation Nov 29 10:03:18 which launches only native applications Nov 29 10:03:22 currently the WebAppMgrProxy Nov 29 10:03:35 calls luna-webappmanager over ls2 when launching a webapp Nov 29 10:03:54 and when it's a native app it launches the native process specified in the appinfo.json Nov 29 10:04:43 so we need some new implementation of this process deciding based on the app what needs to be launched Nov 29 10:05:25 if type = web it needs to default to something like /usr/sbin/webapp-launcher as process and provided needed arguments to launch the webapp Nov 29 10:05:37 if type = native it should just launch the native process Nov 29 10:08:50 ok, let me have a look at these classes first Nov 29 10:10:09 you're talking about the WebAppMgrProxy::instance()->appLaunch, for example, right Nov 29 10:11:30 right Nov 29 10:12:01 take a look at Src/base/application/ApplicationManager.cpp, Src/base/application/ApplicationManagerService.cpp and the ones in Src/remote/ Nov 29 10:12:12 I have some initial design locally I can submit later Nov 29 10:12:39 there are different way to a launch an app Nov 29 10:12:48 WebAppMgrProxy::launchUrl Nov 29 10:12:56 WebAppMgrProxy::appLaunch Nov 29 10:13:43 but I think we can remove launchUrl Nov 29 10:13:47 so basically, there are two things to do: refactor some code, so that the choice web/native is done outside of a WebAppMgrProxy, and have a webapp wrapper app, to separate them in different processes Nov 29 10:14:06 right Nov 29 10:14:13 the webapp wrapper app is very simple to do Nov 29 10:14:23 it's just a matter of processing the command line arguments Nov 29 10:14:28 maybe thats a good one for you Nov 29 10:14:49 as I have a pretty good overview what needs to be done within luna-sysmgr Nov 29 10:14:50 could be; and it can be tested right away, without the other part Nov 29 10:15:15 right Nov 29 10:15:28 https://github.com/webOS-ports/luna-webappmanager/ is pretty well written and it should be easy to rework it for this Nov 29 10:15:50 you just need to remove the service interface and directly create a WebApplication class with the input parameters supplied by the caller Nov 29 10:17:26 yes, move from a singleton/ls2 subsriber to a simple webapp launcher Nov 29 10:18:05 I should be able to get it working Nov 29 10:18:44 great Nov 29 10:18:54 I guess I can suppose the args given through ls2 will now be given through commandline, exactly same syntax ? Nov 29 10:19:23 I didn't look, but I suppose it's simply a JSON structure Nov 29 10:19:43 thats one point I am not sure about yet Nov 29 10:19:49 we need the following: const QUrl& url, const QString& windowType, Nov 29 10:19:49 const ApplicationDescription& desc, const QString& parameters, Nov 29 10:19:49 const QString& processId Nov 29 10:19:59 url, windowType, parameters are fine Nov 29 10:20:07 processId can be determined with getpid() Nov 29 10:20:14 but desc can get pretty big Nov 29 10:20:17 parameters also Nov 29 10:20:37 so I am not sure supplying them as commandline parameter is the best way Nov 29 10:21:06 I thought about creating a temporary file containing both and supply that to the launcher Nov 29 10:21:13 maybe through LS2 too, then, with a single contact point for each instance Nov 29 10:23:10 can't we have LS2 addresses like luna://palm.luna-webappmgr.org:///appDescription ? Nov 29 10:23:21 (without the typos...) Nov 29 10:25:16 hm Nov 29 10:25:37 Also I guess we should have a similar way to start a process, native or not, as much as possible, so maybe my proposal here doesn't fit that aspect Nov 29 10:26:15 somehow I like the idea Nov 29 10:26:41 the app description gets only passed for web apps Nov 29 10:26:45 native apps don't get them Nov 29 10:26:48 just the parameters Nov 29 10:27:12 so we would keep parameters on the cmd line ? Nov 29 10:27:24 would be a good option Nov 29 10:28:08 maybe we only keep parameters, and the rest goes to LS2 pipe ? Nov 29 10:30:23 we're not using that much information from the app description currently: https://github.com/webOS-ports/luna-webappmanager/blob/master/src/applicationdescription.cpp Nov 29 10:30:31 it would be nice to have the url on the cmd line, I must say Nov 29 10:31:14 the thing is that the app manager reads the appinfo.json file /usr/palm/applications//appinfo.json and then extends it with some more info and for example adds a default icon if the configured doesn't exists etc. Nov 29 10:32:39 well, as a start we could forget about LS2, have all as cmd line parameters, and only then migrate -maybe- some of the parameters to LS2 if we see that it will be needed Nov 29 10:33:45 that way we quickly have a first working solution, simple and clean, and then we can tune it Nov 29 10:35:54 Tofe: http://bpaste.net/show/KAIA2Z1TlmSnXVGLe55l/ Nov 29 10:35:54 sounds good Nov 29 10:37:23 ack Nov 29 10:39:37 I'll start a proto this week-end Nov 29 10:44:35 Maybe we can start with forking luna-webappmanager ? Nov 29 10:45:28 as webapp-launch, which sounds like a good name Nov 29 10:45:34 launcher* Nov 29 10:47:30 Tofe: lets do it a separate branch for now Nov 29 10:51:20 oki Nov 29 12:00:18 morphis: May I get write access to that repo ? That would be more convenient, if we work on a branch Nov 29 12:34:26 Tofe: for sure Nov 29 12:35:08 Tofe: done Nov 29 13:51:06 morphis: is there a very simple c++ project that i can work on to get my feet wet? Nov 29 14:16:23 hey all Nov 29 14:22:10 i2y4n: for webOS ports? Nov 29 14:22:50 morphis: preferably, yes Nov 29 14:23:23 inter_fudge: hey Nov 29 14:25:51 i'm glad to see webos is finally being ported over to other devices Nov 29 14:26:54 i was forced to switch to an htc evo after my phone got ran over on new years eve :( Nov 29 14:31:37 i2y4n: hm, let me think Nov 29 14:31:52 inter_fudge: we're trying our best :) Nov 29 14:35:29 i2y4n: you prefer c/c++ over html/js? Nov 29 14:36:30 morphis: well i know a little bit of html and c++ Nov 29 14:40:01 how much c++? Nov 29 14:40:17 and how much do you know about linux system programming? Nov 29 14:48:58 morphis: not a lot and i don't know anything about linux system programming. so maybe it's best to start with html/js. i might know enough to be able to figure things out Nov 29 14:49:12 i2y4n: I think too Nov 29 14:49:18 otherwise it will get very heavy Nov 29 14:49:32 i2y4n: you did some app programming for webOS before? Nov 29 14:52:13 morophis: No, unfortunately not. I started a project but never finished it. Nov 29 14:55:32 i2y4n: hm, ok you already tried the emulator? Nov 29 14:56:21 morphis: yes, i have it installed. tried it out, but it runs soooo slow on my computer that it's almost useless Nov 29 14:56:29 hm Nov 29 14:56:43 you have any other device we're targetting? Nov 29 14:57:44 galaxy nexus or a nexus 7? nope Nov 29 14:59:32 are there emulator settings i can change to speed things up? increasing the processors or something? Nov 29 15:00:26 yes Nov 29 15:00:33 what kind of system do you have? Nov 29 15:00:51 you can configure the virtualbox as every other vbox Nov 29 15:00:58 so increase ram + cpu count Nov 29 15:01:31 as the whole rendering inside the vbox is currently driven by the cpu and the gpu more cpu power will always help for the emulator Nov 29 15:03:38 2GHz quad core i7 with 8GB RAM Nov 29 15:06:21 should be enough Nov 29 15:12:11 i2y4n: one thing I have you can take care about Nov 29 15:18:01 morphis: i'm all ears Nov 29 15:18:11 you know the tweaks application= Nov 29 15:19:00 i2y4n: I have a Core Duo Q8300 with 4Gb RAM, and it works well Nov 29 15:19:01 yes Nov 29 15:19:42 i2y4n: basically we integrated it but its currently not working Nov 29 15:19:52 so I would like you to look whats wrong and make it work Nov 29 15:21:47 I bumped up the specs and the emulator runs much better now. i withheld doing that initially because of this "You don't need to change any of the preconfigured values" on the emulator page. thanks Nov 29 15:22:13 morphis: okay, will do Nov 29 15:22:20 i2y4n: maybe you can add that as hint to the wiki page Nov 29 15:22:35 i2y4n: mostly you should get some info when looking at the system log Nov 29 16:11:59 morphis: sorry for having to ask (wish i didn't need to) how do you find the system logs? Nov 29 16:12:16 journalctl Nov 29 16:17:01 tofe:thanks Nov 29 16:20:47 i2y4n: you have handy options, like -f, -l Nov 29 16:59:23 i2y4n: http://superuser.com/questions/350817/how-to-set-terminal-size-in-android-adb-shell can also help to expand the terminal size Nov 29 17:31:28 i have no clue about this command line stuff. can i use this command to watch the logs in real time? tail -f /home/00000/logs/error_log Nov 29 17:59:14 i2y4n: that was the handy part I was talking about ;) Nov 29 17:59:59 tofe: i finally figured out all i had to do was add -f to journalctl. just took me a while, but thanks! Nov 29 17:59:59 you can also select which systemd units you want to follow, with -u; like "-u luna-next -u luna-webappmanager" Nov 29 18:21:14 where can i find the tweaks app that is included in the webos port? Nov 29 18:21:32 preware Nov 29 20:04:12 morphis: is launchApp or launchUrl also called when starting a new window in an existing application ? Nov 29 21:00:35 Tofe: https://github.com/webOS-ports/luna-sysmgr/commit/689d2f770eddb146fcca83bea073666ea9157215 Nov 29 21:02:33 Tofe: launchUrl is only called in one case Nov 29 21:03:15 ok, good Nov 29 21:03:44 did the initial implementation Nov 29 21:04:22 if you place the launcher as /usr/sbin/webapp-launcher it should just work Nov 29 21:04:35 it's missing some more love but it should work Nov 29 21:05:15 Tofe: and launchUrl and launchApp are the same with the only difference that launchApp reads the entry url from the appinfo.json Nov 29 21:06:48 ok, need to leave Nov 29 21:06:49 gn8 Nov 29 21:07:08 gn8 **** ENDING LOGGING AT Sat Nov 30 02:59:59 2013