Jigs - Revision history

Zhell at 20:08, 28 April 2023

2023-04-28T20:08:14Z

Zhell at 18:17, 27 March 2023

2023-03-27T18:17:48Z

Zhell at 19:23, 15 December 2022

2022-12-15T19:23:28Z

Zhell at 19:15, 15 December 2022

2022-12-15T19:15:49Z

Zhell at 19:06, 15 December 2022

2022-12-15T19:06:08Z

Zhell at 19:04, 15 December 2022

2022-12-15T19:04:47Z

Zhell at 21:16, 14 December 2022

2022-12-14T21:16:00Z

Zhell at 21:13, 14 December 2022

2022-12-14T21:13:55Z

Zhell at 21:00, 14 December 2022

2022-12-14T21:00:24Z

Zhell at 20:55, 14 December 2022

2022-12-14T20:55:14Z

← Older revision		Revision as of 20:08, 28 April 2023
Line 122:		Line 122:
	Now that you understand the basics of jigs, let's see how to use them with more advanced actions like Interactivity, Destroying, Backing or attaching media at [[Jigs (advanced)\|Jigs (advanced)]]		Now that you understand the basics of jigs, let's see how to use them with more advanced actions like Interactivity, Destroying, Backing or attaching media at [[Jigs (advanced)\|Jigs (advanced)]]

−	[[Category:~~run-doc~~]]	+	[[Category:Documentation]]

← Older revision		Revision as of 18:17, 27 March 2023
Line 121:		Line 121:

	Now that you understand the basics of jigs, let's see how to use them with more advanced actions like Interactivity, Destroying, Backing or attaching media at [[Jigs (advanced)\|Jigs (advanced)]]		Now that you understand the basics of jigs, let's see how to use them with more advanced actions like Interactivity, Destroying, Backing or attaching media at [[Jigs (advanced)\|Jigs (advanced)]]
		+
		+	[[Category:run-doc]]

@@ Line 90: / Line 90: @@
 </syntaxhighlight>
 == Checking Parameters ==
@@ Line 196: / Line 119: @@
 </syntaxhighlight>
-Now that you are an expert on jigs, let's go meta by exploring [[Code|Code]]
+Now that you understand the basics of jigs, let's see how to use them with more advanced actions like Interactivity, Destroying, Backing or attaching media at [[Jigs (advanced)|Jigs (advanced)]]

← Older revision		Revision as of 19:15, 15 December 2022
Line 226:		Line 226:
	new DinoPet()		new DinoPet()
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	Now that you are an expert on jigs, let's go meta by exploring [[Code\|Code]]

@@ Line 175: / Line 175: @@
 You should always check the parameters passed to your methods. If you are expecting a number, make sure it is really a number. If you are expecting a jig, then make sure you have a jig of the right class. This prevents others from mis-using your jigs.
