**** BEGIN LOGGING AT Fri Jan 16 03:00:15 2015 Jan 16 04:02:53 Hey, anyone have a working example of how to catch the launchParam in an Enyo 2 app? Jan 16 04:03:43 On a relaunch, an enyo.Signal will catch the onrelaunch event, but it’s not clear that there’s a launch event. Jan 16 04:04:46 The following events do not appear to exist: onWebOSLaunch, onwebOSLaunch, onweboslaunch, nor onlaunch Jan 16 04:06:04 I can make use of window.PalmSystem.launchParams if I have to, but that would be inelegant. Jan 16 06:15:12 Whew! The "Create New Contact" dialog & "Add Contact" API are finished. Jan 16 08:24:12 morning. Jan 16 08:24:46 build of gstreamer fails for me, complains that no objective c compiler is installed. What package do I have to install? Should I add that to the prerequisited in the wiki? Jan 16 08:25:09 all the packages from the wiki are installed. Jan 16 08:28:06 DougReeder: from what I understand you geht the onrelaunch signal also on launch.. so it's more an on(re)launch signal. At least in legacy thats the way I handle it... or? Let me check Jan 16 08:36:48 ok. I was wrong... I just check webos.launchParams() in the on create method. Jan 16 09:37:40 Herrie|Veer: do we have an easy way to publish something like c+dav connector on Preware feeds for the legacy devices? Jan 16 09:38:24 morning! Jan 16 09:38:35 morphis: yes, I tested it before doing the PR :) Jan 16 09:38:48 morning! Jan 16 09:39:06 Garfonso: The connector as app or the patches or both? Jan 16 09:39:20 The app you could do via WebOSNation I think Jan 16 09:42:42 should I publish it with my personal webOS Nation account? Jan 16 09:44:23 Not sure we have a webosports account, think we might have Jan 16 09:44:33 You'd need to ping ka6sox for that I guess Jan 16 09:44:54 uh.. maybe it's easier to do with my own account then. :-p Jan 16 14:57:03 Garfonso, can de done Jan 16 14:57:41 Garfonso, legacy feeds are thru built.git over thru the webos-internals github. Jan 16 15:02:19 DougReeder: nice PR for the contacts app Jan 16 15:02:26 * DougReeder smiles Jan 16 15:03:10 DougReeder: I started to add logging to qtwebkit to find out who drops the subscription call Jan 16 15:03:19 Ah, good. Jan 16 15:03:43 but it seems to come from the subscriber, not the service Jan 16 15:04:02 Yeah, that’s what it looked like to me Jan 16 15:04:36 I suspected something in webos-lib, but enyo-webos has the same problem. Jan 16 15:04:56 right Jan 16 15:05:20 I suspect something between ls2<->PalmServiceBridge or PalmServiceBridge<->js Jan 16 15:05:34 ls2 got timeouts for calls some time ago Jan 16 15:05:40 but by default they should be disabled Jan 16 15:08:24 I’m just not familiar with the layers below JS. Jan 16 15:08:34 :) Jan 16 15:13:21 I’d like to be, but it’s not clear that would be a good use of my limited time. Jan 16 15:14:25 Dang, I keep closing this window when I mean to close a browser tab. :-( Jan 16 15:17:36 DougReeder: you're quite good in js things where I always loose :) Jan 16 15:18:18 Hopefully, we can put that industrial revolution division-of-labor principle to good use. :-) Jan 16 15:45:33 DougReeder: :) Jan 16 15:48:25 DougReeder: btw. what is missing to get the contacts really saved? Jan 16 15:48:47 Wrting the code. Jan 16 15:49:16 … but I’m not certain whic h DB8 kind to save to: contact:1 or person:1 Jan 16 15:50:00 as far as I know contact:1 is the real contact Jan 16 15:50:06 and person:1 the aggregated oned Jan 16 15:50:14 but Garfonso should know Jan 16 15:50:19 Right. Jan 16 15:50:28 Garfonso: ^^ Jan 16 15:51:31 DougReeder: btw. can we already see off which contacts a person is aggregatedß Jan 16 15:51:33 ? Jan 16 15:51:53 Connectors create contacts, from which the persons are created (as you said). I’m not certain if a person is created that a contact will be created. Jan 16 15:52:09 Yes, there’s references in the record. Jan 16 15:52:13 ok Jan 16 15:52:20 … but that’s not currently displayed in the UI Jan 16 15:52:26 and there must be a primary contact for a person, right? Jan 16 15:52:38 or how is decided where changes go to? Jan 16 15:52:53 Well, that’s a good question. Jan 16 15:53:16 I’m not sure what webOS does, but it seems to me changes should go everywher. Jan 16 15:53:44 even if the field isn't set on one contact but on another? Jan 16 15:53:56 Right. Jan 16 15:54:39 The idea, as I understand it, is that the contacts are the same real-life person or organization. Jan 16 15:56:20 So, logically, if you add an email addr (for example) to the person record, it should be added to all contacts. Jan 16 15:58:13 I wonder if there’s some webOS enthusiast (not necessarily a programmer) who figured out all the information flows, that we could ask. Jan 16 15:58:48 Or, do we know who at Palm was the architecht of contact synergy? Jan 16 16:00:56 not really, if we don't know how it was we should select the best way for us Jan 16 16:02:50 I’d like to take advantage of any research Palm did on this. Jan 16 16:03:29 I know how I like things to work, but that’s not always what users in general want. Jan 16 16:08:14 hmm...I may know someone who worked on it Jan 16 16:08:28 I'll ask him when he gets on skype Jan 16 16:11:29 I think the general problem of mutiple sources of contact info is a hard one, and we can’t do everything that everyone might want. Jan 16 16:13:20 If a user is editing a person on device, we can assume he/she has checked that all the contact entries really are the same person, so any changes made on-device really should go to all. Jan 16 16:18:10 In person:1, contactIds is an array of strings, so there doesn’t appear to be a way to designate which account is “primary”. There’s both a name field and names field with names from all contacts, but I don’t know how the system selects which contact to pull the name from. That’s probably a weakness of the database schema - I get frustrated by wrong names under webOS. Jan 16 16:26:54 This may not be that big an issue. A lot of linked contacts will be Skype or IM accounts, where the user doesn’t much care whether it contains complete or up-to-date address book info. Jan 16 16:44:12 DougReeder: you know how Android deals with this problem? Jan 16 16:44:22 I have no idea. Jan 16 16:44:59 DougReeder: let me see if I can find that out Jan 16 16:45:05 for something my Android phone must be good :) Jan 16 16:45:11 * DougReeder nods and smiles Jan 16 20:17:01 no, I don't know anyone who worked on contacts synergy Jan 16 22:04:55 DougReeder: AFAIK contacts are not created from persons. Also things in the person might get overwritten if the original contacts change (not sure about that) Jan 16 22:05:36 So, to save a new person, we need to update the contacts it’s ccreated from? Jan 16 22:06:02 Er, create a new person by createing a contact Jan 16 22:06:16 … and update a person by updating its contacts? Jan 16 22:06:45 DougReeder: in legacy it is a bit random... it saves information in just one of the contacts. Jan 16 22:07:06 that is why would make it more clear in what contact the information goes... Jan 16 22:07:16 I would not copy everything to each contact, though Jan 16 22:07:20 Ah, I wondered. I nver tried to test it. Jan 16 22:07:26 Why not? Jan 16 22:09:17 on the phones you can specify one contact as primary and that is where edits go. On TP it was just the first contact. Maybe you could change it there, too. Not sure. Jan 16 22:09:52 I would not copy everything especially for those IM contacts... they probably don't need (or even can't handle) all that information Jan 16 22:12:04 In general, the back end for a contact doesn’t need to support all the fields. I don’t see the problem with setting them on device and letting the Connector dal with that. Jan 16 22:12:28 personally my favorite would be to only edit contacts, i.e. in the edit window have a dropdown for the single contacts of a person and show only the fields in that contact and add all changes to that contact. Would be the most transparent in my opinion Jan 16 22:14:50 Looks like the TP lets you set the primary contact, also. Jan 16 22:14:56 probably the biggest issue with coping information to all contacts is that potentially multiple background services get triggered and bog down the device ;) Jan 16 22:18:11 It’s not clear how the primary contact is stored. There isn’t a field for it in person:1 Jan 16 22:18:26 probably it is really just the first one in the array? Jan 16 22:19:01 I presume Connectors would use Change Sets, so they’re only triggered for fields that they support. Jan 16 22:20:02 Interpreting the fist listed contact as primary is certainly doable. Jan 16 22:23:37 yes tested, it really is the first contact in the contactIds array Jan 16 22:23:51 Ah, okay. Jan 16 22:28:44 Here’s a scenario: a friend changes jobs, to a diffecrent company. Each secondary contact either implements job title (where it’s wrong if we don’t update it) or doesn’t implement it, in which case the connector should ignore any change. Jan 16 22:30:44 Likewise for physical addresses. **** ENDING LOGGING AT Sat Jan 17 02:59:59 2015