Actually, that is not necessarily the case. If you look at our descriptions of Apollo, we try to make it very clear that Apollo is focused at bringing RIAs to the desktop. It is this use case that is driving feature prioritization.
From the FAQ: http://labs.adobe.com/wiki/index.php/Apollo:developerfaq#What_is_Apollo.3F ---- What is Apollo Apollo is the code name for a cross-operating system runtime being developed by Adobe that allows developers to leverage their existing web development skills (Flash, Flex, HTML, JavaScript, Ajax) to build and deploy Rich Internet Applications (RIAs) to the desktop. What type of applications does Apollo target? While a number of more traditional desktop applications can be built and targeted at the Apollo runtime, Apollo is targeted at making it easy to develop and deploy Rich Internet Applications to the desktop. It is this use case, deploying RIAs to the desktop, which is driving the feature set for Apollo 1.0. What types of developers is Apollo targeting? Apollo is targeted at developers who are currently leveraging web technologies, such as Flash, Flex, HTML, JavaScript and Ajax techniques to build and deploy Rich Internet Applications. ---- Now, having said that, being able to launch native executables directly is still being considered. (although including native DLLs / libraries will not be in 1.0). Btw, you will definately be able to launch file handlers for file types. Of course, this is just for 1.0, and we have to make some difficult decisions around features in order to be able to get 1.0 out. We will be doing versions of Apollo after 1.0. Btw, as far as WPF/E, it is a browser based plugin, not a desktop runtime, and thus has all the same security restrictions and other issues with running in the browser. mike chambers [EMAIL PROTECTED] Jerome Clarke a.k.a sinatosk wrote: > > > To be honest... all this talk I've been hearing about Apollo being used > as desktop applications using web technologies... I would kinda expect > that you can launch exe passing parameters ( like CLI style or something > similar ), talk to dynamic libraries like .dll ( Windows ), .so ( Linux > )... kinda surprised it doesn't support any of that yet... yet they call > it desktop applications... it's more like their own browser in my > opinion... I doubt this is how Apollo will be all the way. But if it > does... can't say people will move to it quickly while MDM Zinc is there > being able to do all of that ( regardless Zinc is free or not ) and WPF/E > > I had plans to write applications where I can use SQLite, MySQL, GD2, > run servers using TCP/IP on specific ports and ip addresses, video > codecs like divx, xvid and others... if all I can do is talk to the file > system then I may aswell stick with Flex 2... The only use I can see > that for is for offline storage applications like the ebay application > and Amazon application... Thats what alot of people want to do anyways > but thats not the only thing they want to do... > > but then again I'm assuming quite abit here... I havn't got full info > about Apollo... but what I've been hearing about WPF/E compared to > Apollo... I'm assuming Apollo can't do some of the things I said above > and I'm not interested in WPF/E. As far as I know... only works on > Windows but I still watch it to see what people say about it... I like > to be cross platform > > I use Flex 2 alot for the things I'm doing now. I don't think I will be > using Apollo as much as I thought I predicted as I do with Flex 2 > > On 2/2/07, * Kevin Newman* <[EMAIL PROTECTED]
