User:DOUG/Sandbox Lich Stuff - Revision history

DOUG: /* GTK3 Beta Test */

2021-03-12T20:51:48Z

GTK3 Beta Test

← Older revision		Revision as of 15:51, 12 March 2021
Line 3:		Line 3:
	==GTK3 Beta Test==		==GTK3 Beta Test==

			The GTK3 Beta Test period is over, and has been released to the public for general use. Please see the [[Lich_(software)/Installation]] page.
	Welcome to the GTK3 Ruby Lich Public Beta!

	Before we begin, there are a couple of things you should know about participating in this beta program:

	1) It IS a beta program. If something can go wrong, it just might, here. So follow these instructions carefully to have the BEST shot at recovering your Lich installation and continuing to enjoy Gemstone.

	* It is vitally important that you NOT participate in the GTK3 beta if you are not already a Lich user. If you are new to Gemstone and Lich, do not use this Public Beta. Instead, use the stable installer build at https://bit.ly/WinLich .

	* If you are already a Lich user, and you are comfortable participating in the Public Beta, then you should at an absolute minimum, back up your existing Lich folder. The beta installer does not touch the existing lich folder, but if something can go wrong, you should have a copy saved somewhere.

	* If you are already a Lich user, and you are comfortable participating in the Public Beta, then you should rename your existing Ruby installation. If you accepted the default installation from the stable installer build, your Ruby installation is at C:\Ruby4Lich . You can simply rename that folder C:\save-Ruby4Lich , and you will be able to easily revert back from the beta to your current Ruby4Lich installation.

	* Remember that the GTK3 beta is intended to retire GTK2, given its age and lack of updates. What this means to you is that any Lich program that uses a graphical user interface (GUI) will behave differently. The team has updated the LICH.RBW file and the core scripts distributed by Tillmen to work with GTK3. The team has also updated some of the more popular scripts and included them in a subdirectory for you to use, if you wish.

	2) If you are happy with what you have read so far, and are eager to get started, exit all characters from the game.

	3) Back up your lich directory and rename your existing Ruby4Lich (or other Ruby) installation.

	4) Download the BetaGTK3-Ruby4Lich installer here: https://www.dropbox.com/s/upkg2qy1vmip31z/BetaGTK3-Ruby4Lich.exe?dl=1

	5) Run the installer. Be patient, it may take some time especially on non-SSD harddrives - it is installing 70K plus files.

	6) When done, click FINISH on the installer, and you will see the GTK3Lich folder on your desktop. Run the LICH.RBW file from that folder and confirm you can log in with Lich active.

	At this point, you can make plans to copy the GTK3Lich files into your existing Lich directory so you don't have to redo everything. You did remember to back up your existing Lich directory, right? If not, do it now before you start moving scripts around.

	Any and all errors please share in the #scripting channel on Discord. Please ensure you provide a current run of ''';version''' with your report

	Enjoy!



	===GTK3 Public Beta FAQ===

	'''Q: Why am I renaming my Ruby4Lich directory instead of just deleting it?'''

	A: During the beta test you may find a critical script that you cannot live without that simply does not work right. If you delete your existing Ruby4Lich installation, and later decide to exit the beta test, you'll have to reinstall Ruby4Lich to continue enjoying Lich and Gemstone. Renaming will save you time, if you decide the beta program is not for you.

	'''Q: What should I do when I see a bunch of information about a script that I'm running needing to be fixed?'''

	A: Come to Discord#scripting and put the script name up with a reference to GTK3. The team will look at it, and convert it or notify the script author to do the update.

	'''Q: I just copied the new GTK3Lich scripts into my standard Lich folder, and now nothing works right. What do I do?'''

	A: Check to be sure you also copied the Lich.rbw file over - without that, your install will not work properly.

	'''Q: Why are we doing this when the existing installer works?'''

	A: Three reasons - the most important being that we want to update to a faster and more stable Ruby. Second, we want to get onto the more current graphics display framework (GTK3), since the older existing graphics display framework (GTK2) is not updated and has some defects in it. Third, some exciting new scripts are being developed that will only work with the more current graphics display framework.

	'''Q: What's my emergency recovery procedure if I just want to go back to what I know?'''

	A: Tricky question! That will depend on what you did or chose not to do from the recommendations. The short list based on the recommendations is to restore your original LICH folder from the copy you made at the very beginning, then uninstall the GTK3Beta-Ruby4Lich application and delete the folder, then rename your saved Ruby4Lich folder back to just Ruby4Lich. You are now ready to try starting up your restored LICH installation. If it asks you how to deal with lich.rbw, just associate the file with the Ruby4Lich\bin\rubyw.exe application. That should restore your functionality. If it doesn't, swing by Discord#scripting and let us know.

	<section end=GTK3PublicBeta />

