<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Technique: Storing Arbitrary Objects in HTML Links</title>
	<atom:link href="http://dispatchevent.org/roger/technique-storing-arbitrary-objects-in-html-links/feed/" rel="self" type="application/rss+xml" />
	<link>http://dispatchevent.org/roger/technique-storing-arbitrary-objects-in-html-links/</link>
	<description>Collective thoughts on the Flash Platform, iOS, Unity, and any other technology we use.</description>
	<lastBuildDate>Tue, 24 Jan 2012 12:18:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Roger Braunstein</title>
		<link>http://dispatchevent.org/roger/technique-storing-arbitrary-objects-in-html-links/comment-page-1/#comment-30737</link>
		<dc:creator>Roger Braunstein</dc:creator>
		<pubDate>Wed, 12 Sep 2007 19:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.partlyhuman.com/blog/roger/technique-storing-arbitrary-objects-in-html-links#comment-30737</guid>
		<description>A better solution to storing objects in HTML text (which will run much faster as well) is creating a simple UID hash of the objects you need to reference back to, storing the UID in the event: href, and looking up the original object reference in your hash.

This approach might be more useful in some cases, for example if you wish to forget about the original objects or collect them or re-use their references for other data; then storing a full copy in the HTML will preserve the objects.</description>
		<content:encoded><![CDATA[<p>A better solution to storing objects in HTML text (which will run much faster as well) is creating a simple UID hash of the objects you need to reference back to, storing the UID in the event: href, and looking up the original object reference in your hash.</p>
<p>This approach might be more useful in some cases, for example if you wish to forget about the original objects or collect them or re-use their references for other data; then storing a full copy in the HTML will preserve the objects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Braunstein</title>
		<link>http://dispatchevent.org/roger/technique-storing-arbitrary-objects-in-html-links/comment-page-1/#comment-30736</link>
		<dc:creator>Roger Braunstein</dc:creator>
		<pubDate>Wed, 12 Sep 2007 19:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.partlyhuman.com/blog/roger/technique-storing-arbitrary-objects-in-html-links#comment-30736</guid>
		<description>Art, this would be used only for your code to link objects at runtime. I&#039;ve used this technique to be lazy about building UIs that use one HTML textfield instead of multiple text fields. I agree that this has serious problems for any sort of human-entered data, and I would never use it for that.

And whether it&#039;s too loosely typed or not really depends on what you&#039;re using it for. Usually I&#039;m just storing an ID or a few string keys, and I would never give a class outside the one that created this htmlText navigation element direct access to those untyped Objects. That said, I do agree with you that this is a hack... I just happen to think it&#039;s a cute one. I should have made that more clear.</description>
		<content:encoded><![CDATA[<p>Art, this would be used only for your code to link objects at runtime. I&#8217;ve used this technique to be lazy about building UIs that use one HTML textfield instead of multiple text fields. I agree that this has serious problems for any sort of human-entered data, and I would never use it for that.</p>
<p>And whether it&#8217;s too loosely typed or not really depends on what you&#8217;re using it for. Usually I&#8217;m just storing an ID or a few string keys, and I would never give a class outside the one that created this htmlText navigation element direct access to those untyped Objects. That said, I do agree with you that this is a hack&#8230; I just happen to think it&#8217;s a cute one. I should have made that more clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art Monstro</title>
		<link>http://dispatchevent.org/roger/technique-storing-arbitrary-objects-in-html-links/comment-page-1/#comment-30734</link>
		<dc:creator>Art Monstro</dc:creator>
		<pubDate>Wed, 12 Sep 2007 19:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.partlyhuman.com/blog/roger/technique-storing-arbitrary-objects-in-html-links#comment-30734</guid>
		<description>I question the use of embedding object data in html. Basically you have a loosely formatted string(html) in which you are embedding arbitrary object data. 

Really you would be better off using XML with nodes within your text data. Consider the circumstance of having to allow an end user (or even a CMS) update the data of your links -- there&#039;s no enforcement of standards.

Also, if you&#039;re still doing new Object() and setting properties, youre already screwed. Its too loosely typed.</description>
		<content:encoded><![CDATA[<p>I question the use of embedding object data in html. Basically you have a loosely formatted string(html) in which you are embedding arbitrary object data. </p>
<p>Really you would be better off using XML with nodes within your text data. Consider the circumstance of having to allow an end user (or even a CMS) update the data of your links &#8212; there&#8217;s no enforcement of standards.</p>
<p>Also, if you&#8217;re still doing new Object() and setting properties, youre already screwed. Its too loosely typed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dispatchEvent &#187; Blood, Sweat, Tears, but Mostly Cupcakes</title>
		<link>http://dispatchevent.org/roger/technique-storing-arbitrary-objects-in-html-links/comment-page-1/#comment-29172</link>
		<dc:creator>dispatchEvent &#187; Blood, Sweat, Tears, but Mostly Cupcakes</dc:creator>
		<pubDate>Thu, 06 Sep 2007 06:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.partlyhuman.com/blog/roger/technique-storing-arbitrary-objects-in-html-links#comment-29172</guid>
		<description>[...] site also uses a bit of the dynamic text wrapping and object serialization techniques I posted about [...]</description>
		<content:encoded><![CDATA[<p>[...] site also uses a bit of the dynamic text wrapping and object serialization techniques I posted about [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gabriel montagnÃ©</title>
		<link>http://dispatchevent.org/roger/technique-storing-arbitrary-objects-in-html-links/comment-page-1/#comment-20009</link>
		<dc:creator>gabriel montagnÃ©</dc:creator>
		<pubDate>Thu, 26 Jul 2007 23:38:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.partlyhuman.com/blog/roger/technique-storing-arbitrary-objects-in-html-links#comment-20009</guid>
		<description>this technique is really really cool.

there&#039;s one &quot;silly&quot; shortcoming, not to this technique, but to html links with &#039;event:&#039; in general, pointed here:

&lt;a href=&quot;http://www.blog.lessrain.com/?p=584&quot; rel=&quot;nofollow&quot;&gt;http://www.blog.lessrain.com/?p=584&lt;/a&gt;

you can&#039;t control the context menu for these links, and if you open them not directly but through the &quot;Open&quot; item on the context menu, not only the event will not be dispatched, but the player will pass the broswer the url, which, of course, will not be understood.

How could this be worked around?</description>
		<content:encoded><![CDATA[<p>this technique is really really cool.</p>
<p>there&#8217;s one &#8220;silly&#8221; shortcoming, not to this technique, but to html links with &#8216;event:&#8217; in general, pointed here:</p>
<p><a href="http://www.blog.lessrain.com/?p=584" rel="nofollow">http://www.blog.lessrain.com/?p=584</a></p>
<p>you can&#8217;t control the context menu for these links, and if you open them not directly but through the &#8220;Open&#8221; item on the context menu, not only the event will not be dispatched, but the player will pass the broswer the url, which, of course, will not be understood.</p>
<p>How could this be worked around?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Romeo</title>
		<link>http://dispatchevent.org/roger/technique-storing-arbitrary-objects-in-html-links/comment-page-1/#comment-14271</link>
		<dc:creator>Romeo</dc:creator>
		<pubDate>Wed, 20 Jun 2007 13:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.partlyhuman.com/blog/roger/technique-storing-arbitrary-objects-in-html-links#comment-14271</guid>
		<description>Really nice ... can i use it to build a TagCloud?</description>
		<content:encoded><![CDATA[<p>Really nice &#8230; can i use it to build a TagCloud?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