-For your convenience, Run provides the <code>expect</code> sidekick. <code>expect</code> lets you make assertions similar to those you might be familiar with in Jest or Chai. You can to check many things, including if a jig is a certain class, if a number is greater than another number, or if a parameter is of a certain type. To get started, add <code>expect<c/ode> as a dependency to your jig class. Then, check out the [https://run.network/docs/#api-reference-extras-expect expect] documention to find the right assertion.
+For your convenience, Run provides the <code>expect</code> sidekick. <code>expect</code> lets you make assertions similar to those you might be familiar with in Jest or Chai. You can to check many things, including if a jig is a certain class, if a number is greater than another number, or if a parameter is of a certain type. To get started, add <code>expect</code> as a dependency to your jig class. Then, check out the [https://run.network/docs/#api-reference-extras-expect expect] documention to find the right assertion.
 Sometimes you may wish to check if a class is part of a changing set. For example, a game may have a list of item classes that may change over time. This is a little more advanced. See the [https://run.network/docs/#tips-and-tricks-dynamic-whitelists Dynamic Whitelists] section.

@@ Line 172: / Line 172: @@
 == Checking Parameters ==
 You should always check the parameters passed to your methods. If you are expecting a number, make sure it is really a number. If you are expecting a jig, then make sure you have a jig of the right class. This prevents others from mis-using your jigs.
-For your convenience, Run provides the expect sidekick. expect lets you make assertions similar to those you might be familiar with in Jest or Chai. You can to check many things, including if a jig is a certain class, if a number is greater than another number, or if a parameter is of a certain type. To get started, add expect as a dependency to your jig class. Then, check out the expect documention to find the right assertion.
+For your convenience, Run provides the <code>expect</code> sidekick. <code>expect</code> lets you make assertions similar to those you might be familiar with in Jest or Chai. You can to check many things, including if a jig is a certain class, if a number is greater than another number, or if a parameter is of a certain type. To get started, add <code>expect<c/ode> as a dependency to your jig class. Then, check out the [https://run.network/docs/#api-reference-extras-expect expect] documention to find the right assertion.
-Sometimes you may wish to check if a class is part of a changing set. For example, a game may have a list of item classes that may change over time. This is a little more advanced. See the Dynamic Whitelists section.
+Sometimes you may wish to check if a class is part of a changing set. For example, a game may have a list of item classes that may change over time. This is a little more advanced. See the [https://run.network/docs/#tips-and-tricks-dynamic-whitelists Dynamic Whitelists] section.
 === Code ===
@@ Line 199: / Line 197: @@
 == Attaching Media ==
 You may optionally set an icon onto a jig using an emoji, a custom image, or both. These icons will show in explorers, exchanges, and wallets, whenever your jig is displayed. To attach an icon, you set the metadata property on your jig class and then this icon will apply to all instances of that class. You can also set rich media like audio and 3D models too.
-Setting an emoji: To add an emoji, set the emoji field on metadata to a single emoji character. You can find an appropriate emoji on Emojipedia.
+'''Setting an emoji:''' To add an emoji, set the <code>emoji</code> field on <code>metadata</code> to a single emoji character. You can find an appropriate emoji on [https://emojipedia.org/ Emojipedia].
-Setting an image: To set an image, first upload your image on-chain in the B:// protocol format. Easy-B is an excellent tool for this. The image data you uploaded can then be referenced using a string that starts with b:// and includes the transaction ID. Currently Run supports SVG, PNG, and GIF formats. SVG is recommended in most cases because it scales up better on large displays and loads quicker due to its smaller file size.
+'''Setting an image:''' To set an image, first upload your image on-chain in the B:// protocol format. [https://run.network/docs/#tools-easy-b Easy-B] is an excellent tool for this. The image data you uploaded can then be referenced using a string that starts with b:// and includes the transaction ID. Currently Run supports SVG, PNG, and GIF formats. SVG is recommended in most cases because it scales up better on large displays and loads quicker due to its smaller file size.
-Setting audio: To add an audio file, set a b:// protocol uri into the audio field in the metadata object similar to images.
+'''Setting audio:''' To add an audio file, set a <code>b://</code> protocol uri into the <code>audio</code> field in the <code>metadata</code> object similar to images.
-Setting a 3d model: To add a 3d model, set a b:// protocol URI to the glbModel field in the metadata object similar to images.
+'''Setting a 3d model''': To add a 3d model, set a <code>b://</code> protocol URI to the <code>glbModel</code> field in the <code>metadata</code> object similar to images.
-For more information, see the section on Standard Metadata.
+For more information, see the section on [https://run.network/docs/#advanced-usage-standard-metadata Standard Metadata.]
 <pre>

@@ Line 52: / Line 52: @@
 == Syncing ==
 === Code ===
@@ Line 79: / Line 91: @@
 == Interactivity ==
 === Code ===
@@ Line 95: / Line 113: @@
 == Destroying ==
 === Code ===
@@ Line 120: / Line 144: @@
 == Backing ==
 === Code ===

@@ Line 2: / Line 2: @@
 == Creating ==
 === Code ===
 <syntaxhighlight lang="javascript">
-TODO
+class Post extends Jig {
 </syntaxhighlight>
@@ Line 16: / Line 24: @@
 <syntaxhighlight lang="javascript">
-TODO
+class EditablePost extends Post {
 </syntaxhighlight>
@@ Line 26: / Line 42: @@
 <syntaxhighlight lang="javascript">
-TODO
+class Dragon extends Jig {
 </syntaxhighlight>
@@ Line 32: / Line 54: @@
 === Code ===
 <syntaxhighlight lang="javascript">
-TODO
+const card2 = await run.load(card.origin)
 </syntaxhighlight>
@@ Line 42: / Line 83: @@
 <syntaxhighlight lang="javascript">
-TODO
+class Event extends Jig {
 </syntaxhighlight>
@@ Line 48: / Line 97: @@
 === Code ===
 <syntaxhighlight lang="javascript">
-TODO
+giftCard.destroy()
 </syntaxhighlight>
@@ Line 58: / Line 124: @@
 <syntaxhighlight lang="javascript">
-TODO
+class Tip extends Jig {
 </syntaxhighlight>
@@ Line 64: / Line 142: @@
 === Code ===
 <syntaxhighlight lang="javascript">
-TODO
+class Hat extends Jig { }
 </syntaxhighlight>
@@ Line 74: / Line 163: @@
 <syntaxhighlight lang="javascript">
-TODO
+class DinoPet extends Jig { }
-== Updating ==
+DinoPet.metadata = {
-=== Code ===
+new DinoPet()
 </syntaxhighlight>