--Apple-Mail-1-85674424 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Hi, I got installed navit and after some tries I got the correct germany.bin file by downloading it with a wget -O germany.bin ... quicklink. For a brief feedback: Very good ! A longer 'play with it': There is many times eaten much cpu time by navit when a route was or is calculated. Is this a known problem ? If navit needs to calculate a big route, isn't it good to display a hint window or a status message instead leaving the user unknown and let even the whole GUI stay blocked like with a message box when tapping on the screen and let the calculations done in a background thread ? It seems that this comes also into play when the position is changed, thus a recalculation would propably triggered ? I am also a programmer, but this seems to be a untrivial issue for a newbie for that code. Thanks Lothar -- Lothar Behrens |Rapid Prototyping ... Heinrich-Scheufelen-Platz 2 |XSLT Codegeneration 73252 Lenningen |www.lollisoft.de --Apple-Mail-1-85674424 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; "><div>Hi,</div><div><br = class=3D"webkit-block-placeholder"></div><div>I got installed navit and = after some tries I got the correct germany.bin file by downloading it = with a wget -O germany.bin ... quicklink.</div><div><br = class=3D"webkit-block-placeholder"></div><div>For a brief feedback: Very = good !</div><div><br class=3D"webkit-block-placeholder"></div><div>A = longer 'play with it': There is many times eaten much cpu time by navit = when a route was or is calculated. Is this a known problem = ?</div><div><br class=3D"webkit-block-placeholder"></div><div>If navit = needs to calculate a big route, isn't it good to display a hint window ...
(i finally ordered and received a Freerunner :) ) This issue has been around for some time : http://trac.navit-project.org/ticket/15 It used to work, then was removed because code was changed, and it If you're willing to help, feel free to contact me or join #navit on freenode. You will get there all the help you should need :) Thanks for your interest.. Sorry for the delayed answer, there is quite some activity here :) K _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Nice, are you a navit dev? I do agree... I've but changed a little the (gtk) interface to make it fit better to the openmoko, and I've to increase the cursor size (not so Well, in my experience it is recalculated but too late imho. Maybe the voice sinthetizer says it but while driving it's not easy to heard my freerunner (the speaker is to low to be heard in the traffic or if I'm listening some music), while often I've to force the refresh from the Nice. I'd like also to ask you a thing about the SDL interface... I've not tried to compile it in my toolchain/OE build due to the fact that I had no time to port/compile the missing libraries, but would it work well in the Freerunner (that has not 3d hardware acceleration)? -- Treviño's World - Life and Linux http://www.3v1n0.net/ _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
--Apple-Mail-1-118607258 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Hi, now I have played around a little with navit and tried to reduce the =20 recalculation when speed is under 4. It's my assumption that a walk is at last about 5 km/h, thus I added =20 some lines of code to handle this case. But before I am really do too much that propably has been done I would =20= ask here. The speed that triggers a recalculation of the displayed map is about =20= more as 2. Should this be done a little bit more ? Or could it be done by a 'lowpass' that increases the trigger about =20 half the average speed (three or four times measured) if the average is more than the result of the increase ? The decrease should be done similar (about some below the average). This will reduce the amount of recalculations a lot I think. A question beside. I want to try my changes on my FreeRunner for a =20 live test: How to get changes into the MokoMakefile built of navit. Should I create a patch to be applied in a prebuild step ? I have seen several directories per user that do something I don't =20 understand yet. Any further help out there ? Another idea: What about a real voice, recorded from someone to =20 replace the synthetic voice ? (There are not so much combinations I think) Thanks Lothar -- | Rapid Prototyping | XSLT Codegeneration | http://www.lollisoft.de Lothar Behrens Heinrich-Scheufelen-Platz 2 73252 Lenningen --Apple-Mail-1-118607258 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; "><div>Hi,</div><div><br = class=3D"webkit-block-placeholder"></div><div>now I have played around a = little with navit and tried to reduce the recalculation when speed is = under 4.</div><div>It's my assumption that a ...
