[04:50:03] *** Joins: xenos1984 (~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120) [04:50:03] *** ChanServ sets mode: +v xenos1984 [14:49:00] *** Quits: xenos1984 (~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120) (Quit: Leaving.) [15:07:02] *** Joins: xenos1984 (~xenos1984@fa34-7f7b-d3b8-8d21-d480-87c4-07d0-2001.dyn.estpak.ee) [15:07:02] *** ChanServ sets mode: +v xenos1984 [16:36:49] hi there [16:37:42] <07KaZeR> @aerostitch \o/ [16:47:27] <11aerostitch> Finally waited the 10mins, so I can talk! \o/ [16:47:29] <11aerostitch> 😄 [16:47:38] <11aerostitch> Morning guys [16:47:55] <11aerostitch> sorry, not really available those last months [16:48:40] <11aerostitch> I'm wondering if we could add a note on each page we move to readthedocs so that we don't try to do it twice [16:49:30] <05jkoan> Hi @aerostitch nice to see you here [16:51:38] aerostitch : makes sense. so far i've added it as a note when protecting pages that have been moved, but we should probably put a big fat warning box at the top of the pages [17:08:02] *** Joins: jandegr (d5dbb394@gateway/web/freenode/ip.213.219.179.148) [17:15:34] <11aerostitch> Also could we hook the "latest" of readthedocs to trunk and keep stable on master so that we mimic the rest of the workflow? We might end up with a ton of merges from master all the time and it is not really nice for the review to clutter the readthedocs branch [17:33:08] well the thing is that master was originally designed as an auto-merge from trunk during the svn to git transition [17:33:36] so to push to trunk you need a pr, but then if the build succeeds in trunk once the pr is merged it automatically goes to master [17:33:58] <07KaZeR> hi @viktorgino ! [17:34:35] <07viktorgino> hi @KaZeR [17:34:45] <07viktorgino> i was directed here from https://github.com/navit-gps/navit/issues/790 [17:35:20] <07viktorgino> I'm planning on creating a QML based GUI for navit [17:35:50] <07viktorgino> Ultimately for use in my head unit software, but I would like to contribute as much of it back as possible [17:35:57] <07KaZeR> yep, i'm the one who posted that last comment 😃 [17:36:15] <07viktorgino> usernames are confusing 😄 [17:36:22] <07KaZeR> yeah they can be 😄 [17:36:37] <07KaZeR> nice. i think it definitely makes sense to unify our efforts because there's still quite a bit of work left [17:37:51] <07viktorgino> sure, i think it would be benefical for both projects [17:38:07] <07KaZeR> what head unit do you have? [17:38:34] <07viktorgino> the projects is this: https://github.com/viktorgino/headunit-desktop [17:38:47] <07viktorgino> here are some older screenshots: http://headunit.viktorgino.me/SCREENSHOTS [17:40:29] <07KaZeR> i just saw the screenshots. You're hired [17:41:20] <07viktorgino> thanks, will collect my company car and laptop tomorrow [17:41:36] <07KaZeR> lol [17:43:51] <07viktorgino> i've started working on the basic layout, i can show you some of the stuff soon [17:44:01] <07KaZeR> definitely interested [17:45:11] <07viktorgino> The menu I use is a drawer based menu, rather than a full screen overlay, i think its only the settings menu that will be full screen [17:45:35] <07viktorgino> but Im still trying to grasp some of the internals of navit [17:46:16] <07viktorgino> the qt5 driver is fairly feature complete tho, so that a huge help [17:46:41] <07KaZeR> yes definitely. It's used on Sailfish OS, but with the internal UI [17:48:31] <07viktorgino> would you know where could find more details on the Sailfish GUI for Navit? [17:48:42] <07KaZeR> have you seen our buildroot repo? allows us to build images for the raspberry pi that you can just flash directly [17:49:18] <07viktorgino> yes I have, not had a chance to test it tho [17:49:29] <07KaZeR> ok. i'm quite familiar with it if you have questiosn [17:49:49] <07viktorgino> I like the buildroot approach tho, i will probably go with buildroot for my own project too [17:49:55] <07KaZeR> regarding Sailfish, I think Zintor and @ilovekiruna would know better [17:50:25] <07viktorgino> sure, i will wait for their replies [17:51:05] <07KaZeR> also we don't really have a sailfish specific gui. AFAIK it's using our internal gui (the default one) on top of the qt5 graphics driver [17:51:29] <07KaZeR> (with some hardware tweaks in the qt5 driver for power management and access to the gps i think) [18:02:26] <07viktorgino> that makes sense [18:43:51] *** Quits: jandegr (d5dbb394@gateway/web/freenode/ip.213.219.179.148) (Quit: Page closed) [18:52:13] hey ilovekiruna [18:52:20] you do have a sailfish device, right? [20:23:20] I even have two [20:23:31] @kazer [20:23:35] nice! what does the UI look like? [20:53:23] i believe we had a picture in the wiki or in my fosdem talk [20:58:55] https://wiki.navit-project.org/index.php/Sailfish_OS [21:35:27] I just noticed that we dont have the sailfish docker image in our docker hub org [21:35:47] @kazer: do you know what the hold-back is? [21:37:28] reminds me, I probably should also make a new version of the image, based on the latest sailfish os version [21:37:35] <07KaZeR> Well the screenshots only show the map and some OSD. If it looks like the internal GUI, then it is the internal GUI using the qt5 driver 😃 [21:38:00] <07KaZeR> I don’t know what is preventing pushing the image. Probably just someone actually doing it 😃 [21:43:55] at least we have it in the dockerfile repo [21:44:18] could you push it? Or should we wait until I build a newer version? [21:57:35] *** Quits: xenos1984 (~xenos1984@fa34-7f7b-d3b8-8d21-d480-87c4-07d0-2001.dyn.estpak.ee) (Quit: Leaving.)