--- Log opened Mon Mar 31 00:00:01 2014 01:08 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/wince_arm/svn/navit-svn-5761.failed 01:08 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html 03:30 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 03:30 -!- mode/#navit [+o KaZeR] by ChanServ 04:18 -!- thirtythreeforty [~thirtythr@unaffiliated/gh403] has joined #navit 04:20 #navit: < thirtythreeforty> Hey #navit! Maybe you guys can enlighten me a bit... I'm wanting to integrate Navit with Crank Software's Storyboard GUI design software. What display methods does Navit support? 04:22 #navit: < thirtythreeforty> Storyboard already renders to the Linux framebuffer, but I'm not familiar enough with fb to know if it can be shared with another program such as Navit. 05:12 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has joined #navit 06:28 #navit: < curious> thirtythreeforty, whatever your sdl supports/builds with 06:29 #navit: < curious> navit can work either with sdl or with gtk 06:30 #navit: < curious> if you run linux and fb , check stuff like wayland 06:30 #navit: < curious> starting from wikipedia article about wayland is very educational 06:32 #navit: < thirtythreeforty> curious, I'd like to avoid the GTK dependency, as that's comparatively slow to load. 06:33 #navit: < thirtythreeforty> So if I use SDL, where will it get rendered to? 06:34 #navit: < thirtythreeforty> Hm. Better question, would Wayland allow the two framebuffer applications to somehow coexist? 07:47 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has quit [Remote host closed the connection] 07:56 -!- _rd_ [~rd@p57B49EB2.dip0.t-ipconnect.de] has joined #navit 08:11 -!- drlizau [~liz@billiau.net] has joined #navit 08:25 -!- _rd_ [~rd@p57B49EB2.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 08:37 -!- _rd_ [~rd@p57B49EB2.dip0.t-ipconnect.de] has joined #navit 08:44 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 08:44 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 08:44 -!- mode/#navit [+o KaZeR] by ChanServ 08:49 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds] 09:21 -!- _rd_ [~rd@p57B49EB2.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds] 09:24 -!- thirtythreeforty [~thirtythr@unaffiliated/gh403] has quit [Ping timeout: 264 seconds] 09:28 -!- thirtythreeforty [~thirtythr@unaffiliated/gh403] has joined #navit 10:13 -!- thirtythreeforty [~thirtythr@unaffiliated/gh403] has quit [Ping timeout: 240 seconds] 10:38 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection] 12:35 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has joined #navit 13:34 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has joined #navit 13:47 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds] 15:03 -!- tryagain [~tryagain@178.216.76.18] has joined #navit 15:04 -!- thirtythreeforty [~thirtythr@unaffiliated/gh403] has joined #navit 15:55 -!- KaZeR [~KaZeR@64.201.252.132] has joined #navit 15:55 -!- mode/#navit [+o KaZeR] by ChanServ 16:23 -!- j_f-f [~quassel@orion2589.server4you.de] has quit [Remote host closed the connection] 16:26 -!- j_f-f [~quassel@orion2589.server4you.de] has joined #navit 16:31 -!- thirtythreeforty [~thirtythr@unaffiliated/gh403] has quit [Quit: You've been great, folks!] 17:16 -!- j_f-f [~quassel@orion2589.server4you.de] has quit [Remote host closed the connection] 17:19 -!- j_f-f [~quassel@orion2589.server4you.de] has joined #navit 17:22 -!- j_f-f [~quassel@orion2589.server4you.de] has quit [Remote host closed the connection] 17:25 -!- j_f-f [~quassel@orion2589.server4you.de] has joined #navit 17:47 -!- gringo [~gringo@unaffiliated/gringo] has quit [Read error: Operation timed out] 17:49 -!- gringo [~gringo@unaffiliated/gringo] has joined #navit 17:50 #navit: < xenos1984> hm... this dbus interface is not quite doing what i expect 17:50 #navit: < xenos1984> dbus-send --print-reply --session --dest=org.navit_project.navit /org/navit_project/navit/default_navit org.navit_project.navit.route.get_attr string:"destination_length" 17:50 #navit: < xenos1984> but it just starts another instance of navit and nothing else happens 17:51 #navit: < xenos1984> binding_dbus plugin is enabled in navit.xml and navit is running 17:56 #navit: * tryagain never used dbus 18:30 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has joined #navit 18:59 #navit: < tryagain> xenos1984 i suppose you've seen this http://trac.navit-project.org/ticket/1200 ? 19:00 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds] 19:03 #navit: < xenos1984> tryagain: hm... interesting... i thought that navit would be running on the session dbus, since also in the wiki --session is used... 19:04 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has joined #navit 19:04 #navit: < tryagain> i guess this may depend on build system used. 19:05 #navit: < xenos1984> ah, i see 19:05 #navit: < xenos1984> CMakeCache.txt:198:DBUS_USE_SYSTEM_BUS:BOOL=TRUE 19:05 #navit: < xenos1984> ok, this explains it... 19:08 #navit: < xenos1984> let's see what happens if i change this 19:12 #navit: < xenos1984> wtf? make[2]: *** No rule to make target `/usr/lib/python3.2/config/libpython3.2.so', needed by `navit/binding/python/.libs/libbinding_python.so'. Stop. 19:15 #navit: < xenos1984> let's disable python for now... 19:25 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 19:28 #navit: < xenos1984> hm... no change 19:28 #navit: < xenos1984> it just opens another navit instance and then hangs 19:29 #navit: < tryagain> strange... :/ 19:31 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has joined #navit 19:32 #navit: < _rd_> tryagain, good that you could repro the Android performance issues. I see approx. the same 5s latency when moving maps on the s4 here. 19:33 #navit: < tryagain> _rd_ looks like we should try passing graphics primitives in bundles to java code. I think it should really help. 19:36 #navit: < tryagain> a different idea would be to use OpenGL ES. It seems to be a native library on android. So it could make sense if we manage to reach it from our native code.... 19:36 #navit: < tryagain> but i don't have any opengl knowlege now besides i've read a few hours ago 19:37 #navit: < _rd_> Hmm....do you know if there is an OpenGL ES interface below the Android HAL? 19:38 #navit: < _rd_> If not, you probably would need to go through jni anyways. 19:39 -!- zoff99 [~chatzilla@unaffiliated/zoff99] has joined #navit 19:39 #navit: < _rd_> If it is, do you understand how portable from one device the solution would be? 19:39 #navit: < zoff99> you know that those issues with map scrolling have long been solved 19:39 #navit: < tryagain> i've only read that data for OpenGL ES should be prepared to pass to native c code 19:39 #navit: < tryagain> zoff99 hi! 19:39 #navit: < zoff99> at least on android 19:39 #navit: < zoff99> tryagain: hi 19:40 #navit: < zoff99> its certainly no S4 issue, or android issue :) 19:40 #navit: < tryagain> well, i think we could backport your improvement... 19:41 #navit: < tryagain> what's the idea behind it? 19:41 #navit: < zoff99> navit does drawing in a very bad way. because on some embedded systems you dont have much other choices 19:48 #navit: < tryagain> zoff99 It looks like you just have moved graphics interaction into a different thread? 19:50 #navit: < tryagain> http://viewsvn1.zanavi.cc/viewvc.cgi/zanavi_public1/navit/navit/graphics/android/graphics_android.c?r1=29&r2=30 19:52 #navit: < zoff99> well, you dont understand how navit draws the map 20:00 #navit: < tryagain> zoff99 ok, i see you're moving the bitmap now. It could be done in navit.xml right now. 20:01 #navit: < tryagain> but your map layout drops detail as our car-android does 20:02 #navit: < tryagain> and it seems to still lag when there are too much objects displayed 20:03 #navit: < tryagain> not as much as navit with generic car layout, but i think with our car layout you'll get the same performance 20:07 #navit: < tryagain> zoff I think I found a rendering glitch in zanavi. Go to Tallinn, Esti, there's a lake Ulemiste jav nearby. At some zoom levels it gets split into triangles. 20:07 #navit: < tryagain> zoff99 ^^^ 20:14 #navit: < tryagain> anyway, I should confess, zanavi is looking and performing very good 20:18 -!- drlizau [~liz@billiau.net] has joined #navit 20:26 #navit: < zoff99> thats no bug :) 20:29 #navit: < zoff99> its a feature :) 20:33 #navit: < tryagain> ;) 20:36 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds] 20:51 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has joined #navit 21:06 -!- zoff99 [~chatzilla@unaffiliated/zoff99] has quit [Quit: ChatZilla 0.9.86-rdmsoft [XULRunner 1.9.1/20090707221522]] 21:13 -!- _rd_ [~rd@p57B48447.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds] 21:14 -!- tryagain [~tryagain@178.216.76.18] has quit [Remote host closed the connection] 22:37 -!- drlizau [~liz@billiau.net] has quit [Ping timeout: 240 seconds] 23:09 #navit: < xenos1984> from my own experience i can confirm that the real ülemiste järv contains no triangles, but regular water - but next time i'm there i will check, just in case 23:09 #navit: < xenos1984> good night 23:09 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has quit [Remote host closed the connection] 23:55 -!- drlizau [~liz@billiau.net] has joined #navit --- Log closed Tue Apr 01 00:00:01 2014