links for 2009-03-31
-
Some have been covered before, but a lot of PSD tutorials and sample looks to check out here.
Just a quick note to clue my visitors in on a fantastic little Firefox addon/cross platform app named Service Capture. From the site…
ServiceCapture runs on your computer(pc or mac) and captures all HTTP traffic sent from your browser or IDE. It is designed to help Rich Internet Application(RIA) developers in the debugging, analysis, and testing of their applications.
It is a time saver and a conundrum killer. It’s a verbose little HTTP sniffer, Flash tracer and bandwidth simulator all in one. It thoroughly rocks. One thing that it certainly shows, is just how many people publish SWF content without either removing or turning off trace statements before pushing files to their sites.
Besides Flash Trace statements, it shows XML files, AMF requests, system logs and tons of other stuff. It’s $35 well spent. I’m always looking for little utilities like this to help me out, so if you have some you like to use, let me know, I’ll check ‘em out.
The Iona Group recently launched a multi-screen 1080P installation at The S.N. Shure Inc. headquarters. Shure is the world’s leading manufacturer of microphones. They make great equipment. They have for decades. Their name is synonymous with quality, integrity and audio history. We were contracted by them to create a media experience for their new theater at the headquarters (which happens to be an architectural masterpiece, by the way). Some details on the theater can be found here. Some highlights:
Beyond that, the space has some great aesthetic characteristics… check this out:
So, that all said… What did we do? Our fantastic creative team came up with an amazing idea. 3 52″ touchscreens lined to create a seamless multi-screen presentation. We developed a multi-user synced experience using the Red5 server and Flash Player. Live spectrum analysis. Triggered by motion detection via Flash Camera activity. Decades of historical photos. Narration by the great Bill Curtis. Video Interviews from dozens of employees. All in all, a great project. Amazing.
The space is gorgeous. The software is cool! The content, historic! Take a look at the install…

Pictured from left to right. Jim Ferolo, Creative Director, Jeremy Lebeau Technical Director, Heather Ford, Designer, Jeff Idleman, Account Consultant.
What a cool project to be part of. The creative team was fantastic. The development process was a ton of fun. The industrial design is tight and the client is top notch. So fun!
For example, with fairly high confidence we can tell the difference between a 1 hour task and a 2 hour task, but it is improbable that someone can tell you the difference between a 34 hour task and a 35 hour task. Here in lies the answer, better estimation comes from estimating smaller bits of work.
FTA: The real problem for Dreamweaver and for its users is that the nature of the web is changing dramatically. Dynamically-generated web applications, from Amazon right down to the humble blog, all offer much more ‚Äì in-built commenting, voting, RSS feeds, etc – than the best sites built on static HTML can ever hope to provide. Read it here.
My take… while I don’t use Dreamweaver, and I don’t like WYSIWYG editors in general, I feel the author is so misguided here in his criticism of the well known Adobe web design tool. He compares Dreamweaver to Drupal and Joomla (two market leading open source content management systems), pointing out that most sites of any scale these days rely on application functionality, ie. RSS, content rating, comments, etc.
Now, while these “Web 2.0″ features certainly are important for user engagement, the actual tool you use for creating the design template used in a site powered by a CMS DOESN’T MATTER! Dreamweaver’s use doesn’t prohibit you from using a CMS, and vice versa. I’m not sure what Tom Arah, the original author of the article, does for a living when he isn’t writing half baked articles for PCPro, but I would be very surprised if it were web design. I can imagine him in a client meeting telling a customer that the Web Server they have doesn’t work with Firefox or that JPGs are obsolete because of iPhones or JQuery is a new database language… Ooh I love unrelated hyperbolic comparisons. Too fun… Let’s try some more. Submit a completely ridiculous web design comparison to my comments here. I need a laugh.
Now, that aside, I do have trouble believing that Dreamweaver is as relevant now as it was a handful of years of ago. With tools like Coda and Expresso out in full force, Eclipse/Aptana offering powerful debugging features and dozens of other free and easy to use text editors out there, I have to think that a WYSIWYG editors appeal is much more limited that it was then. With Web Developer toolbars, Firebug,¬† Safari’s developer toolbar and tons of other design aids for your browser, a design view is pretty pontless IMHO. Simply write your markup, edit or tweak your CSS and tab to a browser window and refresh. Web design, in the world of media production and interactive development is about the easiest deliverable you can preview. What I mean here is that there is virtuall no penalty for tweaking and previewing. Not so in video or compositing, any substantial change requires a new render or RAM preview. This is also not the case in RIA development. You may need to compile your runtime (SWF, Silverlight, etc), upload it to your server and make a tweak to the middleware code, too… You get what I am saying, i think. A design time WYSIWYG offers no real benefit. When you consider that Dreamweaver’s WYSIWYG rendering engine is not Gecko, Explorer or Webkit, it becomes clear that WYSIWYG is actually something more like “What You See Is Wishful thinking Ya Goober” – WYSIWtYG!
That said, Dreamweaver’s editor tool isn’t that bad, and when used only a text editor, it’s okay. It is expensive for that purpose alone though, so unless you are using the site management tools (which I don’t care for – it’s FTP is atrocious), or it’s server behaviors (which are pretty limiting and notoriously brittle – not allowing much customization), or it’s AJAX editing (I won’t touch Spry, sorry) then you may just want to move on. So it’s not so much dying, at least not from the perspective mentioned by Tom Arah, it’s just fading into irrelevance due to lack of upkeep.