--- Log opened Fri Jan 06 00:00:55 2017
03:31 -!- Netsplit *.net <-> *.split quits: jjardon, @Horwitz, Number6, Brinky, bzed, Marc0, latouche, Celelibi, redurgam
03:37 -!- Netsplit over, joins: jjardon, bzed, @Horwitz, Number6, latouche, Celelibi, redurgam, Brinky, Marc0
03:38 -!- zintor [2edfe18e@gateway/web/freenode/session] has joined #navit
03:38 #navit: < zintor> hi @all
03:39 -!- zintor [2edfe18e@gateway/web/freenode/session] has quit [Changing host]
03:39 -!- zintor [2edfe18e@gateway/web/freenode/ip.46.223.225.142] has joined #navit
03:40 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
04:15 -!- jjelen [jjelen@nat/redhat/x-evklvkfxcisvgiah] has joined #navit
08:20 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
10:48 #navit: < zintor> finally I was successfully able to built navit again on SailfishSDK
10:53 -!- zintor [2edfe18e@gateway/web/freenode/ip.46.223.225.142] has quit [Ping timeout: 260 seconds]
11:32 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
11:52 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
11:52 #navit: < zintor> re
12:52 -!- jandegr [5bb61abf@gateway/web/freenode/ip.91.182.26.191] has joined #navit
12:53 -!- jjelen [jjelen@nat/redhat/x-evklvkfxcisvgiah] has quit [Ping timeout: 248 seconds]
13:05 #navit: < kazer> hi there
13:05 #navit: < kazer> zintor: good news! what was wrong? we should probably put it in the wiki or something
13:07 #navit: < zintor> hi kazer!
13:07 #navit: < zintor> I knew, that I wrote all down, but I didn't find it yesterday.
13:07 #navit: < zintor> I will update my wiki page
13:08 #navit: < kazer> great. please share the link, i'm sure it'll help others
13:08 #navit: < kazer> also we could use that doc to try and put some tests in our CI for this build too
13:16 #navit: < zintor> you will find it at http://wiki.navit-project.org/index.php/User:Zintor
13:17 #navit: < zintor> I will build it again with a new fresh install of Sailfish SDK with the steps again and will maybe improve the steps
13:20 #navit: < kazer> great. Actually maybe we should put that on its own page, titled SailfishOS
13:21 #navit: < kazer> would you like to help me put this build in our CI? We could have automated packages this way (and tests that ensure that we don't break the build)
13:21 #navit: < zintor> I will give you "green lights", when I am happy to put it on its own page
13:22 #navit: < kazer> ok
13:22 #navit: < zintor> sure, I will help as much I could to bring it in your CI
13:22 #navit: < kazer> cool. Ready the instructions am i not clear if you are building on the phone itself or on a computer
13:24 #navit: < zintor> I built it on the phone emulator
13:24 #navit: < kazer> do you have more details about this emulator?
13:24 #navit: < zintor> it is a vm
13:25 #navit: < zintor> what details do you need
13:26 #navit: < kazer> i'd like to see if we could run it on circleci, but i doubt it
13:26 #navit: < zintor> it is based on mer
13:26 #navit: < zintor> I will have a look
13:27 #navit: < kazer> ah, actually https://katastrophos.net/andre/blog/2014/03/29/running-sailfishos-build-engine-outside-virtualbox-vm/
13:29 #navit: < zintor> is that what you need?
13:29 #navit: < kazer> it should get me started :)
13:29 #navit: < zintor> :)
13:29 #navit: < kazer> are you familiar with cross-compilation?
13:29 #navit: < zintor> no
13:30 #navit: < kazer> ok. if you have interest in learning, we can work on this together :)
13:30 #navit: < kazer> also once we move that page from your user space to its own page, i'd like to post something about it on the social media
13:31 #navit: < zintor> puh...interest is there to learn cross-compiling, but I assume that my spare time is limited :(
13:32 #navit: < zintor> and I would like to get navit with a "sailfish"-look and usage running
13:32 #navit: < zintor> this makes the "sailors" (SailfishOS-user) happy ;)
13:34 #navit: < zintor> and if navit would pass, or partly pass, the Jolla Harbour Validator would be more great
13:34 #navit: < kazer> i like that! what is needed to for the look and feel?
13:35 #navit: < zintor> qml gui
13:35 #navit: < kazer> which is in my todo list.. qt5+qml2. How familiar are you with qt?
13:35 #navit: < kazer> some of the harbour validator issues should not be too difficult to fix
13:35 #navit: < kazer> like version stuffs
13:35 #navit: < zintor> that's why I would like to see my very basic gui, which shows some entries
13:36 #navit: < zintor> yes, versions and icons are ok for me
13:38 #navit: < zintor> the last error message was from navit:
13:38 #navit: < zintor> error:navit:navit_init:FATAL: No GUI available.
13:38 #navit: < zintor> and you are asking for the output of cmake
13:38 #navit: < zintor> is the output stored somewhere?
13:40 #navit: < jandegr> hi zintor & kazer, are you using qt5 with the existing qml gui ?
13:42 #navit: < kazer> zintor: nop not stored, you need to copy paste. CMakeCache.txt would give us some infos also
13:42 #navit: < kazer> hey jandegr !
13:43 #navit: < jandegr> I have modified metalstrolch graphics qt5 to make it usable on desktops, but I had quite a bit of work to bump gui_qml to qt5
13:45 #navit: < kazer> i have also the premise of a qt5 gui, but i currently have an issue with map <-> gui interactions
13:49 #navit: < zintor> hi jandegr
13:49 #navit: < jandegr> IMHO if metalstrolch's qt5 works on sailfish and the few small issues to make it work on desktops can be fixed, then ditch the old QT code ?
13:50 #navit: < jandegr> to have one common codebase
13:51 #navit: < zintor> I am on the way learning qt...so it is limited, but growing :)
13:52 #navit: < kazer> jandegr: definitely
13:52 #navit: < kazer> zintor: perfect :)
13:53 #navit: < kazer> jandegr: aside from qt5 (the graphics driver) we also need to work on the gui itself (qml2)
13:53 #navit: < jandegr> first things first kazer
13:53 #navit: < kazer> btw : did you see the PR i sent a few days ago?
13:54 #navit: < zintor> what are the next steps? I will install a fresh SailfishSDK and will update my page to get the build instructions to its own page.
13:56 #navit: < kazer> zintor: depends of what's your priority :)
13:57 #navit: < zintor> as I am not so familiar with qt5, I could not help so much in coding
13:58 #navit: < zintor> the next step could be, that I create a navit.xml with a nice layout, which looks nice in sailfish usage
13:59 #navit: < zintor> so it fits nice on Jolla smartphone
14:01 #navit: < jandegr> this is how far I got qml working with qt5 on linux https://dl.dropboxusercontent.com/u/93775123/Navit/qt5%2Bqml.webm
14:02 #navit: < jandegr> so I suppose at first you would use gui_internal on sailfish with qt5,
14:04 #navit: < kazer> zintor: this would be already helpful. Please use https://github.com/pgrandin/navit-nuc-layout as an example, it will allow us to easily test and reuse it
14:04 #navit: < jandegr> kazer wha do you mean with ""but i currently have an issue with map <-> gui interactions""
14:05 #navit: < zintor> I will use this layout
14:10 #navit: < kazer> jandegr: https://github.com/navit-gps/navit/blob/qt5/navit/gui/qml2/gui_qml2.cpp#L255
14:11 #navit: < kazer> if i enable this, i can use the test gui, but no map is drawn. If i enable this, it's the opposite (map is drawn, but UI event are not propagated to the GUI)
14:11 #navit: < kazer> zintor: great let me know if you have questions
14:11 #navit: < zintor> sure
14:11 #navit: < kazer> jandegr: nice web demo you got there. what did you need to change to get this to work? (i'd like to push that to trunk)
14:12 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has quit [Quit: Leaving.]
14:13 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
14:13 #navit: < zintor> re
14:14 #navit: < jandegr> brb
14:19 -!- zintor1 [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
14:20 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has quit [Ping timeout: 272 seconds]
14:24 -!- zintor1 [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has quit [Ping timeout: 245 seconds]
14:26 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
14:26 #navit: < jandegr> kazer there was quite a bit of work to bump qml from qt4 to qt5
14:27 #navit: < jandegr> but while I was working on the search I put it on hold
14:31 #navit: < kazer> jandegr: i am sure that it wasn't trivial indeed
14:32 #navit: < jandegr> that line 255 is commented out in my working code (qt5 graphics)
14:34 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has quit [Quit: Leaving.]
14:36 #navit: < kazer> jandegr: yeah, for qml you need it commented. But i am probably missing a connection between map and gui in the qml2 code to propagate keyboard/mouse events
14:36 #navit: < kazer> jandegr: have you seen the CI PR review i sent a couple of days ago?
14:37 #navit: < jandegr> yes
14:38 #navit: < jandegr> nice, but those fixed coords will reduce its usefullness
14:38 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
14:39 #navit: < zintor> sorry for in/out...but my wlan is not good at the moment :(
14:42 #navit: < kazer> jandegr: it was just to get the ball rolling. We could switch to simulated keypresses instead
14:42 #navit: < kazer> zintor: that's ok :)
14:42 #navit: < jandegr> ok
14:43 #navit: < kazer> jandegr: would you mind putting something in the CR? I'd like to showcase a better collaboration workflow (code in branch, ask for CR, merge PR)
14:43 #navit: < kazer> it could even just be a CR validation
14:43 #navit: < jandegr> what is cr ??
14:43 #navit: < kazer> code review
14:43 #navit: < jandegr> what do you want to review ?
14:44 #navit: < kazer> https://github.com/navit-gps/navit/pull/197 should show "review requested". you can comment inline, comment in the pr, or just validate the CR
14:47 #navit: < jandegr> is it the ""Add your review"" button ???
14:48 #navit: < jandegr> so many options to choose from :)
14:54 #navit: < jandegr> done, your turn again :)
14:54 #navit: < kazer> thanks :)
14:55 #navit: < kazer> i wasn't seeing the reviewers options, as i can't self review :)
15:00 -!- Basilic__ [~Basilic@228-221-190-109.dsl.ovh.fr] has joined #navit
15:03 -!- Basilic_ [~Basilic@228-221-190-109.dsl.ovh.fr] has quit [Ping timeout: 258 seconds]
15:06 #navit: < zintor> why do I get following message, then I use the "nuc-layout"?
15:06 #navit: < zintor> error:navit:graphics_image_new_scaled_rotated:No image for '/usr/share/navit/navit-nuc-layout/zoom_in_64_64.png'
15:06 #navit: < zintor> I could copy the files
15:07 #navit: < zintor> is ${NAVIT_SHAREDIR} not set properly?
15:07 -!- jandegr [5bb61abf@gateway/web/freenode/ip.91.182.26.191] has quit [Quit: Page closed]
15:13 #navit: < zintor> files copied ;) now it needs some tweaking :)
15:30 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has quit [Ping timeout: 272 seconds]
15:30 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
15:33 #navit: < kazer> zintor: please share any feedback about it, it's always useful!
15:36 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 248 seconds]
15:36 -!- zintor1 [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
15:36 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
15:36 #navit: < zintor1> and I am not able to do anything. zoom or pan is not possible
15:36 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has quit [Ping timeout: 258 seconds]
16:00 #navit: < zintor1> I will try some more tomorrow
16:08 #navit: < zintor1> cya all
16:08 -!- zintor1 [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has quit [Quit: Leaving.]
16:33 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
16:44 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has left #navit []
19:33 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
19:57 -!- Horwitz [~mich1@p200300800E04D300022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
20:11 -!- Horwitz [mich1@baldrian.franken.de] has joined #navit
20:11 -!- mode/#navit [+o Horwitz] by ChanServ
--- Log closed Sat Jan 07 00:00:57 2017