<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Alcon 3 Preview</title>
	<atom:link href="http://blog.hexagonstar.com/alcon3-preview/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hexagonstar.com/alcon3-preview/</link>
	<description>turn-based glory and pixel pleasure</description>
	<lastBuildDate>Fri, 03 Feb 2012 14:41:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tomasz Lisiewicz</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-824</link>
		<dc:creator>Tomasz Lisiewicz</dc:creator>
		<pubDate>Wed, 11 Aug 2010 21:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-824</guid>
		<description>Great job! App is awesome!</description>
		<content:encoded><![CDATA[<p>Great job! App is awesome!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Davey</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-823</link>
		<dc:creator>Richard Davey</dc:creator>
		<pubDate>Wed, 27 Aug 2008 08:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-823</guid>
		<description>I think calling it a &quot;Filter&quot; makes the most sense to me (or a &quot;Custom Filter&quot;). Glad you liked the idea though! It was the only thing that made me remove Alcon2 from my last project when it got too big (because it was a nightmare seeing all the trace output I had going on with no means to filter it!)</description>
		<content:encoded><![CDATA[<p>I think calling it a &#8220;Filter&#8221; makes the most sense to me (or a &#8220;Custom Filter&#8221;). Glad you liked the idea though! It was the only thing that made me remove Alcon2 from my last project when it got too big (because it was a nightmare seeing all the trace output I had going on with no means to filter it!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sascha</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-822</link>
		<dc:creator>sascha</dc:creator>
		<pubDate>Wed, 27 Aug 2008 06:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-822</guid>
		<description>Richard, thanks for explanation! That looks much more logical than convoluting strings with custom tags! I&#039;ve added that to the list of future planned features. I&#039;m wondering if we should call it &#039;Categories&#039; or if &#039;Channels&#039; is a better term for that.</description>
		<content:encoded><![CDATA[<p>Richard, thanks for explanation! That looks much more logical than convoluting strings with custom tags! I&#8217;ve added that to the list of future planned features. I&#8217;m wondering if we should call it &#8216;Categories&#8217; or if &#8216;Channels&#8217; is a better term for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JG</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-821</link>
		<dc:creator>JG</dc:creator>
		<pubDate>Mon, 25 Aug 2008 17:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-821</guid>
		<description>beautiful beast</description>
		<content:encoded><![CDATA[<p>beautiful beast</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Davey</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-820</link>
		<dc:creator>Richard Davey</dc:creator>
		<pubDate>Fri, 22 Aug 2008 10:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-820</guid>
		<description>Hi - here is how I imagined it&#039;d work:

Debug.createCategory(1, 0x000000, 0xffff00);

(1 = category ID, 0 = text colour, ffff00 = bg colour)

Then you simply do:

Debug.trace(&quot;your trace string&quot;, 1);

1 being the category (and optional). I had imagined it&#039;d work like this rather than you passing colour values in the trace itself (that would get messy). If you didn&#039;t create a category then it&#039;d ignore that value.

This way Alcon can easily filter incoming trace requests too.</description>
		<content:encoded><![CDATA[<p>Hi &#8211; here is how I imagined it&#8217;d work:</p>
<p>Debug.createCategory(1, 0&#215;000000, 0xffff00);</p>
<p>(1 = category ID, 0 = text colour, ffff00 = bg colour)</p>
<p>Then you simply do:</p>
<p>Debug.trace(&#8220;your trace string&#8221;, 1);</p>
<p>1 being the category (and optional). I had imagined it&#8217;d work like this rather than you passing colour values in the trace itself (that would get messy). If you didn&#8217;t create a category then it&#8217;d ignore that value.</p>
<p>This way Alcon can easily filter incoming trace requests too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sascha</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-819</link>
		<dc:creator>sascha</dc:creator>
		<pubDate>Fri, 22 Aug 2008 03:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-819</guid>
		<description>@aestheticsData (and Richard): Could you give me more detail on how you imagine the requested feature to look and how it should work? I can think of a custom tag to highlight parts of a string that are being color-coded but simply doing this with Debug.trace() means that these tags are always processed by Alcon, even if you want to have the raw output, e.g. ...

Debug.trace(&quot;Some [%0xFF00FF%]Fancy[%0x%] String.&quot;);

@Dimitar: sorry so far no plans are made to make it Open Source again. Maybe at a later time.
There will be no closed or open beta period. But if you find any bugs it&#039;ll be great to submit them.</description>
		<content:encoded><![CDATA[<p>@aestheticsData (and Richard): Could you give me more detail on how you imagine the requested feature to look and how it should work? I can think of a custom tag to highlight parts of a string that are being color-coded but simply doing this with Debug.trace() means that these tags are always processed by Alcon, even if you want to have the raw output, e.g. &#8230;</p>
<p>Debug.trace(&#8220;Some [%0xFF00FF%]Fancy[%0x%] String.&#8221;);</p>
<p>@Dimitar: sorry so far no plans are made to make it Open Source again. Maybe at a later time.<br />
There will be no closed or open beta period. But if you find any bugs it&#8217;ll be great to submit them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dimitar G.</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-818</link>
		<dc:creator>Dimitar G.</dc:creator>
		<pubDate>Thu, 21 Aug 2008 13:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-818</guid>
		<description>Looks good!

Are you going to post the source code whenever it is ready?

And do you need testers?</description>
		<content:encoded><![CDATA[<p>Looks good!</p>
<p>Are you going to post the source code whenever it is ready?</p>
<p>And do you need testers?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aestheticsData</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-817</link>
		<dc:creator>aestheticsData</dc:creator>
		<pubDate>Thu, 21 Aug 2008 11:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-817</guid>
		<description>same request as richard davey : possibility to set color and background color for each different lines.
Alcon si great, i use it every day at work and for my personnal project.
thanks again</description>
		<content:encoded><![CDATA[<p>same request as richard davey : possibility to set color and background color for each different lines.<br />
Alcon si great, i use it every day at work and for my personnal project.<br />
thanks again</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sascha</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-816</link>
		<dc:creator>sascha</dc:creator>
		<pubDate>Thu, 21 Aug 2008 11:18:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-816</guid>
		<description>Hi Richard,
You could use the different filter levels/colors and keywords (which are now configurable in v3) to do what you described in point 1, at least simulating it to some degree. But I see your point about having dedicated definable categories for this. I&#039;ll put that on my back list.
About point 2, I&#039;m not sure if that would be desirable because the output you see in Alcon is basically HTML text and Alcon makes sure to convert any HTML tags that you might have in your output text back so they display as raw HTML tags. This is so that Alcon doesn&#039;t falsify the output result. It might be overkill to add a feature to even detect color-coded parts of an output string. But I will give more thought to this later.
Point 3 sounds definitely useful and I&#039;m going to add that to the App Monitor (if not in v3 then in a soon following update). Thanks for the suggestions!</description>
		<content:encoded><![CDATA[<p>Hi Richard,<br />
You could use the different filter levels/colors and keywords (which are now configurable in v3) to do what you described in point 1, at least simulating it to some degree. But I see your point about having dedicated definable categories for this. I&#8217;ll put that on my back list.<br />
About point 2, I&#8217;m not sure if that would be desirable because the output you see in Alcon is basically HTML text and Alcon makes sure to convert any HTML tags that you might have in your output text back so they display as raw HTML tags. This is so that Alcon doesn&#8217;t falsify the output result. It might be overkill to add a feature to even detect color-coded parts of an output string. But I will give more thought to this later.<br />
Point 3 sounds definitely useful and I&#8217;m going to add that to the App Monitor (if not in v3 then in a soon following update). Thanks for the suggestions!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Davey</title>
		<link>http://blog.hexagonstar.com/alcon3-preview/#comment-815</link>
		<dc:creator>Richard Davey</dc:creator>
		<pubDate>Thu, 21 Aug 2008 10:59:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexagonstar.com/?p=611#comment-815</guid>
		<description>Looking really nice. I used Alcon 2 extensively while debugging my last (very huge) game project, and here are some things that were definitely on my wish list for it:

1) Being able to assign a trace to a section / category (for example traces coming from the main player character could be assigned to section 1, traces coming from the baddies section 2, etc) - and then being able to filter the output to only show specific sections, that would be great.

2) Being able to inject colour values into the output traces (so you can colour the text to highlight important traces, or maybe just set the background colour). I was having to use  the different trace levels (warning, etc) to simulate this!

3) The new graph looks lovely - how about being able to add a marker into it? (so when you call a marker function it just adds a vertical coloured line to the graph). That way you could set a marker for each significant area of your SWF (obviously not something you&#039;d want to do in an enter frame loop, but certainly would be useful after/before large processing events).</description>
		<content:encoded><![CDATA[<p>Looking really nice. I used Alcon 2 extensively while debugging my last (very huge) game project, and here are some things that were definitely on my wish list for it:</p>
<p>1) Being able to assign a trace to a section / category (for example traces coming from the main player character could be assigned to section 1, traces coming from the baddies section 2, etc) &#8211; and then being able to filter the output to only show specific sections, that would be great.</p>
<p>2) Being able to inject colour values into the output traces (so you can colour the text to highlight important traces, or maybe just set the background colour). I was having to use  the different trace levels (warning, etc) to simulate this!</p>
<p>3) The new graph looks lovely &#8211; how about being able to add a marker into it? (so when you call a marker function it just adds a vertical coloured line to the graph). That way you could set a marker for each significant area of your SWF (obviously not something you&#8217;d want to do in an enter frame loop, but certainly would be useful after/before large processing events).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

