--- Log opened Tue Apr 12 00:00:20 2016
02:22 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
02:23 -!- alpha [~alpha@p5DD293E7.dip0.t-ipconnect.de] has joined #navit
02:23 -!- alpha is now known as Guest51992
02:26 -!- Guest51992 [~alpha@p5DD293E7.dip0.t-ipconnect.de] has quit [Client Quit]
02:36 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:dd6:b3df:21d9:94aa] has joined #navit
02:53 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Quit: Page closed]
02:54 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
03:09 -!- jjelen_ [jjelen@nat/redhat/x-bukfhpdgunrdjubz] has joined #navit
04:18 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #navit
05:05 -!- ColdFyre [~lenny@c-71-231-174-131.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds]
05:06 -!- ColdFyre [~lenny@c-71-231-174-131.hsd1.wa.comcast.net] has joined #navit
05:22 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:dd6:b3df:21d9:94aa] has quit [Quit: Leaving.]
05:25 -!- xenos1984 [~xenos1984@utpublic.net.ut.ee] has joined #navit
05:34 -!- dacro [5ec63ecc@gateway/web/freenode/ip.94.198.62.204] has joined #navit
05:35 #navit: < dacro> Hi. How can I toggle the isometric view by configuration with the navit.xml?
06:32 -!- dacro [5ec63ecc@gateway/web/freenode/ip.94.198.62.204] has quit [Ping timeout: 250 seconds]
06:39 -!- dacro [5ec63ecc@gateway/web/freenode/ip.94.198.62.204] has joined #navit
06:46 -!- juse [~juse@fow4.kyla.fi] has joined #navit
06:53 -!- robertp [d9f3f0ac@gateway/web/freenode/ip.217.243.240.172] has joined #navit
06:54 #navit: < robertp> dacro, what do you mean with isometric view?
06:56 #navit: < dacro> I mean this view: http://wiki.navit-project.org/index.php/File:Mineque_OSD_Layout_02.jpg
06:58 #navit: < robertp> Just add a pitch="30" to the <navit> tag in navit.xml.
06:58 #navit: < robertp> http://wiki.navit-project.org/index.php/Configuration/Full_list_of_options#navit
07:00 #navit: < dacro> I try it. Thanks!
07:03 #navit: < robertp> depending on your screen size you might want to adjust the 30 to another value
07:10 #navit: < dacro> yes, it's working! thank you!
07:10 #navit: < dacro> I tried before with a too small value, that's why I thought it's not working :)
07:25 -!- xenos1984 [~xenos1984@utpublic.net.ut.ee] has quit [Ping timeout: 276 seconds]
07:50 -!- alex_123984 [~alexhell0@178.70.89.80] has joined #navit
07:51 -!- alexhell0xbf_4 [~alexhell1@178.70.89.80] has quit [Ping timeout: 276 seconds]
10:57 -!- jjelen_ [jjelen@nat/redhat/x-bukfhpdgunrdjubz] has quit [Ping timeout: 248 seconds]
11:09 -!- jjelen_ [jjelen@nat/redhat/x-lwdcnhfjmgaymfon] has joined #navit
11:10 -!- alex_123984 [~alexhell0@178.70.89.80] has quit [Ping timeout: 276 seconds]
11:14 -!- xenos1984 [~xenos1984@118-166-191-90.dyn.estpak.ee] has joined #navit
11:31 -!- xenos1984 [~xenos1984@118-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
11:57 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 250 seconds]
12:37 -!- jjelen_ [jjelen@nat/redhat/x-lwdcnhfjmgaymfon] has quit [Ping timeout: 264 seconds]
12:47 -!- dacro [5ec63ecc@gateway/web/freenode/ip.94.198.62.204] has quit [Quit: Page closed]
12:49 #navit: <@kazer> hi there
13:00 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Ex-Chat]
13:32 -!- robertp_ [5cd9af0d@gateway/web/freenode/ip.92.217.175.13] has joined #navit
13:35 #navit: < robertp_> hi
13:42 #navit: <@kazer> hi robertp_
13:42 #navit: < robertp_> whats up, kazer?
13:43 #navit: <@kazer> not much. have been a bit busy on other topics lately, but still want to get qt5 started :)
13:43 #navit: <@kazer> and you?
13:44 #navit: < robertp_> fighting with CAN-Bus at the moment. And may I remind my attribute question? :D
13:55 #navit: <@kazer> let me scroll up :)
13:55 #navit: <@kazer> so you want to access audio.playing or audio.shuffle or audio.repeat
13:56 #navit: < robertp_> to access those attrs i'd need to define or create them.
13:56 #navit: <@kazer> correct. something like https://github.com/navit-gps/navit/blob/trunk/navit/attr_def.h#L344
13:57 #navit: < robertp_> Since I asked a lot I would be fine if someone explains how it works
13:57 #navit: <@kazer> beware, you need to add attributes to the end of their blocks to avoid breaking maps
13:57 #navit: <@kazer> sure. where are you at right now ?
13:57 #navit: <@kazer> (and really sorry that you had to ask a lot :( )
13:57 #navit: < robertp_> I am very patient. Don't worry.
13:58 #navit: < robertp_> I am at the beginning. I know, we can Attrs that are acessable through navit.xml to make the plugin configurable
13:59 #navit: < robertp_> I need to know, how the attrs - since we just can put them into attr_def.h - are linked to each other.
14:00 #navit: < robertp_> In your first approach fot the audio plugin there was an "active" attr, which cant be used for some reason.
14:01 #navit: < robertp_> I believe that is the way i need to go for but there my knowledge - nah, its no knowlegde - end
14:03 #navit: <@kazer> ok here's an example : https://github.com/pgrandin/navit/blob/trunk/navit/attr_def.h#L399-L401 notice that they were added right before the end of their block  (ATTR2(0x0003ffff,type_string_end) )
14:04 #navit: < robertp_> yes.
14:05 #navit: <@kazer> they you can access the attribute from the code using something like this : https://github.com/pgrandin/navit/blob/trunk/navit/spotify.c#L378
14:05 #navit: <@kazer> is this helping ?
14:05 #navit: < robertp_> No. That is information I already have. :(
14:06 #navit: < robertp_> I need it the other way around.
14:06 #navit: <@kazer> ok. where are you stuck then ?
14:06 #navit: <@kazer> what are you trying to do exatcly?
14:06 #navit: <@kazer> damn i can't type today
14:07 #navit: < robertp_> Try to use your finger tips, not your nose.
14:08 #navit: < robertp_> Imagine there was an OSD button - in a galaxy far, far away.
14:08 #navit: < robertp_> This button is intended to be used with a powerful, magic audio plugin.
14:10 #navit: < robertp_> This button should start or stop playback and depending on the status of the magic plugin have a triangle-shaped or a double rectangel-shaped icon
14:10 #navit: < robertp_> For some other OSD elements in the Kings Family, the access through attributes is already possible.
14:11 #navit: < robertp_> For example Lady OSD_text_type
14:12 #navit: < robertp_> She can have a value depending on the status of its tracking attribute - its not really her attr. But she would claim it, if she could.
14:14 #navit: < robertp_> She can have a meaningful text like this "Hauptstraße S100" from label="${tracking.item.street_name} ${tracking.item.street_name_systematic}"
14:15 #navit: < robertp_> My approach is to use this kind of attribute for the audio plugin as audio.playing (and audio.repeat and audio.shuffle) because the button icons HAVE TO change if the status changes.
14:16 #navit: < robertp_> I would realize this with osd_configuration, IF I COULD GET THE F******* STATE.
14:17 #navit: < robertp_> *fonderwul ;)
14:20 #navit: <@kazer> haha
14:24 #navit: <@kazer> the thing is that tracking might be a specific beast, because we have a navit_get_tracking() function
14:25 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 260 seconds]
14:25 #navit: <@kazer> mmm i don't have an answer on top of my head for your question. but give me 30 minutes and i'll try to hack a POC plugin that defines an attribute, an osd, and has the osd reflect the attribute change
14:28 #navit: < robertp_> Might this https://github.com/pgrandin/navit/blob/trunk/navit/track.c#L334 be the one to interface attrs and code?
14:29 #navit: <@kazer> yep
14:30 #navit: <@kazer> is this code helping you?
14:31 #navit: < robertp_> Ok. then I can play around with this. But where does navit know which attr is for configuration and which is for accessing through command?
14:33 #navit: <@kazer> iirc, it's the same. they are just attributes. attributes from configuration are populated from xml_config.c
14:33 #navit: <@kazer> a command will just update the state of an attribute
14:33 #navit: <@kazer> like the gps vehicule will update position-related attributes
14:34 #navit: < robertp_> ok.
14:34 #navit: < robertp_> so the wonderful, magic plugin has to change the attribute
14:36 #navit: <@kazer> it makes sense to have the plugin do the change rather than the osd component. the osd should only reflect the state, not the intended action. if your playback does not start for whatever reason, your audio plugin will know and can set the attribute accordingly
14:37 #navit: < robertp_> sure thats exactly what i want
14:38 #navit: < robertp_> What does the NAVIT_OBJECT on top of some structs do? https://github.com/pohlinkzei/navit/blob/trunk/navit/vehicle.c#L55-L76
14:42 -!- robertp_ [5cd9af0d@gateway/web/freenode/ip.92.217.175.13] has quit [Ping timeout: 250 seconds]
14:43 -!- robertp_ [584aaea8@gateway/web/freenode/ip.88.74.174.168] has joined #navit
14:49 -!- robertp_ [584aaea8@gateway/web/freenode/ip.88.74.174.168] has quit []
15:40 -!- alexhell0xbf [~alexhell0@178.70.86.161] has joined #navit
15:40 #navit: < alexhell0xbf> hi there
15:45 #navit: <@kazer> hey alexhell0xbf
15:48 -!- juse [~juse@fow4.kyla.fi] has quit [Quit: Nettalk6 - www.ntalk.de]
15:50 #navit: < alexhell0xbf> kazer i'm close to implement map daemon
15:50 #navit: < alexhell0xbf> i mean partially its made
15:51 #navit: < alexhell0xbf> i was quite busy to implement some misc stuff
15:51 #navit: < alexhell0xbf> a lot of small things ...
15:52 #navit: < alexhell0xbf> mostly about architecture, modules support and so on ...
15:54 #navit: < alexhell0xbf> but now it's quite flexible to add tile maps and other features later ...
16:14 -!- xenos1984 [~xenos1984@118-166-191-90.dyn.estpak.ee] has joined #navit
17:15 #navit: <@kazer> that's great alexhell0xbf :) can't wait to see it!
17:17 #navit: < alexhell0xbf> now i think what to do with there quite flexible stuff :)
17:18 #navit: < alexhell0xbf> btw, i don't spent any time for the client app ...
17:19 #navit: < alexhell0xbf> and it's based on my oss lib, it will require to have a talk with remote daemon
17:30 #navit: <@kazer> when do you think you can start sharing some code? i'd love to have a look
17:47 #navit: < alexhell0xbf> on this weekend
17:48 #navit: < alexhell0xbf> i guess to put some general stuff to my oss project and map daemon code somewhere else ... to show. i guess some general stuff for daemons and flexibility u will be able to see within few days
17:50 #navit: < alexhell0xbf> i gone deep ... and decide to make it flexible for many uses
17:51 #navit: < alexhell0xbf> i hope u have a look at sxmp examples - well, i was quite lazy to implement each function for map daemon in such kind, and i decide to create additional library to make it easy
17:52 #navit: < alexhell0xbf> i.e. you can configure your daemon ... channels, data (now we have map catalog and map itself, but later ...) and other things ...
17:52 #navit: < alexhell0xbf> uff , and i made it.
17:53 #navit: < alexhell0xbf> also, some misc stuff as a configuration values , variable groups ... and many small things.
17:53 #navit: < alexhell0xbf> for variables i made the following
17:54 #navit: < alexhell0xbf> in config file you can
17:54 #navit: < alexhell0xbf> (create-var-group 'global) - create a group
17:54 #navit: < alexhell0xbf> (var-set (global/modsoname ".libs/libmoddummy.so")) - add variable
17:54 #navit: < alexhell0xbf> also, for example tile functions may reside in some additional module
17:55 #navit: < alexhell0xbf> that's ok
17:55 #navit: < alexhell0xbf> i've made addition of there modules quite simple
17:55 #navit: < alexhell0xbf> (module-add 'dummy other) ;; here we will add the module
17:55 #navit: < alexhell0xbf> (module-set 'dummy (:prefix "dummy")(:pathname global/modsoname)) ;; configure the module
18:00 #navit: < alexhell0xbf> and it was too stupid to implement in C code stuff and other things for each data structure ... well it will be also configurable via config
18:00 #navit: < alexhell0xbf> (dm-define-object 'pem (:acc 'access-rights)(:pemid 'u64)(:attr 'u8)(:csid 'u32)
18:00 #navit: < alexhell0xbf>                   (:filename 'cstr 256))
18:00 #navit: < alexhell0xbf> for files ...
18:01 #navit: < alexhell0xbf> sorry, but i was unable to stop this :) now i'm able to implement map daemon faster. i'm lazy yes :)
18:02 #navit: < alexhell0xbf> stay tuned ... few days and u will see all this stuff , and few days also - map daemon will be ready, and i hope i will need only one week to get client running
18:08 #navit: < alexhell0xbf> but i can't promise , because of my limited spare time
18:16 #navit: < alexhell0xbf> kazer i have a last question for now - is it possible to make a PR with map daemon code ? if so - how, i mean this is not part of navit application, but part of the navit project ...
18:58 #navit: <@kazer> yeah, we definitely welcome PR. Actually this should probably go in a new repository in the same org. I'll create it.
18:59 #navit: <@kazer> since it looks like you did most of the work i also can make you a member of the team for this repo directly. even if for good practices, we should code in branch or forks and only merge via PR to have someone else review the code
19:18 #navit: < alexhell0xbf> it will be nice if u will provide access to the repo directly - i will able to create a special branch in git and work there ...
19:20 -!- xenos1984 [~xenos1984@118-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
19:26 #navit: <@kazer> sure. what's your github handle?
19:31 #navit: < alexhell0xbf> not using github yet, i will register and give you my data
19:32 #navit: < alexhell0xbf> i decide to put the general stuff ti my oss project, map daemon will use it, map daemon itself on github ... wait ...
19:35 #navit: < alexhell0xbf> foreverafter on github it's me
19:37 #navit: <@kazer> you've been invited
19:40 #navit: < alexhell0xbf> ok, accepted
19:40 #navit: < alexhell0xbf> which one to use ?
19:40 #navit: < alexhell0xbf> navit ?
19:47 #navit: <@kazer> which one what ?
19:47 #navit: <@kazer> crap i did not validate.
19:50 #navit: <@kazer> https://github.com/navit-gps/mapserver
19:56 #navit: < alexhell0xbf> ok, stay tuned :) very soon
19:57 #navit: <@kazer> great :) thanks!
20:48 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-6652.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-6652.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-6652.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-6652.failed http://download.navit-project.org/logs/navit/n800/svn/navit-svn-6652.failed http://download.navit-project
20:48 #navit: < Navit> it-svn-6652.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-6652.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-6652.failed
20:48 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
--- Log closed Wed Apr 13 00:00:21 2016