--- Log opened Mon Sep 18 00:00:42 2017
00:38 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n
00:38 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed
00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
03:00 -!- noradtux [~noradtux@port-18916.pppoe.wtnet.de] has quit [Ping timeout: 264 seconds]
03:00 -!- noradtux_ [~noradtux@2a02:2028:55d:1101:41a1:9790:7816:bc11] has joined #navit
03:00 -!- noradtux_ is now known as noradtux
05:54 #navit: < jkoan> Kazer : could you say something about browserplugin.c? Was it intended to run navit from the browser?
06:19 #navit: <@KaZeR> it was and it used to work :)
06:19 #navit: <@KaZeR> you were able to use navit from your browser. But it depends on a non released library too iirc
06:23 -!- naggety [028d0773@gateway/web/freenode/ip.2.141.7.115] has joined #navit
06:35 #navit: < jkoan> But if I see it right it uses the NPAPI which is dying today
06:44 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
07:09 #navit: < jkoan> Hi xenos1984
12:11 #navit: < naggety> Hi. I finally have built maptools and generated the .bin files from OSM. With the experimental feature the coast lines are really improved.
12:12 #navit: < naggety> At least in the zones where you have an installed map, and excluding the smallest zoom levels.
12:15 #navit: < naggety> Apparently there is some difference in RAM usage. With variable 'max' at 9, I got over 30MB RAM usage. With max=6 I got around 22MB RAM usage, but with over 30MB peaks. With max=14 I got less than 20MB, but with over 30MB peaks.
12:16 #navit: < naggety> I know you tested this in the past....
12:37 #navit: < naggety> With max=1 it is also arond 30MB. I only have installed the map of Spain. I supose that with a bigger map RAM usage can be higher.
14:05 #navit: < jkoan> naggety: but the grafics looks better?
14:24 #navit: < naggety> Yes
14:25 #navit: < naggety> There are some badly rendered zones, but I think it is related to other bug (land areas painted as sea, and sea areas painted as land)
14:26 #navit: < naggety> but concerning coast lines, experimental feature works for the zoom level it is intended to work
14:30 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
14:34 -!- naggety [028d0773@gateway/web/freenode/ip.2.141.7.115] has quit [Quit: Page closed]
14:51 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has quit [Ping timeout: 252 seconds]
15:12 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
15:36 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has joined #navit
16:50 #navit: <@KaZeR> really good report from naggety. With so low memory usage it might be worth changing the default coastline setting
17:05 #navit: < jkoan> in my opinion the difference between 20 and 30MB is not that much and also its for better coastlines
17:27 #navit: < ilovekiruna> jkoan: how much RAM is there available on the tomtom?
17:28 #navit: < jkoan> 32 but i think we handle it like "if its no ram available it gehts slower" but right now i cant verify
17:29 #navit: < ilovekiruna> was curious, because 20 or 30 MB, must always been seen in relation to available RAM
17:30 #navit: < jkoan> yes, thats probably a good point also
17:45 #navit: < ilovekiruna> for mobile phones it will be probably completely irrelevant, so in general i agree, it should be actived
17:45 #navit: < ilovekiruna> but maybe not for the low-memory devices
18:12 -!- jandegr [5bb34cfc@gateway/web/freenode/ip.91.179.76.252] has joined #navit
18:14 #navit: < jkoan> Ilovekiruna it's not possible to have this enabled per device because it dependent on the map, and the maps are the same for every device. Of course it's possible to generate two maps, but this is even not very handy
18:14 #navit: < jandegr> jkoan AFAIK you can fix memory usage per device with xml
18:15 #navit: < jandegr> however extra time needed to read binfile will stay the same
18:15 #navit: < jkoan> You mean with the route depth?
18:16 #navit: < jandegr> refers to coastlines
18:16 #navit: < jandegr> unless I did not follow the conversation correctly
18:17 #navit: <@KaZeR> jkoan: ram is a factor, but it'll also increase cpu usage (for filtering and rendering)
18:17 #navit: <@KaZeR> hey jandegr
18:18 #navit: < jkoan> jandegr: yes its correct, but how do you want to reduce ram usage in the XML?
18:19 #navit: < jandegr> show them when zoomed in more closely only, dirty fix for flimsy hardware
18:20 #navit: < jandegr> https://trac.navit-project.org/ticket/854
18:28 #navit: < jandegr> what will not be shown will not be stored by graphics.c
18:35 #navit: <@KaZeR> 3 years ago, shit
18:41 -!- jandegr [5bb34cfc@gateway/web/freenode/ip.91.179.76.252] has quit [Quit: Page closed]
22:37 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has quit [Ping timeout: 240 seconds]
22:41 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has joined #navit
22:52 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
23:18 -!- Horwitz [~mich1@p200300800E4D5F00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
23:31 -!- Horwitz [~mich1@p200300800E6C0900022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:31 -!- mode/#navit [+o Horwitz] by ChanServ
--- Log closed Tue Sep 19 00:00:44 2017