--- Log opened Sat Jan 12 00:00:39 2019
00:05 -!- xenos1984 [~xenos1984@b158-0638-8ee6-7806-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Quit: Leaving.]
00:40 #navit: <+ilovekiruna> jkoan: then we could also use the example from here and try to adjust it for our needs: https://github.com/email2vimalraj/appium-stf-example
00:41 #navit: <+ilovekiruna> and: https://github.com/uds-se/stf/wiki/%5Ben%5D-Farm-Testing
05:07 -!- xenos1984 [~xenos1984@aba8-7853-405c-197a-8780-87e7-07d0-2001.dyn.estpak.ee] has joined #navit
05:07 -!- mode/#navit [+v xenos1984] by ChanServ
08:00 -!- tryagain [~quassel@217.107.194.47] has joined #navit
08:00 -!- mode/#navit [+o tryagain] by ChanServ
08:01 #navit: <@tryagain> hi all
08:03 #navit: <@tryagain> mvglasow jkoan regarding f-droid builds. 3 years ago I have managed to test a few versions of navit there using gitlab CI.
08:04 #navit: <@tryagain> I have decided to use gitlab CI beacuse f-droud was using it. so we have the same environments.
08:06 #navit: <@tryagain> in my repo https://gitlab.com/tryagain/Navit-fdroid there's https://gitlab.com/tryagain/Navit-fdroid/tree/no-makebuildserver branch, which was aused to test new navit versions build
08:08 #navit: <@tryagain> after testing the new version, I was adding a PR from my clone of fdroid-data
08:08 #navit: <@tryagain> sample commit https://gitlab.com/tryagain/fdroiddata/commit/57a547531d683be752735301b70b6a2e6d607b74
08:10 #navit: <@tryagain> I was thinking to add commits to my clone of fdroid-data and Navit-Fdroid automatically, but never  done that.
08:12 #navit: <@tryagain> Since then, navit has changed version numbering and now we have tag based versions, so it indeed should be possible to fetch new version information automatically.
08:14 #navit: <@tryagain> But maybe my my yml file from https://gitlab.com/tryagain/Navit-fdroid could help you in tuning CI for f-droid.
08:29 -!- tryagain [~quassel@217.107.194.47] has quit [Remote host closed the connection]
13:27 -!- ilovekiruna [~ilovekiru@2a02:8108:d00:110:d96c:93f4:8be1:474b] has quit [Ping timeout: 252 seconds]
17:02 -!- youte [~youte@95-210-222-17.ip.skylogicnet.com] has joined #navit
17:02 -!- mode/#navit [+v youte] by ChanServ
17:02 #navit: <+youte> hi
19:03 -!- odo2063 [~odo2063@unaffiliated/odo2063] has joined #navit
19:03 #navit: < odo2063> Hi Folks!
19:04 -!- mvglasow [~mvglasow@dslb-188-104-108-118.188.104.pools.vodafone-ip.de] has joined #navit
19:07 #navit: < odo2063> i have installed navit to a NavGear Tourmate N4. now i tried to change the layout but it doens't start anymore. might some would try to help me?
19:09 #navit: < mvglasow> tryagain thanks four your advice, I have put together a new build recipe for navit here:
19:09 #navit: < mvglasow> https://gitlab.com/mvglasow/fdroiddata/commit/40001b90272f466e08e81467ed1c9eb0adfe913f
19:10 #navit: < mvglasow> update checking has been implemented (copied from jkoan, he says it works, I haven't been able to test it yet)
19:11 #navit: < mvglasow> there are two open points left: first, the FIXME comments in the build recipe
19:11 #navit: < mvglasow> we currently don't have a released version for which this recipe will work
19:11 #navit: < mvglasow> but need to specify that this is the recipe for the next version
19:13 #navit: < mvglasow> also I'n mot sure if I need to change the Current Version/Current Version Code fields
19:13 #navit: < mvglasow> secondly, I'd like to test the F-Droid build specifically
19:13 #navit: < mvglasow> the shell script for the actual build works on CI as well as on my local workstation
19:14 #navit: < mvglasow> I'd just like to make sure it runs on the F-Droid build server as well
19:14 #navit: < mvglasow> tryagain any experience with CI for the fdroiddata repo?
19:15 #navit: < mvglasow> I forked mine before they had CI at all, not sure what I need to do in order to set it up
19:15 #navit: < mvglasow> not even which CI service to use, Gitlab offers several ones
20:06 -!- zintor [55d84f3f@gateway/web/freenode/ip.85.216.79.63] has joined #navit
20:07 #navit: < zintor> odo2063: do you have still problems with your layout?
20:07 #navit: < zintor> it could be, that you miss to close a xml tag
20:08 #navit: < odo2063> zintor,  i tried to comment out multiple lines with comments within...
20:09 #navit: < odo2063> zintor,  atm i have trouble with the backgroundcollor of some elements.... http://wiki.navit-project.org/index.php/OSD_Layouts#Layout_for_Sony_nav-u92T
20:11 #navit: < zintor> well, if it starts again. that's a progress
20:15 #navit: < odo2063> atm i am working arround the background problem with inserting an image of pure black XD
20:18 #navit: < zintor> have fun with all the possibilities of navit!
20:18 #navit: < zintor> have to go
20:18 #navit: < zintor> cya all
20:18 -!- zintor [55d84f3f@gateway/web/freenode/ip.85.216.79.63] has quit [Quit: Page closed]
20:23 #navit: < odo2063> can the area of the main map be edited somehow?
21:22 #navit: < mvglasow> odo2063 what do you mean by that? the position on the main map that is shown on startup?
21:22 #navit: < mvglasow> this is saved in a file (I think center.txt) in the data directory
21:23 #navit: < mvglasow> usually on startup Navit should show the last part of the map yu viewed
21:23 #navit: < mvglasow> for the first launch, the position is taken from navit.xml
21:23 #navit: < mvglasow> zoom is also set in navit.xml
22:12 #navit: < odo2063> mvglasow,  i dont want the map to fill the whole screen...just a part of it
22:13 #navit: < mvglasow> what OS does your device run?
22:14 #navit: < odo2063> winCE 6
22:14 #navit: < mvglasow> not sure this is possible at all
22:14 #navit: < mvglasow> when Navit runs in a window, the map takes up the entire window
22:15 #navit: < mvglasow> except for some real estate claimes by the GUI (e.g. menu, toolbars, status bar for the GTK GUI)
22:15 #navit: < mvglasow> in fullscreen mode, it takes up the whole screen
22:15 #navit: < mvglasow> if you have OSD elements enabled, they will display on top of the map
22:17 #navit: < mvglasow> not sure about WinCE6 and windows, it's been ages since I last used WinCE
22:17 #navit: < mvglasow> but you'd have to get Navit to run in a window rather than in fullscreen mode
22:18 #navit: < odo2063> https://pastebin.com/YxJhPQub ,,,help that?
22:26 #navit: < mvglasow> that's your navit.xml, I see you're using the internal GUI (which is the default)
22:26 #navit: < mvglasow> tap the map view to get the menu, Settings > Display > Fullscreen allows you to toggle between window and fullscreen mode
22:27 #navit: < mvglasow> on WinCE 5 (at least on a pocket PC) this should show or hide the taskbar
22:27 #navit: < mvglasow> if you're seeing the taskbar, you are in wondow mode
22:28 #navit: < mvglasow> no idea, however, if WinCE 6 (or the flavor of it that you are using) supports windows (i.e. multiple apps on the screen)
22:28 #navit: < mvglasow> that would really be up to the operating system
22:28 #navit: < odo2063> it doesn't change anything...there is no taskbar on this system...just some kind of carentertainment ui
22:29 #navit: < mvglasow> if you say you don't want the map to occupy the whole screen, what would you use the remaining screen space for? other apps?
22:30 #navit: < odo2063> http://wiki.navit-project.org/index.php/OSD_Layouts#Layout_for_Sony_nav-u92T
22:31 #navit: < odo2063> infos for navigating
22:32 #navit: < mvglasow> now I get what you mean
22:32 #navit: < mvglasow> these are OSD elements, and they are in fact displayed on top of the map
22:33 #navit: < odo2063> and a few map elemnts appear in the info bar...current location etc.
22:34 #navit: < mvglasow> (they can be made semitransparent so the map will still shine through)
22:34 #navit: < mvglasow> the link you sent me has the XML definitions for the OSD elements just underneath the picture
22:35 #navit: < mvglasow> add these to your navit.xml and you should get the information
22:35 #navit: < mvglasow> look for other <osd> tags in your navit.xml and paste the data there
22:35 #navit: < mvglasow> you might need to adapt dimensions, depending on the size of your screen
22:35 #navit: < odo2063> the background settings dont work...had to workaround with a blackpicture behind the infos
22:36 #navit: < odo2063> screensize fits exactly
22:36 #navit: < mvglasow> background settings... you mean background_color?
22:36 #navit: < odo2063> yes
22:37 #navit: < mvglasow> might be a bug in the WinCE build, I use Navit on Android and Linux (for testing), and there background color works
22:37 #navit: < mvglasow> maybe jkoan can help, afaik he uses WinCE
23:17 -!- xenos1984 [~xenos1984@aba8-7853-405c-197a-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Quit: Leaving.]
--- Log closed Sun Jan 13 00:00:41 2019