User:Dan - Revision history

Dan: /* GitHub: SST */

2025-03-09T18:54:38Z

GitHub: SST

← Older revision		Revision as of 11:54, 9 March 2025
Line 15:		Line 15:
	# Click on the white font latest version.		# Click on the white font latest version.
	# Open up the "Assets" down arrow & select the MSI file with the latest version number.		# Open up the "Assets" down arrow & select the MSI file with the latest version number.
			# Download the file.

	To clone:		To clone:

Dan: /* GitHub: SST */

2025-03-09T18:53:24Z

GitHub: SST

← Older revision		Revision as of 11:53, 9 March 2025
Line 10:		Line 10:

	==GitHub: SST==		==GitHub: SST==
			To download latest compiled version:
			# Open the [https://github.com/varranvar/Starship-Tracker (primary, ''i.e.'', Varun's) repository's main page].
			# On the right sidebar, click on the white font "Releases".
			# Click on the white font latest version.
			# Open up the "Assets" down arrow & select the MSI file with the latest version number.

	To ~~Clone~~:		To clone:
	~~# Open the [https://github.com/RevancheSST/Starship-Tracker repository's main page].~~
	~~# Press the green "Code" button.~~
	~~# Copy the URL provided in the "Clone->HTTPS" section.~~
	# Open up the local target directory (i.e., C:\Users\Dan\Desktop\SST build\older\Cloned).		# Open up the local target directory (i.e., C:\Users\Dan\Desktop\SST build\older\Cloned).
	# Type "CMD" into the directory's address field.		# Type "CMD" into the directory's address field.
	# ~~Type "~~git clone https://github.com/~~RevancheSST~~/Starship-Tracker.git~~" into the open terminal.~~		# In the open terminal, type <pre>git clone https://github.com/varranvar/Starship-Tracker.git</pre>
	# Allow the download of the clone to complete and then close the terminal.		# Allow the download of the clone to complete and then close the terminal.

Dan: /* SRMs */

2025-03-09T18:39:05Z

SRMs

@@ Line 8: / Line 8: @@
 * Review article for new glossary terms.
 * Announce update of ship report.
 ==SRMs==

Dan: /* Reverse the process: JSON to Excel */

2025-01-29T01:32:35Z

Reverse the process: JSON to Excel

← Older revision		Revision as of 18:32, 28 January 2025
Line 73:		Line 73:
	# Export the (entire) Boundaries & Nebulae points from the campaign.		# Export the (entire) Boundaries & Nebulae points from the campaign.
	# Open the saved points file and search for the object (ex: Arachnid Nebula).		# Open the saved points file and search for the object (ex: Arachnid Nebula).
	# From the object's data, select everything after "points:" (including the opening and closing ~~braces~~) down to (bit not including) the comma before "boundary_thickness" and copy.		# From the object's data, select everything after "points:" (including the opening and closing brackets) down to (bit not including) the comma before "boundary_thickness" and copy.
	# Open the [https://tableconvert.com/json-to-excel TableConvert site].		# Open the [https://tableconvert.com/json-to-excel TableConvert site].
	:: a. Ensure the Data Source field is set to "JSON Array".		:: a. Ensure the Data Source field is set to "JSON Array".

Dan: /* Creating a new boundary or nebula */

2025-01-29T01:32:03Z

Creating a new boundary or nebula

← Older revision		Revision as of 18:32, 28 January 2025
Line 30:		Line 30:
	# Paste the coordinate data, ''including all three axis headers'' ('''x, y, z'''), into the top field ("Data Source") [https://tableconvert.com/excel-to-json on this site].		# Paste the coordinate data, ''including all three axis headers'' ('''x, y, z'''), into the top field ("Data Source") [https://tableconvert.com/excel-to-json on this site].
	# Scroll down to the site's Table Generator section. Ensure the "JSON" format is selected on the format bar above the display field.		# Scroll down to the site's Table Generator section. Ensure the "JSON" format is selected on the format bar above the display field.
	# Select the "Parsing JSON" check ~~box~~; this removes the quotations around the coordinates themselves.		# Select the "Parsing JSON" and "Minify JSON" check boxes; this removes the quotations around the coordinates themselves.
	# Ensure the JSON Format is set to "Array of Object".		# Ensure the JSON Format is set to "Array of Object".
	# Copy the resulting data from the field.		# Copy the resulting data from the field.

Dan: /* Reverse the process: JSON to Excel */

2025-01-28T11:54:38Z

Reverse the process: JSON to Excel

