--- Log opened Thu Aug 27 00:00:38 2015
00:26 -!- rd_ [~rd@p57A0FCF3.dip0.t-ipconnect.de] has joined #navit
00:40 -!- mithrandir___ [~chatzilla@dslb-084-056-166-031.084.056.pools.vodafone-ip.de] has quit [Remote host closed the connection]
00:45 -!- rd_ [~rd@p57A0FCF3.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
00:51 -!- rd_ [~rd@p57A0FCF3.dip0.t-ipconnect.de] has joined #navit
01:52 -!- rd_ [~rd@p57A0FCF3.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
01:53 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has joined #navit
03:14 -!- robertp [bc5c2134@gateway/web/freenode/ip.188.92.33.52] has joined #navit
03:46 -!- jjelen [jjelen@nat/redhat/x-ypmugfyoaohjqlvw] has joined #navit
03:54 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #navit
05:04 -!- circleci-bot [~circleci-@ec2-54-237-33-219.compute-1.amazonaws.com] has joined #navit
05:04 #navit: < circleci-bot> Failed: greg42's build (#534; push) in navit-gps/navit (pull/20) -- https://circleci.com/gh/navit-gps/navit/534
05:04 -!- circleci-bot [~circleci-@ec2-54-237-33-219.compute-1.amazonaws.com] has quit [Client Quit]
05:14 -!- juse [~juse@85-76-134-213-nat.elisa-mobile.fi] has joined #navit
05:34 -!- circleci-bot [~circleci-@ec2-174-129-118-92.compute-1.amazonaws.com] has joined #navit
05:34 #navit: < circleci-bot> Fixed: greg42's build (#535; push) in navit-gps/navit (pull/20) -- https://circleci.com/gh/navit-gps/navit/535
05:34 -!- circleci-bot [~circleci-@ec2-174-129-118-92.compute-1.amazonaws.com] has quit [Client Quit]
06:04 -!- circleci-bot [~circleci-@ec2-50-16-25-199.compute-1.amazonaws.com] has joined #navit
06:04 #navit: < circleci-bot> Fixed: greg42's build (#536; push) in navit-gps/navit (pull/5) -- https://circleci.com/gh/navit-gps/navit/536
06:04 -!- circleci-bot [~circleci-@ec2-50-16-25-199.compute-1.amazonaws.com] has quit [Client Quit]
06:47 -!- juse2 [~juse@b738.ip16.netikka.fi] has joined #navit
06:50 -!- juse [~juse@85-76-134-213-nat.elisa-mobile.fi] has quit [Ping timeout: 245 seconds]
09:43 -!- robertp [bc5c2134@gateway/web/freenode/ip.188.92.33.52] has quit []
12:02 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Leaving]
12:08 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
12:15 -!- jjelen [jjelen@nat/redhat/x-ypmugfyoaohjqlvw] has quit [Ping timeout: 240 seconds]
12:26 -!- tryagain [~quassel@178.216.76.67] has joined #navit
12:43 -!- jandegr [57416108@gateway/web/freenode/ip.87.65.97.8] has joined #navit
12:52 #navit: < KaZeR_> hi there
12:54 -!- rcorello [~greg@ip5b408443.dynamic.kabel-deutschland.de] has joined #navit
12:54 #navit: < rcorello> hi all
12:57 #navit: < KaZeR_> how are you doing rcorello?
12:57 #navit: < rcorello> fine. you?
12:58 #navit: < juse2> hellooo
12:58 #navit: < juse2> how are things doing KaZeR_?
12:58 #navit: < KaZeR_> yeah fine too
12:59 #navit: < KaZeR_> hey juse2
12:59 #navit: < rcorello> that's good to hear.
13:00 #navit: < KaZeR_> any progress on your project rcorello ?
13:01 #navit: < rcorello> well, actually yes. i'm currently experimenting with the speedcam warning module.
13:02 #navit: < rcorello> (of course not on public streets, that'd be an offense in my country of residence)
13:02 #navit: < KaZeR_> haha
13:02 #navit: < rcorello> i've submitted a pr on github that allows you to reload csv maps - i believe that could come in handy when speedcam data changes while you're driving
13:04 #navit: < rcorello> other than that, i've done some hardware changes, but that's not related to navit :)
13:05 #navit: < KaZeR_> oh let me check that PR
13:05 #navit: < KaZeR_> btw : any thoughts about having this list online ? do you have internet access in your car ?
13:06 #navit: < juse2> I do ;)
13:06 #navit: < rcorello> i've just ordered the necessary hardware for that.
13:06 #navit: < rcorello> if you want to have that list online, i guess you should check scdb.info
13:07 #navit: < KaZeR_> juse2: please share :)
13:07 #navit: < juse2> huh?
13:09 #navit: < KaZeR_> ha, you answered my internet access question :) i thought you answered the one regarding the thoughts of having that online :)
13:09 #navit: < KaZeR_> rcorello: do you have a membership for that website already ?
13:09 #navit: < juse2> hahaha :D
13:09 #navit: < juse2> yeah, sorry
13:09 #navit: < rcorello> KaZeR_: i don't.
13:11 #navit: < KaZeR_> ok. i'd be curious to see the file format and see if we could integrate that as a native plugin
13:12 #navit: < rcorello> hm. i personally would just fetch their database using cron (or similar means) and convert it using a script. and then tell navit to reload the csv.
13:12 #navit: < KaZeR_> it would work indeed.
13:12 #navit: < KaZeR_> https://github.com/navit-gps/navit/pull/20/files : can you please add a doxygen header to the methods you are adding ? i know a lot of them are missing but we need to get better at this
13:13 #navit: < rcorello> oh ok. sure.
13:13 #navit: < rcorello> i'll do that within the next days.
13:14 #navit: < rcorello> regarding the other PRs i sent.. did you have a chance to look that that stuff already?
13:14 #navit: < KaZeR_> i did have a look last week. something was bugging me, let me re-check that ( i definitely don't want them to be forgotten, thanks for reminding me )
13:15 #navit: < rcorello> :)
13:15 #navit: < KaZeR_> tryagain: are you around ?
13:19 #navit: < rcorello> oh and another thing on my todo-list is handling traffic disturbances. i've already had a look at the code, but first wanted to get that speedcam warner running.
13:20 #navit: < rcorello> you don't happen to know the current state of that feature, do you?
13:21 #navit: < rcorello> as far as i've seen, the code for routing around disturbances is there. but from within the internal gui you're not able to tell navit about new disturbances
13:24 #navit: < tryagain> hey KaZeR
13:27 #navit: < tryagain> rcorello i have a couple of ideas to implement csv map reload without changing api... Are you interested in?
13:29 #navit: < rcorello> tryagain: sure, how would you do it?
13:29 #navit: < tryagain> first way would be to switch active attr to off/on and react on the change by reloading map
13:31 #navit: < tryagain> another one would be to monitor file date/time when the map_rect is created, and reload the map if the change is noticed
13:32 #navit: < rcorello> hm. i thought about such solutions as well. both feel a bit hacky for me.
13:33 #navit: < rcorello> in case of the second solution: what if your csv update process writes to the file a couple of times before it's finished?
13:33 #navit: < rcorello> we would reload the map more often than we have to
13:33 #navit: < tryagain> then it should write into a temporary file and rename it when it finishes ;)
13:34 #navit: < rcorello> well, yeah ;)
13:34 #navit: < rcorello> but let me ask this way: why is it a bad idea to change the api?
13:35 #navit: < rcorello> don't get me wrong - i'm not claiming my solution is "the right one". i just wanna understand your concerns.
13:36 #navit: < tryagain> i'm afraid we can finish exploding api with lots of unneded functions which exist only in selected map plugins
13:36 #navit: < tryagain> sure
13:37 #navit: < rcorello> i see
13:37 #navit: < tryagain> that migth be just my conservativeness though
13:37 #navit: < tryagain> i like stable public interfaces
13:38 #navit: < rcorello> i can totally understand that
13:38 #navit: < tryagain> sorry, have to go afk for a few minutes
13:38 #navit: < rcorello> sure no problem
13:39 #navit: < KaZeR_> actually rcorello the fact that we have to change content in navit/map/garmin_img/garmin_img.c for example is why i wanted tryagain's opinion on this
13:39 #navit: < KaZeR_> so i kind of agree with him :)
13:40 #navit: < rcorello> yeah i mean it's of course up to you
13:42 #navit: < KaZeR_> don't get it wrong, the idea is really good :)
13:43 #navit: < rcorello> no no i'm sure your concerns are valid
13:44 #navit: < tryagain> i'm back again
13:50 #navit: < rcorello> alright, i have to leave
13:51 #navit: < tryagain> good bye rcorello
13:51 #navit: < rcorello> just tell me what you think in the pr :)
13:51 #navit: < tryagain> ok
13:57 -!- juse2 [~juse@b738.ip16.netikka.fi] has quit [Ping timeout: 244 seconds]
14:11 -!- ColdFyre_ [~lenny@c-71-231-174-131.hsd1.wa.comcast.net] has quit [Ping timeout: 250 seconds]
14:14 -!- juse [~juse@b738.ip16.netikka.fi] has joined #navit
14:21 -!- juse [~juse@b738.ip16.netikka.fi] has quit [Ping timeout: 260 seconds]
14:31 -!- jjelen [~jjelen@ip4-95-82-163-69.cust.nbox.cz] has joined #navit
14:44 -!- juse [~juse@b738.ip16.netikka.fi] has joined #navit
14:51 -!- KaZeR_ is now known as KaZeR
14:51 -!- robertp [584aaf83@gateway/web/freenode/ip.88.74.175.131] has joined #navit
14:52 #navit: < robertp> hi
14:52 #navit: < tryagain> hi
14:52 #navit: < KaZeR> hey robertp
14:54 #navit: < robertp> kazer: any news on the audio framework?
14:55 #navit: < KaZeR> yes! not finished, but tryagain unblocked me yesterday
14:55 -!- juse [~juse@b738.ip16.netikka.fi] has quit [Ping timeout: 260 seconds]
14:56 #navit: < KaZeR> the issue i was having is that given the way i implemented it, only one plugin could be active at a time, which is not enough ( eg : output-alsa and player-something )
14:56 #navit: < robertp> yes i saw soma activity and my android navit updated a couple of times
14:56 #navit: < KaZeR> so when loading the spotify player you were loosing the capabilities to manage the audio volume
15:02 #navit: < robertp> do you have an idea for a solution?
15:02 #navit: < KaZeR> yes, we're going to do it as we do for the vehicles
15:03 #navit: < KaZeR> my issue was that registering a plugin was not pushing it into the list, but tryagain share the right snippet to fix that
15:03 -!- juse [~juse@b738.ip16.netikka.fi] has joined #navit
15:07 #navit: < tryagain> hm i was thinking that audio input and output plugins would have a different api and different tags, wouldn't them?
15:08 #navit: < KaZeR> i thought about that too. on one hand, it makes sense. on the other, it means adding more code currently. but if you feel that it's a better way of doing it, i can change the implementation, no problem
15:14 #navit: < tryagain> that depends: if both apis are almost the same, it's good to keep them as one. If there's almost nothing similar in them, then split :)
15:15 #navit: < tryagain> actually, if there's only one api, we could probably do some chainning
15:19 #navit: < tryagain> so, say, speech output would normally pass music through to alsa, but mute during announcements
15:20 #navit: < KaZeR> yeah ultimately this would be really useful
15:26 #navit: < tryagain> but i have no experience working with different audio apis. Maybe it's a more common/intuitive approach to have a single output audio object, which allows source clients of different importance to connect to.
15:27 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 246 seconds]
15:28 #navit: < KaZeR> well, i also foresee some compatibilities issues on top of that. the current spotify code only works with alsa for example
15:28 #navit: < KaZeR> so my take was to setup the premise of a good approach, without trying to make it perfect because : 1) i can fail and 2) maybe we will never have another output plugin than alsa..
15:31 #navit: < tryagain> android audio seems to be another good candidate. If everything is done correctly, your spotify plugin would be crossplatform.
15:41 #navit: < KaZeR> would be cool
15:49 -!- rd_ [~rd@p4FD1C87A.dip0.t-ipconnect.de] has joined #navit
15:58 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
16:15 -!- robertp [584aaf83@gateway/web/freenode/ip.88.74.175.131] has quit [Quit: Page closed]
16:18 -!- jandegr [57416108@gateway/web/freenode/ip.87.65.97.8] has quit [Quit: Page closed]
16:22 -!- jjelen [~jjelen@ip4-95-82-163-69.cust.nbox.cz] has quit [Ping timeout: 240 seconds]
16:38 #navit: < rd_> For the website, the navigation menu on the top is hard to read for me.
16:39 #navit: < rd_> Also it is not w3c compliant: http://validator.w3.org/check?uri=https%3A%2F%2F5a1305f3.ngrok.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=0
16:40 #navit: < rd_> That is probably the reason why it does not scroll very well using the konqueror web browser.
16:41 #navit: < KaZeR> thanks rd_ that's really useful
16:45 #navit: < KaZeR> this is really a work in progress. any comments regarding the content itself? stuffs that we should add or remove ?
17:27 -!- rd_ [~rd@p4FD1C87A.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
17:29 -!- rd_ [~rd@p4FD1C87A.dip0.t-ipconnect.de] has joined #navit
17:33 -!- tryagain [~quassel@178.216.76.67] has quit [Ping timeout: 252 seconds]
17:38 #navit: < KaZeR> i moved the website demo to a repo : http://navit-gps.github.io/website/
17:39 -!- tryagain [~quassel@178.216.76.79] has joined #navit
17:45 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
17:45 -!- rd_ [~rd@p4FD1C87A.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
17:54 #navit: < KaZeR> (repo is https://github.com/navit-gps/website )
18:21 -!- juse [~juse@b738.ip16.netikka.fi] has quit [Ping timeout: 260 seconds]
18:47 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 250 seconds]
19:05 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
19:07 -!- pini [~pini@bou-fi.pustule.org] has quit [Client Quit]
19:28 -!- tryagain [~quassel@178.216.76.79] has quit [Remote host closed the connection]
20:28 -!- ColdFyre [~lenny@c-71-231-174-131.hsd1.wa.comcast.net] has joined #navit
23:28 -!- xenoxaos [xenoxaos@2600:3c02::f03c:91ff:feae:2da1] has quit [Ping timeout: 246 seconds]
23:33 -!- xenoxaos [xenoxaos@2600:3c02::f03c:91ff:feae:2da1] has joined #navit
--- Log closed Fri Aug 28 00:00:40 2015