--- Log opened Thu Mar 19 00:00:50 2015
00:48 -!- KaZeR [~KaZeR@64.201.252.132] has quit [Remote host closed the connection]
00:49 -!- KaZeR [~KaZeR@64.201.252.132] has joined #navit
00:49 -!- mode/#navit [+o KaZeR] by ChanServ
00:53 -!- KaZeR [~KaZeR@64.201.252.132] has quit [Ping timeout: 252 seconds]
01:14 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
01:18 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit
01:19 -!- mode/#navit [+o KaZeR] by ChanServ
01:26 -!- magruder [redurgam@gateway/shell/panicbnc/x-catdsaoqubolgnqs] has quit [Ping timeout: 272 seconds]
01:36 -!- redurgam [redurgam@gateway/shell/panicbnc/x-hjlnxxzdqlfascvd] has joined #navit
05:21 -!- circleci-bot [~circleci-@ec2-54-196-254-121.compute-1.amazonaws.com] has joined #navit
05:21 #navit: < circleci-bot> Timed out: pgrandin's build (#107; push) in navit-gps/navit (maptool) -- https://circleci.com/gh/navit-gps/navit/107
05:21 -!- circleci-bot [~circleci-@ec2-54-196-254-121.compute-1.amazonaws.com] has quit [Client Quit]
06:11 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Remote host closed the connection]
06:30 -!- jjelen [jjelen@nat/redhat/x-toaiqxmoxzbuzdsf] has joined #navit
06:59 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has joined #navit
07:23 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
07:41 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has joined #navit
07:54 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
08:06 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has joined #navit
08:09 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has joined #navit
08:12 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Quit: Page closed]
08:13 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
08:39 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
12:20 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
15:04 -!- KaZeR [~KaZeR@64.201.252.132] has joined #navit
15:05 -!- mode/#navit [+o KaZeR] by ChanServ
15:05 #navit: <@KaZeR> hi there
15:15 #navit: < woglinde> hi kazer
15:27 #navit: <@KaZeR> fyi, i was able to process a planet.pbf up to phase 4 in circle ci : https://circleci.com/gh/navit-gps/navit/107
15:28 #navit: <@KaZeR> free processing, and maybe free storage and bandwidth...
15:57 -!- jjelen [jjelen@nat/redhat/x-toaiqxmoxzbuzdsf] has quit [Ping timeout: 252 seconds]
16:08 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 255 seconds]
16:36 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has quit [Ping timeout: 264 seconds]
16:44 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
17:42 -!- jandegr [57414f02@gateway/web/freenode/ip.87.65.79.2] has joined #navit
17:43 -!- robertp [584aadb5@gateway/web/freenode/ip.88.74.173.181] has joined #navit
17:44 #navit: < robertp> hello, someone here? :D
17:44 -!- tryagain [~quassel@178.216.76.56] has joined #navit
17:44 #navit: < jandegr> hi all
17:45 #navit: < robertp> hi
17:50 #navit: < tryagain> KaZeR great results
17:50 #navit: <@KaZeR> hey robertp! welcome!
17:51 #navit: < tryagain> are these time limits documented somewhere
17:51 #navit: <@KaZeR> jandegr: we past the 5k installs of r6021 last night
17:51 #navit: <@KaZeR> tryagain: thanks. i need your help to tackle phase 4 now :)
17:51 #navit: < tryagain> I guess we have two options: tweak maptool
17:51 #navit: < tryagain> or tweak ci people
17:51 #navit: < tryagain> :)
17:52 #navit: <@KaZeR> tryagain: unfortunately, 2 hours is a hard limit. I asked them. We need to find a way to split the task. One idea i had was to add a timeout option, where maptool would save the progress and this would allow restarting the phase at a given point
17:52 #navit: <@KaZeR> do you think it would be complicated ?
17:53 #navit: < tryagain> I'm wondering if there is some limit for the whole process, given for all commands
17:53 #navit: <@KaZeR> also it looks like pbf processing is MUCH faster than osm. And i had a few failures processing OSM because of a broken tag
17:53 #navit: < tryagain> o5c could be even more fast
17:53 #navit: <@KaZeR> as far as i know, it's only a limit per task. so other limit could be our artifact quota, but we could still upload the file somewhere at the end
17:53 #navit: < tryagain> that's why it was implemented
17:54 #navit: <@KaZeR> but o5c needs a first conversion right? can we download a planet.o5c somewhere? i don't recall seeing one
17:54 #navit: < tryagain> s/o5c/o5m/
17:54 #navit: < tryagain> ah, sure
17:54 #navit: < tryagain> but we can download it from our server for the first time, and update it afterwards
17:55 #navit: < tryagain> anyway, it will affect only the first phase
17:55 #navit: < tryagain> so probably no need to bother
17:55 #navit: < robertp> back on keys
17:55 #navit: <@KaZeR> mmm. yeah one our for the first phase is acceptable. there is no local file caching so the "cache" is actually downloaded from s3 everytime
17:56 #navit: <@KaZeR> hey robertp
17:58 #navit: < tryagain> what is "command" in terms of ci? Can it be ran in some loop?
17:58 #navit: < robertp> maybe this sounds alien, bit its the very first chat for me....
17:59 #navit: <@KaZeR> mmm. command is actually an arbitrary shell command. we should be able to have it loop. At worst you can put the loop in a script and call that script. but if you loop on the same command, then you face the timeout issue again
17:59 #navit: <@KaZeR> robertp: glad it's with us then :) your project looks really, really cool!
18:00 #navit: < robertp> but i have a lot work to do
18:01 #navit: < tryagain> would it be limit for the whole loop or for a single execution of loop body?
18:02 #navit: < tryagain> anyway, we could unroll the loop and have 30 or so copies of the same command
18:02 #navit: <@KaZeR> tryagain: it would be for the loop itself
18:03 #navit: <@KaZeR> exactly. if we resume from the end, the command would take only a few seconds to process anyway
18:03 #navit: <@KaZeR> robertp: i'd be happy to help you. Do you have a working prototype or are you still working on it? Any code that you can share? How can i help you?
18:03 #navit: < robertp> KaZeR: how do you control navit? touch and wheel-buttons?
18:04 #navit: < robertp> KaZeR: I am still working on the embedding of navit.
18:04 #navit: < tryagain> the idea is to make maptool to process only limited number of slices at phase4, and be able to restart from the needed slice within phase 4.
18:04 #navit: <@KaZeR> robertp: exactly. i've been thinking about your rotary encoder problematic. Currently we do not have a tab-index in gui internal so that makes things a bit difficult
18:04 #navit: < robertp> KaZeR: the musicplayer works right now
18:04 #navit: <@KaZeR> tryagain: yes. do we know the number of slices beforehand ? it seems to be around 42 currently
18:05 #navit: <@KaZeR> robertp: cool. what would you think of trying to put that into navit itself? it might make your life easier.. and it might be useful for other users
18:05 #navit: < tryagain> it depends on slice size parameter and number of nodes in planet.bin
18:05 #navit: < tryagain> planet.osm
18:06 #navit: < tryagain> worst thing is that we would have to implement same behaviour on phase12. Longest one, and for now we cant even restart it from the beginning.
18:07 #navit: < robertp> KaZeR: sure. but before i'll have to translate the comments in the code from german to english ;)
18:09 #navit: <@KaZeR> tryagain: well if we can move up to phase 12 it's already a progress :)
18:09 #navit: <@KaZeR> what is blocking us from restarting phase 12 ?
18:09 #navit: <@KaZeR> robertp: ha yeah that would help.. my german really sucks :)
18:10 #navit: < robertp> i didn't think about sharing the code outside my friends so german was an option
18:11 #navit: < tryagain> main stopper is that nobody reachable fully understands phase12, and restarting from that phase produced me once a broken planet.bin
18:14 #navit: < tryagain> maybe i just have to redo the test
18:15 #navit: <@KaZeR> robertp: i definitely understand
18:16 #navit: <@KaZeR> tryagain: we can leverage circle ci to do the tests
18:16 #navit: <@KaZeR> you just need to commit to the maptool branch to trigger the test
18:24 #navit: < robertp> KaZeR: i like the Qt-gui idea. Could you explai it a littel?
18:25 #navit: <@KaZeR> sure. Currently we already have a qt4/qml gui, but it was never really finished. the internal gui is great because it provides a standard user experience and works on low-end devices, but it has some limitations.
18:25 -!- xenos1984 [~xenos1984@p578a6c81.dip0.t-ipconnect.de] has joined #navit
18:25 #navit: <@KaZeR> users are used to get more eye-candies today. I want more eye-candies. I have been having a look at qt5/qml2 and you can do some really fancy things
18:27 #navit: <@KaZeR> here's an example : https://www.youtube.com/watch?v=8X6PI6CR3-w and here is another one : https://www.youtube.com/watch?v=Bx7iEHlGxMU
18:28 #navit: < robertp> qt5 isnt available via apt-get. is this a problem?
18:28 #navit: <@KaZeR> qt5 is fairly new so it's not packaged for all distros yet. http://qt-project.org/wiki/RaspberryPi_Beginners_guide
18:29 #navit: <@KaZeR> robertp: i am working on providing pre-built up to date package of navit btw. we should even be able to provide a ready-to-flash navit image soon ( because compiling on a pi sucks )
18:31 #navit: < robertp> I know the compile it youself guide. possibly it solves my embedding problems
18:33 #navit: <@KaZeR> ok cool
18:34 #navit: <@KaZeR> so are you interested in joining forces ? :)
18:34 #navit: < robertp> but integrating the mp3player to navit is cooler :D
18:34 #navit: < robertp> yes i am
18:35 #navit: < robertp> how do such plugins work generally?
18:36 #navit: <@KaZeR> cool!
18:38 #navit: <@KaZeR> our plugin documentation sucks, but i can help you with this. Here is our current doc : http://wiki.navit-project.org/index.php/Plugin
18:38 #navit: <@KaZeR> I will enhance it as we work on your own plugin
18:40 #navit: < robertp> Ah. okay. I didnt knew. seems to be more simple as i expected
18:41 #navit: <@KaZeR> it's fairly simple honestly. And your plugin can define new functions, a new osd, lots of stuffs. the only thing that is slightly complicated is communication between plugins currently
18:42 #navit: <@KaZeR> but you can do things like command_evaluate(&navit, "gui.spotify_volume_up()" ); from a plugin to call a function somewhere else. just as you would do from the osd
18:43 #navit: < robertp> so i could create a plugin for my application and connect it to navit instead of embedding navit
18:43 #navit: < robertp> ?
18:45 #navit: <@KaZeR> from what i know of your project, there would be two plugins ( canbus, mp3) and one gui
18:48 #navit: < robertp> mp3 and I2C maybe OBD via ISO-something. Canbus is done by a separate device inside the dashboard
18:48 #navit: <@KaZeR> ha ok. well as i told you on the forum, i need to drive a i2c display myself so...
18:49 #navit: < robertp> but mp3 is the most important
18:49 #navit: <@KaZeR> how are you fetching the canbus frames for your other device? i2c too? is it raw canbus or something like obd ?
18:49 #navit: <@KaZeR> if your code is already working it should be quite easy to convert it in a plugin
18:50 #navit: < robertp> its data from the ecu. no diagnose at all. diagnose is done via volkswagen-typical undocumented KWP-Protocol.
18:50 #navit: < robertp> mp3 works well
18:51 #navit: <@KaZeR> interesting. i will have to go afk for ~1h soon but i will be back after
18:51 #navit: < robertp> the other stuff is not implemented yet. just ideas.
18:51 #navit: < robertp> ok
18:51 #navit: <@KaZeR> are you familiar with github? we could start collaborating there
18:55 #navit: < robertp> no. i set up a subversion server on a pi behind my router.
18:55 #navit: < robertp> but i could learn :D
18:57 #navit: <@KaZeR> ok cool. git is quite easy to use, and i can help you. i would recommend starting by creating an account on github, creating a repo and publishing your code there. then i can help you convert it into a plugin
18:58 #navit: <@KaZeR> if your code is in svn you can even use https://import.github.com/new which will do everything for you
19:03 #navit: <@KaZeR> have to go, i should be back in ~1h or so
19:15 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 256 seconds]
19:18 #navit: < Navit> mdankov * r6026 /trunk/navit/navit/maptool/misc.c: Fix:maptool:Fix experimental map by moving coastline to order=9. See #845. http://sourceforge.net/p/navit/code/6026/
20:07 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has joined #navit
20:24 -!- robertp [584aadb5@gateway/web/freenode/ip.88.74.173.181] has quit [Quit: Page closed]
20:34 -!- tryagain [~quassel@178.216.76.56] has quit [Remote host closed the connection]
20:40 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
20:46 -!- woglinde [~henning@g225110166.adsl.alicedsl.de] has joined #navit
21:03 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has joined #navit
21:18 -!- woglinde [~henning@g225110166.adsl.alicedsl.de] has quit [Remote host closed the connection]
21:18 -!- woglinde [~henning@g225110166.adsl.alicedsl.de] has joined #navit
21:20 -!- Robertp [584aadb5@gateway/web/freenode/ip.88.74.173.181] has joined #navit
21:21 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
21:22 -!- jandegr [57414f02@gateway/web/freenode/ip.87.65.79.2] has left #navit []
21:26 -!- xenos1984 [~xenos1984@p578a6c81.dip0.t-ipconnect.de] has quit [Quit: Leaving.]
21:26 -!- Robertp [584aadb5@gateway/web/freenode/ip.88.74.173.181] has quit [Ping timeout: 246 seconds]
21:32 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has joined #navit
22:21 -!- _rd [~rd@p4FD1E55B.dip0.t-ipconnect.de] has quit []
22:45 -!- Ernesto75 [5710d758@gateway/web/freenode/ip.87.16.215.88] has joined #navit
22:47 #navit: < Ernesto75> hello
22:48 #navit: < Ernesto75> any news about building navit for maemo? i saw the last try timed out, is because it request to answer yes or no to the question: add user in scratchbox?
22:48 #navit: < Ernesto75> Add user ubuntu to group 'sbox'? [yes/no] (yes): command bash make_navit took more than 10 minutes since last output
22:52 #navit: <@KaZeR> hey Ernesto75
22:52 #navit: <@KaZeR> yes indeed the last timeout was because of that, but i had some other issues with setting up scratchbox. I did not give up, i just had to work on something else
22:53 #navit: <@KaZeR> there is actually a way for you to help me : if you are able to reproduce the setup on a fresh install and help me find the missing steps that would help a lot
22:53 #navit: <@KaZeR> you are running on ubuntu right ?
22:54 #navit: < Ernesto75> yes
22:56 #navit: <@KaZeR> ok. there is a really simple way to reproduce our build environment then. apt-get install docker.io, then run docker run -ti ubuntu-12.04
22:56 #navit: <@KaZeR> and you will be in the same environment ( minus a few packages ) than the one where we run our tests
22:56 #navit: <@KaZeR> so if you run the scratchbox install script from there, you can reproduce the latest issue.. and maybe expand the setup script :)
23:00 #navit: < Ernesto75> i see, so i'll install and let you know
23:03 #navit: <@KaZeR> ok cool. feel free to ping me whenever you want
23:28 -!- Ernesto75 [5710d758@gateway/web/freenode/ip.87.16.215.88] has quit [Quit: Page closed]
23:53 -!- woglinde [~henning@g225110166.adsl.alicedsl.de] has quit [Ping timeout: 255 seconds]
23:57 -!- robertp [584aadb5@gateway/web/freenode/ip.88.74.173.181] has joined #navit
--- Log closed Fri Mar 20 00:00:01 2015