Talk:HorizonVirtual:Terminology Conversion Guide - Revision history

99.67.21.243: /* Development Discussion */

2011-01-03T09:34:14Z

Development Discussion

← Older revision		Revision as of 09:34, 3 January 2011
Line 14:		Line 14:
	Some standard D20 terms I'm looking for ''Virtual'' equivalents for at the moment are:		Some standard D20 terms I'm looking for ''Virtual'' equivalents for at the moment are:
	* Magic (in the sense of the single generic term for rewrites and rewriting).		* Magic (in the sense of the single generic term for rewrites and rewriting).
	Suggestion: "Hax" - suggests an illicit alteration to ongoing system ~~funcitons~~.		Suggestion: "Hax" - suggests an illicit alteration to ongoing system functions.
	* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)		* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)
	Suggestion: "Fluctuating" - suggests that ~~incorperating~~ it (as in eating) may pass a ~~ceratin~~ amount of instability to the consumer.		Suggestion: "Fluctuating" - suggests that incorporating it (as in eating) may pass a certain amount of instability to the consumer.
	--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)

99.67.21.243 at 09:33, 3 January 2011

2011-01-03T09:33:08Z

← Older revision		Revision as of 09:33, 3 January 2011
Line 14:		Line 14:
	Some standard D20 terms I'm looking for ''Virtual'' equivalents for at the moment are:		Some standard D20 terms I'm looking for ''Virtual'' equivalents for at the moment are:
	* Magic (in the sense of the single generic term for rewrites and rewriting).		* Magic (in the sense of the single generic term for rewrites and rewriting).
			Suggestion: "Hax" - suggests an illicit alteration to ongoing system funcitons.
	* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)		* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)
			Suggestion: "Fluctuating" - suggests that incorperating it (as in eating) may pass a ceratin amount of instability to the consumer.
	--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)

IMAGinES at 08:18, 14 August 2005

2005-08-14T08:18:32Z

← Older revision		Revision as of 08:18, 14 August 2005
Line 15:		Line 15:
	* Magic (in the sense of the single generic term for rewrites and rewriting).		* Magic (in the sense of the single generic term for rewrites and rewriting).
	* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)		* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)
	* Cantrip (a basic rewrite)

	--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)

	~~----~~		== Solved Terms ==

	Igtenio ~~and I have been batting some suggestions for a replacement~~ of "~~cantrip~~" ~~back and forth~~. ~~The best we~~'~~ve been able to come up with are~~ "~~Quickie~~" ~~(his idea) and~~ "~~One Liner~~" ~~(mine)~~, ~~both of~~ which ~~have obvious drawbacks. Can anyone else come up with something?~~		Igtenio's brilliant suggestion of replacing "Dispel" with "Undo" hs been incorporated into the conversion guide. He's also suggested "Corrupted" as a replacement for "Undead", which makes sense to me.

	~~--[[User:IMAGinES\|IMAGinES]] 00:53, 21 Jun 2005 (PDT)~~

	~~How about "macro"? It doesn't appear~~ to ~~ber used anywhere else in Program Space, and its computing-based definition, an easily-usable string of code that executes a complex command, seems equivalent with what a D&D cantrip does~~.

	~~--[[User:IMAGinES\|IMAGinES]] 01:00, 14 Aug 2005 (PDT)~~

	~~== Solved Issues ==~~		Also, after Igtenio and I batted some suggestions for a replacement of "cantrip" back and forth, including "Quickie" (his idea) and "One Liner" (mine), both of which had obvious drawbacks, I went with "macro". It doesn't appear to be used anywhere else in Program Space, and its computing-based definition, an easily-usable string of code that executes a complex command, seems equivalent with what a D&D cantrip does.

	Igtenio~~'s brilliant suggestion~~ of ~~replacing~~ "~~Dispel~~" with "~~Undo~~" ~~hs been incorporated into the conversion guide~~. He'~~s also suggested "Corrupted" as~~ a ~~replacement for "Undead"~~, ~~which makes sense to me~~.

	--[[User:IMAGinES\|IMAGinES]] 19:20, ~~18 Jun~~ 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 01:18, 14 Aug 2005 (PDT)

IMAGinES: /* Development Discussion */

2005-08-14T08:03:12Z

Development Discussion

← Older revision		Revision as of 08:03, 14 August 2005
Line 15:		Line 15:
	* Magic (in the sense of the single generic term for rewrites and rewriting).		* Magic (in the sense of the single generic term for rewrites and rewriting).
	* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)		* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)
	* dispelling/dispelled (i.e. negating the effect of an already-executed rewrite). Restoring? Debugging? Something along the lines of correcting code.
	* Cantrip (a basic rewrite)		* Cantrip (a basic rewrite)

	--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)

	~~----~~

	~~Igtenio's brilliant suggestion of replacing "Dispel" with "Undo" hs been incorporated into the conversion guide. He's also suggested "Corrupted" as a replacement for "Undead", which makes sense to me.~~

	~~--[[User:IMAGinES\|IMAGinES]] 19:20, 18 Jun 2005 (PDT)~~

	----		----
