This day, again, is one of those days. As agile as a start-up has to be, and release as often as possible, there are times when you just have to spend a little more time on something in order to get it out. This is one of those times. 🙂 It’s been a while since the last release but, I’m pretty sure, you’ll be happy enough about what this release brings you.
Among the plethora of little features and improvements that are constantly being added to FlairBuilder, there are some big additions that people have been asking for quite some time. Today I’m happy to mark another one of those items as being officially added to the application. Drums roll….
iPhone Applications Prototyping
Ta-da! Yay! 🙂 So, I’m happy to announce that since today, FlairBuilder comes with dedicated support for iPhone applications prototyping. And by dedicated I mean that there’s now a special type of project, iPhone prototype project, with a fixed width page and a surrounding iPhone picture. Each iPhone project page has also a top and bottom bar which can be toggled visible/non-visible. I didn’t see any use in having masters for iPhone project pages, so I didn’t include this feature here.
There is a number of new, iPhone specific, components that have been added: a Button Bar, ON/OFF toggle button, a pointy navigation button, a very flexible tree-table list, a large button, and a horizontal slider.
Custom Widgets Library
You are now able to quickly select a set of components, group and save them for later reuse. Anything you need and can think of, from login forms to specific groups of components that you find yourself implementing again and again.
Coming up soon will be the possibility to share you custom widgets with the FlairBuilder community by uploading them directly from inside the app. You’ll also be able to access the community library from the application as well.
You now have the option to add your own icons to the icons set that comes with FlairBuilder. Just drop your icons into the folder located at USER_HOME/.flairbuilder/icons, and FlairBuilder will pick them up. It should be straightforward. And by the way, when opening the project in the viewer, it will just work. Your custom icons that you used in the project will also be available in the viewer. Enjoy!
Embedded page links
An highly requested features was for some time the ability to specify links to other pages inside components like DataGrid, List, Tree or Paragraph. Well, now you’re able to do just that with a simple syntax: [Page Name#Link Text].
Handy formatting toolbar
There are a lot of places where you double-click a component to edit its content and FlairBuilder supports a custom syntax to help you insert formatted content easily. However, remembering all those formatting options (include the new page link syntax) is not as easy. Add to this inserting icons, thing which, I must confess, was quite painful until now.
Yeah, until now, because now there’s a formatting toolbar to assist you in editing the content of all those components that support formatting. Plus, you know have a drop-down for inserting icons as well as inserting page links. To insert a link, just select the link text, click on the Link icon, and you’ll get a pop-up with all pages in the project to choose one.
To insert an image, just click on the Image icon and you’ll get a pop-up with the default icons library plus your custom library. Click on an icon to insert its associated syntax.
Improved Window component: Now collapsible
The Window component got a face lift. Not only that now is much more customizable, but it also got a little feature that some of may appreciate. You can now specify if the window should toggle visibility of its content. For this I introduced a new syntax element, [+] and [-] to specify expanded state.
Specify expanded nodes in the Tree component
Using the same ‘expanded’ [+] and [-] syntax used in the Window component, you can now specify which nodes to be opened by default in the Tree. Just use [-] for an expanded node. The other option is implicit.
Change visibility and enabling of components
FlairBuilder prototypes just got a little more interactive. All components now have two new states: visibility and enabling. I also added two new actions that let you change this states for a certain component or group of components. Unleash your imagination! 🙂
Card stack transition effects
This is a cool little addition that will spice up your prototypes: specify that transition between the cards of a card stack should be done with an effect. For now there’re two effects available: Fade and Slide. I think it’s enough for now. 😉
The Rectangle component got a little more flexible by allowing you to change it’s opacity. This will let you add even more ‘flair’ to your prototypes.
Page on load event
For the first time in the history of FlairBuilder, it’s now possible to attach an event to a container. And which container have I had to start with other than the pages themselves? Attach any action you think it makes sense to be performed when displaying a page. I hope you’ll find this helpful.
Other improvements and bug fixes
- Improved application menu, including on Mac OS X. It used to be half-native, but not it’s fully integrated with the native capabilities of the Adobe AIR platform.
- Go to page action lets you specify a generic ‘Go to last page’ option instead of specify a particular page. Handy, I’m sure you’ll find it.
- Bug fix:Action conditions where not correctly saved when specified as being exclusive (OR switch was reverted to an AND).
This release has been by far one of the biggest in the history of FlairBuilder. I guess that only last summer’s 1.7 release could compare with it. A lot of work went into this release and I’m extremely happy and excited about it. I’ll take a short break from development but I want you to start shooting with new ideas and suggestions TODAY! 🙂 There’s nothing more valuable to a tool developer than the feedback received from users. So, don’t hesitate!
Should you find any problems or issues with anything of the features mentioned above, just let me know at firstname.lastname@example.org and I’ll get fixed in no time.
Until next time, take care and have fun prototyping!
Unknown, here I come!