User:LepreKhaun Resident/Json Pretty Printer - Revision history

Duckie Dickins: Change code layout for better readability

2016-01-03T20:42:43Z

Change code layout for better readability

← Older revision		Revision as of 13:42, 3 January 2016
Line 11:		Line 11:
	It expects a link message with the JSON string as the third parameter. The second parameter is used as a "channel ID" (defaults to 75 as written). If this conflicts with your existing link messaging system, I'd expect you should see how to modify the code to suit yourself.		It expects a link message with the JSON string as the third parameter. The second parameter is used as a "channel ID" (defaults to 75 as written). If this conflicts with your existing link messaging system, I'd expect you should see how to modify the code to suit yourself.

	<div><~~lsl~~>		<div><source lang = "lsl2">
	////////////////////////////////////////////////////		////////////////////////////////////////////////////
	// JsonPrettyChat.lsl		// JsonPrettyChat.lsl
Line 94:		Line 94:
	}		}
	}		}
	</~~lsl~~></div>		</source></div>

	Harness program, showing usage:		Harness program, showing usage:

	<div><~~lsl~~>		<div><source lang = "lsl2">
	default		default
	{		{
Line 134:		Line 134:
	}		}
	}		}
	</~~lsl~~></div>		</source></div>

	Outputs:		Outputs:

LepreKhaun Resident: Nicety rewording.

2013-09-25T03:30:16Z

Nicety rewording.

← Older revision		Revision as of 20:30, 24 September 2013
Line 1:		Line 1:
			['''NOTE:''' Pages within my Name Space are a WIP and constantly changing. As my understanding of the problems I attempt to address and the grasp of the subject matter itself deepens, I regularly review what I have written and update the content as better algorithms occur to me.

			However, for this process of refinement, improvement and tweaking to result in something that might (hopefully!) benefit the community at large, I ask that comments, suggested improvements, corrections of fact or your own personal style preferences be made ONLY on the Discussion Pages within my Name Space. Thank you!]

	== JsonPrettyChat.lsl - a JSON Pretty Printer ==		== JsonPrettyChat.lsl - a JSON Pretty Printer ==

LepreKhaun Resident: Formatting fix.

2013-09-24T23:52:46Z

Formatting fix.

← Older revision		Revision as of 16:52, 24 September 2013
Line 1:		Line 1:
	['''NOTE:''' Since I refrain from rearranging the flamingos in front of your trailer home, you are expected to extend the courtesy and leave comments, suggested improvements, corrections of fact or your own personal preferences ONLY on the Discussion Pages within my Name Space. Thank you!]

	== JsonPrettyChat.lsl - a JSON Pretty Printer ==		== JsonPrettyChat.lsl - a JSON Pretty Printer ==

Line 48:		Line 46:
	while (iter < jLength) {		while (iter < jLength) {
	char = llGetSubString(jsonText, iter, iter++);		char = llGetSubString(jsonText, iter, iter++);
	if (char == "\"" && prevChar != "\\") {		if (char == "\"" && prevChar != "\\") { //"//
	inQuote = !inQuote;		inQuote = !inQuote;
	result += char;		result += char;

LepreKhaun Resident: Minor format correction.

2013-09-24T14:19:08Z

Minor format correction.

← Older revision		Revision as of 07:19, 24 September 2013
Line 9:		Line 9:
	It expects a link message with the JSON string as the third parameter. The second parameter is used as a "channel ID" (defaults to 75 as written). If this conflicts with your existing link messaging system, I'd expect you should see how to modify the code to suit yourself.		It expects a link message with the JSON string as the third parameter. The second parameter is used as a "channel ID" (defaults to 75 as written). If this conflicts with your existing link messaging system, I'd expect you should see how to modify the code to suit yourself.

	<lsl>		<div><lsl>
	////////////////////////////////////////////////////		////////////////////////////////////////////////////
	// JsonPrettyChat.lsl		// JsonPrettyChat.lsl
Line 92:		Line 92:
	}		}
	}		}
	</lsl>		</lsl></div>

	Harness program, showing usage:		Harness program, showing usage:

	<lsl>		<div><lsl>
	default		default
	{		{
Line 132:		Line 132:
	}		}
	}		}
	</lsl>		</lsl></div>

	Outputs:		Outputs:
	<pre>
			<div><pre>
	Object: Hello, LepreKhaun Resident		Object: Hello, LepreKhaun Resident
	Object: Json Pretty Chat V2.0 is waiting for your JSON string		Object: Json Pretty Chat V2.0 is waiting for your JSON string
Line 204:		Line 205:
	Object: }		Object: }
	Object: }		Object: }
	</pre>		</pre></div>

	----		----

	<center>== [[User:LepreKhaun_Resident\|'''More Json Tips, Tricks and Coding Examples''']] ==</center>		<center>== [[User:LepreKhaun_Resident\|'''More Json Tips, Tricks and Coding Examples''']] ==</center>

LepreKhaun Resident: Needed to strike through a paragraph...

2013-09-24T14:14:38Z

Needed to strike through a paragraph...

