--- Log opened Thu Jan 10 00:00:36 2019 05:06 -!- xenos1984 [~xenos1984@8051-7fac-79a4-b82c-8780-87e7-07d0-2001.dyn.estpak.ee] has joined #navit 05:06 -!- mode/#navit [+v xenos1984] by ChanServ 07:34 -!- naggety [~naggety@217.red-88-31-104.dynamicip.rima-tde.net] has joined #navit 10:28 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection] 10:28 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has joined #navit 10:28 -!- mode/#navit [+v Navit] by ChanServ 10:30 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection] 10:31 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has joined #navit 10:31 -!- mode/#navit [+v Navit] by ChanServ 11:06 -!- xenos1984 [~xenos1984@8051-7fac-79a4-b82c-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Ping timeout: 260 seconds] 12:45 #navit: <+Navit> Hi @all 15:27 -!- xenos1984 [~xenos1984@8051-7fac-79a4-b82c-8780-87e7-07d0-2001.dyn.estpak.ee] has joined #navit 15:27 -!- mode/#navit [+v xenos1984] by ChanServ 15:31 -!- naggety [~naggety@217.red-88-31-104.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!] 15:45 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection] 15:46 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has joined #navit 15:46 -!- mode/#navit [+v Navit] by ChanServ 15:51 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection] 15:52 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has joined #navit 15:52 -!- mode/#navit [+v Navit] by ChanServ 16:07 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection] 16:07 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has joined #navit 16:07 -!- mode/#navit [+v Navit] by ChanServ 16:32 -!- udovdh [~udovdh@2001:981:a812:0:213:3bff:fe0f:9fb1] has joined #navit 16:38 -!- udovdh [~udovdh@2001:981:a812:0:213:3bff:fe0f:9fb1] has quit [Remote host closed the connection] 16:42 #navit: <+Navit> Hi @all been going through the navit docs and could not find the answers I was looking for... Is it possible to run Navit locally on a RaspberryPi but use it through a web browser on the Pi itself ? 16:45 -!- udovdh [~udovdh@2001:981:a812:0:213:3bff:fe0f:9fb1] has joined #navit 16:50 -!- udovdh [~udovdh@2001:981:a812:0:213:3bff:fe0f:9fb1] has quit [Remote host closed the connection] 17:05 #navit: <@KaZeR> Hi IndianaTux. We used to have a plugin that would do exactly that but it hasn't been maintained. This would be possible to fix this using one of the qt components though 17:09 #navit: <+Navit> KaZeR: any pointers to documentation ? 17:59 #navit: <@KaZeR> this would require some coding as of today. How comfortable would you be with that? 18:04 #navit: <@KaZeR> http://blog.qt.io/blog/2017/07/07/qt-webgl-streaming-merged/ would be the easiest solution 18:05 #navit: <@KaZeR> at some point i do want to fix this. It would allow anybody to try navit directly from one of our servers 18:28 #navit: <+Navit> Should be able to manage it. 18:28 #navit: <@KaZeR> awesome! 18:30 #navit: <+Navit> so if I understand well, navit is a Qt app and this plugin would allow "any" Qt application to be streamed through a web browser ? 18:39 #navit: <+ilovekiruna> hi KaZeR, hi IndianaTux 18:39 #navit: <+ilovekiruna> great idea, love it 19:14 #navit: <@KaZeR> IndianaTux: almost. Navit CAN be a QT app via one of its graphics drivers. But yeah that's what this plugin is supposed to do 20:19 -!- genesis [~genesis@unaffiliated/genesis] has quit [Remote host closed the connection] 21:24 -!- tryagain [~quassel@217.107.194.47] has joined #navit 21:24 -!- mode/#navit [+o tryagain] by ChanServ 21:41 -!- tryagain [~quassel@217.107.194.47] has quit [Remote host closed the connection] 21:43 -!- mvglasow [~mvglasow@dslb-088-067-043-080.088.067.pools.vodafone-ip.de] has joined #navit 21:47 #navit: < mvglasow> hi folks 21:48 #navit: < mvglasow> following a unified build script for CI and local Linux, I am now trying to fix the F-Droid build 21:49 #navit: < mvglasow> with some obstacles, though, as Coverity is offline, therefore trunk currently isn’t getting merged into master 21:52 #navit: < mvglasow> but in any case, what would we want pushed to F-Droid? Every commit that makes it into master? 21:58 #navit: <+ilovekiruna> mvglasow, with this script would it also be possible to push ci builds to the beta channel or a custom developer fdroid channel? 22:01 #navit: < mvglasow> the script just builds Navit 22:02 #navit: < mvglasow> I've moved the build steps from the CircleCI yml into a shell script 22:02 #navit: < mvglasow> and the yml calls the script now 22:04 #navit: < mvglasow> updating the download center is a separate step in the yml (backed by a separate script) 22:04 #navit: < mvglasow> but in theory this could be triggered from CI 22:05 #navit: < mvglasow> i.e. everything F-Droid related 22:05 #navit: <+ilovekiruna> ah, ok, I get it now 22:05 #navit: <+ilovekiruna> just like I was doing it on sailfish 22:48 -!- xenos1984 [~xenos1984@8051-7fac-79a4-b82c-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Quit: Leaving.] --- Log closed Fri Jan 11 00:00:38 2019