Building a large Flex application that communicates with a remote server through SQL commands create an architect design problem. What do you do with all the SQL commands? Do you store them in a properties file or create 50-100 ColdFusion files? What do you do once you want to change some of these SQL commands?
The issue gets even worse once you need to submit few SQL commands for one operation. For example you have a form and once that form submit the client request to sign to a newsletter so you would need two SQL statements.
I created an elegant solution to that problem, utilizing the Abstract Method design pattern. The “SQLStatements Manager” (Flex SQL statements API) will let you create different CRUD (Create, Read, Update and Delete) statements for each form and you have one place where all your SQL commands are located so once it’s time to change them or update your database design, you don’t have to go through your entire application looking for all these SQL statements.
Once you have the SQL statement you can submit them to the database in order to process. I may give an example of implementation of the API using ColdFusion and Cairngorm.
To see an example and download source code:
http://elromdesign.com/blog/Flex/API/SQLStatementsManager/
To view the ASDOC of the API:
http://elromdesign.com/blog/Flex/API/asdoc/
This API will be in a new Flex 3.0 book I am writing called “Developing Enterprise Architect Applications.” click here to read more and pre-order.
All source code contained on this page has been published under the MIT license and is protected as stated therein.
I am currently in the process of writing as a co-author in a new book by Apress called: “AdvancED Flex 3″
This book makes advanced Flex 3 concepts and techniques easy. Ajax, RIA, Web 2.0, mashups, mobile, the most sophisticated Web tools and the coolest interactive Web applications are all covered with practical, visually-oriented recipes.
* Practical, how-to approach for advanced results.
* Leverage the tools you know, Java, PHP, Python, Ruby, in combination with Flex.
* Build high-performance Web applications with interactivity that really engages your users
To read more about the book click here.
Additionally, I am in the process of writing the following book:
Advanced Flex 3.0 - Developing Enterprise Architect Applications.
The book will be published in late 2008. The book will cover the subject of developing an Enterprise Level Flex Applications from planning to designing and finally testing. It is intended for the experienced Flex developer wishing to expand his/her knowledge and expertise. Developing a large scale Flex application is different than developing a small application and although there is a lot of information, there is not any one resource that covers it all. This book will cover all the best practices and give you the tools you need to develop such a large scale Flex application.
In the next few months I will be giving away some of the API’s that will be part of the book. To learn more about the book and signup for the pre-order list click here.
AutoSuggest API can be used to display an Auto Suggest input box. The separation of the data and view is what makes AutoSuggestion API flexible and easy to modify and fit different applications. The UIAutoSuggest gets “TextInput” and “TileList” and the “AbstractAutoSuggest ” keep sorting the list of words based on the user interaction, the data is bindable which allow the TileList and TextInput to be updates on the fly.
This API will be in a new Flex 3.0 book I am writing called “Developing Enterprise Architect Applications.” click here to read more and pre-order.
All source code contained on this page has been published under the MIT licence and is protected as stated therein.
To see an example and download source code:
http://elromdesign.com/blog/Flex/API/AutoSuggest/
To view the ASDOC of the API:
http://elromdesign.com/blog/Flex/API/asdoc/
The API is responsible for displaying different files type. There are many scenarios where you want your application to use a different class or component to display different types of files. You can use “if-else” statements; however the problem is when you want to use different type of component or classes to handle the different types of files. Using the factory design pattern solve that problem; The concrete product needs to implements the “IView” interface and the component that is responsible for displaying the file can be of any type. “UIFileViewer” class is responsible for creating the component and adding it to the UIComponent.
This API will be in a new Flex 3.0 book I am writing called “Developing Enterprise Architect Applications.” click here to read more and pre-order.
All source code contained on this page has been published under the MIT licence and is protected as stated therein.
To see an example and download the source code click here:
http://elromdesign.com/blog/Flex/API/FileViewer/
ASDOC:
http://elromdesign.com/blog/Flex/API/asdoc/