← Older revision		Revision as of 04:54, 28 January 2025
Line 69:		Line 69:

	====<span style="color:green">Reverse the process: JSON to Excel</span>====		====<span style="color:green">Reverse the process: JSON to Excel</span>====
			There are / may be reasons to save the data points in their Excel coordinate format. The [https://tableconvert.com/json-to-excel TableConvert site] will be used again for this process.

			# Export the (entire) Boundaries & Nebulae points from the campaign.
			# Open the saved points file and search for the object (ex: Arachnid Nebula).
			# From the object's data, select everything after "points:" (including the opening and closing braces) down to (bit not including) the comma before "boundary_thickness" and copy.
			# Open the [https://tableconvert.com/json-to-excel TableConvert site].
			:: a. Ensure the Data Source field is set to "JSON Array".
			:: b. Ensure the Table Generator field has "Excel" selected on the format bar above it. No options are checked.
			:: c. Paste the copied data from the points file into the Data Source field.
			:: d. Copy the converted data from the Table Generator field and paste to your target file.

	==SST Knowledge Base==		==SST Knowledge Base==

Dan: /* Adding onto an existing boundary or nebula */

2025-01-28T11:42:39Z

Adding onto an existing boundary or nebula

← Older revision		Revision as of 04:42, 28 January 2025
Line 67:		Line 67:
	# Save the file and import to a temporary campaign to check for errors. This file will have ''only'' the points for the campaign's boundaries & nebulae, not for any other location. ''Remember to turn off '''Parallax''' mode when checking for errors.''		# Save the file and import to a temporary campaign to check for errors. This file will have ''only'' the points for the campaign's boundaries & nebulae, not for any other location. ''Remember to turn off '''Parallax''' mode when checking for errors.''
	# If there are no errors, open the target campaign and either merge this temporary campaign with it or import the '''Boundaries and Nebulae''' JSON file directly.		# If there are no errors, open the target campaign and either merge this temporary campaign with it or import the '''Boundaries and Nebulae''' JSON file directly.

			====<span style="color:green">Reverse the process: JSON to Excel</span>====

	==SST Knowledge Base==		==SST Knowledge Base==

Dan at 15:20, 21 January 2025

2025-01-21T15:20:44Z

← Older revision		Revision as of 08:20, 21 January 2025
Line 16:		Line 16:

	* [https://www.dailystartreknews.com/read/tag/In+Memoriam In Memoriam (Daily Star Trek News)]		* [https://www.dailystartreknews.com/read/tag/In+Memoriam In Memoriam (Daily Star Trek News)]


	==SST==		==SST==

Dan: /* SST */

2025-01-10T15:27:50Z

SST

← Older revision		Revision as of 08:27, 10 January 2025
Line 20:		Line 20:
	==SST==		==SST==
	===How to...JSON file conversion===		===How to...JSON file conversion===
	====Creating a new boundary or nebula====		====<span style="color:green">Creating a new boundary or nebula</span>====
	<u>'''Prepare the JSON file'''</u>		<u>'''Prepare the JSON file'''</u>
	# Open a new temporary campaign.		# Open a new temporary campaign.
Line 48:		Line 48:
	: 3. You may now import the JSON file into your primary campaign, but it is recommended you first import it into the temporary campaign made for the single nebula / boundary. From there you can check for conversion errors and to make sure the name label is in proximity to the object. ''Remember to turn off '''Parallax''' mode when checking for errors.'' Following that, open your primary campaign and merge in the temporary campaign (by selecting the temporary campaign's file). Your nebula or boundary should now appear in the place you directed.		: 3. You may now import the JSON file into your primary campaign, but it is recommended you first import it into the temporary campaign made for the single nebula / boundary. From there you can check for conversion errors and to make sure the name label is in proximity to the object. ''Remember to turn off '''Parallax''' mode when checking for errors.'' Following that, open your primary campaign and merge in the temporary campaign (by selecting the temporary campaign's file). Your nebula or boundary should now appear in the place you directed.

	====Adding onto an existing boundary or nebula====		====<span style="color:green">Adding onto an existing boundary or nebula</span>====
	This is both simpler & possibly more complicated.		This is both simpler & possibly more complicated.

Dan: /* How to...JSON file conversion */

2025-01-10T15:25:44Z

How to...JSON file conversion

← Older revision		Revision as of 08:25, 10 January 2025
Line 21:		Line 21:
	===How to...JSON file conversion===		===How to...JSON file conversion===
	====Creating a new boundary or nebula====		====Creating a new boundary or nebula====
	[u]'''Prepare the JSON file'''[/u]		<u>'''Prepare the JSON file'''</u>
	# Open a new temporary campaign.		# Open a new temporary campaign.
	# Create a new nebula or boundary. While its location does not matter at this point, you might want to place the Label Coordinates in the vicinity of the nebula/boundary (based on your compiled coordinate points). You do not need to add any points at this time.		# Create a new nebula or boundary. While its location does not matter at this point, you might want to place the Label Coordinates in the vicinity of the nebula/boundary (based on your compiled coordinate points). You do not need to add any points at this time.
Line 27:		Line 27:
	# Go to Settings->Data and press "Export Boundaries and Nebulae to JSON", saving the file to a location of your choosing.		# Go to Settings->Data and press "Export Boundaries and Nebulae to JSON", saving the file to a location of your choosing.

	* '''Convert the data'''		<u>'''Convert the data'''</u>
	# The data you will be converting needs to be prepared on your spreadsheet in three columns labeled "x", "y", & "z". The "z" column is required, even if your map is 2D; the Z coordinates should all be 0 (zero), if this is the case.		# The data you will be converting needs to be prepared on your spreadsheet in three columns labeled "x", "y", & "z". The "z" column is required, even if your map is 2D; the Z coordinates should all be 0 (zero), if this is the case.
	# Paste the coordinate data, ''including all three axis headers'' ('''x, y, z'''), into the top field ("Data Source") [https://tableconvert.com/excel-to-json on this site].		# Paste the coordinate data, ''including all three axis headers'' ('''x, y, z'''), into the top field ("Data Source") [https://tableconvert.com/excel-to-json on this site].
Line 35:		Line 35:
	# Copy the resulting data from the field.		# Copy the resulting data from the field.

	* '''Update the JSON file'''		<u>'''Update the JSON file'''</u>
	: 1. In your exported JSON file, replace the two brackets ('''[]''') right after '''"points:"''' with the converted data. Your JSON file will expand to include all of the coordinates in the Array of Object format and should be followed by ''', "boundary thickness:"'''. Be sure to include the comma following the closing bracket (''']''').<br>The last entry should look similar to this (followed by the remainder of the JSON file data):<br>		: 1. In your exported JSON file, replace the two brackets ('''[]''') right after '''"points:"''' with the converted data. Your JSON file will expand to include all of the coordinates in the Array of Object format and should be followed by ''', "boundary thickness:"'''. Be sure to include the comma following the closing bracket (''']''').<br>The last entry should look similar to this (followed by the remainder of the JSON file data):<br>
	<pre>		<pre>
Line 51:		Line 51:
	This is both simpler & possibly more complicated.		This is both simpler & possibly more complicated.

	* '''Existing object file'''<br>		<u>'''Existing object file'''</u><br>
	If there is an existing individually-saved up-to-date JSON file for this particular object, then it is a bit easier.		If there is an existing individually-saved up-to-date JSON file for this particular object, then it is a bit easier.
	# Convert the new coordinates per the '''Convert the data''' section above but, for the final step, only copy the data between the two brackets ('''[]'''), not the brackets themselves. Instead, capture the data starting with and including the two braces ('''{}''') that are within the two external brackets.		# Convert the new coordinates per the '''Convert the data''' section above but, for the final step, only copy the data between the two brackets ('''[]'''), not the brackets themselves. Instead, capture the data starting with and including the two braces ('''{}''') that are within the two external brackets.
Line 60:		Line 60:
	# Open the target campaign and either merge this temporary campaign with it or import the boundary / nebula object's JSON file directly.		# Open the target campaign and either merge this temporary campaign with it or import the boundary / nebula object's JSON file directly.

	* '''No existing object file'''<br>		<u>'''No existing object file'''</u><br>
	If there is no individually-saved up-to-date JSON file for this particular object, the data will need to be added to the campaign's points database. Care must be taken to not corrupt the campaign's existing points, so it is recommended the entire campaign be saved prior to the following steps being taken.		If there is no individually-saved up-to-date JSON file for this particular object, the data will need to be added to the campaign's points database. Care must be taken to not corrupt the campaign's existing points, so it is recommended the entire campaign be saved prior to the following steps being taken.
	# Convert the new coordinates per the '''Convert the data''' section above but, for the final step, only copy the data between the two brackets ('''[]'''), not the brackets themselves. Instead, capture the data starting with and including the two braces ('''{}''') that are within the two external brackets.		# Convert the new coordinates per the '''Convert the data''' section above but, for the final step, only copy the data between the two brackets ('''[]'''), not the brackets themselves. Instead, capture the data starting with and including the two braces ('''{}''') that are within the two external brackets.