<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss'><id>tag:blogger.com,1999:blog-3424907</id><updated>2009-02-21T06:48:25.518-08:00</updated><title type='text'>JD on MX</title><subtitle type='html'>A daily log of news related to Macromedia MX from &lt;a href="http://www.macromedia.com/desdev/jd_forum/jd001.html"&gt;John Dowdell&lt;/a&gt;. This is a personal site, with subjective takes on breaking news... if you want official news, then that's on the Macromedia site itself, thanks.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://jdmx.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default?start-index=26&amp;max-results=25'/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>1138</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-3424907.post-89923085</id><published>2003-02-28T13:48:00.000-08:00</published><updated>2003-02-28T13:49:53.000-08:00</updated><title type='text'></title><content type='html'>&lt;font size=+1&gt;&lt;a href="http://www.macromedia.com/go/blog_jd/"&gt;I'VE MOVED!&lt;/a&gt; Thanks to Josh Dura for design, and Mike Chambers for implementation. &lt;a href="http://markme.com/jd/index.rdf"&gt;RSS&lt;/a&gt; is available, but Haloscan comments did not come across. (That Macromedia "go" address should switch over soon... if it brings you back here to Blogspot, then try http://www.markme.com/jd/  The markme.com addresses will change to macromedia.com addresses in the near future, so the "go" shortcut is the best long-term address.) Thanks for visiting, and I hope you enjoy my new digs!&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89923085?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89923085'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89923085'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89923085' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89861459</id><published>2003-02-27T13:45:00.000-08:00</published><updated>2003-02-27T13:46:26.000-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://radio.weblogs.com/0001011/2003/02/26.html"&gt;Scoble on corporate blogging:&lt;/a&gt; Bob Scoble works for NEC, and he has contacts among the Microsoft bloggers -- he and I first "met" in the Dreamweaver newsgroup. He's got some of the good guidelines here, although it's a post-Cluetrain document... lots of these principles were known before the web or usenet got popular. &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89861459?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89861459'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89861459'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89861459' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89857263</id><published>2003-02-27T12:27:00.000-08:00</published><updated>2003-02-27T12:27:19.483-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.poynter.org/column.asp?id=31&amp;aid=22178"&gt;Downside of site registration:&lt;/a&gt; Steve Poynter points out how the Rhode Island newspaper &lt;a href="http://www.projo.com/"&gt;Providence Journal&lt;/a&gt; had the primary news on the recent loss of life in the nightclub fire, but was inaccessible to the world because many articles were in the site's main publishing system, behind a registration screen. (Their site does offer some of this news to non-subscribers.) It's an unusual situation, but is a strong example of the costs of not being linkable.&lt;br /&gt;[via &lt;a href="http://doc.weblogs.com/2003/02/27#linkLearn"&gt;Doc Searls&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89857263?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89857263'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89857263'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89857263' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89856946</id><published>2003-02-27T12:20:00.000-08:00</published><updated>2003-02-27T12:20:46.123-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.artdirectorsanonymous.com/escalate/"&gt;Art Directors Anonymous:&lt;/a&gt; This is a group-portfolio piece, heavy on a video-like style sense, but it's also a good example of combining multiple pieces into a single interface. Give it some load time.&lt;br /&gt;[via &lt;a href="http://www.zeldman.com/daily/0203c.shtml#flashcity"&gt;Jeffrey Zeldman&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89856946?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89856946'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89856946'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89856946' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89850179</id><published>2003-02-27T10:08:00.000-08:00</published><updated>2003-02-27T10:08:03.840-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.daypop.com/burst/"&gt;Word burst implemented:&lt;/a&gt; Last week there was &lt;a href="http://www.sciam.com/article.cfm?chanID=sa003&amp;articleID=0000AC7A-BBAC-1E52-A98A809EC5880105"&gt;theoretical discussion&lt;/a&gt; about measuring frequency changes of particular words in blogs to reveal hot trends. This week Dan Chan of Daypop has already implemented it. I think this is signficant work, because one of the big tasks businesses have these days is extracting info from data, of pulling signal from noise. This wordburst implementation, like the general &lt;a href="http://www.daypop.com/top/"&gt;Daypop&lt;/a&gt; and &lt;a href="http://blogdex.media.mit.edu/"&gt;Blogdex&lt;/a&gt; link-popularity engines, works on weblogs-as-a-whole... useful because you can scan a range of rated news from &lt;a href="http://www.buzzflash.com/analysis/03/02/26_Ari.html"&gt;left&lt;/a&gt; to &lt;a href="http://www.nationalreview.com/comment/comment-taheri022603.asp"&gt;right&lt;/a&gt; (both links are from today's Top 40). But we also need to implement this on a filtered-source basis, so you can tell discussion trends in a given community or business... both the server and the client have roles to play in this type of work. Still, I'm amazed that Dan pulled off this existence proof so quickly, two thumbs up.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89850179?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89850179'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89850179'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89850179' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89809425</id><published>2003-02-26T17:51:00.000-08:00</published><updated>2003-02-26T17:51:38.513-08:00</updated><title type='text'></title><content type='html'>&lt;b&gt;Blog offline for a bit:&lt;/b&gt; I'll be migrating existing entries to a system on a Macromedia server, so this blog may look wonky for a little bit, but should return to normalcy soon. Best address across changes will be &lt;a href="http://www.macromedia.com/go/blog_jd"&gt;http://www.macromedia.com/go/blog_jd&lt;/a&gt;... this address will always bring you to the current site.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89809425?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89809425'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89809425'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89809425' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89805475</id><published>2003-02-26T16:36:00.000-08:00</published><updated>2003-02-26T16:36:45.810-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.sciencedaily.com/releases/2003/02/030226073614.htm"&gt;Pioneer 10 last contact:&lt;/a&gt; It has been running out of power, and missed its last message... launched 30 years ago, passing through the asteroid belt, investigating Jupiter, it's now 20 years outside Pluto's orbit, half-a-day's travel at the speed of light.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89805475?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89805475'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89805475'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89805475' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89804211</id><published>2003-02-26T16:12:00.000-08:00</published><updated>2003-02-26T16:12:28.610-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.fortune.com/fortune/alsop/0,15704,423026,00.html"&gt;Stewart Alsop on smart mobiles:&lt;/a&gt; There's a new class of phones which can do more than just let you talk: &lt;i&gt;"...the experience of getting the phone was very similar to the experience of getting an Apple II computer with the VisiCalc program in 1981... it let me do something with the first electronic spreadsheet that wasn't possible with pen and paper: It allowed me to rapidly try out different business ideas and test the outcomes. The Motorola T720 and its ilk also inspire me because they promise a new world of usefulness as personal assistants. With these new-generation cellphones, I'll still be able to talk to people, but I can also entertain myself between calls, find help in locating stores and even people when I'm traveling, and get a different kind of information than computers have been delivering to me so far."&lt;/i&gt; The World Wide Web helped people link documents, but there's more to the internet than just the web.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89804211?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89804211'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89804211'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89804211' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89803250</id><published>2003-02-26T15:53:00.000-08:00</published><updated>2003-02-26T15:53:41.153-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://news.com.com/2100-1008-986173.html?tag=fd_top"&gt;Better traffic detection:&lt;/a&gt; This CNET article discusses how someone is post-processing raw sensor information to enable better prediction of upcoming traffic jams. There's that key pattern again of a rapid increase in throughput of realworld sensing devices, and the need for pattern recognition and discrimination on a single dedicated server, which then feeds a single tight stream of useful conclusions to many portable devices.  You wouldn't want all that client software to each pull raw data themselves... the server needs to turn bulky data into useful info, before sending it to each subscriber. Client-side interface and server-side preferences are both key elements in this equation.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89803250?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89803250'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89803250'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89803250' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89800685</id><published>2003-02-26T15:05:00.000-08:00</published><updated>2003-02-26T15:05:22.590-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.blueworld.com/blueworld/news/02.26.03-LS6DWMX.html"&gt;New Lasso Studio for Dreamweaver:&lt;/a&gt; Even if you use ColdFusion, it's good to keep note of options like this, because you can't always control what server, database, application server you use. Knowing how to connect the pieces is key.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89800685?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89800685'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89800685'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89800685' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89800434</id><published>2003-02-26T15:00:00.000-08:00</published><updated>2003-02-26T15:00:45.106-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.bacfug.net/"&gt;In San Francisco? CFUG tomorrow:&lt;/a&gt; The Bay Area ColdFusion UserGroup meets the fourth Thursday of the month. The speaker schedule suddenly changed for this month, but fortunately Christian Cantrell and Mike Chambers are both in town, and will be doing a joint Q&amp;A session. Should be fun... if you're in the area it could well be worth your while. (To find a group in your area for face-to-face contacts, check &lt;a href="http://www.macromedia.com/v1/usergroups/"&gt;here&lt;/a&gt;.)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89800434?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89800434'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89800434'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89800434' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89798996</id><published>2003-02-26T14:35:00.000-08:00</published><updated>2003-02-26T14:35:16.186-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://director-online.com/classified/JobBoard.cfm"&gt;Find a Director developer:&lt;/a&gt; I see lots of people on Flash boards trying to handle projects which get too complex for Flash... they say "I know Director can do this, but I don't know Director". Use the job board at &lt;a href="http://www.director-online.com/"&gt;Director Online&lt;/a&gt;, or the &lt;a href="http://www.macromedia.com/locator/"&gt;Macromedia Developer Locator&lt;/a&gt; to find someone in your area. (Tip: The earlier in the process you contact them, the easier it is to avoid designing yourself into a corner... some projects can be hosted in a new environment as-is, but if you know the destination ahead of time you've usually got a smoother path.)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89798996?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89798996'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89798996'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89798996' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89795163</id><published>2003-02-26T13:22:00.000-08:00</published><updated>2003-02-26T13:27:23.000-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.russellbeattie.com/notebook/20030226.html#113444"&gt;Future drivers for mobile use:&lt;/a&gt; Russell Beattie writes of "Things To Do While You're Waiting"... how the social drivers for pocket devices differ from what we're used to with big computers. He discusses the necessity of offline functionality, the difficulty of locating trustworthy applications, and the difficulty of current business models for development. I came across this while reading his &lt;a href="http://www.russellbeattie.com/notebook/20030224.html#222526"&gt;thoughts on the Flash/DoCoMo announcement&lt;/a&gt;... he's got lots more good stuff about mobile use, about &lt;a href="http://www.russellbeattie.com/notebook/20030224.html#224121"&gt;disposable software&lt;/a&gt;, &lt;a href="http://www.russellbeattie.com/notebook/20030225.html#012619"&gt;phone aggregators&lt;/a&gt;, &lt;a href="http://www.russellbeattie.com/notebook/20030225.html#012619"&gt;news links&lt;/a&gt;, etc.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89795163?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89795163'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89795163'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89795163' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89789642</id><published>2003-02-26T11:35:00.000-08:00</published><updated>2003-02-26T11:35:34.860-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.discreet.com/subscription/extensions.html"&gt;New Max-to-Shockwave export:&lt;/a&gt; People who work in Discreet's 3DS Max can now export directly to Shockwave format. You can set up physics behaviors from Havok and it will translate across... skin, bones and other character features from Max or Character Studio will also come across. This can be instantly seen by &lt;a href="http://www.macromedia.com/software/player_census/shockwaveplayer/version_penetration.html"&gt;half of all consumers tested&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89789642?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89789642'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89789642'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89789642' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89745381</id><published>2003-02-25T17:10:00.000-08:00</published><updated>2003-02-25T17:10:30.780-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.poynter.org/column.asp?id=31&amp;aid=21971"&gt;Poynter on DoCoMo Flash:&lt;/a&gt; Not much meat here, but they already see some of the opportunities for their clients: &lt;i&gt;"News publishers might want to start planning for the arrival of this technology in mobile phones. It means they'll be able to deliver content to phones that's much, much more than a few characters of text."&lt;/i&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89745381?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89745381'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89745381'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89745381' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89743907</id><published>2003-02-25T16:40:00.000-08:00</published><updated>2003-02-25T16:40:44.403-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.bacardidj.com/"&gt;Bacardi DJ SoundStudio:&lt;/a&gt; Okay, I'm blown away. Build and store up to seven tracks of many audio types. Built by &lt;a href="http://www.2advanced.com/flashindex.htm"&gt;2advanced&lt;/a&gt; for Bacardi, who will sponsor a contest on it later this year. Really good piece of work here.&lt;br /&gt;[via &lt;a href="http://www.actionscript.com/archives/00000456.html"&gt;Mat Bastian&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89743907?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89743907'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89743907'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89743907' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89742347</id><published>2003-02-25T16:09:00.000-08:00</published><updated>2003-02-25T16:09:39.966-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.actionscript.com/archives/00000452.html"&gt;Roundup of free Flash components:&lt;/a&gt; Scott Manning at ActionScript.com draws together a number of resources for configurable UI widgets. I know that ColdFusion folks have been particularly interested in these, because they drive down the cost of development. But if you're a high-end Flash coder these are also useful for comparative purposes: examine how they handle interface decisions, inspect or extend the functionality, etc. &lt;br /&gt;&lt;br /&gt;Sometimes people balk at using a readymade component because you're downloading generalized functionality which you may not need for that specific app. Yes, custom code tuned for a particular instance can be smaller than a generic component... it's your choice whether to use generic functionality or custom functionality, assuming you can cover the development costs. But what's really interesting here is that over the last year the Flash community has been developing a grammar of UI componentry -- we've been finding what works, and what works better. At some point you might be able to count on component code already being available clientside, so that just your instructions for configuring the component need to be downloaded....&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89742347?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89742347'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89742347'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89742347' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89740914</id><published>2003-02-25T15:41:00.000-08:00</published><updated>2003-02-25T15:41:41.500-08:00</updated><title type='text'></title><content type='html'>&lt;b&gt;Comments down, moving soon:&lt;/b&gt; Many blogs use HaloScan, and their servers are probably overloaded from other blogs arguing about UN inspections. I'll be moving HTML, RSS and comments to a Macromedia server this week. The best address will be through a redirect at http://www.macromedia.com/go/blog_jd.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89740914?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89740914'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89740914'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89740914' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89740696</id><published>2003-02-25T15:37:00.000-08:00</published><updated>2003-02-25T15:37:45.496-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.economist.com/business/displayStory.cfm?story_id=1596073"&gt;Designer phones:&lt;/a&gt; Wacky Hollywood stars... I'd pick up a disposable from the 7-11 myself. Still, it's signficant how they're using a mobile as a voice-interface service device, rather than just a phone... check out how the concierge changes the experience. For them, a phone is no longer a commodity, but an experience of increased service and status. &lt;a href="http://www.vertu.com/vertu/gallery/tailor.html"&gt;Vertu's site&lt;/a&gt; is interesting for what it attempts, although the frequent screen-refreshes don't quite seem to match the ticket price.&lt;br /&gt;[via &lt;a href="http://boingboing.net/2003_02_01_archive.html#90367204"&gt;Boing Boing&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89740696?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89740696'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89740696'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89740696' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89739339</id><published>2003-02-25T15:10:00.000-08:00</published><updated>2003-02-25T15:10:49.483-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://news.yahoo.com/news?tmpl=story2&amp;ncid=&amp;e=5&amp;u=/nf/20030225/bs_nf/20837"&gt;7 ecommerce failures:&lt;/a&gt; Short checklists are fun to read... maybe you know it all already, but the structure provides new value. "E-Commerce Times" lists these seven classic problems as: (1) not paying enough attention to delivery &amp; fulfillment; (2) offering only online, without catalogues, phone or stores; (3) using outdated technology; (4) having no personality (commodity vs experience); (5) forgetting customer preferences; (6) stale content; (7) not bringing existing customers into the website.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89739339?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89739339'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89739339'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89739339' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89738009</id><published>2003-02-25T14:47:00.000-08:00</published><updated>2003-02-25T14:47:19.466-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.business2.com/articles/web/0,1653,47427,00.html"&gt;Browser wars, round two:&lt;/a&gt; Rafe Needleman discusses connectivity on portable devices. Browsing hypertext documents isn't the only way to use connections between machines.Unlike a full computer, many portables can only receive instruction updates from the device manufacturer. Yet what really drives adoption is wild innovation from unexpected places. The dynamics are different than on desktop machines....&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89738009?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89738009'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89738009'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89738009' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89735496</id><published>2003-02-25T13:58:00.000-08:00</published><updated>2003-02-25T13:58:12.450-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.macromedia.com/support/dreamweaver/ts/documents/ap_faq.htm"&gt;'Answers Panel' misconnects:&lt;/a&gt; Recently some were reporting problems getting updates to the Answers Panel within MX applications... they were seeing timeouts when trying to freshen the list of recent technotes and other resources. With the site revamp we have been moving some servers, and certain connections had increased latency. This should be squared away now. If you have any problems with the Answers Panel yourself, or if you see a conversation online where someone is reporting problems after today, then could you drop a comment here please? Thanks!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89735496?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89735496'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89735496'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89735496' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89735192</id><published>2003-02-25T13:52:00.000-08:00</published><updated>2003-02-25T13:52:36.686-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://news.com.com/2100-1032-985941.html"&gt;Prescriptive specs vs descriptive specs:&lt;/a&gt; This CNET article notes that many W3C sites don't validate to latest specs. I guess this link will rise high on Daypop, but I'm not sure there's much of a real issue here.&lt;br /&gt;&lt;br /&gt;Documents like a W3C Recommendation are prescriptive specifications -- they describe how things should be ideally, how future software should act. Something like the &lt;a href="http://www.macromedia.com/software/flash/open/licensing/fileformat/"&gt;SWF SDK&lt;/a&gt; is more of a descriptive spec -- it describes how something actually does work today. With the latter you're concerned about completeness and accuracy. With the former there are all the arguments inherent in "should" statements, and it can take awhile for the real world to match the platonic ideal set up for it.&lt;br /&gt;&lt;br /&gt;For the tools aspect, the expertise of WASP members &lt;a href="http://www.webstandards.org/act/campaign/"&gt;has been valuable&lt;/a&gt;, and I hope it will continue. But saying the W3C is "leading by fiat, not by example" seems quite harsh -- a prescriptive spec can be a worthy goal, no need to get so judgmental about it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89735192?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89735192'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89735192'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89735192' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89734529</id><published>2003-02-25T13:40:00.000-08:00</published><updated>2003-02-25T13:40:36.700-08:00</updated><title type='text'></title><content type='html'>&lt;a href="http://www.macromedia.com/showcase/submit/"&gt;Seeking financial applications:&lt;/a&gt; The Macromedia Showcase already has a special section for &lt;a href="http://dynamic.macromedia.com/bin/MM/showcase/scripts/showcase_cs_listing_by_query.jsp?industry=Financial"&gt;finance applications&lt;/a&gt;, but there will be an upcoming focus on Rich Internet Applications which use both the client and the server together to do financial work. If you're working on such a project, please drop a note to Showcase folks at the above link -- there's no commitment, and they'd really like to learn of what you're working on. If you've instead visited an existing financial RIA without creating it yourself, then please drop a note in Comments here so I can alert Showcase staff myself. (Hey, I'm also interested in any finances-on-the-web work you've seen, regardless of whether it uses anything Macromedia-ish... I'm also interested in hearing of any financial website you've been impressed with.) Thanks!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89734529?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89734529'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89734529'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89734529' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry><entry><id>tag:blogger.com,1999:blog-3424907.post-89680984</id><published>2003-02-24T17:46:00.000-08:00</published><updated>2003-02-24T17:46:36.060-08:00</updated><title type='text'></title><content type='html'>&lt;a href="javascript:Qr=prompt('Get Lucky at Google:','');if(Qr)location.href='http://www.google.com/search?btnI=a&amp;q='+escape(Qr)"&gt;Get Lucky at Google:&lt;/a&gt; This link here can be saved into your bookmarks or installed on the browser toolbar. When you invoke it you'll get a JavaScript prompt for a search term, and you'll then go directly to the top hit for that term at Google. It works in Mozilla, and I haven't tested the JS for other browsers. (I search Google in my locater bar quite a bit, and got tired of the two-step process in reaching a site.)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3424907-89680984?l=jdmx.blogspot.com'/&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89680984'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3424907/posts/default/89680984'/><link rel='alternate' type='text/html' href='http://jdmx.blogspot.com/2003_02_23_archive.html#89680984' title=''/><author><name>John</name><uri>http://www.blogger.com/profile/07502998658700228829</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14907503776178667931'/></author></entry></feed>