--- Log opened Mon Nov 06 00:00:12 2017
00:28 -!- Horwitz [~mich1@p200300800E696800022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
00:40 -!- Horwitz [~mich1@p200300800E0DF600022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:40 -!- mode/#navit [+o Horwitz] by ChanServ
00:43 -!- Josue [bdfa1d72@gateway/web/freenode/ip.189.250.29.114] has joined #navit
00:44 #navit: < Josue> Hello
00:52 -!- Josue [bdfa1d72@gateway/web/freenode/ip.189.250.29.114] has quit [Quit: Page closed]
01:27 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds]
01:34 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
03:48 -!- noradtux [~noradtux@port-5841.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
03:48 -!- noradtux [~noradtux@port-18236.pppoe.wtnet.de] has joined #navit
05:10 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 260 seconds]
05:20 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
05:20 -!- noradtux [~noradtux@port-18236.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
05:21 -!- noradtux [~noradtux@port-56857.pppoe.wtnet.de] has joined #navit
06:31 -!- Netsplit *.net <-> *.split quits: Millesimus, ColdFyre
06:35 -!- noradtux [~noradtux@port-56857.pppoe.wtnet.de] has quit [Ping timeout: 260 seconds]
06:35 -!- noradtux [~noradtux@port-56857.pppoe.wtnet.de] has joined #navit
06:43 -!- youte [~youte@32.ip-37-187-37.eu] has quit [Ping timeout: 258 seconds]
07:12 -!- Netsplit over, joins: ColdFyre, Millesimus
07:14 -!- noradtux [~noradtux@port-56857.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
07:15 -!- noradtux [~noradtux@port-56857.pppoe.wtnet.de] has joined #navit
08:32 -!- youte [~youte@32.ip-37-187-37.eu] has joined #navit
16:23 #navit: < kazer> hi there
16:24 #navit: < kazer> charles__: museum.png isn't expected, as we generate png images for each size that we might need (like museum_22_22.png)
16:24 #navit: < jkoan> hi kazer
16:24 #navit: < kazer> charles__: thanks for the update on imperial. It shouldn't be too hard to replicate
16:24 #navit: < ilovekiruna> hi kazer, hi jkoan
16:25 #navit: < jkoan> hi ilovekiruna
16:26 #navit: < kazer> jkoan: re: wikipedia, definitely. Want to put a note in trello or a task in trac so that we don't forget?
16:26 #navit: < kazer> ilovekiruna: thanks for taking care of the slides!
16:26 #navit: < kazer> it looks like you exported it with my comment though :) look at the slide with the navit UI example
16:27 #navit: < jkoan> kazer: we must only discuss one thing
16:27 #navit: < ilovekiruna> kazer: :-o
16:27 #navit: < ilovekiruna> didnt notice about the comment
16:27 #navit: < ilovekiruna> kazer: we can fix that
16:27 #navit: < ilovekiruna> kazer: i hope
16:35 #navit: < kazer> ilovekiruna: no big deal, it's just a yellow marker in a corner with a note that expands when you hover over it
16:35 #navit: < kazer> true that libreoffice doesn't make comments really obvious
16:40 #navit: < jkoan> kazer: what do you think about git submodules? for the fdroid metadata we need a submodule
16:41 #navit: < ilovekiruna> kazer: will check soon about the volvo pics
16:41 #navit: < ilovekiruna> jkoan: where can i get bleeding edge versions of navit?
16:41 #navit: < jkoan> for android?
16:41 #navit: < ilovekiruna> yes
16:42 #navit: < jkoan> play store?
16:42 #navit: < ilovekiruna> dont we just push there "stable" releases?
16:42 #navit: < jkoan> or for one time install you must search for last android_arm build
16:42 #navit: < jkoan> you must sign up for beta channel
16:43 #navit: < ilovekiruna> cool, that was what i looked for
16:43 #navit: < ilovekiruna> can you please explain me how
16:44 #navit: < jkoan> jep, only searching for the link
16:46 #navit: < jkoan> https://play.google.com/apps/testing/org.navitproject.navit 
16:46 #navit: < kazer> jkoan: we need a submodule?
16:46 #navit: < ilovekiruna> kazer: look here: https://imgur.com/a/XcZWn
16:47 #navit: < kazer> ilovekiruna: nice! Navit can already do that but it's poorly documented. I'll have to find an example
16:47 #navit: < ilovekiruna> i wonder if we can change the number of symbols displayed depending on the zoom level.
16:47 #navit: < ilovekiruna> yesterday while driving the whole street was covered by P symbols :(
16:47 #navit: < kazer> depending on the zoom level, that's exacly how it works :)
16:48 #navit: < kazer> which map layout are you using?
16:48 #navit: < ilovekiruna> how to c that?
16:49 #navit: < kazer> from the settings/display/layout menu
16:49 #navit: < kazer> anyway, https://github.com/navit-gps/navit/blob/trunk/navit/navit_shipped.xml#L1939 is probably what you want to change
16:52 #navit: < ilovekiruna> change the order?
16:53 #navit: < ilovekiruna> kazer: I am on the car layout
16:53 #navit: < ilovekiruna> should be car-android better?
16:55 #navit: < kazer> it's really a matter of taste
16:56 #navit: < ilovekiruna> kazer: i meant with regard to the number of symbols displayed
16:56 #navit: < ilovekiruna> because in any zoom level, i think it isnt good that the road is pretty much invisible because of all the symbols on top of them
16:58 #navit: < kazer> ilovekiruna: true. we should generate examples of the various layouts at various zoom level. This should be quite easy to script
16:59 #navit: < kazer> jkoan: https://trac.navit-project.org/ticket/1290#comment:5 fixed ?
17:00 #navit: < jkoan> why not?
17:00 #navit: < ilovekiruna> kazer: I made one more observation, but not sure, if one fixed it already
17:01 #navit: < ilovekiruna> when closing and reopening the app the map doesnt move a long with the route anymore
17:01 #navit: < ilovekiruna> just completely closing navit and restarting it, resolves it
17:02 #navit: < ilovekiruna> i think the question with the zoom-levels I should put on my agenda
17:02 #navit: < kazer> jkoan: doesn't seem obvious to me reading the comments. The last one is me complaining that the patch is malformed
17:02 #navit: < ilovekiruna> fits perfectly with my device testing
17:02 #navit: < kazer> ilovekiruna: talking about device testing!
17:02 #navit: < kazer> http://trac.navit-project.org/ticket/1356 
17:03 #navit: < kazer> ilovekiruna: closing and reopening the map, do you mean switching to another app? what's different between closing and completely closing ?
17:04 #navit: < ilovekiruna> kazer: that bug seems related to what i work on, very true
17:04 #navit: < ilovekiruna> i mean leaving app via home buttom
17:04 #navit: < ilovekiruna> one just closes the device via power button
17:04 #navit: < ilovekiruna> i think i had those two
17:05 #navit: < ilovekiruna> completely closing means, using the quit button and also remove it from the task switcher of android
17:05 #navit: < jkoan> kazer: look at this: https://github.com/gsantner/markor do you see the submodule?
17:05 #navit: < kazer> ok. this might be worth a ticket as it could be hindering the UX
17:05 #navit: < ilovekiruna> kazer: when i next drive a bit longer can try to confirm it
17:06 #navit:  * ilovekiruna will be off now for a while, need to rest, trip left me a bit sick
17:06 #navit: < kazer> jkoan: i see. so we'd push the metadata tags in another repo and link to it via a submodule. you don't want to use http anymore?
17:06 #navit: < kazer> ilovekiruna: get better!
17:11 #navit: < jkoan> the metadata is only for the store --> fdroid app it contains the name, description and so on, and the bonus feature is that we can translate the description in the store
17:18 #navit: < kazer> makes sense. Want to submit a PR to get this done?
17:19 #navit: < kazer> also that android issue is really problematic. think you'd have some time to help on this?
17:19 #navit: < jkoan> #1356?
17:22 #navit: < kazer> yep
17:27 #navit: < jkoan> could you provide logcat also?
17:28 #navit: < kazer> attaching to the ticket
17:28 #navit: < jkoan> thx
17:33 #navit: < kazer> done, updated the ticket description too
17:35 #navit: < jkoan> i see the problem will be fixed after i get notifications working again
17:36 #navit: < kazer> ha? 
17:38 #navit: < jkoan> the app is crashing because of broken notifications
17:42 #navit: < kazer> ok
17:42 #navit: < kazer> can you please rebase https://github.com/navit-gps/navit/pull/315/files ?
17:42 #navit: < kazer> and remove the commit about navit/android/src/org/navitproject/navit/NavitTextTranslations.java 
17:43 #navit: < jkoan> github can do automatic rebase :X
17:44 #navit: < kazer> yeah but the commit log will still be messy :) we need to get better at this
17:44 #navit: < jkoan> okay, i will do soon
17:44 #navit: < kazer> thanks. i can help if you aren't too familiar with it. it should be quite easy
18:12 -!- Josue [bdfaa5bc@gateway/web/freenode/ip.189.250.165.188] has joined #navit
18:12 #navit: < Josue> Hello
18:22 #navit: < kazer> hey Josue 
18:23 #navit: < Josue> thanks for answering,  I've written before
18:24 #navit: < Josue> i´m interested on how to write Navit's street name on a text file 
18:25 #navit: < Josue> i´m using a gps and allready have on screen the name of the streeet where i am
18:26 #navit: < Josue> so, what i´m trying to do is to export that street name when pushing a screen button, could it be possible for u to help me? 
18:36 #navit: < kazer> yeah sure. i need to finish something, probably need 45-60 mins
18:41 #navit: < Josue> ok ok, could it be possible to continue on facebook messenger or what´s app?
18:49 #navit: < kazer> i have neither of those :)
18:54 #navit: < kazer> we also like to favor group discussions in the channel vs 1:1 interactions. helps spreading the knowledge
19:04 #navit: < kazer> Josue: ok i'm available. So there's several ways to do what you want
19:04 #navit: < kazer> the easiest is to hook the OSD item with a navit internal command, and have this command export the text to a file
19:04 #navit: < kazer> are you using Linux?
19:05 #navit: < Josue> yes, i'm running navit on an Raspberry Pi with Raspbian
19:07 #navit: < kazer> ok perfect.
19:07 #navit: < kazer> do you want to log only the latest street or do you want that to be more of a log with multiple entries?
19:08 #navit: < kazer> in a nutshell, for the easy way you probably want to use a spawn() call : https://wiki.navit-project.org/index.php/Command_interface
19:08 #navit: < Josue> i just wanna log the street where i am, when pressing a button
19:09 #navit: < kazer> but you want '>' (overwrite) or '>>' (append) ?
19:09 #navit: < kazer> here's an example of defining an OSD item that uses spawn : https://github.com/pgrandin/navit-nuc-layout/blob/master/nuc_osd.xml#L39
19:10 #navit: < kazer> this example uses an external script that will take a screenshot when the item is clicked
19:11 #navit: < kazer> so in your case i think something like : spawn("/bin/bash", "<path to your script>", "${tracking.item.street_name}") should work
19:11 #navit: < kazer> the script could be as simple as : echo $1 > yourfile
19:11 #navit: < kazer> (or >> if you want to keep track of more than one entry)
19:11 #navit: < kazer> does it make sense?
19:12 #navit: < Josue> sure
19:12 #navit: < Josue> for sure 
19:13 #navit: < Josue> is it possible to concatenate the street name with a specific text?
19:14 #navit: < Josue> for example, You are on tracking.item.street_name 
19:15 #navit: < kazer> yep, just replace the 3rd parameter with "You are on ${tracking.item.street_name}" and i think that it should work
19:16 #navit: < Josue> thanks a lot man, i don't have my Rpi right now but i'll try to solve it with the information u gave me
19:17 #navit: < kazer> np, anytime
19:17 #navit: < kazer> where are you from? We're usually mosly active during western europe evenings. sometimes the day, but it varies a bit
19:17 #navit: < Josue> i´m from Mexico
19:18 #navit: < kazer> ok cool!
19:18 #navit: < Josue> so, at this time is good for u ?
19:19 #navit: < kazer> i'm actually on PST, but most of the people here are on GMT+1 or so. I'm online pretty much everyday at this time yeah
19:20 #navit: < Josue> sorry if my english isn't so good
19:20 #navit: < Josue> ok man, i'm gonna make some code arriving home
19:21 #navit: < kazer> don't worry about that, I think that charles__ and Number6 are the only native english speakers :)
19:21 #navit: < kazer> cool, see you then!
19:21 #navit: < Josue> thanks again
19:21 #navit: < Josue> ejejeje
19:21 #navit: < Josue> bye
19:56 #navit: < ilovekiruna> kazer: you said what i said about the visualization is already possible?
19:59 #navit: < kazer> ilovekiruna: yeah absolutely. Using dbus for example
20:00 #navit: < kazer> https://github.com/navit-gps/navit/blob/trunk/ci/run_linux_tests.sh could be used as a basis
20:00 #navit: < kazer> we also need to put that script back in the ci (hasn't been implemented in civ2 yet)
20:01 #navit: < kazer> i think that a mix of that bash script (for the screen capture) and this script https://github.com/navit-gps/navit/blob/trunk/ci/dbus_tests.py (for the dbus control) would do just nicely
20:02 #navit: < ilovekiruna> kazer: could that run on android?
20:02 #navit: < ilovekiruna> for sailfish i would be quite optimistic
20:09 #navit: < kazer> ilovekiruna: it could but you might need to replace the dbus calls with appium actions
20:09 #navit: < kazer> which would be great, as it'll help build/expand the actual UI tests
20:10 #navit: < ilovekiruna> kazer: ilost a bit the point now
20:10 #navit: < kazer> ilovekiruna: you wanted to generate screenshots of different map layouts and different POI layouts, at different zoom levels, right?
20:11 #navit: < ilovekiruna> kazer: what i asked now was sth different
20:11 #navit: < ilovekiruna> I was asking about the thing where we have sth like the volvo thingy
20:12 #navit: < kazer> ohhhh
20:12 #navit: < kazer> ilovekiruna: i used the dbus method to generate the screenshots here : http://trac.navit-project.org/ticket/854#comment:7 for example
20:13 #navit: < ilovekiruna> seems familiar :)
20:14 #navit: < kazer> :) 
20:14 #navit: < ilovekiruna> i was also thinking of using that, when making video for sailfish
20:14 #navit: < kazer> oh, i even copied the scripts in that comment. Cool
20:14 #navit: < kazer> now, the viewport thing
20:17 #navit: < ilovekiruna> u can compare what i found here: https://together.jolla.com/question/39930/howto-take-a-screenshot-from-the-command-line/
20:21 #navit: < kazer> oh, cool
20:21 -!- Josue [bdfaa5bc@gateway/web/freenode/ip.189.250.165.188] has quit [Quit: Page closed]
20:38 #navit: < kazer> ilovekiruna: super ugly example of the 2nd view port : https://imgur.com/a/Vua0O 
20:39 #navit: < kazer> this one is done using the (undocumented) auxmap OSD : <osd enabled="yes" type="auxmap" w="320" h="320" x="10" y="10"/> 
20:39 #navit: < kazer> i had to search my logs from 2005 to remember how it was working :)
20:40 #navit: < kazer> oh, 2007 actually
20:41 #navit: < ilovekiruna> kazer: so i just should put it in my navit.xml file and test later on?
20:42 #navit: < ilovekiruna> kazer: one more thing i wonder, if we make useful improvements to navit.xml maybe we should add that then to navit_shipped.xml
20:42 #navit: < ilovekiruna> what i do not understand yet, that viewport is permanent, right?
20:42 #navit: < kazer> yes, adding that line to your navit.xml file should work. I took the screenshot today using that line
20:43 #navit: < kazer> osd items can be activated or hidden programatically
20:43 #navit: < kazer> also, auxmap is just a really crude example of how to implement it, but it's not the only way
20:43 #navit: < ilovekiruna> so we could then when approaching a turn or a round-about we could automatically activate it and then after the turn was made, deactivate it again, right?
20:43 #navit: < kazer> the code is maybe 100 lines or so, this one is really basic
20:44 #navit: < kazer> yes, for example you could make that based on navigation.item[1].length . if it's <200m activate the OSD
20:45 #navit: < ilovekiruna> cool
20:45 #navit: < ilovekiruna> when a bit better again, will take care of that
20:45 #navit: < kazer> it's possible to get this to work using OSD scripts, and it's also possible to expand the existing OSD so that it can do it natively
20:45 #navit: < kazer> awesome
20:45 #navit: < ilovekiruna> would really like to c it in navit and hope it will also get shipped ;-)
20:45 #navit: < kazer> yeah, navit_shipped is long overdue for a rework
20:46 #navit: < kazer> for example we should add a few routing profiles, i have a map layout based on android that i also want to push there
20:46 #navit: < kazer> that's where having the script to generate captures of layouts at various zoom levels would help
20:47 #navit: < ilovekiruna> actually u know, sometimes i would wish we had sth like NavitConfigurator as an app version included
20:47 #navit: < kazer> the default `android` layout sucks, you zoom out like 2 times and you only see highways
20:47 #navit: < kazer> yeah me too, although i'd offer that as a web app instead maybe
20:48 #navit: < ilovekiruna> navitconfigurator is too much geeky, still
20:48 #navit: < kazer> exactly
20:48 #navit: < ilovekiruna> u need to know the xml code :(
20:49 #navit: < kazer> yep. http://www.chengfolio.com/google_map_customizer# < that would be cool
20:49 #navit: < kazer> actually it shouldn't be difficult to build layouts from openstreetmaps layouts
20:50 #navit: < ilovekiruna> that is actually amazing
20:50 #navit: < ilovekiruna> that customizer
20:52 #navit: < kazer> yep
20:54 -!- xenos1984 [~xenos1984@p4FDD0B62.dip0.t-ipconnect.de] has joined #navit
23:03 -!- xenos1984 [~xenos1984@p4FDD0B62.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
23:12 #navit: < kazer> ilovekiruna: i think that we could get something to work with http://editor.openmaptiles.org 
23:33 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 240 seconds]
23:47 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
--- Log closed Tue Nov 07 00:00:13 2017