Comments for Ladislav Hajabacs

Comment on Embedding symbols while maintain their classes! by teleskopy astronomiczne

teleskopy astronomiczne — Tue, 29 Dec 2009 13:37:31 +0000

Very nice blog, your article is interesting, i have bookmarked it for future referrence

Comment on Why to (not) use Adobe AIR! An open letter for Adobe. by B

Wed, 07 Oct 2009 02:00:13 +0000

It looks like not only does Adobe listen to it’s customers, but it follows though as well.

Check out the first bullet in the AIR 2 feature list.
http://blogs.adobe.com/air/2009/10/previewing_adobe_air_2_at_adob.html

Comment on Why to (not) use Adobe AIR! An open letter for Adobe. by Tom McQuarrie

Tom McQuarrie — Tue, 21 Jul 2009 08:56:43 +0000

I say kudos to Kevin Hoyt!

Adobe AIR is a completely free tool released by Adobe for the benefit of the developer community. It’s a young and developing technology, in no way guaranteed to be perfect or fully featured.

The sign of a good developer is that they are able to understand the benefits and shortfalls of the technologies available, and to choose the best technology to meet the needs of the task at hand. The complaints I see in this post show me that the majority of you have not done that. You’ve proceeded in development, invested time and resources without doing the necessary homework, and are now in a hole because you’ve hit a point where Adobe AIR doesn’t do what your project needs, and are now taking it out on Adobe.

I say thank you, Adobe, for putting desktop application development within easy reach of us web developers, and to those who would complain about the limitations of the technology, I’d recommend taking responsibility for the choices you’ve made in development, and do better homework next time.

Regards,
Tom McQuarrie | elTomTom.com

Comment on When simple overriding is not possible! by David Wolever

David Wolever — Fri, 10 Jul 2009 14:58:49 +0000

I found this post because I needed to overload a private method… But, alas, the method you talk about here didn’t work for me (I don’t have access to the source code). I finally ended up hacking the byte code, which I’ve written about here: http://blog.codekills.net/archives/56-Overriding-private-methods-in-ActionScript,-the-hard-way.html

Comment on Why to (not) use Adobe AIR! An open letter for Adobe. by Michael Prescott

Michael Prescott — Tue, 13 Jan 2009 21:30:29 +0000

I agree, the ability to launch an external application is much desired, especially since the security model of AIR seems too restrictive. If I can launch an external application I can by-pass these restrictions. My immediate requirements are to be able to load a swf from the local system without the user having to open a file dialog, and the swf does not live in the application or applicationStorage directories, rather it lives in on a file server with a mapped drive. Bottom-line, we need levels of security, and the user installing our AIR apps can choose to allow an application to have unfettered access. I say again, allow user’s to choose. There is nothing out of balance about giving users a choice.

Comment on Why to (not) use Adobe AIR! An open letter for Adobe. by Oliver Goldman

Oliver Goldman — Fri, 09 Jan 2009 19:35:35 +0000

This feature is not absent from AIR due to any security restrictions. On the contrary, we just haven’t gotten to it yet. We can only develop new features so quickly, and since we *do* listen to our customers, we have to pick those from the many, many features that have been requested.

regards,
Oliver Goldman | Adobe AIR Engineering

Comment on Why to (not) use Adobe AIR! An open letter for Adobe. by Matthew Fabb

Matthew Fabb — Thu, 08 Jan 2009 05:31:49 +0000

From way back in June: http://www.flashmagazine.com/news/detail/air_roadmap/#When:11:12:00Z

“AIR 2.0 is up in the “air” and the team is currently doing developer interviews to find out what features to add. We talked to Mike Chambers and asked him what users are requesting and he revealed that among the current requests there’s better debugging support for javascript development, opening applications and USB support.”

That the first reference I could find quickly, but I’ve seen other mentions of AIR 2.0 having the ability to open up applications. Adobe won’t confirm it yet, as the features are still being worked out, but I imagine it’s likely going to happen. As Kevin Hoyt points out above AIR is only at version 1.5 and so there’s still a lot of features that both Adobe and developers would like to add to AIR, but it’s still a very new product and it these things take time. Especially when making sure that AIR works as seamlessly as possible on 3 different OS’s.

Meanwhile, Mike Chambers put together a quick proof of concept on how to use .Net code to launch an application from AIR:
http://www.mikechambers.com/blog/2008/01/17/commandproxy-net-air-integration-proof-of-concept/
It’s a bit of a hack and got a lot of controversy from Microsoft employees who pointed out security flaws opens up. Not a great solution, but it’s a possible way to go until hopefully AIR 2.0 includes the functionality natively.

Comment on Why to (not) use Adobe AIR! An open letter for Adobe. by admin

admin — Wed, 07 Jan 2009 12:06:48 +0000

My reason to wanting to launch an external application is simple speed. There are some areas where speed of the AIR is not enough. But I want some good looking application with nice animations - and develop it quickly. And as I know Flex it’s obvius to choose AIR as a user interface, with the help of some extra tools if needed. The external tool can be already developed as an open source project, what can save me time/money.
Mobile phones are different area, nobody will want run some application that has high requirements on hardware.

for Quentin:
As I (and the customer) wants cross platform application maybe Java would be the only solution later JavaFx maybe.
You say: “AIR is not intended as a replacement to native platform development.” This is exactly what I want to know, because they say something about bringing your web development experience to the desktop.

I need the cross platformness of AIR with more power. FluorineFx helps with windows but I need the other operating systems too.

And to make it clear, I could use different solution (Java) in other projects, but this is exactly what Adobe should care of. How many people/projects will have to choose different tools, because they will not be able to choose AIR. I can live without AIR, I don’t lost money if I use something else, only Adobe can lost in this. (Actually I will need some extra time to get better in other languages, that will cost money for me too.)

Comment on Why to (not) use Adobe AIR! An open letter for Adobe. by Tom Chiverton

Tom Chiverton — Wed, 07 Jan 2009 10:35:19 +0000

I’m sure you have a good reason for wanting to launch an external tool.
But are you going to ship PC, Linux and Mac versions of that external tool ? What about whatever-the-hell-it-is in a TV or mobile phone ?

Comment on Why to (not) use Adobe AIR! An open letter for Adobe. by Quentin

Quentin — Tue, 06 Jan 2009 20:31:28 +0000

If you need full power more than you need “something between a web based application and the desktop”, why are you using AIR in the first place? AIR is not intended as a replacement to native platform development. It IS a web based application mindset ported to the desktop. If you are only releasing for or targeting a specific OS, you are doing your client a great disservice by NOT developing with that OS’s core development tools. If that’s the case, and you are not a .NET, WPF, Carbon, Cocoa, etc. developer, then your client should be getting their work done elsewhere to begin with.