**** BEGIN LOGGING AT Sat Jan 17 02:59:59 2015 Jan 17 06:44:52 Hey, I can’t *ever* get the email app to properly launch.Tapping the icon gets no visible action, while lauching it using luna-send gives a return value of true, but no window.. Is that http://issues.webos-ports.org/issues/649 or some other bug? Jan 17 07:06:17 This is on my N4. On the TP, Email launches normally. Jan 17 12:10:29 DougReeder: yeah that should be 649 Jan 17 12:10:47 DougReeder: Indeed 649 was on my N4 as well. Jan 17 12:10:54 Didn't test much on TP tbh Jan 17 12:12:39 there seems to be still something wrong with the relaunch handling and nowindow cards Jan 17 12:13:37 Garfonso: I am going to push the InAppBrowser work today into the build, can you rework the validator to use it then? Jan 17 12:16:17 Herrie: btw. airplane mode was working now, right? Jan 17 12:18:32 morphis: yes. Jan 17 12:20:57 Garfonso: great Jan 17 12:30:55 morphis: Well not really yet Jan 17 12:31:21 Herrie: what doesn't work? Jan 17 12:32:25 morphis behavior was inconsistent Jan 17 12:32:42 Hope tohave some time this weekend to sort Jan 17 12:33:15 Had flu earlier in the week + was busy in the office so little time... Jan 17 12:35:14 Herrie: oh, hope you are better now :) Jan 17 12:38:08 Gets better by the days but still not 100% Jan 17 13:08:56 Herrie: can you help me with writing down requirements for the messaging app? Jan 17 13:08:59 started on https://github.com/webOS-ports/org.webosports.messaging/wiki/Features already Jan 17 14:17:41 morphis: OK Jan 17 14:21:12 Herrie: already started with describing technical aspects Jan 17 14:38:43 morphis, thanks for merging my Contacts PR. Jan 17 14:38:58 DougReeder: np Jan 17 14:39:21 Garfonso, were you the one who asked for the Add Contact API? Jan 17 14:43:33 Herrie: is http://issues.webos-ports.org/issues/777 fixed? Jan 17 14:43:55 doesn't look so Jan 17 14:44:01 Tofe: can you look at 777? Jan 17 14:45:51 DougReeder: are you implementing that now? Jan 17 14:46:05 DougReeder: if yes, please update 759 once you're done with that Jan 17 14:46:09 That was in the PR Jan 17 14:46:21 ah good Jan 17 14:46:27 DougReeder: can you also look at http://issues.webos-ports.org/issues/743? Jan 17 14:46:57 did saw that, just the UI work Jan 17 14:56:00 I don’t know whether that scene is part of Contacts or Accounts; I can take a look Jan 17 14:57:30 DougReeder: from what I know it's part of the enyo-1.0 component library Jan 17 14:57:54 https://github.com/webOS-ports/enyo-1.0/tree/master/framework/lib/accounts ? Jan 17 15:14:36 The Prefs scene is part of Contacts Jan 17 15:21:46 DougReeder: what is with https://github.com/webOS-ports/enyo-1.0/tree/master/framework/lib/contactsui? Jan 17 15:22:13 I believe that is pulled in and also used Jan 17 15:22:17 seems to have atleast a kind to deal with account providers Jan 17 15:22:23 ok Jan 17 15:26:05 The Enyo 1 Contacts app depends on $enyo-lib/contactsui/, which is defined by the built-in Enyo 1 lib. Jan 17 15:26:20 I’m not sure what the analog is for Enyo 2 apps. Jan 17 15:28:07 So, 743 can’t be implemented until 1) Contacts prefs is implemented and 2) we figure out what the analog to $enyo-lib is for Enyo 2. Jan 17 15:29:01 Both of which are doable, they just will take time. Jan 17 15:34:54 DougReeder: afaik for enyo2 you have to add those bits directly in your app Jan 17 15:35:15 $enyo-lib doesn't really exist as all sources need to be there when the app is minimized Jan 17 15:35:20 from what I understood Jan 17 15:36:37 DougReeder: uhm.. no. But I positive, that we want to have that. :) Jan 17 15:40:10 morphis: do we want to have group chat support in the messaging app? All the newer messengers (WhatsApp, Textsecure, facebook, google whatever) have that and it seems to be a central concept for them. Jan 17 15:47:16 Garfonso: my idea was to somehow abstract those messaging services in our app Jan 17 15:47:42 so you can have a group chat via SMS, Whatsever, ... and don't need to care which app you're using for that Jan 17 15:48:14 however I am not clear yet what the best way to integrate those together Jan 17 15:49:25 issue with groupchat for sms is that you do not know about the "group" if you receive a groupchat sms (which is different for the other services AFAIK)... so especially for replies to a group sms it will be hard to distinguish where they go.. Jan 17 15:50:45 I'm not sure how to handle that, either. It would be nice if the messaging app can handle it. Was just asking, because we might want to add it as feature here https://github.com/webOS-ports/org.webosports.messaging/wiki/Features Jan 17 15:51:47 Garfonso: feel free to add it there Jan 17 15:52:01 Garfonso: we already have the serviceName field for the messaging objects Jan 17 15:53:04 for a group chat we have to send multiple SMS and also the remote side needs to handle that to have a real group chat Jan 17 15:53:15 so for SMS it is rather .. not as we want it Jan 17 15:53:44 Garfonso: btw. what about integrate the messages from different services in one chat thread Jan 17 15:53:45 ? Jan 17 15:55:52 morphis: that should already work, because chatthreader does it. Jan 17 15:56:54 chatthreader looks at the other-persons address (or list of addresses) and searches a personId for that. It does not care much if it is IM or SMS/MMS. Just because it needs to search for phone numbers differently than for IM addresses. Jan 17 15:57:30 so if it is an IM address it compares those instead of the phone number? Jan 17 15:57:55 so we get chatthreads which have different kind types attached? Jan 17 15:58:39 right. That's what legacy does also. So I thought that's were we want to go. :) Jan 17 15:58:47 really? Jan 17 15:58:59 didn't legacy made a difference between IM and SMS messages? Jan 17 15:59:11 just MMS and SMS messages where put in the same thread if I remember Jan 17 15:59:39 I quite sure I had google talk and sms go into the same chatthreads. Of course the contacts need to be linked correctly, too. Jan 17 16:00:18 when replying you could choose in a drawer on top of the window what service to use, Jan 17 16:00:32 ah Jan 17 16:00:42 that is what I want :) Jan 17 16:01:01 Garfonso: can you put that on the features page? Jan 17 16:01:14 we need to document those bits for people going to implement it Jan 17 16:01:34 also if you have any further details which are needed feel free to add them to the "Technical Aspects" page Jan 17 16:02:35 ok. :) Jan 17 16:10:10 morphis: my build fails https://bpaste.net/show/896e96f6de82 ... it fails for gstreamer1.0-plugins-bad_1.4.1.bb and complains about no object c compiler Jan 17 16:10:21 not sure how to solve that Jan 17 16:13:32 morphis: regarding this: https://github.com/webOS-ports/org.webosports.messaging/wiki/Implementation-aspects - the chatthreader can also take the responsibilty to assign outgoing messages to chatthreads. In fact that is already implemented and was not more work (and it seems legacy does the same, too). Jan 17 16:14:00 then the messaging app would only need to creat a com.palm.message:1 object with the folder set to "outbox". Jan 17 16:16:58 Garfonso: you're building on ubuntu? Jan 17 16:17:15 yes, but 14.04 or so. Jan 17 16:17:40 hm Jan 17 16:18:16 Garfonso: can you try with --c cleansstate gstreamer1.0-plugins-bad and rebuild? Jan 17 16:18:52 basically it should not build those bits so wondering why it pulls them in .. Jan 17 16:18:58 maybe JaMa knows when he is back Jan 17 16:45:37 morphis: it still tries to build it and fails. :-/ Trying to build luneos-dev-package for mako Jan 17 16:46:47 morphis: I ... uhm... rewrote https://github.com/webOS-ports/org.webosports.messaging/wiki/Implementation-aspects that's how I understood messaging works on legacy. It more elegantely solves the "if user cancels new message" issue that was there before and explains how to handle multiple recepients. Jan 17 17:49:41 morphis: 777 still there afaik Jan 17 17:53:33 morphis: chatthread service currently requires flag.visible = true for message objects. I took this from legacy. Do we want to keep that? Not sure where invisible messages make sense / can happen at all (drafts or something like that?). Jan 17 18:12:23 morphis: ping Jan 17 19:15:56 Garfonso: why not Jan 17 19:15:57 Tofe: pong Jan 17 19:17:56 It sounds like you all are working on different aspects of messaging, but a UI concept you might consider is distinguishing between left and right swipes: http://webos-ports.org/wiki/Swipe_UI Jan 17 19:19:21 Swiping left would delete a message. I’m thinking it would be nice if swiping right created a Task in the Tasks app (that we haven’t written yet). Jan 17 19:37:40 DougReeder: yeah UI concept is really something we have to think about Jan 17 19:38:26 I’m not a heavy user of messaging on mobile, so I don’t necessarily know what poeple need it to do. Jan 17 19:39:20 I am also not that heavy messaging guy Jan 17 19:40:00 Me neither, but that could also be because the legacy one is limited a bit ;) If it do WhatsApp, IRC + various IM's like Skype I would use it more ;) Jan 17 19:40:02 but first it should do basic things, then we can make them integrating into the whole concept Jan 17 19:40:13 Herrie: right Jan 17 19:40:47 for WhatsApp or TextScecure I am not sure what amount of support is out there in FOSS components we can use Jan 17 19:43:23 Does the idea swipe-left-to-delete, swipe-right-to-do-more sound like a useful one for messaging? Jan 17 19:44:28 morphis: yes, I was looking at that tabletUi setting Jan 17 19:44:53 and it looks like there is actually quite nothing to be done to expose it, it's already done -- and by you, I think :) Jan 17 19:49:39 WhatsApp: EricBlade had something more or less working before they started using encryption Jan 17 19:49:57 WhatsApp is not very friendly for people trying to reverse engineer their protocol Jan 17 19:50:13 They have been taking some DCMA shutdown notices to WhatsApi etc Jan 17 19:51:18 One of the Meego devs reverse engineered their protocol on which MojoWhatApp is also based ;) Jan 17 19:54:00 Tofe: ah great Jan 17 19:54:34 Herrie: ok, then it looks like something we should not touch if the legal site is so unclear Jan 17 19:54:42 doesn't use it anyway :) Jan 17 20:20:14 morphis: Yeah, people can always create something unofficial outside of our project ;) Jan 17 23:52:08 my nexus 4 refuses touch with LuneOS Jan 17 23:52:22 can someone help me fix this or know of a solution? Jan 17 23:59:30 “refuses touch” ? Jan 18 00:23:26 it doesn't register a touch. I did a logcat on android 4.2.2 and the driver loaded fine, but it said that it ignored touch input. **** ENDING LOGGING AT Sun Jan 18 02:59:59 2015