--- Log opened Wed Jan 30 00:00:06 2019
00:26 -!- xenos1984 [~xenos1984@227-28-196-88.dyn.estpak.ee] has quit [Quit: Leaving.]
01:47 -!- Horwitz [~mich1@p200300EC9BC62700022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
02:01 -!- Horwitz [~mich1@p200300EC9BC2DD00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
02:01 -!- mode/#navit [+o Horwitz] by ChanServ
06:09 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:09 -!- mode/#navit [+v xenos1984] by ChanServ
07:08 -!- grayhatter [grayhatter@utox/developer/grayhatter] has joined #navit
07:12 #navit: < grayhatter> should I be on IRC or discord for developer questions?
07:13 #navit: < grayhatter> related, how does navit render it's images? To gtk or with opengl?
07:30 -!- naggety [~naggety@22.red-88-29-212.staticip.rima-tde.net] has joined #navit
07:51 #navit: < genesis> yo grayhatter :)
07:51 #navit: < genesis> depend your compile option 
07:51 #navit: < grayhatter> I want to compile something I can run on my mazda
07:52 #navit: < genesis> which OS ?
07:52 #navit: < grayhatter> I also don't wanna fundemntally break the thing... so I'm restricted to what existing libs I'm allowed to use
07:52 #navit: < grayhatter> lol
07:52 #navit: < grayhatter> arm-linux... mostly
07:52 #navit: < grayhatter> it's this franken beast of nightmares
07:53 #navit: < grayhatter> fun fact, did you know most stock car infotainment systems are webbrowsers running on wayland ?
07:53 #navit: < grayhatter> there's something you can't unknow :D
07:53 #navit: < genesis> i've worked at hertz, we use openembedded ;)
07:55 #navit: < genesis> you can build sdl or gtk version without opengl, look cmake options
07:55 #navit: < grayhatter> hertz has their own what now? Is it a car system, or the pay extra for this navigation app we superglued to the car thing?
07:55 #navit: < grayhatter> what parts do I need to do turn-by-turn navigation? and how do I get that data onto my screen?
07:55 #navit: < genesis> i worked for rental service; the rental embedded stuff has inboard rental information 
07:56 #navit: < grayhatter> I (probably) don't need hand holding, you can point me to code I can read
07:57 #navit: < genesis> no sorry.
15:26 -!- naggety [~naggety@22.red-88-29-212.staticip.rima-tde.net] has quit [Quit: Konversation terminated!]
15:51 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
16:18 -!- xenos1984 [~xenos1984@4622-3e28-cab5-0543-8780-87e7-07d0-2001.dyn.estpak.ee] has joined #navit
16:18 -!- mode/#navit [+v xenos1984] by ChanServ
20:25 -!- ilovekiruna [~ilovekiru@2a02:8108:d00:110:d96c:93f4:8be1:474b] has joined #navit
20:25 -!- mode/#navit [+v ilovekiruna] by ChanServ
21:17 #navit: <+ilovekiruna> hi grayhatter
21:17 #navit: < grayhatter> hi ilovekiruna 
21:18 #navit: <+ilovekiruna> I just read the log of the irc messages. I might not be able to tell you everything, but hopefully I have some useful hints
21:19 #navit: <+ilovekiruna> so far I did not exactly understand your goal
21:19 #navit: <+ilovekiruna> you want sth mazda specific?
21:20 #navit: <+ilovekiruna> for the turn by turn navigation is the question related to our routing algorithm?
21:22 #navit: < grayhatter> the goal is turn by turn navigation support for my mazda
21:22 #navit: < grayhatter> I have a "working" hud, I'm wondering how I get the data from navi onto the screen
21:22 #navit: < grayhatter> compiling gtk for my car is a non-starter, it'll never happen
21:23 #navit: <+ilovekiruna> which libraries are supported by the hud?
21:23 #navit: <+ilovekiruna> or how do you draw on it?
21:24 #navit: < grayhatter> I have to use wayland, so I'm drawing directly to shared memory block
21:24 #navit: < grayhatter> I do have access to opengl
21:25 #navit: < grayhatter> https://gist.github.com/GrayHatter/f569fc35e2fcf40d5c6d10283da0a6e7
21:26 #navit: < grayhatter> thoes are the libraries that come preloaded, I'm also willing to build/install others if I need to
21:30 #navit: <+ilovekiruna> just a speculation by me, but shouldnt qt run on wayland?
21:30 #navit: < grayhatter> I'm also not putting Qt on my car
21:31 #navit: <+ilovekiruna> i asked, because we for example run also navit on SailfishOS devices which to my knowledge use wayland further down
21:31 #navit: <+ilovekiruna> but all via qt5
21:32 #navit: <+ilovekiruna> I think a little idea you could get from here: https://wiki.navit-project.org/index.php/Configuration/Display_Options
21:32 #navit: <+ilovekiruna> these are the options potentially have
21:33 #navit: <+ilovekiruna> but I dont know exactly the current status of all guis
21:33 #navit: <+ilovekiruna> seems like thethere was also a driver for opengl
21:35 #navit: <+ilovekiruna> what do you think?
21:36 #navit: <+ilovekiruna> the corresponding code for opengl you could fine here: https://github.com/navit-gps/navit/tree/trunk/navit/graphics/opengl
22:48 -!- mvglasow [~mvglasow@dslb-188-104-100-007.188.104.pools.vodafone-ip.de] has joined #navit
22:50 #navit: < mvglasow> hi there, any Tomtom folks out there?
22:50 #navit: < mvglasow> if so, I'd like to ask you to take a look at https://github.com/navit-gps/navit/pull/737
22:51 #navit: < mvglasow> it's a proposed redesign of the default OSD (currently only for Android and iOS) which I'd like to extend to other mobile platforms
23:17 #navit: <+ilovekiruna> mvglasow, could you also add sth to the discussion above?
23:19 #navit: < mvglasow> not much, I'm afraid, whatever little background on platform integration I have is pretty mainstream (desktop Linux and Android)
23:40 -!- xenos1984 [~xenos1984@4622-3e28-cab5-0543-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Quit: Leaving.]
23:46 -!- mvglasow [~mvglasow@dslb-188-104-100-007.188.104.pools.vodafone-ip.de] has quit [Quit: Leaving]
--- Log closed Thu Jan 31 00:00:08 2019