DOUG at 19:09, 9 September 2020

2020-09-09T19:09:38Z

← Older revision		Revision as of 14:09, 9 September 2020
Line 37:		Line 37:
	===GTK3 Public Beta FAQ===		===GTK3 Public Beta FAQ===

	Q: Why am I renaming my Ruby4Lich directory instead of just deleting it?		'''Q: Why am I renaming my Ruby4Lich directory instead of just deleting it?'''

	A: During the beta test you may find a critical script that you cannot live without that simply does not work right. If you delete your existing Ruby4Lich installation, and later decide to exit the beta test, you'll have to reinstall Ruby4Lich to continue enjoying Lich and Gemstone. Renaming will save you time, if you decide the beta program is not for you.		A: During the beta test you may find a critical script that you cannot live without that simply does not work right. If you delete your existing Ruby4Lich installation, and later decide to exit the beta test, you'll have to reinstall Ruby4Lich to continue enjoying Lich and Gemstone. Renaming will save you time, if you decide the beta program is not for you.

	Q: What should I do when I see a bunch of information about a script that I'm running needing to be fixed?		'''Q: What should I do when I see a bunch of information about a script that I'm running needing to be fixed?'''

	A: Come to Discord#scripting and put the script name up with a reference to GTK3. The team will look at it, and convert it or notify the script author to do the update.		A: Come to Discord#scripting and put the script name up with a reference to GTK3. The team will look at it, and convert it or notify the script author to do the update.

	Q: I just copied the new GTK3Lich scripts into my standard Lich folder, and now nothing works right. What do I do?		'''Q: I just copied the new GTK3Lich scripts into my standard Lich folder, and now nothing works right. What do I do?'''

	A: Check to be sure you also copied the Lich.rbw file over - without that, your install will not work properly.		A: Check to be sure you also copied the Lich.rbw file over - without that, your install will not work properly.

	Q: Why are we doing this when the existing installer works?		'''Q: Why are we doing this when the existing installer works?'''

	A: Three reasons - the most important being that we want to update to a faster and more stable Ruby. Second, we want to get onto the more current graphics display framework (GTK3), since the older existing graphics display framework (GTK2) is not updated and has some defects in it. Third, some exciting new scripts are being developed that will only work with the more current graphics display framework.		A: Three reasons - the most important being that we want to update to a faster and more stable Ruby. Second, we want to get onto the more current graphics display framework (GTK3), since the older existing graphics display framework (GTK2) is not updated and has some defects in it. Third, some exciting new scripts are being developed that will only work with the more current graphics display framework.

	Q: What's my emergency recovery procedure if I just want to go back to what I know?		'''Q: What's my emergency recovery procedure if I just want to go back to what I know?'''

	A: Tricky question! That will depend on what you did or chose not to do from the recommendations. The short list is to restore your original LICH folder from the copy you made at the very beginning, then uninstall the GTK3Beta-Ruby4Lich application and delete the folder, then rename your saved Ruby4Lich folder back to just Ruby4Lich. ~~Then,~~ try starting up your restored LICH installation. If it asks you how to deal with lich.rbw, just associate the file with the Ruby4Lich\bin\rubyw.exe application. That should restore your functionality. If it doesn't, swing by Discord#scripting and let us know.		A: Tricky question! That will depend on what you did or chose not to do from the recommendations. The short list based on the recommendations is to restore your original LICH folder from the copy you made at the very beginning, then uninstall the GTK3Beta-Ruby4Lich application and delete the folder, then rename your saved Ruby4Lich folder back to just Ruby4Lich. You are now ready to try starting up your restored LICH installation. If it asks you how to deal with lich.rbw, just associate the file with the Ruby4Lich\bin\rubyw.exe application. That should restore your functionality. If it doesn't, swing by Discord#scripting and let us know.

	<section end=GTK3PublicBeta />		<section end=GTK3PublicBeta />