Line 35:		Line 28:

	--[[User:IMAGinES\|IMAGinES]] 01:00, 14 Aug 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 01:00, 14 Aug 2005 (PDT)

			== Solved Issues ==

			Igtenio's brilliant suggestion of replacing "Dispel" with "Undo" hs been incorporated into the conversion guide. He's also suggested "Corrupted" as a replacement for "Undead", which makes sense to me.

			--[[User:IMAGinES\|IMAGinES]] 19:20, 18 Jun 2005 (PDT)

IMAGinES: /* Development Discussion */

2005-08-14T08:02:31Z

Development Discussion

← Older revision		Revision as of 08:02, 14 August 2005
Line 14:		Line 14:
	Some standard D20 terms I'm looking for ''Virtual'' equivalents for at the moment are:		Some standard D20 terms I'm looking for ''Virtual'' equivalents for at the moment are:
	* Magic (in the sense of the single generic term for rewrites and rewriting).		* Magic (in the sense of the single generic term for rewrites and rewriting).
	* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater")		* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater". The term should reflect "poisonous" in the sense that a nightshade berry can be poisonous to humans, not because someone added a poison to it, but because poison is formed naturally within the berry as part of its processes.)
	* dispelling/dispelled (i.e. negating the effect of an already-executed rewrite). Restoring? Debugging? Something along the lines of correcting code.		* dispelling/dispelled (i.e. negating the effect of an already-executed rewrite). Restoring? Debugging? Something along the lines of correcting code.
	* Cantrip (a basic rewrite)		* Cantrip (a basic rewrite)

IMAGinES: /* Development Discussion */

2005-08-14T08:00:23Z

Development Discussion

← Older revision		Revision as of 08:00, 14 August 2005
Line 34:		Line 34:
	How about "macro"? It doesn't appear to ber used anywhere else in Program Space, and its computing-based definition, an easily-usable string of code that executes a complex command, seems equivalent with what a D&D cantrip does.		How about "macro"? It doesn't appear to ber used anywhere else in Program Space, and its computing-based definition, an easily-usable string of code that executes a complex command, seems equivalent with what a D&D cantrip does.

	--[[User:~~60.228.72.128~~\|~~60.228.72.128~~]] 00~~:59~~, 14 Aug 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 01:00, 14 Aug 2005 (PDT)

60.228.72.128: /* Development Discussion */

2005-08-14T07:59:50Z

Development Discussion

← Older revision		Revision as of 07:59, 14 August 2005
Line 31:		Line 31:

	--[[User:IMAGinES\|IMAGinES]] 00:53, 21 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 00:53, 21 Jun 2005 (PDT)

			How about "macro"? It doesn't appear to ber used anywhere else in Program Space, and its computing-based definition, an easily-usable string of code that executes a complex command, seems equivalent with what a D&D cantrip does.

			--[[User:60.228.72.128\|60.228.72.128]] 00:59, 14 Aug 2005 (PDT)

IMAGinES: /* Development Discussion */

2005-06-21T07:53:40Z

Development Discussion

← Older revision		Revision as of 07:53, 21 June 2005
Line 19:		Line 19:

	--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)

			----

	Igtenio's brilliant suggestion of replacing "Dispel" with "Undo" hs been incorporated into the conversion guide. He's also suggested "Corrupted" as a replacement for "Undead", which makes sense to me.		Igtenio's brilliant suggestion of replacing "Dispel" with "Undo" hs been incorporated into the conversion guide. He's also suggested "Corrupted" as a replacement for "Undead", which makes sense to me.

	--[[User:IMAGinES\|IMAGinES]] 19:20, 18 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 19:20, 18 Jun 2005 (PDT)

			----

			Igtenio and I have been batting some suggestions for a replacement of "cantrip" back and forth. The best we've been able to come up with are "Quickie" (his idea) and "One Liner" (mine), both of which have obvious drawbacks. Can anyone else come up with something?

			--[[User:IMAGinES\|IMAGinES]] 00:53, 21 Jun 2005 (PDT)

IMAGinES at 02:20, 19 June 2005

2005-06-19T02:20:20Z

← Older revision		Revision as of 02:20, 19 June 2005
Line 19:		Line 19:

	--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)

			Igtenio's brilliant suggestion of replacing "Dispel" with "Undo" hs been incorporated into the conversion guide. He's also suggested "Corrupted" as a replacement for "Undead", which makes sense to me.

			--[[User:IMAGinES\|IMAGinES]] 19:20, 18 Jun 2005 (PDT)

IMAGinES: /* Development Discussion */

2005-06-11T00:23:16Z

Development Discussion

← Older revision		Revision as of 00:23, 11 June 2005
Line 16:		Line 16:
	* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater")		* Poisonous (as in something that is naturally dangerous to programs; term needs to relate back to the ''Virtual'' term for poison, "codeeater")
	* dispelling/dispelled (i.e. negating the effect of an already-executed rewrite). Restoring? Debugging? Something along the lines of correcting code.		* dispelling/dispelled (i.e. negating the effect of an already-executed rewrite). Restoring? Debugging? Something along the lines of correcting code.
			* Cantrip (a basic rewrite)

	--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)		--[[User:IMAGinES\|IMAGinES]] 17:15, 10 Jun 2005 (PDT)