Advanced Use - Revision history

Alexwolf: /* Mac OS X */

2013-03-19T18:01:42Z

Mac OS X

Alexwolf: /* Adding Planetary Bodies */

2012-12-17T10:29:23Z

Adding Planetary Bodies

Didgeweb: Reverted edits by Liaozexin (talk) to last revision by Alexwolf

2012-08-23T14:32:34Z

Reverted edits by Liaozexin (talk) to last revision by Alexwolf

Liaozexin: /* Files and Directories */

2012-08-23T07:33:07Z

Files and Directories

Alexwolf: /* Other Configuration Files */

2012-05-18T16:38:07Z

Other Configuration Files

Fred v: /* Other Configuration Files */ formatting fixes: avoid unescaped magical characters

2012-05-15T20:32:01Z

Other Configuration Files: formatting fixes: avoid unescaped magical characters

Alexwolf: /* Scripting */

2011-05-25T19:21:37Z

Scripting

Alexwolf at 19:19, 25 May 2011

2011-05-25T19:19:13Z

Alexwolf: /* Windows */

2011-05-25T19:16:24Z

Windows

Alexwolf: /* Other Configuration Files */

2011-05-05T18:34:49Z

Other Configuration Files

@@ Line 30: / Line 30: @@
 ===Mac OS X===
 * '''installation directory''' This is found inside the application bundle, <code>Stellarium.app</code>. See the [http://www.mactipsandtricks.com/articles/Wiley_HT_appBundles.lasso Inside Application Bundles] for more information.
-* '''user directory''' This is the <code>Library/Preferences/Stellarium/</code> sub-directory of the users home directory.
+* '''user directory''' This is the <code>Library/Preferences/Stellarium/</code> (or <code>~/Library/Application Support/Stellarium</code> on newest versions of Mac OS X) sub-directory of the users home directory.
 * '''screenshot save directory''' Screenshots are saved to the users Desktop.

@@ Line 340: / Line 340: @@
   |float
   |Specify the albedo of the body
   |-
   |rot_periode
@@ Line 405: / Line 413: @@
   |Object parameter used in comet_orbit calculations
   |-
-  |orbit_ArgOf Pericenter
+  |orbit_ArgOfPericenter
   |float
   |Object parameter used in comet_orbit calculations
   |}
 Orbital calculations for the major planets is handled by sophisticated custom algorithms, and are accurate for a comparatively long time. For asteroids and comets the calculations are not as accurate, and the data in <code>ssystem.ini</code> for these bodies should be updated periodically (every year or two).

@@ Line 3: / Line 3: @@
 Stellarium has many data files containing such things as star catalogue data, nebula images, button icons, font files and configuration files. When Stellarium looks for a file, it looks in two places. First, it looks in the ''user directory'' for the account which is running Stellarium. If the file is not found there, Stellarium looks in the ''installation directory''<ref>The installation directory was referred to as the config root directory in previous versions of this guide</ref>. Thus it is possible for Stellarium to be installed as an administrative user and yet have a writable configuration file for non-administrative users. Another benefit of this method is on multi-user systems: Stellarium can be installed by the administrator, and different users can maintain their own configuration and other files in their personal user accounts.
