User:V 0 1 D/Draft:VNotation - Revision history

V 0 1 D: /* Issues with the existing system */

2022-09-07T13:46:47Z

Issues with the existing system

← Older revision		Revision as of 13:46, 7 September 2022
Line 5:		Line 5:
	The existing system has two major flaws that cause a lot of headaches, arguments and tedium:		The existing system has two major flaws that cause a lot of headaches, arguments and tedium:
	# It is inflexible, and does not make good use of formatting or space as it is derived from patches to an old and incomplete system that was not designed to be extended. This makes things difficult to read and understand, with an entire book being required to understand the system in its entirety.		# It is inflexible, and does not make good use of formatting or space as it is derived from patches to an old and incomplete system that was not designed to be extended. This makes things difficult to read and understand, with an entire book being required to understand the system in its entirety.
	# It suffers numerous ambiguities and inconsistencies, such as collisions between modifiers where two different modifiers can be applied separately to a trick and create the same result. Another example is needing to remember which direction is the "Normal" direction of each trick, as it could imply either a clockwise or anticlockwise path depending on the trick. These ambiguities have ~~lead~~ to countless arguments in the past.		# It suffers numerous ambiguities and inconsistencies, such as collisions between modifiers where two different modifiers can be applied separately to a trick and create the same result. Another example is needing to remember which direction is the "Normal" direction of each trick, as it could imply either a clockwise or anticlockwise path depending on the trick. These ambiguities have led to countless arguments in the past.

	==Goals==		==Goals==

V 0 1 D: /* Explicit Blocks */

2022-09-07T12:59:42Z

Explicit Blocks

← Older revision		Revision as of 12:59, 7 September 2022
Line 28:		Line 28:
	An explicit block is a notation block where the actual breakdown of the trick exists in VNS already. For example here is the block of a Twisted Sonic		An explicit block is a notation block where the actual breakdown of the trick exists in VNS already. For example here is the block of a Twisted Sonic
	#Our actual combo		#Our actual combo
	TO: Twisted Sonic(34, 23) - Twisted Sonic (23, 12)		TO: Twisted Sonic(34, 23) - Twisted Sonic(23, 12)

	#Twisted Sonic block referenced		#Twisted Sonic block referenced

V 0 1 D: /* Explicit Blocks */

2022-09-07T12:56:39Z

Explicit Blocks

← Older revision		Revision as of 12:56, 7 September 2022
Line 31:		Line 31:

	#Twisted Sonic block referenced		#Twisted Sonic block referenced
	Twisted Sonic = (_SL1, _SL2)[		Twisted Sonic = (_SL1, _SL2)[
	TO: Charge(.5) - Pass.DIR - Charge(.5)		TO: Charge(.5) - Pass.DIR - Charge(.5)
	SL: _SL1 - _SL2		SL: _SL1 - _SL2

V 0 1 D: /* Blocks */

2021-03-01T13:16:34Z

Blocks

← Older revision		Revision as of 13:16, 1 March 2021
Line 31:		Line 31:

	#Twisted Sonic block referenced		#Twisted Sonic block referenced
	Twisted Sonic = (_SL1, _SL2)[		Twisted Sonic = (_SL1, _SL2)[
	TO: Charge(.5) - Pass.DIR - Charge(.5)		TO: Charge(.5) - Pass.DIR - Charge(.5)
	SL: _SL1 - _SL2		SL: _SL1 - _SL2
	CH: CHG		CH: CHG
	].{DIR, CHG(CW)}		].{DIR, CHG(CW)}

Line 43:		Line 43:

	Hai Tua = (_SL1, _CNT)[		Hai Tua = (_SL1, _CNT)[
	#IMPLIED		#IMPLIED
	].{}		].{}

V 0 1 D at 13:15, 1 March 2021

2021-03-01T13:15:57Z

← Older revision		Revision as of 13:15, 1 March 2021
Line 1:		Line 1:
	'''V 0 1 D's Notation System''', also called '''VNotation''' or '''VNS''' is an experimental alternative to the standard notation system being created by V 0 1 D.		'''V 0 1 D's Notation System''', also called '''VNotation''' or '''VNS''' is an experimental alternative to the standard notation system being created by V 0 1 D.

			This page is an overview of the included features and some demonstrations. It is not a tutorial designed to teach you how to write VNS.
	==Issues with the existing system==		==Issues with the existing system==
	The existing system has two major flaws that cause a lot of headaches, arguments and tedium:		The existing system has two major flaws that cause a lot of headaches, arguments and tedium:
Line 34:		Line 36:
	CH: CHG		CH: CHG
	].{DIR, CHG(CW)}		].{DIR, CHG(CW)}

			===Implied Blocks===
			More usefully, an implied block refers to a block that is referenced but not formally notated. This allows the easy conversion of existing notation into VNS with the ability to expand on the detail by writing explicit blocks later. An implicit block can be formally referred to by specifying what values it takes in and uses, but not specifying how they are implemented. For instance:

			TO: Hai Tua(T1, 1x)

			Hai Tua = (_SL1, _CNT)[
			#IMPLIED
			].{}

	==Standardized directions==		==Standardized directions==

V 0 1 D at 13:08, 1 March 2021

2021-03-01T13:08:43Z

