Differences
This shows you the differences between two versions of the page.
|
intro [2009/03/21 14:11] arpit |
intro [2009/03/21 14:12] (current) arpit |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== How is OpenPyro different from Flex ? ==== | ==== How is OpenPyro different from Flex ? ==== | ||
| - | * Use it as a framework or as a collection of utility libraries: Different packages in OpenPyro can be used just as utility libraries if you dont want to buy into the entire framework. If you, for example, already have an old project and you only want to use the Painters available in OpenPyro, you can do that without having to re-write the entire application in this new framework. However the different packages are even more potent when used together. | + | |
| + | |||
| + | * Use it as a framework or as a collection of utility libraries: Different packages in OpenPyro can be used just as utility libraries if you dont want to buy into the entire framework. If you, for example, already have an old project and you only want to use the Painters available in OpenPyro, you can do that without having to re-write the entire application in this new framework. However the different packages are even more potent when used together. | ||
| * OpenPyro is not a monolithic framework. OpenPyro is being built with a pay-as-you-go architecture and we are trying to encapsulate different parts of the project to make sure your final swf only compiles the classes for functionality you actually need. So if you are only using the Collections package for example, you will never end up compiling in the code for the layout manager. | * OpenPyro is not a monolithic framework. OpenPyro is being built with a pay-as-you-go architecture and we are trying to encapsulate different parts of the project to make sure your final swf only compiles the classes for functionality you actually need. So if you are only using the Collections package for example, you will never end up compiling in the code for the layout manager. | ||