Stellarium Wiki - User contributions [en]

Configuring Build Options

2012-10-28T15:54:34Z

Daggerstab: /* Make targets */

On all platforms, Stellarium uses a two-step building process:
* <tt>[http://www.cmake.org/ CMake]</tt> processes a set of project files (<tt>CMakeLists.txt</tt>) to generate a set of scripts for <tt>make</tt> (if you are using Qt Creator, it runs CMake when you open the project);
* <tt>[http://en.wikipedia.org/wiki/Make_%28software%29 make]</tt> performs the steps detailed in the scripts, calling the compiler, the linker and other utility programs to build Stellarium's executables, libraries and data files.

This page explains the various command-line options that can be passed to <tt>CMake</tt> and <tt>make</tt> to produce different build configurations.

== CMake options ==

CMake caches the current project configuration in <tt>CMakeCache.txt</tt>, including the options passed to it at the command line. This is useful, as it saves typing the next time you invoke CMake for the project, but it can also be annoying if you are not careful.

The proper way to change the options is to pass them to CMake on the command line, instead of editing directly the CMakeCache file. This way, the make files will be updated in case there is some hidden dependency on the value of the option you are passing.

For example, the next command is a first invocation of CMake for Stellarium that configures the build of a development version for Windows in Release mode which based on revision 5520:
cmake -G "MSYS Makefiles" -DCMAKE_INSTALL_PREFIX=C:/stellarium -DCMAKE_BUILD_TYPE=Release -DRELEASE_BUILD=0 -DBZR_REVISION=5520 ../..

Qt Creator provides a wrapper around CMake - the CMake Wizard. It is automatically launched when Stellarium's CMakeLists.txt is opened for the first time, and it can be launched at any time from the "Build" -> "Run CMake" menu.

===BUILD_FOR_MAEMO===
''Default value'': '''0'''.

This option enables building Stellarium for Maemo devices and also enables optimization for ARM processors.

===BUILD_STATIC_PLUGINS===
''Default value'': '''1'''.

This option defines that plugins should be compiled statically and linked to the main program. ''If this option has value '''1''' then for BUILD_DYNAMIC_PLUGINS should be value '''0'''.''

===BUILD_DYNAMIC_PLUGINS===
''Default value'': '''0'''.

This option defines that plugins should be compiled dynamically. ''If this option has value '''1''' then for BUILD_STATIC_PLUGINS should be value '''0'''.''

===BZR_REVISION===
This option is used together with [[#RELEASE_BUILD|RELEASE_BUILD]] option and sets Bazaar's revision for package.

===CMAKE_BUILD_TYPE===
Possible values: None, Debug, GProf, Valgrind, Release, RelWithDebInfo, MinSizeRel.

''Default value'': '''Debug'''

Possible values:
;Release:Release mode - the binary package does not include debug characters and some of the source code is ignored; this mode is the default for users.
;Debug:Debug mode - the binary package includes debug characters and debug macros in the source code are not ignored; this mode is the default for developers.
;RelWithDebInfo:Release mode, but the binary package includes debug characters; this mode is for developers and users.
;GProf:Support for GNU gprof profiler - binary package includes debug characters for profiler; this mode is for developers
;Valgrind:Support for Valgrind - binary package includes debug characters for memory debugging, memory leak detection, and profiling; this mode is for developers.
;MinSizeRel:Release mode - binary package optimized for minimal size.

===CMAKE_INSTALL_PREFIX===
This option sets a prefix for the installation of the binary package location. Used on Linux to set the location for the software installation, building from source code, the default location is ''/usr/local'' but if you want to install software elsewhere such as into ''/opt'' you need use ''CMAKE_INSTALL_PREFIX=/opt''

===CMAKE_C_COMPILER===
This option sets a custom path to C compiler. For example if you have installed GCC and Clang; and wish to use the Clang compiler you need use ''CMAKE_C_COMPILER=/usr/bin/clang''

===CMAKE_CXX_COMPILER===
This option sets a custom path to the C++ compiler. For example; if you have installed GCC and Clang; to use the Clang compiler you need use ''CMAKE_CXX_COMPILER=/usr/bin/clang''

===ENABLE_NLS===
''Default value'': '''1'''.

This option activates translation with gettext.

===ENABLE_SOUND===
''Default value'': '''0'''.

This option activates sound support.The default value is 0 because sound is not available on all platforms and may require 3rd party software.

===ENABLE_SCRIPTING===
''Default value'': '''1'''.

This option activates the scripting feature.

===ENABLE_SCRIPT_CONSOLE===
''Default value'': '''1'''.

This option activates the script edit console.

===ENABLE_STRATOSCRIPT_COMPAT===
''Default value'': '''0'''.

This option enable the StratoScript compatibility mode. If set to 1 many of the old *.sts scripts can be used.

===GUI_MODE===
Possible values: Standard, None, External

''Default value'': '''Standard'''.

This option set a type of GUI for using in Stellarium.

===OPENGL_MODE===
Possible values: Desktop, ES2

''Default value'': '''Desktop'''.

This option defines mode to supporting OpenGL version - OpenGL for desktops or OpenGL ES

===OPTIMIZE_INTEL_ATOM===
''Default value'': '''0'''.

This option enables optimization for Atom processors.

===RELEASE_BUILD===
''Default value'': '''1'''.

This option flags the build as an official release.

===STELLARIUM_SPLASH===
Possible values: Development, ReleaseCandidate, Release

''Default value'': '''Development'''.

This option set the splash screen for Stellarium.

===USE_PLUGIN_*===
These options control whether the given plugin is built. For example to build the Historical Supernovae plugin you need use ''USE_PLUGIN_SUPERNOVAE=1''.

;USE_PLUGIN_HELLOSTELMODULE: (Default value: '''0''') The Hello StelModule example plugin.
;USE_PLUGIN_ANGLEMEASURE: (Default value: '''1''') The Angle Measure plugin.
;USE_PLUGIN_COMPASSMARKS: (Default value: '''1''') The Compass Marks plugin.
;USE_PLUGIN_SATELLITES: (Default value: '''1''') The Satellites plugin.
;USE_PLUGIN_TELESCOPECONTROL: (Default value: '''1''') The Telescope Control plugin.
;USE_PLUGIN_LOGBOOK: (Default value: '''0''') The Logbook plugin - unfinished, development suspended indefinitely.
;USE_PLUGIN_OCULARS: (Default value: '''1''') The Oculars plugin.
;USE_PLUGIN_SVMT: (Default value: '''0''') The [https://launchpad.net/svmt Survey Monitoring and Visualization Tool], a plug-in for professional astronomers developed separately from Stellarium. (I.e. its code is not in the main repository.)
;USE_PLUGIN_TEXTUSERINTERFACE: (Default value: '''1''') The Text User Interface plugin.
;USE_PLUGIN_TIMEZONECONFIGURATION: (Default value: '''1''') The Time Zone plugin.
;USE_PLUGIN_VIRGO: (Default value: '''0''') [https://launchpad.net/virgo VirGO], a plug-in for professional astronomers developed separately from Stellarium. (I.e. its code is not in the main repository.)
;USE_PLUGIN_SOLARSYSTEMEDITOR: (Default value: '''1''') The Solar System Editor plugin.
;USE_PLUGIN_SUPERNOVAE: (Default value: '''1''') The Historical Supernovae plugin.
;USE_PLUGIN_QUASARS: (Default value: '''1''') The Quasars plugin.
;USE_PLUGIN_PULSARS: (Default value: '''1''') The Pulsars plugin.
;USE_PLUGIN_EXOPLANETS: (Default value: '''1''') The Exoplanets plugin.

==Make targets==

Make groups various tasks as "targets". Starting <code>make</code> without any arguments causes make to build the default target - in our case, building Stellarium, its tests, the localization files, etc.

To list all possible targets, use the "help" target:
make help

Other useful targets:

make install
Installation of all binaries and related files to the directory determined by [[#CMAKE_INSTALL_PREFIX|CMAKE_INSTALL_PREFIX]]. Straight installation on Linux, first step of creating an installer package on Windows.

make test
Launch the suite of test executables.

make macosx_bundle
Package a bundle for Mac OS X.

make package
This option make package for Linux.

[[Category: Development]]
[[Category: Customization]]

Configuring Build Options

2012-10-28T15:43:26Z

Daggerstab:

On all platforms, Stellarium uses a two-step building process:
* <tt>[http://www.cmake.org/ CMake]</tt> processes a set of project files (<tt>CMakeLists.txt</tt>) to generate a set of scripts for <tt>make</tt> (if you are using Qt Creator, it runs CMake when you open the project);
* <tt>[http://en.wikipedia.org/wiki/Make_%28software%29 make]</tt> performs the steps detailed in the scripts, calling the compiler, the linker and other utility programs to build Stellarium's executables, libraries and data files.

This page explains the various command-line options that can be passed to <tt>CMake</tt> and <tt>make</tt> to produce different build configurations.

== CMake options ==

CMake caches the current project configuration in <tt>CMakeCache.txt</tt>, including the options passed to it at the command line. This is useful, as it saves typing the next time you invoke CMake for the project, but it can also be annoying if you are not careful.

The proper way to change the options is to pass them to CMake on the command line, instead of editing directly the CMakeCache file. This way, the make files will be updated in case there is some hidden dependency on the value of the option you are passing.

For example, the next command is a first invocation of CMake for Stellarium that configures the build of a development version for Windows in Release mode which based on revision 5520:
cmake -G "MSYS Makefiles" -DCMAKE_INSTALL_PREFIX=C:/stellarium -DCMAKE_BUILD_TYPE=Release -DRELEASE_BUILD=0 -DBZR_REVISION=5520 ../..

Qt Creator provides a wrapper around CMake - the CMake Wizard. It is automatically launched when Stellarium's CMakeLists.txt is opened for the first time, and it can be launched at any time from the "Build" -> "Run CMake" menu.

===BUILD_FOR_MAEMO===
''Default value'': '''0'''.

This option enables building Stellarium for Maemo devices and also enables optimization for ARM processors.

===BUILD_STATIC_PLUGINS===
''Default value'': '''1'''.

This option defines that plugins should be compiled statically and linked to the main program. ''If this option has value '''1''' then for BUILD_DYNAMIC_PLUGINS should be value '''0'''.''

===BUILD_DYNAMIC_PLUGINS===
''Default value'': '''0'''.

This option defines that plugins should be compiled dynamically. ''If this option has value '''1''' then for BUILD_STATIC_PLUGINS should be value '''0'''.''

===BZR_REVISION===
This option is used together with [[#RELEASE_BUILD|RELEASE_BUILD]] option and sets Bazaar's revision for package.

===CMAKE_BUILD_TYPE===
Possible values: None, Debug, GProf, Valgrind, Release, RelWithDebInfo, MinSizeRel.

''Default value'': '''Debug'''

Possible values:
;Release:Release mode - the binary package does not include debug characters and some of the source code is ignored; this mode is the default for users.
;Debug:Debug mode - the binary package includes debug characters and debug macros in the source code are not ignored; this mode is the default for developers.
;RelWithDebInfo:Release mode, but the binary package includes debug characters; this mode is for developers and users.
;GProf:Support for GNU gprof profiler - binary package includes debug characters for profiler; this mode is for developers
;Valgrind:Support for Valgrind - binary package includes debug characters for memory debugging, memory leak detection, and profiling; this mode is for developers.
;MinSizeRel:Release mode - binary package optimized for minimal size.

===CMAKE_INSTALL_PREFIX===
This option sets a prefix for the installation of the binary package location. Used on Linux to set the location for the software installation, building from source code, the default location is ''/usr/local'' but if you want to install software elsewhere such as into ''/opt'' you need use ''CMAKE_INSTALL_PREFIX=/opt''

===CMAKE_C_COMPILER===
This option sets a custom path to C compiler. For example if you have installed GCC and Clang; and wish to use the Clang compiler you need use ''CMAKE_C_COMPILER=/usr/bin/clang''

===CMAKE_CXX_COMPILER===
This option sets a custom path to the C++ compiler. For example; if you have installed GCC and Clang; to use the Clang compiler you need use ''CMAKE_CXX_COMPILER=/usr/bin/clang''

===ENABLE_NLS===
''Default value'': '''1'''.

This option activates translation with gettext.

===ENABLE_SOUND===
''Default value'': '''0'''.

This option activates sound support.The default value is 0 because sound is not available on all platforms and may require 3rd party software.

===ENABLE_SCRIPTING===
''Default value'': '''1'''.

This option activates the scripting feature.

===ENABLE_SCRIPT_CONSOLE===
''Default value'': '''1'''.

This option activates the script edit console.

===ENABLE_STRATOSCRIPT_COMPAT===
''Default value'': '''0'''.

This option enable the StratoScript compatibility mode. If set to 1 many of the old *.sts scripts can be used.

===GUI_MODE===
Possible values: Standard, None, External

''Default value'': '''Standard'''.

This option set a type of GUI for using in Stellarium.

===OPENGL_MODE===
Possible values: Desktop, ES2

''Default value'': '''Desktop'''.

This option defines mode to supporting OpenGL version - OpenGL for desktops or OpenGL ES

===OPTIMIZE_INTEL_ATOM===
''Default value'': '''0'''.

This option enables optimization for Atom processors.

===RELEASE_BUILD===
''Default value'': '''1'''.

This option flags the build as an official release.

===STELLARIUM_SPLASH===
Possible values: Development, ReleaseCandidate, Release

''Default value'': '''Development'''.

This option set the splash screen for Stellarium.

===USE_PLUGIN_*===
These options control whether the given plugin is built. For example to build the Historical Supernovae plugin you need use ''USE_PLUGIN_SUPERNOVAE=1''.

;USE_PLUGIN_HELLOSTELMODULE: (Default value: '''0''') The Hello StelModule example plugin.
;USE_PLUGIN_ANGLEMEASURE: (Default value: '''1''') The Angle Measure plugin.
;USE_PLUGIN_COMPASSMARKS: (Default value: '''1''') The Compass Marks plugin.
;USE_PLUGIN_SATELLITES: (Default value: '''1''') The Satellites plugin.
;USE_PLUGIN_TELESCOPECONTROL: (Default value: '''1''') The Telescope Control plugin.
;USE_PLUGIN_LOGBOOK: (Default value: '''0''') The Logbook plugin - unfinished, development suspended indefinitely.
;USE_PLUGIN_OCULARS: (Default value: '''1''') The Oculars plugin.
;USE_PLUGIN_SVMT: (Default value: '''0''') The [https://launchpad.net/svmt Survey Monitoring and Visualization Tool], a plug-in for professional astronomers developed separately from Stellarium. (I.e. its code is not in the main repository.)
;USE_PLUGIN_TEXTUSERINTERFACE: (Default value: '''1''') The Text User Interface plugin.
;USE_PLUGIN_TIMEZONECONFIGURATION: (Default value: '''1''') The Time Zone plugin.
;USE_PLUGIN_VIRGO: (Default value: '''0''') [https://launchpad.net/virgo VirGO], a plug-in for professional astronomers developed separately from Stellarium. (I.e. its code is not in the main repository.)
;USE_PLUGIN_SOLARSYSTEMEDITOR: (Default value: '''1''') The Solar System Editor plugin.
;USE_PLUGIN_SUPERNOVAE: (Default value: '''1''') The Historical Supernovae plugin.
;USE_PLUGIN_QUASARS: (Default value: '''1''') The Quasars plugin.
;USE_PLUGIN_PULSARS: (Default value: '''1''') The Pulsars plugin.
;USE_PLUGIN_EXOPLANETS: (Default value: '''1''') The Exoplanets plugin.

==Make targets==

===install===
This option make installation of binaries and related files (installation of program).

===test===
This option launched tests from test suite.

===macosx_bundle===
This option make bundle package for Mac OS X.

===package===
This option make package for Linux.

[[Category: Development]]
[[Category: Customization]]

Configuring Build Options

2012-10-28T15:28:11Z

Daggerstab: copyediting

On all platforms, Stellarium uses a two-step building process:
* <tt>[http://www.cmake.org/ CMake]</tt> processes a set of project files (<tt>CMakeLists.txt</tt>) to generate a set of scripts for <tt>make</tt> (if you are using Qt Creator, it runs CMake when you open the project);
* <tt>[http://en.wikipedia.org/wiki/Make_%28software%29 make]</tt> performs the steps detailed in the scripts, calling the compiler, the linker and other utility programs to build Stellarium's executables, libraries and data files.

This page explains the various command-line options that can be passed to <tt>CMake</tt> and <tt>make</tt> to produce different build configurations.

== CMake options ==

CMake caches the current project configuration in <tt>CMakeCache.txt</tt>, including the options passed to it at the command line. This is useful, as it saves typing the next time you invoke CMake for the project, but it can also be annoying if you are not careful.

The proper way to change the options is to pass them to CMake on the command line, instead of editing directly the CMakeCache file. This way, the make files will be updated in case there is some hidden dependency on the value of the option you are passing.

For example, the next command is a first invocation of CMake for Stellarium that configures the build of a development version for Windows in Release mode which based on revision 5520:
cmake -G "MSYS Makefiles" -DCMAKE_INSTALL_PREFIX=C:/stellarium -DCMAKE_BUILD_TYPE=Release -DRELEASE_BUILD=0 -DBZR_REVISION=5520 ../..

Qt Creator provides a wrapper around CMake - the CMake Wizard. It is automatically launched when Stellarium's CMakeLists.txt is opened for the first time, and it can be launched at any time from the "Build" -> "Run CMake" menu.

===BUILD_FOR_MAEMO===
''Default value'': '''0'''.

This option enables building Stellarium for Maemo devices and also enables optimization for ARM processors.

===BUILD_STATIC_PLUGINS===
''Default value'': '''1'''.

This option defines that plugins should be compiled statically and linked to the main program. ''If this option has value '''1''' then for BUILD_DYNAMIC_PLUGINS should be value '''0'''.''

===BUILD_DYNAMIC_PLUGINS===
''Default value'': '''0'''.

This option defines that plugins should be compiled dynamically. ''If this option has value '''1''' then for BUILD_STATIC_PLUGINS should be value '''0'''.''

===BZR_REVISION===
This option is used together with [[#RELEASE_BUILD|RELEASE_BUILD]] option and sets Bazaar's revision for package.

===CMAKE_BUILD_TYPE===
Possible values: None, Debug, GProf, Valgrind, Release, RelWithDebInfo, MinSizeRel.

''Default value'': '''Debug'''

Possible values:
;Release:Release mode - the binary package does not include debug characters and some of the source code is ignored; this mode is the default for users.
;Debug:Debug mode - the binary package includes debug characters and debug macros in the source code are not ignored; this mode is the default for developers.
;RelWithDebInfo:Release mode, but the binary package includes debug characters; this mode is for developers and users.
;GProf:Support for GNU gprof profiler - binary package includes debug characters for profiler; this mode is for developers
;Valgrind:Support for Valgrind - binary package includes debug characters for memory debugging, memory leak detection, and profiling; this mode is for developers.
;MinSizeRel:Release mode - binary package optimized for minimal size.

===CMAKE_INSTALL_PREFIX===
This option sets a prefix for the installation of the binary package location. Used on Linux to set the location for the software installation, building from source code, the default location is ''/usr/local'' but if you want to install software elsewhere such as into ''/opt'' you need use ''CMAKE_INSTALL_PREFIX=/opt''

===CMAKE_C_COMPILER===
This option sets a custom path to C compiler. For example if you have installed GCC and Clang; and wish to use the Clang compiler you need use ''CMAKE_C_COMPILER=/usr/bin/clang''

===CMAKE_CXX_COMPILER===
This option sets a custom path to the C++ compiler. For example; if you have installed GCC and Clang; to use the Clang compiler you need use ''CMAKE_CXX_COMPILER=/usr/bin/clang''

===ENABLE_NLS===
''Default value'': '''1'''.

This option activates translation with gettext.

===ENABLE_SOUND===
''Default value'': '''0'''.

This option activates sound support.The default value is 0 because sound is not available on all platforms and may require 3rd party software.

===ENABLE_SCRIPTING===
''Default value'': '''1'''.

This option activates the scripting feature.

===ENABLE_SCRIPT_CONSOLE===
''Default value'': '''1'''.

This option activates the script edit console.

===ENABLE_STRATOSCRIPT_COMPAT===
''Default value'': '''0'''.

This option enable the StratoScript compatibility mode. If set to 1 many of the old *.sts scripts can be used.

===GUI_MODE===
Possible values: Standard, None, External

''Default value'': '''Standard'''.

This option set a type of GUI for using in Stellarium.

===OPENGL_MODE===
Possible values: Desktop, ES2

''Default value'': '''Desktop'''.

This option defines mode to supporting OpenGL version - OpenGL for desktops or OpenGL ES

===OPTIMIZE_INTEL_ATOM===
''Default value'': '''0'''.

This option enables optimization for Atom processors.

===RELEASE_BUILD===
''Default value'': '''1'''.

This option flags the build as an official release.

===STELLARIUM_SPLASH===
Possible values: Development, ReleaseCandidate, Release

''Default value'': '''Development'''.

This option set the splash screen for Stellarium.

===USE_PLUGIN_*===
This option is used to build the desired plugin from source. There will be one entry for each plugin being built. For example to build the Historical Supernovae plugin you need use ''USE_PLUGIN_SUPERNOVAE=1''.

Examples of the current default settings;

====*_HELLOSTELMODULE====
''Default value'': '''0'''.

This option defines that the HelloStelModule plugin should be built.

====*_ANGLEMEASURE====
''Default value'': '''1'''.

This option defines that the Angle Measure plugin should be built.

====*_COMPASSMARKS====
''Default value'': '''1'''.

This option defines that the Compass Marks plugin should be built.

====*_SATELLITES====
''Default value'': '''1'''.

This option defines that the Satellites plugin should be built.

====*_TELESCOPECONTROL====
''Default value'': '''1'''.

This option defines that the Telescope Control plugin should be built.

====*_LOGBOOK====
''Default value'': '''0'''.

This option defines that the LogBook plugin should be built.

====*_OCULARS====
''Default value'': '''1'''.

This option defines that the Oculars plugin should be built.

====*_SVMT====
''Default value'': '''0'''.

This option defines that the SVMT plugin should be built. Note: special dependancies and source are required for this option

====*_TEXTUSERINTERFACE====
''Default value'': '''1'''.

This option defines that the Text User Interface plugin should be built.

====*_TIMEZONECONFIGURATION====
''Default value'': '''1'''.

This option defines that the Time Zone Configuration plugin should be built.

====*_VIRGO====
''Default value'': '''0'''.

This option defines that the VirGO plugin should be built. Note: special dependancies and source are required for this option

====*_SOLARSYSTEMEDITOR====
''Default value'': '''1'''.

This option defines that the Solar System Editor plugin should be built.

====*_SUPERNOVAE====
''Default value'': '''1'''.

This option defines that the Historical Supernovae plugin should be built.

====*_QUASARS====
''Default value'': '''1'''.

This option defines that the Quasars plugin should be built.

====*_PULSARS====
''Default value'': '''1'''.

This option defines that the Pulsars plugin should be built.

====*_EXOPLANETS====
''Default value'': '''1'''.

This option defines that the Exoplanets plugin should be built.

==Make targets==

===install===
This option make installation of binaries and related files (installation of program).

===test===
This option launched tests from test suite.

===macosx_bundle===
This option make bundle package for Mac OS X.

===package===
This option make package for Linux.

[[Category: Development]]
[[Category: Customization]]

MediaWiki:Loginstart

2012-10-10T06:54:14Z

Daggerstab: warning

== Warning ==
Due to the increased amount of spam, creating new user accounts has been temporarily disabled. If you need a user account, please write to [https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel Stellarium's '''public''' developers mailing list]. You don't need to subscribe, just send a message to its address.

MediaWiki:Spam-blacklist

2012-10-10T06:43:12Z

Daggerstab:

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki

abercrombie
bathroom
bingo
bracelet
breastpump
casino
cheap
cheapuggs
cigarette
clothing
coupon
crusher
dental
dentist
diamond
essay
estate
homeowners
hosting
insurance
jewellery
jewelry
loan
louisvuitton
market
massage
outlet
poker
psychic
qrops
reviews
surrogate
ticket
uggboot
ukash
vending
watch
yeast
-ugg-

virket\.com
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
blogleaf\.com
palungjit\.com
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

User talk:Didgeweb

2012-10-06T21:24:37Z

Daggerstab: /* Spammers */

Can someone please block user [[User:Thebig-J|Thebig-J]] and its IP address permanently after its major act of vandalism on July 4, 2012?

I think I've undone all of his vandalism. Couldn't restore the links to RefreshLock though.

[[User:Didgeweb|Didgeweb]] 08:03, 5 July 2012 (UTC)

== Mop and bucket ==

I've given you administrator rights (see [[Special:ListGroupRights]]). Now you can delete and protect pages and block people. If blocking spammers, please make sure you check the "block other IP addresses option" and don't block them for more than 3 months - most spammers use botnets and/or proxies, so blocking a user account for an indefinite period of time is pointless. --[[User:Daggerstab|Daggerstab]] 16:06, 9 July 2012 (UTC)

== Wiki Main Page in Italian ==

Hello! I'm new here! How do I start the Italian version of the Wiki Guide? I see that it is available in French, Spanish... And I'd like to create an Italian version too. Help me, please!--[[User:Raniero|Raniero]] 18:46, 20 August 2012 (UTC)
:Thank you!--[[User:Raniero|Raniero]] 15:42, 21 August 2012 (UTC)

== Spammers ==

I've changed the questions that are supposed to deter bots. Let's see if there's any difference. :) --[[User:Daggerstab|Daggerstab]] 21:24, 6 October 2012 (UTC)

User talk:Didgeweb

2012-10-06T21:24:06Z

Daggerstab: /* Spammers */ new section

Download

2012-09-08T16:20:20Z

Daggerstab: /* Official packages */

==Official packages==
The [http://stellarium.org stellarium.org home page] contains links to the latest official releases for Windows, Mac OS, and a source package for Linux. The files themselves are hosted on Stellarium's project page at SourceForge.net:

http://sourceforge.net/projects/stellarium/files/

As of September 2012, the latest version is '''0.11.4'''. Direct links:
* [http://sourceforge.net/projects/stellarium/files/Stellarium-win32/0.11.4/stellarium-0.11.4-win32.exe/download '''Windows''' (32-bit, installer)]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-MacOSX/0.11.4/Stellarium-0.11.4.dmg/download '''Mac OS X''' package] (64-bit, Intel only)
* [http://sourceforge.net/projects/stellarium/files/Stellarium-sources/0.11.4/stellarium-0.11.4.tar.gz/download '''Linux''' tarball (source package)] (for binary packages for Ubuntu, see below)

Older versions can be downloaded from the same place:
* [http://sourceforge.net/projects/stellarium/files/Stellarium-win32/ Windows]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-MacOSX/ Mac OS X]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-sources/ Source packages]

===Stellarium packages for Ubuntu===
====Ubuntu-maintained packages====
If you are running Ubuntu, a Stellarium package exists in the Ubuntu repositories. It can be installed either through the '''Software Center''', or through a terminal with the following command:
sudo apt-get install stellarium

====Stellarium Releases PPA====

As the Stellarium release schedule does not follow closely the Ubuntu release schedule, often the Stellarium version in Ubuntu's repositories is not the latest one. Stellarium's team provides a Launchpad PPA (personal package archive) that allows Ubuntu users to obtain the latest released version.

The page of the PPA in Launchpad is here: [https://launchpad.net/~stellarium/+archive/stellarium-releases Stellarium Ubuntu Releases].

To install the packages from this PPA, you need to add it to your system's Software Sources. The PPA address is:
ppa:stellarium/stellarium-releases

You can add it either in the '''Software Center''' ("Edit" -> "Software Sources..." -> "Other software" -> "Add.."), or with a terminal, using the following commands:

sudo add-apt-repository ppa:stellarium/stellarium-releases
sudo apt-get update
sudo apt-get install stellarium

====Daily Builds PPA====

There is also a "daily builds" PPA that provides automatically built packages from the latest development code. It is updated once daily, or less often if there are no changes to the code.

'''Warning:''' This is provided '''for testing purposes only'''. Nothing guarantees that the latest development code will be usable. Use it at your own risk! (Thankfully, Ubuntu makes removing packages easy.) For that reason, we don't provide detailed instructions for adding this PPA. If you don't know how to use a PPA, you shouldn't use this one.

*[https://code.launchpad.net/~stellarium/+archive/daily Stellarium Daily Builds]

==Unofficial packages==
''Please do not report bugs found in unofficial builds. Also, treat them as you would any software whose source cannot be easily verified (i.e. with caution).''

If you have, or know about, other unofficial builds (previews etc.), please list them here.

===Plugins===
{{obsolete|January 2011}}
====For Stellarium 0.10.2/Ubuntu i386====
* Bundle containing AngleMeasure, CompassMarks, Ocular, TextUserInterface and Satellite plugins. Un-tar this in your ~/.stellarium directory: [http://porpoisehead.net/misc/stellarium-plugin-bundle.tar.bz2 stellarium-plugin-bundle.tar.bz2]

====For Stellarium 0.10.2/Win32====
* Bundle of plugins (AngleMeasure, CompassMarks, Ocular): [http://porpoisehead.net/misc/stellarium-plugin-bundle.exe stellarium-plugin-bundle.exe]
* AngleMeasre 0.0.5 (including configurable display colors via the module.ini file) [http://porpoisehead.net/misc/stellarium-anglemeasure-plugin.exe stellarium-anglemeasure-plugin.exe]
* Satellites plugin installer (v0.1.1): [http://porpoisehead.net/misc/stellarium-satellites-plugin.exe stellarium-satellites-plugin.exe]

====For Stellarium 0.10.5/win32====
* With the release of version 0.10.5 the principal plugins are now static and will be automatically loaded when invoked from the configure menu
* Barry Gerdes maintains some updated pre-built patches and extras for Windows systems, which you can find on [http://sarcasmogerdes.dyndns.org/stellarium his site].

===Telescope Servers===
====Win32 Binaries====
*Zip file containing all the open source telescope servers [http://porpoisehead.net/mysw/downloads/win32_telescope_servers.zip here].

Or individually:
*[http://members.aon.at/johannes_gajdosik/TelescopeServerLx200.exe.gz TelescopeServerLx200.exe.gz]
*[http://members.aon.at/johannes_gajdosik/TelescopeServerNexStar.exe.gz TelescopeServerNexStar.exe.gz]
*[http://members.aon.at/johannes_gajdosik/TelescopeServerDummy.exe.gz TelescopeServerDummy.exe.gz]
Some people have problems with their browsers: the browser silently unpacks the gziped file. If you suffer from such a problem, just rename the downloaded file to TelescopeServerLx200.exe (or similar).

*With version 0.10.5 the expanded telescope control plugin is now loaded and configured from the plugin section of the confugure menu (F2)

Download

2012-09-08T16:10:35Z

Daggerstab:

==Official packages==
The [http://stellarium.org stellarium.org home page] contains links to the latest official releases for Windows, Mac OS, and a source package for Linux. The files themselves are hosted on Stellarium's project page at SourceForge.net:

http://sourceforge.net/projects/stellarium/files/

As of September 2012, the latest version is '''0.11.4'''. Direct links:
* [http://sourceforge.net/projects/stellarium/files/Stellarium-win32/0.11.4/stellarium-0.11.4-win32.exe/download '''Windows''' (32-bit, installer)]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-MacOSX/0.11.4/Stellarium-0.11.4.dmg/download '''Mac OS X''' package]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-sources/0.11.4/stellarium-0.11.4.tar.gz/download '''Linux''' tarball (source package)] (for binary packages for Ubuntu, see below)

Older versions can be downloaded from the same place:
* [http://sourceforge.net/projects/stellarium/files/Stellarium-win32/ Windows]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-MacOSX/ Mac OS X]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-sources/ Source packages]

===Stellarium packages for Ubuntu===
====Ubuntu-maintained packages====
If you are running Ubuntu, a Stellarium package exists in the Ubuntu repositories. It can be installed either through the '''Software Center''', or through a terminal with the following command:
sudo apt-get install stellarium

====Stellarium Releases PPA====

As the Stellarium release schedule does not follow closely the Ubuntu release schedule, often the Stellarium version in Ubuntu's repositories is not the latest one. Stellarium's team provides a Launchpad PPA (personal package archive) that allows Ubuntu users to obtain the latest released version.

The page of the PPA in Launchpad is here: [https://launchpad.net/~stellarium/+archive/stellarium-releases Stellarium Ubuntu Releases].

To install the packages from this PPA, you need to add it to your system's Software Sources. The PPA address is:
ppa:stellarium/stellarium-releases

You can add it either in the '''Software Center''' ("Edit" -> "Software Sources..." -> "Other software" -> "Add.."), or with a terminal, using the following commands:

sudo add-apt-repository ppa:stellarium/stellarium-releases
sudo apt-get update
sudo apt-get install stellarium

====Daily Builds PPA====

There is also a "daily builds" PPA that provides automatically built packages from the latest development code. It is updated once daily, or less often if there are no changes to the code.

'''Warning:''' This is provided '''for testing purposes only'''. Nothing guarantees that the latest development code will be usable. Use it at your own risk! (Thankfully, Ubuntu makes removing packages easy.) For that reason, we don't provide detailed instructions for adding this PPA. If you don't know how to use a PPA, you shouldn't use this one.

*[https://code.launchpad.net/~stellarium/+archive/daily Stellarium Daily Builds]

==Unofficial packages==
''Please do not report bugs found in unofficial builds. Also, treat them as you would any software whose source cannot be easily verified (i.e. with caution).''

If you have, or know about, other unofficial builds (previews etc.), please list them here.

===Plugins===
{{obsolete|January 2011}}
====For Stellarium 0.10.2/Ubuntu i386====
* Bundle containing AngleMeasure, CompassMarks, Ocular, TextUserInterface and Satellite plugins. Un-tar this in your ~/.stellarium directory: [http://porpoisehead.net/misc/stellarium-plugin-bundle.tar.bz2 stellarium-plugin-bundle.tar.bz2]

====For Stellarium 0.10.2/Win32====
* Bundle of plugins (AngleMeasure, CompassMarks, Ocular): [http://porpoisehead.net/misc/stellarium-plugin-bundle.exe stellarium-plugin-bundle.exe]
* AngleMeasre 0.0.5 (including configurable display colors via the module.ini file) [http://porpoisehead.net/misc/stellarium-anglemeasure-plugin.exe stellarium-anglemeasure-plugin.exe]
* Satellites plugin installer (v0.1.1): [http://porpoisehead.net/misc/stellarium-satellites-plugin.exe stellarium-satellites-plugin.exe]

====For Stellarium 0.10.5/win32====
* With the release of version 0.10.5 the principal plugins are now static and will be automatically loaded when invoked from the configure menu
* Barry Gerdes maintains some updated pre-built patches and extras for Windows systems, which you can find on [http://sarcasmogerdes.dyndns.org/stellarium his site].

===Telescope Servers===
====Win32 Binaries====
*Zip file containing all the open source telescope servers [http://porpoisehead.net/mysw/downloads/win32_telescope_servers.zip here].

Or individually:
*[http://members.aon.at/johannes_gajdosik/TelescopeServerLx200.exe.gz TelescopeServerLx200.exe.gz]
*[http://members.aon.at/johannes_gajdosik/TelescopeServerNexStar.exe.gz TelescopeServerNexStar.exe.gz]
*[http://members.aon.at/johannes_gajdosik/TelescopeServerDummy.exe.gz TelescopeServerDummy.exe.gz]
Some people have problems with their browsers: the browser silently unpacks the gziped file. If you suffer from such a problem, just rename the downloaded file to TelescopeServerLx200.exe (or similar).

*With version 0.10.5 the expanded telescope control plugin is now loaded and configured from the plugin section of the confugure menu (F2)

User:Daggerstab

2012-09-08T15:35:40Z

Daggerstab: /* Things that are wrong with this wiki */

'''Daggerstab''' is (the pseudonym of) a Bulgarian programmer.

*[http://badlyhonedbytes.wordpress.com Daggerstab's blog]
*[http://launchpad.net/~stellarium Daggerstab in Launchpad]
*[http://www.ohloh.net/accounts/daggerstab Daggerstab in Ohloh]

== TODO ==
* [[User:Daggerstab/TelescopeControl rewrite]]
* [[Template:User page]] and [[Template:User talk]] (and [[Template:Talk page]])
* Template for easy navigation between languages.
* [[Template:Unsigned]]
* Fixing the help page
* Fixing [[Project:Copyrights]]
* [[/Building Stellarium on Windows with Qt Creator/]]

== Mentions/reviews of Stellarium ==
* [http://astro.nineplanets.org/astrosoftware.html List of planetarium software] on Bill Arnett's Nine Planets website (a.k.a "The List of the Competition" :))
* [http://www.cloudynights.com/item.php?item_id=1896 The Silicon Sky Part I: Planetariums for PCs] (Cloudy Nights, September 2008?)
*Bad Astronomy and Universe Today Forums:
**[http://www.bautforum.com/bad-astronomy-stories/68142-bad-astronomy-stellarium-some-help-here.html Bad Astronomy on stellarium? Some help here?] (December 2007)
**[http://www.bautforum.com/space-astronomy-questions-answers/67770-star-viewing-software-website.html Star viewing software or website?] (December 2007)
**[http://www.bautforum.com/astronomy-cast/87697-free-planetarium-software.html Free Planetarium Software?] (April 2009)

== Other notes ==
The Sky-Watcher family:
* http://www.skywatchertelescope.net/ (main website?)
* http://www.skywatcherusa.com/
* http://www.opticalvision.co.uk/ (UK partner? The Explorer and Skymax brands.)

Windows Build Instructions

2012-09-08T15:27:56Z

Daggerstab: /* Step 2: Qt SDK */ slight edit/update on mingw-get

This document explains how to compile the development version of Stellarium on WinXP. The easiest method is to use QtCreator as described in this page. However it is also possible to compile using MSYS or MS Visual C++. See [[CompileWithMSYS]] and [[CompileWithVisualCpp]].

For 64-bit builds see [[CompileWithMinGW-w64]]

==Building with Qt Creator (Prefered method) ==

Note: This is a patched updated method to allow building from stellarium build 5492

Stellarium can be built in Windows XP as below. If you use Vista 32 bit or Windows 7 32 bit. The procedure should be the same. However I have tried Vista home basic and Qt creator does not work there because it needs cwctype declared. Msys compiling works OK in Vista home. If you have the 64 bit version it will be necessary to install the Virtual XP version from Microsoft (470MB download) and the virtual computer interface from Microsoft or VMware.

Note : I've tested compiling Stellarium with Qt Creator on windows seven and it appears to work fine.

http://www.microsoft.com/windows/win...s-xp-mode.aspx

http://www.microsoft.com/windows/vir.../download.aspx

The virtual XP program will then need to be fully set up as a complete separate virtual XP installation with all the below dependancies including the environment variables. When Stellarium is compiled a package can be made that can be installed in the Program Files (x86)of Windows 7 64 bit (or anywhere else you fancy). Only tested on Windows 7 64 bit ultimate where it runs without problems.

I upgraded my development environment on windows (XP), and decided to
start from scratch, and write what I do. I managed to compile and run
Stellarium pretty quickly *without using the windows command line or
msys* by following these steps.

Go to the [[Bzr checkout|Bazaar checkout instructions]] first.

===Step 1: SVN client===
Install a SVN command line client: CollabNet Subversion Note: This method is no longer applicable since the code is stored in Bazzar. See STEP 7

Command-Line Client works fine.
To get this you will need to register and download
Collabnetsubversion-server-1.6.9-1.win32.exe from
http://www.collab.net (subversion).
Run this and install it in your preferred location or use the default

===Step 2: MinGW and Qt SDK===
At the moment the Qt SDK does not contain the latest versions of Qt 4.8.2 for Windows, MinGW or Qt Creator, so it will be necessary to obtain them and install them individually. Download this for installation after MinGW is installed.

Qt libraries 4.8.2 for Windows (MinGW 4.4, 318 MB)

from http://qt.nokia.com . Remove any earlier version first.

Next we will need the version of MinGW that contains Gettext and libintl versions 0.18.1.1-2. The easiest way to install MinGW and its components is to use mingw-get ([http://sourceforge.net/projects/mingw/files/latest/download download the latest mingw-get]).

It is at the top of the page. Run mingw-get-inst-20120426.exe (662.7kB) and it will install MinGW with GCC 4.6, Libiconv, Gettext-0.18.1.1-2, and libintl-0.18.1.1-2. This is quite a large down load and requires some additions to the starting menu.

In the select components menu MinGW compile suite and the C compiler are already ticked. Add ticks to C++ compiler and the last item MinGW Developer tool kit.

MinGW needs to be installed before any other dependencies as it location must be known by Qt and Msys.

As of build #5572 you will need the updated version of Glext.h from the OpenGL site
http://www.opengl.org/registry/api/glext.h and install it in Mingw\include\gl in lieu of the existing version. Note: This may not be necessary with later updates.

Next we need a copy of Qtcreator, again obtained from http://qt.nokia.com and installed in Qt\4.8.2. Put the new MinGW here also to conform with previous builds.

Now we can install Qt libraries 4.8.2 for Windows (MinGW 4.4, 318 MB) into C:\Qt\4.8.2\Qt rather than the default location of C:\Qt\2010.01

Note: Qt 4.8.2 installation will emit a warning that only MinGW w32api.h version
3.13 is supported. Our new version is 3.17 (newer), and you can safely
ignore the warning and continue.

===Step 3: CMake===
Download cmake 2.8 from http://www.cmake.org
and install it. Remove any earlier versions first

===Step 4: MinGW===
For Qt Creator/cmake to find the mingw environment you now need to
add some directories to your path. Assuming you installed everything
in the location C:\Qt\4.8.2 you should add in your path:

C:\Qt\4.8.2;C:\Qt\4.8.2\qt\bin;C:\Qt\4.8.2\mingw\bin;C:\Program Files\CMake 2.8\bin;
C:\Qt\4.8.2\mingw\lib;C:\Qt\4.8.2\mingw\include

Note: Make sure there is no path to any previous locations of the older versions of gettext, libintl, libiconv-2. Typically in \Program Files\GnuWin32 or \DevCpp from earlier dependencies.

You can edit your path in the "system property" dialog of windows (easy on XP but a little more obscure in Vista and Windows 7). Be very careful editing the path, any syntax errors will stop the creation of the cmakecache.txt when paths can't be found. Remove the paths to other instances of mingw.

You need to (re)start Qt Creator after this.

Gettext, libintl and libiconv will be installed as part of the new MinGW environment.so you will only need zlib

===Step 5: Zlib===
zlib: Download the "Complete package, except sources" installer
from http://gnuwin32.sourceforge.net/packages/zlib.htm and install it
in C:\Qt\4.8.2\mingw\ It will install everything we need in the
mingw environment.

===Step 6: Folder for build===
Create a folder “\prog\ before you start Qt creator.
Start Qt Creator and tell it where your svn.exe is in
Tools/Options../Version Control/Subversion.

My program automatically installed in /program files/Collabnet/subversion Server

===Step 7: Fetch source code===
Create a new project File/New File or Project/Version
Control/Subversion Checkout, and give the following url:

bzr co lp:stellarium

and tell it to put it in the directory of your choice: in my case, I had already
created C:\prog\ The checkout should create the stellarium directory in there and the project headers will be in Documents and settings\your name\stellarium .

===Step 8: Configure===
Once the source code is checked out, Qt Creator automatically
detects a cmake-based project and launches the CMake Wizard. I tell it
to build stellarium in C:\prog\stellarium\qtcreator-build .(default location)
Then run cmake using the MinGW target.
This will configure cmakecache.txt in the qtcreator-build folder (you can edit it if necessary)
If this action fails to find any dependancies. check the cmakecache.txt you may need to manually
install the requirement paths. When this completes OK click on finish.

===Step 9: Building===
If everything went well, click on the "build all" button in Qt
Creator, and wait that everything is build. This can take some time for the first build and
may show many warning messages. Watch the progress "build" bar in the left menu column.
It will turn green when the build is complete.
Click on build issues in lower window and you can see the progress.
(warning messages that don't stop the build or major reasons that do).
When it stops check the qtcreator-build\src folder to see the stellarium.exe and libstelmain.dll files. Copy these files to the stellarium folder.

The Dll's should be found OK if the path is set correctly but it is often better to go to the Qt\4.8.2 and \Mingw folders and copy them from the following sources.

libgcc_s_dw2-1.dll....from qt/4.8.2/MinGW/bin

libiconv2.dll....from qt/4.8.2/mingw/bin

libintl3.dll....from qt/4.8.2/mingw/bin

zlib1.dll .... from qt/4.8.2/mingw/bin

mingwm10.dll....from qt/4.8.2/mingw/bin

libstdc++.dll.... from qt/4.8.2/mingw/bin

phonon4.dll....from qt/4.8.2/qt/bin

Qtcore4.dll....from qt/4.8.2/qt/bin

Qtgui4.dll....from qt/4.8.2/qt/bin

Qtnetwork4.dll....from qt/4.8.2/qt/bin

Qtopengl4.dll....from qt/4.8.2/qt/bin

Qtscript4.dll....from qt/4.8.2/qt/bin

Qtsvg4.dll....from qt/4.8.2/qt/bin

Qtxml4.dll....from qt/4.8.2/qt/bin

To the stellarium folder

10. Run Stellarium and enjoy

==Installing Stellarium ==

Stellarium will be automatically installed into a folder in your boot drive \program files\stellarium when "make install" is run and place the necessary files for use of the inno compiler in sub directories of this folder.

Note: Will someone please show how this is done from Qtcreator?

==Making the Package==

To make an installation package you will first need to download and install the Inno installer

From http://www.jrsoftware.org download isetup-5.2.3.exe, run it to install.

There is a stellarium.iss file in the stellarium source folder that holds the package compiler source to be used with the inno compiler.

This file will look for all the necessary components in a folder \program files\stellarium created by the "make install" command

When all this is prepared it is only necessary to click on the stellarium.iss file to load it and then compile under the build heading.

The package will be built and placed in a new folder created "installers". The package will be "stellarium-0.11.4-win32.exe". This package can then be run on any XP, Vista or Windows 7 computer. Note:- If you are installing on a 64 bit computer the program will need to be placed in the Program files (x86) folder, not the Program Files folder.

MediaWiki:Spam-blacklist

2012-07-22T07:50:53Z

Daggerstab: + "Qrops"

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
dental
massage
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
watch
louisvuitton
abercrombie
abercrombie
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
yeast
surrogate
breastpump
reviews
qrops
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

User:Daggerstab/Building Stellarium on Windows with Qt Creator

2012-07-16T15:02:41Z

Daggerstab: /* Setting environmental variables */

DRAFT
==Install the Qt SDK==
Stellarium is based on the [http://qt.nokia.com/ Qt] framework, so you need to install it. Before, the Qt libraries and [http://qt.nokia.com/products/developer-tools Qt Creator] were distributed separately, but then Nokia integrated all Qt components in a SDK. So you can download a small installer, and select and download only the components you are going to use.

*Qt downloads page: http://qt.nokia.com/downloads
*The "online installer" for Windows is only 15 MB and allows you to pick which components to download and install
*You need Qt Creator and the Qt Desktop libraries (open source, with MinGW), so in the component selection screen:
**Under "Development Tools":
***Under "Desktop Qt", make sure that the latest version of Qt is checked (as of November 2011, that is 4.7.4). Under the version number, select only "'''Desktop Qt 4.7.4 - MinGW'''"
***Make sure "'''Qt Designer'''" is selected
***You probably don't need anything else under "Development Tools", so feel free to uncheck the rest.
**'''Under "Miscellaneous", make sure that "MinGW 4.4" is checked.''' You don't need the source code. You may need the Qt Examples only if you are a programmer and you want to contribute to Stellarium - they will be useful to understand Qt.
**You need "Documentation" only if you are a programmer who wishes to contribute to Stellarium.
**You don't need "APIs" and "Experimental".

Even if you miss anything at this point, you can install it later with the "Maintain Qt SDK" application (it can be found in the Start menu after the installation is complete).

'''Remember where you install the Qt SDK, because you'll need it later.'''

==Install some GnuWin libraries==
Stellarium needs <code>gettext</code>, <code>libiconv</code> and <code>zlib</code>. You can get them form the GnuWin project:
*http://gnuwin32.sourceforge.net/packages/gettext.htm
*http://gnuwin32.sourceforge.net/packages/libiconv.htm
*http://gnuwin32.sourceforge.net/packages/zlib.htm

For all of them, download the "Complete package, except sources" executable installer. Run the installers and let them install the libraries to the directory they want. It should be something like <code>C:\Program Files\GnuWin32</code>

==Setting environmental variables==
You need to add a few paths to your PATH environmental variable. On Windows, you can modify it with a configuration window: right click on your "My computer" and select "Properties". It's somewhere there, under "Environmental Variables". :)

'''WARNING:''' Don't just blindly copy the paths. Make sure that these directories exist and that the Qt version number is the same as yours.

'''TIP:''' The environmental variables window allows you to modify and define variables separately for the current user and for the system. There should be already a "Path" variable defined for the system, but not for the user. Instead of modifying the system PATH, it is more convenient to define a user PATH (just click on the "New..." button and fill in the boxes).

If you have let the Qt SDK install itself in its default location, the path to the Qt libraries should be something like <code>C:\QtSDK\Desktop\Qt\4.7.4\mingw</code> You need to add three subdirectories to the PATH variable:
C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin
C:\QtSDK\Desktop\Qt\4.7.4\mingw\lib
C:\QtSDK\Desktop\Qt\4.7.4\mingw\include

You also need to add the MinGW directories themselves:
C:\QtSDK\mingw\bin
C:\QtSDK\mingw\lib
C:\QtSDK\mingw\include

And the GnuWin libraries:
C:\Program Files\GnuWin32\bin
C:\Program Files\GnuWin32\lib
C:\Program Files\GnuWin32\include

All elements of the list should be separated with a semicolon (;). So the end result should look something like this:
<code>C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin;C:\QtSDK\Desktop\Qt\4.7.4\mingw\lib;C:\QtSDK\Desktop\Qt\4.7.4\mingw\include;C:\QtSDK\mingw\bin;C:\QtSDK\mingw\lib;C:\QtSDK\mingw\include;C:\Program Files\GnuWin32\bin;C:\Program Files\GnuWin32\lib;C:\Program Files\GnuWin32\include</code>

==Install CMake==
CMake download page: http://www.cmake.org/cmake/resources/software.html

And interesting bug: As of 9 November 2011, if you use CMake 2.8.*, on Windows 7, Qt Creator won't show you Stellarium's source file tree in the "Projects" panel. Download and use '''CMake 2.6.4''' (from the same website). If you have any idea why this is happening, contact us in the Stellarium developers mailing list or the Feedback forums.

During the installation, make sure to tell the installer that CMake should be added to the system PATH (for all users). This will save you editing it manually. :)

==Get Stellarium's code==
:''See the [[Bzr checkout|Bazaar checkout instructions]]''

==Opening Stellarium with Qt Creator==
Open Qt Creator.

Open "File" -> "Open File or Project..." (or just press Ctrl+O).

Find the folder where you have put Stellarium's files. Open the topmost <code>CMakeLists.txt</code> file - the one that is '''at the same level''' as the <code>README</code> file and the <code>/src</code> and <code>/data</code> directories.

A "CMake Wizard" window will open. It is small and inconvenient to use. You can resize it to a larger size.
*In the "Build Location" step, there will be a default path already in the location field. '''''Ignore it'''''. Instead:
**Select your base Stellarium location, the same directory where the <code>CMakeLists.txt</code> file was. For example, <code>D:\stellarium\trunk</code>
**Then, add <code>\builds\msys</code>. The whole path should look like something like this:<code>D:\stellarium\trunk\builds\msys</code>
**The point is that this will allow you to run Stellarium directly from inside Qt Creator without having to copy files or to create an installer and install Stellarium.
*In the "Run CMake step", there is an "Arguments" field where you can set CMake command-line arguments.
**You can use it to set Stellarium's pseudo-installation directory. This is necessary only if you want to use a trick useful to translators (described below) or to create an executable installer. Just type in <code>-DCMAKE_INSTALL_PREFIX=c:\stellarium-temp\</code>, where <code>c:\stellarium-temp\</code> is the path to the pseudo-installation directory. (It is not necessary to exist, CMake will create it.)
**When you are done with the arguments, click on the "Run CMake" button. CMake will start and its log will be displayed in the box below. If everything is OK, the last lines will be something like: "Configuring done. Generating done. Build files have been written to <your build directory>" The "Finish" button will be enabled. Click it to close the wizard.

After you close the wizard, Qt Creator should open the project.

'''Tip:''' You can always run again CMake by choosing "Run CMake" from the "Build" menu.

==Building Stellarium==

==Running Stellarium==
You can run the freshly-built Stellarium from inside Qt Creator. You only need to fix the default working directory first.

From the left column, select "Projects" (or press Ctrl+5). Then select the "Run Settings" tab. On that page, under "Run", there must be a "Working directory:" field with a path that looks like this:
C:\stellarium\trunk\builds\msys\src

Select and remove the <tt>builds\msys\src</tt> tail so that the path looks like this:
C:\stellarium\trunk\

After that, you can run the build by clicking on the green arrow button in the left column (or pressing Ctrl+R). You can also run the project in debug mode, etc.

If you have forgotten to set the correct working directory, Stellarium will crash when you try to run it and it will display a "WARNING: could not locate installation directory" error in the log.

==Creating an installer==

===Inno Setup and the project file===
Stellarium uses [http://www.jrsoftware.org/isinfo.php Inno Setup] to create its Windows installers (the self-extracting setup files), so you need to download and install Inno Setup first.

The Inno Setup project file that contains the rules for creating the installer is called <tt>stellarium.iss</tt>. It is generated from the template <tt>stellarium.iss.cmake</tt> when you run CMake, so:
* To have <tt>stellarium.iss</tt>, you need to have run CMake and/or built Stellarium at least once.
* If you run CMake (or build Stellarium?) after you've made changes to <tt>stellarium.iss</tt>, they will be overwritten, so be careful - always keep in mind what changes do you want to make and why, and in which file do you need to make them.

===Building in "install" configuration===
TODO
- add screenshots
To generate an installer, you need to have something to install. Make sure you build Stellarium in the normal way first.

After that, you need to "build" it in an "install" configuration, the equivalent of running <tt>make install</tt> from the command line. Before trying to do it, though, please make sure that you've set the <tt>CMAKE_INSTALL_PREFIX</tt> parameter as described [[#Opening Stellarium with Qt Creator|above]]. If you haven't done it, run CMake again with the appropriate parameters. (You can trigger a new run of CMake at any time - from the "Build" menu at the top select "Run CMake".)

You need to add the build configuration only once per object. From the left column, select "Projects" (or press Ctrl+5). In the "Build Settings" tab, look at the first line: "Edit build configuration:". Click on the "Add" button, then select "Clone selected" from the menu. (This will create a copy of the current configuration, which should be "all".) In the small window that appears, type a name for the new configuration ("install" will do). Make sure that the new configuration is selected in the first box on the same line, then look below for the "Make Steps" section. There should be a "Make:" field containing something like this:
mingw32-make.exe
Click on the "Details" button to the right. More controls should fold out. In the "Additional arguments:" field, type <tt>install</tt>, then click on the "Details" button again to fold the controls. The "Make:" field should now read:
mingw32-make.exe install
That's it, you can now use the new build configuration.

To change the current build configuration, press Ctrl+T (or click on the computer screen icon labelled "Stellarium" in the left column). In the box that opens, the "Build:" drop down list should offer two options - "all" and whatever name you gave the "install" configuration.

So, to build Stellarium in the "install" configuration, make sure that it is selected and then just trigger a new build (for example, by pressing Ctrl+B). The <tt>make</tt> script will then copy all the necessary files to the temporary installation directory that you have set.

If you need only to (re)compile Stellarium after that, open the build configuration selection window again and select "all".

===Running Inno Setup===
After Stellarium has been built in the "install" configuration (which should have copied the necessary files to the temporary installation directory), open the <tt>stellarium.iss</tt> file with Inno Setup (just double-click it). You can make some final changes before running the script.

By default, the new installer will be created in the <tt>/installers</tt> sub-directory in the main directory of your Stellarium working tree. Bazaar is set to ignore it, so you can't accidentally commit a setup file to the repository.

==Using translations==

TO BE CONTINUED

MediaWiki:Spam-blacklist

2012-07-13T19:04:28Z

Daggerstab: + massage

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
dental
massage
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
watch
louisvuitton
abercrombie
abercrombie
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
yeast
surrogate
breastpump
reviews
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

Android port

2012-07-09T18:18:43Z

Daggerstab: update on the Stellarium Mobile situation

Experimental port of Stellarium to Android using not-yet-complete Android port of Qt, [http://sourceforge.net/p/necessitas/home/necessitas/ necessitas].

This is an experimental branch built on an incomplete library and is '''not yet ready for public consumption'''.

An official public release won't happen until some time after necessitas reaches Beta, and this port is sufficiently mature, whichever comes later; testing releases will probably start well before then.

You can build it at any time, though (see: '''[[Building for Android]]'''). If you want to help out in any way with development, it would be appreciated.

This page is development-centric right now; most of this will have to be spun off into another page at some point.

<div class="toc">'''Note''': There is a '''paid''' [https://play.google.com/store/apps/details?id=com.noctuasoftware.stellarium ''Stellarium Mobile''] port for Android by [http://www.noctua-software.com/ Noktua Software]. It is based on Fabien Chereau's ''Stellarium Mobile'' fork/port for Nokia smartphones. (For those who don't know, Fabien is Stellarium's original author. Noktua Software is a small company set up by Fabien and his brother.) There used to be another port on Google Play that used the same name without permission, but it apparently was taken down at the time the NS port was uploaded (some time in June 2012). Both apps are not related to the port discussed on this page - it uses a novel UI and '''it will not cost anything''' when it eventually makes it onto Google Play and elsewhere.</div>

== Specification / design ==
See: '''[[Android port/Specification]]''' for a detailed breakdown of the current design. Technical implementation details are broken-up into tasks below.

== Communication ==

* IRC channel: [irc://irc.freenode.org/stellarium #Stellarium] on [http://freenode.net/ freenode]. Webchat client: [http://webchat.freenode.net/?channels=stellarium&uio=MTE9MjQ255]
* Development mailing list: [https://sourceforge.net/mailarchive/forum.php?forum_name=stellarium-pubdevel]
* [https://sourceforge.net/projects/stellarium/forums/forum/278769 Feedback forum]
* Please ''don't'' submit bugs related to the port to Launchpad ''yet''. Add them to the Wiki under New Issues, and/or pop on IRC. Anything that seems incomplete probably is.

== Remaining tasks ==
=== Rough timeline ===
(This is a rough timeline / list of ''remaining'' feature tasks; some completed items may be in here, most not. Bugs and general issues are below, and slot into the timeline ''somewhere'')
* Complete first releasable QML-based GUI
** <strike>Design GUI</strike>
** Get GUI basically operational
*** <strike>Hook QML up, and a non-functional UI minus configuration dialogs</strike>
*** <strike>Pinch-zoom</strike>
*** <strike>Get a the main GUI view actions doing something (playback, accelerometer (not hooked up, but maybe print something))</strike>
*** Add button tooltips
*** Add View / Markings / Plugin dynamic button drawers
** Fix the static plugins
*** Some don't support ES 2. Based on IRC discussions, these plugins should be, whenever possible, doing their drawing through StelPainter and ''not'' accessing OpenGL directly
*** plugins know too much about the GUI; they access the concrete StelGui directly to create buttons, rather than the abstract StelGuiBase
** <strike>Add pretty, Android-styled button icons
*** Decide on DPI buckets
*** Add a custom image provider for icons. This image provider will choose the correct icon based on the DPI bucket we're in. This process will be transparent to QML; all it needs to do is use use this image provider (e.g. <code>Image{ source: "scaled://image.png" }</code>), and it'll get the image from the correct bucket</strike>
** Add search
*** ...
** Add settings screen
*** Create item types, a view, and a basic model
*** Hook items up to backend
*** Refine items, view and model
*** Have multiple list views working, along with categories
*** Complete the models (with most necessary settings)
** Add locations screen
*** <small>A specialized settings screen with a little image of the Earth and such</small>
*** Design
*** Implement
*** Hook up to GPS/location/(orientation?) plugin
**** Plugin doesn't exist yet. [http://doc.qt.nokia.com/qtmobility/location-overview.html#controlling-aspects-of-data-sources QtMobility's location support] looks like it supports desktop OSs, so this plugin would be useful for more than just mobile
** Cook up additional layouts (small phone, 5" tablet, 7" tablet, 10" tablet)
*** Design
*** Implement
* Add Android art (icon, replace necessitas' splashscreen, etc.)
* Consider beginning preliminary ("pre-alpha") testing
* Localization support
** Autodetect locales via JNI
*** This works; however, we need to manually fall back when we don't have the language+country, as this isn't handled by libintl-lite. For instance: if the locale requests "fr_CA" (which doesn't exist), we should fall back to "fr" (sans country code). Currently it just fails and falls back to "C" (English/US, the default)
** Ensure that everything in QML is translatable, and in the gettext files
* Accelerometer support
* Fix large bugs and feature requests from pre-Alpha
* Alpha testing
* Optimize
** Implement ETC1 texture compression
*** ETC1 may have issues with large chroma shifts, which could render it useless for us. If so, may have to use device-specific texture compression formats. => more work. We may want to move that way ''eventually'' anyways
** Profile OpenGL
** Profile with gprof or callgrind
** Optimization ideas:
*** Consider ways of reducing per-frame accuracy for performance/battery use boost (value caching, lerping and dead reckoning instead of recalculating constantly)
* Fix most Alpha bugs, any particularly large ones
* Implement big/easy Alpha feedback
* "Beta" test
** Dependent on Necessitas hitting Beta; until it does, spin around 'alpha' versions
* Implement beta feedback items
* Fix as many bugs as is feasible
* Add remaining Android art: all ''Google Play''-required items (banners, large icon, etc.)
* (Eventually) - First public ''Google Play'' / other sources release, followed by bug fixing and more bug fixing

=== Other tasks ===
* add-ons (additional catalogues and such) downloadable via Google Play to reduce bandwidth load from Android users?
* [http://stackoverflow.com/questions/9219747/how-to-block-the-back-key-in-android-when-using-qt] control the back key
* find the ''correct'' location for the user's External Storage via JNI
* location and orientation support
** ''scientes'' suggested on IRC that we might create a multiplatform Location plugin, using QtMobility's [http://doc.qt.nokia.com/qtmobility/location-overview.html Location API]. This API appears to support desktop as well as mobile clients.
*** the location API should supported by necessitas, but may require some minor Android-specific hacks. See [https://groups.google.com/forum/#!topic/android-qt/1pAnsyy84tQ] and [https://sourceforge.net/p/necessitas/tickets/147/]

=== Art ===
The following art is needed. Each section of art is accompanied with a link to the specification page describing what that piece of art is used for.

==== Raster artwork ====

Note that 1dp = 1px at 160dpi. Google recommends using a 3:4:6:8 scaling ratio for assets for screens of different densities; this means we'll end up having 4 sets of most every piece of art; to convert from dp to pixels for each of the groups:
* 0.75x
* 1.0x
* 1.5x
* 2.0x

The Android GUI design guidelines are at [http://developer.android.com/guide/practices/ui_guidelines/index.html] as well as [http://developer.android.com/design/index.html]

Android artwork can be found in the AOSP repositories. The [http://developer.android.com/design/index.html Android design] site also has vector art, but it's under a somewhat vague license (unrestricted use ''to develop your apps''). Much of the same art is available rasterized in AOSP's repository (under the Apache license 2.0) though.

==== Vector artwork ====

Vector artwork (in SVG format) can also be used. In that case, one can include them for as many of the above groups as desired. Simple icons may just be one image; more complex ones might have a simpler fallback for lower-DPI screens so that they don't end up as a blur.

==== Art grouping ====

Currently, the art resides in <code>data/mobileGui</code> in the following directories:
* images-ldpi (low DPI; 0.75x scaling factor)
* images-mdpi (medium DPI; 1.0x scaling factor)
* images-hdpi (high DPI; 1.5x scaling factor)
* images-xhdpi (extra-high DPI; 2.0x scaling factor)
* images (used as a fallback if no images were found in the above directories; most vector art is here)
* images-nodpi (non-scaled images; images here ''shouldn't'' have duplicates in the above directories)

==== 'Action bar' icons ====
The current thought is to imitate Android's Action Bar to provide a layout that's consistent with other Android apps. Standard size for an Action Bar icon in Android 4.0, according to the Android Design guidelines, is 32dp x 32dp.

The Action Bar itself is 48dp high.

The Action Bar logo (see [[Android_port/Specification]]; the icon on the far-left of the bar) should be larger than the other icons. It can be the same size as the launcher icon. In fact, it can be the same image as the launcher icon, or it can be a variant with larger margins, whatever works best.

There's more details in the guidelines, but Google says they should be flat (not shaded, outlined, or shadowed), pictographic, and #ffffff at 80% opacity (*** I think it's a good idea if we just do the opacity programatically. Make the image 100%, have Stellarium do 80% or 30% depending on if it's enabled or disabled. Halves the number of images we need to bother with...). If we diverge from that, we should keep things consistent.

If we're doing activated/deactivated icons like Stellarium does, the deactivated ones should probably still be fairly bright (near or at #ffffff). Mobile devices vary in screen quality, and are frequently used with low brightness settings and in adverse lighting conditions.

Icons. 32dp unless otherwise noted, and ''all four sizes are needed'' (see above):
* [[Android_port/Specification#Main_view]]
** Action Bar Logo (48dp)
*** related: left arrow ( see [[Android_port/Specification#Playback]] ) for the Action Bar logo when it becomes a back button (is not displayed otherwise). There's an Android asset for this.
** Open search
** Open controls
** Toggle accelerometer (on / off)
** . . . / maximize sidebar (standard Android-style)

* [[Android_port/Specification#Object_selected]]
* (these should probably be shadowed or outlined as they don't have a background behind them)
** Deselect object
** Center on object
** (Center and zoom to object?)
** Toggle info (two states: brief / long)

* [[Android_port/Specification#Playback]]
** Rewind (on / off)
** 1x speed (on / off)
** Current time (on / off)
** Fast forward (on / off)

* [[Android_port/Specification#Search]]
** Search

* [[Android_port/Specification#Pull-down bar]]
** Close/minimize sidebar
** Night vision mode
** Date/Time
** Location
** Settings
** Information box
** Objects dialog
*** for enabling/disabling stars, planets, etc.
** Markings dialog
*** likewise for markings; grids, constellations, etc.
** View/misc dialog
*** everything else. Oculars, equitorial/altaz toggle, etc.
** <strike>Plugins dialog</strike>

==== Android / Google Play art ====
[https://support.google.com/googleplay/android-developer/support/bin/answer.py?hl=en&answer=1078870]

This time, all sizes in '''pixels''' and only one size needed unless otherwise noted
* Launcher icons (48dp; need all four sizes, so 36px, 48px, 72px, 96px)
* High Resolution Application Icon (512x512, 32-bit PNG with alpha; Max size of 1024KB)
* Promotional graphic (optional) (180w x 120h, 24 bit PNG or JPEG (no alpha), Full bleed, no border in art)
* Feature graphic (optional) (1024w x 500h, 24 bit PNG or JPEG (no alpha) with no transparency; all important elements within 924x400 safe zone in center of image

==== Other art ====
* Qt splashscreen (any size)
** the same size as the normal splash is probably fine; 512x512. Or anything smaller. Or larger, even. Will be placed in the center of the screen and scaled ''down'' uniformly until it fits in view
** this is shown ''before'' the normal Stellarium splashscreen, but this one doesn't have a version # or anything else on it that isn't baked-in (so yes, we get two splash screens, so this should probably not be a repeat of the other one)

== New issues ==


== Known issues ==
* Performance and CPU usage need to be looked at (above)
* Check for NPOT texture support (driver may be returning true even if it's not)
** do we care?
* App should be suspended or outright killed when it's switched away from, as it continues to go full tilt and drain battery
* need to (re)disable "Zoom to Fullscreen" option on tablets
* it occasionally crashes very soon after starting; usually shortly after, or even during the loading screen
** it ''may'' happen more frequently immediately after installing the app. The log and logcat output show nothing interesting.
** this is associated with startup somehow; after the ~30 second mark, I've not seen it crash. I've had it running overnight unintentionally without instability.
** this occurs on only one of my two devices, and somewhere deep in the GPU driver's code. May be a driver issue, though that doesn't mean we can't find a way to avoid it (assuming we're doing something to aggravate it, not necessitas, which is unclear)

=== Issues waiting for necessitas ===
* [https://sourceforge.net/p/necessitas/tickets/120/ necessitas bug #120] prevents us from using the package's Assets directory, as we would ideally do. For now, manually copy the files that get placed in stellarium/android/java/assets to /sdcard/stellarium on the device.
** there's a fix that's yet to be reviewed
* <strike>resuming the app (switching to another app, then back before Android closes it) results in a blank screen
** there's a not-yet-reviewed fix for this as well</strike>
* [https://groups.google.com/d/topic/android-qt/7rCEv7ddtmU/discussion]
* [https://sourceforge.net/p/necessitas/tickets/169/ issue 169] - soft keyboard always resizes window

== Misc notes ==

* [https://groups.google.com/forum/?fromgroups#!topic/android-qt/vtVVr__wxuw]

== Contributing ==

=== Building ===

See: '''[[Building for Android]]'''

=== Contributing ===

Right now, the main thing I need is development help. Please feel free to lend a hand; create a branch off the current one (see [[Building for Android]]) and go to town. Read above for means of communication.

Translators and testers will be needed at some point.

MediaWiki:Spam-blacklist

2012-07-09T16:08:11Z

Daggerstab: + "dental"

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
dental
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
watch
louisvuitton
abercrombie
abercrombie
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
yeast
surrogate
breastpump
reviews
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

User talk:Didgeweb

2012-07-09T16:06:54Z

Daggerstab: /* Mop and bucket */ new section

User talk:Daggerstab

2012-07-09T16:01:45Z

Daggerstab: /* Thebig-J */

=== Cleaning up fake user accounts? ===
Hi Daggerstab,

Now that you've activated the user creation log, it seems that a lot of fake user accounts are continuously created. It might be that the number of fake users is already quite large. Would it be an idea (if this isn't done automatically yet) to delete users, older than say 3 months, who never contributed anything? Might clean up the wiki database quite a bit.

Cheers and keep up the good work as admin!

[[User:Didgeweb|Didgeweb]] 18:36, 1 December 2010 (UTC)
:I thought the creation log was visible before? Anyway, I haven't done anything special about it. The MediaWiki software that runs the wiki was updated to a newer version yesterday.
:The new accounts that have appeared today are spammers, but the SpamBlacklist extension is finally working properly and they can't post their spam. :)
:As far as I know, user accounts can't be deleted without editing directly the SQL database. I prefer not to do that. :)
:I can try to put some kind of captcha verification on the registration page. This will solve the problem with new registrations, if these are bots, but not if they are humans.--[[User:Daggerstab|Daggerstab]] 18:50, 1 December 2010 (UTC)

== Thebig-J ==
Hi Daggerstab. If you're still active, can you look into Thebig-J's behavior?
Cheers

[[User:Didgeweb|Didgeweb]] 03:55, 6 July 2012 (UTC)

Блок со мной, если хочешь, я никогда больше не будет. Во всяком случае, я не знаю Stellarium.

:I've blocked them. I'll probably give you Administrator rights later, after I check the current condition of the wiki. I haven't logged in for some time.--[[User:Daggerstab|Daggerstab]] 15:57, 9 July 2012 (UTC)

Thanks :-) Guess I missed one page when reverting.

[[User:Didgeweb|Didgeweb]] 15:58, 9 July 2012 (UTC)
:The user contributions page lists for which pages the user have made the last edit. They are marked with '''(top)''', see for example [[Special:Contributions/Daggerstab]]. :) --[[User:Daggerstab|Daggerstab]] 16:01, 9 July 2012 (UTC)

User talk:Daggerstab

2012-07-09T15:57:36Z

Daggerstab:

Najczęściej zadawane pytania

2012-07-09T15:50:20Z

Daggerstab: Reverted edits by Thebig-J (talk) to last revision by Eland

{| cellpadding="8"
| bgcolor=green | '''Uwaga: to FAQ jest krótką listą odpowiedzi na wspólne problemy.'''
To nie jest to samo co [[:Category:User's Guide|podręcznik użytkownika]], który zapewnia o wiele bardziej szczegółowe informacje na temat korzystania ze Stellarium, krajobrazów, dostosowywania, astronomii, itp. Ta strona to absolutne minimum.
|}

==Pytania ogólne==

===Co to jest Stellarium?===
Stellarium to wolnodostępne planetarium dla Linux/Unix, Windows i MacOSX. Renderuje niebo w czasie rzeczywistym przy użyciu OpenGL, co oznacza że niebo wygląda tak jak w rzeczywistości przy oglądane za pomocą oczu, lornetki, lub małego teleskopu. Stellarium jest bardzo proste w użyciu, co jest jedną z jego największych zalet: może być z powodzeniem używane przez początkujących.
Projekt Stellarium został zapoczątkowany przez Fabien Chéreau latem 2001 i korzysta intensywnie z witryny Sourceforge. Dostęp do strony projektu na Sourceforge [http://sourceforge.net/projects/stellarium/ tutaj].

===Czy Stellarium jest za darmo?===
Oczywiście! Stellarium to wolne oprogramowanie. Każdy ma prawo do pobierania, korzystania z programu za darmo, rozpowszechniania bez modyfikowania kodu, lub zmiany kodu źródłowego, wszystko na warunkach określonych w [http://www.gnu.org/copyleft/gpl.html Powszechnej Licencji Publicznej GNU (GPL)].

===Gdzie mogę pobrać Stellarium?===
Ze [[Pobieranie|strony pobierania]]. Stellarium jest hostowane na serwerach Sourceforge. Po kliknięciu na prawidłowy link ze strony pobierania, zostaniesz przeniesiony na listę serwerów Sourceforge, z których każdy ma inną lokalizację. Wybierz serwer geograficznie najbliższy Tobie, zapewni to szybsze pobieranie.

===Gdzie mogę przekazać swoje uwagi?===
Twoje pomysły i uwagi są bezcenne dla Stellarium. Rzuć okiem na [http://www.stellarium.org stronę główną], aby zobaczyć, gdzie można uzyskać wsparcie osobiste, poprosić o nowe funkcje, zgłosić błąd, a nawet przedstawić własne poprawki.

==Instalacja Stellarium==

===Jakie są wymagania systemowe Stellarium?===
Karta graficzna zdolna do renderowania OpenGL. Minimalnie Riva TNT2, wydana w 1999 lub 2000. Stellarium wykorzystuje intensywnie procesor, więc więcej klatek na sekundę uzyskasz na szybszym procesorze. Każdy dość nowy komputer powinien być w stanie uruchomić Stellarium. Dostępne są wersje programu pracujące w środowisku Linux, Windows lub MacOSX.

Aby pokazać Ci możliwości instalacji programu, z sukcesem uruchomiliśmy go na poniższych konfiguracjach sprzętowych:
*Pentium III 800Mhz, 128MB RAM, karta graficzna Intela (w systemie Windows XP).
*AMD K6 400 Mhz, 256MB RAM, Nvidia GeForce2 AGP, DirectX 9.0 (Windows XP)
*Mac PowerPC około 667MHz, uruchomione przynajmiej na OSX 10.3.9, wszelkie Mac Intel

===Jak zainstalować Stellarium?===
Dla użytkowników Windows, uruchom pobrany plik "setup.exe" i postępuj zgodnie z instrukcjami.
Dla użytkowników Linux, najprościej jest znaleść skompilowaną paczkę dla Twojej dystrybucji.
Ale jest możliwość skompilowania programu samodzielnie: szczegółowe instrukcje dotyczące [http://www.stellarium.org/wiki/index.php/Kompilacja_pod_Linuksem kompilacji pod Linux-em], Posix, Cygwin i MacOSX są dostępne w pliku "INSTALL". Użytkownicy Mac OS X powinni pobrać plik dmg, kliknąć dwukrotnie, aby otworzyć, aplikacja jest zawarta wewnątrz, przenieś aplikację do Twojego folderu aplikacji.

===Jak odinstalować Stellarium?===
* Dla użytkowników Windows, odinstaluj Stellarium za pomocą "Dodaj/Usuń programy" w Panelu Sterowania.
* Dla użytkowników Linux, użyj menedżera pakietów jeśli zainstalowałeś binarne pakiety dla Twojej dystrybucji.
* Jeśli został skompilowany samodzielnie, można odinstalować poprzez wpisanie "make uninstall" w katalogu kompilacji.
* Jeśli został skompilowany samodzielnie, uruchomiłeś jako root make install, i usunąłeś katalog kompilacji
** Po pierwsze ściągnij ponownie (jeśli to konieczne) i rozpakuj '''pakiet źródłowy dla wersji, którą masz zainstalowaną'''
*** Aby sprawdzić jaką masz wersję wykonaj polecenie: <code>stellarium --version</code>
** Aby odinstalować uruchom: <code>./configure && sudo make uninstall</code>

==Korzystanie ze Stellarium==

===Jak rozpocząć korzystanie ze Stellarium?===
*Najpierw ustaw lokalizację! Domyślną lokalizacją jest Paryż, Francja. Możesz wybrać swoją lokację klikając na mapie lub ustawiając współrzędne. Nie zapomnij zapisać zmian. Zrób to klikając "Ustaw jako domyślne". Od teraz, niebo będzie wyglądać dokładnie tak jak w twojej lokalizacji w rzeczywistości. Oczywiście, jeśli zabierzesz Stellarium w podróż na laptopie, możesz zmienić swoją lokalizację.
*Użyj myszki lub klawiszy strzałek, aby się rozejrzeć.
*Użyj klawiszy Page Up i Page Down, aby przybliżyć i pomniejszyć.
*Użyj lewego przycisku myszy, aby wybrać obiekt, prawy przycisk, aby odznaczyć obiekt i środkowy przycisk lub spację, aby wyśrodkować wybrany obiekt.
*Powiększanie do mgławic i planet jest bardzo ciekawe...
*J spowalnia lub odwraca czas, L zwiększa szybkość, a K sprawia, że czas powraca do normalnej prędkości.
*Naciśnij F1, aby uzyskać pomoc.

===Jak mogę zmienić rozdzielczość do takiej której nie ma w konfiguracji?===
Stellarium uruchomiony jest na laptopie z panoramicznym ekranem i nie ma opcji określających twoją rozdzielczość. W takim przypadku wystarczy otworzyć plik config.ini w edytorze tekstu i znaleźć wartości screen_w i screen_h. Ustaw numery do żądanych wymiarów, zapisz plik i ponownie uruchom Stellarium: ciesz się widokiem!

===Czy istnieje instrukcja obsługi do Stellarium?===
Tak. Dowiedz się więcej o Stellarium i astronomicznych zasadach zademonstrowanych w programie. Lektura. [[:Category:User's_Guide|Kliknij tutaj, aby uzyskać więcej informacji]]

===Jak ustawić określoną datę w inny sposób niż klikając setki razy przycisk zmiany roku?===
Konkretną datę można wpisać używając menu tekstowego (zwanego też tekstowym interfejsem użytkownika, w skrócie TUI):
#Naciśnij klawisz '''m''' w celu wywołania TUI;
#Za pomocą klawiszy kursora przejdź do pozycji '''2.1 Czas widoku nieba''';
#Używając klawiszy kursora lewo/prawo podświetl rok/miesiąc/dzień/godzinę do zmiany.
#Wybraną wartość można zwiększać i zmniejszać za pomocą klawiszy kursora góra/dół;
można też po prostu wpisać żądaną wartość;
#Naciśnij ENTER albo ESC aby powrócić do wyboru pozycji menu TUI (jeśli chcesz jeszcze zmieniać jakieś inne opcje), albo po prostu naciśnij '''m''' aby zamknąć TUI.
'''Uwagi:'''
* W wersji 0.9.1 występuje błąd polegający na tym, że nie da się wybrać lat wcześniejszych niż 1 r. p.n.e. Pracujemy nad rozwiązaniem go.
* TUI jest '''wyłączone''' w wersjach od 0.10.0 (beta) do 0.10.2. Opracowywany jest nowy tekstowy interfejs użytkownika, który w przyszłości zostanie udostępniony w postaci wtyczki do programu. Praktycznie to samo można osiągnąć w wersji 0.10.5 w oknie zmiany czasu wywołanym klawiszem F5.

==Dostosowywanie==

===Jak mogę korzystać z innych obrazów konstelacji w Stellarium?===
Chciałbyś wyświetlać inne rysunki niż te, które są zawarte w programie Stellarium, np. swoje własne albo starożytne ryciny z Uranografii?

Będziesz musiał zmienić tekstury konstelacji i ewentualnie dostosować swoje współrzędne w pliku constellationsart.fab.
Jeśli nie są obciążone ograniczającymi prawami autorskimi, możesz udostępnić zestaw reszcie społeczności.

===Czy można wyświetlać więcej gwiazd?===
Stellarium używa katalogu Hipparcos, który zawiera ponad 120000 gwiazd. Obecnie nie jest możliwe użycie innych katalogów gwiazd. Dodatkowe gwiazdy do programu Stellarium można znaleźć na stronie projektu w serwisie Sourceforge:
http://sourceforge.net/project/showfiles.php?group_id=48857&package_id=233730

W wersji 0.10.2, w oknie ustawień i zakładce narzędzia można bezpośrednio pobrać dodatkowe katalogi z milionami gwiazd.

===Czy Stellarium dostępne jest w moim języku?===
Począwszy od wersji 0.8.0, Stellarium może porozumiewać się w Twoim języku. Ustawienia są w oknie preferencji lub w pliku config.ini. Możliwe jest, że tłumaczenie nie jest jeszcze kompletne, więc bylibyśmy wdzięczni, jeżeli utalentowany tłumacz wśród społeczności Stellarium przyczynił się do tłumaczenia. Informacje na temat tego procesu na [[Translation using gettext|stronie tłumaczenia]].

==Problemy==

===Nie mogę zainstalować Stellarium.===
Przeczytaj instrukcje instalacji zawarte w pliku "INSTALL", z którym dostarczane jest Stellarium.

===Stellarium installs, but does not run.===
'''0.9.0 / OSX''' If you have upgraded from an older version of Stellarium, and your old config.ini file was set so that Stellarium started in full screen mode, 0.9.0 will fail to start. Just edit your config.ini file and edit the line with the fullscreen setting so the value is false.

For other problems, we can offer some accounts of what people experienced in the past. Maybe a file necessary for Stellarium was corrupted or badly formatted in some way. Try reinstalling, don't forget to backup any Stellarium files you might have customized.

Stellarium reports basic actions on standard output and standard error. This output can be read in the cmd window on Windows, or can be seen by starting Stellarium from a terminal in Linux and OS X. Have a read of this output and see if there is any helpful information. If you can't fix your problem, post a support request, and include this output.

====Message on console, "locale::facet::_S_create_c_locale name not valid"====
If stellarium does not start, and you see this message on the console:
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
Abort trap

Try setting the LC_ALL environment variable to "C" and re-run.

===Stellarium działa bardzo wolno, ,mam mało klatek na sekundę.===
Dzieję się tak, gdy jest wyłączone przyspieszenie sprzętowe. Jeśli masz kartę graficzną 3D, upewnij się, czy sterowniki OpenGL są zainstalowane i aktualne.

===Stellarium zawiesza się albo ulega awarii po pewnym czasie od uruchomienia.===
Stellarium wykorzystuje dość dużo mocy procesora. Oznacza to, że elementy wewnątrz komputera mogą się dość mocno nagrzewać. Jeżeli komputer zacznie się zawieszać albo pojawią się błędy, to prawdopodobnie jest to związane z dużą ilością wydzielanego ciepła. Jeśli tak jest, to inne zadania wymagające dużej mocy procesora, takie jak kodowanie mp3, będą źródłem takich samych problemów. W najnowszych wersjach Stellarium można ograniczyć liczbę generowanych klatek obrazu na sekundę. Włączenie tej funkcji powinno rozwiązać problem.

===Niektóre księżyce są w innym miejscu, niż powinny być.===
Obecnie nie mamy dokładnych danych położenia Charona i ogólnie wszystkich satelitów Neptuna. Pozostałe położenia satelitów powinny być poprawne. Jeśli porównać z tym, co widać przez teleskop należy włączyć czas propagacji światła w config.ini.

===W programie nie są wyświetlane poprawnie polskie znaki diakrytyczne===
Język polski jest poprawnie obsługiwany w Stellarium. Jedyną przyczyną może być brak odpowiedniej czcionki na Twoim komputerze. Znajdź właściwą i poinstruuj program by ją używał za pomocą wpisu w pliku config.ini. Strona:
[[Display complex characters in Stellarium]] zawiera więcej szczegółów.

===Stellarium działa w trybie pełnoekranowym z częstotliwością odświeżania 60Hz===
Jest to błąd w systemie Windows XP. Istnieją liczne poprawki i mały program dostępny tutaj (instalujesz na własną odpowiedzialność): [http://www.pagehosting.co.uk/rl/ RefreshLock].

===Mój lokalny język nie jest kompletny lub niektóre terminy są nieprawidłowe===
Tłumaczenia w Stellarium są pracą społeczności, więc jest możliwe że lokalny tłumacz rozpoczął tłumaczenie, ale nie ukończył go lub nie znalazł odpowiednich słów. Możesz nam pomóc! Wskazówki dotyczące tłumaczenia są na tej stronie: [[Translation using gettext]]

===Występują problemy z wyświetlanym obrazem (np. zamiast liter wyświetlane są punkty)===
Przyczyny mogą być różne, poczynając od braku elementów interfejsu Stellarium przez problemy związane z wyświetlaniem tekstu (na kartach graficznych S3 i ATI Rage) aż do braku danych na temat gwiazd. Tego rodzaju błędy występują głównie na starszym sprzęcie i na określonych wbudowanych układach graficznych (jednemu z użytkowników układu GeForce 4 MX udało się rozwiązać problem przywracając starszą wersję sterownika - 5.2.1.6). Radzimy spróbować dokonać zmian związanych ze sterownikiem grafiki (zaktualizować go, zmienić ustawienia, przywrócić jedną ze starszych wersji) pod warunkiem, że się na tym znasz. Użytkownicy mający kłopoty z układami graficznymi S3 powinni zaktualizować zainstalować aktualny sterownik, tj. sterownik S3 Graphics ProSavageDDR dla Windows XP.

Wiele programów poprawiających wygląd graficznego interfejsu użytkownika albo umożliwiających zastosowanie kompozycji (tematów) lub skórek w systemie Windows może wywołać problemy z aplikacjami OpenGL, w tym również ze Stellarium. Spróbuj wyłączyć wszelkie programy tego typu (jeśli masz je zainstalowane), takie jak: WindowBlinds, WindowFX, ObjectDock, IconPackager, Entbloess (oraz podobne).

===I can't record scripts (on Windows)===
:'''''Note:''' Since version 0.10.1, Stellarium has a new scripting engine. The text bellow applies to versions prior to that.''
Stellarium attempts to save a Stellarium script file (.sts) in your user directory. On international versions of Windows, this doesn't work perfectly yet, as the program is looking for the English "Documents and Settings" folder. Workaround: open the stderr.txt file in the Stellarium directory to see where Stellarium is trying to write, create that folder, and you should be able to record scripts now.

===W trybie pełnoekranowym nadal częściowo widać pulpit (dotyczy Windows)===
Jeśli korzystasz z WindowBlinds albo innego programu zmieniającego wygląd systemu za pomocą skórek, to wyłącz go, ewentualnie dodaj Stellarium do listy aplikacji, których wygląd ma pozostać niezmieniony.

===Nie można zapisywać zrzutów ekranu (w systemie Windows Vista)===
Vista nie pozwala większości programów zapisywać plików na pulpicie. Można wybrać inny katalog do zapisu plików poprzez zmianę skrótu (w menu Start), który jest używany do uruchamiania Stellarium, na następujący:

stellarium.exe --screenshot-dir "C:\Ścieżka\Do\Katalogu"

W wersji 0.10.1 katalog do zapisu zrzutów ekranu można ustawiać bezpośrednio w interfejsie użytkownika, mianowicie w zakładce ''Narzędzia'' okna ''Konfiguracja''.

==Różne==

===Czy wolno zamieszczać zrzuty ekranu Stellarium w książkach / na stronach WWW / w kalendarzach itp.?===
Przypuszczalnie tak. Przeczytaj [https://sourceforge.net/forum/message.php?msg_id=4720018 ten wątek na forum] - omawiane są tam prawne konsekwencje korzystania ze zrzutów ekranu Stellarium. Jeżeli rozpoczynasz przedsięwzięcie biznesowe, to prawdopodobnie powinieneś przedyskutować tę kwestię z prawnikiem i/lub wydawcą.

==="Brakuje roku zerowego", "Daty przed naszą erą są przesunięte o rok"===
Stellarium w wersji 0.9.1 i późniejsze używają [http://en.wikipedia.org/wiki/Astronomical_year_numbering astronomicznej numeracji lat].

Tradycyjna numeracja BC/AD (czy też p.n.e./n.e.) nie uwzględnia roku 0, ponieważ stworzono ją w czasach gdy w Europie liczba zero nie była zbyt szeroko znana. Dlatego też przed rokiem 1 n.e. jest rok 1 p.n.e. Powoduje to problemy z obliczeniami arytmetycznymi, więc astronomowie używają zwykle innej numeracji - lata naszej ery oznacza się liczbami dodatnimi, a rok 1 p.n.e. zamieniony jest na rok 0. Stąd:

{| class="wikitable" cellspacing="8" style="text-align:center"
|-
! Kalendarz gregoriański !! N.e./p.n.e. !! Numeracja astronomiczna
|-
|2 AD || 2 n.e. || 2
|-
|1 AD || 1 n.e. || 1
|-
|1 BC || 1 p.n.e. || 0
|-
|2 BC || 2 p.n.e. || -1
|-
|3 BC || 3 p.n.e. || -2
|-
|}
Zobacz też [http://sunearth.gsfc.nasa.gov/eclipse/SEhelp/dates.html to krótkie wyjaśnienie na stronie NASA].

MediaWiki:Spam-blacklist

2012-04-29T09:49:22Z

Daggerstab:

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
watch
louisvuitton
abercrombie
abercrombie
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
yeast
surrogate
breastpump
reviews
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

Creating a Personalised Landscape for Stellarium

2012-04-29T09:48:11Z

Daggerstab: Reverted edits by Grado (talk) to last revision by Gzotti

{{ActualVersion|0.10.6}}
Although this procedure is based on the Microsoft Windows System the basics will apply to any platform that can run the programs mentioned or similar programs on the preferred system.

The first thing needed for a personalised landscape to superimpose on the horizon display is a 360° panorama with a transparent background. To make this you will need the following:
* A digital camera on a tripod or stable platform
* A program to convert the pictures into a 360° panorama
* A program to remove the background and convert the panorama into about 8 square pictures in PNG format for insertion into Stellarium as the sides and if possible a similar square picture of the base you are standing on to form the ground. This last requirement is only really possible if this area is relatively featureless as the problem of knitting a complex base is well nigh impossible.
* Patience. (Maybe a soundproof room so that the swearing wont be heard when you press the wrong key and lose an hours work)

==The Camera==
Digital cameras are easy and cheaply available these days so whatever you have should do. One mega-pixel resolution is quite sufficient.

The camera needs to be mounted on a tripod so that reasonably orientated pictures can be taken. Select a time of day that is quite bright with a neutral cloudy sky so there will be no shadows and a sky of the same overall texture. This will make it easier to remove later. The pictures were all saved in the JPG format which was used as the common format for all processes up to the removal of the background.

With a camera that takes 4:3 ratio pictures I found 14 evenly spaced pictures gave the best 360° panorama in the program I used to produce it.

==Processing into a Panorama==
This is the most complicated part of the process of generating the panorama. I used two separate programs to do this. Firstly I used Microsoft Paint which is part of the Windows operating system, to cleanup and resize the pictures to 800x600 size and so make them easier to handle in the panorama program.

If you have prominent foreground items like posts wires etc. that occur in adjacent pictures the panorama program will have difficulty in discerning them because of the 3D effect and may give double images. I overcame this by painting out the offending item by cut and paste between the two pictures. Quite easy with a little practice using the zoom in facility and I found the MSpaint program the easiest to do this in.

When I had my 14 processed pictures I inserted them into the panorama program. I used a program called the Panorama Factory. Version 1.6 is a freebee that works well and can be downloaded from the internet - a Google search will find it. I used version 3.4 that is better and cost about $40 off the Internet. This program has many options and can be configured to suit most cameras and can make a seamless 360° panorama in barrel form that will take a highly trained eye to find where the joins occur.

The resulting panorama was then loaded into Paint and trimmed to a suitable size. Mine ended up 4606 x 461 pixels. I stretched the 4606 to 4610 pixels, almost no distortion, that would allow cutting into 10 461x461 pictures at a later date. If the height of the panorama had been greater I could have made fewer pictures and so shown more of the foreground.

http://www.stellarium.org/wikiimg/UserManual/landscape_beaumonthills.jpg

==Removing the background to make it transparent==
This is the most complex part of the process and requires a program that can produce transparency to parts of your picture, commonly called an alpha channel. Two programs I know of will do this. The very expensive and sophisticated Adobe Photoshop and a freebee called The Gimp.

I used Photoshop to produce the alpha channel because selection of the area for transparency was more positive with the complex skyline I had and I had learnt a little more on how to drive it before I found an executable form of The Gimp. For the rest I used a combination of both programs. I will describe the alpha channel process in detail for Photoshop. A lot of this would be suitable for The Gimp as they are very similar programs but I have only tried the bare essential in The Gimp to prove to myself that it could be done.

<ol>
<li> Load the panorama picture into Photoshop.</li>
<li> Create an alpha channel using the channel pop up window. This channel was then selected as the only channel visible and it was all black at this stage. It needs to be all white. To edit this took me some time to discover how. What I did was click on Edit in Quick mask mode and then Edit in standard mode. This procedure was the only way I found I could edit. Click on the magic wand and click it on the channel picture. It will put a mask around the whole picture. Next I selected the brush tool and toggled the foreground to white and painted the whole channel white (using a very large brush size 445 pixels).</li>
<li> Next I turned the alpha channel off and selected the other channels to get the original picture. I got rid of the full mask that I had forgotten to remove by selecting Step backwards from the edit menu. I first tried the magnetic loop tool to select the sections for a mask but it was too fiddly for me. I then used the magic wand tool to select the sky sections bit by bit (zoom in on the image to see what you are doing) this would have been easy if the sky had been cloudless because colour match does this selection. I cut each selection out. It took about an hour to remove all the sky (because it was cloudy) and leave just the skyline image as a suitable mask. Clicking the magic wand in the sky area when all the sky has been removed will show an outline mask of the removed sky. Zoom in and carefully check the whole area to make sure there is no sky left. Leave this mask there.</li>
<li> Re-select the alpha channel and turn the other channels off. The alpha channel will be visible and the mask should be showing. Re-select Edit in Quick mask mode and then Edit in standard mode to edit. Select the brush tool and toggle to the black foreground. Fill in the masked area with a large brush size. The colour (black) will only go into the masked area. It wont spill over so the job is quite easy.</li>
<li> When this is done you will have created your alpha layer. Check the size of the image and if it is greater than 5000 pixels wide reduce its size by a fixed percentage till it is under this limit. The limit was necessary for one of the programs I used but may not be always necessary. However any greater resolution will be wasted and the file size will be excessive. Save the whole image in the compressed tiff form or PNG form. The only formats that preserve the alpha channel.</li>
<li> This image is the horizon picture. Give it a name .tif or .png, whichever format you save it in.

After making the ''panorama.tif'' I noticed that the trees still had areas of the original sky embedded that were not blanked by the alpha layer. I found that I could add these sections piece by piece to the alpha layer with the magic wand and paint them out. This took some time, as there were a large number to be removed. However the result was worth the effort, as it allows the sky display to be seen through the trees. Especially at high zooms ins.

Another little trick I discovered was that the panorama could be saved as a JPEG file (no alpha channel) and the alpha channel also saved as a separate JPEG file. This can save space for transmission. And allow manipulation of the original file in another program as long as the skyline is unchanged. At a later date the two files can be re-combined in Photoshop to re-form the TIFF file with alpha channel.

Using this trick I did a little patching and painting on the original picture in Paint on the original JPEG form. When completed I loaded it into Photoshop and added the blank alpha channel to it. I was then able to paste the previously created alpha layer into the new picture. It worked perfectly.</li>
<li> The panorama now needs to be broken up into suitable square images for insertion into a landscape. It took me some time to get the hang of this but the process I found best was in The Gimp. It was the easiest to cut the main panorama into sections as it has a mask scale in the tool bar.</li>
<li> Load the panorama file with alpha channel into The Gimp. Then using the mask tool cut out the squares of the predetermined size starting from the left hand side of the picture. I don't think it is necessary to make them exact squares but I did not experiment with this aspect. The position of the cut will be shown on the lower tool bar. Accuracy is improved if you use the maximum zoom that will fit on the page.</li>
<li> Create a new picture from the file menu then select and adjust the size to your predetermined size then select transparent for the background. Because of the alpha channel the transparent section will be automatically clipped of much of the transparent part of the picture. Paste the cutting into the new picture. If it is smaller than your predetermined size it will go to the centre leaving some of the transparent background at the bottom of the picture. Save the file in the PNG format. Moving the picture to the bottom of the window is much easier in Photoshop although quite possible in The Gimp.</li>
<li> I repeated steps 8 and 9 till I had all sections of the panorama saved.</li>
<li> Next I re-loaded Photoshop and opened the first of the saved pictures. Then from the menu selected the picture with the mask tool and then selected move. Next clicking on the picture will cut it out. The cutting can now be dragged to the bottom of the frame. It will not go any further so there is no trouble aligning. This bottom stop did not work on The Gimp and so it was harder to cut and place the picture section. It is most important to align the pictures to the bottom. </li>
<li> Save the picture with the name you intend to call your landscape as ''xxxxxx1.png''.</li>
<li> Repeat steps 11 and 12 for the rest of the pictures till you have all the elements for your landscape.</li>
<li> Make a new directory for the landscape. This should be a sub-directory of either the ''<user directory>/landscapes'' or ''<installation>/landscapes'' directory. The name of the directory should be unique to your landscape, and is the landscape ID. The convention is to use a single descriptive word in lowercase text, for example gueriens. Place your pictures your new directory.</li>
<li> In your new landscape directory, create a new file called ''landscape.ini'' file (I used wordpad). Add a line for the '''[landscape]''' section. It's probably easiest to copy the ''landscape.ini'' file for the Gueriens landscape and edit it. Edit the name Guereins in every instance to the name you have given your landscape. Don't forget to make the number of tex entries agree with the number of your pictures. If you haven't made a groundtex picture use one of the existing ones from the file or make a square blank picture of your own idea. Because I took my pictures from the roof of the house I used an edited picture of the roof of my house from Google Earth. It was pretty cruddy low resolution but served the purpose.</li>
<li> Next you need to orientate your picture North with true North. This is done roughly by making the arrangement of side1 to siden suit your site as close as possible. Now you need to edit the value of '''decor_angle_rotatez''' to move your landscape in azimuth. Edit '''decor_alt_angle''' to move you landscape in altitude to align your visible horizon angle. Edit '''ground_angle_rotatez''' to align your ground with the rest of the landscape. If you know (or have even measured) these angles, use the flag '''calibrated=true''' (since 0.10.6; this activates a bugfix especially notable if you have high trees!) Leave the other entries, they are suitable as is.</li></ol>

After re-starting Stellarium, your landscape will appear in the landscape tab of the configuration window, and can be selected as required.

{{Template:LRCNavigation|Star Catalogue|Stellarium User Guide|Sky Guide}}

[[Category:Stellarium User Guide]]

User talk:Brady Brenot

2012-04-24T15:29:22Z

Daggerstab: Mop and bucket

== Mop and bucket ==

I've given you administrator rights (see [[Special:ListGroupRights]]). Now you can delete and protect pages and block people. If blocking spammers, please make sure you check the "block other IP addresses option" and don't block them for more than 3 months - most spammers use botnets and/or proxies, so blocking a user account for an indefinite period of time is pointless. You can also edit the blacklists - [[MediaWiki:Spam-blacklist]] and [[MediaWiki:Titleblacklist]] (there are also analogous whitelists).--[[User:Daggerstab|Daggerstab]] 15:29, 24 April 2012 (UTC)

Telescope Control plug-in

2012-04-24T15:20:01Z

Daggerstab:

<div style="margin-bottom:25px; background-color:silver; padding:7px; border:solid 1px #847f93;">'''Warning:''' The information on this page is '''not''' up-to-date. The version of the Telescope Control plug-in released with Stellarium 0.10.5 is newer and has a slightly different interface. This page will be updated later.</div>

:''See [[Telescope Control]] for general information about telescope control in Stellarium.''
----
The Telescope Control plug-in allows Stellarium to control a telescope on a computerized mount (a "Go To" or "Push To" telescope) and offers a graphical user interface for setting up the connection.

It has been included as a static plug-in in Stellarium since version 0.10.3.

This page covers version 0.1.9, the one distributed with Stellarium 0.10.3 and 0.10.4.

== Abilities and limitations ==
This plug-in allows Stellarium to send only "'''slew'''" ("go to") commands to the device and to receive its current position. It cannot issue any other commands, so users should be aware of the possibility for mount collisions and similar situations. (To abort a slew, you can start another one to an object in a safe position.)

As of the current version, this plug-in doesn't allow satellite tracking, and is not very suitable for Moon or planetary observations.

<span style="color: red; font-weight: bolder">WARNING: Stellarium CANNOT prevent your telescope from being pointed at the Sun.</span>
* Never point your telescope at the Sun without a proper solar filter installed. The powerful light amplified by the telescope WILL cause irreversible damage to your eyes and/or your equipment.
* Even if you don't do it deliberately, a slew during daylight hours may cause your telescope to point at the sun on its way to the given destination, so it is strongly recommended to avoid using the telescope control feature before sunset without appropriate protection.

== Using the Telescope Control plug-in ==

There are two general ways to control a device with this plug-in, depending on the situation:
* '''DIRECT CONNECTION''': A [[#Supported devices|device supported by the plug-in]] is connected with a cable to the computer running Stellarium;
* '''INDIRECT CONNECTION''':
** a device is connected to the same computer but it is driven by a [[Telescope Control (client-server)|stand-alone telescope server program]] or a [[Telescope Control#Third party applications|third-party application]] ''that can "talk" to Stellarium'';
** a device is connected to a remote computer and the software that drives it can "talk" to Stellarium ''over the network''; this software can be either one of Stellarium's stand-alone telescope servers, or a third party application.

Most older telescopes use cables that connect to a {{wikipedia-en|serial port}} (RS-232), the newer ones use {{wikipedia-en|Universal Serial Bus|USB}} (Universal Serial Bus). On Linux and Max OS X both cases are handled identically by the plug-in. On Windows, a USB connection may require a "virtual serial port" software, if it is not supplied with the cable or the telescope. Such a software creates a virtual ("fake") COM port that corresponds to the real USB port so it can be used by the plug-in.

Telescope set-up (setting geographical coordinates, performing alignment, etc.) should be done before connecting the telescope to Stellarium.

To activate the Telescope Control plug-in:
* open the Configuration window (press F2);
* go to the Plugin tab;
* select "Telescope Control" from the list;
* check the "Load at startup" option;
* exist Stellarium.
The plug-in should be active the next time you start Stellarium.

=== Main window ===
The plug-in's main window can be displayed by pressing Alt+0 or the "Telescopes window" button on the bottom toolbar.

http://img201.imageshack.us/img201/6854/telescopecontroltabtele.png

The '''Telescopes''' tab displays a list of the telescope connections that have been set up:
* the number ('''#''') column shows the number used to control this telescope. For example, for telescope #2, the shortcut is Ctrl+2.
* the '''Status''' column indicates if this connection is currently active or not. Unfortunately, there are some cases in which "Connected" is displayed when no working connection exists.
* the '''Type''' field indicates what kind of connection is this:
** '''local, Stellarium''' means a DIRECT connection to the telescope (see [[# Using the Telescope Control plug-in|above]]);
** '''local, external''' means an INDIRECT connection to a program running on the same computer;
** '''remote, unknown''' means an INDIRECT connection over a network to a remote machine.

To set up a new telescope connection, press the '''Add''' button. To modify the configuration of an existing connection, select it in the list and press the '''Configure''' button. In both cases, a telescope connection configuration window will open.

=== Telescope connection configuration window ===
The telescope connection configuration window ([http://img201.imageshack.us/img201/1958/telescopecontroladdtele.png full image])...

==== Connection type ====
The topmost field represents the choice between the two types of connections, DIRECT and INDIRECT respectively (see [[# Using the Telescope Control plug-in|above]]):

http://img697.imageshack.us/img697/9157/telescopecontrolconnect.png

The type of connection determines what information should be entered in the other fields, so it is at the top.

==== Telescope properties ====
http://img89.imageshack.us/img89/7180/telescopecontrolproptel.png
;Name
:The name of the telescope that will be displayed on the screen next to the telescope reticle.
;Connection delay
:If the movement of the telescope reticle on the screen is uneven, you can try increasing or decreasing this value.
;Start/connect at startup
:Check this option if you want Stellarium to attempt to connect to the telescope immediately after it starts. Otherwise, to start the telescope, you need to open the main window, select that telescope and press the "Start/Connect" button.

==== Device settings ====
This section is active only for DIRECT connections (see [[#Connection type]]).

http://img89.imageshack.us/img89/9915/telescopecontrolpropdev.png
;Serial port
:sets the serial port used by the telescope.
:The list contains the default values for the first four serial ports. On Windows, these are COM1 to COM4, on Linux these are /dev/ttyS0 to /dev/ttyS3, on Mac OS X the list is empty as it names its ports in a peculiar way. On all three platforms '''the list can be edited and new values can be added'''. (If you are using a USB cable, the default serial port of your telescope most probably is not in the list.)
:To list all valid serial port names in Mac OS X, open a terminal and type:
:<pre>ls /dev/*</pre>
:This will list all devices, the full name of your serial port should be somewhere in the list (for example, "/dev/cu.usbserial-FTDFZVMK").
:On Mac OS X 10.6. / 64bit it might be that the original drivers from Prolific do not actually connect to the NexStar-based hand controller even though it shows "connected" in the telescope control. A remedy is to download a driver (for the Prolific 2303-based adapters) which is 64bit compatible. One solution could be the driver from this homepage: http://sourceforge.net/projects/osx-pl2303/:

;Device model
:see [[#Supported devices]] below.

==== Connection settings ====
http://img697.imageshack.us/img697/1374/telescopecontrolpropcon.png

Both fields here refer to communication over a network ({{wikipedia-en|TCP/IP}}). Doing something with them is necessary only for INDIRECT connections.

'''Host''' can be either a host name or an {{wikipedia-en|IPv4}} address such as "127.0.0.1". The default value of "localhost" means "this computer".

'''Port''' refers to the TCP port used for communication. The default value depends on the telescope number and ranges between 10001 and 10009.

Both values are ignored for DIRECT connections. (Unless a certain option is checked, but this is [[#Advanced use]].)

For INDIRECT connections, modifying the default host name value makes sense only if you are attempting a remote connection over a network. In this case, it should be the name or IP address of the computer that runs a program that runs the telescope.

==== Field of view circles ====
A series of circles representing different fields of view can be added around the telescope marker. This is a relic from the times before the [[Ocular plugin|Oculars plug-in]] existed.

http://img638.imageshack.us/img638/8056/telescopecontrolcircles.png

In the telescope configuration window, click on "User Interface Settings". Mark the "Show FOV circles" options, then enter a list of values separated with comas in the field below. The values are interpreted as degrees of arc.

This can be used in combination with the [[#Stellarium Virtual Telescope]] to display a moving marker with the Telrad circles. In this case, the list of FOV values should be "0.5, 2, 4".

=== Sending commands ===
Once a telescope is successfully started/connected, Stellarium displays a telescope reticle labelled with the telescope's name on its current position in the sky. The reticle is an object like every other in Stellarium - it can be selected with the mouse, it can be tracked and it appears as an object in the Search window.

To send a "slew" command to the telescope, select an object (e.g. a star) and press the number of the telescope while holding down the Ctrl key. (For example, Ctrl+1 for telescope #1.)

As of version 0.1.9/Stellarium 0.10.4, there is no way to slew to a specific set of coordinates.

=== Stellarium Virtual Telescope ===
If you want to test this plug-in without an actual device connected to the computer, choose "Stellarium Virtual Telescope" from the "Device model" list. It will show a telescope reticle that will react in the same way as the reticle of a real telescope controlled by the plug-in. In this case, the value of "Serial port" is ignored.

See the section above about [[#Field of view circles]] for a possible practical application.

This feature is a (descendant?) of the "Dummy" type of telescope in [[Telescope Control (client-server)|the old way of doing things]].

== Advanced use ==

== Supported devices ==
:''Main page: [[Telescope Compatibility]]''

All devices (except [[#Stellarium Virtual Telescope|one]]) listed in the [[#Device settings|"Device model" list]] are convenience definitions using one of the two built-in interfaces: the Meade LX200 (the Meade Autostar controller) interface and the Celestron NexStar interface.

The device list contains the following:
;Celestron NexStar (compatible)
:Any device using the NexStar interface.
;Losmandy G-11
:A computerized telescope mount made by Losmandy. (Meade LX-200/Autostar interface)
;Meade Autostar Compatible
:Any device using the LX-200/Autostar interface.
;Meade ETX-70 (#494 Autostar, #506 CCS)
:The Meade ETX-70 telescope with the #494 Autostar controller and the #506 Connector Cable Set. According to the tester, it is a bit slow, so its default setting of [[#Telescope properties|"Connection delay"]] is 1.5 seconds instead of 0.5 seconds.
;Meade LX200 (compatible)
:Any device using the LX-200/Autostar interface.
;[[#Stellarium Virtual Telescope|Stellarium Virtual Telescope]]
: A fake telescope. :)
;Wildcard Innovations Argo Navis (Meade mode)
:Argo Navis is a "Digital Telescope Computer" by Wildcard Innovations. It is an advanced digital setting circle that turns an ordinary telescope (for example, a dobsonian) into a "Push To" telescope (a telescope that uses a computer to find targets and human power to move the telescope itself). Just don't forget to set it to Meade compatibility mode and set the baud rate to 9600B. [http://www.iceinspace.com.au/forum/showpost.php?p=554948&postcount=18]

Not included in the device list (for now):
;Sky-Watcher SynScan AZ mount
:The Sky-Watcher SynScan AZ GoTo mount is used in a number of telescopes. [http://www.opticalvision.co.uk/astronomical_telescopes/sky-watcher/sysncan_az_go-to_computerised_telescopes] '''SynScan''' is also the name of the hand controller used in other Sky-Watcher GoTo mounts, and it seems that any mount that uses a SynScan controller version 3.0 or greater is supported by the plug-in, as it uses the NexStar protocol. To use any of these mounts with the plug-in, choose '''Celestron NexStar (compatible)''' from the device list.

== External links ==
* [http://www.youtube.com/watch?v=bxOP-thX2ts Controlling the Meade ETX-LS 6 with Stellarium], a YouTube video by John Kramer
* [http://www.iceinspace.com.au/63-581-0-0-1-0.html Ice in Space » Stellarium Telescope Control with a HEQ5/EQ6], an article by Karl van Louwersen on how to use this plug-in with StellariumScope and EQMOD

[[Category: Telescope Control]]
[[Category: Plugins]]

MediaWiki:Spam-blacklist

2012-04-23T11:20:06Z

Daggerstab: + "watch"

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
watch
louisvuitton
abercrombie
abercrombie
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
yeast
surrogate
breastpump
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

User:Daggerstab/Building Stellarium on Windows with Qt Creator

2012-04-14T15:25:37Z

Daggerstab: /* Creating an installer */

DRAFT
==Install the Qt SDK==
Stellarium is based on the [http://qt.nokia.com/ Qt] framework, so you need to install it. Before, the Qt libraries and [http://qt.nokia.com/products/developer-tools Qt Creator] were distributed separately, but then Nokia integrated all Qt components in a SDK. So you can download a small installer, and select and download only the components you are going to use.

*Qt downloads page: http://qt.nokia.com/downloads
*The "online installer" for Windows is only 15 MB and allows you to pick which components to download and install
*You need Qt Creator and the Qt Desktop libraries (open source, with MinGW), so in the component selection screen:
**Under "Development Tools":
***Under "Desktop Qt", make sure that the latest version of Qt is checked (as of November 2011, that is 4.7.4). Under the version number, select only "'''Desktop Qt 4.7.4 - MinGW'''"
***Make sure "'''Qt Designer'''" is selected
***You probably don't need anything else under "Development Tools", so feel free to uncheck the rest.
**'''Under "Miscellaneous", make sure that "MinGW 4.4" is checked.''' You don't need the source code. You may need the Qt Examples only if you are a programmer and you want to contribute to Stellarium - they will be useful to understand Qt.
**You need "Documentation" only if you are a programmer who wishes to contribute to Stellarium.
**You don't need "APIs" and "Experimental".

Even if you miss anything at this point, you can install it later with the "Maintain Qt SDK" application (it can be found in the Start menu after the installation is complete).

'''Remember where you install the Qt SDK, because you'll need it later.'''

==Install some GnuWin libraries==
Stellarium needs <code>gettext</code>, <code>libiconv</code> and <code>zlib</code>. You can get them form the GnuWin project:
*http://gnuwin32.sourceforge.net/packages/gettext.htm
*http://gnuwin32.sourceforge.net/packages/libiconv.htm
*http://gnuwin32.sourceforge.net/packages/zlib.htm

For all of them, download the "Complete package, except sources" executable installer. Run the installers and let them install the libraries to the directory they want. It should be something like <code>C:\Program Files\GnuWin32</code>

==Setting environmental variables==
You need to add a few paths to your PATH environmental variable. On Windows, you can modify it with a configuration window: right click on your "My computer" and select "Properties". It's somewhere there. :)

'''TIP:''' The environmental variables window allows you to modify and define env-variables for the current user and for the system. There should be already a "Path" variable defined for the system, but not for the user. Instead of modifying the system PATH, it is more convenient to define a user PATH (just click on the "New..." button and fill in the boxes).

If you have let the Qt SDK install itself in its default location, the path to the Qt libraries should be something like <code>C:\QtSDK\Desktop\Qt\4.7.4\mingw</code> You need to add three subdirectories to the PATH variable:
C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin
C:\QtSDK\Desktop\Qt\4.7.4\mingw\lib
C:\QtSDK\Desktop\Qt\4.7.4\mingw\include

You also need to add the GnuWin libraries:
C:\Program Files\GnuWin32\bin
C:\Program Files\GnuWin32\lib
C:\Program Files\GnuWin32\include

All elements of the list should be separated with a semicolon (;). So the end result should look something like this:
<code>C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin;C:\QtSDK\Desktop\Qt\4.7.4\mingw\lib;C:\QtSDK\Desktop\Qt\4.7.4\mingw\include;C:\Program Files\GnuWin32\bin;C:\Program Files\GnuWin32\lib;C:\Program Files\GnuWin32\include</code>

'''Warning:''' Don't just blindly copy the paths. Make sure that these directories exist and that the Qt version number is the same as yours.

==Install CMake==
CMake download page: http://www.cmake.org/cmake/resources/software.html

And interesting bug: As of 9 November 2011, if you use CMake 2.8.*, on Windows 7, Qt Creator won't show you Stellarium's source file tree in the "Projects" panel. Download and use '''CMake 2.6.4''' (from the same website). If you have any idea why this is happening, contact us in the Stellarium developers mailing list or the Feedback forums.

During the installation, make sure to tell the installer that CMake should be added to the system PATH (for all users). This will save you editing it manually. :)

==Get Stellarium's code==
:''See the [[Bzr checkout|Bazaar checkout instructions]]''

==Opening Stellarium with Qt Creator==
Open Qt Creator.

Open "File" -> "Open File or Project..." (or just press Ctrl+O).

Find the folder where you have put Stellarium's files. Open the topmost <code>CMakeLists.txt</code> file - the one that is '''at the same level''' as the <code>README</code> file and the <code>/src</code> and <code>/data</code> directories.

A "CMake Wizard" window will open. It is small and inconvenient to use. You can resize it to a larger size.
*In the "Build Location" step, there will be a default path already in the location field. '''''Ignore it'''''. Instead:
**Select your base Stellarium location, the same directory where the <code>CMakeLists.txt</code> file was. For example, <code>D:\stellarium\trunk</code>
**Then, add <code>\builds\msys</code>. The whole path should look like something like this:<code>D:\stellarium\trunk\builds\msys</code>
**The point is that this will allow you to run Stellarium directly from inside Qt Creator without having to copy files or to create an installer and install Stellarium.
*In the "Run CMake step", there is an "Arguments" field where you can set CMake command-line arguments.
**You can use it to set Stellarium's pseudo-installation directory. This is necessary only if you want to use a trick useful to translators (described below) or to create an executable installer. Just type in <code>-DCMAKE_INSTALL_PREFIX=c:\stellarium-temp\</code>, where <code>c:\stellarium-temp\</code> is the path to the pseudo-installation directory. (It is not necessary to exist, CMake will create it.)
**When you are done with the arguments, click on the "Run CMake" button. CMake will start and its log will be displayed in the box below. If everything is OK, the last lines will be something like: "Configuring done. Generating done. Build files have been written to <your build directory>" The "Finish" button will be enabled. Click it to close the wizard.

After you close the wizard, Qt Creator should open the project.

'''Tip:''' You can always run again CMake by choosing "Run CMake" from the "Build" menu.

==Building Stellarium==

==Running Stellarium==
You can run the freshly-built Stellarium from inside Qt Creator. You only need to fix the default working directory first.

From the left column, select "Projects" (or press Ctrl+5). Then select the "Run Settings" tab. On that page, under "Run", there must be a "Working directory:" field with a path that looks like this:
C:\stellarium\trunk\builds\msys\src

Select and remove the <tt>builds\msys\src</tt> tail so that the path looks like this:
C:\stellarium\trunk\

After that, you can run the build by clicking on the green arrow button in the left column (or pressing Ctrl+R). You can also run the project in debug mode, etc.

If you have forgotten to set the correct working directory, Stellarium will crash when you try to run it and it will display a "WARNING: could not locate installation directory" error in the log.

==Creating an installer==

===Inno Setup and the project file===
Stellarium uses [http://www.jrsoftware.org/isinfo.php Inno Setup] to create its Windows installers (the self-extracting setup files), so you need to download and install Inno Setup first.

The Inno Setup project file that contains the rules for creating the installer is called <tt>stellarium.iss</tt>. It is generated from the template <tt>stellarium.iss.cmake</tt> when you run CMake, so:
* To have <tt>stellarium.iss</tt>, you need to have run CMake and/or built Stellarium at least once.
* If you run CMake (or build Stellarium?) after you've made changes to <tt>stellarium.iss</tt>, they will be overwritten, so be careful - always keep in mind what changes do you want to make and why, and in which file do you need to make them.

===Building in "install" configuration===
TODO
- add screenshots
To generate an installer, you need to have something to install. Make sure you build Stellarium in the normal way first.

After that, you need to "build" it in an "install" configuration, the equivalent of running <tt>make install</tt> from the command line. Before trying to do it, though, please make sure that you've set the <tt>CMAKE_INSTALL_PREFIX</tt> parameter as described [[#Opening Stellarium with Qt Creator|above]]. If you haven't done it, run CMake again with the appropriate parameters. (You can trigger a new run of CMake at any time - from the "Build" menu at the top select "Run CMake".)

You need to add the build configuration only once per object. From the left column, select "Projects" (or press Ctrl+5). In the "Build Settings" tab, look at the first line: "Edit build configuration:". Click on the "Add" button, then select "Clone selected" from the menu. (This will create a copy of the current configuration, which should be "all".) In the small window that appears, type a name for the new configuration ("install" will do). Make sure that the new configuration is selected in the first box on the same line, then look below for the "Make Steps" section. There should be a "Make:" field containing something like this:
mingw32-make.exe
Click on the "Details" button to the right. More controls should fold out. In the "Additional arguments:" field, type <tt>install</tt>, then click on the "Details" button again to fold the controls. The "Make:" field should now read:
mingw32-make.exe install
That's it, you can now use the new build configuration.

To change the current build configuration, press Ctrl+T (or click on the computer screen icon labelled "Stellarium" in the left column). In the box that opens, the "Build:" drop down list should offer two options - "all" and whatever name you gave the "install" configuration.

So, to build Stellarium in the "install" configuration, make sure that it is selected and then just trigger a new build (for example, by pressing Ctrl+B). The <tt>make</tt> script will then copy all the necessary files to the temporary installation directory that you have set.

If you need only to (re)compile Stellarium after that, open the build configuration selection window again and select "all".

===Running Inno Setup===
After Stellarium has been built in the "install" configuration (which should have copied the necessary files to the temporary installation directory), open the <tt>stellarium.iss</tt> file with Inno Setup (just double-click it). You can make some final changes before running the script.

By default, the new installer will be created in the <tt>/installers</tt> sub-directory in the main directory of your Stellarium working tree. Bazaar is set to ignore it, so you can't accidentally commit a setup file to the repository.

==Using translations==

TO BE CONTINUED

User:Daggerstab/Building Stellarium on Windows with Qt Creator

2012-04-14T13:07:53Z

Daggerstab: /* Running Stellarium */

DRAFT
==Install the Qt SDK==
Stellarium is based on the [http://qt.nokia.com/ Qt] framework, so you need to install it. Before, the Qt libraries and [http://qt.nokia.com/products/developer-tools Qt Creator] were distributed separately, but then Nokia integrated all Qt components in a SDK. So you can download a small installer, and select and download only the components you are going to use.

*Qt downloads page: http://qt.nokia.com/downloads
*The "online installer" for Windows is only 15 MB and allows you to pick which components to download and install
*You need Qt Creator and the Qt Desktop libraries (open source, with MinGW), so in the component selection screen:
**Under "Development Tools":
***Under "Desktop Qt", make sure that the latest version of Qt is checked (as of November 2011, that is 4.7.4). Under the version number, select only "'''Desktop Qt 4.7.4 - MinGW'''"
***Make sure "'''Qt Designer'''" is selected
***You probably don't need anything else under "Development Tools", so feel free to uncheck the rest.
**'''Under "Miscellaneous", make sure that "MinGW 4.4" is checked.''' You don't need the source code. You may need the Qt Examples only if you are a programmer and you want to contribute to Stellarium - they will be useful to understand Qt.
**You need "Documentation" only if you are a programmer who wishes to contribute to Stellarium.
**You don't need "APIs" and "Experimental".

Even if you miss anything at this point, you can install it later with the "Maintain Qt SDK" application (it can be found in the Start menu after the installation is complete).

'''Remember where you install the Qt SDK, because you'll need it later.'''

==Install some GnuWin libraries==
Stellarium needs <code>gettext</code>, <code>libiconv</code> and <code>zlib</code>. You can get them form the GnuWin project:
*http://gnuwin32.sourceforge.net/packages/gettext.htm
*http://gnuwin32.sourceforge.net/packages/libiconv.htm
*http://gnuwin32.sourceforge.net/packages/zlib.htm

For all of them, download the "Complete package, except sources" executable installer. Run the installers and let them install the libraries to the directory they want. It should be something like <code>C:\Program Files\GnuWin32</code>

==Setting environmental variables==
You need to add a few paths to your PATH environmental variable. On Windows, you can modify it with a configuration window: right click on your "My computer" and select "Properties". It's somewhere there. :)

'''TIP:''' The environmental variables window allows you to modify and define env-variables for the current user and for the system. There should be already a "Path" variable defined for the system, but not for the user. Instead of modifying the system PATH, it is more convenient to define a user PATH (just click on the "New..." button and fill in the boxes).

If you have let the Qt SDK install itself in its default location, the path to the Qt libraries should be something like <code>C:\QtSDK\Desktop\Qt\4.7.4\mingw</code> You need to add three subdirectories to the PATH variable:
C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin
C:\QtSDK\Desktop\Qt\4.7.4\mingw\lib
C:\QtSDK\Desktop\Qt\4.7.4\mingw\include

You also need to add the GnuWin libraries:
C:\Program Files\GnuWin32\bin
C:\Program Files\GnuWin32\lib
C:\Program Files\GnuWin32\include

All elements of the list should be separated with a semicolon (;). So the end result should look something like this:
<code>C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin;C:\QtSDK\Desktop\Qt\4.7.4\mingw\lib;C:\QtSDK\Desktop\Qt\4.7.4\mingw\include;C:\Program Files\GnuWin32\bin;C:\Program Files\GnuWin32\lib;C:\Program Files\GnuWin32\include</code>

'''Warning:''' Don't just blindly copy the paths. Make sure that these directories exist and that the Qt version number is the same as yours.

==Install CMake==
CMake download page: http://www.cmake.org/cmake/resources/software.html

And interesting bug: As of 9 November 2011, if you use CMake 2.8.*, on Windows 7, Qt Creator won't show you Stellarium's source file tree in the "Projects" panel. Download and use '''CMake 2.6.4''' (from the same website). If you have any idea why this is happening, contact us in the Stellarium developers mailing list or the Feedback forums.

During the installation, make sure to tell the installer that CMake should be added to the system PATH (for all users). This will save you editing it manually. :)

==Get Stellarium's code==
:''See the [[Bzr checkout|Bazaar checkout instructions]]''

==Opening Stellarium with Qt Creator==
Open Qt Creator.

Open "File" -> "Open File or Project..." (or just press Ctrl+O).

Find the folder where you have put Stellarium's files. Open the topmost <code>CMakeLists.txt</code> file - the one that is '''at the same level''' as the <code>README</code> file and the <code>/src</code> and <code>/data</code> directories.

A "CMake Wizard" window will open. It is small and inconvenient to use. You can resize it to a larger size.
*In the "Build Location" step, there will be a default path already in the location field. '''''Ignore it'''''. Instead:
**Select your base Stellarium location, the same directory where the <code>CMakeLists.txt</code> file was. For example, <code>D:\stellarium\trunk</code>
**Then, add <code>\builds\msys</code>. The whole path should look like something like this:<code>D:\stellarium\trunk\builds\msys</code>
**The point is that this will allow you to run Stellarium directly from inside Qt Creator without having to copy files or to create an installer and install Stellarium.
*In the "Run CMake step", there is an "Arguments" field where you can set CMake command-line arguments.
**You can use it to set Stellarium's pseudo-installation directory. This is necessary only if you want to use a trick useful to translators (described below) or to create an executable installer. Just type in <code>-DCMAKE_INSTALL_PREFIX=c:\stellarium-temp\</code>, where <code>c:\stellarium-temp\</code> is the path to the pseudo-installation directory. (It is not necessary to exist, CMake will create it.)
**When you are done with the arguments, click on the "Run CMake" button. CMake will start and its log will be displayed in the box below. If everything is OK, the last lines will be something like: "Configuring done. Generating done. Build files have been written to <your build directory>" The "Finish" button will be enabled. Click it to close the wizard.

After you close the wizard, Qt Creator should open the project.

'''Tip:''' You can always run again CMake by choosing "Run CMake" from the "Build" menu.

==Building Stellarium==

==Running Stellarium==
You can run the freshly-built Stellarium from inside Qt Creator. You only need to fix the default working directory first.

From the left column, select "Projects" (or press Ctrl+5). Then select the "Run Settings" tab. On that page, under "Run", there must be a "Working directory:" field with a path that looks like this:
C:\stellarium\trunk\builds\msys\src

Select and remove the <tt>builds\msys\src</tt> tail so that the path looks like this:
C:\stellarium\trunk\

After that, you can run the build by clicking on the green arrow button in the left column (or pressing Ctrl+R). You can also run the project in debug mode, etc.

If you have forgotten to set the correct working directory, Stellarium will crash when you try to run it and it will display a "WARNING: could not locate installation directory" error in the log.

==Creating an installer==

===Inno Setup and the project file===
Stellarium uses [http://www.jrsoftware.org/isinfo.php Inno Setup] to create its Windows installers, so you need to download and install Inno Setup first.

The Inno Setup project file that contains the rules for creating the installer is called <tt>stellarium.iss</tt>. It is generated from the template <tt>stellarium.iss.cmake</tt> when you run CMake, so:
* To have <tt>stellarium.iss</tt>, you need to have run CMake and/or built Stellarium at least once.
* If you run CMake (or build Stellarium?) after you've made changes to <tt>stellarium.iss</tt>, they will be overwritten, so be careful - always keep in mind what changes do you want to make and why, and in which file do you need to make them.

===Building in "install" configuration===

===Running Inno Setup===
After Stellarium has been built in the "install configuration" (and files have been copied to the temporary installation directory), open the <tt>stellarium.iss</tt> file with Inno Setup (just double-click it). You can make some final changes before running the script.

By default, the new installer will be created in the <tt>/installers</tt> sub-directory in the main directory of your Stellarium working tree. Bazaar is set to ignore it, so you can't accidentally commit a setup file to the repository.

==Using translations==

TO BE CONTINUED

User:Daggerstab/Building Stellarium on Windows with Qt Creator

2012-04-14T12:58:04Z

Daggerstab: /* Creating an installer */

DRAFT
==Install the Qt SDK==
Stellarium is based on the [http://qt.nokia.com/ Qt] framework, so you need to install it. Before, the Qt libraries and [http://qt.nokia.com/products/developer-tools Qt Creator] were distributed separately, but then Nokia integrated all Qt components in a SDK. So you can download a small installer, and select and download only the components you are going to use.

*Qt downloads page: http://qt.nokia.com/downloads
*The "online installer" for Windows is only 15 MB and allows you to pick which components to download and install
*You need Qt Creator and the Qt Desktop libraries (open source, with MinGW), so in the component selection screen:
**Under "Development Tools":
***Under "Desktop Qt", make sure that the latest version of Qt is checked (as of November 2011, that is 4.7.4). Under the version number, select only "'''Desktop Qt 4.7.4 - MinGW'''"
***Make sure "'''Qt Designer'''" is selected
***You probably don't need anything else under "Development Tools", so feel free to uncheck the rest.
**'''Under "Miscellaneous", make sure that "MinGW 4.4" is checked.''' You don't need the source code. You may need the Qt Examples only if you are a programmer and you want to contribute to Stellarium - they will be useful to understand Qt.
**You need "Documentation" only if you are a programmer who wishes to contribute to Stellarium.
**You don't need "APIs" and "Experimental".

Even if you miss anything at this point, you can install it later with the "Maintain Qt SDK" application (it can be found in the Start menu after the installation is complete).

'''Remember where you install the Qt SDK, because you'll need it later.'''

==Install some GnuWin libraries==
Stellarium needs <code>gettext</code>, <code>libiconv</code> and <code>zlib</code>. You can get them form the GnuWin project:
*http://gnuwin32.sourceforge.net/packages/gettext.htm
*http://gnuwin32.sourceforge.net/packages/libiconv.htm
*http://gnuwin32.sourceforge.net/packages/zlib.htm

For all of them, download the "Complete package, except sources" executable installer. Run the installers and let them install the libraries to the directory they want. It should be something like <code>C:\Program Files\GnuWin32</code>

==Setting environmental variables==
You need to add a few paths to your PATH environmental variable. On Windows, you can modify it with a configuration window: right click on your "My computer" and select "Properties". It's somewhere there. :)

'''TIP:''' The environmental variables window allows you to modify and define env-variables for the current user and for the system. There should be already a "Path" variable defined for the system, but not for the user. Instead of modifying the system PATH, it is more convenient to define a user PATH (just click on the "New..." button and fill in the boxes).

If you have let the Qt SDK install itself in its default location, the path to the Qt libraries should be something like <code>C:\QtSDK\Desktop\Qt\4.7.4\mingw</code> You need to add three subdirectories to the PATH variable:
C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin
C:\QtSDK\Desktop\Qt\4.7.4\mingw\lib
C:\QtSDK\Desktop\Qt\4.7.4\mingw\include

You also need to add the GnuWin libraries:
C:\Program Files\GnuWin32\bin
C:\Program Files\GnuWin32\lib
C:\Program Files\GnuWin32\include

All elements of the list should be separated with a semicolon (;). So the end result should look something like this:
<code>C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin;C:\QtSDK\Desktop\Qt\4.7.4\mingw\lib;C:\QtSDK\Desktop\Qt\4.7.4\mingw\include;C:\Program Files\GnuWin32\bin;C:\Program Files\GnuWin32\lib;C:\Program Files\GnuWin32\include</code>

'''Warning:''' Don't just blindly copy the paths. Make sure that these directories exist and that the Qt version number is the same as yours.

==Install CMake==
CMake download page: http://www.cmake.org/cmake/resources/software.html

And interesting bug: As of 9 November 2011, if you use CMake 2.8.*, on Windows 7, Qt Creator won't show you Stellarium's source file tree in the "Projects" panel. Download and use '''CMake 2.6.4''' (from the same website). If you have any idea why this is happening, contact us in the Stellarium developers mailing list or the Feedback forums.

During the installation, make sure to tell the installer that CMake should be added to the system PATH (for all users). This will save you editing it manually. :)

==Get Stellarium's code==
:''See the [[Bzr checkout|Bazaar checkout instructions]]''

==Opening Stellarium with Qt Creator==
Open Qt Creator.

Open "File" -> "Open File or Project..." (or just press Ctrl+O).

Find the folder where you have put Stellarium's files. Open the topmost <code>CMakeLists.txt</code> file - the one that is '''at the same level''' as the <code>README</code> file and the <code>/src</code> and <code>/data</code> directories.

A "CMake Wizard" window will open. It is small and inconvenient to use. You can resize it to a larger size.
*In the "Build Location" step, there will be a default path already in the location field. '''''Ignore it'''''. Instead:
**Select your base Stellarium location, the same directory where the <code>CMakeLists.txt</code> file was. For example, <code>D:\stellarium\trunk</code>
**Then, add <code>\builds\msys</code>. The whole path should look like something like this:<code>D:\stellarium\trunk\builds\msys</code>
**The point is that this will allow you to run Stellarium directly from inside Qt Creator without having to copy files or to create an installer and install Stellarium.
*In the "Run CMake step", there is an "Arguments" field where you can set CMake command-line arguments.
**You can use it to set Stellarium's pseudo-installation directory. This is necessary only if you want to use a trick useful to translators (described below) or to create an executable installer. Just type in <code>-DCMAKE_INSTALL_PREFIX=c:\stellarium-temp\</code>, where <code>c:\stellarium-temp\</code> is the path to the pseudo-installation directory. (It is not necessary to exist, CMake will create it.)
**When you are done with the arguments, click on the "Run CMake" button. CMake will start and its log will be displayed in the box below. If everything is OK, the last lines will be something like: "Configuring done. Generating done. Build files have been written to <your build directory>" The "Finish" button will be enabled. Click it to close the wizard.

After you close the wizard, Qt Creator should open the project.

'''Tip:''' You can always run again CMake by choosing "Run CMake" from the "Build" menu.

==Building Stellarium==

==Running Stellarium==

==Creating an installer==

===Inno Setup and the project file===
Stellarium uses [http://www.jrsoftware.org/isinfo.php Inno Setup] to create its Windows installers, so you need to download and install Inno Setup first.

The Inno Setup project file that contains the rules for creating the installer is called <tt>stellarium.iss</tt>. It is generated from the template <tt>stellarium.iss.cmake</tt> when you run CMake, so:
* To have <tt>stellarium.iss</tt>, you need to have run CMake and/or built Stellarium at least once.
* If you run CMake (or build Stellarium?) after you've made changes to <tt>stellarium.iss</tt>, they will be overwritten, so be careful - always keep in mind what changes do you want to make and why, and in which file do you need to make them.

===Building in "install" configuration===

===Running Inno Setup===
After Stellarium has been built in the "install configuration" (and files have been copied to the temporary installation directory), open the <tt>stellarium.iss</tt> file with Inno Setup (just double-click it). You can make some final changes before running the script.

By default, the new installer will be created in the <tt>/installers</tt> sub-directory in the main directory of your Stellarium working tree. Bazaar is set to ignore it, so you can't accidentally commit a setup file to the repository.

==Using translations==

TO BE CONTINUED

User talk:Hikiko

2012-04-14T10:06:54Z

Daggerstab: Hello

== Hello ==

Hello and welcome. :) --[[User:Daggerstab|Daggerstab]] 10:06, 14 April 2012 (UTC)

MediaWiki:Spam-blacklist

2012-04-14T10:05:34Z

Daggerstab: + "breastpump

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
louisvuitton
abercrombie
abercrombie
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
yeast
surrogate
breastpump
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

MediaWiki:Spam-blacklist

2012-04-14T10:00:15Z

Daggerstab: + "surrogate"

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
louisvuitton
abercrombie
abercrombie
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
yeast
surrogate
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

MediaWiki:Titleblacklist

2012-04-14T09:59:30Z

Daggerstab: + "surrogate"

# <pre>
# This is a title blacklist. Titles and users that match a regular expression here cannot be created.
# Use "#" for comments.
# This is case insensitive by default
.*loan.*
.*cheap.*
.*mortgage.*
.*jobs.*
.*forex.*
.*credit.*
.*payday.*
.*casino.*
.*poker.*
.*insurance.*
.*jewelry.*
.*cellulite.*
.*drug.*
.*crusher.*
.*cash.*
.*surrogate.*
.*\s*buy\s*.*
.*\s*sale\s*.*
#</pre>

File location test

2012-03-23T13:45:47Z

Daggerstab:

To whoever is able to build Stellarium on non-Linux platforms:

*Please see if build works with respect to the locations of files (I moved code from elsewhere into StelFileMgr, but don't have access to non-linux machines to do a test build).
*Report where files end up. It is not clear to me where this is on non-POISX systems, as the location is determined by a system call unfamiliar to me.

I would like to know the following for the user guide:
#Installation directory - the name of the directory where the nebulae, scripts, skycultures, landscapes etc. are installed.
#Location of config.ini (the version which is saved when clicking save in the config window, not the default_config.ini file)
#Location where screenshots get saved
#Location where recorded scripts get saved.

Please enter your results in this table:
{| class="wikitable" width=100%
| '''Version (or revision)''' || '''Platform''' || '''Item''' || '''Result'''
|-
||v-0.9.1||Linux||install dir||$PREFIX/share/stellarium/
|-
||v-0.9.1||Linux||config.ini||$HOME/.stellarium/config.ini
|-
||v-0.9.1||Linux||screenshots||$HOME/
|-
||v-0.9.1||Linux||recorded scripts||$HOME/.stellarium/scripts/
|-
||v-0.9.1||Win XP Win 2000||install dir||(root-partition):\Program Files\Stellarium\
|-
||v-0.9.1||Win XP Win 2000||config.ini||(root-partion):Documents and settings\(your settings folder)\stellarium\
|-
||v-0.9.1||Win XP Win 2000||screenshots||(root-partition):\Documents and settings\(your settings)\Desktop\stellarium-xxx.bmp
|-
||v-0.9.1||Win XP Win 2000||Recorded scripts||(root-partition):\Documents and settings\(your settings)\stellarium\scripts\recorded-xxx.sts
|-
||r2133||OSX||install dir||can be anywhere, but typically /Applications
|-
||r2133||OSX||config.ini||~/Library/Preferences/Stellarium/config.ini
|-
||r2133||OSX||screenshots||~/Desktop
|-
||r2133||OSX||recorded scripts||~/Library/Preferences/Stellarium/scripts
|-
||0.9.1||Vista||install dir||(root-partition):\Program Files\Stellarium\
|-
||0.9.1||Vista||config.ini||(root-partition)\Users\(user name)\Appdata\Roaming\Stellarium
|-
||0.9.1||Vista||screenshots||error msg: 'directory ~\desktop not writable' The attribute for this directory needs to be changed from read only to allow stellarium to write screenshot. This is best done by opening a command prompt in the (root drive)\users\(user name) and typing attrib -r desktop
|-
||0.9.1||Vista||recorded scripts||(root-partition)\Users\(user name)\Appdata\Roaming\Stellarium\scripts
|-
||v-0.9.1||Windows ME & 98-2e||install dir||Stellarium is not availble under Qt4 for these systems Use version 0.8.2
|-
||v-0.9.1||Windows ME & 98-2e|| config.ini||Stellarium is not availble under Qt4 for these systems Use version 0.8.2
|-
|| v-0.9.1||Windows ME & 98-2e||screenshots||Stellarium is not availble under Qt4 for these systems Use version 0.8.2
|-
|| v-0.9.1||Windows ME & 98-2e||recorded Scripts||Stellarium is not availble under Qt4 for these systems Use version 0.8.2
|-
||v-0.9.0||Windows XP (zhTW Locale)||install dir||\Program Files\Stellarium
|-
||v-0.9.0||Windows XP (zhTW Locale)||config.ini||(User Profile)\Stellarium\config.ini
|-
||v-0.9.0||Windows XP (zhTW Locale)||config.ini||'''Stellarium WILL UNABLE TO START if User Profile dir consists non-English names'''
|-
||v-0.9.0||Windows XP (zhTW Locale)||screenshots||'''ERROR StelAppSdl::saveScreenShot: could not determine screenshot directory: NOTFOUND'''
|-
||v-0.9.0||Windows XP (zhTW Locale)||recorded scripts||(Not tested)
|-
||v-0.10.2||Windows XP (zhCN Locale)||install dir||c:\Program Files\Stellarium
|-
||v-0.10.2||Windows XP (zhCN Locale)||config.ini||c:\Program Files\Stellarium\config.ini
|-
||v-0.10.5||Windows 7 (zhCN Locale)||config.ini||C:\Users\%username%\AppData\Roaming\Stellarium\config.ini
|-
||v-0.11.2||Windows 7 64-bit ||install dir||C:\Program Files (x86)\Stellarium
|-
||v-0.11.2||Windows 7 64-bit ||config.ini||C:\Users\%username%\AppData\Roaming\Stellarium\config.ini
|-
||v-0.11.2||Windows 7 64-bit ||screenshots||C:\Users\%username%\Desktop
|-
||v-0.11.2||Windows 7 64-bit ||recorded scripts||(Not tested)

|-

|}

[[Category:Development]]

MediaWiki:Spam-blacklist

2012-03-23T13:43:57Z

Daggerstab: + 3 - if it goes on like this, all designers will end here

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
louisvuitton
abercrombie
abercrombie
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
yeast
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

User talk:Silverfields1

2012-03-20T16:55:58Z

Daggerstab: Congratulations

== Congratulations ==

I've given you sysop/Administrator rights. Now you can [[Special:ListGroupRights|delete and lock pages, etc.]] --[[User:Daggerstab|Daggerstab]] 16:55, 20 March 2012 (UTC)

System requirements

2012-03-20T16:50:53Z

Daggerstab: /* Note about OpenGL version */

* Linux/Unix; Windows NT/2000/XP/Vista/7; MacOS X 10.3.x or greater
* 3D graphics card which supports OpenGL
* a dark room for realistic rendering - details like the Milky Way or star twinkling can’t be seen in a bright room
* a minimum of 256 MiB RAM, 1 GiB or more required for the largest star catalogues

===Note about OpenGL version===
Stellarium is compiled to specifically use OpenGL 2 for better rendering quality.
If your video card does not have an OpenGL 2 compatible driver you can force Stellarium to use OpenGL 1.x by:
* (under Windows) using menu icon '''Stellarium (no OpenGL2)''', or
* placing '''use_qpaintenginegl2 = false''' in section '''[main]''' of the '''config.ini''' file

{| class="wikitable"
! rowspan="3" | Stellarium version
! colspan="12" | System requirements
|-
! colspan="6" | Minimal
! colspan="6" | Recommended
|-
! Linux/UNIX
! Windows
! Mac OS X
! RAM
! HDD
! OpenGL
! Linux/UNIX
! Windows
! Mac OS X
! RAM
! HDD
! OpenGL
|-
| 0.6.0
| colspan="12" | -
|-
| 0.6.1
| colspan="12" | -
|-
| 0.7.0
| colspan="12" | -
|-
| 0.7.1
| colspan="12" | -
|-
| 0.8.0
| colspan="12" | -
|-
| 0.8.1
| colspan="12" | -
|-
| 0.8.2
| colspan="12" | -
|-
| 0.9.0
| colspan="12" | -
|-
| 0.9.1
| colspan="12" | -
|-
| 0.10.0
| colspan="12" | -
|-
| 0.10.1
| colspan="12" | -
|-
| 0.10.2
| colspan="12" | -
|-
| 0.10.3
| colspan="12" | -
|-
| 0.10.4
| colspan="12" | -
|-
| 0.10.5
| colspan="12" | -
|-
| 0.10.6
| colspan="12" | -
|-
| 0.11.0
| colspan="12" | -
|-
| 0.11.1
| colspan="12" | -
|-
| 0.11.2
| colspan="12" | -
|-
| ''0.11.3''
| colspan="12" | -
|-
|}

Google Summer of Code 2012

2012-03-19T19:35:52Z

Daggerstab:

Ideas for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC 2012] (Google Summer of Code 2012).

'''For students applications we have a Google Docs [https://docs.google.com/spreadsheet/viewform?formkey=dDFpYUJZbm5tWVQ3TmNQVWc3c3Vpb2c6MQ#gid=0 form]. Please fill in what you can.'''

==Common requirements==
All of these tasks require knowledge of '''C/C++''', as Stellarium is written in it, and some knowledge of the [http://qt.nokia.com/products/ '''Qt framework'''] (or willingness to learn the basics very quickly), because Stellarium relies heavily on it, especially for its GUI.

==Suggested workflow==
For each task that looks interesting to you:
*Understand it - read the description and try to imagine what is required
*Research it - if the description is unclear, you can ask for clarification and/or do some research and come up with your own ideas. Also, look at how Stellarium works with similar tasks
*Sketch it - Check out Stellarium's code and build it (there are instructions on this wiki), look at what can be used and what needs to be done to implement your idea, how it will come together with the rest of Stellarium
*All of this should prepare you to write a good proposal.

Please don't just submit a re-write of the task description here (some people actually did that last year). We are not that stupid, and plagiarism is a bad habit to learn this early in your career.

==Ideas/projects==
===Support for collections of multi-resolution sky surveys ===
'''Brief explanation:''' Work has already started on this project and we have a working initial code displaying images encoded in the TOAST format.
The image data for each sky survey needs to be pre-processed and stored on a server. We currently have a server hosted by the Free Software Fundation France with a potentially high bandwith for serving the (huge amount of) data.

'''Knowledge Prerequisite:''' OpenGL, Geometry, Astronomy.

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Meteor shower calendar ===
:See [[Proposals:Realistic meteor showers]], Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/realistic-meteor-showers Realistic meteor showers]
'''Brief explanation:''' At the moment, Stellarium can show meteors, but they are simply decorative - they appear at random points at a rate set by the user. The existing code of the MeteorMgr class can be used as a base for a plug-in that shows more or less scientifically accurate meteor showers. They are not random - the meteors appear to "stream" from a single point in the celestial sphere, the radiant.

The data behind the rendering can be organized in two different forms:
* Strong form: Keeps a meteor shower catalogue in JSON format as with the other kinds of objects tracked by Stellarium, and shows only what should be in the sky for the given date. The catalogue should contain information about the radiant and the annual changes in the zenith hourly rate (as meteor showers typically have a peak and are active some time before and after that; a distribution function can do).
* Very strong form: Use a professional model for predicting meteor showers, based on the orbits of the clouds of space particles that cause them.

Data about visual meteor showers can be found on the website of the [http://www.imo.net International Meteor Organization] (e.g. [http://www.imo.net/calendar/2011 calendar for 2011]) or the [http://www.ta3.sk/IAUC22DB/MDC2007/ Meteor Data Center]. Attribution and/or copyright issues should be cleared before using the data!

It would be nice to have an improvement in the quality of the graphics, but the main point of this project is the support for a catalog of multiple meteor showers.

In all cases, the feature should meet the following requirements:
*It should display a list of the meteor showers in the catalog
**It should allow individual showers to be enabled/disabled
**It should allow individual showers to be triggered on a whim. (Perhaps by jumping to the day of the peak? By setting radiant/ZHR, for example for demonstrations of historic showers?)
*It should allow the user to toggle a marker showing the radiant(s). (Note that the radiants are not exactly point objects.)
*It should model the drift of the radiant across the sky over time.
*It should model the increasing/decreasing ZHR of each shower over time.
*Some support for random "background" meteors would be nice to remain.

'''Knowledge Prerequisite:''' OpenGL, Geometry, Basic Astronomy.

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

===Realistic comet rendering ===
:See [[Proposals:Realistic comet rendering]], Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/realistic-comet-rendering Realistic renedring of comets]
'''Brief explanation:''' At the moment, Stellarium supports comets as solar system bodies, but displays them as star-like objects. More realistic and more scientifically accurate rendering of a comet requires the rendering of four elements - a core, a coma and two tails, oriented according to the comet's relative position to the Sun and its direction. The tails and the coma should appear only when the comet is close enough to the Sun. (See the Wikipedia article on comets for more information.)

As not all comets are identical, this feature should allow comet customization. The visual characteristics of comets should be stored along with their orbital elements.

'''Knowledge Prerequisite:''' OpenGL, some mathematics and astronomy.

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Satellite and ring shadows on parent planets===
'''Brief explanation:''' At the moment, satellites and ring in Stellarium don't cast visible shadows on their parent planets and vice versa (solar and lunar eclipses are implemented as special cases).

The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.

'''Knowledge Prerequisite:''' OpenGL

'''Mentors:''' [https://launchpad.net/~alexwolf Alexander Wolf], [https://launchpad.net/~treaves Timothy Reaves]

===Irregular Solar System bodies===
'''Brief explanation:''' At the moment, all Solar System bodies are rendered as spheroids. This is fine for all planets and large satellites, but unrealistic for all asteroids and some smaller moons (such as Phobos, etc.). Realistic rendering of asteroids requires the rendering of a simple 3D model, either in some accepted open 3D model format (e.g. COLLADA?) or in a simple format developed for Stellarium. Rough shape data for about 20+ asteroids can be found somewhere on NASA's websites. Working on this project should start with finding it and deciding which format to use.

The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.

'''Knowledge Prerequisite:''' OpenGL

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Add-on manager for management of downloadable extras===
:See Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/add-on-manager Add-on manager for management of downloadable extras]
'''Brief explanation:''' An Add-on manager something along the lines of that in Firefox, for downloading, installing, updating and removing extras: specifically landscapes, scripts, sky cultures, star catalogs, nebula sets.

'''Knowledge Prerequisite:'''

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

=== Update the current DSO catalog ===
:See Launchpad Blueprints [https://blueprints.launchpad.net/stellarium/+spec/new-ngc-catalog Update the current NGC catalog to a new updated one], [https://blueprints.launchpad.net/stellarium/+spec/stellarium-dso-catalog Stellarium DSO catalog] and [https://blueprints.launchpad.net/stellarium/+spec/messier-caldwell Display Messier and Caldwell Objects]
The NGC catalog used in Stellarium currently has many mistakes. Fabien had the very kind permission from Wolfgang Steinicke to use his updated NGC and IC catalogs available from his web site: http://www.klima-luft.de/steinicke/ngcic/rev2000/Explan.htm

His catalog provide more accurate positions, merge doublons etc..

He also provide more information on the type of the nebula. This info could be used to use icons matching the type of nebula, and also to draw ellipses for galaxies.

The code change should be located in modules/NebulaMgr.hpp/cpp and modules/Nebula.hpp/cpp

A lot of amateur astronomers set out to track down all of the Messier and Caldwell objects. It would, therefore, be very handy if Stellarium could highlight these objects. Envisage an option which would make all M (or C, or NGC, or Herschel) objects visible at all zoom levels and distinguish then from other DSOs by making their symbols a different colour and (optionally) labelling them by their catalog number.

'''Knowledge Prerequisite:''' Basic astronomy knowledge

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

[[Category:Summer of Code]]

Google Summer of Code 2012

2012-03-19T19:14:04Z

Daggerstab: /* Meteor shower calendar */

Ideas for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC 2012] (Google Summer of Code 2012).

'''For students applications we have a Google Docs [https://docs.google.com/spreadsheet/viewform?formkey=dDFpYUJZbm5tWVQ3TmNQVWc3c3Vpb2c6MQ#gid=0 form]. Please fill in what you can.'''

==Common requirements==
All of these tasks require knowledge of '''C/C++''', as Stellarium is written in it, and some knowledge of the [http://qt.nokia.com/products/ '''Qt framework'''] (or willingness to learn the basics very quickly), because Stellarium relies heavily on it, especially for its GUI.

==Ideas/projects==
===Support for collections of multi-resolution sky surveys ===
'''Brief explanation:''' Work has already started on this project and we have a working initial code displaying images encoded in the TOAST format.
The image data for each sky survey needs to be pre-processed and stored on a server. We currently have a server hosted by the Free Software Fundation France with a potentially high bandwith for serving the (huge amount of) data.

'''Knowledge Prerequisite:''' OpenGL, Geometry, Astronomy.

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Meteor shower calendar ===
:See [[Proposals:Realistic meteor showers]], Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/realistic-meteor-showers Realistic meteor showers]
'''Brief explanation:''' At the moment, Stellarium can show meteors, but they are simply decorative - they appear at random points at a rate set by the user. The existing code of the MeteorMgr class can be used as a base for a plug-in that shows more or less scientifically accurate meteor showers. They are not random - the meteors appear to "stream" from a single point in the celestial sphere, the radiant.

The data behind the rendering can be organized in two different forms:
* Strong form: Keeps a meteor shower catalogue in JSON format as with the other kinds of objects tracked by Stellarium, and shows only what should be in the sky for the given date. The catalogue should contain information about the radiant and the annual changes in the zenith hourly rate (as meteor showers typically have a peak and are active some time before and after that; a distribution function can do).
* Very strong form: Use a professional model for predicting meteor showers, based on the orbits of the clouds of space particles that cause them.

Data about visual meteor showers can be found on the website of the [http://www.imo.net International Meteor Organization] (e.g. [http://www.imo.net/calendar/2011 calendar for 2011]) or the [http://www.ta3.sk/IAUC22DB/MDC2007/ Meteor Data Center]. Attribution and/or copyright issues should be cleared before using the data!

It would be nice to have an improvement in the quality of the graphics, but the main point of this project is the support for a catalog of multiple meteor showers.

In all cases, the feature should meet the following requirements:
*It should display a list of the meteor showers in the catalog
**It should allow individual showers to be enabled/disabled
**It should allow individual showers to be triggered on a whim. (Perhaps by jumping to the day of the peak? By setting radiant/ZHR, for example for demonstrations of historic showers?)
*It should allow the user to toggle a marker showing the radiant(s). (Note that the radiants are not exactly point objects.)
*It should model the drift of the radiant across the sky over time.
*It should model the increasing/decreasing ZHR of each shower over time.
*Some support for random "background" meteors would be nice to remain.

'''Knowledge Prerequisite:''' OpenGL, Geometry, Basic Astronomy.

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

===Realistic comet rendering ===
:See [[Proposals:Realistic comet rendering]], Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/realistic-comet-rendering Realistic renedring of comets]
'''Brief explanation:''' At the moment, Stellarium supports comets as solar system bodies, but displays them as star-like objects. More realistic and more scientifically accurate rendering of a comet requires the rendering of four elements - a core, a coma and two tails, oriented according to the comet's relative position to the Sun and its direction. The tails and the coma should appear only when the comet is close enough to the Sun. (See the Wikipedia article on comets for more information.)

As not all comets are identical, this feature should allow comet customization. The visual characteristics of comets should be stored along with their orbital elements.

'''Knowledge Prerequisite:''' OpenGL, some mathematics and astronomy.

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Satellite and ring shadows on parent planets===
'''Brief explanation:''' At the moment, satellites and ring in Stellarium don't cast visible shadows on their parent planets and vice versa (solar and lunar eclipses are implemented as special cases).

The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.

'''Knowledge Prerequisite:''' OpenGL

'''Mentors:''' [https://launchpad.net/~alexwolf Alexander Wolf], [https://launchpad.net/~treaves Timothy Reaves]

===Irregular Solar System bodies===
'''Brief explanation:''' At the moment, all Solar System bodies are rendered as spheroids. This is fine for all planets and large satellites, but unrealistic for all asteroids and some smaller moons (such as Phobos, etc.). Realistic rendering of asteroids requires the rendering of a simple 3D model, either in some accepted open 3D model format (e.g. COLLADA?) or in a simple format developed for Stellarium. Rough shape data for about 20+ asteroids can be found somewhere on NASA's websites. Working on this project should start with finding it and deciding which format to use.

The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.

'''Knowledge Prerequisite:''' OpenGL

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Add-on manager for management of downloadable extras===
:See Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/add-on-manager Add-on manager for management of downloadable extras]
'''Brief explanation:''' An Add-on manager something along the lines of that in Firefox, for downloading, installing, updating and removing extras: specifically landscapes, scripts, sky cultures, star catalogs, nebula sets.

'''Knowledge Prerequisite:'''

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

=== Update the current DSO catalog ===
:See Launchpad Blueprints [https://blueprints.launchpad.net/stellarium/+spec/new-ngc-catalog Update the current NGC catalog to a new updated one], [https://blueprints.launchpad.net/stellarium/+spec/stellarium-dso-catalog Stellarium DSO catalog] and [https://blueprints.launchpad.net/stellarium/+spec/messier-caldwell Display Messier and Caldwell Objects]
The NGC catalog used in Stellarium currently has many mistakes. Fabien had the very kind permission from Wolfgang Steinicke to use his updated NGC and IC catalogs available from his web site: http://www.klima-luft.de/steinicke/ngcic/rev2000/Explan.htm

His catalog provide more accurate positions, merge doublons etc..

He also provide more information on the type of the nebula. This info could be used to use icons matching the type of nebula, and also to draw ellipses for galaxies.

The code change should be located in modules/NebulaMgr.hpp/cpp and modules/Nebula.hpp/cpp

A lot of amateur astronomers set out to track down all of the Messier and Caldwell objects. It would, therefore, be very handy if Stellarium could highlight these objects. Envisage an option which would make all M (or C, or NGC, or Herschel) objects visible at all zoom levels and distinguish then from other DSOs by making their symbols a different colour and (optionally) labelling them by their catalog number.

'''Knowledge Prerequisite:''' Basic astronomy knowledge

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

[[Category:Summer of Code]]

Google Summer of Code 2012

2012-03-19T19:10:29Z

Daggerstab: /* Meteor shower calendar */ these people will be paid to do this, won't they?

Ideas for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC 2012] (Google Summer of Code 2012).

'''For students applications we have a Google Docs [https://docs.google.com/spreadsheet/viewform?formkey=dDFpYUJZbm5tWVQ3TmNQVWc3c3Vpb2c6MQ#gid=0 form]. Please fill in what you can.'''

==Common requirements==
All of these tasks require knowledge of '''C/C++''', as Stellarium is written in it, and some knowledge of the [http://qt.nokia.com/products/ '''Qt framework'''] (or willingness to learn the basics very quickly), because Stellarium relies heavily on it, especially for its GUI.

==Ideas/projects==
===Support for collections of multi-resolution sky surveys ===
'''Brief explanation:''' Work has already started on this project and we have a working initial code displaying images encoded in the TOAST format.
The image data for each sky survey needs to be pre-processed and stored on a server. We currently have a server hosted by the Free Software Fundation France with a potentially high bandwith for serving the (huge amount of) data.

'''Knowledge Prerequisite:''' OpenGL, Geometry, Astronomy.

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Meteor shower calendar ===
:See [[Proposals:Realistic meteor showers]], Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/realistic-meteor-showers Realistic meteor showers]
'''Brief explanation:''' At the moment, Stellarium can show meteors, but they are simply decorative - they appear at random points at a rate set by the user. The existing code of the MeteorMgr class can be used as a base for a plug-in that shows more or less scientifically accurate meteor showers. They are not random - the meteors appear to "stream" from a single point in the celestial sphere, the radiant.

The data behind the rendering can be organized in two different forms:
* Strong form: Keeps a meteor shower catalogue in JSON format as with the other kinds of objects tracked by Stellarium, and shows only what should be in the sky for the given date. The catalogue should contain information about the radiant and the annual changes in the zenith hourly rate (as meteor showers typically have a peak and are active some time before and after that; a distribution function can do).
* Very strong form: Use a professional model for predicting meteor showers, based on the orbits of the clouds of space particles that cause them.

Data about visual meteor showers can be found on the website of the [http://www.imo.net International Meteor Organization] (e.g. [http://www.imo.net/calendar/2011 calendar for 2011]) or the [http://www.ta3.sk/IAUC22DB/MDC2007/ Meteor Data Center]. Attribution and/or copyright issues should be cleared before using the data!

In all cases, the feature should meet the following requirements:
*It should display a list of the meteor showers in the catalog
**It should allow individual showers to be enabled/disabled
**It should allow individual showers to be triggered on a whim. (Perhaps by jumping to the day of the peak?)
*It should allow the user to toggle a marker showing the radiant(s). (Note that the radiants are not exactly point objects.)
*It should model the drift of the radiant across the sky over time.
*It should model the increasing/decreasing ZHR of each shower over time.

'''Knowledge Prerequisite:''' OpenGL, Geometry, Basic Astronomy.

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

===Realistic comet rendering ===
:See [[Proposals:Realistic comet rendering]], Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/realistic-comet-rendering Realistic renedring of comets]
'''Brief explanation:''' At the moment, Stellarium supports comets as solar system bodies, but displays them as star-like objects. More realistic and more scientifically accurate rendering of a comet requires the rendering of four elements - a core, a coma and two tails, oriented according to the comet's relative position to the Sun and its direction. The tails and the coma should appear only when the comet is close enough to the Sun. (See the Wikipedia article on comets for more information.)

As not all comets are identical, this feature should allow comet customization. The visual characteristics of comets should be stored along with their orbital elements.

'''Knowledge Prerequisite:''' OpenGL, some mathematics and astronomy.

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Satellite and ring shadows on parent planets===
'''Brief explanation:''' At the moment, satellites and ring in Stellarium don't cast visible shadows on their parent planets and vice versa (solar and lunar eclipses are implemented as special cases).

The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.

'''Knowledge Prerequisite:''' OpenGL

'''Mentors:''' [https://launchpad.net/~alexwolf Alexander Wolf], [https://launchpad.net/~treaves Timothy Reaves]

===Irregular Solar System bodies===
'''Brief explanation:''' At the moment, all Solar System bodies are rendered as spheroids. This is fine for all planets and large satellites, but unrealistic for all asteroids and some smaller moons (such as Phobos, etc.). Realistic rendering of asteroids requires the rendering of a simple 3D model, either in some accepted open 3D model format (e.g. COLLADA?) or in a simple format developed for Stellarium. Rough shape data for about 20+ asteroids can be found somewhere on NASA's websites. Working on this project should start with finding it and deciding which format to use.

The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.

'''Knowledge Prerequisite:''' OpenGL

'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]

===Add-on manager for management of downloadable extras===
:See Launchpad Blueprint [https://blueprints.launchpad.net/stellarium/+spec/add-on-manager Add-on manager for management of downloadable extras]
'''Brief explanation:''' An Add-on manager something along the lines of that in Firefox, for downloading, installing, updating and removing extras: specifically landscapes, scripts, sky cultures, star catalogs, nebula sets.

'''Knowledge Prerequisite:'''

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

=== Update the current DSO catalog ===
:See Launchpad Blueprints [https://blueprints.launchpad.net/stellarium/+spec/new-ngc-catalog Update the current NGC catalog to a new updated one], [https://blueprints.launchpad.net/stellarium/+spec/stellarium-dso-catalog Stellarium DSO catalog] and [https://blueprints.launchpad.net/stellarium/+spec/messier-caldwell Display Messier and Caldwell Objects]
The NGC catalog used in Stellarium currently has many mistakes. Fabien had the very kind permission from Wolfgang Steinicke to use his updated NGC and IC catalogs available from his web site: http://www.klima-luft.de/steinicke/ngcic/rev2000/Explan.htm

His catalog provide more accurate positions, merge doublons etc..

He also provide more information on the type of the nebula. This info could be used to use icons matching the type of nebula, and also to draw ellipses for galaxies.

The code change should be located in modules/NebulaMgr.hpp/cpp and modules/Nebula.hpp/cpp

A lot of amateur astronomers set out to track down all of the Messier and Caldwell objects. It would, therefore, be very handy if Stellarium could highlight these objects. Envisage an option which would make all M (or C, or NGC, or Herschel) objects visible at all zoom levels and distinguish then from other DSOs by making their symbols a different colour and (optionally) labelling them by their catalog number.

'''Knowledge Prerequisite:''' Basic astronomy knowledge

'''Mentor:''' [https://launchpad.net/~alexwolf Alexander Wolf]

[[Category:Summer of Code]]

Main Page

2012-03-18T09:40:29Z

Daggerstab: + link to GSOC

__NOTOC__

==Welcome==
Welcome to the Stellarium wiki, a knowledge website about Stellarium, the free planetarium for your computer. The wiki allows Stellarium users to collectively build the knowledge base about Stellarium, so if you have something to add, register and edit the page.

<div style="float:left; width:29%; margin-right:25px;">
<div style="margin-bottom:25px; padding:7px; border:solid 1px #847f93;">
<h2>Getting started</h2>
* [[Stellarium Wiki:About Stellarium|What is Stellarium?]]
* [[Complete feature list]]
* [[Download|Where to download Stellarium]]
* [[Installation guide]]
* [[Quickstart guide]]
* [[Keyboard actions]]
* [[Screencasts]]
* [[FAQ|Frequently Asked Questions]]
===user guide===
* [[Stellarium_User_Guide|User Guide]] (in this wiki)
* [http://downloads.sourceforge.net/stellarium/stellarium_user_guide-0.10.2-1.pdf Download User's Guide PDF]
* [[:Category:User's_Guide|Other languages & links]]
* [[User guide contributions|Making user guide contributions]]
</div>

<div style="margin-bottom:25px; padding:7px; border:solid 1px #847f93;">

<h2>Extras</h2>

===extra files for Stellarium===
* [[Stars]]
* [[Landscapes]]
* [[Nebula images]]
* [[Scripts]]
* [[Solar System Objects]]
* [[Sky cultures]]: See how people across the world look at the heavens above.

===education===
* [[Education|Education Resources]]
</div>
</div>

<div style="float:left; width:29%; margin-right:25px;">
<div style="margin-bottom:25px; padding:7px; border:solid 1px #847f93;">
<h2>Help us</h2>
===Google Summer of Code===
Stellarium is participating in GSoC 2012!
*[[Google Summer of Code 2012|GSoC task list]]

===ongoing efforts===
* [[Translation of Stellarium|Translate Stellarium in your language]]
* [[Homepage translation|Translate the homepage in your language]]
* [[Help:Contents|Tips for editing the wiki]]
===specific things you can do===
* [[Help with_Fortran90|Compiling FORTRAN90 Neptunian satellite ephemeris]]
* [[File location test|Reports of where files go for different platforms]]
* [[Testers wanted|Help us test Stellarium]]
* [[Catalogue cleanup|Help to remove artifacts from the star catalogues]]
* [[Sky culture art research]]
</div>

<div style="margin-bottom:25px; padding:7px; border:solid 1px #847f93;">

<h2>Known bugs</h2>

===common problems===
* [[Known issues in Stellarium 0.10.1|In Version 0.10.1]]
* [[Known issues in Stellarium 0.10.2|In Version 0.10.2]]
* [[Known issues in Stellarium 0.10.3|In Version 0.10.3]]
* [[FAQ|Don't forget to check the FAQ]]
</div>
</div>

<div style="float:left; width:29%; margin-right:0px;">
<div style="margin-bottom:25px; padding:7px; border:solid 1px #847f93;">

<h2>Advanced topics</h2>
===projection===
* [[Setting up your own dome using Stellarium's spheric mirror distortion feature|Dome projection with a spheric mirror]]
===telescope control===
* [[Telescope Control|Control your telescope]]
* [[Telescope Compatibility|Telescope control compatibility]]
</div>

<div style="margin-bottom:25px; padding:7px; border:solid 1px #847f93;">

<h2>Developers</h2>
===compiling===
* [[How to get Stellarium's source code|Getting Stellarium's source code]]
* [[Compilation on Linux]]
* [[Windows Build Instructions]]
* [[Compilation on Macosx]]
* [[Plugin Development|Building and Developing Plugins]]

===coding===
* [[Coding Standard]]
* [[File and Directory Structure]]

===public mailing list===
* [http://sourceforge.net/mail/?group_id=48857 Follow what's going on by reading our public development mailing list] You can send e-mail to this list, but it will be moderated before it appears.

===release schedule===
* [[Release Schedule]]
</div>
</div>

MediaWiki:Titleblacklist

2012-03-16T14:23:19Z

Daggerstab: + "cheap"

# <pre>
# This is a title blacklist. Titles and users that match a regular expression here cannot be created.
# Use "#" for comments.
# This is case insensitive by default
.*loan.*
.*cheap.*
.*mortgage.*
.*jobs.*
.*forex.*
.*credit.*
.*payday.*
.*casino.*
.*poker.*
.*insurance.*
.*jewelry.*
.*cellulite.*
.*drug.*
.*crusher.*
.*cash.*
.*\s*buy\s*.*
.*\s*sale\s*.*
#</pre>

MediaWiki:Spam-blacklist

2012-03-16T14:21:47Z

Daggerstab: + "cheap"

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
cheap
insurance
loan
poker
bingo
casino
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
louisvuitton
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

Satellites plugin

2012-03-11T11:52:44Z

Daggerstab: /* Current format */

{{obsolete|12 November 2011 (but the problem dates from before that)}}
The Satellites plugin simulates artificial satellites in Earth orbit. Satellite orbits could not be predicted precisely enough using Stellarium's existing orbital models for Solar System bodies, as there are other factor involved - irregularities in the Earth's gravitational field, lunar interactions, atmospheric drag and so on. So this plugin implements the SGP4 and SDP4 orbital models, using as its input data in NORAD's {{wikipedia-en|two-line element set}} (TLE) format. Lists with TLEs for hundreds of satellites are available online and are regularly updated. The plugin downloads the lists prepared by [http://celestrak.com/ celestrak.com] to keep itself up-to-date, but the users can specify other sources online or load updates from local files.

==Enabling the Satellites plugin==
This plugin comes bundled with Stellarium version 0.10.3, although it is not enabled by default. To enable the plugin, open the configuration dialog and go to the plugins tab. Click '''Satellites''' from the list of available plugins and check the '''load at startup''' checkbox. You will need to re-start Stellarium for changes to take effect.

==Using the Satellites plugin==
To see the position of artificial satellites, you must have the observer location set to Earth. You must also turn on Satellite indicators on the main tool bar as shown in the image below:
<div align="center">
http://stellarium.org/wikiimg/sat_howto_02.jpg
</div>

===Searching for satellites===
It should now be possible to search for artificial satellites using the regular search dialog (F3). Note that at any given time, most Satellites will be below the horizon.
<div align="center">
http://stellarium.org/wikiimg/sat_howto_03.jpg
</div>
===Displaying satellite data===
{{obsolete-section}}
<div style="float:right">http://stellarium.org/wikiimg/sat_howto_04.jpg</div>
When you have selected a Satellite, information about it will be shown just as for any other object which is selected. This includes:

* Normal '''positional data''' (RA/Dec, Alt/Azi and so on)
* '''Range''' in kilometers. This is the line-of-sight distance between the observer and the selected satellite
* '''Range Rate''' in kilometers per second. This is the closing/parting speed of the satellite. It is useful when calculating doppler shift necessary for communications (and is also just nice to know)
* '''Altitude''' of the satellite above the ground in kilometers
* '''Comms''' data. Some satellites broadcast on frequencies which can be received by the general public or used by amateur radio operators. Where such data is known about a satellite Stellarium will show it.

<br clear="all"/>

===Configuration===
When the satellites plugin is loaded, the configuration button in the plugins tab of the configuration dialog will be enabled. Clicking this button (or pressing Control+Shift+Z) will open the configuration dialog for the satellites plugin.

====Settings tab====
<div style="float:right">http://stellarium.org/wikiimg/sat_howto_05.jpg</div>
In the settings tab you can control how often the Satellites plugin downloads updates for the TLE sets of known satellites. The default is every 72 hours. If an update is due when Stellarium is started, it will commence 30 seconds or so after the plugin is loaded.

If the box enabling updates from online sources is unchecked, a new button will appear. It allows loading satellite data from local files, a feature useful for computers without Internet access.

TODO
- update screenshot
- add information on satellite trajectories

<br clear="all"/>

====Satellites tab====
<div style="float:right">http://stellarium.org/wikiimg/sat_howto_06.jpg</div>
The Satellites tab shows data on known satellites and lets you choose which ones are displayed. Note that for each satellite which is displayed, Stellarium must do extra work to calculate and show the position of the satellite. If Stellarium is running very slowly with the Satellites plugin enabled, try reducing the number of satellites which are displayed.

You can select and go to a satellite by double clicking it in the list.

At time of writing, this dialog is only doe display information about satellites and changing their visibility. In future it will be possible to edit descriptions, comms data and so on, but this is not yet implements.

TODO
- update screenshot
- add information on selecting satellite groups
- add information on adding/removing satellites

<br clear="all"/>

====Sources tab====
<div style="float:right">http://stellarium.org/wikiimg/sat_howto_07.jpg</div>
The Sources tab lets you see (and modify) where Stellarium is getting its TLE data from. The default is a list of sources from [http://celestrak.com celestrak.com].

TODO:
- update screenshot
- descriptions of the different files

<br clear="all"/>

==Adding new satellites==

In version 0.7.1 of the plug-in, included with Stellarium 0.11.2, there is a simple way of adding satellites through a window opened by the "+" button on the "Satellites" tab of the plug-in's configuration window. For earlier versions and for more complex tasks (adding/modifying groups, colors, etc.), the only way to do it is by manually editing the satellites list (see below).

TODO:
- add screenshot
- explain that it uses the update lists
- explain how to use offline

==Editing the satellite list==

You can modify the <tt>satellites.json</tt> file manually using a text editor. '''If you are using Windows, it is strongly recommended to use an advanced text editor such as [http://notepad-plus-plus.org/ Notepad++]''' to avoid problems with end-of-line characters. (It will also color the JSON code and make it easier to read.)

'''Warning:''' Before editing your <tt>satellites.json</tt>, make a backup copy. Leaving out the smallest detail (such as a comma or forgetting to close a curly bracket) will prevent Stellarium from starting.

The path to the directory which contains <tt>satellites.json</tt> is something like:
{{user data directory|modules\Satellites|modules/Satellites}}

Note that the format of the <tt>satellites.json</tt> is different between Stellarium 0.11.2 and previous versions, so be careful.

===Current format===
:''Used in Satellites plug-in 0.7.1 and later (Stellarium 0.11.2 and later)''
To add a new satellite, open a new line after line 5 and paste the following, note commas and brackets, they are important:

<pre>
"NORAD number":
{
"name": "name of the satellite"
"description": "description goes here",
"comms": [
{
"description": "downlink 1",
"frequency": 437.49,
"modulation": "AFSK 1200 bps"
},
{
"description": "downlink 2",
"frequency": 145.825
}
],
"groups": ["group1", "group2"],
"tle1": "1 12345U 90005D 09080.85236265 .00000014 00000-0 20602-4 0 5632",
"tle2": "2 12345 98.2700 53.2702 0011918 71.1776 289.0705 14.31818920 653",
"visible": true
},
</pre>

Explanation of the fields:
* NORAD number - required parameter, surrounded by double quotes ("), followed by a colon (:). It is used internally to identify the satellite. You should replace the text "NORAD number" with the first number on both lines of the TLE set (in this case, "'''12345'''") It must match the number of the satellite in the source you are adding from if you want the TLE to be automatically updated.

The remaining parameters should be listed between two curly brackets and the closing curly bracket must be followed by a comma to separate it from the next satellite in the list:
* name - required parameter. It will be displayed on the screen and used when searching for the satellite with the Find window. Use the description field for a more readable name if you like. (The description field can accept HTML tags such as <tt><nowiki><br/></nowiki></tt> (new line), <code><nowiki><b></b></nowiki></code> (bold), etc.)
* description - optional parameter, double quoted. Appears when you click on the satellite
* comms- ''optional parameter'', square bracketed list of curly bracketed communications information.
* groups - ''optional parameter'', comma separated list of double quoted group names contained in square brackets. Used for grouping satellites in the drop down box on the config (see above)
* tle1 - required parameter, line 1 of the TLE, must be contained in double quotes and begin with "1 "
* tle2 - required parameter, line 2 of the TLE, must be contained in double quotes and begin with "2 "
* visible - required parameter, set to true if you want to see it, this can be toggled from the configuration window once the satellite is loaded.

You can edit the tags for a satellite, modify the description and comms data, and even add new satellites.

===Old format===
Before version 0.7.* of the plug-in (before Stellarium 0.11.2), the format of the <tt>satellites.json</tt> file was slightly different. It used only the name to identify satellites instead of their NORAD number:
<PRE>
"satellite name":
{
"description": "description goes here",
"comms": [
{
"description": "downlink 1",
"frequency": 437.49,
"modulation": "AFSK 1200 bps"
},
{
"description": "downlink 2",
"frequency": 145.825
}
],
"groups": ["group1", "group2"],
"tle1": "1 12345U 90005D 09080.85236265 .00000014 00000-0 20602-4 0 5632",
"tle2": "2 12345 98.2700 53.2702 0011918 71.1776 289.0705 14.31818920 653",
"visible": true
},
</PRE>
* satellite name - required parameter, double quoted with a colon following. Use the name as it appears in source you are updating from if you want the TLE to be automatically updated. Use the description field for a more readable name if you like. (The description field can accept HTML tags such as <tt><nowiki><br/></nowiki></tt> (new line), <code><nowiki><b></b></nowiki></code> (bold), etc.)

The remaining parameters should be includes in curly brackets, the closing curly bracket must be followed by a comma to separate it from the next satellite in the list.:
* description - optional parameter, double quoted. Appears when you click on the satellite
* comms- ''optional parameter'', square bracketed list of curly bracketed communications information.
* groups - ''optional parameter'', comma separated list of double quoted group names contained in square brackets. Used for grouping satellites in the drop down box on the config (see above)
* tle1 - required parameter, line 1 of the TLE, must be contained in double quotes and begin with "1 "
* tle2 - required parameter, line 2 of the TLE, must be contained in double quotes and begin with "2 "
* visible - required parameter, set to true if you want to see it, this can be toggled from the config once loaded.

===Online list creator===

A user (LCoronelP) has written a satellites.json creator in PHP using the TLE sources in your config.ini, you can use it [http://www.lbcoders.com/stellarium/createsatjson.php here], and the sourcecode is [http://www.lbcoders.com/stellarium/createsatjson.phps here].

Note: This generator only works if your sources are OK.

==Sources for TLE data==

* [http://celestrak.com/NORAD/elements/ Celestrak], used as default update source, it also has TLE lists beyond those included by default in Satellite plug-in
* [http://www.tle.info/joomla/index.php TLE.info]
* [http://www.space-track.org Space Track], the definitive source, requires signup, operated by United States Department of Defense

==TODO==
* Provide download links for alternative satellites.json files which include specialist lists of satellites.

[[Category:Plugins]]

Satellites plugin

2012-03-11T11:47:57Z

Daggerstab: update for the latest version - needs more work and new screenshots

{{obsolete|12 November 2011 (but the problem dates from before that)}}
The Satellites plugin simulates artificial satellites in Earth orbit. Satellite orbits could not be predicted precisely enough using Stellarium's existing orbital models for Solar System bodies, as there are other factor involved - irregularities in the Earth's gravitational field, lunar interactions, atmospheric drag and so on. So this plugin implements the SGP4 and SDP4 orbital models, using as its input data in NORAD's {{wikipedia-en|two-line element set}} (TLE) format. Lists with TLEs for hundreds of satellites are available online and are regularly updated. The plugin downloads the lists prepared by [http://celestrak.com/ celestrak.com] to keep itself up-to-date, but the users can specify other sources online or load updates from local files.

==Enabling the Satellites plugin==
This plugin comes bundled with Stellarium version 0.10.3, although it is not enabled by default. To enable the plugin, open the configuration dialog and go to the plugins tab. Click '''Satellites''' from the list of available plugins and check the '''load at startup''' checkbox. You will need to re-start Stellarium for changes to take effect.

==Using the Satellites plugin==
To see the position of artificial satellites, you must have the observer location set to Earth. You must also turn on Satellite indicators on the main tool bar as shown in the image below:
<div align="center">
http://stellarium.org/wikiimg/sat_howto_02.jpg
</div>

===Searching for satellites===
It should now be possible to search for artificial satellites using the regular search dialog (F3). Note that at any given time, most Satellites will be below the horizon.
<div align="center">
http://stellarium.org/wikiimg/sat_howto_03.jpg
</div>
===Displaying satellite data===
{{obsolete-section}}
<div style="float:right">http://stellarium.org/wikiimg/sat_howto_04.jpg</div>
When you have selected a Satellite, information about it will be shown just as for any other object which is selected. This includes:

* Normal '''positional data''' (RA/Dec, Alt/Azi and so on)
* '''Range''' in kilometers. This is the line-of-sight distance between the observer and the selected satellite
* '''Range Rate''' in kilometers per second. This is the closing/parting speed of the satellite. It is useful when calculating doppler shift necessary for communications (and is also just nice to know)
* '''Altitude''' of the satellite above the ground in kilometers
* '''Comms''' data. Some satellites broadcast on frequencies which can be received by the general public or used by amateur radio operators. Where such data is known about a satellite Stellarium will show it.

<br clear="all"/>

===Configuration===
When the satellites plugin is loaded, the configuration button in the plugins tab of the configuration dialog will be enabled. Clicking this button (or pressing Control+Shift+Z) will open the configuration dialog for the satellites plugin.

====Settings tab====
<div style="float:right">http://stellarium.org/wikiimg/sat_howto_05.jpg</div>
In the settings tab you can control how often the Satellites plugin downloads updates for the TLE sets of known satellites. The default is every 72 hours. If an update is due when Stellarium is started, it will commence 30 seconds or so after the plugin is loaded.

If the box enabling updates from online sources is unchecked, a new button will appear. It allows loading satellite data from local files, a feature useful for computers without Internet access.

TODO
- update screenshot
- add information on satellite trajectories

<br clear="all"/>

====Satellites tab====
<div style="float:right">http://stellarium.org/wikiimg/sat_howto_06.jpg</div>
The Satellites tab shows data on known satellites and lets you choose which ones are displayed. Note that for each satellite which is displayed, Stellarium must do extra work to calculate and show the position of the satellite. If Stellarium is running very slowly with the Satellites plugin enabled, try reducing the number of satellites which are displayed.

You can select and go to a satellite by double clicking it in the list.

At time of writing, this dialog is only doe display information about satellites and changing their visibility. In future it will be possible to edit descriptions, comms data and so on, but this is not yet implements.

TODO
- update screenshot
- add information on selecting satellite groups
- add information on adding/removing satellites

<br clear="all"/>

====Sources tab====
<div style="float:right">http://stellarium.org/wikiimg/sat_howto_07.jpg</div>
The Sources tab lets you see (and modify) where Stellarium is getting its TLE data from. The default is a list of sources from [http://celestrak.com celestrak.com].

TODO:
- update screenshot
- descriptions of the different files

<br clear="all"/>

==Adding new satellites==

In version 0.7.1 of the plug-in, included with Stellarium 0.11.2, there is a simple way of adding satellites through a window opened by the "+" button on the "Satellites" tab of the plug-in's configuration window. For earlier versions and for more complex tasks (adding/modifying groups, colors, etc.), the only way to do it is by manually editing the satellites list (see below).

TODO:
- add screenshot
- explain that it uses the update lists
- explain how to use offline

==Editing the satellite list==

You can modify the <tt>satellites.json</tt> file manually using a text editor. '''If you are using Windows, it is strongly recommended to use an advanced text editor such as [http://notepad-plus-plus.org/ Notepad++]''' to avoid problems with end-of-line characters. (It will also color the JSON code and make it easier to read.)

'''Warning:''' Before editing your <tt>satellites.json</tt>, make a backup copy. Leaving out the smallest detail (such as a comma or forgetting to close a curly bracket) will prevent Stellarium from starting.

The path to the directory which contains <tt>satellites.json</tt> is something like:
{{user data directory|modules\Satellites|modules/Satellites}}

Note that the format of the <tt>satellites.json</tt> is different between Stellarium 0.11.2 and previous versions, so be careful.

===Current format===
:''(Used in Satellites plug-in 0.7.1 and later (Stellarium 0.11.2 and later)''
To add a new satellite, open a new line after line 5 and paste the following, note commas and brackets, they are important:

<pre>
"NORAD number":
{
"name": "name of the satellite"
"description": "description goes here",
"comms": [
{
"description": "downlink 1",
"frequency": 437.49,
"modulation": "AFSK 1200 bps"
},
{
"description": "downlink 2",
"frequency": 145.825
}
],
"groups": ["group1", "group2"],
"tle1": "1 12345U 90005D 09080.85236265 .00000014 00000-0 20602-4 0 5632",
"tle2": "2 12345 98.2700 53.2702 0011918 71.1776 289.0705 14.31818920 653",
"visible": true
},
</pre>

Explanation of the fields:
* NORAD number - required parameter, surrounded by double quotes ("), followed by a colon (:). It is used internally to identify the satellite. You should replace the text "NORAD number" with the first number on both lines of the TLE set (in this case, "'''12345'''") It must match the number of the satellite in the source you are adding from if you want the TLE to be automatically updated.

The remaining parameters should be includes in curly brackets, the closing curly bracket must be followed by a comma to separate it from the next satellite in the list:
* name - required parameter. It will be displayed on the screen and used when searching for the satellite with the Find window. Use the description field for a more readable name if you like. (The description field can accept HTML tags such as <tt><nowiki><br/></nowiki></tt> (new line), <code><nowiki><b></b></nowiki></code> (bold), etc.)
* description - optional parameter, double quoted. Appears when you click on the satellite
* comms- ''optional parameter'', square bracketed list of curly bracketed communications information.
* groups - ''optional parameter'', comma separated list of double quoted group names contained in square brackets. Used for grouping satellites in the drop down box on the config (see above)
* tle1 - required parameter, line 1 of the TLE, must be contained in double quotes and begin with "1 "
* tle2 - required parameter, line 2 of the TLE, must be contained in double quotes and begin with "2 "
* visible - required parameter, set to true if you want to see it, this can be toggled from the configuration window once the satellite is loaded.

You can edit the tags for a satellite, modify the description and comms data, and even add new satellites.

===Old format===
Before version 0.7.* of the plug-in (before Stellarium 0.11.2), the format of the <tt>satellites.json</tt> file was slightly different. It used only the name to identify satellites instead of their NORAD number:
<PRE>
"satellite name":
{
"description": "description goes here",
"comms": [
{
"description": "downlink 1",
"frequency": 437.49,
"modulation": "AFSK 1200 bps"
},
{
"description": "downlink 2",
"frequency": 145.825
}
],
"groups": ["group1", "group2"],
"tle1": "1 12345U 90005D 09080.85236265 .00000014 00000-0 20602-4 0 5632",
"tle2": "2 12345 98.2700 53.2702 0011918 71.1776 289.0705 14.31818920 653",
"visible": true
},
</PRE>
* satellite name - required parameter, double quoted with a colon following. Use the name as it appears in source you are updating from if you want the TLE to be automatically updated. Use the description field for a more readable name if you like. (The description field can accept HTML tags such as <tt><nowiki><br/></nowiki></tt> (new line), <code><nowiki><b></b></nowiki></code> (bold), etc.)

The remaining parameters should be includes in curly brackets, the closing curly bracket must be followed by a comma to separate it from the next satellite in the list.:
* description - optional parameter, double quoted. Appears when you click on the satellite
* comms- ''optional parameter'', square bracketed list of curly bracketed communications information.
* groups - ''optional parameter'', comma separated list of double quoted group names contained in square brackets. Used for grouping satellites in the drop down box on the config (see above)
* tle1 - required parameter, line 1 of the TLE, must be contained in double quotes and begin with "1 "
* tle2 - required parameter, line 2 of the TLE, must be contained in double quotes and begin with "2 "
* visible - required parameter, set to true if you want to see it, this can be toggled from the config once loaded.

===Online list creator===

A user (LCoronelP) has written a satellites.json creator in PHP using the TLE sources in your config.ini, you can use it [http://www.lbcoders.com/stellarium/createsatjson.php here], and the sourcecode is [http://www.lbcoders.com/stellarium/createsatjson.phps here].

Note: This generator only works if your sources are OK.

==Sources for TLE data==

* [http://celestrak.com/NORAD/elements/ Celestrak], used as default update source, it also has TLE lists beyond those included by default in Satellite plug-in
* [http://www.tle.info/joomla/index.php TLE.info]
* [http://www.space-track.org Space Track], the definitive source, requires signup, operated by United States Department of Defense

==TODO==
* Provide download links for alternative satellites.json files which include specialist lists of satellites.

[[Category:Plugins]]

Download

2012-03-10T18:09:57Z

Daggerstab: /* Official packages */

=Official packages=
The [http://stellarium.org stellarium.org home page] contains links to the latest official releases for Windows, Mac OS, and a source package for Linux. The files themselves are hosted on Stellarium's project page at SourceForge.net:

http://sourceforge.net/projects/stellarium/files/

As of 10 March 2011, the latest version is '''0.11.2'''. Direct links:
* [http://sourceforge.net/projects/stellarium/files/Stellarium-win32/0.11.2/stellarium-0.11.2-win32.exe/download '''Windows''' (32-bit, installer)]
* Previously, there was an universal package of '''Mac OS X''', but for 0.10.6, it was split in two. For 0.11.2, there are:
** [http://sourceforge.net/projects/stellarium/files/Stellarium-MacOSX/0.11.2/Stellarium-0.11.2-Universal.dmg/download Mac OS X (Universal)]
** [http://sourceforge.net/projects/stellarium/files/Stellarium-MacOSX/0.11.2/Stellarium-0.11.2-Intel.dmg/download Mac OS X (Intel)]
** [http://sourceforge.net/projects/stellarium/files/Stellarium-MacOSX/0.11.2/Stellarium-0.11.2-PowerPC.dmg/download Mac OS X (PowerPC)]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-sources/0.11.2/stellarium-0.11.2.tar.gz/download '''Linux''' tarball (source package)] (for binary packages for Ubuntu, see below)

Older versions can be downloaded from the same place:
* [http://sourceforge.net/projects/stellarium/files/Stellarium-win32/ Windows]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-MacOSX/ Mac OS X]
* [http://sourceforge.net/projects/stellarium/files/Stellarium-sources/ Source packages]

==Stellarium packages for Ubuntu==
===Ubuntu-maintained packages===
If you are running Ubuntu, a Stellarium package exists in the Ubuntu repositories. It can be installed either through the '''Software Center''', or through a terminal with the following command:
sudo apt-get install stellarium

===Stellarium Releases PPA===

As the Stellarium release schedule does not follow closely the Ubuntu release schedule, often the Stellarium version in Ubuntu's repositories is not the latest one. Stellarium's team provides a Launchpad PPA (personal package archive) that allows Ubuntu users to obtain the latest released version.

The page of the PPA in Launchpad is here: [https://launchpad.net/~stellarium/+archive/stellarium-releases Stellarium Ubuntu Releases].

To install the packages from this PPA, you need to add it to your system's Software Sources. The PPA address is:
ppa:stellarium/stellarium-releases

You can add it either in the '''Software Center''' ("Edit" -> "Software Sources..." -> "Other software" -> "Add.."), or with a terminal, using the following commands:

sudo add-apt-repository ppa:stellarium/stellarium-releases
sudo apt-get update
sudo apt-get install stellarium

===Daily Builds PPA===

There is also a "daily builds" PPA that provides automatically built packages from the latest development code. It is updated once daily, or less often if there are no changes to the code.

'''Warning:''' This is provided '''for testing purposes only'''. Nothing guarantees that the latest development code will be usable. Use it at your own risk! (Thankfully, Ubuntu makes removing packages easy.) For that reason, we don't provide detailed instructions for adding this PPA. If you don't know how to use a PPA, you shouldn't use this one.

*[https://code.launchpad.net/~stellarium/+archive/daily Stellarium Daily Builds]

=Unofficial Packages=
''Please do not report bugs found in unofficial builds. Also, treat them as you would any software whose source cannot be easily verified (i.e. with caution).''

If you have, or know about, other unofficial builds (previews etc.), please list them here.

==Plugins==
{{obsolete|January 2011}}
===For Stellarium 0.10.2/Ubuntu i386===
* Bundle containing AngleMeasure, CompassMarks, Ocular, TextUserInterface and Satellite plugins. Un-tar this in your ~/.stellarium directory: [http://porpoisehead.net/misc/stellarium-plugin-bundle.tar.bz2 stellarium-plugin-bundle.tar.bz2]

===For Stellarium 0.10.2/Win32===
* Bundle of plugins (AngleMeasure, CompassMarks, Ocular): [http://porpoisehead.net/misc/stellarium-plugin-bundle.exe stellarium-plugin-bundle.exe]
* AngleMeasre 0.0.5 (including configurable display colors via the module.ini file) [http://porpoisehead.net/misc/stellarium-anglemeasure-plugin.exe stellarium-anglemeasure-plugin.exe]
* Satellites plugin installer (v0.1.1): [http://porpoisehead.net/misc/stellarium-satellites-plugin.exe stellarium-satellites-plugin.exe]

===For Stellarium 0.10.5/win32===
* With the release of version 0.10.5 the principal plugins are now static and will be automatically loaded when invoked from the configure menu
* Barry Gerdes maintains some updated pre-built patches and extras for Windows systems, which you can find on [http://sarcasmogerdes.dyndns.org/stellarium his site].

==Telescope Servers==
===Win32 Binaries===
*Zip file containing all the open source telescope servers [http://porpoisehead.net/mysw/downloads/win32_telescope_servers.zip here].

Or individually:
*[http://members.aon.at/johannes_gajdosik/TelescopeServerLx200.exe.gz TelescopeServerLx200.exe.gz]
*[http://members.aon.at/johannes_gajdosik/TelescopeServerNexStar.exe.gz TelescopeServerNexStar.exe.gz]
*[http://members.aon.at/johannes_gajdosik/TelescopeServerDummy.exe.gz TelescopeServerDummy.exe.gz]
Some people have problems with their browsers: the browser silently unpacks the gziped file. If you suffer from such a problem, just rename the downloaded file to TelescopeServerLx200.exe (or similar).

*With version 0.10.5 the expanded telescope control plugin is now loaded and configured from the plugin section of the confugure menu (F2)

User:Daggerstab

2012-02-27T19:45:53Z

Daggerstab: Reverted edits by Pasbancity1 (talk) to last revision by Daggerstab

'''Daggerstab''' is (the pseudonym of) a Bulgarian programmer.

*[http://badlyhonedbytes.wordpress.com Daggerstab's blog]
*[http://launchpad.net/~stellarium Daggerstab in Launchpad]
*[http://www.ohloh.net/accounts/daggerstab Daggerstab in Ohloh]

== TODO ==
* [[User:Daggerstab/TelescopeControl rewrite]]
* [[Template:User page]] and [[Template:User talk]] (and [[Template:Talk page]])
* Template for easy navigation between languages.
* [[Template:Unsigned]]
* Fixing the help page
* Fixing [[Project:Copyrights]]
* [[/Building Stellarium on Windows with Qt Creator/]]

===Things that are wrong with this wiki===
* The MediaWiki version
** No easily editable stylesheet (MediaWiki:Common.css)

== Mentions/reviews of Stellarium ==
* [http://astro.nineplanets.org/astrosoftware.html List of planetarium software] on Bill Arnett's Nine Planets website (a.k.a "The List of the Competition" :))
* [http://www.cloudynights.com/item.php?item_id=1896 The Silicon Sky Part I: Planetariums for PCs] (Cloudy Nights, September 2008?)
*Bad Astronomy and Universe Today Forums:
**[http://www.bautforum.com/bad-astronomy-stories/68142-bad-astronomy-stellarium-some-help-here.html Bad Astronomy on stellarium? Some help here?] (December 2007)
**[http://www.bautforum.com/space-astronomy-questions-answers/67770-star-viewing-software-website.html Star viewing software or website?] (December 2007)
**[http://www.bautforum.com/astronomy-cast/87697-free-planetarium-software.html Free Planetarium Software?] (April 2009)

== Other notes ==
The Sky-Watcher family:
* http://www.skywatchertelescope.net/ (main website?)
* http://www.skywatcherusa.com/
* http://www.opticalvision.co.uk/ (UK partner? The Explorer and Skymax brands.)

MediaWiki:Spam-blacklist

2012-02-22T20:24:32Z

Daggerstab: +1

# <pre>
# This is a list of domain names which are considered spam. Please check
# the guidelines on the talk page when adding entries. Changes should take
# effect immediately. Please do not use this list against spam that can
# be dealt with by user blocking or protection of a small number of pages.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts
# inside URLs
#Specific to Stellarium Wiki
insurance
loan
poker
bingo
casino
crusher
jewellery
jewelry
bracelet
ticket
estate
coupon
diamond
vending
louisvuitton
outlet
uggboot
market
psychic
hosting
cigarette
ukash
essay
natoli\.ru
ck-wholesale\.com
resumewritingservice\.biz
tablets.*\.ru
health.*\.ru
ameritrustshield
wellbeing\.ru
store\.ru
pills\.ru
drug.*\.ru
xsale\.com
ugg.*fashion
-ugg-
blogleaf\.com
palungjit\.com
cheapuggs
rotta\.ru
lease-a-seo\.com
payday\.co\.uk
hvacinstaller\.com
merchantos\.com
iwanttosellmydiamond\.net
pacquiaomosley\.co\.cc
antiqueszaar\.com
patioheaterz\.com
usfirepits\.com
bringexbackblog\.com
yourperfectenglish\.com
outdoorfountains\.com
bce-online\.com
slow-computers\.com
besttelescope\.co
siteandrunning\.com
magic-publisher\.com
cooperspick\.com
cars\.com
zaptechsolutions\.com
#</pre>

Google Summer of Code 2012

2012-02-13T18:55:11Z

Daggerstab:

Ideas for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC 2012] (Google Summer of Code 2012)

==Common requirements==
All of these tasks require knowledge of '''C/C++''', as Stellarium is written in it, and some knowledge of the [http://qt.nokia.com/products/ '''Qt framework'''] (or willingness to learn the basics very quickly), because Stellarium relies heavily on it, especially for its GUI.

==Ideas/projects==
===Support for collections of multi-resolution sky surveys ===
'''Brief explanation:''' Work has already started on this project and we have a working initial code displaying images encoded in the TOAST format.
The image data for each sky survey needs to be pre-processed and stored on a server. We currently have a server hosted by the Free Software Fundation France with a potentially high bandwith for serving the (huge amount of) data.

'''Knowledge Prerequisite:''' OpenGL, Geometry, Astronomy.

'''Mentor:'''

===Meteor shower calendar ===
:See [[Proposals:Realistic meteor showers]], Launchpad Blueprint: https://blueprints.launchpad.net/stellarium/+spec/realistic-meteor-showers
'''Brief explanation:''' At the moment, Stellarium can show meteors, but they are simply decorative - they appear at random points at a rate set by the user. The existing code of the MeteorMgr class can be used as a base for a plug-in that shows more or less scientifically accurate meteor showers. They are not random - the meteors appear to "stream" from a single point in the celestial sphere, the radiant.

This feature can take several forms:
* Weak form: Allows the user to define a meteor shower and/or pick it from a list, and then to turn it on and off on a whim.
* Strong form: Keeps a meteor shower catalogue in JSON format as with the other kinds of objects tracked by Stellarium, and shows only what should be in the sky for the given date. The catalogue should contain information about the radiant and the annual changes in the zenith hourly rate (as meteor showers typically have a peak and are active some time before and after that; a normal distribution function can do).
* Very strong form: Use a professional model for predicting meteor showers, based on the orbits of the clouds of space particles that cause them.

Data about visual meteor showers can be found on the website of the [http://www.imo.net International Meteor Organization] (e.g. [http://www.imo.net/calendar/2011 calendar for 2011])

The implementation should allow the user to toggle a marker showing the radiant.

'''Knowledge Prerequisite:''' OpenGL, Geometry, Basic Astronomy.

'''Mentor:'''

===Realistic comet rendering ===
:See [[Proposals:Realistic comet rendering]], Launchpad Blueprint: https://blueprints.launchpad.net/stellarium/+spec/realistic-comet-rendering
'''Brief explanation:''' At the moment, Stellarium supports comets as solar system bodies, but displays them as star-like objects. More realistic and more scientifically accurate rendering of a comet requires the rendering of four elements - a core, a coma and two tails, oriented according to the comet's relative position to the Sun and its direction. The tails and the coma should appear only when the comet is close enough to the Sun. (See the Wikipedia article on comets for more information.)

As not all comets are identical, this feature should allow comet customization. The visual characteristics of comets should be stored along with their orbital elements.

'''Knowledge Prerequisite:''' OpenGL, some mathematics and astronomy.

'''Mentor:'''

===Satellite shadows on parent planets===
At the moment, satellites in Stellarium don't cast visible shadows on their parent planets and vice versa (solar and lunar eclipses are implemented as special cases).

The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.

'''Knowledge Prerequisite:''' OpenGL

===Irregular Solar System bodies===
At the moment, all Solar System bodies are rendered as spheroids. This is fine for all planets and large satellites, but unrealistic for all asteroids and some smaller moons (such as Phobos, etc.). Realistic rendering of asteroids requires the rendering of a simple 3D model, either in some accepted open 3D model format (e.g. COLLADA?) or in a simple format developed for Stellarium. Rough shape data for about 20+ asteroids can be found somewhere on NASA's websites. Working on this project should start with finding it and deciding which format to use.

The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.

'''Knowledge Prerequisite:''' OpenGL

[[Category:Summer of Code]]

Talk:Google Summer of Code 2012

2012-02-13T18:36:35Z

Daggerstab:

== The planet rendering idea ==

The list has been copied from the SOCIS list, hasn't it?

I've removed this item:
<pre><nowiki>
===Project: Improve the planet rendering ===
:See Launchpad Blueprints https://blueprints.launchpad.net/stellarium/+spec/improved-planet-rendering and https://blueprints.launchpad.net/stellarium/+spec/realistic-atmospheric-phenomenas
'''Brief explanation:''' The current rendering is very basic: planets are ellipsoids mapped with a rectangular texture, lightning is very basic (material parameters are the same for each planets), no shadow or bump mapping is performed, no atmosphere is rendered when a planet is seen from outside its atmosphere.

The goal is to improve the code related to 3D rendering so that the level of realism is improved. Main features would be:
* Allow for 3D models, not only ellipsoids. This will allow proper rendering of non spherical asteroids, artificial satellites.
* Improve lightning openGL parameters (material, etc..).
* Allow for satellites/rings shadow on the mother planet.
* Rendering of atmospheric phenomenon: clouds, noctilucent clouds, zodiacal light, auroras.

During the last refactoring the code where all these operations appear was grouped in a single place, thus making coding easier. The main method to modify is Planet::draw3dModel(...)

'''Knowledge Prerequisite:''' OpenGL, Geometry, Basic Astronomy.

'''Mentor:'''</nowiki></pre>

It's too vaguely defined. Some work on atmospheres has been done by Hikiko, but we still haven't even decided what to do with it yet. I'm going to add some more defined task. Feel free to edit/argue.--[[User:Daggerstab|Daggerstab]] 18:35, 13 February 2012 (UTC)

Talk:Google Summer of Code 2012

2012-02-13T18:35:47Z

Daggerstab: The planet rendering idea

== The planet rendering idea ==

The list has been copied from the SOCIS list, hasn't it?

I've removed this item:
<nowiki>
===Project: Improve the planet rendering ===
:See Launchpad Blueprints https://blueprints.launchpad.net/stellarium/+spec/improved-planet-rendering and https://blueprints.launchpad.net/stellarium/+spec/realistic-atmospheric-phenomenas
'''Brief explanation:''' The current rendering is very basic: planets are ellipsoids mapped with a rectangular texture, lightning is very basic (material parameters are the same for each planets), no shadow or bump mapping is performed, no atmosphere is rendered when a planet is seen from outside its atmosphere.

The goal is to improve the code related to 3D rendering so that the level of realism is improved. Main features would be:
* Allow for 3D models, not only ellipsoids. This will allow proper rendering of non spherical asteroids, artificial satellites.
* Improve lightning openGL parameters (material, etc..).
* Allow for satellites/rings shadow on the mother planet.
* Rendering of atmospheric phenomenon: clouds, noctilucent clouds, zodiacal light, auroras.

During the last refactoring the code where all these operations appear was grouped in a single place, thus making coding easier. The main method to modify is Planet::draw3dModel(...)

'''Knowledge Prerequisite:''' OpenGL, Geometry, Basic Astronomy.

'''Mentor:'''</nowiki>

It's too vaguely defined. Some work on atmospheres has been done by Hikiko, but we still haven't even decided what to do with it yet. I'm going to add some more defined task. Feel free to edit/argue.--[[User:Daggerstab|Daggerstab]] 18:35, 13 February 2012 (UTC)

Google Summer of Code 2012

2012-02-13T18:31:53Z

Daggerstab: /* Project: Improve the planet rendering */ that was ill-defined the last time