--- Log opened Thu Oct 30 00:00:32 2014
01:22 -!- KaZeR [~KaZeR@64.201.252.132] has quit [Remote host closed the connection]
06:09 -!- udovdh [~udovdh@pindarots.xs4all.nl] has joined #navit
06:17 -!- udovdh [~udovdh@pindarots.xs4all.nl] has quit [Quit: Leaving]
06:23 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has joined #navit
06:43 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit
06:44 -!- mode/#navit [+o KaZeR] by ChanServ
06:46 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Remote host closed the connection]
07:39 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has joined #navit
10:31 -!- noradtux [~noradtux@2a02:8108:28bf:fc94::1] has quit [Ping timeout: 260 seconds]
10:34 -!- noradtux [~noradtux@2a02:8108:28bf:fc94::1] has joined #navit
10:58 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has quit [Remote host closed the connection]
12:00 -!- ZeroOne01 [~ZeroOne01@81.189.57.6] has joined #navit
12:27 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
13:51 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/wince_arm/svn/navit-svn-5917.failed
13:51 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
15:05 -!- KaZeR [~KaZeR@64.201.252.132] has joined #navit
15:05 -!- mode/#navit [+o KaZeR] by ChanServ
15:22 -!- ZeroOne01 [~ZeroOne01@81.189.57.6] has quit [Read error: Connection reset by peer]
15:58 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
16:31 #navit: <@KaZeR> hi there
16:48 -!- jandegr [51f345ef@gateway/web/freenode/ip.81.243.69.239] has joined #navit
17:02 -!- bafplus [~bafplus@go.allip.nl] has joined #navit
17:05 #navit: < woglinde> joo
17:06 -!- bafplus [~bafplus@go.allip.nl] has quit [Ping timeout: 256 seconds]
17:07 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
17:07 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has quit [Client Quit]
17:07 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
17:07 #navit: < bafplus> Hy woglinde
17:10 #navit: < bafplus> Building win32 works great, just few minor things:
17:11 #navit: < bafplus> The locale folder is placed in the root (navit-build/) instead of the navit folder (navit-build/navit/) so you have to manualy cut-paste the folder in the navit folder to enable the language
17:12 #navit: < bafplus> The country-flags images don't work (in the town search for example). They do work if i build a linux version, if i use the same source and build win32 they don't work. Images are present in the xmp folder
17:13 #navit: < bafplus> There are a lot of empty/not used folders. Is that correct/normal behavior?
17:20 #navit: <@KaZeR> bafplus: nice to hear! would you mind sharing your experience on the wiki ? how relevant is this page according to you? http://wiki.navit-project.org/index.php/Windows_development
17:20 #navit: <@KaZeR> did you do a cross-build from linux or did you build from windows?
17:29 #navit: < bafplus> i did a cross-build from Linux (ubuntu 14)
17:30 #navit: < bafplus> As far as i can see that wiki page is not relevant because its a cross-build from ubuntu.
17:31 #navit: < bafplus> I'm willing to write it but its not going to be more than the steps woglinde gave me.
17:31 #navit: < bafplus> I still have "no clue" what i'm doing and i'm not sure this is the way that will work for everyone.
17:32 #navit: < bafplus> Maybe woglinde is willing to write it including some more info on this.
17:34 #navit: < bafplus> Ans as i explianed a few lines back there are stil a few bugs, i think regarding the mingw config file wogline contributes a few days ago.
17:36 #navit: < bafplus> another question KaZeR, whats the best way to edit images on ubuntu?
17:36 #navit: < bafplus> I'm willing to make the icon for the zipcodesearch but in a usable format ;-)
17:36 #navit: < bafplus> Is GIMP ok for this?
17:38 #navit: <@KaZeR> gimp is fine. it's more about the format than the tool
17:39 #navit: <@KaZeR> bafplus: it would still be interesting to add a section "Cross compiling from Linux" with the steps you followed. I can then review it, maybe expand the doc, and add automated builds to our CI infrastructure
17:40 #navit: <@KaZeR> and it would be a step forward regarding http://trac.navit-project.org/ticket/1253
17:41 #navit: <@KaZeR> bafplus: do you log your trips? iirc, you are using navit quite a lot lately, and having logs with a track and associated route could be interesting, if you do not feel that it would violate your privacy
17:42 #navit: < bafplus> its no problem for me.
17:43 #navit: < bafplus> Just help me set up the logging part and i can supply you with the logs on request
17:43 #navit: < bafplus> can i add the crosscompile to this wiki?: http://wiki.navit-project.org/index.php/Linux_development
17:46 #navit: < bafplus> brb, rebooting to linux....
17:46 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has quit [Quit: HydraIRC -> http://www.hydrairc.com <- IRC with a difference]
17:49 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
17:51 #navit: <@KaZeR> i would rather have the cross compilation in the windows page, as it is the target platform, but a link in the linux page is indeed a good idea
17:51 #navit: < bafplus> KaZeR , how are things going with the planetextracter? I noticed last "build" was 30-9-2014, wassen't it supposed to update on a regular basis like once a week?
17:51 #navit: <@KaZeR> it should update once a week indeed
17:52 #navit: <@KaZeR> i am having issue updating the root map using diffs from OSM with my own server
17:52 #navit: <@KaZeR> i can generate maps, but the update fails. so it means redownloading the whole map each time, which is really annoying
17:53 #navit: <@KaZeR> to log your tracks, you can add a section like this to your vehicle :
17:54 #navit: <@KaZeR> we now have the possibility to export routes as gpx (committed) or geojson ( not yet in trunk) so i will probably add that to the logging soon
17:54 #navit: < bafplus> this wil produce files for each route? per day? just one file?
17:54 #navit: <@KaZeR> (details about route logging are in this ticket if you are interested : http://trac.navit-project.org/ticket/1268 )
17:55 #navit: < bafplus> i have about 15-20 routes/trips a day...
17:55 #navit: <@KaZeR> this will create a file to log your track ( != route ). you can configure the max file size too.
17:56 #navit: < bafplus> i have a ned hd with about 100gb free space :-)
17:56 #navit: <@KaZeR> a short trip will give one track log. a longer trip might get splitted into several track logs (but it's easy to merge them back )
17:57 #navit: <@KaZeR> i am logging all the tracks for debugging, and several months of datas are currently 275MB
17:57 #navit: < bafplus> First i want to clean my navit up a bit. Due to the zipcodeserach ive been stuck with a build a month or 2-3 back.
17:57 #navit: <@KaZeR> sure. let's build that wiki page, then i can setup build automation for your platform :)
17:58 #navit: < bafplus> Now i can build myself i want tu pick the latest, reaply my changes and keep it updated with the comming changes (without erasing my own changes), whats the best aproach for this? fork?
18:01 #navit: <@KaZeR> a fork would work indeed. or maybe i can push your changes into the trunk if you give me some details
18:04 #navit: < bafplus> Not sure what you mean with trunk...these are personal changes...not ment for redistributing to the source ;-)
18:05 #navit: <@KaZeR> oh ok. then a patch maybe. Is it code or config ?
18:05 #navit: <@KaZeR> (the trunk is the default, standard source for navit)
18:05 #navit: < bafplus> 99% are costumizations to the navit.xml
18:06 #navit: < bafplus> and then the zipcode changes but i heard its going to be commited if i supply i icon for it ;-)
18:08 #navit: < bafplus> my osd for example doesent benifit enyone else....
18:08 -!- noradtux [~noradtux@2a02:8108:28bf:fc94::1] has quit [Quit: Bye]
18:08 -!- noradtux [~noradtux@2a02:8108:28bf:fc94::1] has joined #navit
18:09 #navit: <@KaZeR> are you familiar with git ?
18:09 #navit: < bafplus> so a small roadmap: adding wiki for the cross-compiling. cleaning and updating by navit, make it updatebla without losing my own changes. Enable logging
18:10 #navit: < bafplus> seen it a few times, no experience with git myself
18:10 #navit: <@KaZeR> ok. one easy way to keep your changes could be to put your config and osd in a git repo. example : https://github.com/pgrandin/navit-nuc-layout
18:10 #navit: <@KaZeR> i can help you with that
18:11 #navit: < bafplus> and after every update/rebuild overwrite the config with the git?
18:12 #navit: <@KaZeR> no need to. the config file would be in the navit sharedir folder
18:12 #navit: < bafplus> my biggest conserb is the navit.xml. I want to break it up in parts for a better overview, but how to handle codeupdates in the navit.xml?
18:12 #navit: <@KaZeR> under linux (i have to check for windows) the first place navit will look for the config is your homedir, so you can keep your own file there without interference
18:13 #navit: <@KaZeR> navit.xml does not change that often. you should probably not worry too much :)
18:13 #navit: <@KaZeR> also you can use some xi:include magic to rebuild a file from different sourcefiles
18:14 #navit: < bafplus> don't throw tech term to a noob ;-)
18:15 #navit: < bafplus> k.i.s.s. ;-)
18:16 #navit: <@KaZeR> haha :) in short you can use a navit.xml skeleton, which will use the default config excepted for the part that you choose. you probably want to tweak the vehicle and gui settings, plus osd.
18:16 #navit: <@KaZeR> actually here's an example :
18:16 #navit: <@KaZeR> by adding only two lines to your navit.xml. you can use your own OSD setting and your own map layout
18:16 #navit: <@KaZeR>
18:16 #navit: <@KaZeR>
18:17 #navit: <@KaZeR> and you can keep the OSD in a dedicated file, and the map layout in another dedicated file
18:17 #navit: < bafplus> i understand that part...so the lines you gave me would override the osd and layout within the xml itself?
18:18 #navit: < bafplus> There is a trac-ticket about doing that splitting of the xml with the shipped xml, i second that idea ;-)
18:19 #navit: <@KaZeR> yeah it has been discussed a few times..
18:20 #navit: <@KaZeR> the idea of having only one file is that it makes it easier to parse in an automated way to generate tailored configs
18:20 #navit: <@KaZeR> i know it's a pain for the users. but eventually the solution would be to be able to modify the config from the UI, instead of the xml. then everyone would be happy :)
18:21 #navit: < bafplus> or make it so that navit.xml is used as default EXCEPT when there are override-snippets in , say, the /config/ folder
18:22 #navit: < bafplus> So gps example: navit.xml is used by default, except when there is a vehicle.xml present in the config folder
18:24 #navit: < bafplus> that way it would work both ways and if the user want to use splitted files he only have to put thoses files in the config folder and those files automaticly override the native navit.xml
18:24 #navit: < bafplus> get it???
18:25 #navit: < bafplus> hoewever...for my own overview, lets take this step by step beginning with the wiki for cross-compiling
18:33 #navit: < bafplus> for the wiki...i will only give a "fast" walkthru. Somebody else has to check it and add domment end more details about the functions. I dont even know if my walktryu will work for "everyone"
18:38 #navit: <@KaZeR> your idea would work but would be quite a pain to put in place. that's why we rather use xi:include :)
18:39 #navit: <@KaZeR> don't worry for the wiki. I will review it, expand it, and I will start pushing scripts into the trunk as discussed in the ticket
18:39 #navit: <@KaZeR> and I can setup a build automation too
18:46 #navit: < bafplus> whats the correct wikitag to post commandline commands? ?
18:49 #navit: <@KaZeR>
i think
18:49 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has quit [Ping timeout: 255 seconds]
18:50 #navit: < bafplus> no, found it, just prepend with a space on each line...
18:53 #navit: <@KaZeR> cool.
18:53 #navit: <@KaZeR> have to go afk for lunch. back in a few, i will review the doc if you want :)
19:46 #navit: < bafplus> KaZeR , woglinde (and maybe jandegr) , wiki page for compiling win32 from ubuntu is done: http://wiki.navit-project.org/index.php/Windows_development#Compiling_win32_exe_using_Linux_Ubuntu_14.04.1
19:46 #navit: < bafplus> Please review/change/add/addapt :-)
20:11 #navit: < bafplus> jandegr i have an icon svg for the zipcodesearch
20:14 #navit: < bafplus> https://www.wetransfer.com/downloads/1cae5751e563a6855fd3b45caa098afe20141030201317/75e6918b5dcb50399aa1b741cf4e69e620141030201317/4597e9
20:17 #navit: < jandegr> bafplus it's tryagain who did the poi filter for zipcode, but it looks like you can simply include the patch in your build
20:19 #navit: < bafplus> Ok, thanks.
20:24 #navit: < bafplus> Maybe KaZeR can do something?
20:51 #navit: < bafplus> Dams...got a win32 compiler error...wheres woglinde when you nee dhim ;-)
21:05 #navit: < jandegr> and what does the error say bafplus ?
21:07 #navit: < bafplus> http://pastebin.com/X5HU9M7G
21:10 #navit: < bafplus> I have a second source folder and that one works...but doing the same steps but instead use navit-source gives this error...
21:22 #navit: < bafplus> hmmm...if i just copy the navit from navit-source to navit-source-custom is works, but doing same steps with another source folder fails
21:22 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has quit [Quit: Leaving]
21:24 -!- woglinde [~henning@e179136186.adsl.alicedsl.de] has joined #navit
21:24 -!- woglinde [~henning@e179136186.adsl.alicedsl.de] has quit [Client Quit]
21:24 -!- woglinde [~henning@e179136186.adsl.alicedsl.de] has joined #navit
21:25 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
21:30 -!- jandegr [51f345ef@gateway/web/freenode/ip.81.243.69.239] has quit [Quit: Page closed]
21:34 #navit: < bafplus> KaZeR logs are enabled so let me know when yoy want a batch
21:35 #navit: < bafplus> I'm of, woglinde, hope you can take a look at the cross-compiling wiki and look for any incorrect/missing commands
21:35 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has quit [Quit: HydraIRC -> http://www.hydrairc.com <- It'll be on slashdot one day...]
21:35 #navit: <@KaZeR> bafplus: just got back. i will review the icon and the doc
21:36 #navit: <@KaZeR> thanks for sharing
21:36 #navit: < woglinde> bafplus hm
22:40 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
22:44 #navit: < bafplus> Hy woglinde
22:44 #navit: < bafplus> read the logs?
22:44 #navit: < woglinde> yes
22:45 #navit: < woglinde> now
22:45 #navit: < bafplus> building works great...but using another folder as source gives troubles, can't figure out why...
22:50 #navit: < bafplus> brb, booting to linux
22:50 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has quit [Quit: HydraIRC -> http://www.hydrairc.com <- *I* use it, so it must be good!]
22:52 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
22:59 #navit: < woglinde> bafplus move the install of libsaxonb-java up
22:59 #navit: < bafplus> up to what?
23:00 #navit: < woglinde> first apt-get
23:00 #navit: < bafplus> no matter from what directory?
23:01 #navit: < woglinde> bafplus normaly you can make the build-dir someware
23:02 #navit: < woglinde> and provide the full path to cmake -DCMAKE_TOOLCHAIN_FILE=/fullpathtonavitsource/Toolchain/mingw32.cmake /fullpathtonavitsource/
23:03 #navit: < bafplus> i ment tje libsaxonb-java, does it matter in what directory i'm in when running the apt-get install?
23:03 #navit: < woglinde> the apt-get command can be ran from everywhere
23:03 #navit: < woglinde> sure
23:03 #navit: < woglinde> its only a package installer
23:03 #navit: < woglinde> it does not need a special directory
23:04 #navit: < woglinde> dpkg -L packagename and you will get the list and locations of the installed files of the package
23:05 #navit: < bafplus> usr/shar/.
23:05 #navit: < bafplus> usr/share/...
23:06 #navit: < woglinde> yes I know ,)
23:06 #navit: < woglinde> I only wanted to give you more inside of a debian/ubuntu system
23:07 #navit: < woglinde> insight even
23:07 #navit: < bafplus> :-)
23:07 #navit: < woglinde> okay time to go to sleep now
23:07 #navit: < woglinde> and thanks again for editing the wiki
23:07 #navit: < bafplus> no problem, thank you for setting this all up
23:09 #navit: < bafplus> btw..any quick thuoghts about the country images?
23:10 #navit: < bafplus> linux build=ok win32 build=no images in menu
23:12 -!- woglinde [~henning@e179136186.adsl.alicedsl.de] has quit [Ping timeout: 258 seconds]
23:24 #navit: < bafplus> KaZeR, u there?
23:26 #navit: <@KaZeR> bafplus: yes
23:26 #navit: <@KaZeR> bafplus: i did some minor adjustments to the doc
23:26 #navit: < bafplus> I noticed, thanks
23:26 #navit: <@KaZeR> i was able to build a binary following the doc in a local docker instance. i am now trying to figure out an issue with the automated build
23:27 #navit: < bafplus> I did a clean run thru it it all seems to work correctly
23:27 #navit: <@KaZeR> eventually we want to pack that in something like installshield i gues
23:27 #navit: <@KaZeR> thanks for taking the time to write that doc :)
23:27 #navit: < bafplus> np
23:27 #navit: < bafplus> question about the speedwarner osd item
23:28 #navit: < bafplus> I have it set up using images so it looks like actual speedlimit roadsigns
23:28 #navit: <@KaZeR> oh i remember that. did you figure out your color issue? or did you edit some code directly ?
23:29 #navit: < bafplus> when the user is getting over the speedlimit the sign and number get red, when within speedlimit the number is green
23:29 #navit: < bafplus> I think i found the code, have to roadtest it tomorow to change the idle state to use the color black instead of green
23:30 #navit: < bafplus> that way it looks exactly like the actual roadsigns
23:30 #navit: < bafplus> What do you think...should green be the standard idle color or shall i commit it to the svn toe be black?
23:31 #navit: < bafplus> i think its a matter of taste but i think black would be better
23:31 #navit: < bafplus> if we can set it to black in the svn i can commit adding my roadsign osd layout
23:36 #navit: < bafplus> for a better idea: When black is used, the number within the sign is also black, when exceeding the limit the sign and number turn red , image when idle: http://www.solarwebsite.nl/wp-content/uploads/2011/03/Snelweg_130_kmu.png
23:37 #navit: < bafplus> With the current color set to green the "130" is displayed in green
23:38 #navit: <@KaZeR> i think that for Europe it would make sense to have black letters. People would understand it as a sign
23:39 #navit: <@KaZeR> in the US the speed limit is also black text, but within a black box : http://images.thecarconnection.com/med/speed-limit-55_100172129_m.jpg
23:40 #navit: < bafplus> So both are black... changing the images for the signs is no problem, i can make a europe and US version etc.
23:41 #navit: < bafplus> In this context using images the green text isnt making sence
23:42 #navit: <@KaZeR> yep, but i don't have a better idea :)
23:42 #navit: <@KaZeR> red text in both case if you're overspeeding maybe ?
23:42 #navit: < bafplus> Sure, i'm only talking about when you are within the speedlimits
23:43 #navit: < bafplus> Should i post this on the TRAC or just commit the change to use black as default?
23:45 #navit: < bafplus> thinking about the different signs...is it possibla to use the mapdata to determin the used signs? Zo when driving on a europa map use the round one, when driving on us map use youre sign etc?
23:46 #navit: < bafplus> or just put those 2 (and on request others) in the OSD-wiki so the user can pick the one the like?
23:46 #navit: < bafplus> but use black letters in all of them ;-)
23:46 #navit: <@KaZeR> mmm
23:47 #navit: <@KaZeR> we can use the env_var LC_LANG for that i guess
23:47 #navit: <@KaZeR> that's how we "guess" the default country
23:50 #navit: < bafplus> No clue how to code that, just trowing in ideas...
23:51 #navit: <@KaZeR> no worries. in short, it should work and should not be that hard :)
23:52 #navit: < bafplus> Let me first try my colorchange tomorow to see if my change works.
23:53 #navit: < bafplus> Then i will commit the change (if thats ok with everyone) and post the complete sign osd in the wiki and maybe even trow in a us version.
23:54 #navit: <@KaZeR> what do you call commit ? :o)
23:54 #navit: < bafplus> then somebody can throw itself on coding it in the source...
23:55 #navit: < bafplus> Changing the "green" to "black" in the SF SVN...
23:56 #navit: <@KaZeR> you have access to the svn repo ?
23:56 #navit: < bafplus> i guess not, but i can ask someone who has ;-)
23:59 #navit: <@KaZeR> oh ok :)
--- Log closed Fri Oct 31 00:00:32 2014