Ted Patrick’s 10 Reasons Convinced Me to go to MAX

Well, that’s not entirely true, but his reasons are pretty good :) . It’s looked like I was going to be heading out to Vegas for a little while now, but it was a bit more finalized this week.

I love MAX, it’s a fantastic conference, and it was only extraordinary circumstances that would have kept me from going. It was bordering on that, but luckily it all worked out.

The most intriguing reason on Ted’s list is actually number 11, the MAXUP. Hopefully we’ll get more info on this soon. MAX is only a few weeks away.

[tags]Adobe, Max 2006, Max2006[/tags]

Looking for Design Work on a Flex 2 Application

One of my readers is working on a Flex 2 application and they are looking for someone to help out with some icons and logo work. As you can see below, it is a smaller application, but I think it is one that you would have a lot of fun doing some work for. If you’re interested, or know someone who might be interested, drop me an email.

I have a small RIA I’ve been developing for personal use with Flex 2 (and ColdFusion on the server). During development I’ve used mostly random icons, or icons that reflect none of the functionality that is behind them. This has worked for my purposes (I know what they mean), but really leaves the application feeling unfinished. I think I’m about ready to start sharing it with other people (friends and family) and would like to finish those rough edges by having some icons created professionally.

I am in need of approximately ten (10) icons and perhaps a logo (around which I already have some ideas). The application has sports/exercise theme.

As this is a personal project, my finances are limited, but I am happy to pay for the work done (or perhaps something off an Amazon wish list). If it helps, I’ve been using some icons from the FamFamFam, Silk collection and like that look and feel. I also like that those icons are delivered as 32-bit PNG files (alpha goodness). This would be my expected delivery format, at 16×16 and 25×25 pixels (maybe others).

It is probable that fulfillment of this request will lead to more work in the future (albeit along the same lines and equally limited in scope). I’ll be happy to iron out the details over email and/or phone as necessary if anybody is interested.

Why the InterAKT Acquisition is a MUCH Bigger Deal than People Seem to Realize

If you haven’t heard (which seems impossible), Adobe acquired InterAKT, a firm that has been a part of the Adobe/Macromedia community for a very long time and has made a name for itself developing extensions for Dreamweaver. In fact, many of the blog posts I read about the acquisition focused on that fact, but after talking with Michael Haynie, I think they’re all missing the big part of this news.

If you read between the lines, for instance the first part of the FAQ, and Matt Chotin’s post, you’ll see Flex mentioned. What do Flex and a company building extensions for Dreamweaver have in common? Absolutely nothing. But take a look at this product: KTML. It is a fantastic online, rich-text, HTML editor. If Flex has one glaring Flaw, it would have to be its handling of text.

The web is still mostly text, and what I hear over and over from people is that Flex is great, but it handles text very poorly. This is because Flash was never really intended for text in the beginning, and the attempts to enhance text support in Flash have fallen somewhat short. That’s not to say it is impossible to create great rich text editing in Flash, I’ve seen some very good examples, but for most people it is out of reach.

Matt’s blog says that “Some of the engineers there (at InterAKT) will begin working on Flex-related projects very soon. We haven’t figured out all of what those are yet, but they’re bound to be exciting!” I hope he’s being coy here, because there is a big need in Flex and a lot of rich text experience over at InterAKT :) .

[tags]Interakt, Adobe, Flex, Rich Text[/tags]

I Promise, I Do Not Hate Ajax

Owen called me out, and rightly so (although Owen, ‘respected’, no way) :) . Between my ZDNet post and my post responding to Rey, I look like a pretty big Ajax hater. And I’ve been accused of a whole lot of fear mongering and incendiary writing. I’m not going to shy away from thought provoking posts, which is what my ZDNet article was intended to do just that. And I think I usually do a good job of sticking to the facts, as Owen says we should. I think there are going to be some serious compatibility issues down the road. A post by JD today made me think even more about that. What can we expect from browsers developed in China or India? Will they follow all the rules? Will Ajax apps run on a browser that 1 billion Chinese use written by a Chinese company? Who knows. With Flash, it’s not an issue.

What I want to stress is that I am all for using the right tool for the right job. I’ve talked about that before. I even put a big stop sign! But my main problem with Ajax is that more and more people are using it to build entire web applications. I think Ajax adds great functionality to the web, and it makes the entire experience better, but if you are trying to replicate the desktop application experience in Ajax, you are going to fall short. You’re going to spend valuable developer time and a lot of energy implementing a solution that will be second rate – especially as multimedia and collaboration become bigger parts of Rich Internet Applications.

I agree wholeheartedly with Owen that a factually, intelligent “debate” over Ajax and Flex is good. However I also think we need to look at EVERY angle, and if we get some heated posts every once in a while, we just need to wade through them.

[tags]Ajax, Flash, Flash Platform, Rich Internet Applications[/tags]

Rey, Rey, Rey, We need to talk

Michael Haynie (pssst…Michael…. your blog looks very dusty) pinged me this link to Rey Bango’s post about Flex vs. Ajax. I may have mentioned before that I used to eschew the Flex vs. Ajax argument. Everyone would say things like “but you can use them both!” and “Flex and Ajax together are a great way to build RIAs.” But now, I say bull. Trying to build web applications with Ajax is a lot like knitting yourself a sweater. It takes a long, long time, ends up costing you much more than it would have to just go buy a new sweater, and it’s going to have a lot of mistakes and “improvising” as you deviate from the pattern. But Ryan, you say, I lovingly crafted that sweater, and the mistakes and creative improvising give it character. I am 100% sure that this is what JavaScript developers tell themselves at night. Replace sweater with JavaScript and it works.

In order to build a web app with Ajax, you have to take into account all of the different browser DOMs, the various workarounds required to make everything look right, and you’re relying on a technology that really hasn’t seen major changes since 1999. Not to mention that once you build a web application, you have to run it inside a browser. Browsers work one place – the desktop. You talk about Flash Flex (I misquoted Rey) only being good being good for structured corporate environments? Try running a 37 signals app on your cell phone – it’s not pretty. Building Flash apps gives you much more exposure.

I just don’t understand why people like Ajax so much. Sure it was neat the first time, it reinvigorated the web and all that, hooray! But why take the time to knit your own sweater when you can just go out and buy one? Emotional attachment? Is everyone afraid to let JavaScript go? It flabbergasted me.