<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for RefreshDelVal</title>
	<link>http://refreshdelval.org</link>
	<description>Web Standards, Accessibility, and Usability Group of the Delaware Valley</description>
	<pubDate>Wed, 23 Jul 2008 19:33:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>Comment on A Dreamweaver Rival: Aptana (open-source!) by bj</title>
		<link>http://refreshdelval.org/web-standards/a-dreamweaver-rival-aptana-open-source#comment-25</link>
		<pubDate>Wed, 21 Mar 2007 14:14:44 +0000</pubDate>
		<guid>http://refreshdelval.org/web-standards/a-dreamweaver-rival-aptana-open-source#comment-25</guid>
					<description>Sorry, Sean, but Aptana is more of a resource hog than Dreamweaver.

I actually ended up using Topstyle, which is featherlight on system resources. I don't like everything about it, but the biggest plus was that I could configure all the keyboard shortcuts in it to what I'm used to. I could also configure the top toolbar to include things I'm used to having there.</description>
		<content:encoded><![CDATA[<p>Sorry, Sean, but Aptana is more of a resource hog than Dreamweaver.</p>
<p>I actually ended up using Topstyle, which is featherlight on system resources. I don&#8217;t like everything about it, but the biggest plus was that I could configure all the keyboard shortcuts in it to what I&#8217;m used to. I could also configure the top toolbar to include things I&#8217;m used to having there.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on A Dreamweaver Rival: Aptana (open-source!) by Sean</title>
		<link>http://refreshdelval.org/web-standards/a-dreamweaver-rival-aptana-open-source#comment-4</link>
		<pubDate>Wed, 24 Jan 2007 19:06:55 +0000</pubDate>
		<guid>http://refreshdelval.org/web-standards/a-dreamweaver-rival-aptana-open-source#comment-4</guid>
					<description>It won't be that tough ;) I'll betcha that if you install Aptana, take a gander at the help file for the shortcut keys and then just use it, you can make the transition in a few days.</description>
		<content:encoded><![CDATA[<p>It won&#8217;t be that tough <img src='http://refreshdelval.org/wp/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  I&#8217;ll betcha that if you install Aptana, take a gander at the help file for the shortcut keys and then just use it, you can make the transition in a few days.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on A Dreamweaver Rival: Aptana (open-source!) by bj</title>
		<link>http://refreshdelval.org/web-standards/a-dreamweaver-rival-aptana-open-source#comment-3</link>
		<pubDate>Wed, 24 Jan 2007 17:16:29 +0000</pubDate>
		<guid>http://refreshdelval.org/web-standards/a-dreamweaver-rival-aptana-open-source#comment-3</guid>
					<description>I've been noticing that DW takes forever to load some of the more massive files I need to open, especially php files. It might be time to take a look at something else, especially since I don't use all those dang bells and whistles (that all produce bloated and nasty code) in DW anyway, and always use it in codeview.

But damn, it will be tough learning new shortcut keys, like ctr/shift/p for paragraph, and ctr/1 for an h1 heading . . . which are second nature since I've been using DW since version 2. Yeah, that long.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been noticing that DW takes forever to load some of the more massive files I need to open, especially php files. It might be time to take a look at something else, especially since I don&#8217;t use all those dang bells and whistles (that all produce bloated and nasty code) in DW anyway, and always use it in codeview.</p>
<p>But damn, it will be tough learning new shortcut keys, like ctr/shift/p for paragraph, and ctr/1 for an h1 heading . . . which are second nature since I&#8217;ve been using DW since version 2. Yeah, that long.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
