Comments for Dynamic Flash

Comment on Base64 encoder/decoder class by 岛屿 » Blog Archive » Base64 encoder/decoder class

岛屿 » Blog Archive » Base64 encoder/decoder class — Sun, 20 Jul 2008 07:43:27 +0000

[...] http://dynamicflash.com/goodies/base64/ « b+樹數據結構 [...]

Comment on Flex 2 required reading by SOG knives

SOG knives — Fri, 18 Jul 2008 03:11:31 +0000

SOG knives…

Interesting ideas… I wonder how the Hollywood media would portray this?…

Comment on I am Singularity by SOG knives

SOG knives — Thu, 17 Jul 2008 20:05:24 +0000

SOG knives…

Interesting ideas… I wonder how the Hollywood media would portray this?…

Comment on The problem with SproutCore by Naseer

Naseer — Thu, 17 Jul 2008 06:20:32 +0000

They key is: what captures the imagination of the main audience right now… And right now, that’s the developers. Apple’s big push is to move further in that since there are new energies being created and spent in the Cocoa programming environment… for the iPhone, feeding back to the desktop, and now moving to the web. SproutCore plugs into that with MVC, bindings, etc. Making it easy for new developers to jump in is a wise move, because today’s adopters are tomorrow’s providers.

[I know this is a business and people dynamics comment in a tech heavy discussion, but I hope you see the point. And full disclosure: I own the stock!!!]

Comment on Base64 encoder/decoder class by import mx.utils.Base64Decoder in Flash CS3 | import Slice.of.Infinity;

import mx.utils.Base64Decoder in Flash CS3 | import Slice.of.Infinity; — Wed, 16 Jul 2008 07:06:50 +0000

[...] is only available to Flex. Luckily with the richness of the web, I found an alternative dynamicflash’s Base 64 Class . However, i still think it’s possible to use Flex library into Flash (AS3) and i found out [...]

Comment on The problem with SproutCore by Andrew

Andrew — Tue, 15 Jul 2008 21:17:15 +0000

@Ben who replied, I’m sorry you missed the point. Apple doesn’t have to worry about users that might enjoy progressive enhancement. Firefox and Safari users upgrade their browsers, and Apple doesn’t care about IE users.

SproutCore is great for Apple. Maybe not for you.

If you’re implemented an equivalent service to MobileMe (or OWA, or Gmail) without Javascript or Flash, you’re a rockstar. The world would love to see it. It’s not the problem Apple wants to solve, but mazel tov.

Comment on The problem with SproutCore by Ben

Ben — Tue, 15 Jul 2008 19:22:21 +0000

@Andrew who commented, I’m sorry you’re an idiot. I’ve successfully implemented a _very_ similar version of what apple has done with me.com using progressive enhancement and best practices to great success. To say its OK to turn away users is just plain old stupid.

Comment on Read and write local files with Flash Player 10 by Ronny Karam

Ronny Karam — Tue, 15 Jul 2008 15:09:43 +0000

Hey,

thanks for the new info. But i think that this will force adobe to increase security on the player. And later on we’ll have anti-virus applications deleting our swf files

Comment on Read and write local files with Flash Player 10 by Alan

Alan — Tue, 15 Jul 2008 15:03:59 +0000

Nice info, thanks

Comment on The problem with SproutCore by Andrew

Andrew — Tue, 15 Jul 2008 14:57:18 +0000

Progressive enhancement doesn’t have much meaning on a web application as complex as MobileMe. It would be wasted dev effort to try to make it sort-of-work without Javascript.

For a publishing site with a few extra features (digg, etc)…sure, progressively enhance away. For a hardcore web app (Outlook Web Access, MobileMe, Gmail)…don’t cripple yourself by trying to cater to the outliers, especially if they represent 5% of your potential audience.

The interesting thing about SproutCore is that it looks and feels a lot like Cocoa / ObjectiveC, and abstracts away a lot of tedious stuff. It isn’t right for everything, but for the right problem set it’s a viable choice. It’s also a little slow with release-version javascript interpreters…but FF and Safari are soon-to-release huge improvements there (Tamarin, Squirrelfish), and the number of users using IE on MobileMe is insignificant and probably worth some active discouragement.

Also: 95% vs 97.4% isn’t that big of a difference. The 5% who disable Javascript or have ancient browsers are just going to have to live without complex web apps. HTML5 (FF and Safari very soon, probably not IE8) will also enable local data storage.

I agree that the assertion that “no one likes to download …” is silly. Flash is established, although the versioning can be tricky sometimes. And as you note, slightly fewer people enable Javascript than have Flash. Those are valid reasons for avoiding Silverlight, of course, outside a controlled user population. But not Flash.

The point about sandboxing is also questionable. Perhaps they meant that Flash *feels* like it’s running in a sandbox, which it does. It doesn’t interact with the DOM, and I think it’s safe to say that doing the whole site or app in Flash has a well-known set of problems.

We know why Apple doesn’t like Flash though — Adobe has been a terrible partner in the Flash world. The OSX plugin is pretty awful. There’s a reason that so few Flash developers work on Macs, and it isn’t because they don’t want to.

I sympathize with Apple’s interest in “seeing other people”, so to speak. The RIA space is very important and contentious…and Apple doesn’t have proprietary tech there, so for them to sign up for more mistreatment from Adobe or Microsoft would be just plain dumb. As a standards geek, I’ll be happy if the answer turns out to be open standards and superior tech in the interpreter.