--- Log opened Thu Jan 19 00:00:15 2017 01:13 -!- navit_ [59cb9018@gateway/web/freenode/ip.89.203.144.24] has joined #navit 01:13 -!- navit_ [59cb9018@gateway/web/freenode/ip.89.203.144.24] has quit [Client Quit] 01:30 -!- Jkoan2 [~jkoan@ip4d1412e1.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds] 01:31 -!- Jkoan2 [~jkoan@ip-109-45-2-201.web.vodafone.de] has joined #navit 01:36 -!- Jkoan2 [~jkoan@ip-109-45-2-201.web.vodafone.de] has quit [Client Quit] 01:40 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 02:45 -!- jjelen [jjelen@nat/redhat/x-ntjhvnevfgtgwhrr] has joined #navit 04:21 -!- Celelibi [celelibi@4.172.87.79.rev.sfr.net] has joined #navit 04:28 -!- ColdFyre [~lenny@c-71-231-174-131.hsd1.wa.comcast.net] has quit [Ping timeout: 245 seconds] 05:18 -!- jjelen [jjelen@nat/redhat/x-ntjhvnevfgtgwhrr] has quit [Ping timeout: 252 seconds] 05:48 -!- jjelen [jjelen@nat/redhat/x-moaykxzwspphivwf] has joined #navit 06:04 -!- jjelen [jjelen@nat/redhat/x-moaykxzwspphivwf] has quit [Ping timeout: 240 seconds] 06:53 -!- jjelen [jjelen@nat/redhat/x-lzgsrlbgeqfiavvv] has joined #navit 07:25 -!- jjelen [jjelen@nat/redhat/x-lzgsrlbgeqfiavvv] has quit [Ping timeout: 256 seconds] 11:29 -!- ColdFyre [~lenny@c-73-42-128-132.hsd1.wa.comcast.net] has joined #navit 12:05 -!- jkoan [~jan@ip4d1412e1.dynamic.kabel-deutschland.de] has joined #navit 12:05 #navit: < jkoan> hi @all 12:18 #navit: <@KaZeR> hi there 12:19 #navit: < jkoan> kazer, i dont have the permission to edit Main Page/news 12:25 #navit: <@KaZeR> let me see 12:26 #navit: <@KaZeR> weird, permissions says "Allow all users" 12:29 #navit: < jkoan> You do not have permission to edit this page, for the following reason: 12:29 #navit: < jkoan> The action you have requested is limited to users in the group: Users. 12:30 #navit: < jkoan> oh fail 12:31 #navit: < jkoan> the browser session was closed and dont have seen it 12:47 -!- jandegr [5742b121@gateway/web/freenode/ip.87.66.177.33] has joined #navit 12:50 #navit: <@KaZeR> haha :) 12:56 #navit: < jkoan> sorry for trouble 13:16 #navit: <@KaZeR> no worries :) 13:30 #navit: < jkoan> Better now? 13:30 #navit: < jkoan> http://wiki.navit-project.org/index.php/Configuration 13:42 #navit: <@KaZeR> oh just stumbled upon this : http://kenneth.belitzky.com/post/142960572276/generating-navit-configuration-files-via-templates 13:42 #navit: <@KaZeR> really cool 13:44 #navit: <@KaZeR> "Just remember to turn off 'save UTF8 byte mark' in Preferences or navit may complain very much on the first byte of the file." so that was probably what caused the scp issue 13:44 #navit: <@KaZeR> we should maybe address that in the code 13:44 #navit: <@KaZeR> thanks jkoan for taking the lead on this 13:46 -!- circleci-bot [~circleci-@ec2-54-237-30-252.compute-1.amazonaws.com] has joined #navit 13:46 #navit: < circleci-bot> Failed: pgrandin's build (#1566; retry by pgrandin) in navit-gps/navit (add_linux_tests) -- https://circleci.com/gh/navit-gps/navit/1566?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc 13:46 -!- circleci-bot [~circleci-@ec2-54-237-30-252.compute-1.amazonaws.com] has quit [Client Quit] 13:50 #navit: < jandegr> kazer the thing you found on github for config is not cool :( 13:52 #navit: <@KaZeR> jandegr: why? 13:52 #navit: < jkoan> i want to ask the same :D 13:52 #navit: < jandegr> forking navit.xml even if it is in the form of a template is really bad 13:53 #navit: <@KaZeR> i agree that instead of a pure template it's better to leverage xml to do the changes, but i like the fact that he took time to build a generator for layouts 13:53 #navit: < jandegr> hence navit uses xslt on one single source instance 13:53 #navit: < jandegr> if smth is changed in the mother.xml then it propagates into all the res 13:53 #navit: < jandegr> all the rest 13:54 #navit: < jandegr> or isolate yourself on an island by forking xml and soon have an outdated thing 13:55 #navit: < jandegr> have seen it happen over and over 13:57 #navit: <@KaZeR> yes, but if we change this tool to generate layouts only, it's just a matter of using xi:include afterwards 13:59 #navit: < jandegr> not true 14:00 #navit: <@KaZeR> why? 14:00 #navit: < jandegr> says the board :) 14:00 #navit: <@KaZeR> haha 14:01 #navit: < jandegr> you came up with that :) 14:01 #navit: < jandegr> long answer : you pov implies layouts are static, but all of Navit is so dynamic 14:02 #navit: <@KaZeR> it is dynamic in the sense that you can change everything. But you have to change the elements yourself 14:03 #navit: < jandegr> it is dynamic in as it is still actively worked on .... 14:05 #navit: < jandegr> the board took another look at xml and they still oppose.. 14:05 #navit: < jandegr> from time to time some poi is added in maptool, an icon added for it and layout modified, 14:06 #navit: < jandegr> you're missing out on all of it with your forked xml's 14:06 #navit: < jandegr> I have seen plenty of badly outdated (forked) xml's 14:17 #navit: <@KaZeR> yes, and what we have in the wiki is a good example 14:17 #navit: <@KaZeR> i'm not saying that forked xml is good, i'm saying that the layout generator is good 14:19 #navit: < jandegr> and in what way is it better than xslt ? 14:21 #navit: <@KaZeR> because someone took the time to write a layout generator 14:21 #navit: <@KaZeR> we don't have that. We could, it wouln't be hard. But we don't have it 14:32 #navit: <@KaZeR> this is also why i am trying to get people to put their layouts or osd in github repo, to make it easier to test/distribute/reuse 14:32 -!- circleci-bot [~circleci-@ec2-54-166-224-18.compute-1.amazonaws.com] has joined #navit 14:32 #navit: < circleci-bot> Failed: pgrandin's build (#1567; ssh by pgrandin) in navit-gps/navit (add_linux_tests) -- https://circleci.com/gh/navit-gps/navit/1567?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc 14:32 -!- circleci-bot [~circleci-@ec2-54-166-224-18.compute-1.amazonaws.com] has quit [Client Quit] 14:39 #navit: < jkoan> kazer: what about an repo from navit only for layouts? each directory could be a layout for example. And on the wiki we could make an gallery. if we click on the layout picture we get the github dir with readme how to install. I can take the wiki path 14:44 #navit: <@KaZeR> jkoan: yep this is actually close to what i had in mind 14:44 #navit: <@KaZeR> we could use git submodules to group them 14:45 #navit: < jkoan> also the OSD pages XML examples are collor highlited ;) (does not seems so, but this is so much...) 14:46 #navit: < jkoan> submodules are an good idea because than every user can have its repo as it is 14:46 #navit: <@KaZeR> i think that we should really move the osd code outside of the wiki. Often it's broken, or a path is hardcoded. Would you like to help moving them to github ? 14:46 #navit: < jkoan> the negative point is that a user can deleate it 14:47 #navit: < jkoan> i ment this page http://wiki.navit-project.org/index.php/OSD mainly this sould work 14:47 #navit: < jkoan> but for full configs of course 14:48 #navit: <@KaZeR> oh, i was talking about http://wiki.navit-project.org/index.php/OSD_Layouts 14:50 #navit: < jkoan> another point is probably that we sould make something like navit.d for layouts so that the parts that changes on every device are in navit.xml like now and the visual things are in invidual config files in navit.d/xyz.xml 14:50 #navit: < jkoan> what do you thing about this? 14:50 #navit: < jkoan> OSD_Layouts is a little bit messy... 14:51 #navit: <@KaZeR> i think it's important to clarify layouts (=map layouts) and osd layouts (=osd). Both are layouts, but usually when talking about layouts we talk about map layouts 14:52 #navit: <@KaZeR> osd layouts are linked to the screen resolution. map layouts are mostly about design and device performance (so if your device is slow you can just disable items) 14:52 #navit: < jkoan> what about Overlay Gui (=OSD) and Map Design (=map layout) 14:53 -!- jandegr [5742b121@gateway/web/freenode/ip.87.66.177.33] has quit [Quit: Page closed] 14:55 #navit: <@KaZeR> actually the names that we use currently are linked to the name of the items in the xml :) 14:56 #navit: < jkoan> yes okay :D 14:56 #navit: <@KaZeR> overlay gui wouldn't be great, because it is actually not gui related ( it would work the same way on internal, qt, or gtk) 14:57 #navit: < jkoan> okay, i see your point :X 14:57 #navit: <@KaZeR> i see that we still have references to svn in the wiki. This is outdated so whenever you find one, please change it to git instead 14:58 #navit: < jkoan> sometimes expachely at building this is not so easy 15:00 #navit: <@KaZeR> afk a moment 15:00 #navit: < jkoan> does we have official debian packages and who is the maintainer for ubuntu/debian? 15:00 #navit: < jkoan> okay, i will wait :D 15:20 #navit: <@KaZeR> i believe that pini is the maintainer of the navit package : https://qa.debian.org/developer.php?login=pini%40debian.org 15:20 #navit: <@KaZeR> he usually hangs in this irc channel 15:21 #navit: < jkoan> are the debian builds up to aour last release? 15:21 #navit: < jkoan> *our 15:33 #navit: <@KaZeR> i don't think so, if i recall correclty they are using a somewhat old release 15:36 #navit: < jkoan> what do you think is the most importent point of the wiki (for my next scope) 15:51 #navit: <@KaZeR> i think it's important to make it easier for new users 15:51 #navit: <@KaZeR> navit is so configurable that it's easy to get lost at the beginning 15:51 #navit: < jkoan> so beter instruktions how to start? 15:51 #navit: <@KaZeR> map download (where to put them) and basic config 15:51 #navit: <@KaZeR> yep probably 15:51 #navit: < jkoan> so we sould write an new howto? 15:52 #navit: <@KaZeR> maybe. or revamp the current one 15:52 #navit: <@KaZeR> it's especially useful that you are the one doing it since you are also new to navit :) 15:53 #navit: < jkoan> wheres the old one? 16:01 #navit: <@KaZeR> i think that http://wiki.navit-project.org/index.php/Basic_configuration would be the current one 16:19 #navit: <@KaZeR> maybe we should make that page more obvious 16:29 #navit: < jkoan> i think i will make an howto page or caregory 16:38 #navit: <@KaZeR> sounds good! 18:03 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 19:42 -!- Horwitz [~mich1@p200300800E022500022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds] 19:55 -!- Horwitz [~mich1@p200300800E031500022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 19:55 -!- mode/#navit [+o Horwitz] by ChanServ 22:03 -!- noradtux [~noradtux@port-5042.pppoe.wtnet.de] has quit [Ping timeout: 264 seconds] 22:08 -!- noradtux [~noradtux@port-57027.pppoe.wtnet.de] has joined #navit 22:38 -!- KaZeR [~kazer@2601:643:8104:ba60:eea8:6bff:fef8:449] has quit [Ping timeout: 245 seconds] 22:49 -!- circleci-bot [~circleci-@ec2-54-159-52-140.compute-1.amazonaws.com] has joined #navit 22:49 #navit: < circleci-bot> Failed: pgrandin's build (#1568; push) in navit-gps/navit (linux-network-info) -- https://circleci.com/gh/navit-gps/navit/1568?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc 22:49 -!- circleci-bot [~circleci-@ec2-54-159-52-140.compute-1.amazonaws.com] has quit [Client Quit] 22:49 -!- KaZeR [~kazer@2601:643:8104:ba60:eea8:6bff:fef8:449] has joined #navit 23:07 -!- circleci-bot [~circleci-@ec2-54-205-179-67.compute-1.amazonaws.com] has joined #navit 23:07 #navit: < circleci-bot> Failed: pgrandin's build (#1569; push) in navit-gps/navit (add_linux_tests) -- https://circleci.com/gh/navit-gps/navit/1569?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc 23:07 -!- circleci-bot [~circleci-@ec2-54-205-179-67.compute-1.amazonaws.com] has quit [Client Quit] --- Log closed Fri Jan 20 00:00:16 2017