--- Log opened Wed Jul 11 00:00:04 2018 00:31 -!- Horwitz [~mich1@p200300800E070C00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 00:38 -!- tryagain [~quassel@217.107.194.24] has quit [Ping timeout: 248 seconds] 00:44 -!- Horwitz [~mich1@p200300800E05B900022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 00:44 -!- mode/#navit [+o Horwitz] by ChanServ 03:56 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 03:56 -!- mode/#navit [+v xenos1984] by ChanServ 04:39 -!- noradtux [~noradtux@2a04:4540:8c06:ae01:15e0:fa1f:c1c8:6370] has quit [Ping timeout: 240 seconds] 04:44 -!- noradtux [~noradtux@2a04:4540:8c07:7301:15e0:fa1f:c1c8:6370] has joined #navit 06:02 -!- naggety [~naggety@107.red-81-47-63.dynamicip.rima-tde.net] has joined #navit 06:18 -!- lains [55733cca@gateway/web/freenode/ip.85.115.60.202] has joined #navit 06:21 #navit: < lains> Hello all 06:21 #navit: < lains> I have been playing with navit on my old Mio C210 (running WinCE 4.2) 06:22 #navit: < lains> I does work quite nicely, I am so delighted that an obsolete device like this one, with so old maps (that cannot be updated anymore) can be brought alive again. 06:22 #navit: < lains> I have no environment to build WinCE images. 06:23 #navit: < lains> Is there a way to get the package resulting of a circle CI build? 06:23 #navit: < lains> Also, it seems speech is not working. 06:24 #navit: < lains> I have read on the Wiki that this should work by adding to navit.xml 06:24 #navit: < lains> But on my device, this does not seem to work. 06:25 #navit: < lains> Any idea on how I could debug this (adding logs in specific functions)? 06:26 #navit: < lains> And finally, I have seen that there is a specific page for navit on Sony Nav-U devices:https://wiki.navit-project.org/index.php/Sony_Nav-u_Devices 06:27 #navit: < lains> I have myself added a specific page for navit on Mio C210 and C310: https://wiki.navit-project.org/index.php/Unlocking_Mio_C310_and_C210_for_Navit 06:29 #navit: < lains> What about moving all the common stuff (if any) in the WinCE page, and have these two pages as "children" pages of the WinCE page? 06:30 #navit: < lains> Having links from WinCE to these pages, by allowing to click on specific devices? 06:48 -!- lains [55733cca@gateway/web/freenode/ip.85.115.60.202] has quit [Ping timeout: 252 seconds] 07:05 -!- lains [55733cca@gateway/web/freenode/ip.85.115.60.202] has joined #navit 07:29 -!- lains [55733cca@gateway/web/freenode/ip.85.115.60.202] has quit [Ping timeout: 252 seconds] 13:29 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 244 seconds] 13:59 -!- naggety [~naggety@107.red-81-47-63.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!] 15:01 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 15:02 -!- mode/#navit [+v xenos1984] by ChanServ 15:20 -!- lains [4eeca108@gateway/web/freenode/ip.78.236.161.8] has joined #navit 15:25 #navit: <@KaZeR> lains: you can get the latest builds from circleci here : http://download.navit-project.org/ thanks to jkoan's work 15:26 #navit: <@KaZeR> and the wiki changes that you suggest make change. It'll make it easier to find if we have one generic wince page, with some device-specific tips grouped there 15:32 #navit: < lains> Hi KaZeR 15:32 #navit: < lains> OK, so that's where I downloaded the WinCE build from. 15:34 #navit: < lains> I was thinking about getting the result of work that has not gone mainstream yet, but is in a pull request (so has gone through circleci). 15:34 #navit: < lains> In circleci, I can get build logs, but not the actual resulting package. 16:21 #navit: <@KaZeR> ha! 16:22 #navit: <@KaZeR> let me check something 16:22 #navit: <@KaZeR> i wonder if we could post back to a PR from circleci 16:23 #navit: <@KaZeR> i mean i know that it's possible, i'm just unsure if the artifact link is available during the build or if it becomes available once the build finishes 16:23 #navit: <@KaZeR> in the meantime if you have the buildid you're interested in i can check the link for you 16:24 #navit: < lains> OK 16:26 #navit: < lains> I don't have a build yet, but I will try an improvement that was suggested by charlescurley here: https://github.com/navit-gps/navit/pull/564#issuecomment-386750966 16:27 #navit: < lains> Once I have done that code, I can share the build to you to try the result on my WinCE device and make sure that it works as expected. 16:27 #navit: < lains> I have also recently worked on the "View on map" pointer. 16:28 #navit: <@KaZeR> ok nice. actually, do you want an invite to the github org? this way you should be able to access the artifacts directly 16:30 #navit: < lains> Yes, why not. 16:31 #navit: <@KaZeR> cool 16:32 #navit: <@KaZeR> sent 16:32 #navit: < lains> For the "View on map", I reused most of the existing code. 16:33 #navit: < lains> I also have thoughts about how to make the label (next to the location) more readable, but I keep this for the future. 16:33 #navit: < lains> I will submit a pull request for this. 16:33 #navit: < lains> Have you ever launched navit on a WinCE device? 16:34 #navit: < lains> It seems the audio is not working, even though all posts seem to refer to the same configuration. 16:34 #navit: <@KaZeR> i have, but not in quite some time 16:35 #navit: < lains> OK. At least it's not working on my Mio C210 but it is maybe coming from the audio config of the device itself... 16:35 #navit: <@KaZeR> i seem to recall a discussion in one of the ticket about speech in wince, let me see 16:36 #navit: <@KaZeR> ha no that was windows, not wince 16:36 #navit: < lains> Or if there is any debug log I should pay attention to... 16:36 #navit: < lains> I haven't seen anything in navit.log 16:37 #navit: < lains> But I am not at logging level set to debug, just warnings... 16:37 #navit: <@KaZeR> do you have access to a terminal on the device? you could test/experiment with espeak directly from there 16:37 #navit: < lains> No, I don't. 16:38 #navit: < lains> But if it's just a WinCE application to install, I could do that. 16:38 #navit: < lains> Do you mean that the espeak binary should be installed on the device? 16:42 #navit: < lains> I am searching, but it seems there are command line binaries for Windows. 16:42 #navit: < lains> I'm not sure there is a WinCE ARM version however. 16:43 #navit: < lains> Does navit.exe (compiled for WinCE) need another WinCE espeak.exe executable or is it able to render audio alone? 16:50 #navit: <@KaZeR> most of the time we use an external binary. i know that there's something in /support for the edge cases let me check 16:51 #navit: < lains> Ah, OK, so this is why it's not working. 16:51 #navit: <@KaZeR> https://github.com/navit-gps/navit/blob/trunk/navit/support/espeak/CMakeLists.txt#L2 16:52 #navit: <@KaZeR> so yeah if support/espeak is activated during the build, then espeak should be used directly from navit as a regular plugin 16:52 #navit: <@KaZeR> i've never used it that way myself though. Maybe we need to add a "plugin" entry in navit.xml 16:52 #navit: < lains> OK. 16:53 #navit: <@KaZeR> and according to the build logs, it is enabled : Enabled espeak ( Windows detected ) 16:53 #navit: < lains> I will first try to get espeak working on the device as standalone. 16:53 #navit: <@KaZeR> sounds good. you could also start navit in debug mode and check if the plugin is initialized 16:54 #navit: < lains> OK 16:55 #navit: <@KaZeR> actually we don't use dbg() there so there won't be any logs 16:56 #navit: <@KaZeR> if we want to go that way, you could start by adding a dbg statement there : https://github.com/navit-gps/navit/blob/trunk/navit/support/espeak/speak_init.c 16:56 #navit: < lains> I think my first track is going to copy what has been done on the Wiki part dedicated to Sony Nav-u: https://wiki.navit-project.org/index.php/Sony_Nav-u_Devices 16:56 #navit: < lains> It seems there is some code at startup to set the volume level... 16:57 #navit: < lains> Maybe that is just the missing part! 16:58 #navit: <@KaZeR> yeah this wiki page is a good starting point. We should maybe replace the static big-ass config file in the page with an xslt translation and provide the file in the package 16:58 #navit: <@KaZeR> cause it's impossible to maintain like that 16:58 #navit: < lains> Yes, I have seen that! 16:58 #navit: <@KaZeR> :) 16:59 #navit: < lains> I am actually going to make a diff to understand what is really changed compared to the default shipped file... 16:59 #navit: <@KaZeR> perfect 16:59 #navit: <@KaZeR> are you familiar with xslt ? 16:59 #navit: < lains> I think I will rework that page and link it to the main WinCE, now that I am a bit more familiar with this arch. 17:00 #navit: < lains> I have done some xslt to customiz my own navit.xml 17:00 #navit: < lains> Especially when I have been working on moving the layout XML in standalone files for android. 17:01 #navit: <@KaZeR> awesome 17:03 #navit: < lains> BTW, is there any consensus on what to do with that PR? 17:03 #navit: < lains> I mean https://github.com/navit-gps/navit/pull/559 17:07 #navit: <@KaZeR> thanks for bumping it. I personally like it. Let's give it a couple more days, tryagain was online yesterday, i will ask him to have a look when he comes back 17:11 #navit: < lains> OK thanks. 17:11 #navit: < lains> And thanks to the whole community for this nice software. 17:12 #navit: <@KaZeR> :D 17:12 #navit: < lains> I discovered it a bit more than one year ago, and I really like using it. 17:12 #navit: <@KaZeR> that's great :) there's still a lot to do, especially to make it more user friendly and refresh the UI a bit, but we'll get there! 17:16 #navit: < lains> For sure. 17:17 #navit: < lains> I have a list of "nice to have" features. 17:17 #navit: < lains> Most of them are actually UI. 17:18 #navit: <@KaZeR> definitely the biggest hurdle today. Our widget toolkit is outdated and has limitations. I personally think that qt5 is the way to go. I'm just going to need some help to finish the prototype :) 17:18 #navit: <@KaZeR> have you seen the POC? 17:19 #navit: < lains> No, but I'm interested! 17:19 #navit: < lains> You mean that Qt would replace the UI for all platforms? 17:19 #navit: <@KaZeR> probably yeah. 17:19 #navit: <@KaZeR> check out https://wiki.navit-project.org/index.php/QML2_GUI 17:20 #navit: <@KaZeR> qt5+qml2 brings menu backgrounds + transparency, UI effects like sliding/fading, etc 17:23 #navit: < lains> I have watched the animated demo. 17:23 #navit: <@KaZeR> qt5 also allows us to run navit on linux devices without X server. Super fast boot, native experience. Looks like a profesional grade device 17:24 #navit: <@KaZeR> qt5 is already usable on several platforms. not sure about wince though. The work is to finish building a minimal qml2 UI now 17:24 #navit: < lains> Yes, because it brings animations and effects, I think this is the way to go to make the UI more user-friendly (and so drive a wider adoption) 17:25 #navit: < lains> Great job. 17:25 #navit: <@KaZeR> if you want to help, qml is quite easy to learn. Most of the work is design and gruntwork (implement basic menu things) 17:27 #navit: < lains> August is going to be busy, but I will maybe have a look during the last weeks of July, just to see. 17:27 #navit: <@KaZeR> great! I started working on this over a year ago so i'm not expecting us to tackle that in 2 weeks :D 17:27 #navit: <@KaZeR> but having more hands/brains on it will definitely help 17:28 #navit: < lains> Is there a specific branch in git? 17:29 #navit: < lains> I have seen that there are instructions on how to build with cmake, but I don't know if this is for branch trunk. 17:29 #navit: <@KaZeR> https://github.com/navit-gps/navit/tree/qml2 17:30 #navit: <@KaZeR> some of the features were merged into trunk already, as they don't break anything 17:30 #navit: <@KaZeR> i have a stash somewhere that enables qt's virtual keyboard too 17:31 #navit: < lains> OK, I will try to rebuild it when I have some spare time. 17:32 #navit: < lains> But I can't commit to anything right now ;-) 17:33 #navit: < lains> I have to go. 17:33 #navit: < lains> Tx for the chat. 17:35 #navit: <@KaZeR> np 17:39 -!- lains [4eeca108@gateway/web/freenode/ip.78.236.161.8] has quit [Quit: Page closed] 17:47 -!- tim0 [~kvirc@dslb-092-076-123-237.092.076.pools.vodafone-ip.de] has joined #navit 17:50 #navit: < tim0> Hi! what happend to http://maps.navit-project.org/ or http://maps9.navit-project.org/ ? Can I still download maps somewhere? 17:56 #navit: <+jkoan> Hi tim0 17:57 #navit: <+jkoan> Currently our main server is down due to a hardware failure. You can download a map from maps3.navit-project.org 18:02 #navit: < tim0> thank you very much....i won't be lost now on the next trip 18:03 #navit: < tim0> what about current android builds? they are not updated for quite a while now. 18:08 #navit: <+jkoan> That's because we are about to switch our build environment for Android but don't have everything finished yet, so we can't update currently 18:09 #navit: <+jkoan> Mostly because we don't have enough manpower to drive the frequent development of navit 18:35 -!- tryagain [~quassel@217.107.194.6] has joined #navit 18:35 -!- mode/#navit [+o tryagain] by ChanServ 18:58 #navit: <@KaZeR> hey tryagain ! 18:58 #navit: <@KaZeR> hi tim0 and jkoan 18:58 #navit: <@tryagain> hi all 18:58 #navit: <+jkoan> Hi KaZeR 18:58 #navit: <@KaZeR> tryagain: would you mind sharing your opinion about https://github.com/navit-gps/navit/pull/559 ? 18:59 #navit: <@tryagain> np, once I get one :) 19:16 #navit: <@tryagain> looks very good. Was it tested on Win/WinCE platforms? IIRC we had some XML parsing specifics there. 19:25 #navit: <@KaZeR> we probably need to run a few more tests for wince, but yeah the root of the discussion was actually an issue we found with a wince device with limited memory 19:25 #navit: <@KaZeR> lains has a wince device and should be able to run more tests 19:42 #navit: <@tryagain> KaZeR what kind of problem? Lookls like I can't find its description on PR conversation page... I have a WINCE device too, so maybe I could try to reproduce it too. 20:16 #navit: <@tryagain> wince navit.zip artifact seems to contain no layout xml files, only root navit.xml. Maybe it's related to another navit.zip issue: it doesn't have espeak files inside. 20:16 #navit: <@tryagain> have to go now 20:32 -!- aerostitch [~aerostitc@c-24-23-230-215.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 20:34 -!- aerostitch [~aerostitc@c-24-23-230-215.hsd1.ca.comcast.net] has joined #navit 20:37 -!- tim0 [~kvirc@dslb-092-076-123-237.092.076.pools.vodafone-ip.de] has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/] 21:12 #navit: <@KaZeR> tryagain: issue was on a device with low memory. Trying to load the default navit.xml resulted in a crash. removing a couple of profiles solved the issue 23:29 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] --- Log closed Thu Jul 12 00:00:06 2018