DOUG: Minor Update

2020-09-09T19:07:51Z

Minor Update

← Older revision		Revision as of 14:07, 9 September 2020
Line 35:		Line 35:


	===FAQ===		===GTK3 Public Beta FAQ===

	Q: Why am I renaming my Ruby4Lich directory instead of just deleting it?		Q: Why am I renaming my Ruby4Lich directory instead of just deleting it?

DOUG: Initial GTK3 Beta Public Invite (for transclusion)

2020-09-09T19:06:34Z

Initial GTK3 Beta Public Invite (for transclusion)

Show changes

DOUG at 17:53, 14 June 2018

2018-06-14T17:53:35Z

Show changes

DOUG: /* Update 8/2/2016 */ The next greatest OS is in public beta - yay.

2016-08-09T06:18:29Z

Update 8/2/2016: The next greatest OS is in public beta - yay.

@@ Line 2: / Line 2: @@
 Initial effort successful.  Now working with basic installation.  Basic installation below successful (for those who might be peeking and simply can't wait).  Now working on bottling the two odd lines (cairo and gtk+).  If I can bottle them, I should be able to build a binaries distribution package that won't require a long time compiling these brew recipes and the gems.  It'll start being El Cap only, but I might add Mavericks and Yosemite to the binaries package as well.  I'd have to move to downloading most of the bottles at that point, but it still would be significantly faster.
 ==Update 8/2/2016==
@@ Line 20: / Line 40: @@
 create applescript applet (or bash script that calls osascript) to automate the login sequence
 ==Results from lichdiag.sh==

DOUG: And there. Adding a next step or two. . .

2016-08-02T07:48:57Z

And there. Adding a next step or two. . .

← Older revision		Revision as of 02:48, 2 August 2016
Line 2:		Line 2:

	Initial effort successful. Now working with basic installation. Basic installation below successful (for those who might be peeking and simply can't wait). Now working on bottling the two odd lines (cairo and gtk+). If I can bottle them, I should be able to build a binaries distribution package that won't require a long time compiling these brew recipes and the gems. It'll start being El Cap only, but I might add Mavericks and Yosemite to the binaries package as well. I'd have to move to downloading most of the bottles at that point, but it still would be significantly faster.		Initial effort successful. Now working with basic installation. Basic installation below successful (for those who might be peeking and simply can't wait). Now working on bottling the two odd lines (cairo and gtk+). If I can bottle them, I should be able to build a binaries distribution package that won't require a long time compiling these brew recipes and the gems. It'll start being El Cap only, but I might add Mavericks and Yosemite to the binaries package as well. I'd have to move to downloading most of the bottles at that point, but it still would be significantly faster.

			==Update 8/2/2016==

			Ok, I'm satisfied with the bash scripts. I'll be releasing them through the wiki on the Mac Install page.

			Next steps:

			Create brew point

			Create brew formula

			distribute through brew

			And later:

			create install_wine shell script for SFE / Wizard

			create applescript applet (or bash script that calls osascript) to automate the login sequence


	==Results from lichdiag.sh==		==Results from lichdiag.sh==

DOUG: /* Current Issues */ Status with output samples - yay.

2016-08-01T05:27:27Z

Current Issues: Status with output samples - yay.

← Older revision		Revision as of 00:27, 1 August 2016
Line 3:		Line 3:
	Initial effort successful. Now working with basic installation. Basic installation below successful (for those who might be peeking and simply can't wait). Now working on bottling the two odd lines (cairo and gtk+). If I can bottle them, I should be able to build a binaries distribution package that won't require a long time compiling these brew recipes and the gems. It'll start being El Cap only, but I might add Mavericks and Yosemite to the binaries package as well. I'd have to move to downloading most of the bottles at that point, but it still would be significantly faster.		Initial effort successful. Now working with basic installation. Basic installation below successful (for those who might be peeking and simply can't wait). Now working on bottling the two odd lines (cairo and gtk+). If I can bottle them, I should be able to build a binaries distribution package that won't require a long time compiling these brew recipes and the gems. It'll start being El Cap only, but I might add Mavericks and Yosemite to the binaries package as well. I'd have to move to downloading most of the bottles at that point, but it still would be significantly faster.

			==Results from lichdiag.sh==
	==Current Issues==

			Ok, this one's ready for prime time, I think.
	Nearly finished with core install script. Need to solve for CLT install and sudo brew - if they are in fact linked.

			===Results from 10.9.5 system actively used===

			<pre{{log2}}>

			Welcome to Mac OS X and Lich Diagnostics
			Run on Sun Jul 31 22:11:29 PDT 2016


			#############################################################
			## Item ## Version ## Status ##
			#############################################################
			## Your OS is supported ## 10.9.5 ## ✔ ##
			## You have xQuartz installed ## 2.7.94 ## ✔ ##
			## You have Command Line Tools ## 6.2.0.0.1 ## ✔ ##
			## Your Ruby may not work ## 2.3.1 ## ✘ ##
			## Homebrew is installed ## 0.9.9 ## ✔ ##
			## Ruby mgr rbenv is installed ## 1.0.0 ## ✔ ##
			## Cairo installed ## 1.12.16_1 ## ✔ ##
			## gtk+ tools installed ## 2.24.23 ## ✔ ##
			## sqlite3 gem installed ## 1.3.11 ## ✔ ##
			## gtk2 gem installed ## 3.0.8 ## ✔ ##
			## You have Lich ## ## ✔ ##
			## You have Avalon ## ## ✔ ##
			##############################################################


			If you are running this script because you're having a
			problem with getting Lich (or a script, like narost) to
			run, but you don't see anything in the diagnostics check
			that can help, this script can save further diagnostic
			information to the diagnostics text file on your desktop,
			so you can forward it for analysis to someone you trust.


			Gather additonal diagnostics? (y/n) y



			Script finished in 13 sec from script start

			Script finished: Sun Jul 31 22:11:42 PDT 2016
			</pre>

			===Results from 10.11 bare bones reference system===

			<pre{{log2}}>

			Welcome to Mac OS X and Lich Diagnostics
			Run on Sun Jul 31 22:00:51 PDT 2016


			##############################################################
			## Item ## Version ## Status ##
			##############################################################
			## Your OS is supported ## 10.11.6 ## ✔ ##
			## You do not have xQuartz ## ----- ## ✘ ##
			## You do not have CL Tools ## ----- ## ✘ ##
			## Your Ruby needs updating ## 2.0.0 ## ✘ ##
			## Homebrew is not installed ## ----- ## ✘ ##
			## Ruby mgr rbenv not installed ## ----- ## ✘ ##
			## Without Homebrew, no Cairo ## ----- ## ✘ ##
			## Without Homebrew, no gtk+ ## ----- ## ✘ ##
			## sqlite3 gem installed ## 1.3.7 ## ✔ ##
			## gtk2 gem not found ## --- ## ✘ ##
			## You should download lich ## ## ✘ ##
			## You should download Avalon ## ## ✘ ##
			##############################################################


			If you are running this script because you're having a
			problem with getting Lich (or a script, like narost) to
			run, but you don't see anything in the diagnostics check
			that can help, this script can save further diagnostic
			information to the diagnostics text file on your desktop,
			so you can forward it for analysis to someone you trust.


			Gather additonal diagnostics? (y/n) n
			Quitting...



			Script finished in 14 sec from script start

			Script finished: Sun Jul 31 22:01:05 PDT 2016
			</pre>

			Additional diags presently is brew --config and gem env outputs.

			As time goes on, I'll build in a library of recommendations for the user to consider live.

			The installer script is also ready for beta release. It isn't nearly as nicely formatted, but it installs to the 10.11 bare reference system.

			Will be testing on 10.9 and 10.10 (mebbe?) throughout the week.

			==Current Issues==

			Formatting on install script - and sudo is going to be required for xQuartz and Homebrew - so dreams of unattended install vanish in the night like a fresh breeze of jasmine.

	==7/30 Testing status: V 1.0==		==7/30 Testing status: V 1.0==

DOUG: /* Current Issues */ Almost there. Aaaalmoooost there!

2016-07-31T02:19:22Z

Current Issues: Almost there. Aaaalmoooost there!

← Older revision		Revision as of 21:19, 30 July 2016
Line 5:		Line 5:
	==Current Issues==		==Current Issues==

			Nearly finished with core install script. Need to solve for CLT install and sudo brew - if they are in fact linked.
⚫	7/30 Testing status: V 1.0


		⚫	==7/30 Testing status: V 1.0==

	Testing against 10.11.6 bare system.		Testing against 10.11.6 bare system.
Line 23:		Line 26:
	Second pass - correcting log out signal at xQuartz install complete		Second pass - correcting log out signal at xQuartz install complete

	Third pass - Add time hack to xQuartz install and rerun clean (~~later~~ ~~today~~, ~~perhaps~~ 9 PM or ~~so)~~		Third pass - Add time hack to xQuartz install and rerun clean; nearly flawless. Two points - CLT tools license acceptance which (may?) lead to sudo being necessary to complete brew install. Unanticipated, but doesn't seem to hurt.

			Fourth pass - Modify CLT to do participative install; test to see if that helps the brew situation

	Next steps:		Next steps:
Line 36:		Line 41:


	AS OF 7/30/2016		==AS OF 7/30/2016==

	Ok, let's get this party started. Decisions:		Ok, let's get this party started. Decisions:
Line 51:		Line 56:

	Implemented the following features in a bash script (as of 7/30)		Implemented the following features in a bash script (as of 7/30)
			<pre{{log2}}>

	1) Detect version of OS X (supporting 10.9 through current - or Mavericks through El Capitan)		1) Detect version of OS X (supporting 10.9 through current - or Mavericks through El Capitan)
	2) Detect xQuartz installed - FIXME: Good grief this is messy and requires logout / login and rerunning the script, ugh.		2) Detect xQuartz installed - FIXME: Good grief this is messy and requires logout / login and rerunning the script, ugh.
Line 64:		Line 69:
	11) Detect lich - download / unzip in $HOME if not detected at $HOME. Remove zip file. FIXME: Current version handling, detect at locations other than $HOME		11) Detect lich - download / unzip in $HOME if not detected at $HOME. Remove zip file. FIXME: Current version handling, detect at locations other than $HOME
	12) Detect Avalon - download / unarchive in $HOME/Desktop if not detected at $HOME/Desktop. Remove zip file. FIXME: Current version handling, detect at locations other than $HOME/Desktop.		12) Detect Avalon - download / unarchive in $HOME/Desktop if not detected at $HOME/Desktop. Remove zip file. FIXME: Current version handling, detect at locations other than $HOME/Desktop.
			</pre>


	Testing: Bare bones 10.11.6		Testing: Bare bones 10.11.6

DOUG: /* Current Issues */

2016-07-30T22:59:25Z

Current Issues

← Older revision		Revision as of 17:59, 30 July 2016
Line 32:		Line 32:

	Continue diag script development while staring at little spinning balls and wishing for more / better / faster		Continue diag script development while staring at little spinning balls and wishing for more / better / faster

			Consider better organization in script - functional, but might be easier to maintain if.