gosmore icon not working

[kalxas]

Desktop --> Navigation and Maps --> Gosmore report an error

[hamish]

see the quickstart:

    * Before running Gosmore you will need to convert a planet-*.osm data file.
Some data is provided in the /usr/local/share/osm/ directory.

Import it with:

bzip2 -dc /usr/local/share/data/osm/feature_city.osm.bz2 | gosmore rebuild

This will create gosmore.pak.

I agree that it's not a very nice user experience and we should take steps to do this for the user automatically, but the version of gosmore we ship right now is not very interesting so I didn't feel the need to spend more time on it. The new version in the 5.0 livedvd release on the other hand does cool stuff like 3D/head's up routing AFAICT, much like a in-car navigation device, so will be worth more effort.

Hamish

[kalxas]

Perhaps we should consider hiding the desktop link in that case...

Replying to hamish:

see the quickstart:

    * Before running Gosmore you will need to convert a planet-*.osm data file.
Some data is provided in the /usr/local/share/osm/ directory.

Import it with:

bzip2 -dc /usr/local/share/data/osm/feature_city.osm.bz2 | gosmore rebuild

This will create gosmore.pak.

I agree that it's not a very nice user experience and we should take steps to do this for the user automatically, but the version of gosmore we ship right now is not very interesting so I didn't feel the need to spend more time on it. The new version in the 5.0 livedvd release on the other hand does cool stuff like 3D/head's up routing AFAICT, much like a in-car navigation device, so will be worth more effort.

Hamish

[hamish]

Perhaps we should consider hiding the desktop link in that case...

It works fine once you've followed the instructions in the quickstart, so I'd be mildly inclined to leave it as-is.

another important issue I didn't mention is that if we did the prep step for the user it would incur some duplication of the .osm data file space on the disc. Plus what good is a tutorial if all the work is already done for you? :)

Hamish

[kalxas]

I agree with you, but an error message gives *always* bad impression to the end user. There are people who will click on it without having read the quickstart...

Angelos

[hamish]

I'll replace the startup icon's exec to a wrapper script which detects if the osm file has been generated yet, and asks if you want to want to generate it now (using gxmessage).

this won't happen for today's build, but as long as people read the quickstart page they'll be ok. The icon does work after they've done the generation step.

I accept the error message need to be improved, but I want to repeat this point:

Plus what good is a tutorial if all the work is already done for you?

best, Hamish