--- Log opened Tue Sep 26 00:00:57 2017
00:39 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n
00:39 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed
00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
00:57 -!- pmckinley [~Peter_McK@88.110.218.124] has left #navit []
02:56 -!- noradtux [~noradtux@2a02:2028:86f:3901:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 252 seconds]
03:09 -!- noradtux [~noradtux@port-54865.pppoe.wtnet.de] has joined #navit
05:30 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
05:31 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Remote host closed the connection]
05:32 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:28 -!- naggety [512f18cf@gateway/web/freenode/ip.81.47.24.207] has joined #navit
08:30 #navit: < naggety> Hi jkoan
08:31 #navit: < jkoan> hi naggety :D
08:32 #navit: < naggety> I have taken a look to TMC thing
08:32 #navit: < jkoan> you know that i am the only person which could be online at this time :D
08:32 #navit: < jkoan> and what do you think?
08:33 #navit: < naggety> My first idea is that the relationship between TMC points and map points should be done by maptool
08:33 #navit: < naggety> yes, I know, but it's also because my message is for you xD
08:34 #navit: < jkoan> if we get thishendelt with the maptool that would be nice, but the question would be why we do not push this work back to OSM so other projects could yuse it also
08:35 #navit: < naggety> As I can read, a "point" of the TMC tables could be something like: between exit 3 and exit 4 of E-15 motorway
08:35 #navit: < jkoan> * this handelt
08:35 #navit: < jkoan> yes, more or less, it has a type, a name and a position
08:36 #navit: < jkoan> but the question is how accurat the position is
08:36 #navit: < naggety> Not accurate
08:36 #navit: < jkoan> sorry for spelling i dont have a spell checker installed where i am
08:36 #navit: < naggety> In fact, the position in a format like coordinates or similar are not given
08:37 #navit: < naggety> I think the exact position have to be selected by us, manually
08:37 #navit: < jkoan> inside the locationcode table i have coordinates (germany)
08:39 #navit: < naggety> But for example, just a question: an exit of a motorway exist now as a point in the map?
08:40 #navit: < jkoan> Right now inside osm there are a few points from the location code table, yes. But definitely not all.
08:42 #navit: < jkoan> The best for us would be that every location code would be mapped inside osm that would be the easiest way for us. Probably xenos1984 could help with that because he has already done a lot of work some years ago at osm
08:50 #navit: < naggety> Then I am just like yesterday: I would need to learn more about OSM data edition
08:50 #navit: < jkoan> But if we think that we theoretically have the mapping from the location code to the segment inside navit, we need to add a a plugin type for traffic plugins (so we can add others later) and the routing must take care of what those plugins say. Also we must provide a trigger to let the tmc plugin say the routing that new data is available and a rerouting could be necessary.
08:53 #navit: < jkoan> Currently I am working on the other front (receiveing the data and process them so that the future plugin could receive them)
09:07 #navit: < naggety> One question: where can I consult the javascript available variables and functions of internal_gui? I didn't find it in the wiki
09:08 #navit: < naggety> I want to make that the user choices such as 3D/2D view persist after closing navit for the next time
09:12 #navit: < jkoan> do you men this one https://wiki.navit-project.org/index.php/OSD#Commands ?
09:13 #navit: < jkoan> kazer: i think doxygen/ woud be good here :D we should work on it
09:18 #navit: < naggety> Almost, in this case: https://wiki.navit-project.org/index.php/OSD#GUI_commands
09:18 #navit: < naggety> but this seems not to be very complete
09:19 #navit: < jkoan> yes this i a really big prolemof navit, it is able to do so much but its not well decmented
09:19 #navit: < jkoan> *problem
09:31 #navit: < naggety> I found them in navit/gui/internal/gui_internal_command.c
09:34 #navit: < jkoan> also in navit/navit.c alls functions beginning with navit_cmd probably
10:52 #navit: < jkoan> when i look at this link (zooming to Hannover in germany) i get big hopes: http://overpass-turbo.eu/?template=key-value-type&key=type&value=tmc:point&type=relation
11:44 #navit: < naggety> Finally I found it
11:44 #navit: < jkoan> what? the commands?
11:44 #navit: < naggety> to save a config it's with command 'set'
11:45 #navit: < jkoan> oh :D
11:45 #navit: < naggety> onclick='navit.pitch=pitch;set("navit.pitch=*", pitch);redraw_map();back_to_map()'
11:46 #navit: < naggety> what do we have to see in your link
11:46 #navit: < jkoan> looks correct ^^ (i had even no idea where to search
11:46 #navit: < naggety> i zoomed to hannover but I see nothing special
11:47 #navit: < jkoan> click on runon the upper left side
11:47 -!- ara [6dc07be0@gateway/web/freenode/ip.109.192.123.224] has joined #navit
11:47 #navit: < jkoan> hi ara
11:47 -!- ara is now known as Guest60774
11:48 #navit: < naggety> received empty database
11:48 #navit: < naggety> that's what I get
11:48 #navit: < jkoan> zoom a little bit out and see that the "A2" is inside the view
11:48 #navit: < naggety> ah ok
11:49 #navit: < naggety> now I see
11:49 -!- Guest60774 [6dc07be0@gateway/web/freenode/ip.109.192.123.224] has left #navit []
11:50 #navit: < jkoan> this is exactly what navit can (probably) see if we take progress on tmc
13:11 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
14:31 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
14:32 -!- naggety [512f18cf@gateway/web/freenode/ip.81.47.24.207] has quit [Quit: Page closed]
14:32 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Client Quit]
14:57 #navit: < jkoan> Hi again all together
15:37 #navit: < youte> hi
15:45 #navit: < jkoan> Hi youte
15:45 #navit: < jkoan> What's up?
15:50 #navit: < youte> yes and u
16:20 #navit: <@KaZeR> hi there
16:20 #navit: < jkoan> Hi Kazer
16:22 #navit: <@KaZeR> 'sup guys?
16:22 #navit: <@KaZeR> i missed naggety again. it would be great if he could expand a bit our wiki with what he's learning
16:24 #navit: < jkoan> what do you think about pushing doxygen to the next level? :D
16:25 #navit: < youte> hello KaZeR
16:25 #navit: < youte> i have send a pm for you :D
16:26 #navit: < jkoan> KaZeR: you probably need a better irc client :D because the pn's
16:27 #navit: < youte> haha
16:28 #navit: < youte> xchat is cool :D
16:33 #navit: <@KaZeR> jkoan: all for it just let me know how we can help
16:33 #navit: <@KaZeR> jkoan: maybe i do :)
16:34 #navit: < jkoan> KaZeR: the first message refers to what?
16:35 #navit: <@KaZeR> doxygen
16:35 #navit: < jkoan> i have done some work today
16:40 #navit: <@KaZeR> on doxygen?
16:40 #navit: <@KaZeR> inline documentation improvements?
16:41 #navit: <@KaZeR> i did some work on upgrading doxygen a few months ago : https://github.com/navit-gps/navit/tree/doxygen
16:41 #navit: <@KaZeR> should finish that and push the result to the webservice server
16:41 #navit: < jkoan> yep inline doku
16:43 #navit: <@KaZeR> nice! thanks!
16:44 #navit: < jkoan> but not to much
17:03 #navit: <@KaZeR> small incremental improvements.. that's the best way to move forward :)
17:18 #navit: < jkoan> kazer do you know cloud 9 (ide)?
17:25 #navit: <@KaZeR> jkoan: i don't
17:49 #navit: < jkoan> KaZeR: do you have some minutes?
17:57 #navit: <@KaZeR> sure
17:58 #navit: < jkoan> https://preview.c9users.io/jkoan/navit-git/doc/html/index.html
17:59 #navit: < jkoan> i added some functions in navit core
18:01 #navit: <@KaZeR> sweet thanks!
18:01 #navit: <@KaZeR> you can just submit a PR, it'll be easier to review than browsing an actual doxygen site
18:01 #navit: < jkoan> https://github.com/navit-gps/navit/compare/trunk...jkoan:doxy
18:02 #navit: <@KaZeR> -/** -> +/* did you do that or is it your IDE?
18:04 #navit: < jkoan> i did that because i activated the java style autobrief because its more handy
18:05 #navit: < jkoan> real changes are in navit.c and osd/core/osd_core.c
18:07 #navit: <@KaZeR> ok. We probably don't want to commit this change that removes one '*' in 100 places :)
18:07 #navit: <@KaZeR> it makes the review really difficult
18:07 #navit: < jkoan> give me 5 mins ;)
18:08 #navit: <@KaZeR> sure :)
18:18 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
18:20 #navit: < jkoan> hi xenos1984
18:20 #navit: < jkoan> KaZeR: https://github.com/navit-gps/navit/compare/trunk...jkoan:doxygen better?
18:31 #navit: <@KaZeR> jkoan: much better. Found a small typo though : Add a new mepset to the navit instance
18:31 #navit: <@KaZeR> -> mapset
18:33 #navit: < jkoan> fixed
18:33 #navit: <@KaZeR> also i believe that having the return type and the function name on the same line does not match the K&R standard
18:33 #navit: <@KaZeR> style, not standard
18:33 #navit: <@KaZeR> https://wiki.navit-project.org/index.php/Programming_guidelines
18:52 #navit: < jkoan> oh okay, i thought it would be more modern to have it in the same line. but okay, i haven't see the guidlines :X
18:55 #navit: < jkoan> but one interesting thing: https://wiki.navit-project.org/index.php/Programming_guidelines#Classes.2FStructs.2FFunctions.2FMethods look here :D
19:21 #navit: < jkoan> KaZeR: lizenses, what do you think for a new project? (arduino firmware for tmc)
19:50 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Read error: Connection reset by peer]
19:53 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
19:55 #navit: <@KaZeR> ah, interesting example. I personally don't mind much if we use one or two lines, as long as we keep it consistent
19:55 #navit: < jkoan> agreed
19:56 #navit: <@KaZeR> i just did the test, and " indent --procnames-start-lines --k-and-r-style --indent-level 8" will put it on two lines. So we should probably keep it like that
19:56 #navit: < jkoan> okay
19:57 #navit: < jkoan> also in the new arduino firware? (separate repo)
19:57 #navit: <@KaZeR> regarding the license, i'd say that it's a bit up to you. I like the GPL v2, but if you don't care about getting contributions back you could use something like MIT too
19:58 #navit: <@KaZeR> if you are to define a coding policy for a project in another repo we have some leeway. I personally prefer 4 spaces instead of 8 for example
19:58 #navit: < jkoan> gpl v2 or v3? :X
19:59 #navit: <@KaZeR> https://copyleft.org/guide/comprehensive-gpl-guidech10.html#x13-620009.1
20:18 #navit: < jkoan> writing the firmware for the arduino is not as easy as i thought. i have most of the code ready, but its not good code which i want to push. the biggest problem is to make it subtable for other chips without big impact on the rds and tmc code :X but i will get it managed, but not today
20:21 #navit: <@KaZeR> in my experience, it's better to push suboptimal code rather than push nothing, because someone might help you :
20:21 #navit: <@KaZeR> :)
20:22 #navit: < jkoan> maybe next week
20:22 #navit: < jkoan> :-P
20:22 #navit: <@KaZeR> sure
20:24 #navit: < jkoan> KaZeR: do you also have a rds module at home?
20:25 #navit: < jkoan> or a fm module?
20:30 #navit: <@KaZeR> i have a fm module but it does not support rds
20:30 #navit: < jkoan> which one?
20:30 #navit: <@KaZeR> well.. i have a i2c fm module without rds, and a usb realtek based module that does support it
20:31 #navit: < jkoan> i am using the Si4703 and the eds is quiet good :D
20:34 #navit: <@KaZeR> yeah the si4703 looks like a great device. i have a tea5767
20:37 #navit: < jkoan> i have seen the doc tea5767 because i searched for other fm chips ^^ but unforchently you are right, no rds :(
20:38 #navit: < jkoan> *unfortunately
20:45 #navit: < jkoan> my si703 is from ebay so it was really cheap ;)
20:54 #navit: <@KaZeR> my tea5767 was from a friend's abandonned project so it was free :)
20:55 #navit: <@KaZeR> if i were to buy one, i'd go for the si4703 for sure. I might do it once i'll be ready to put the new setup in the car. RDS is handy
20:59 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Read error: No route to host]
21:26 #navit: <@KaZeR> jkoan: i see that you linked a pdf regarding TMC. I think that it would be best to host also a copy of it, while mentionning the source, in case the original website goes offline
21:28 #navit: < jkoan> I already saved the PDF file ;) but i don't want to upload it because I don't know it's legal
21:59 #navit: <@KaZeR> ok. usually it's not a problem to host a mirror unless it's explicitely forbidden
22:04 #navit: < jkoan> It's an iso standard and has a explicit copyright notice so I want to avoid it
22:08 #navit: <@KaZeR> sounds good
23:10 -!- Horwitz [~mich1@p200300800E753900022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
23:23 -!- Horwitz [~mich1@p200300800E717300022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:23 -!- mode/#navit [+o Horwitz] by ChanServ
--- Log closed Wed Sep 27 00:00:59 2017