--- Log opened Thu Nov 15 00:00:09 2018
00:28 #navit: < genesis> maptool could be in same repo but separate from navit build ?
00:28 #navit: < genesis> like others tools in navit.
04:14 #navit: <@KaZeR> it's already the case.. the only thing that we could change would be to not build it by default maybe?
05:54 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
05:54 -!- mode/#navit [+v xenos1984] by ChanServ
06:58 #navit: <+Navit> <jkoan> @KaZeR of course at now maptool is using files together with navit core, but nearly everything I found so far can be replaced. The only thing that is really a dependency is probably the item def which is in case a problem. But even this can easily be ruled out by making a navit lib with real headers and so on. So plugins can be written out of tree, and don't need to be coded and compiled in navit tree. I also
06:58 #navit: <+Navit> described this on your pr of the audio branch. It would be a long way, but we can make navit work in two parts, the library and the gui separately. Then also the maptool can be in its own repo by relying on libnavit which provides functions, constants and so on for external use. And I think this is what we need to target. Of course I don't want to break modularity, and I think we don't do it with this way. And the reason
06:58 #navit: <+Navit> maptool should be it's own sub project is to make things clearer and again more modular.
07:04 #navit: <+Navit> <jkoan> It's more or less the same we talked about in this PR:  https://github.com/navit-gps/navit/pull/368 (audio merge pr)
07:06 -!- naggety [~naggety@232.red-81-47-9.dynamicip.rima-tde.net] has joined #navit
09:10 #navit: < rokm> Hi
09:10 #navit: < rokm> KaZeR: any finding regarding DBus ?
09:51 -!- basilic666 [b92ed44f@gateway/web/freenode/ip.185.46.212.79] has joined #navit
09:52 #navit: < basilic666> hello all
11:00 -!- basilic666 [b92ed44f@gateway/web/freenode/ip.185.46.212.79] has quit [Ping timeout: 256 seconds]
13:43 -!- basilic666 [4d88133c@gateway/web/freenode/ip.77.136.19.60] has joined #navit
13:43 #navit: < basilic666> hello all
13:43 #navit: < basilic666> again :=)
13:56 -!- basilic666 [4d88133c@gateway/web/freenode/ip.77.136.19.60] has quit [Ping timeout: 256 seconds]
15:05 -!- naggety [~naggety@232.red-81-47-9.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
15:43 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
15:50 #navit: <@KaZeR> hi there
15:51 #navit: <@KaZeR> rokm: not yet, yesterday was quite busy. But thanks for the reminder
15:52 #navit: <@KaZeR> jkoan: the issue with the audio branch is that it's a scope creep indeed. But looking at projects from basilic, rokm or man-x86 i'm thinking that we now have more manpower to push a sister project forward, where we would move the audio playback into another app that would embed navit. Pretty much what rokm's app is doing
15:53 #navit: <@KaZeR> rokm: would you be interested in consolidating your work in a new app under the navit-gps github org?
16:04 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
16:04 -!- mode/#navit [+v xenos1984] by ChanServ
17:02 -!- basilic [~basilic@228-221-190-109.dsl.ovh.fr] has joined #navit
17:02 #navit: < basilic> hello all again again :)
17:41 #navit: < basilic> I have some problem on the menu setting
17:41 #navit: < basilic> on the navit.xml
17:56 #navit: < basilic> I don't know why My main menu was not on screen
17:57 #navit: < basilic> https://snag.gy/pHNceO.jpg
18:31 #navit: < man-x86> KaZeR: I only came here for an issue with dbus and the lack of documentation
18:44 #navit: <@KaZeR> basilic: odd. did you change the menu xml?
18:44 #navit: <@KaZeR> man-x86: but you're working on a carputer project right?
18:48 #navit: < basilic> odd?
18:48 #navit: < man-x86> KaZeR: right
18:49 #navit: < basilic> I want to has only former destination, city, configuration and music 
18:49 #navit: < basilic> on the main menu
18:52 #navit: < basilic> I don't know Why, but if I delete the return line on the former destination menu, it's no good
18:52 #navit: < basilic> https://snag.gy/Nn0zoi.jpg
18:53 #navit: <@KaZeR> basilic: it kind of makes sense since internal isn't aware of the width of your screen. It doesn't support fluid/liquid as qt would
18:54 #navit: < basilic> okai
18:54 #navit: <@KaZeR> man-x86: would you be interested in collaborating on a project like that? how far is your own UI currently?
18:58 #navit: < man-x86> I'm afraid I barely have enough time for my own projects... but I can still contribute to the documentation when I understand how the dbus interface works
18:59 #navit: < basilic> KaZeR, I have clone the navit git
18:59 #navit: < basilic> to my github
18:59 #navit: <@KaZeR> man-x86: ha, time! do you have a screenshot of your current UI?
18:59 #navit: < basilic> to push my modification
18:59 #navit: < man-x86> it's not very complex at the moment, it's based on PyQt and uses dbus to get the data from Navit
18:59 #navit: < man-x86> KaZeR: sure http://monorailc.at/private/navit/uit9_0.png
19:00 #navit: <@KaZeR> ha right that's the one i remember. For some reason i thought that this capture was from rokm 
19:00 #navit: <@KaZeR> man-x86: that's python right?
19:00 #navit: < man-x86> yep, PyQt
19:00 #navit: <@KaZeR> ok. are you using qml?
19:01 #navit: < man-x86> not at all
19:02 #navit: <@KaZeR> ok. have you seen the qt5/qml2 POC ?
19:02 #navit: < man-x86> actually, I don't know how to use them or if it would help, so I went the Qt4 way with widgets
19:02 #navit: < man-x86> nope
19:02 #navit: <@KaZeR> https://wiki.navit-project.org/index.php/QML2_GUI 
19:02 #navit: <@KaZeR> qml has the benefit of allowing a separation between the code and the UI design
19:02 #navit: < man-x86> oh, nice
19:03 #navit: <@KaZeR> here's the main menu from one of the two gifs in the wiki page i shared : https://github.com/navit-gps/navit/blob/trunk/navit/gui/qt5_qml/skins/modern/MainMenu.qml 
19:03 #navit: < man-x86> i'm using a terrible hack with windowcontainers, but it seems to work
19:04 #navit: <@KaZeR> i don't think that the windowcontainer is bad.. it's actually handy :)
19:04 #navit: < man-x86> i'll probably upgrade to the QML interface when the rest of the interface work better, but I still want all the tabs to be separated
19:05 #navit: <@KaZeR> http://doc.qt.io/qt-5/qml-qtquick-controls-tabview.html 
19:05 #navit: <@KaZeR> i would advise you to have a look at qtcreator. It's handy to design QML UIs
19:06 #navit: <@KaZeR> qt5 also allows nice, modern features like menu transition (fade in/out, sliding, etc)
19:06 #navit: < man-x86> I went a totally different way, building everything in a text editor
19:06 #navit: <@KaZeR> it works too :) i actually edit a lot of qml directly with a text editor
19:06 #navit: < man-x86> I'm more an hardware guy who wanted to have a software that works, so my code is far from pretty, but it works
19:08 #navit: <@KaZeR> absolutely. I'm just thinking that what's lacking today (not just in navit, but globally) is a coordinated effort to build something like this
19:08 #navit: <@KaZeR> here's the POI menu, with a dynamic map embeded on line 81 : https://github.com/navit-gps/navit/blob/trunk/navit/gui/qt5_qml/skins/modern/poi.qml 
19:09 #navit: < man-x86> but IMO dbus is a big part of such thing
19:09 #navit: <@KaZeR> absolutely
19:09 #navit: <@KaZeR> we are going to need to move the audio code out of navit, and moving it into something like your app is the solution
19:09 #navit: < man-x86> I mean integrating Navit into an interface is one thing, but getting the data where it needs to be is also a big thing as well
19:11 #navit: < man-x86> choices like these are up to you, I'm only an user, I can't really decide for everyone
19:12 #navit: <@KaZeR> it's just that i see that i see that there's an overlapping need, and some independent efforts to work on something like this. we could have much better results if we work together
19:13 #navit: < man-x86> sure, but I don't see how you want it to work
19:15 #navit: <@KaZeR> what you have is a good basis. That screenshot shows the core of an IVI software. we would just need to convert it to a C app
19:15 #navit: <@KaZeR> is your code available online yet?
19:15 #navit: < man-x86> I only plan to release it when it works
19:16 #navit: <@KaZeR> ok - that's your call :)
19:16 #navit: < man-x86> to be honest, I wanted to try other navigation softwares, not necessarily Navit
19:16 #navit: < man-x86> same for the music
19:17 #navit: <@KaZeR> what are you using for the music currently?
19:17 #navit: <@KaZeR> what other navigation softwares are you planning on trying?
19:17 #navit: < man-x86> I tried to integrate Clementine, but ended up doing my own Qt widget
19:17 #navit: <@KaZeR> you want mpd playback right?
19:17 #navit: < man-x86> I'm using MPD
19:17 #navit: <@KaZeR> ok
19:18 #navit: < man-x86> http://monorailc.at/private/navit/uit9_3.png < it looks ugly and needs lots of improvements
19:18 #navit: < man-x86> but at least it works
19:18 #navit: < man-x86> @KaZeR | what other navigation softwares are you planning on trying? < I wanted to try Offroad and Marble
19:19 #navit: < man-x86> but the idea of my interface is to have something more modular
19:19 #navit: <@KaZeR> working is an important thing. designing pretty UI is *really* difficult
19:19 #navit: < man-x86> I started with Kodi and the "CarPC-Touch" skin
19:20 #navit: < man-x86> it looked good, but it was terrible to customize or to debug
19:20 #navit: <@KaZeR> yeah, it's also quite resource heavy
19:21 #navit: <@KaZeR> btw : things like this http://1.bp.blogspot.com/-Y1MJoj4NQKM/VRSAnjaObfI/AAAAAAAAAog/2b-h9LVsE24/s1600/settings%2Bpage.png are quite easy to do with qt5/qml
19:21 #navit: < man-x86> to be honest, I prefer practicality over prettiness
19:21 #navit: < man-x86> too late, I already have that: http://monorailc.at/private/navit/uit9_1.png
19:22 #navit: < man-x86> and it's not too hard either in PyQt
23:29 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
--- Log closed Fri Nov 16 00:00:10 2018