From: Bogdan M. <dag...@gm...> - 2010-01-11 18:51:50
|
On Mon, Jan 11, 2010 at 8:37 PM, Timothy Reaves <tr...@si...> wrote: > > On Jan 11, 2010, at 12:44 PM, Fabien Chéreau wrote: > >> Dear all, >> After some days of work I finally recoded the way external star >> catalogs are managed. The new design is much simpler as the previous >> one, and hopefully more robust. >> The main differences with the previous way of doing it are: >> - store stars catalog description in a JSON file in >> $HOME/.stellarium/stars/default/ >> - automatic import of previously downloaded files, even if the config >> file was deleted or stellarium updated. >> - each time the content/format of 1 star catalog is changed, the >> local config is overridden and old catalogs re-checked for >> compatibility (using checksum). >> - no config file needs to be stored online and checked at startup. If >> we updated the star files, we need to make a new release with an >> updated defaultStarsConfig.json. This previous feature was useless, >> too complicated, bug prone and even doubtful for security. >> - when a download is on-going and stellarium is quit, the download is >> lost. I didn't have time to code that properly... > > > This does not seem to be working. I renamed my stars directory to test a defect. It was re-created (for another user, it crashes). When I put the directory back and started the app, it did not show that I had downloaded the catalogs. It works on my Ubuntu: I just downloaded a catalog from SourceForge and put it in ~/.stellarium/stars/default. (There was already another catalog and the .json file there.) Stellarium recognised it and offered downloading the next catalog in the series. I deleted the .json file - it recognised the existing catalogs, determined that the incomplete download was incomplete and offered it for download again. Bogdan |