Default Startup Values -- Config file

The place to discuss creating, porting and modifying Celestia's source code.
Topic author
don
Posts: 1709
Joined: 12.07.2003
With us: 21 years 4 months
Location: Colorado, USA (7000 ft)

Default Startup Values -- Config file

Post #1by don » 24.07.2003, 18:01

Howdy Developers,

Since there has been some discussion recently about how when a user goes to someone elses Cell:// URL, that it changes all of the existing Celestia settings on the user's machine. And how there is not a "simple" way for the user to "recall" or "reset" his/her settings.

One suggestion was for the user to create his/her own Cell:// URL with the settings they want. This is a good idea, but not everyone knows how to code HTML.

Another suggestion was to have a "reset" key in Celestia that would reset all values to some pre-defined (by the developers?) settings. Someone would need to define these settings, and it should be the user, not the developer. Sooooo . . .

Here is yet another idea ... Celestia already has a config file, so why not use it? 8O

It should contain every value that can be changed by a Celestia user, with a description of what the value is and what the possible values are, along with "default" values. It's an easy file for anyone to edit but it *will* need to have descriptions for the values represent (not just variable names), unless you make them all human-readable (ie. CurrentlySelectedObject, LockedObject, RenderAtmospheres, ShowLocationTypeXyz, etc.).

Yes, it will be a LARGE file, and it will need to be maintained every time a new command / function / feature (that the user can do) is added -- but -- all the user will have to do after going to someone elses Cell:// URL is to Exit and restart Celestia and ALL of their settings will be restored.

Thanks for your consideration of this idea.

-Don

PS. I'll even volunteer to create the initial listing to be added to the config file, if you want. :)

Topic author
don
Posts: 1709
Joined: 12.07.2003
With us: 21 years 4 months
Location: Colorado, USA (7000 ft)

Post #2by don » 28.07.2003, 21:24

. . .

Comments?

Criticism?

Sarcasm?

Discussion?

Anyone?

Or are all the developer's on summer vacation?

. . .

Christophe
Developer
Posts: 944
Joined: 18.07.2002
With us: 22 years 4 months
Location: Lyon (France)

Post #3by Christophe » 29.07.2003, 10:18

Maybe the solution is to make the Windows version closer to the KDE version where the problem is already fixed:
- Base the Bookmarks on URLs instead of favorites; and
- add commands to bookmark the current absolute/relative or setting URL.
Christophe

chris
Site Admin
Posts: 4211
Joined: 28.01.2002
With us: 22 years 9 months
Location: Seattle, Washington, USA

Post #4by chris » 29.07.2003, 15:28

Christophe wrote:Maybe the solution is to make the Windows version closer to the KDE version where the problem is already fixed:
- Base the Bookmarks on URLs instead of favorites; and
- add commands to bookmark the current absolute/relative or setting URL.

I agree that the bookmarks in Windows should behave a lot more like the ones in the KDE version. I started out be renaming the locations menu in Windows to bookmarks but haven't gotten much further than that. On the topic of bookmarks, it might also be nice to have bookmarks that set the location only and not any render or label flags.

--Chris

Topic author
don
Posts: 1709
Joined: 12.07.2003
With us: 21 years 4 months
Location: Colorado, USA (7000 ft)

Post #5by don » 30.07.2003, 17:19

Chris and Christophe,

Both good ideas, for sure.

However, aside from doing those things, having Celestia's settings available to the user via the config file allows them to set-up exactly how they want Celestia to be configured every time they start it. This way, they can feel free to visit Cell://URLs, try someone elses script, play with scripting themselves, etc. So, no matter how bad Celestia's settings might get messed up, all they have to do is Exit and re-run Celestia.

They will not have to create their own Cell://URL (which they can't do if they don't know HTML), they will not have to create their own cel or celx script (which they won't do if they don't know about scripting or programming), etc.

Thus, the config file becomes a "safety blanket" of sorts.

With each variable/parameter/argument described in detail, along with a list of it's possible settings, anyone who can run a text editor will be able to modify the config file. I would also suggest duplicating the file in the release package, with a name like "celestia_ORIG.cfg", for those overzealous folks who edit and save the original "celestia.cfg" file before making a copy of it <smile>.

And, like I wrote above, I am willing to create the initial file, with descriptions, settings, etc., to the best of my ability.
-Don G.
My Celestia Scripting Resources page

Avatar: Total Lunar Eclipse from our back yard, Oct 2004. Panasonic FZ1 digital camera (no telescope), 36X digital zoom, 8 second exposure at f6.5.

Christophe
Developer
Posts: 944
Joined: 18.07.2002
With us: 22 years 4 months
Location: Lyon (France)

Post #6by Christophe » 30.07.2003, 17:51

Don,

Maybe I should clarify here how things work in KDE.

You can directly bookmark settings, you don't need to edit any file. Simply go to Bookmarks->Bookmark Settings. And a new bookmark with the current settings is created, no need to edit a file, to know HTML or .cel scripting.

This way you can even have several settings for different exploration types. You can also assign shortcuts to these bookmarks if you place them in your personnal toolbar.

I think this solves the problem elegantly?
Christophe

Topic author
don
Posts: 1709
Joined: 12.07.2003
With us: 21 years 4 months
Location: Colorado, USA (7000 ft)

Post #7by don » 30.07.2003, 18:02

:D I LIKE it! I LIKE it! :D
-Don G.

My Celestia Scripting Resources page



Avatar: Total Lunar Eclipse from our back yard, Oct 2004. Panasonic FZ1 digital camera (no telescope), 36X digital zoom, 8 second exposure at f6.5.


Return to “Development”