That was the title of the session I did with Peleus Uhley on Wednesday. It’s always fun to talk about security, especially with such an informed audience. Hopefully it was fun for them, too.
It’s taken longer than I’d hoped but the slides are available here as PDF.
UPDATE 2012/05/28: Updated the link to the PDF, which got busted in blog migration.
The internet is funny. Things get written, then cross-referenced, then indexed by mammoth search engines. Later, when the truth changes, the old postings stay around in various indexes.
So, if you did a search for “Adobe AIR XSLT” via your favorite search engine, you’d be forgiven for thinking that AIR doesn’t yet support client-side XSLT.
But the vast majority of those pages were from August 2007, when AIR was still in Beta. By the time AIR 1.0 launched in 2008, XSLT support was enabled.
So yes: Adobe AIR Supports XSLT!
I’ve only seen one blog post about this truth, by my co-worker Brian Riggs, who works on Adobe Media Player.
Please, read his post, link to it, and link to this one. Together, we can change the search engines!
I’ve gone more in depth into security and injection attacks before. But sometimes, it’s nicer to see everything boiled down into a few slides.
Here, then, are the security slides from my onAIR presentation (PDF). You may see some familiar diagrams…
For more detailed information on how application upgrade really works, check out this trio of posts that Serge Jespers did.
I’m posting this from the beautiful city of Stockholm, Sweden. This week I’ll be traveling with Mike Chambers, Ryan Stewart and the rest of the onAIR crew.
My presentation is an introduction to building security applications in AIR. The first leg of the tour is sold out, and I’m totally excited to be presenting to a full house. If you’re coming to the events in Stockholm, Berlin, or Warsaw, say hi. I want to use this opportunity outside my cube to meet the developers who give meaning to the platform.
I’ve been getting a lot of questions about how to use remote “modules” in AIR. “Modules” is in quotes because it can mean different things. In every case, it refers to running some SWF or HTML/JS content that is loaded at runtime from the network. The difference are in how the content is loaded and how an application can communicate with it.
Depending on the specifics of the modules you want to load there are different options about how to load and communicate with the content. Let’s explore the options!!
Two big announcements on the Adobe + Linux front today. A public alpha of AIR and a new rev of Flex Builder.
For years I’ve been toying with the theory that Linux hasn’t caught on in the consumer desktop space because the apps users expect to run don’t run there. And the apps don’t run there because developers need to learn different styles to develop Linux apps. There’s different distros and packaging requirements, wide variance in window managers, etc, etc.
Sure, the rise of Wine kind of undermines the whole theory. But it adds an extra wrinkle: virtualized apps are cool, but a little bit weird. I’m hooked on virtualized OSes for daily life, but I still feel like they’re not really playing well with others.
Anyway, the ability to develop Linux apps using AIR is a big step. Developers can write these apps on any OS. And just as cool, developers who love what Linux offers for their own work productivity can create AIR apps that run on Mac and Win as well. Same .air file, any OS.
So try out the Linux tools and file some bugs!! It’s the best way to get quality where we all want it to be.
First off, thanks to everyone who came to Brent and my sessions at MAX. We had a great time doing them. It was a blast to meet so many people I’ve only known from email lists and blogs. People seemed really interested and excited in Apollo. Judging from the great questions, a lot of people had put some hard thought into what it’ll take to make Apollo successful.
I’m sure the final slides will get posted somewhere central, but I’d like now to summarize the key points of our presentation.
I’ll leave the detail-heavy blog posts to someone else. Brent and I still have to finish up the demos for our session this afternoon. But I want to get some thoughts down while the impressions are still fresh.
The strongest theme running through the presentations was the integration of separate products to support real workflows. Fancy products like Flash and Photoshop and ColdFusion can be used creatively to do almost anything. That’s great power and freedom. But it doesn’t mean that the most common tasks can be ignored.
I was especially impressed when Sho Kuwamoto demo’d a workflow between Illustrator and Flex Builder. Using well-designed assets in Illustrator, he mapped those to Flash symbols which were used to skin Flex components.
Focus on that kind of developer experience will be huge for the Flex community. By optimizing the common task, designers and developers will be able to make their Flex apps more distinctive. Can’t wait to try that out!