- What is Durango?
- Does Durango work for Adobe Flex applications running in browser?
- What can developers do with Durango?
- What can designers do with Durango?
- What can consumers or end-users do with Durango?
- What platforms are currently supported by Durango?
- I don't have Adobe Flex Builder. Can I use Durango?
- How do Durango components communicate?
- How are automatic connections between components established?
- Is it safe to use Durango enabled components?
- What is the goal in putting Durango on Adobe Labs?
- Can I get any technical support?
- Will this project become open source?
- When will Durango be officially released as a supported Adobe product?
- What is the licensing for Durango?
- Can I license Durango for distribution on CD or for my company's intranet?
- Can I make Durango available directly from my website?
- Does Adobe provide a common place to share my components?
- Where do I publish applications I've built using Durango?
- What is Durango?
-
Durango is a framework that allows developers to build Adobe AIR applications that can be customized by end-users. Durango allows developers, designers and end-users to easily mashup independent components to create new applications or extend existing Durango-enable applications.
Developers need to download the Durango SDK to use the Durango framework. Durango enabled AIR applications are delivered as AIR (.air) files which end users install. These applications incorporate the Durango framework and are Durango enabled.
- Does Durango work for Adobe Flex applications running in browser?
- The current release of Durango only allows drag and drop of components across Adobe AIR applications. However, URL's can be dragged from browsers and dropped in Durango applications to create an HTML wrapper component displaying the contents of the URL. Remote SWF content can also be incorporated in a Durango application using a similar wrapper component.
- What can developers do with Durango?
- Developers can use the Durango APIs when developing components and within applications. Components can be made reusable by implementing a Durango interface and specifying values for some new metadata tags. Applications can use Durango to accept and display dragged components at runtime.
- What can designers do with Durango?
- With a palette of components, designers can create wire-frame mockups of applications, including behavior, in real time.
- What can consumers or end-users do with Durango?
- Consumers or end-users can create interesting, personalized mashups without needing to know any kind of programming. They can also save and share their new applications.
- What platforms are currently supported by Durango?
- Durango applications and components can be used wherever the AIR runtime is supported. On Windows and Macintosh, additional shell desktop integration is available for creation of new Durango applications and working with application fragments.
- I don't have Adobe Flex Builder. Can I use Durango?
- Yes. You can use Durango to create, save and re-launch new application mashups, but you will not be able to edit a Flex Builder project generated from a mashup, nor will you be able to create a .AIR redistributable application.
- How do Durango components communicate?
- Durango components can share information via conventional Flex Data Binding. Bindings between components are made automatically when components are added to an application. Users can also manually make and break connections between components.
- How are automatic connections between components established?
- Properties on Durango components that may be connected are marked using metadata tags. Properties may be tagged as data sources, destinations, or both. When new components are added to an application, Durango makes as many connections to it as possible from among the available unbound component properties already in the application. Connections are made whenever values can be converted to the available type, or can be constrained to match property names.
- Is it safe to use Durango enabled components?
- Durango allows reuse of components from Adobe AIR applications that have been installed on the user's computer. Like any desktop application, Adobe AIR applications can have access to local computer resources, like user files and the network. When Adobe AIR applications are installed, the user learns how the application was signed and can decide whether to trust it. Since Durango mashes up components from trusted applications, it doesn't introduce new security problems; if the user only reuses components from applications the user trusts, they will feel comfortable with those components.
- What is the goal in putting Durango on Adobe Labs?
- Durango component reuse represents a completely new way to share code and drive viral adoption of new components and services. We are soliciting your feedback on this Labs release to guide us as we continue to develop the features and capabilities of Durango.
- Can I get any technical support?
- The current Durango release is only supported through the Durango discussion forum.
- Will this project become open source?
- The current release of the Durango framework source is not being open-sourced at this time. Adobe believes the technology is in an early stage and its implementation and feature set may change significantly before it is released as part of a product. When Durango is released, its source will most likely be made available in a manner consistent with the host product.
- When will Durango be officially released as a supported Adobe product?
- Durango is an experimental technology. Its release as a supported product depends on a number of factors — robust market demand, viable business models and overall product strategy.
- What is the licensing for Durango?
-
In general, you may modify and incorporate the sample code into your application but you may not modify the documentation or the Adobe AIR runtime or Adobe AIR SDK in any manner. You may create applications that incorporate ReuseLib.swc, and these applications may be redistributed as AIR files (.air) only. You may not delete or in any manner alter the copyright notices, trademarks, logos or related notices, or other proprietary rights components of the Adobe Durango SDK other than sample code that you modify in accordance with the Durango license agreement. Full details and specific license terms are included in the Durango SDK License and Adobe AIR SDK found in the installation directory. Please read the Adobe AIR SDK license for details on restrictions and use of components.
- Can I license Durango for distribution on CD or for my company's intranet?
-
You may make, install and use a limited and reasonable number of copies of the components of the Adobe Durango SDK for purposes of your internal development of Developer Applications. Full details and specific license terms are included in the Durango SDK License.
You may not distribute the Adobe AIR SDK without first obtaining distribution rights from Adobe.
- Can I make Durango available directly from my website?
- You may copy and distribute the sample code and redistributable components as incorporated into your application. You cannot distribute the documentation or runtime or any component included in the Adobe AIR SDK on your website. Full details and specific license terms are included in the Durango SDK License.
- Does Adobe provide a common place to share my components?
- At this time Adobe does not provide a designate place to share your components although we may offer such an exchange in the future.
- Where do I publish applications I've built using Durango?
- You can use the Adobe AIR Marketplace to publish your applications.
