--- Log opened Thu May 18 00:00:17 2017
01:28 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
01:35 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
01:40 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 260 seconds]
02:56 -!- ilovekiruna [~ilovekiru@b2b-130-180-113-170.unitymedia.biz] has quit [Ping timeout: 240 seconds]
03:17 -!- jjelen [jjelen@nat/redhat/x-sjqnsexrmqybllrv] has joined #navit
06:04 -!- linesoff [5b243213@gateway/web/freenode/ip.91.36.50.19] has joined #navit
06:08 -!- linesoff [5b243213@gateway/web/freenode/ip.91.36.50.19] has quit [Client Quit]
06:18 -!- kazer [~kazer@2601:643:8680:2630:eea8:6bff:fef8:449] has quit [Ping timeout: 255 seconds]
06:29 -!- kazer [~kazer@2601:643:8680:2630:eea8:6bff:fef8:449] has joined #navit
09:43 -!- noradtux [~noradtux@2a02:2028:849:5601:c21:f1d1:5b2:68e7] has quit [Ping timeout: 240 seconds]
09:48 -!- noradtux [~noradtux@2a02:2028:574:7501::1] has joined #navit
10:48 -!- ilovekiruna [~ilovekiru@161-237.eduroam.rwth-aachen.de] has joined #navit
10:54 -!- ilovekiruna [~ilovekiru@161-237.eduroam.rwth-aachen.de] has quit [Ping timeout: 240 seconds]
11:02 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 246 seconds]
12:30 -!- ColdFyre [~lenny@c-73-221-248-99.hsd1.wa.comcast.net] has quit [Ping timeout: 268 seconds]
12:31 -!- ColdFyre [~lenny@c-73-221-248-99.hsd1.wa.comcast.net] has joined #navit
12:40 #navit: < kazer> hi there
12:42 -!- ilovekiruna [~ilovekiru@b2b-130-180-113-170.unitymedia.biz] has joined #navit
12:44 #navit: < kazer> hi ilovekiruna
12:52 -!- ilovekiruna [~ilovekiru@b2b-130-180-113-170.unitymedia.biz] has quit [Ping timeout: 240 seconds]
12:53 -!- ilovekiruna [~ilovekiru@b2b-130-180-113-170.unitymedia.biz] has joined #navit
12:53 #navit: < ilovekiruna> kazer: hi
12:54 -!- jandegr [5bb4bc1d@gateway/web/freenode/ip.91.180.188.29] has joined #navit
12:54 #navit: < ilovekiruna> from my trip the last two days, I got some more ideas
12:55 #navit: < kazer> great! was your code working as expected ?
12:55 #navit: < ilovekiruna> honestly I am not sure.
12:55 #navit: < kazer> haha
12:55 #navit: < kazer> did you record your gps track ?
12:55 #navit: < ilovekiruna> I realized that you point of using a botton is a lot better
12:55 #navit: < ilovekiruna> right now I dont c visually which state the speed warner is in
12:56 #navit: < kazer> that's easy to add to the current code
12:56 -!- jjelen [jjelen@nat/redhat/x-sjqnsexrmqybllrv] has quit [Ping timeout: 240 seconds]
12:56 #navit: < ilovekiruna> I also wonder, how can I place osd elements that they are in a good position both in landscape and portrait mode
12:56 #navit: < kazer> we could use a specific color for the strict mode, or maybe a background icon
12:56 #navit: < kazer> ha, that part is tricky
12:57 #navit: < kazer> i don't use navit on a phone a lot, so i personally don't have this orientation issue. But i think that the best way to address it is to build two different osd sets, and swap between them
12:58 #navit: < ilovekiruna> i also noticed why it is good when one displays streets, that one is using street_name and street_name_systematic for displaying
12:58 #navit: < ilovekiruna> otherwise too often empty ;-)
12:59 #navit: < ilovekiruna> i also noticed one thing with my phone,
12:59 #navit: < ilovekiruna> when using navit, it seems like the soft buttons blink time to time
12:59 #navit: < ilovekiruna> is there anything known?
13:01 #navit: < kazer> ah that's a good question. jandegr have you noticed that?
13:01 #navit: < kazer> ilovekiruna: were you able to build for android using your own circleci fork by the way?
13:01 #navit: < ilovekiruna> yes,
13:01 #navit: < kazer> sweet
13:01 #navit: < ilovekiruna> kazer: at first I built the wrong branch :(
13:02 #navit: < ilovekiruna> master
13:02 #navit: < ilovekiruna> realized later
13:02 #navit: < kazer> ah :)
13:02 #navit: < ilovekiruna> also didnt manage to use the bookmark and give coordinate destination properly
13:02 #navit: < ilovekiruna> maybe a pebak problem ;-)
13:02 #navit: < kazer> yeah, we do not commit against master, so that it should never break. we also refrain from commiting against trunk, and leverage feature branches instead
13:03 #navit: < kazer> yeah the bookmark thing interactions can be a bit confusing.. altough it does work well, i use it myself a lot
13:04 #navit: < ilovekiruna> in actions, If I go to the globe, icon I think I am missing the option to input own coordinates
13:04 #navit: < ilovekiruna> I just hv a preset  coordinate, which I can set as destination, position, add as bookmark, POIs
13:05 #navit: < ilovekiruna> ok, the bookmark thingy, I understand now :)
13:05 #navit: < ilovekiruna> thought it is in the bookmark action icon, not the coordinate one ;-)
13:06 #navit: < jandegr> hi
13:09 #navit: < kazer> ilovekiruna: yeah the "input your coordinates menu" is not in internal i think. It should not be too hard to fix if you are interested
13:09 #navit: < ilovekiruna> kazer: I thought in the app directly from the play store, it was included
13:09 #navit: < ilovekiruna> but ofc hv my custom build now installed
13:10 #navit: < ilovekiruna> would be nice, if I under your guidance can fix things one by one
13:10 #navit: < ilovekiruna> am just now trying to remember if any ideas are still missing, I wanted to tell u
13:11 #navit: < ilovekiruna> hopefully later, I could fix such things more on my own
13:11 #navit: < ilovekiruna> btw: saving GPS track is possible with navit?
13:15 #navit: < kazer> ilovekiruna: happy to help you work on any feature you're interested in, just ask
13:16 #navit: < kazer> to log your gps track : http://wiki.navit-project.org/index.php/Configuration/Vehicle_Options#Logging_tracks
13:17 #navit: < kazer> in the future i would personnally like less config editing and more settings in the UI. This is  a bit challenging with gui_internal (although not impossible) but this will be one of the focus of the new UI : https://github.com/navit-gps/navit/pull/254
13:18 #navit: < ilovekiruna> kazer: u r right, more UI settings would be awesome
13:18 #navit: < kazer> :)
13:19 #navit: < kazer> we started ideating on this some time ago. https://github.com/navit-gps/navit-gui-qt5/blob/master/ideas_from_couka.txt is just a starting point, but contributions are welcome
13:20 #navit: < kazer> qml allows us to seperate backend and frontend. One could work on the UI without needing to know much about navit internals. It should make it easier for people to contribute UI improvements
13:20 #navit: < kazer> if you are interested in helping, have a look at qtcreator
13:21 #navit: < ilovekiruna> i hv installed qtcreator for sailfish
13:21 #navit: < ilovekiruna> when looking on the ideas list
13:21 #navit: < ilovekiruna> how do u determine the fuel consumption?
13:21 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
13:22 #navit: < ilovekiruna> One thing I would be really curious in implementing.
13:22 #navit: < ilovekiruna> Could one improve the location estimation algorithm
13:22 #navit: < ilovekiruna> it is strange that time to time when going on Autobahn, suddenly navit locks on a road beside the Autobahn
13:23 #navit: < ilovekiruna> could one implment there sth to prevent sudden jumps?
13:23 #navit: < kazer> fuel consumption?
13:23 #navit: < ilovekiruna> 1.6.5.1
13:23 #navit: < ilovekiruna> in the list
13:24 #navit: < jandegr> the problem is in tracking, it ignores the route
13:24 #navit: < ilovekiruna> :-o
13:24 #navit: < kazer> ah! this would depend a lot. In my car for example, i can read values from the canbus, so i can actually get the real averaged value. Otherwise it could be based upon values entered by the user (amount of fuel in)
13:25 #navit: < ilovekiruna> kazer: ah, ok. Then it makes sense
13:25 #navit: < kazer> regarding the location estimation it's tricky, because if you do exit, you want the position to be correct. So we can't really favor the autobahn vs a smaller road. try driving ton the left hand lane :)
13:25 #navit: < jandegr> [19:24] <jandegr> the problem is in tracking, it ignores the route
13:26 #navit: < ilovekiruna> I mean especially when there is not necessarily an exit
13:26 #navit: < ilovekiruna> also in an exit u wont drive 140 km/h ;-)
13:26 #navit: < kazer> jandegr: true, but if i do exit the road (by mistake or intentionally) i dont want navit to believe that i am still on the planned route if i am not
13:26 #navit: < kazer> i have a really good example if you are interested :)
13:27 #navit: < ilovekiruna> I know the issue might not be really trivial
13:28 #navit: < kazer> the problem is that we could implement a workaround, but in many cases it would make things worse
13:30 #navit: < ilovekiruna> would the qt gui then also be used on Android?
13:31 #navit: < kazer> that's the plan yes
13:31 #navit: < ilovekiruna> neat
13:32 #navit: < ilovekiruna> i like qt for being one of the small number of really multi-platform frameworks
13:32 #navit: < kazer> some help building it and testing it for android would be much appreciated :)
13:32 #navit: < kazer> yeah exactly
13:32 #navit: < ilovekiruna> kazer: testing, i can for sure try to help with
13:33 #navit: < kazer> so jandegr might be our only hope regarding the build? :)
13:33 #navit: < ilovekiruna> btw: is there any collaboration with ModRana?
13:35 #navit: < jandegr> kazer I do not have the habbit to drive from a bridge onto the road below, that must be a CA specialty
13:35 #navit: < jandegr> when in doubt, I want it to think I'm still on the route
13:44 #navit: < kazer> jandegr: monster trucks powa!
13:45 #navit: < kazer> ilovekiruna: not that i know of, never heard of that. I'd love to know more though
13:45 #navit: < ilovekiruna> ModRana is a kind of navigation project which is a bit more focused around sailfish
13:45 #navit: < ilovekiruna> let me search for the link
13:45 #navit: < ilovekiruna> http://modrana.org/trac
13:46 #navit: < kazer> interesting
13:46 #navit: < kazer> found their github too
13:46 #navit: < ilovekiruna> I think they also must hv a qt ui
13:47 #navit: < ilovekiruna> right now not yet fully functional under SFOS afaik
13:48 #navit: < jandegr> modrana navigation is infantile, one sees that right away
13:48 #navit: < ilovekiruna> I know, it is not up to the level of navit
13:49 #navit: < ilovekiruna> jandegr: Afaik, I think Modrana is just developed by a single person
13:53 #navit: < jandegr> the market is swamped with mediocre navi solutions, better join an existing one instead of making more mediocre
14:00 #navit: < kazer> the best one on the market could use some help for sure :D
14:01 #navit: < jandegr> zanavi ?
14:01 #navit: < kazer> ...
14:02 -!- mode/#navit [+o kazer] by ChanServ
14:02 #navit: <@kazer> looking for troubles, jandegr ? :)
14:05 #navit: < jandegr> the fact is I like to work on stuff that needs work both in zanavi and navit, then I can sell twice :)
14:05 #navit: < jandegr> and there is already $1 available :)
14:08 #navit: <@kazer> ahah true
14:11 #navit: < ilovekiruna> kazer: to come back to input coordinates in the internal gui
14:11 #navit: < ilovekiruna> what would I hv to do
14:11 #navit: < ilovekiruna> just add it in the navit.xml file?
14:19 #navit: <@kazer> https://github.com/navit-gps/navit/blob/trunk/navit/gui/internal/gui_internal_command.c#L1333 is probably what we want
14:19 #navit: <@kazer> and the implementation is here : https://github.com/navit-gps/navit/blob/trunk/navit/gui/internal/gui_internal.c#L2521
14:20 #navit: <@kazer> so yeah i think that just adding an entry to the xml should work
14:29 #navit: < ilovekiruna> ok, will test it
14:35 #navit: <@kazer> thanks
14:56 #navit: < ilovekiruna> am testing right the navit.xml via navitconfigurator
14:56 #navit: < ilovekiruna> right now seems like I made a mistake, cant start navit via the configurator
14:56 #navit: < ilovekiruna> how can I debug that?
15:04 #navit: <@kazer> navitconfigurator? yeah i'm not sure that this works :)
15:04 #navit: < ilovekiruna> before copying it via that was rather simple
15:04 #navit: <@kazer> oh wow, 2017-02-25 last update
15:04 #navit: < ilovekiruna> I guess I somehow corrupted my navit.xml file
15:05 #navit: <@kazer> i need to contact that guy to integrate it better
15:05 #navit: <@kazer> are you trying to launch navit on android or linux?
15:06 #navit: <@kazer> if linux, start navit from the command line and it should tell you where the error is at
15:07 #navit: < ilovekiruna> I think I found the issue
15:07 #navit: < ilovekiruna> Android
15:07 #navit: < ilovekiruna> but I think I found the issue
15:07 #navit: < ilovekiruna> good old file comparison
15:14 #navit: <@kazer> cool
15:15 #navit: < ilovekiruna> btw: If u r also running gentoo, in my private overlay, I hv a ebuild for the configurator
15:18 #navit: < ilovekiruna> i guess for testing it is better to do on linux now, compared to android
15:19 #navit: <@kazer> yeah, linux testing would probably make your life easier. although it should just be a matter of copying the xml file...
15:20 #navit: < ilovekiruna> I thought i found the mistake
15:20 #navit: < ilovekiruna> but was wrong
15:20 #navit: < ilovekiruna> will next, after upgrades install navit here
15:21 -!- jandegr [5bb4bc1d@gateway/web/freenode/ip.91.180.188.29] has quit [Quit: Page closed]
15:31 #navit: < ilovekiruna> kazer: where are you located?
15:50 #navit: <@kazer> California
16:07 #navit: < ilovekiruna> wow, nicely warm
16:09 #navit: < jkoan> We head a big spam "attack" from the wiki account Sandysingh. I deleted the spam pages and blocked the account
16:24 #navit: <@kazer> thanks jkoan. It's really hard to filter applications, our manual account review process does not really help, all it does it slow down the new users
16:24 #navit: <@kazer> ilovekiruna: yep indeed :)
16:26 #navit: < jkoan> No problem, I have only seen it because I have the wiki as rss feed ;)
16:26 #navit: <@kazer> i am going to do that right now.
16:30 #navit: <@kazer> done! thanks for the hint
16:32 #navit: < jkoan> No problem
16:32 #navit: < jkoan> Did someone missed me in the last month?
16:36 #navit: <@kazer> we definitely did
16:37 #navit: <@kazer> did you miss us? :)
16:37 #navit: <@kazer> have you seen the progress on the new UI? https://github.com/navit-gps/navit/pulls/254
16:46 #navit: < jkoan> No I haven't seen anything because I'm very busy, but I learned c and c++ ;)
16:47 #navit: < jkoan> I must go of for now, sorry. Hopefully we will hear in some day's or weeks
16:49 #navit: < jkoan> But the design gifs are really cool
16:52 #navit: <@kazer> sweet. Come back anytime!
18:40 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
20:00 -!- Horwitz [~mich1@p200300800E463B00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
20:01 #navit: < ilovekiruna> kazer: Is the wiki page for downloading navit still uptodate?
20:01 #navit: < ilovekiruna> at least the gentoo section, I would update tomorrow, because it seems outdated
20:02 #navit: < ilovekiruna> seems like more are outdated, would update it tomorrow, if  i can
20:10 #navit: < ilovekiruna> except fedora in the list, I think all other linux distributions hv a navit package in some repo
20:10 #navit: < ilovekiruna> check here: http://wiki.navit-project.org/index.php/Download
20:10 #navit: < ilovekiruna> eeePC and Arch I didnt check
20:13 -!- Horwitz [~mich1@p200300800E0A1500022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
20:13 -!- mode/#navit [+o Horwitz] by ChanServ
20:16 #navit: <@kazer> yeah the wiki is probably outdated
20:16 #navit: <@kazer> tracking packaging of navit in the various distro is actually really challenging, because it's mostly third party
20:16 #navit: <@kazer> i could make the CI auto-update the page with the links for the packages that we build ourself though
21:03 -!- noradtux [~noradtux@2a02:2028:574:7501::1] has quit [Ping timeout: 255 seconds]
21:07 -!- noradtux [~noradtux@port-19208.pppoe.wtnet.de] has joined #navit
--- Log closed Fri May 19 00:00:18 2017