--- Log opened Fri Sep 04 00:00:50 2015
01:22 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:541d:cb06:fc7f:bea7] has joined #navit
01:38 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
01:44 -!- juse [~juse@fox5.kyla.fi] has joined #navit
02:12 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
02:38 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
02:58 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
03:03 -!- jjelen [jjelen@nat/redhat/x-tohdfheqgaokoqud] has joined #navit
03:36 -!- robertp [bc5c2134@gateway/web/freenode/ip.188.92.33.52] has quit [Quit: Page closed]
04:12 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #navit
04:27 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
04:29 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
06:26 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
06:32 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
06:48 -!- robertp [bc5c2134@gateway/web/freenode/ip.188.92.33.52] has joined #navit
06:53 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:541d:cb06:fc7f:bea7] has quit [Quit: Leaving.]
07:01 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
07:06 -!- robertp [bc5c2134@gateway/web/freenode/ip.188.92.33.52] has quit []
07:14 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
07:22 -!- juse [~juse@fox5.kyla.fi] has quit [Ping timeout: 246 seconds]
07:58 -!- juse [~juse@fox5.kyla.fi] has joined #navit
09:25 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds]
09:26 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
09:58 -!- jandegr [5bb54d2f@gateway/web/freenode/ip.91.181.77.47] has joined #navit
11:11 -!- juse [~juse@fox5.kyla.fi] has quit [Ping timeout: 260 seconds]
11:30 -!- jandegr [5bb54d2f@gateway/web/freenode/ip.91.181.77.47] has quit [Ping timeout: 246 seconds]
11:32 -!- jandegr [5bb54d2f@gateway/web/freenode/ip.91.181.77.47] has joined #navit
11:51 -!- robertp [584aaf83@gateway/web/freenode/ip.88.74.175.131] has joined #navit
11:51 #navit: < robertp> Hi all!
12:07 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
12:15 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
12:25 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Ex-Chat]
12:40 -!- juse [~juse@fox5.kyla.fi] has joined #navit
12:43 #navit: < KaZeR> hi there
12:47 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has joined #navit
12:48 #navit: < robertp> hi
12:54 #navit: < KaZeR> how are you doing robertp ?
12:57 #navit: < robertp> well. i succeeded to read my own navit.xml-tag.
12:58 #navit: < robertp> now i am searching the way to write to the file.
13:01 #navit: < KaZeR> cool. i don't think that we have any code to write to the xml file right now. but gui_internal saves some datas in a seperate file
13:01 #navit: < KaZeR> also, i think that it makes sense to have a "static" xml file, and save state datas to another file. that way you can have a "reset to defaults" button, which will wipe the state data files
13:02 #navit: < KaZeR> what do you think ?
13:02 #navit: < KaZeR> (but i agree that we should have a standardized mechanism to do it via a simple navit call )
13:03 #navit: < juse> KaZeR is the FPS smoothening project doing good ? :)
13:03 #navit: < robertp> that sounds good, but this would be the next step - in my opinion.
13:04 #navit: < KaZeR> juse : i honestly haven't looked into it a lot yet. i need to finish the audio framework first
13:04 #navit: < KaZeR> robertp: you think that it would be easier to write the xml file rather than write to a state file ?
13:05 #navit: < juse> okay kazer!
13:06 #navit: < robertp> i dont know. i thought there is no difference between state and reset file
13:08 #navit: < robertp> maybe we should export the user configurable options to another file
13:09 #navit: < robertp> and this file overrides the static options in navit.xml
13:09 #navit: < KaZeR> yeah that would be the optimal case i think
13:10 #navit: < robertp> i hope exporting the user configurable options is possible after building a gui which can do the configuration
13:11 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
13:13 #navit: < robertp> how is the current layout saved, after navit is closed?
13:16 #navit: < robertp> ok i found it. i hate it. one asks a question and just after sending you get the solution....
13:16 #navit: < KaZeR> haha no worries :)
13:17 #navit: < KaZeR> but yeah, this is part of what we should do better with qt5 :)
13:17 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
13:17 #navit: < robertp> i dont expect that thinking before posting has to do with Qt. :D
13:18 #navit: < KaZeR> no, i meant saving the UI state :)
13:18 #navit: < robertp> i know, just kidding.
13:18 #navit: < KaZeR> :)
13:21 -!- jjelen [jjelen@nat/redhat/x-tohdfheqgaokoqud] has quit [Ping timeout: 268 seconds]
13:29 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
13:44 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
14:06 #navit: < robertp> kazer i think using the "statefile".txt way wouldnt work for a lot of options.
14:08 #navit: < KaZeR> robertp: can you elaborate?
14:11 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
14:12 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has joined #navit
14:22 #navit: < robertp> i went through the parts of code where a state file is written. only the former destinations have multiple entries in the file.
14:24 #navit: < robertp> and they are all the same type
14:25 #navit: < robertp> i want a state file, where all types of possible options can be stored an read.
14:25 #navit: < robertp> so it looks like xml would be the only way to go for it
14:26 #navit: < KaZeR> yeah i definitely agree that the current way of doing it is hacky
14:26 #navit: < KaZeR> xml would allow a better structure. yaml could be a good option too, maybe
14:27 #navit: < robertp> ok, looks like it will ba a longer way to MY navit than expected. :D
14:31 #navit: < KaZeR> why longer?
14:33 #navit: < robertp> Just a lot work to do. There are some features I want. One is the gui-based configuration.
14:33 #navit: < robertp> does navit use any kind of xmllib?
14:34 #navit: < robertp> I thought that adding the music player isn't too much work. And then the todo-list grew. Its funny.
14:34 #navit: < KaZeR> you can use either a lib or an internl xml implementation iirc. i can find the name from the cmake output
14:35 #navit: < KaZeR> well i really don't want you to feel that things are complicated or that they will take a lot of times. we should be able to code faster and collaborate more easily
14:36 #navit: < KaZeR> if you want to save the state of your player in a file, you can just to it as you see fit. we'll rework it when the time is right
14:36 #navit: < robertp> no kazer it's great. i really like it.
14:36 #navit: < KaZeR> we just need to be a bit careful to avoid to much rework of small contributions, and try to move in a common direction
14:36 #navit: < KaZeR> ha great :)
14:36 #navit: < robertp> hard work feels good. but its never fast.
14:37 #navit: < robertp> and i dont take myself too serious, i do a lot of (sometimes stupid) kidding. Maybe i should say that. :D
14:38 #navit: < KaZeR> well i did not interpret that as you being too serious about yourself. but i care a lot about ensuring that everybody can contribute and enjoy it
14:39 #navit: < KaZeR> if we have a cumbersome or tedious collaboration process, that's bad
14:40 #navit: < robertp> sure
14:45 #navit: < KaZeR> so keep going with the jokes :D
15:12 #navit: < robertp> i have some kind of language issue... parsing doesnt include the ability to write back to file, does it?
15:15 #navit: < robertp> i thought to use the existing xml-functions, but it looks like they just cant write to file.
15:21 #navit: < KaZeR> mmm indeed looks like we are looking for ezxml which is only a parser
15:22 #navit: < KaZeR> but qt5 provides qtxml.. so it should be easier when we will have started the work on the qt5 gui :)
15:22 #navit:  * KaZeR tries to federate some coders around qt5. is that obvious? :D
15:23 #navit: < robertp> it looks like qt5 ist the answer of all my questions.
15:23 #navit: < robertp> haha
15:24 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 240 seconds]
15:26 -!- RobertP_ [584aaf83@gateway/web/freenode/ip.88.74.175.131] has joined #navit
15:27 -!- jandegr [5bb54d2f@gateway/web/freenode/ip.91.181.77.47] has quit [Quit: Page closed]
15:27 -!- robertp [584aaf83@gateway/web/freenode/ip.88.74.175.131] has quit [Ping timeout: 246 seconds]
15:27 -!- tryagain [~quassel@178.216.76.64] has joined #navit
15:28 -!- RobertP_ [584aaf83@gateway/web/freenode/ip.88.74.175.131] has quit [Client Quit]
15:30 -!- RobertP [584aaf83@gateway/web/freenode/ip.88.74.175.131] has joined #navit
15:32 #navit: < RobertP> KaZeR how would you start changing the gui to qt. cuurently i cant imagine how to go for it.
15:36 #navit: < KaZeR> what do you mean changing the gui ?
15:36 #navit: < KaZeR> the gui itself is a plugin, so we can develop it aside from the internal gui
15:37 #navit: < RobertP> sure, but i dont know how and where to start
15:37 -!- _rd_ [~rd@p57A0FAC3.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
15:38 #navit: < KaZeR> ha!
15:38 #navit: < KaZeR> ok. i see two things that anybody wanting to help can do right now :
15:38 #navit: < RobertP> ha?
15:38 #navit: < KaZeR> - get familiar with qt editor
15:39 #navit: < KaZeR> - think about a better menu organization. the current one in gui internal sucks, it's confusing
15:39 #navit: < RobertP> here, me *winking and waving*
15:39 #navit: < KaZeR> hehe :)
15:39 #navit: < KaZeR> i was planning to start a wiki page. i have at least one, maybe two other folks interested in helping
15:41 #navit: < RobertP> ok, and all the stuff inside navit/gui/internal/ must be implemented in qt?
15:43 #navit: < KaZeR> probably yeah. and maybe a few more :)
15:43 #navit: < KaZeR> i think that we should start fresh tho and not try to mimic what we have in gui_internal
15:44 #navit: < KaZeR> also, there is far less code required for qt5, as most of the widgets we need will already be implemented ( eg: we have our own list implementation in internal )
15:44 #navit: < KaZeR> the qt4 gui isn't really functional, it was never finished, but you can get an idea of how to articulate a qt gui on top of navit
15:45 #navit: < RobertP> ok, ill try that
15:48 #navit: < KaZeR> great. i played a bit with the qteditor, it's not difficult to use
15:48 #navit: < KaZeR> whenever you feel ready, we can start a branch :)
15:48 #navit: < RobertP> i used qtcreator for my mp3player which runs currently on the hardware
15:49 #navit: < RobertP> but i built on the pi A+ and it was veeeeery slow
15:50 #navit: < KaZeR> oh great. So you are our official qtcreator expert then :D
15:51 #navit: < KaZeR> and we'll can try to cross compile a package using circle ci to speed things up!
15:51 #navit: < KaZeR> (i know that circleci has some limitation regarding cpu limitation, but i'll have a look)
15:51 #navit: < RobertP> i currently dont code on the pi
15:52 #navit: < RobertP> i made a working debian-vm
15:52 #navit: < RobertP> everything works. except audio. :D So mpd crashes.
15:54 #navit: < RobertP> but i have alot of cpu power
15:55 #navit: < KaZeR> great :)
16:11 -!- _rd_ [~rd@p4FD1DACA.dip0.t-ipconnect.de] has joined #navit
16:16 #navit: < RobertP> KaZeR qmake and cmake arent compatible, i'd expect. will navit be made with cmake and qmake side by side or will qmake do all the work?
16:20 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
16:28 #navit: < RobertP> and again... found it. cmake will be used.
16:33 #navit: < KaZeR> :)
16:34 #navit: < RobertP> downloading 1GB QT5...
16:37 #navit: < KaZeR> yeah that's the drawback. tho, we don't need the full blown qt5 setup
16:38 #navit: < RobertP> i dont care. not now. i can easyly increase my virtual harddisk
16:39 #navit: < RobertP> but for the raspberry it could be a problem. because qt5 is not in the debian wheezy packages
16:39 -!- tryagain [~quassel@178.216.76.64] has quit [Ping timeout: 240 seconds]
16:42 #navit: < KaZeR> yeah hopefully we can cross compile everything and just provide binary packages for faster installs. i even have a script to install navit automatically on top of raspbian net install
16:55 #navit: < RobertP> qtcreator seems to have the ability to cross compile for armv5 and armv7.
17:00 -!- RobertP [584aaf83@gateway/web/freenode/ip.88.74.175.131] has quit [Quit: gn]
17:05 #navit: < KaZeR> but only for the qt part of the project i'm afraid. i'm not sure that we could use that to fully cross compile navit ( qmake vs cmake )
17:14 -!- _rd_ [~rd@p4FD1DACA.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
17:16 -!- gernot_ [508ec793@gateway/web/freenode/ip.80.142.199.147] has joined #navit
17:16 #navit: < gernot_> hi
17:18 #navit: < KaZeR> hi gernot_
17:21 #navit: < gernot_> At the moment i try to get better results driving around closed roads.
17:21 #navit: < KaZeR> closed roads?
17:21 #navit: < KaZeR> juse: what about this video btw ? :)
17:22 #navit: < gernot_> here are holllday. Many streets are locked for maintain
17:25 #navit: < KaZeR> interesting. are you using the traffic distortion for that ?
17:25 #navit: < gernot_> If you drive small street detour it takes long time with "please turn..."
17:25 #navit: < KaZeR> yeah we need to fix that. i might do it now actually. this is annoying
17:25 #navit: < KaZeR> is there an online database of the closed roads?
17:26 #navit: < gernot_> only for main overland roads
17:27 #navit: < KaZeR> do you have a url ?
17:28 #navit: < gernot_> I can use waypoints,
17:29 #navit: < gernot_> e.g. https://stau.info/
17:30 #navit: < gernot_> with detour: https://stau.info/bundesstrasse/B12
17:32 #navit: < KaZeR> mmm it's timing out for me
17:32 #navit: < gernot_> i try to change routing priority for a "car_deour" vehicle :-)
17:32 #navit: < gernot_> byt
17:33 #navit: < gernot_> t
17:33 #navit: < gernot_> by
17:37 -!- gernot_ [508ec793@gateway/web/freenode/ip.80.142.199.147] has quit []
17:48 -!- pini [~pini@bou-fi.pustule.org] has quit [Read error: Connection reset by peer]
17:48 -!- pini [~pini@88.189.102.17] has joined #navit
18:01 -!- pini [~pini@88.189.102.17] has quit [Ping timeout: 272 seconds]
18:04 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
18:08 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
20:37 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 252 seconds]
20:39 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/osm/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/wince_386/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/wince_cmake/svn/navit-svn-12310.failed http://download.na
20:39 #navit: < Navit> avit-svn-12310.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32_cmake/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32_gtk_cmake/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/n800/svn/navit-svn-12310.failed http://download.navit-pro
20:39 #navit: < Navit> /navit-svn-12310.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/iphone/svn/navit-svn-12310.failed
20:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
21:38 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/osm/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/wince_386/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/wince_cmake/svn/navit-svn-12310.failed http://download.na
21:38 #navit: < Navit> avit-svn-12310.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32_cmake/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32_gtk_cmake/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/n800/svn/navit-svn-12310.failed http://download.navit-pro
21:38 #navit: < Navit> /navit-svn-12310.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/iphone/svn/navit-svn-12310.failed
21:38 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
--- Log closed Sat Sep 05 00:00:52 2015