--- Log opened Wed May 10 00:00:05 2017 01:37 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 02:51 -!- jjelen [jjelen@nat/redhat/x-sgfojnrudugupmkn] has joined #navit 07:46 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has joined #navit 07:47 #navit: < jfitie> Any thoughts on this PR? https://github.com/navit-gps/navit/pull/252 08:04 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has quit [Ping timeout: 260 seconds] 08:15 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has joined #navit 08:21 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has quit [Quit: Page closed] 09:06 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has joined #navit 09:07 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has quit [Client Quit] 09:15 -!- circleci-bot [~circleci-@54.146.255.37] has joined #navit 09:15 #navit: < circleci-bot> Success: jfitie's build (#1873; push) in navit-gps/navit (pull/252) -- https://circleci.com/gh/navit-gps/navit/1873?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc 09:15 -!- circleci-bot [~circleci-@54.146.255.37] has quit [Client Quit] 09:16 -!- pini [~pini@bou-fi.pustule.org] has joined #navit 09:28 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 240 seconds] 10:14 -!- j_f-f [~quassel@rs-6.jff-webhosting.net] has quit [Remote host closed the connection] 10:17 -!- j_f-f [~quassel@rs-6.jff-webhosting.net] has joined #navit 10:40 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 11:18 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 11:50 -!- jjelen [jjelen@nat/redhat/x-sgfojnrudugupmkn] has quit [Ping timeout: 240 seconds] 11:57 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 240 seconds] 11:58 #navit: < kazer> hi there 12:29 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 12:42 -!- jfitie [4df99fa5@gateway/web/freenode/ip.77.249.159.165] has joined #navit 13:25 #navit: < kazer> hi jfitie 13:25 #navit: < kazer> i should have a nice solution for you in a couple of days to test layout changes and get automated screenshots of various places at various zoom levels. It will make testing and reviewing layout changes easier 13:29 #navit: < kazer> jfitie: i personally like this layour https://github.com/pgrandin/navit-nuc-layout i find it more legible than our current default one. Or maybe i just grew tired of our default one :) 13:30 #navit: < jfitie> Hey Kazer, excellent. It's a bit complicated at the moment as I'm mainly running everything on Android 13:35 #navit: < kazer> oh, editing the file for tests must be quite painful indeed :) 13:35 #navit: < jfitie> That layout is a bit too busy for my liking. The current default one (at least on Android) is not too bad. I like a simple layout, for example this one https://images-eu.ssl-images-amazon.com/images/G/02/uk-electronics/product_content/tomtom/start60_DV._V147861673_.jpg 13:36 #navit: < jfitie> Did you take a look at this PR? https://github.com/navit-gps/navit/pull/252 13:37 #navit: < kazer> i did yes. I had some concerns about the performance impact thought. That's also why we'll need this layout review system 13:38 #navit: < kazer> ideally, soon we should be able to download additional layouts directly from the app.. We have almost everything we need for that 13:40 #navit: < jfitie> That's why I changed the order to 10- for the new features. On the 4 devices I tested this on, impact on performance felt minimal. On lower zoom levels (>10) performance suffered, but that's fixed with the latest commit. 13:40 #navit: < kazer> ok sweet 13:41 #navit: < kazer> also, you seem to have a knack for design. Are you interested in helping on some other things than layouts? I have a barebone qml2/qt5 UI and we're going to need some help for the design part (because i really suck at this :) ) 13:44 #navit: < jfitie> Well I would really like to, but I can't commit to anything at the moment. I won't have a lot of free time in the coming months (work, kids, ..). But if I do find some more spare time, I'll give you a shout! 13:44 #navit: < kazer> sounds good! 13:45 #navit: < kazer> feel free to jump in at any time, even if it's a simple comment about taste or a suggestion to change a color. We'll have some code in the repo soon 13:45 #navit: < jfitie> Sure! Another question: do you know if any work has been done on multipolygons? Not sure about the current status on that (been following this project sinds about 2012). 13:45 #navit: < kazer> i would just like to involve as many users as possible to get a collegial common sense and avoid pitfalls related to one person's view :) 13:46 #navit: < kazer> yeah, i've seen your 5 years old patch recently... thanks for not giving up on us :) we need to get better at following thru 13:47 #navit: < kazer> i don't think that a lot has been done on multipolygons. That being said, sometimes all it takes is to nag the right person and it might get fixed.. 13:49 #navit: < jfitie> I think it's one of the biggest issues at the moment. I saw some possible solutions on trac (http://trac.navit-project.org/ticket/754), and I know the Zanavi fork has fixed this. 13:50 #navit: < kazer> ah, too bad he did not share the fix :) 13:53 #navit: < kazer> damn yeah this one is gnarly. I'll ping Jan about it 13:53 #navit: < kazer> also this is a perfect example of the need that we have for a better way to test visual changes. Sometime a fix improves one area, but has horrible effect on another and it's currently a bit hard to detect 13:56 #navit: < jfitie> Yep. There are lots of multipolygons in OSM around where I live/work, so I see this issue creeping up all the time. Jan posted some images earlier, I think Circle CI automagically generates some screen shots for every build? Should be easy to add lots of 13:56 #navit: < jfitie> * locations with (possible) issues to the build scripts then. 14:02 #navit: < kazer> yes, exactly. Jan probably shared screenshots from the routing qa, that we use to assess the impact of changes on routes. It's time for us to setup a layout qa, to assess changes in layouts and their performance impact :) 14:06 #navit: < jfitie> Here's Jans comment with screenshots: https://github.com/navit-gps/navit/pull/240#issuecomment-299688542 14:07 #navit: < kazer> yep, that's from routing QA 14:18 #navit: < jfitie> Gotta run - ttyl 14:18 -!- jfitie [4df99fa5@gateway/web/freenode/ip.77.249.159.165] has quit [Quit: Page closed] 16:06 -!- j_f-f [~quassel@rs-6.jff-webhosting.net] has quit [Remote host closed the connection] 16:08 -!- j_f-f [~quassel@rs-6.jff-webhosting.net] has joined #navit 16:52 -!- noradtux [~noradtux@2a02:2028:50f:7801:f184:2a3:6333:c1ae] has quit [Ping timeout: 255 seconds] 16:57 -!- noradtux [~noradtux@2a02:2028:843:1001:3cf7:445b:8798:e637] has joined #navit 17:18 -!- Celelibi [celelibi@179.69.86.79.rev.sfr.net] has quit [Ping timeout: 255 seconds] 17:21 -!- Celelibi [celelibi@46.187.203.77.rev.sfr.net] has joined #navit 18:51 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 19:30 -!- noradtux [~noradtux@2a02:2028:843:1001:3cf7:445b:8798:e637] has quit [Ping timeout: 264 seconds] 19:35 -!- noradtux [~noradtux@2a02:2028:754:1e01:3cf7:445b:8798:e637] has joined #navit 19:44 -!- Horwitz [~mich1@p200300800E023900022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 245 seconds] 19:57 -!- Horwitz [~mich1@p200300800E01B600022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 19:57 -!- mode/#navit [+o Horwitz] by ChanServ 22:01 -!- noradtux [~noradtux@2a02:2028:754:1e01:3cf7:445b:8798:e637] has quit [Ping timeout: 240 seconds] --- Log closed Thu May 11 00:00:06 2017