You can add an "Advanced Configuration Options" button that will provide this sort of functionality without forcing the user to remember a piece of command syntax.
I look forward to your forthcoming patch with inspired optimism and an open heart.
At the bottom, TFA links to this IEBlog which states:
To maintain compatibility and be secure by default we didn't want to invoke fallback either, as original web authors might not have intended this behavior.
Dear MS:
A fallback, be definition, means that if you can't render the original, fall back to this content. This is exactly what the web author would have wanted. Thank you.
I'm pretty tired of waiting for AIR support on Linux. As previous posters have mentioned, it really shouldn't be that hard. It's webkit + Flash + SQLite, all of which run just fine today.
A few weeks ago I got wind of an email stating that the Linux builds would be available to Adobe Prerelease members. It's not feature complete, and they're basically looking for Linux alpha/beta testers. I was ready to beta test AIR a year ago when the Windows and Mac betas were released.
If Adobe wants to treat linux users as second-class citizens, that's fine. It's really too bad though since we're the ones who are usually keen on cross-platform development, and would likely have been the champions of a truly cross-platform runtime for desktop development.*
Of course, AIR's lack of support for two key features is a dealbreaker for me anyway. That is, launching of shell commands and listening to TCP ports. But I digress.
I've been following AIR since beta 1, and despite my initial excitement, I can tell you that the last few releases have illustrated Adobe's extraordinary dedication to the principle of CYA. To the point of destroying the platform's flexibility.
One way to develop an AIR application is to use HTML/CSS/JavaScript. In beta 1, you could use DOM injection to add new <script> elements pointing to outside sources, and they'd execute within the scope of the application. This made it possible (trivial even) to have an auto-updating codebase, since you could just download the new JS each time the app fires up.
From beta 2 onwards, this was no longer possible. They split up the application playing field into two sandboxes, one which could access the local filesystem, and the other which could access the outside world (as by XMLHttpRequest or script tag injection). The only way to communicate between them is using the Sandbox Bridge. This is less than ideal since there's still no way to run arbitrary code in the privileged sandbox. They shut off eval(), setTimeout(string), setInterval(string) and, as mentioned, script tag injection. It's not even possible to hide script in the onLoad attribute of a dynamically created <img> tag.
More from the dept of CYA, AIR lacks the ability to execute shell commands or bind listening TCP ports (no P2P applications for you).
So, if you like being restricted in what you can do with a platform, AIR is for you. For me, all these preventative measures and missing features make it unusable as a desktop development platform.
There's a great book called Stealing the Network: How to Own the Box which contains a series of realistic short stories chronicaling a variety of black hat adventures. In one story, the protagonist uses an open printer as a base of operations from which to launch attacks on other boxes in the network. This is especially useful since internal servers may be IP-range limited to prevent direct access from outside machines.
IIRC, the attacker also used it as a gateway to steal and forward packets traveling through the local network hub. Good stuff:)
I'd draw the same analogy with video games. The first console FPS I played was Quake III Arena for PS2 - in that game, the default controls are left-stick=move/turn and shoulder buttons are for strafe. The right stick (if used) is for looking up and down.
When I played Halo for the first time (left-stick=look/turn, right-stick=move/strafe), I was so bad, people couldn't hit me. That is to say, my movements were so unpredictable that I was tough to snipe (fairly easily taken out by melee damage however). After a good deal of practice, I can now effortlessly move about using standard controls, and it "feels" like an extension of regular walking.
Slashdot Mirror
It's times like these I wish I hadn't spent all my mod points on that iPod touch :|
Dear MS:
A fallback, be definition, means that if you can't render the original, fall back to this content. This is exactly what the web author would have wanted. Thank you.
Don't blame me, I voted for Kodos.
What about John-jacob-jingleheimer-schmidt?
Hey now, at least it passes the reference rendering, which is more than I can say for some browsers (*cough* lynx *cough*)
Clearly these kids need to see Office Space.
Obviously what we need is mind encryption - so the words coming out your mouth are already 0AA96BA2278F48CD39281
I'm pretty tired of waiting for AIR support on Linux. As previous posters have mentioned, it really shouldn't be that hard. It's webkit + Flash + SQLite, all of which run just fine today.
A few weeks ago I got wind of an email stating that the Linux builds would be available to Adobe Prerelease members. It's not feature complete, and they're basically looking for Linux alpha/beta testers. I was ready to beta test AIR a year ago when the Windows and Mac betas were released.
If Adobe wants to treat linux users as second-class citizens, that's fine. It's really too bad though since we're the ones who are usually keen on cross-platform development, and would likely have been the champions of a truly cross-platform runtime for desktop development.*
Of course, AIR's lack of support for two key features is a dealbreaker for me anyway. That is, launching of shell commands and listening to TCP ports. But I digress.
* Talking about non-Java here. RCP be damned! :P
DUPE! I read that story weeks ago! Get off Slashdot you troll!
I've been following AIR since beta 1, and despite my initial excitement, I can tell you that the last few releases have illustrated Adobe's extraordinary dedication to the principle of CYA. To the point of destroying the platform's flexibility.
One way to develop an AIR application is to use HTML/CSS/JavaScript. In beta 1, you could use DOM injection to add new <script> elements pointing to outside sources, and they'd execute within the scope of the application. This made it possible (trivial even) to have an auto-updating codebase, since you could just download the new JS each time the app fires up.
From beta 2 onwards, this was no longer possible. They split up the application playing field into two sandboxes, one which could access the local filesystem, and the other which could access the outside world (as by XMLHttpRequest or script tag injection). The only way to communicate between them is using the Sandbox Bridge. This is less than ideal since there's still no way to run arbitrary code in the privileged sandbox. They shut off eval(), setTimeout(string), setInterval(string) and, as mentioned, script tag injection. It's not even possible to hide script in the onLoad attribute of a dynamically created <img> tag.
More from the dept of CYA, AIR lacks the ability to execute shell commands or bind listening TCP ports (no P2P applications for you).
So, if you like being restricted in what you can do with a platform, AIR is for you. For me, all these preventative measures and missing features make it unusable as a desktop development platform.
Pointing out security flaws is never a good idea - especially by way of demonstration. Just look at that kid with the boarding pass generator
The unfortunate truth about vulnerabilities is that those who report them are rarely rewarded, often interrogated, and occasionally imprisoned.
Look buddy, if you're trying to get matches, you have to be specific. You've just described 84% of slashdotters!
* The other 16% being mac fanboys
No no, that's UPS smoke you smell - server smoke is more bacony.
See, what some of you won't realize is that ryder's ID is really 7.
There's a great book called Stealing the Network: How to Own the Box which contains a series of realistic short stories chronicaling a variety of black hat adventures. In one story, the protagonist uses an open printer as a base of operations from which to launch attacks on other boxes in the network. This is especially useful since internal servers may be IP-range limited to prevent direct access from outside machines.
IIRC, the attacker also used it as a gateway to steal and forward packets traveling through the local network hub. Good stuff :)
up down down right right-left up-down!
Don't blame me, I voted for Kodos.
MOD PARENT UP: +1 Foo
I'd draw the same analogy with video games. The first console FPS I played was Quake III Arena for PS2 - in that game, the default controls are left-stick=move/turn and shoulder buttons are for strafe. The right stick (if used) is for looking up and down.
When I played Halo for the first time (left-stick=look/turn, right-stick=move/strafe), I was so bad, people couldn't hit me. That is to say, my movements were so unpredictable that I was tough to snipe (fairly easily taken out by melee damage however). After a good deal of practice, I can now effortlessly move about using standard controls, and it "feels" like an extension of regular walking.