**** BEGIN LOGGING AT Wed Feb 25 02:59:58 2015
Feb 25 04:17:28 <DougReeder> HaDAk, Mochi was *not* finished. There’s plenty to build on, but there are many unfinished bits that need to be written.  Nothing that can’t be done, but it would take developer time.
Feb 25 04:18:15 <DougReeder> But, by all means, forge ahead - an make a list of what needs to be finished as you go.
Feb 25 05:44:54 <Herrie> DougReeder: I'm looking into the timezone description issue
Feb 25 05:45:04 <Herrie> Found the culprit, just need to think about a proper fix
Feb 25 09:04:33 <Tofe> morning!
Feb 25 09:07:54 <Herrie|Veer> morning
Feb 25 09:07:59 <Herrie|Veer> Tofe: ping
Feb 25 09:19:26 <morphis> Herrie|Veer: morning
Feb 25 09:25:52 <Herrie|Veer> morphis: morning
Feb 25 09:26:34 <Herrie|Veer> Tofe: Not sure what's up with digital clock of Dockmode on TP. In QtCreator in landscape it shows letters but on device not :s
Feb 25 09:28:43 <Tofe> Herrie|Veer: ok, I'll test that. It's specific to TP, right?
Feb 25 09:36:50 <Herrie|Veer> Tofe: Seems so
Feb 25 09:36:58 <Herrie|Veer> N4 uses portrait and is fine
Feb 25 10:11:28 <Tofe> ok, that's pretty weird. One question though: when you say "no letters", which letters is it ?
Feb 25 10:24:00 <Herrie|Veer> On the digital clock on top of the images
Feb 25 10:24:44 <Herrie|Veer> on top of the "flipper" images there should be letters
Feb 25 10:25:05 <Herrie|Veer> It's OK in QtCreator in landscape when I force resolution to 1024*768
Feb 25 10:25:29 <Herrie|Veer> Just not on actual device
Feb 25 10:25:41 <Herrie|Veer> I tried increasing letter size to no avail
Feb 25 10:25:53 <Herrie|Veer> I don't see anything wrong with the code per se
Feb 25 10:37:14 <Garfonso> morning
Feb 25 10:50:12 <Tofe> ok
Feb 25 10:53:16 <Herrie|Veer> Tofe: Also I think we shouldn't show gesture area on TP (only) because we have the physical button available. It also gives some distorted images due to space the gesture area takes. Not sure what's morphis' and Garfonso's view on this?
Feb 25 10:55:40 <Garfonso> uhm.. I like gesture area on tp.. my  home buttons on the TPs are quite worn out already. ;) Also we need it for back gestures. Not sure we want to add back buttons to all that apps again.
Feb 25 10:56:50 <Garfonso> not sure what you mean by "distorted images", though.. shouldn't at least the web apps adjust to the window size? So no real "distortion" there, right?
Feb 25 10:58:24 <Herrie|Veer> Ah Garfonso: true didn't think about that
Feb 25 10:58:31 <Herrie|Veer> The back gesture
Feb 25 11:06:48 <nizovn> has anyone tried to type on keyboard in browser on TP? for me some keys don't work
Feb 25 11:08:25 <Herrie|Veer> nizovn: Any keys in specific?
Feb 25 11:08:55 <Herrie|Veer> Will have a look. I noticed this as well but my touchscreen on tp4g is faulty so thought that was the cause
Feb 25 11:11:25 <nizovn> Herrie|Veer: right half of keyboard completely doesn't work(only on browser), for example enter
Feb 25 11:14:29 <Herrie|Veer> I noticed the touchscreen in LuneOS is less responsive compared to webOS. This probably has to do with drivers or firmware or combination of both
Feb 25 11:15:14 <Herrie|Veer> But my touch controller board is faulty so difficult to really assess properly at my end
Feb 25 13:35:48 <Garfonso> ok.. how was that build process again? Hm...
Feb 25 13:43:43 <Herrie|Veer> Which one?
Feb 25 13:44:17 <Garfonso> to get something into preware. ;)
Feb 25 13:46:34 <Garfonso> didn't Brent Hunter once allow FeedSpider 2 to be integrated into our Preware-LuneOS feed?
Feb 25 13:46:47 <Herrie|Veer> Ehm make IPK and upload to WON?
Feb 25 13:46:53 <Garfonso> Or how is our current plan for 3rd party apps on LuneOS? :)
Feb 25 13:47:50 <Garfonso> Herrie|Veer: I do that for my own apps, yes... but wanted to put C+dav into the webos-internals feeds. Because technically its not my app, it will be published in the name of webos-ports / webos-internals. ;)
Feb 25 13:50:41 <Herrie|Veer> Ah we have a webosports account on won
Feb 25 13:50:52 <Herrie|Veer> Not sure that can publish apps
Feb 25 13:51:19 <Herrie|Veer> The other way like Tailor you'd need to do it differently.
Feb 25 13:51:48 <Garfonso> yes, I'm looking into that right now. ;)
Feb 25 14:17:20 <DougReeder> Have the PivotCE guys made any progress toward implementing a feed?
Feb 25 14:17:42 <Herrie|Veer> Yeah they have a feed ready
Feb 25 14:24:53 <DougReeder> What’s the URL?  We could add it to the disabled-but-enableable-feeds.
Feb 25 14:51:24 <DougReeder> HaDAk, changing an app to use Mochi is behind several other items on my to-do list, but I’d love to see someone do a whole app with it.
Feb 25 14:55:09 <GodGinrai> yea, Mochi is awesome :)
Feb 25 14:55:53 <GodGinrai> seems like HaDAk is having connection problems
Feb 25 15:06:37 <GodGinrai> HaDAk: 09:51 < DougReeder> HaDAk, changing an app to use Mochi is behind several other items on my to-do list, but I’d love to see someone do a whole app with it.
Feb 25 15:06:49 <HaDAk> :)
Feb 25 15:20:49 <Garfonso> DougReeder: there is NISI in the webos nation forums which is a Pocket client. It was done in Mochi.
Feb 25 15:21:25 <DougReeder> Ah, I’ll check it out!
Feb 25 15:22:13 <Garfonso> Ok.. so.. who knows about the build process. What will break if I give two apps the same app id? ;)
Feb 25 15:24:13 <DougReeder> At a guess, last one overwrites previous.
Feb 25 15:24:35 <Garfonso> yes, I'm pretty sure that will happen.
Feb 25 15:24:38 <DougReeder> … that is, files from the second overwrite files from the previous
Feb 25 15:25:17 <DougReeder> last app should work normally, unless the presense of extra files causes a behavior change.
Feb 25 15:26:23 <Garfonso> I don't like that build process. :-/ How to have two versions of the same app for different versions of webOS?
Feb 25 15:29:26 <Garfonso> hm.. maybe I can cheat and internally have another Id than I show to the surrounding make via APP_ID flag.
Feb 25 15:31:25 <GodGinrai> Garfonso: why do you want them to have the same app id?
Feb 25 15:31:45 <GodGinrai> ah
Feb 25 15:31:54 <GodGinrai> I just read the part about 2 versions of the same app
Feb 25 15:32:44 <GodGinrai> I haven't used the build process, but isn't this the kind of thing you use pre-processor directives for?
Feb 25 15:32:57 <GodGinrai> and separate make targets
Feb 25 15:33:56 <Garfonso> I think it works if I set the APP_ID variable to something different (i.e. cdav-hd instead of cdav) but work with the old id internally... that *should* build me the right ipks. Test is running. ;)
Feb 25 15:34:08 <Garfonso> I now even have different Makefiles
Feb 25 15:34:10 <DougReeder> It does kinda sound like your trying to do something at the wrong stage of the build process.
Feb 25 15:34:49 <GodGinrai> ^ this
Feb 25 15:34:54 <DougReeder> Which different versions of webos need different versions of the app?
Feb 25 15:35:13 <GodGinrai> probably phone OS and LuneOS
Feb 25 15:35:28 <Garfonso> the issue is the custom account validator
Feb 25 15:35:54 <Garfonso> I did not manage to get the mojo-account app (phones) to work with enyo or the enyo account app (tablet) to work with mojo or enyo.
Feb 25 15:36:18 <Garfonso> So I basically have an enyo app and a mojo app for the validators. The rest is identical.
Feb 25 15:37:30 <DougReeder> You need one version of the app for webOS 2.x and another for webOS 3.x?
Feb 25 15:38:06 <Garfonso> yes, but only the app and account template. Package and service (the main part) is the same.
**** BEGIN LOGGING AT Wed Feb 25 15:40:32 2015
Feb 25 15:41:11 <DougReeder> Ah, you need a different versions in a Preware feed!
Feb 25 15:41:33 <Garfonso> currently my approach is to create two different makefiles, which means different ipks and apps in the sense of the feed. But internally it still is the same app.id if both ipks.
Feb 25 15:41:35 <Garfonso> right. :)
Feb 25 15:43:11 <DougReeder> So, this issue is specific to the Preware “build” script.  You might need to track down the original authors and see if that functionality is available.
Feb 25 15:43:48 <DougReeder> If not, you might need to modify the Preware build scripts.
Feb 25 15:44:16 <Garfonso> uhm.. I'm barely able to read makefiles... in fact makefiles is the stuff I really dislike most about c++. ^^
**** BEGIN LOGGING AT Wed Feb 25 15:46:16 2015
Feb 25 15:48:01 <Garfonso> that is true... but I really have no clue about this build system. Also, at least the webos-internals version, is not working anymore, because it tries to download stuff from palm.com that is gone. :-(
Feb 25 15:48:18 <DougReeder> Oi
Feb 25 15:48:31 <GodGinrai> Garfonso: don't hate makefiles, hate people who make obfuscated makefiles
Feb 25 15:48:43 <GodGinrai> often times, people will overcomplicate things
Feb 25 15:48:51 <Garfonso> hehe. ;)
Feb 25 15:49:02 <GodGinrai> Make is great when used correctly
Feb 25 15:50:13 <DougReeder> The main problem is visibility - there’s so many implicit rules, and no good way to see which would be invoked by a given Makefile
Feb 25 15:56:11 <Garfonso> its right... if you have a good build system, then make is really great. :) But I would never be able to set something up myself.
Feb 25 16:00:30 <DougReeder> Nisi is a desent-looking app (though the discoverability of navigation is poor).
Feb 25 16:00:50 <DougReeder> I can’t say it make a strong case for switching to Mochi.
Feb 25 16:01:45 <DougReeder> It certainly doesn’t look worse than onyx.
Feb 25 16:05:39 <DougReeder> Now, something like an Arranger that put divided two panes vertically in portrait mode and horizontally in landscape mode, THAT would be exciting.
Feb 25 16:08:05 <Garfonso> ahrg... why does it think it needs the toolchain target for the alpha-apps target? :-(
Feb 25 16:08:46 <Garfonso> DougReeder: build it. ^^
Feb 25 17:13:02 <morphis> Herrie: mockup for mochi phone app looks great
Feb 25 17:16:01 <GodGinrai> the mockup done by the enyo team?
Feb 25 17:16:06 <GodGinrai> or did Herrie make a mockup?
Feb 25 17:16:19 <morphis> GodGinrai: one of our graphic guys did
Feb 25 17:16:41 <morphis> nizovn: I reverted the qtsensors change for now
Feb 25 17:16:53 <nizovn> ok
Feb 25 17:17:16 <morphis> and included sensorfw through packagegroup-luneos-extended in LIBHYBRIS_RDEPENDS
Feb 25 17:17:29 <morphis> that will fix the build for now
Feb 25 17:17:36 <GodGinrai> morphis: oh really?  IIRC, didn't you not want to use Enyo for the phone app?
Feb 25 17:17:56 <morphis> yes, we're using QML
Feb 25 17:18:04 <GodGinrai> but making it look like Mochi?
Feb 25 17:18:12 <morphis> that was one of the ideas
Feb 25 17:18:17 <GodGinrai> I see
Feb 25 17:18:40 <morphis> GodGinrai: http://files.gravedo.de/20150221084203.png
Feb 25 17:18:44 <morphis> that is how it looks atm
Feb 25 17:19:17 <nizovn> morphis: i also think to add qtsensors and qtsensors-qmlplugins to RDEPENDS_${PN} in packagegroup-luneos-extended
Feb 25 17:19:48 <morphis> nizovn: yeah good idea
Feb 25 17:20:18 <GodGinrai> morphis: nice and simple
Feb 25 17:20:28 <morphis> it should be pulled in through qtwebkit already but (atleast qtsensors not -qmlplugins) having a explicit dependency is better
Feb 25 17:20:36 <morphis> GodGinrai: programmers art :)
Feb 25 17:20:41 <GodGinrai> lol
Feb 25 17:26:33 <morphis> Herrie: https://github.com/webOS-ports/luna-appmanager/pull/6 will help to solve #765
Feb 25 17:36:58 <morphis> GodGinrai: what is with you, anything you can help us with?
Feb 25 17:51:50 <GodGinrai> morphis: Currently trying to fix docker-related problems with my work laptop
Feb 25 17:58:19 <Herrie> morphis: Yeah Benjamin had quite some comments but was busy so just quickly forwarded the mock :)
Feb 25 17:58:41 <morphis> Herrie: so first question now is if we want mochi as primary UI design
Feb 25 17:58:41 <Herrie> It's just Photoshop mock for now, but I'm quite sure he could put this into QT Component bits that we were talking about
Feb 25 17:58:56 <Herrie> morphis: It's really a matter of taste...
Feb 25 17:59:05 <Herrie> Some people love it, some hate it
Feb 25 18:00:05 <GodGinrai> I think Mochi is a good direction
Feb 25 18:00:13 <GodGinrai> looks much better than Onyx
Feb 25 18:00:59 <GodGinrai> and is easier than trying to make a new UI, since you would want to make an Enyo version of it as well so that Enyo apps gelled with the design
Feb 25 18:01:39 <Herrie> Well we could have both, but we'd need some people to maintain it
Feb 25 18:01:54 <Herrie> Mochi is quite complete but misses a few things that are available in Onyx currently
Feb 25 18:02:22 <GodGinrai> I'm sure it does
Feb 25 18:02:40 <GodGinrai> what in particular are you wanting that onyx has?
Feb 25 18:02:46 <morphis> Herrie: at least we need a point where we start using mochi
Feb 25 18:02:56 <morphis> getting it in place all over the system is a pretty big job
Feb 25 18:04:11 <Herrie> Yeah, legacy allowed you to play with themese
Feb 25 18:04:21 <Herrie> Which might a good approach for flexibility
Feb 25 18:05:31 <Herrie> http://www.webosnation.com/webos-theme-gallery
Feb 25 18:06:13 <Herrie> http://forums.webosnation.com/webos-themes/204088-how-themebuilder.html
Feb 25 18:11:12 <morphis> puuh, that might make things only more complicate
Feb 25 18:16:23 <morphis> Herrie: thing is just that we miss the power to establish a common UI priniciple
Feb 25 18:22:52 <morphis> DougReeder: ping
Feb 25 18:26:42 <DougReeder> pong
Feb 25 18:28:07 <morphis> DougReeder: I just added https://github.com/webOS-ports/telephony-lib
Feb 25 18:28:22 <morphis> it uses PhoneNumber.js to format them
Feb 25 18:28:43 <morphis> right now its QML only but we can easily extend it and add enyo kinds or what is needed
Feb 25 18:29:11 <morphis> would like to do the same for contact related things
Feb 25 18:29:56 <DougReeder> Ah, okay.  After adding it as a git submodule, we’ll need to tweak the bb recipe.
Feb 25 18:30:11 <morphis> no problem
Feb 25 18:30:21 <ka6sox> morphis, ping?
Feb 25 18:30:25 <morphis> ka6sox: pong
Feb 25 18:31:08 <ka6sox> Garfonso brings up a good point about how originally tablets and phones had different series of webOS and that way Apps could be separated by form factor.
Feb 25 18:31:19 <ka6sox> 2.x for phones and 3.x for tablets
Feb 25 18:31:42 <ka6sox> the app metadata for which app version is used for which form factor is now no longer valid.
Feb 25 18:32:12 <morphis> right, but I think that isn't needed anymore today
Feb 25 18:32:22 <Herrie> morphis: There are quite some people really opposed to Mochi that I've seen as well. I think that offering 2 options would be really good. So Onyx + Mochi
Feb 25 18:32:24 <morphis> as the layout of an app should scale accross different form factors
Feb 25 18:32:30 <Herrie> And create 2 sets of QT Controls
Feb 25 18:32:39 <Herrie> Extend Enyo Mochi with missing bits from Onyx
Feb 25 18:32:49 <morphis> Herrie: hm
Feb 25 18:33:02 <ka6sox> morphis, so all the apps are usable across both platforms without any changes?
Feb 25 18:33:03 <morphis> would be quite a lot work to get both working the same way
Feb 25 18:33:10 <morphis> ka6sox: that is the idea
Feb 25 18:33:16 <morphis> enyo2 already allows this
Feb 25 18:33:31 <ka6sox> yes, but as a practical matter that wasn't done
Feb 25 18:33:49 <ka6sox> even after Enyo2 came out
Feb 25 18:33:55 <ka6sox> (and was back ported to 2.x devices
Feb 25 18:34:07 <ka6sox> sorry 1.x devices)
Feb 25 18:34:18 <morphis> it always depends on what the app does
Feb 25 18:34:23 <morphis> but the ground work is there
Feb 25 18:34:39 <morphis> if a app doesn't play well then it's not the fault of the framework
Feb 25 18:35:15 <ka6sox> mostly the issue is button sizes get too small on phones.
Feb 25 18:35:37 <ka6sox> so either you dumb down the tablet version so when they shrink you still have a reasonable size or you suffer on the phone.
Feb 25 18:36:09 <DougReeder> All apps should use reactive design - that’s largely an issue of developer education.
Feb 25 18:36:16 <morphis> yeah
Feb 25 18:36:30 <morphis> ka6sox: if you statically set 100px for a button width than you're doomed anyway
Feb 25 18:36:31 <ka6sox> DougReeder, how do we educate them?
Feb 25 18:36:43 <ka6sox> of course
Feb 25 18:36:47 <Garfonso> morphis: my issue is the c+dav app. But it's more an issue with legacy, especially the phones which require the mojo account validator.
Feb 25 18:36:47 <DougReeder> Wiki pages?
Feb 25 18:37:03 <Garfonso> I did look into the build process for the webos-internals feeds.
Feb 25 18:37:03 <DougReeder> Human Interface Guidelines?
Feb 25 18:37:22 <ka6sox> DougReeder, that sounds like a really good way to go.
Feb 25 18:37:25 <morphis> Garfonso: yeah, those needs to be done in enyo2 anyway
Feb 25 18:37:39 <DougReeder> Garfonso’s issue is different - needing different builds of an app for webOS 2.x vs. 3.x
Feb 25 18:37:54 <Garfonso> DougReeder: right.
Feb 25 18:38:16 <ka6sox> since we don't have mojo to build against its going to have to be ported anyways?
Feb 25 18:38:16 <DougReeder> phone != 2.x, tablet !=3.x
Feb 25 18:39:05 <ka6sox> morphis, to make the builder happy are we agreed to use 4.x as the OS version internally?
Feb 25 18:39:22 <ka6sox> its not external of the app build process.
Feb 25 18:39:24 <morphis> ka6sox: I think that is fine
Feb 25 18:40:01 <ka6sox> I took a look at the builder code and it should be happy with 4.x
Feb 25 18:40:25 <ka6sox> minimum version for LuneOS apps would be 4.0 and max is whatever number we are up to at the time?
Feb 25 18:40:47 <morphis> right
Feb 25 18:41:07 <ka6sox> okay I'll verify the builder won't barf on that and let you know.
Feb 25 18:41:58 <morphis> ka6sox: which builder?
Feb 25 18:42:04 <ka6sox> autobuilder
Feb 25 18:42:19 <ka6sox> thru webosinternals/build.git
Feb 25 18:42:23 <morphis> we have this setup already up and working
Feb 25 18:42:34 <morphis> https://github.com/webOS-ports/build
Feb 25 18:42:38 <ka6sox> using that or something else
Feb 25 18:42:41 <morphis> that is used by our jenkins
Feb 25 18:42:42 <ka6sox> okay never mind then.
Feb 25 18:42:53 <morphis> :)
Feb 25 18:42:58 <ka6sox> wait
Feb 25 18:43:05 <ka6sox> this is for the apps  we ship right?
Feb 25 18:43:05 <morphis> http://jenkins.nas-admin.org/job/luneos-preware-feeds/ is the jenkins job for it
Feb 25 18:43:18 <morphis> for those we put into our feeds
Feb 25 18:43:34 <morphis> http://feeds.webos-ports.org/
Feb 25 18:43:45 <DougReeder> I’ve made a proposal, which if accepted, would be part of our HIG: http://webos-ports.org/wiki/Swipe_UI
Feb 25 18:47:51 <Herrie> We should write our own Zen of Palm?
Feb 25 18:47:54 <DougReeder> It doesn’t look like the webOS HIG were updated for non-phone form factors: https://developer.palm.com/content/api/design/mojo/user-interface-summary.html
Feb 25 18:48:16 <DougReeder> Yes.
Feb 25 18:48:41 <Herrie> For people not familiar with it: http://www.cs.uml.edu/~fredm/courses/91.308-fall05/palm/zenofpalm.pdf
Feb 25 18:50:07 <DougReeder> Or, rather, update and extend it.
Feb 25 18:51:01 <DougReeder> If you’re on a Mac, you may want to skip FF 36.0 in favor of 36.0.1, when it comes out. :-S
Feb 25 19:04:38 <DougReeder> Maybe we should rename http://webos-ports.org/wiki/Enyo_Ports_UI to “LuneOS Human Interface Guidelines”
Feb 25 19:12:48 <DougReeder> morphis, when my fork of meta-webos-ports is behind, is there a good way to produce a PR with just new changes?  I’ve tried both pulling form upstream + pushing to my fork, and by doing a PR on GitHub directly form upstream to my fork, but they always seem to create an extra “merge” commit.
Feb 25 19:14:39 <morphis> DougReeder: try to rebase on top of the upstream repo
Feb 25 19:14:47 <morphis> pulling will always merge
Feb 25 19:14:52 <morphis> like git rebase origin/master
Feb 25 19:14:59 <morphis> with -i you can edit what you're rebasing
Feb 25 19:17:32 <DougReeder> And what branch of meta-webos-ports should I target with a PR?
Feb 25 19:18:25 <DougReeder> dizzy?
Feb 25 19:35:16 <Herrie> dizzy yes currently
Feb 25 19:38:58 <morphis> DougReeder: right
Feb 25 19:39:19 <DougReeder> Okay, that would cut out some of the chaff
Feb 25 19:40:22 <morphis> nizovn: merged
Feb 25 19:40:50 <nizovn> ok, will do PR to meta-webos-ports
Feb 25 19:41:42 <Herrie> morphis: that phonenumber.js stuff doesn't do matching of phone # to city etc?
Feb 25 19:41:56 <morphis> Herrie: right
Feb 25 19:42:03 <morphis> just formatting
Feb 25 19:42:14 <morphis> for countries and international variants
Feb 25 19:42:19 <Herrie> OK
Feb 25 19:42:31 <morphis> but it uses the same database for number formatting as Android does
Feb 25 19:42:54 <Herrie> We have something for this city stuff already available somewhere?
Feb 25 19:45:40 <morphis> not sure
Feb 25 19:45:50 <morphis> but there are databases for sure
Feb 25 19:54:30 <Herrie> I guess legacy one wasn't open sourced let me check
Feb 25 20:06:30 <morphis> nizovn: PR looks good
Feb 25 20:14:15 <Herrie> morphis: Seems ITU has something published, quite sure webOS piggybacked on that http://www.itu.int/oth/T0202.aspx?parent=T0202
Feb 25 20:14:24 <Herrie> They did for MCC mapping stuff
Feb 25 20:15:24 <morphis> for sure
Feb 25 20:16:19 <Herrie> Not sure what's up with my internet it's slow like hell
Feb 25 20:17:17 <Herrie> Seem to have 50% or so packet loss :S
Feb 25 20:17:20 <Herrie> Way to go UPC :S
Feb 25 20:23:13 <Herrie> Seems it was open sourced :)
Feb 25 20:23:16 <Herrie> See /usr/palm/frameworks/enyo/0.10/framework/build/g11n/phone/geo/data/area
Feb 25 20:25:03 <Herrie> Seems /usr/palm/frameworks/enyo/0.10/framework/build/g11n/phone/geo/javascript/geo.js has the necessary parsing stuff available already :D
Feb 25 20:36:46 <morphis> Herrie: ah nice
Feb 25 20:38:47 <morphis> Herrie: https://github.com/webOS-ports/enyo-1.0/tree/master/framework/build/g11n/phone/geo
Feb 25 20:39:02 <Herrie> Ah seems that Google has libphonenumber used in Android
Feb 25 20:39:03 <Herrie> https://github.com/googlei18n/libphonenumber
Feb 25 20:39:07 <Herrie> Has both JS and Java
Feb 25 20:39:13 <Herrie> Might be more actively updated
Feb 25 20:39:24 <morphis> the JS one is crap
Feb 25 20:39:29 <Herrie> Though numberplans aren't changing that much
Feb 25 20:39:41 <morphis> there is also a C++ one but not sure we want the full blown one
Feb 25 20:39:50 <morphis> using https://github.com/andreasgal/PhoneNumber.js atm
Feb 25 20:41:03 <Herrie> Yeah but that one doesn't do the mapping to area, so when you have an unknown number calling like + 31-(0)20-1234567 it would show "Netherlands, Amsterdam" or something on legacy ;)
Feb 25 20:41:12 <Herrie> So you have an idea where the person is claling from
Feb 25 20:41:21 <morphis> yes, but that can be added easily on top
Feb 25 20:41:35 <morphis> if we have the dataset to do this its just a matter of finding the right entry
Feb 25 20:41:43 <Herrie> Yeah
Feb 25 20:41:47 <Herrie> Formatting varies a bit
Feb 25 20:42:15 <Herrie> Some libs include country code so 3120, others just have a file for country and then just 20
Feb 25 20:42:19 <Herrie> But that's minor
Feb 25 20:42:40 <Herrie> The Enyo geo one is limited to a small number of countries so ideally we'd replace that sometime
Feb 25 20:44:04 <Herrie> Or extend it with more countries, but taking some existing actively updated source would be a better idea I guess
Feb 25 20:45:10 <morphis> that is all minor atm, lets get some usable phone app first :)
Feb 25 20:49:33 <Herrie> morphis: Yes
Feb 25 20:49:45 <Herrie> I saw you did quite some work on the audio service to accomodate some of the stuff :D
Feb 25 20:51:23 <morphis> yes
Feb 25 20:53:29 <Herrie> The big q is: Does audio call work :P ?
Feb 25 22:24:18 <morphis> Herrie: not yet, need to sort a lot other bits first
Feb 25 22:24:22 <morphis> but generally, yes
Feb 25 22:24:32 <morphis> plugging things together the right way takes some time
Feb 25 22:32:57 <Herrie> morphis: I know it's not easy :) Outgoing and incoming calls worked with me last month already, just no audio routing it seemed
**** ENDING LOGGING AT Thu Feb 26 02:59:59 2015