-In addition to the main search path, Stellarium saves some files in other locations, for example screens shots and recorded scripts.Also [http://www.spainfootball.org/adidas-adipower-predator-sl-c-53_63.html/ adidas adipower predator]
+In addition to the main search path, Stellarium saves some files in other locations, for example screens shots and recorded scripts.
 The locations of the user directory, installation directory, ''screenshot save directory'' and ''script save directory'' vary according to the operating system and installation options used. The following sections describe the locations for various operating systems.

@@ Line 3: / Line 3: @@
 Stellarium has many data files containing such things as star catalogue data, nebula images, button icons, font files and configuration files. When Stellarium looks for a file, it looks in two places. First, it looks in the ''user directory'' for the account which is running Stellarium. If the file is not found there, Stellarium looks in the ''installation directory''<ref>The installation directory was referred to as the config root directory in previous versions of this guide</ref>. Thus it is possible for Stellarium to be installed as an administrative user and yet have a writable configuration file for non-administrative users. Another benefit of this method is on multi-user systems: Stellarium can be installed by the administrator, and different users can maintain their own configuration and other files in their personal user accounts.
-In addition to the main search path, Stellarium saves some files in other locations, for example screens shots and recorded scripts.
+In addition to the main search path, Stellarium saves some files in other locations, for example screens shots and recorded scripts.Also [http://www.spainfootball.org/adidas-adipower-predator-sl-c-53_63.html/ adidas adipower predator]
 The locations of the user directory, installation directory, ''screenshot save directory'' and ''script save directory'' vary according to the operating system and installation options used. The following sections describe the locations for various operating systems.

@@ Line 466: / Line 466: @@
   |-
   |.../stars/*/name.fab
-  |This file defines the Flamsteed designation for a star (see section [sec:flamsteeddesignation]). Each line of the file contains one record of two fields, separated by the pipe character (&#x007C;). The first field is the Hipparcos catalogue number of the star, the second is the Flamsteed designation, e.g:
+  |This file defines the Flamsteed designation for a star (see section [[Astronomical_Phenomena#Flamsteed_Designation|Flamsteed Designation]]). Each line of the file contains one record of two fields, separated by the pipe character (&#x007C;). The first field is the Hipparcos catalogue number of the star, the second is the Flamsteed designation, e.g:
 <code>72370|&alpha;_Aps</code>

@@ Line 158: / Line 158: @@
 ==Scripting==
-In version 0.10.2 of Stellarium includes the beginnings of a new scripting engine. The new scripting engine is still in development - there are missing features and probably a lot of bugs.
+Since version 0.10.2 of Stellarium includes the beginnings of a new scripting engine. The new scripting engine is still in development - there are missing features and probably a lot of bugs.
 ===Running Scripts===

@@ Line 1: / Line 1: @@
-{{ActualVersion|0.10.2}}
+{{ActualVersion|0.10.6}}
 ==Files and Directories==
 Stellarium has many data files containing such things as star catalogue data, nebula images, button icons, font files and configuration files. When Stellarium looks for a file, it looks in two places. First, it looks in the ''user directory'' for the account which is running Stellarium. If the file is not found there, Stellarium looks in the ''installation directory''<ref>The installation directory was referred to as the config root directory in previous versions of this guide</ref>. Thus it is possible for Stellarium to be installed as an administrative user and yet have a writable configuration file for non-administrative users. Another benefit of this method is on multi-user systems: Stellarium can be installed by the administrator, and different users can maintain their own configuration and other files in their personal user accounts.

← Older revision		Revision as of 19:16, 25 May 2011
Line 19:		Line 19:

	C:\Documents and Settings\Bob Dobbs\Application Data\Stellarium\		C:\Documents and Settings\Bob Dobbs\Application Data\Stellarium\
		+
		+	Thus, on a typical Windows Vista and Windows 7 systems with user “Bob Dobbs”, the user directory will be:
		+
		+	C:\Users\Bob Dobbs\AppData\Roaming\Stellarium\

	Stellarium version 0.9.0 did use the <code>%APPDATA%\Stellarium</code> folder. Thus if a <code>config.ini</code> file exists in the <code>%USERPROFILE%\Stellarium\</code> directory, that will be used in preference to the <code>%APPDATA%\Stellarium\</code> directory. This is to prevent users of version 0.9.0 from losing their settings when they upgrade.		Stellarium version 0.9.0 did use the <code>%APPDATA%\Stellarium</code> folder. Thus if a <code>config.ini</code> file exists in the <code>%USERPROFILE%\Stellarium\</code> directory, that will be used in preference to the <code>%APPDATA%\Stellarium\</code> directory. This is to prevent users of version 0.9.0 from losing their settings when they upgrade.

@@ Line 435: / Line 435: @@
 In addition to the files discussed in the previous sections, Stellarium uses various other data files. Many of these files may be edited easily to change Stellarium's behaviour<ref>Not all files in the <code>.../data</code> directory are listed here - only the ones which the advanced user is most likely to want to modify.</ref>.
-{|
+{| class="guidetable"
   |File
   |Purpose