Difference between revisions of "Autogenerated Galaxy Guide"
(New page: This is a kind of "Project Page" for the Autogenerated Galaxy Guide. == Status == I have set up a System List for Galaxy Sector One and pages for Lerelace and Oresri ...) |
m (→Icons: Typo) |
||
Line 35: | Line 35: | ||
=== Icons === |
=== Icons === |
||
− | I grabbed the icons for governments and economies for the project |
+ | I grabbed the icons for governments and economies for the project from an Oolite font png found in the sources: |
[[image:Logo64_Anarchy.png]] [[image:Logo64_Feudal.png]] |
[[image:Logo64_Anarchy.png]] [[image:Logo64_Feudal.png]] |
Revision as of 13:00, 4 October 2009
This is a kind of "Project Page" for the Autogenerated Galaxy Guide.
Contents
Status
I have set up a System List for Galaxy Sector One and pages for Lerelace and Oresri as samples.
Please don't edit these pages manually as they will propably be overwritten one day with a more current version.
I am working on "Prices and Availabilities" for the systems.
I know that "Planet Radius" is still missing. I just forgot it...
I have to find out where to get the Information on sun and planet colors and station types.
I have to find which OXPs are considered canonical enough for inclusion into the guide.
For requests and criticism use the thread Galaxy Guideon the Oolite Bulletin Board.
I found that there was an earlier attempt at generating such a guide, see Zaonce and Tionisla. As this was dated somewhere 2007 and 2008, I consider this abandoned.
The systems Lave, Vetitice, and Tianve in the first sector have manually written pages, which I will respect, of course. If my design is found agrreable, I will manually integrate those pages.
I'm planning to integrate two more advanced features into a systems' page: An overview map to locate the system in the map, and a local area map showing the worlds in witchspace distance. Both can be done by abusing the "timeline" feature of the MediaWiki if I read the documentation correctly, but this will definitely require an update of the EliteWiki engine (which is at Version 1.9, the current Stable Version is 1.15.1).
Aims
I started this project because I consider it crucial that in such a multi-author environment the store background is as consistent as possible. When I asked how the various fiction and OXP writers communicate and coordinate their efforts and how they know whether a system is already part of another authors story domain, I only learned that there is no real coordination and synchronisation effort.
Another factor was to get a better overview over the worlds of the Oolite multiverse.
Sources
Information
I started off with an extract of the list in Oolite planet list/Galaxy 1, but I soon learned that this would never give me the information on prices and availabilities of items, so I analyzed the TXTELITE and Oolite sources and the spreadsheet and wrote a perl module to give me all the relevant information.
I took the information on trade routes and regions from the Downloadable Vector Map of Galaxy 1 made by ClymAngus.
Icons
I grabbed the icons for governments and economies for the project from an Oolite font png found in the sources:
The Icons for the tech level were made by me:
Tech Level | Logo for the System template | Compact version for tables |
---|---|---|
1 | ||
2 | ||
3 | ||
4 | ||
5 | ||
6 | ||
7 | ||
8 | ||
9 | ||
10 | ||
11 | ||
12 | ||
13 | ||
14 | ||
15 |
Templates
To ease the programming and helping to get a more consistent look, I designed various templates:
The System Description Box on the right side | Template:System |
The box for the original Oolite System Descriptions | Template:GalacticCatalogueEntry |
Header, Entry and Footer for a Witchspace List | Template:WitchspaceHeader Template:WitchspaceEntry Template:WitchspaceFooter |
Header, Entry and Footer for a Systems List | Template:SectorTableHeader Template:SectorTableEntry Template:SectorTableFooter |
Dummy templates needed to accomodate ancient MediaWiki
As the extension ParserFunctions 1.1.1 for the MediaWiki 1.9 does not support the "switch" function, I had to work around some problems by creating a bunch of dummy Templates: