Not sure but I hope your not implying I don't build tiered enterprise apps. I'll assume not. What youve stated is why dll access is important. This was the whole point, separation of the application tiers. Not every app lends it self to be a service oriented architecture. All this depends on the type of application your creating, and the infrastructure your user(s) can support.
Chat, IM, mail, photo retouch (insert a gazillion others), type apps quickly become impossible. I don't think Apollo is meat to target only enterprise level applications. How does your app function in a disconnected fashion? If your app is service based, what is the point of using Apollo as opposed to Flex? Why break out of the browser? A number of people I know are thrilled with the fact that there is no data access in flex, which forces people to at least try to adhere to a proper structure. Youve lost me with the above comment. Layering an application into different tiers is an architectural design decision that implies separation. It has nothing to do with the technology or tools used to build those tiers. Your proper structure implies different tools. What is the benefit of this? I can only see having to train people on multiple tools, maintaining multiple code bases, updates, unit testing problems, performance problems.. the list goes on and on. jason -----Message d'origine----- De : [email protected] [mailto:[EMAIL PROTECTED] la part de Andrey Envoyé : samedi 3 février 2007 16:39 À : [email protected] Objet : Re: [flexcoders] Apollo features Haven't replied too often, but this one struck a chord. In real enterprise-level applications, you are split up into tiers. you have presentation layer (which apollo/flex/flash/etc fits very nicely in), and you have your back-end with business logic and the storage). A number of people I know are thrilled with the fact that there is no data access in flex, which forces people to at least try to adhere to a proper structure. Now, in the situation at hand, you'd use apollo to make your pretty applications which all they do serve as a frontend, and they'd just query your services to get the actual data they're working with. This way, you can have anything you want in the backend, the same dll's and the same business logic which can be written in .net/java/vb or whatever else fancies you. This way the businesses keep their existing investments, and get a much better and more user-friendly (hopefully, if designed so) front-end which runs as a desktop app instead of a browser. ... am I missing anything? On 2/3/07, Jason Hawryluk <[EMAIL PROTECTED]> wrote: So your saying it's better for a company to re create the wheel then to leverage their existing investments. 80%+ of business applications are specific to windows not leveraging that investment is just stupid. So now if I have a client that wants to leverage Apollo I have to let them know their going to need to dump everything they have built as it's not cross platform, and even though they are a windows platform company they really need cross platform. I had never stated just target win dll's, and I had meant a value proposition for business. Do you honestly think that company is going to look at Apollo and say "sweet now I can target the other 5% of the market. Let's dump everything and start over"? I'm totally missing your logic here. jason -----Message d'origine----- De : [email protected] [mailto: [EMAIL PROTECTED] la part de Shannon Hicks Envoyé : vendredi 2 février 2007 18:31 À : [email protected] Objet : Re: [flexcoders] Apollo features The real value of Apollo would be cross-platform applications. I can't run your DLL's on my Mac. If you need DLL's, use VB to build your app, and don't tease me with the false hope of a cross-platform application by building with Apollo and then ruining it with windows-only code. :) Shan Jason Hawryluk wrote: I have to agree here, if we can't extend it with our own dll's then what is the real value proposition for Apollo. I think support for dll's is important (com, managed, other). Allowing us to reuse our existing middle tiers/frameworks, and use Apollo to create engaging user experiences. jason -----Message d'origine----- De : [email protected] [ mailto:[EMAIL PROTECTED] la part de Jerome Clarke a.k.a sinatosk Envoyé : vendredi 2 février 2007 16:54 À : [email protected] Objet : Re: [flexcoders] Apollo features 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]> wrote: Tom Chiverton wrote: > Does anyone or has read somewhere, if Apollo will allow you to launch native > local applications ? > As far as I know, Apollo is using webkit, does this include the ability to run other plugins besides Flash (like Java)? If so, can you use one of those other plugins (java, or perhaps a custom plugin) to access native dlls and such by communicating from Flash to Javascript, then to the other plugin in Javascript? Kevin N.
