FlairBuilder允许使用者创建自己的Web或者是桌面的Flex应用程序，也就是说，是在Flair运行中，直接在里面添加控件，自定义程序各种UI以及事件。作者还在完善之中，下载了Demo体验了一下。其中基本的控件已经实现（双击进行添加），不过位置的移动等操作实现比较麻烦。有兴趣地可以去体验一下。

Google Code上主页：http://code.google.com/p/flair/

作者网站：http://www.flairbuilder.com/

我试用了一下：

1、首先在http://www.flairbuilder.com/install-flairbuilder/下载 FlairBuilder，请注意在线下载或安装这个AIR程序使用的是在线安装，跟在IE里下载软件并安装差不多。使用的AIR Express Install Badge。

说明：

为了AIR能迅速的普及和良好的用户体验，官方提供了一个叫Badge的检测SWF文件。

由他来做下载AIR应用程序的入口，他会首先检测用户系统是否安装了AIR运行环境，如果判断AIR运行环境已经安装，会启动AIR来下载相应的AIR应用程序。

如果目标没有机器没有安装AIR运行环境，你可以手动下载安装程序来安装。

理所当然，也提供了类似于Flash Player升级快速安装模式的接口。可以直接通过Flash Player来下载安装AIR。

看得出这是Adobe官方为了尽快普及AIR应用真可谓撒费苦心。

Badge的主要功能大致就是这些。

为方便之后的AIR应用程序更好的让人接受，我在原有基础上加入了简体中文的支持。

在简体中文系统上会显示中文界面，其他的则为显示英文界面。

Badge的Flashvars配置参数如下。

必选参数

• appname (应用程序名，会显示在按钮的下面)
• appurl (.air文件的绝对地址)
• airversion (AIR的运行环境版本)

可选参数

• buttoncolor (按钮的六位十六进制色彩值，或者使用 transparent 为透明)
• messagecolor (按钮下面提示文本的六位十六进制色彩值)
• imageurl (背景图片地址，jpg、png、gif 之类)

2、 FlairBuilder安装界面：

3、FlairBuilder试用界面：

作者应该还会完善更新。有兴趣的朋友可以去下来试试。

————————————————————————————————————————————

关于这个软件的原文介绍：

How many times you’ve had an idea of an application (CD’s database, a library, revolutionary issue tracking system etc.) and you could not find the time to start coding it? I know I did several times.

And even with “create a blog app in less then x minutes” kind of framework, you still need to write code, and actually need to digg into each if, for or while of the classes behind. And no matter how clean your language is, or how domain driven you design is, you still need to tell the machine what you have in mind, and, what’s frustrating me most, not in the way it’s in your mind.

And imagine that you sit right beside your client and you wanna make sure that she agrees as much as possible with what you’re about to implement. In this case, how much time do you need to mock up something that really shows how the real thing will work?

There might be cool frameworks out there that just know what CRUD operation are, but software is most of the time more then CRUD. Most of what the user sees is the UI, and the UI is far more complex then basic CRUD database operations.

On the other hand, given the complexity of software, one may easily (or hardly sometimes) find that there are certain patterns that a developer gets to implement yet again and again. The examples are countless. From simple object creation/updating to user rights based visualization.
And since the patterns are there and well known, what’s so hard to think of a tool that actually has all the knowledge built in and sort of leads you through the steps of applying those patterns?

If there is no such think as “New Bridge Pattern Implementation Wizard” in your favorite IDE, does it means that the IDE should not be able to understand that a form (web or desktop) should not be submitted with invalid fields and not be submitted twice (hence disable OK button on submit)?

How many combinations of OK-Save-Cancel-Help are in the applications we all use every day?
Given a button in a toolbar, which is the probability that button’s action will impact somehow (CRUD?) the selected item(s) somewhere close to the button? Like, for instance, in a table or in a tree or a list.

The combinations and possibilities are countless but the basic bricks are well known and well defined (a button may be clicked but not flipped or dragged). What a developer does most of the time is assembly those bricks in a set of yet another well known but little more complex pieces of walls. And man, how many times they get it all wrong!?

So, these are some of the reasons that made me start this FlairBuidler project. Initially was built in Java Swing, as quick and dirty as it can be done in Java. It got too dirty to continue it, so I said to myself that a web based application should be more appealing to users.

So, here I am with a Flex version. Working with Flex for regular application it’s OK. Making an application that actually relies on Flex as framework is just great. You get to discover (together with some weired bugs ) the great design behind the framework. More about that in future posts.

The separation of MXML and AS code, data binding, event system, class metadata, all these made the Flex implementation much more cleaner and flexible and faster (development time). There are still lots of things to do, lots of optimizations to be made but one thing is sure. Flex is not the kind of framework that gets in your way. It’s a great technology and it deserves it’s place as no. 1 RIA technology.

Coming soon with more details about the features that FlairBuilder has right now, and the set of features I am planning to implement in the near future.

————————————————————————————————————————————

参考网址：
http://www.cnblogs.com/xxcainiao/archive/2008/06/09/1216131.html
http://www.cbmland.com/post/433/air-badge-engchs-version.html