@@ Line 19: / Line 19: @@
   SL: 23                    - 12                                 - 23
   CH: CW
 ==Standardized directions==
@@ Line 36: / Line 51: @@
 ===Charges===
 Marked by the "CH:" line, charges are considered relative to gravity, as though looking down from the sky to the ground. In traditional notation, Palm up/Palm Side Charge Normal is a "CH: CW" charge, while Palm Down Charge Normal is a "CH: CCW" charge. The benefit of writing it this way is that a trick can always be assumed to link easily without a counter or otherwise into another trick unless a change in charge is written.
 ===Converting to VNS===
 VNS accepts implied blocks, blocks that have not been explicitly defined in the current notation or at all. This can be used to put traditional notation from a variety of sources into place with minimal transformation effort, allowing for a combination of multiple notation systems and VNS. These blocks can later be filled in or linked to a block that has a definition for a standardized VNS block.

V 0 1 D at 12:57, 1 March 2021

2021-03-01T12:57:21Z

← Older revision		Revision as of 12:57, 1 March 2021
Line 14:		Line 14:

	===Whitespace===		===Whitespace===
	As tracks run parallel to eachother, elements on a track must be lined up through the use of whitespace. Consider the formal VNS notation of what is informally PU Twisted Sonic 23-12 -> PD Inverse Twisted Sonic Reverse 12-23:		As tracks run parallel to eachother, elements on a track must be lined up through the use of whitespace. Consider the formal VNS notation of what is informally PU Twisted Sonic 23-12 -> PD Inverse Twisted Sonic Reverse 12-23:
	~~```~~		HO: PU - PD
	HO: PU - PD		TO: Charge(.5) - Pass.CCW - Charge(.5) - Charge(.5) - Pass.CCW - Charge(.5) - End
	TO: Charge(.5) - Pass.CCW - Charge(.5) - Charge(.5) - Pass.CCW - Charge(.5) - End		SL: 23 - 12 - 23
	SL: 23 - 12 - 23		CH: CW
	CH: CW
	~~```~~

	==Standardized directions==		==Standardized directions==

V 0 1 D: /* Element Tracks */

2021-03-01T12:56:58Z

Element Tracks

← Older revision		Revision as of 12:56, 1 March 2021
Line 11:		Line 11:
	* To provide both a highly detailed variant as well as an informal, lower-detail variant for easy discussion.		* To provide both a highly detailed variant as well as an informal, lower-detail variant for easy discussion.
	==Element Tracks==		==Element Tracks==
			VNS uses individual 'element track' lines running parallel to each-other to notate various occurrences. For instance, a track can be used to notate what orientation the hand is in. Usefully, the state of a track is considered static unless a new value is placed onto the track, removing the need to notate directions or hand positions unless they are changed.

	===Whitespace===		===Whitespace===
			As tracks run parallel to eachother, elements on a track must be lined up through the use of whitespace. Consider the formal VNS notation of what is informally PU Twisted Sonic 23-12 -> PD Inverse Twisted Sonic Reverse 12-23:
			```
			HO: PU - PD
			TO: Charge(.5) - Pass.CCW - Charge(.5) - Charge(.5) - Pass.CCW - Charge(.5) - End
			SL: 23 - 12 - 23
			CH: CW
			```

	==Standardized directions==		==Standardized directions==
	In VNS directions are all standardized between tricks. A trick described as moving in a direction in VNS can link directly into another trick moving in that same direction without a direction change.		In VNS directions are all standardized between tricks. A trick described as moving in a direction in VNS can link directly into another trick moving in that same direction without a direction change.

V 0 1 D at 12:45, 1 March 2021

2021-03-01T12:45:06Z

← Older revision		Revision as of 12:45, 1 March 2021
Line 10:		Line 10:
	* Improve consistency between trick names and trick definitions		* Improve consistency between trick names and trick definitions
	* To provide both a highly detailed variant as well as an informal, lower-detail variant for easy discussion.		* To provide both a highly detailed variant as well as an informal, lower-detail variant for easy discussion.
			==Element Tracks==

			===Whitespace===
	==Standardized directions==		==Standardized directions==
	In VNS directions are all standardized between tricks. A trick described as moving in a direction in VNS can link directly into another trick moving in that same direction without a direction change.		In VNS directions are all standardized between tricks. A trick described as moving in a direction in VNS can link directly into another trick moving in that same direction without a direction change.

V 0 1 D: /* Converting to VNF */

2021-02-11T17:05:09Z

Converting to VNF

← Older revision		Revision as of 17:05, 11 February 2021
Line 30:		Line 30:
	==Blocks==		==Blocks==

	===Converting to ~~VNF~~===		===Converting to VNS===
	~~VNF~~ accepts implied blocks, blocks that have not been explicitly defined in the current notation or at all. This can be used to put traditional notation from a variety of sources into place with minimal transformation effort, allowing for a combination of multiple notation systems and ~~VNF~~. These blocks can later be filled in or linked to a block that has a definition for a standardized ~~VNF~~ block.		VNS accepts implied blocks, blocks that have not been explicitly defined in the current notation or at all. This can be used to put traditional notation from a variety of sources into place with minimal transformation effort, allowing for a combination of multiple notation systems and VNS. These blocks can later be filled in or linked to a block that has a definition for a standardized VNS block.