<?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: Top 5 Ways to Develop LSL Scripts for Second Life</title>
	<atom:link href="http://www.benchodroff.com/blog/2007/06/13/top-5-ways-to-develop-lsl-scripts-for-second-life/feed" rel="self" type="application/rss+xml" />
	<link>http://www.benchodroff.com/blog/2007/06/13/top-5-ways-to-develop-lsl-scripts-for-second-life</link>
	<description>lux non veritas</description>
	<pubDate>Tue, 06 Jan 2009 20:34:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nobama</title>
		<link>http://www.benchodroff.com/blog/2007/06/13/top-5-ways-to-develop-lsl-scripts-for-second-life/comment-page-1#comment-5166</link>
		<dc:creator>Nobama</dc:creator>
		<pubDate>Sun, 12 Oct 2008 19:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.benchodroff.com/blog/2007/06/13/top-5-ways-to-develop-lsl-scripts-for-second-life/#comment-5166</guid>
		<description>LSL code is fucking stupid, and half of the time it compiles even when there are errors.

How the hell is anyone able to learn this code, when it doesnt obey the rules of any other language?

Linden Labs can kiss my ass</description>
		<content:encoded><![CDATA[<p>LSL code is fucking stupid, and half of the time it compiles even when there are errors.</p>
<p>How the hell is anyone able to learn this code, when it doesnt obey the rules of any other language?</p>
<p>Linden Labs can kiss my ass</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RobbyRacoon</title>
		<link>http://www.benchodroff.com/blog/2007/06/13/top-5-ways-to-develop-lsl-scripts-for-second-life/comment-page-1#comment-5136</link>
		<dc:creator>RobbyRacoon</dc:creator>
		<pubDate>Wed, 30 Jan 2008 04:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.benchodroff.com/blog/2007/06/13/top-5-ways-to-develop-lsl-scripts-for-second-life/#comment-5136</guid>
		<description>I tried the ByronStar-SL Eclipse plugin, and I'm very impressed.  I love the Outline and code folding, and it seems quite nice.

I won't be using it, however, as it doesn't have two features I've come to absolutely rely on: It doesn't seem to provide any lslint integration, which I use *constantly* when developing LSL scripts in Scite, and it doesn't appear to have any way to set F1 or any other hotkey to look up the selected function on the LSL wiki, which I also am used to being able to do from within Scite.  Both of those are absolutely critical features for me, and the ability to look up code examples, script delay, and other pertinent data on the LSL wiki through a single keystroke is much too convenient to give up.

Scite's not much of a development environment (hell, it's not even much of an editor, what the heck kind of editor has no horizontal scrollbar?), but I do at least get syntax highlighting, code folding, lslint integration, and easy lookups.

When ByronStar-SL includes those two features, I'll switch in a heartbeat.

LSL-Editor looks interesting, but I already use Eclipse and Scite for so many other things that I'll just stick with them until something comes along compelling enough justify having *yet another* IDE on my system (I already have more than 7 I can name off the top of my head).</description>
		<content:encoded><![CDATA[<p>I tried the ByronStar-SL Eclipse plugin, and I&#8217;m very impressed.  I love the Outline and code folding, and it seems quite nice.</p>
<p>I won&#8217;t be using it, however, as it doesn&#8217;t have two features I&#8217;ve come to absolutely rely on: It doesn&#8217;t seem to provide any lslint integration, which I use *constantly* when developing LSL scripts in Scite, and it doesn&#8217;t appear to have any way to set F1 or any other hotkey to look up the selected function on the LSL wiki, which I also am used to being able to do from within Scite.  Both of those are absolutely critical features for me, and the ability to look up code examples, script delay, and other pertinent data on the LSL wiki through a single keystroke is much too convenient to give up.</p>
<p>Scite&#8217;s not much of a development environment (hell, it&#8217;s not even much of an editor, what the heck kind of editor has no horizontal scrollbar?), but I do at least get syntax highlighting, code folding, lslint integration, and easy lookups.</p>
<p>When ByronStar-SL includes those two features, I&#8217;ll switch in a heartbeat.</p>
<p>LSL-Editor looks interesting, but I already use Eclipse and Scite for so many other things that I&#8217;ll just stick with them until something comes along compelling enough justify having *yet another* IDE on my system (I already have more than 7 I can name off the top of my head).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nobody Fugazi</title>
		<link>http://www.benchodroff.com/blog/2007/06/13/top-5-ways-to-develop-lsl-scripts-for-second-life/comment-page-1#comment-2481</link>
		<dc:creator>Nobody Fugazi</dc:creator>
		<pubDate>Wed, 13 Jun 2007 18:29:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.benchodroff.com/blog/2007/06/13/top-5-ways-to-develop-lsl-scripts-for-second-life/#comment-2481</guid>
		<description>I just use the LSL-Editor, which came in *real* handy with the recent asset server issues.</description>
		<content:encoded><![CDATA[<p>I just use the LSL-Editor, which came in *real* handy with the recent asset server issues.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