← Older revision		Revision as of 07:14, 24 September 2013
Line 5:		Line 5:
	This is a stand alone debugging tool for working with JSON text. It acts like all JSON pretty printers and outputs to llOwnerSay(). This is NOT a JSON validator, meaning it may well "pretty print" your string even if your strings within it are mal-formed json constructions (such as having "\s" within it or empty values such as "[,,,]", which breaks strict JSON compliance). But, it will separate your strings out for visual inspection.		This is a stand alone debugging tool for working with JSON text. It acts like all JSON pretty printers and outputs to llOwnerSay(). This is NOT a JSON validator, meaning it may well "pretty print" your string even if your strings within it are mal-formed json constructions (such as having "\s" within it or empty values such as "[,,,]", which breaks strict JSON compliance). But, it will separate your strings out for visual inspection.

	It uses recursion A LOT so will likely crash if you have a very large JSON structure. However, it'll have worked it up to a point where you can determine where it hit the stack heap collision, and you simply need to break parts of the JSON string out to continue deeper into it.		<strike>It uses recursion A LOT so will likely crash if you have a very large JSON structure. However, it'll have worked it up to a point where you can determine where it hit the stack heap collision, and you simply need to break parts of the JSON string out to continue deeper into it.</strike> (No longer true with V2.0!)

	It expects a link message with the JSON string as the third parameter. The second parameter is used as a "channel ID" (defaults to 75 as written). If this conflicts with your existing link messaging system, I'd expect you should see how to modify the code to suit yourself.		It expects a link message with the JSON string as the third parameter. The second parameter is used as a "channel ID" (defaults to 75 as written). If this conflicts with your existing link messaging system, I'd expect you should see how to modify the code to suit yourself.

LepreKhaun Resident: Version 2.0, major rewrite and way mo' bettah. :)

2013-09-24T14:07:27Z

Version 2.0, major rewrite and way mo' bettah. :)

Show changes

LepreKhaun Resident at 00:37, 24 September 2013

2013-09-24T00:37:01Z

← Older revision		Revision as of 17:37, 23 September 2013
Line 1:		Line 1:
			['''NOTE:''' Since I refrain from rearranging the flamingos in front of your trailer home, you are expected to extend the courtesy and leave comments, suggested improvements, corrections of fact or your own personal preferences ONLY on the Discussion Pages within my Name Space. Thank you!]

	== JsonPrettyChat.lsl - a JSON Pretty Printer ==		== JsonPrettyChat.lsl - a JSON Pretty Printer ==

LepreKhaun Resident: added footer

2013-09-01T15:10:20Z

added footer

← Older revision		Revision as of 08:10, 1 September 2013
Line 163:		Line 163:
	Object: }		Object: }
	</pre>		</pre>

			----

			<center>== [[User:LepreKhaun_Resident\|'''More Json Tips, Tricks and Coding Examples''']] ==</center>

LepreKhaun Resident at 05:25, 26 August 2013

2013-08-26T05:25:24Z

← Older revision		Revision as of 22:25, 25 August 2013
Line 1:		Line 1:
	== JsonPrettyChat.lsl - a JSON Pretty Printer ==		== JsonPrettyChat.lsl - a JSON Pretty Printer ==

	This is a stand alone debugging tool for working with JSON ~~objects~~. It acts like all JSON pretty printers and outputs to llOwnerSay(). This is NOT a JSON validator, meaning it may well "pretty print" your string even if your strings within it are mal-formed json constructions (such as having "\s" within it or empty values such as "[,,,]", which breaks strict JSON compliance). But, it will separate your strings out for visual inspection.		This is a stand alone debugging tool for working with JSON text. It acts like all JSON pretty printers and outputs to llOwnerSay(). This is NOT a JSON validator, meaning it may well "pretty print" your string even if your strings within it are mal-formed json constructions (such as having "\s" within it or empty values such as "[,,,]", which breaks strict JSON compliance). But, it will separate your strings out for visual inspection.

	It uses recursion A LOT so will likely crash if you have a very large JSON structure. However, it'll have worked it up to a point where you can determine where it hit the stack heap collision, and you simply need to break parts of the JSON string out to continue deeper into it.		It uses recursion A LOT so will likely crash if you have a very large JSON structure. However, it'll have worked it up to a point where you can determine where it hit the stack heap collision, and you simply need to break parts of the JSON string out to continue deeper into it.

LepreKhaun Resident at 08:53, 18 August 2013

2013-08-18T08:53:41Z

← Older revision		Revision as of 01:53, 18 August 2013
Line 132:		Line 132:
	touch_start(integer total_number)		touch_start(integer total_number)
	{		{
	~~string source~~;		// Used as a "channel ID' for link messages
	source = llList2Json(~~JSON_ARRAY~~, ["x", ~~1, JSON_TRUE]);~~		integer MESSAGE_CHANNEL = 75;
	~~source =~~ llList2Json(~~JSON_OBJECT~~, ["x",~~source~~,"Y",JSON_FALSE]);
	llMessageLinked (LINK_THIS, 75, source, NULL_KEY);		string source = llList2Json(JSON_OBJECT, ["x",llList2Json(JSON_ARRAY, ["x", 1, JSON_TRUE]),"Y",JSON_FALSE]);

			llMessageLinked (LINK_THIS, MESSAGE_CHANNEL, source, NULL_KEY);
	}		}
	}		}