<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>scott fegette &#187; dreamweaver</title>
	<atom:link href="http://bigdark.com/archives/tag/dreamweaver/feed" rel="self" type="application/rss+xml" />
	<link>http://bigdark.com</link>
	<description>split-brained technophile</description>
	<lastBuildDate>Sat, 29 Jan 2011 21:12:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Nitobi Complete UI 2007 and Dreamweaver</title>
		<link>http://bigdark.com/archives/1490</link>
		<comments>http://bigdark.com/archives/1490#comments</comments>
		<pubDate>Thu, 04 Oct 2007 16:08:18 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[dreamweaver]]></category>
		<category><![CDATA[ajax]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1490</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1490">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>One of the coolest bit of news I heard at MAX was that Ajax gurus Nitobi have <a href="http://www.nitobi.com/news/?a=54">released Complete UI 2007</a>, their Ajax UI component library, with full support for Dreamweaver included.  Nitobi&#8217;s long been delivering quality code for hardcore Ajax developers, and now they can be used with drag-and-drop ease by Dreamweaver developers, too.  Awesome stuff from some great guys (Andre Charland, Nitobi&#8217;s co-founder, was recently on the <a href="http://onair.adobe.com/">AIR bus tour as well</a> &#8211; they&#8217;re all over the place lately!).</p>
<p>Check out more details on <a href="http://www.nitobi.com">Nitobi&#8217;s Complete UI 2007</a>, which is easy because they&#8217;ve got a <a href="http://www.nitobi.com/download/">trial version you can play with</a> too.  I think you&#8217;ll be impressed.  This is great stuff- kudos, Nitobi!</p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1490/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dreamweaver &#8220;Next&#8221;- What Won&#8217;t Be In It</title>
		<link>http://bigdark.com/archives/1486</link>
		<comments>http://bigdark.com/archives/1486#comments</comments>
		<pubDate>Tue, 28 Aug 2007 17:26:06 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[dreamweaver]]></category>
		<category><![CDATA[news]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1486</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1486">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Dreamweaver&#8217;s a big application.  Huge, in fact.  And the next release is going to be an equally huge one &#8211; I haven&#8217;t seen the team this excited in years.   But as they consider new features and proposals for downstream releases, it&#8217;s a struggle to both innovate on features and architecture while also testing and maintaining all the legacy features in DW.   So, after a lot of careful consideration and research, the DW team has arrived at a short list of features to be dropped (in releases after CS3) that both a) require a lot of release-to-release effort to maintain, and b) are frankly not being used with much, if any frequency by the DW community.    <a href="http://www.adobe.com/go/kb402489">You can read the details here</a>.</p>
<p>Yes, this list will likely be controversial to some &#8211; particularly if you&#8217;re relying on one or more of these features today.  However, the team decided to publish this list early- to both help you prepare for the changes, evaluate other options and adjust your own workflows.   Most all the deprecated features either have become more code-centric workflows in other dedicated IDEs/environments (JSP, .NET), or had visual user interfaces that enabled DW developers and designers to generate poorly-formed code in the back end (Layout Mode and Timelines, for example) &#8211; something the team takes very seriously.</p>
<p>My personal opinion is that this move will really free up resources to do a LOT in the next few releases of Dreamweaver, and start doing more &#8216;revolutionary&#8217; feature and architectural work as opposed to strictly &#8216;evolutionary&#8217; features and polish.  If any of the features to be removed give you pause, post a note, and it&#8217;s likely we can suggest alternatives for the post-CS3 era to help smooth the transition.</p>
<p>Personally- I hope that when we&#8217;re able to talk more about what&#8217;s being planned for the next version (or two) of Dreamweaver, the tradeoffs made here will be more than justified in your eyes.  But that&#8217;s a subject for a much later date with a lot more details- so keep posted.  <img src='http://bigdark.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1486/feed</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>Eric Meyer&#8217;s CSS Sculptor for Dreamweaver</title>
		<link>http://bigdark.com/archives/1485</link>
		<comments>http://bigdark.com/archives/1485#comments</comments>
		<pubDate>Thu, 23 Aug 2007 18:35:27 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[dreamweaver]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1485</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1485">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>To quote Zeldman: &#8220;<a href="http://www.zeldman.com/2007/08/23/eric-meyers-css-sculptor/">danged if Eric Meyer hasn&#8217;t launched a product</a>&#8220;, and in collaboration with long-time Dreamweaver extensionology specialists <a href="http://www.webassist.com">WebAssist</a>, no less.<br />
Today WebAssist announced their new product &#8220;<a href="http://www.webassist.com/professional/products/productdetails.asp?PID=135&#038;CouponID=ht8nbu&#038;WAAID=302&#038;RID=929&#038;utm_source=CSSS_EricMeyer&#038;utm_medium=Partner&#038;utm_campaign=CSSS_launch">Eric Meyer&#8217;s CSS Sculptor</a>&#8220;, a collaboration with <a href="http://meyerweb.com/">Eric </a>on a very well-concieved Dreamweaver extension that allows you to create drop-dead simple, standards-compliant CSS designs quickly and comprehensively.  Quite a nice collaboration at that, if I do say so myself.</p>
<p>CSS Sculptor is an elegant Dreamweaver extension that helps you quickly build a customized CSS layout, starting with 30 of the most popular variants- elastic, liquid and fixed layouts, 1-3 column configurations, and much more.  The interface doesn&#8217;t just help you choose from a completely &#8216;pre-canned&#8217; design, but gives you a clear starting point to help expose the CSS and attributes required to customize a layout for your specific project and design- helping educate users on CSS best practices as well as expedite their development.  Win/win.</p>
<p>The community is taking notice, too- you can read <a href="http://www.zeldman.com/2007/08/23/eric-meyers-css-sculptor/">Jeffrey Zeldman&#8217;s</a> aforementioned take on CSS Sculptor (<a href="http://www.zeldman.com/2007/08/23/eric-meyers-css-sculptor/#comments">great comment thread, too</a>), articles from <a href="http://www.infoworld.com/article/07/08/23/webassist-meyer_1.html">InfoWorld </a>and <a href="http://www.websitemagazine.com/content/blogs/posts/archive/2007/08/23/CSS_Sculptor.aspx">Website Magazine</a>, and of course <a href="http://meyerweb.com/eric/thoughts/2007/08/23/css-sculptor-released/">Eric&#8217;s own take on CSS Sculptor</a> at his <a href="http://meyerweb.com/">personal weblog</a>.   Don&#8217;t forget <a href="http://digg.com/design/Eric_Meyer_s_CSS_SCULPTOR_This_is_interesting">to digg the news</a>, as well. <img src='http://bigdark.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Great product from two heavyweights in their respective spheres of influence, and yet another reason why Dreamweaver&#8217;s such a rich product to work with- the extensibility/third-party developer community around Dreamweaver just plain rocks!  Awesome job, guys.</p>
<p><em>(Side note: I feel compelled to put a little plug in here for the standards-compliant CSS Layouts that ship with Dreamweaver CS3 for the record &#8211; which are also great sources of education on CSS design/layout best practices &#8211; heavily commented, and coded for Dreamweaver by <a href="http://webstandards.org">The Web Standards Project</a>&#8216;s <a href="http://www.w3conversions.com">Stephanie Sullivan</a>.)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1485/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Configuring Dreamweaver CS3 for AIR Coding</title>
		<link>http://bigdark.com/archives/1484</link>
		<comments>http://bigdark.com/archives/1484#comments</comments>
		<pubDate>Mon, 20 Aug 2007 23:09:58 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[air]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[dreamweaver]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1484</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1484">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re using Dreamweaver CS3 but hesitant to get started with AIR development, I put together a <a href="http://www.adobe.com/devnet/dreamweaver/articles/air_dw_demo.html">very quick one-off screencast</a> showing how to configure DWCS3 for AIR previewing and deployment using the beta AIR Extension for Dreamweaver (<a href="http://labs.adobe.com/wiki/index.php/AIR:Dreamweaver_CS3_Extension">available on Adobe Labs</a>).</p>
<p>This screencast covers installation and general functionality of the extension, and should get you up and running quickly.  From there, it should be a snap to start leveraging your existing XHTML/JS/Spry/CSS skills to write sweet desktop apps using the AIR runtime.<br />
Enjoy!</p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1484/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Source Control and Dreamweaver</title>
		<link>http://bigdark.com/archives/1482</link>
		<comments>http://bigdark.com/archives/1482#comments</comments>
		<pubDate>Mon, 13 Aug 2007 18:58:37 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[community]]></category>
		<category><![CDATA[dreamweaver]]></category>
		<category><![CDATA[code]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1482</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1482">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>
&#8230; do you use them together?  If so (or even if you just use source control regularly with other web design/development tools), please jump in with your thoughts and observations at this post by Lori Hylan-Cho on the Dreamweaver team weblog &#8211; &#8220;<a href="http://blogs.adobe.com/dreamweaver/2007/08/s.html">Source Control: Do You Use It?</a>&#8220;.  Lori&#8217;s trying to gather feedback on how you use version control/source control systems like Subversion, CVS, Perforce (and others) in web-based projects, whether application, site or both.   If you haven&#8217;t used a source control system in the past but are interested in possibly doing so in the future, your comments and suggestions are also welcomed.  So if this interests you even remotely, please hit that link and join the conversation.  Thanks!</p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1482/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Be a Dreamweaver Video Star</title>
		<link>http://bigdark.com/archives/1480</link>
		<comments>http://bigdark.com/archives/1480#comments</comments>
		<pubDate>Sat, 11 Aug 2007 00:49:39 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[community]]></category>
		<category><![CDATA[dreamweaver]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1480</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1480">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>
Wanna get your mug up on the big screen at MAX this year?   Enthusiasm about the CS3 launch has you warm and fuzzy, but anxious and jittery?  Well, we&#8217;ve just the outlet for you hardcores to let off some steam.
</p>
<p>
Between August 24th and 28th Adobe will be shooting on-camera interviews of Adobe software enthusiasts, talking about the software and work they love, for a video to be shown at the MAX conference in Chicago.   If selected, you&#8217;d only be needed for one of those days (individual shoots will range between 1 to 2 hours maximum, FYI).  If you want to be considered for this big-screen appearance you just have to drop a note to &#8216;adobecast@yahoo.com&#8217; providing:
</p>
<ul>
<li>Your occupation</li>
<li>What Adobe products you use</li>
<li>A recent photo or two of yourself</li>
<li>Contact information</li>
</ul>
<p>
If you&#8217;ve got an interesting story to tell &#8211; especially if you&#8217;re using Dreamweaver, of course (as I&#8217;m biased that way) &#8211; drop a note to the production email account and get yourself in the running.  I&#8217;m really looking forward to seeing the final piece, as well as the blooper reels&#8230; <img src='http://bigdark.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1480/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ajaxian: Time to Take Dreamweaver Seriously?</title>
		<link>http://bigdark.com/archives/1474</link>
		<comments>http://bigdark.com/archives/1474#comments</comments>
		<pubDate>Mon, 23 Jul 2007 18:52:32 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[community]]></category>
		<category><![CDATA[dreamweaver]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1474</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1474">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>
<a href="http://ajaxian.com/">Ajaxian&#8217;s</a> Dion Almaer asks an interesting question of the Javascript/Ajax crowd &#8211; <a href="http://ajaxian.com/archives/dreamweaver-for-ajax-should-we-take-it-serious-again">is it time to take Dreamweaver for Ajax seriously again</a>?   I think the question is really a broader one- is it time to take <em>Dreamweaver</em> seriously again &#8211; to which I respond with a booming &#8220;HELLS YES&#8221;.   Particularly in workflow ecosystems where a combined designer/developer workflow is crucial, I might add.
</p>
<p>
The comments in the Ajaxian article&#8217;s thread are interesting- I was pleased to see there&#8217;s certainly a contingent of folks within giving a thumbs-up to recent release(s) of DW, along with the expected &#8216;WYSIWYG editing is for dolts&#8217; responses, the latter of which Dion&#8217;s question may actually be a valid one for.   My answer is simple- I&#8217;m a designer who likes code.  I spend most of my time in DW&#8217;s code view exclusively, and occasionally do quick mockups/proof-of-concept work with the WYSIWYG tools.  DW CS3 is speedy and nimble for me (particularly when compared to the glacial performance of MX 2004 and perhaps DW 8), and I have no problems using it regularly as a code editor &#8211; again, with the occasional drift into the GUI-driven features if I&#8217;m doing quick tests/proofs.
</p>
<p>
Now I can&#8217;t (and won&#8217;t) argue with those who simply prefer completely stripped-down tools like Notepad or TextMate/BBEdit &#8211; I occasionally do as well (have been a BBEdit user longer than a Dreamweaver user), and understand the minimalist approach &#8211; but the extended features of DW (along with it&#8217;s recent updates for code-centric folks) are way too much to discount wholesale just for percieved street cred on my part, or the spectre of old (and now- largely resolved) code trust issues in the visual editing features.
</p>
<p>
Anyway, I&#8217;d be interested in your comments, suggestions and opinions on this, too- as Dreamweaver is a app very near and dear to my own workflow I&#8217;ve also got strong (and yes- potentially biased) opinions upon it myself.   Sound off below, why dontcha?</p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1474/feed</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Adobe Exchange Updated</title>
		<link>http://bigdark.com/archives/1468</link>
		<comments>http://bigdark.com/archives/1468#comments</comments>
		<pubDate>Fri, 18 May 2007 17:01:29 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[community]]></category>
		<category><![CDATA[dreamweaver]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1468</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1468">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The Adobe web team just announced that the <a href="http://www.adobe.com/cfusion/exchange/">Exchange</a> just launched it&#8217;s first significant UI update in 4 years last night &#8211; in many respects a simple reversion from it&#8217;s circa-2003 Flash-based interface to a lean, mean and quick-loading HTML front end.  Functionality and features are mostly the same as before, but now some of the long-standing issues with the venerable Flash UI (lack of scroll wheel support, faster load times, ability to print views, et al) have been addressed, and without requiring you to completely relearn the application.</p>
<p>The Adobe web team&#8217;s <a href="http://www.adobeforums.com/cgi-bin/webx/.3bc3f0a0">David Hatch talks a little more about the update in this forums thread</a>, and notes that this is the first, interim release of several updates the web team will be making to the Exchange app based on extensive user research across the Adobe product communities they&#8217;ve been doing over the past few months.  David&#8217;s also noted some current issues with the updated Exchange UI &#8211; be sure to <a href="http://www.adobeforums.com/cgi-bin/webx/.3bc3f0a0">visit the thread</a> and let the web team know what you think &#8211; and of course report bugs you run into so they can be addressed downstream.</p>
<p>(Note: comments are closed in this post, as discussion is being centralized in <a href="http://www.adobeforums.com/cgi-bin/webx/.3bc3f0a0">David&#8217;s forum thread</a> instead.)</p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1468/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PVII Slide Show Magic</title>
		<link>http://bigdark.com/archives/1463</link>
		<comments>http://bigdark.com/archives/1463#comments</comments>
		<pubDate>Mon, 23 Apr 2007 17:36:40 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[dreamweaver]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1463</guid>
		<description><![CDATA[
 <a href="http://bigdark.com/archives/1463">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The next step in my tour of Dreamweaver extensions takes me to long-time Dreamweaver extensionologists, <a href="http://www.projectseven.com">Project Seven</a>.  Project Seven (PVII) has always had a warm spot in my heart for taking very specific problem scenarios for web developers, and coming up with extremely elegant and deep solutions to address them.</p>
<p>PVII&#8217;s newest commercial extension &#8211; <a href="http://www.projectseven.com/products/galleries/ssm/index.htm">Slide Show Magic</a> &#8211; is a great example of their problem-specific focus, enabling an automated Dreamweaver interface to create rich, interactive image galleries and slide shows.  Sure, you could build out a slideshow&#8217;s markup by hand, and code in the fades and dynamic loads by hand, but where Project Seven always excels is coming up with an elegant, accessible, well-structured and <em>automated</em> solution that covers all the bases eloquently.</p>
<p>Not only is Slide Show Magic accessible and indexable, but it gracefully degrades in older browsers, or when JavaScript is disabled.  The markup generated by Slide Show Magic isn&#8217;t littered with event handlers and extraneous code, and the JavaScript is unobtrusively-written and lean.  Their technical solution is as eloquent as the rich visual front end.</p>
<p>If you find yourself building image galleries or slideshows regularly, I can say that I&#8217;m very impressed with not just the elegant user interface, but the plumbing beneath the hood of Slide Show Magic- it&#8217;s a great automated solution that generates excellent code even the purists can be proud of.</p>
<p>Check out a <a href="http://www.projectseven.com/products/galleries/ssm/media/preview/index.htm">quick screencast of Slide Show Magic</a> at the Project Seven site (which really highlights the Dreamweaver interface and workflow), or better yet- <a href="http://www.projectseven.com/products/galleries/ssm/ssm_03.htm">live demos of the extension in action</a>.  Dreamweaver MX and greater are supported, as well as Fireworks MX or greater for image processing (which is optional).  Dreamweaver CS3 is supported of course (as are the rest of PVII&#8217;s products).  Great extension!</p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1463/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WebAssist&#8217;s eCart 4 Released</title>
		<link>http://bigdark.com/archives/1461</link>
		<comments>http://bigdark.com/archives/1461#comments</comments>
		<pubDate>Wed, 18 Apr 2007 16:13:41 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[dreamweaver]]></category>

		<guid isPermaLink="false">http://www.bigdark.com/archives/1461</guid>
		<description><![CDATA[WebAssist releases a brand-spankin' new upgrade to their eCart product, adding configurable standards-compliant CSS layouts and rich payment processing support to an already powerful and popular commercial Dreamweaver add-on product.  Nice work!
 <a href="http://bigdark.com/archives/1461">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>WebAssist president Eric Ott dropped by the Adobe offices last week to give me a sneak peek of their <a href="http://www.webassist.com/professional/products/productdetails.asp?PID=123&#038;RID=857&#038;WAAID=122&#038;utm_source=123_Press&#038;utm_medium=Press&#038;utm_campaign=123_Press">new eCart 4 release</a>, which begins shipping as of today.  eCart 4 is a significant upgrade to WebAssist&#8217;s popular commerce extension to Dreamweaver (supporting DW MX 2004, 8 and CS3).</p>
<p>Back during Eric&#8217;s tenure as product manager for Dreamweaver, a huge feature request was an integrated shopping cart solution that made commerce enablement a snap, a call taken up quite admirably by the third-party Dreamweaver developer ecosystem.  And from what I can tell, the engineers at WebAssist did a bang-up job of building a very complex but easy-to-use Dreamweaver extension by way of eCart 4 to enable exactly that- rich shopping and commerce functionality in a very user-friendly package.  You can see some examples of third-party eCart implementations at <a href="http://www.webassist.com/professional/products/productdetails.asp?PID=123&#038;RID=857&#038;WAAID=122&#038;utm_source=123_Press&#038;utm_medium=Press&#038;utm_campaign=123_Press#features_1_Control">the eCart showcase</a>.</p>
<p>Sporting freshly redesigned, standards-based CSS layouts (reviewed and approved by CSS guru <a href="http://www.meyerweb.com">Eric Meyer</a>, no less), support for a veritable plethora of back-end payment processing services and frameworks (including all of PayPal&#8217;s options), and a very configurable design and layout engine.</p>
<p>The eCart interface itself has undergone a major face-lift as well, with a clean, fresh new look and very well thought-out workflow.  Although the options for an ecommerce solution can be vast and overwhelming, WebAssist has done a great job of streamlining the configuration process.  Read more about this in the <a href="http://www.webassist.com/professional/products/productdetails.asp?PID=123&#038;RID=857&#038;WAAID=122&#038;utm_source=123_Press&#038;utm_medium=Press&#038;utm_campaign=123_Press#features_1_Control">feature breakdown/tour</a>, of course.</p>
<p>This looks like a fantastic upgrade to eCart- an incredibly valuable extension for Dreamweaver overall.  <a href="http://www.webassist.com/professional/products/productdetails.asp?PID=123&#038;RID=857&#038;WAAID=122&#038;utm_source=123_Press&#038;utm_medium=Press&#038;utm_campaign=123_Press">Check out the eCart 4.0 website</a> for more details, including a very nicely-done product walkthru by Mark Fletcher.  Great job and a powerful new upgrade!</p>
<p>Note: I&#8217;ll be looking at some other new offerings from the Dreamweaver extension community over the next few weeks, so keep posted for more soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://bigdark.com/archives/1461/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.301 seconds -->

