<?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: Using ASDoc with JASPA</title>
	<atom:link href="http://timwhitlock.info/blog/2009/03/28/using-asdoc-with-jaspa/feed/" rel="self" type="application/rss+xml" />
	<link>http://timwhitlock.info/blog/2009/03/28/using-asdoc-with-jaspa/</link>
	<description>Tim Whitlock&#039;s personal site and blog</description>
	<lastBuildDate>Fri, 03 Feb 2012 12:28:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Tim</title>
		<link>http://timwhitlock.info/blog/2009/03/28/using-asdoc-with-jaspa/#comment-74</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sun, 18 Apr 2010 15:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://web.2point1.com/2009/03/28/using-asdoc-with-jaspa/#comment-74</guid>
		<description>Hi, yes the spam bots have destroyed my wiki.
This project isn&#039;t in active development any more, but thanks for your interest in it. I may pick it up again one day</description>
		<content:encoded><![CDATA[<p>Hi, yes the spam bots have destroyed my wiki.<br />
This project isn&#8217;t in active development any more, but thanks for your interest in it. I may pick it up again one day</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://timwhitlock.info/blog/2009/03/28/using-asdoc-with-jaspa/#comment-73</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 16 Apr 2010 19:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://web.2point1.com/2009/03/28/using-asdoc-with-jaspa/#comment-73</guid>
		<description>I stumbled upon your website while searching for an ActionScript to Javascript cross-compiler.  I&#039;d like to develop in FlashBuilder and produce javascript analogous to Google GWT.

But what is going on with this page on your website?
http://www.jaspa.org.uk/wiki/JAS_language

It has all sorts of porn tags injected into it.</description>
		<content:encoded><![CDATA[<p>I stumbled upon your website while searching for an ActionScript to Javascript cross-compiler.  I&#8217;d like to develop in FlashBuilder and produce javascript analogous to Google GWT.</p>
<p>But what is going on with this page on your website?<br />
<a href="http://www.jaspa.org.uk/wiki/JAS_language" rel="nofollow">http://www.jaspa.org.uk/wiki/JAS_language</a></p>
<p>It has all sorts of porn tags injected into it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daan</title>
		<link>http://timwhitlock.info/blog/2009/03/28/using-asdoc-with-jaspa/#comment-72</link>
		<dc:creator>Daan</dc:creator>
		<pubDate>Sun, 29 Mar 2009 14:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://web.2point1.com/2009/03/28/using-asdoc-with-jaspa/#comment-72</guid>
		<description>I think it really depends on the final goal of the JAS language. Positioning it as a new language for the web means you can iron out the wrinkles in AS3. Modelling it to AS3 means there is no learning curve for AS3 developers planning to switch &#039;platforms&#039;, and the code is portable; (development) tools designed for AS3 projects can be used for JAS projects (I am indeed thinking about asdoc, but maybe there are more?) With portability I don&#039;t mean from flash to javascript and vice versa by the way. I don&#039;t see the advantage of that.

The question is if people need another deviation of a programming language. On the other hand, why define a language with known shortcomings when now is the perfect time to get rid of those.

I think it might be better to go your own way, and if that requires writing a JAS documentor, so be it.</description>
		<content:encoded><![CDATA[<p>I think it really depends on the final goal of the JAS language. Positioning it as a new language for the web means you can iron out the wrinkles in AS3. Modelling it to AS3 means there is no learning curve for AS3 developers planning to switch &#8216;platforms&#8217;, and the code is portable; (development) tools designed for AS3 projects can be used for JAS projects (I am indeed thinking about asdoc, but maybe there are more?) With portability I don&#8217;t mean from flash to javascript and vice versa by the way. I don&#8217;t see the advantage of that.</p>
<p>The question is if people need another deviation of a programming language. On the other hand, why define a language with known shortcomings when now is the perfect time to get rid of those.</p>
<p>I think it might be better to go your own way, and if that requires writing a JAS documentor, so be it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

