Flex Formatter is an extremely useful plugin for FlexBuilder / FlashBuilder that formats your ActionScript code (AS3) and MXML according to a broad range of settings, and helps you to generate ASDoc comments automatically. It is free, and open source.
It’s code formatting is quite robust and configurable, handling things like brace settings (cuddling versus next line), white space around parameters and operators, sorting imports, and a ton more. Thankfully, you can export your settings to a file and share it with your whole team. You can also have it automatically update settings from a file that you can share over the network or via SVN / GIT.
Unfortunately, it’s ASDoc features are much more rudimentary, and do not have any configuration options. They serve as an acceptable starting point, and save some time, but I would love to see some additional support here (for example, an option to mark private and or protected members as @private, which is a very common requirement).
Regrettably, Flex Formatter does not seem to come with installation instructions. If you are not familiar with installing Eclipse plugins, it can take a lot of work to figure it out, but it’s very simple if you know how to do it:
- Start up FlexBuilder / FlashBuilder.
- From the Help menu, select ‘Software Updates > Find and Install…’
- Select ‘Search for new features to install’ and click ‘Next >’
- Click ‘New Remote Site…’
- Use name: ‘Flex Formatter’ and url: ‘http://flexformatter.googlecode.com/svn/trunk/FlexFormatter/FlexPrettyPrintCommandUpdateSite/’
- Click OK
- Make sure only ‘Flex Formatter’ is selected in the ‘Sites to search’ list, and click ‘Finish’
- Follow the prompts to install Flex Formatter, and restart the IDE
Once you’ve restarted, you should see the Flex Formatter bar with buttons to ASDoc, format, and rearrange your code. You should also have a ‘Flex Formatting’ entry in preferences.
If you’d like, you can import my settings for Flex Formatter. You can download them by clicking here, unzip them, and import them using the ‘import…’ button at the bottom of Flex Formatter’s preferences.
Flex Formatter’s project home is here and you can find documentation on it’s settings here.
Useful yes, but should have been part of the new Flash Builder instead of a plug-in. I went back to Powerflasher FDT after trying out Flex Builder for a while, as it has these features build in.
Nice plugin, but I agree formatting code should be standard kit.
Like FlexFlip I also prefer FDT, but it lacks the advantage of being integrated in-company like Flash Builder does (FB4 + CS5 could be nice). Also the debugger-capable version of FDT costs like 599 euros, which is a bit steep.
I can attest to your sentiment! I’ve been using Flex Formatter for well over six months now in both FB3 and recently FB4 (both under Leopard and Snow Leopard). It’s a great piece of software that does wonders for code formatting. It’s a must-have in my Flex dev kit.
FlashDevelop has FD Flex Formater plugin, which is port from original FlexFormat
You can also just download the jar files and dump them in your eclipse plugins folder
Shane – huh, I tried that, but it didn’t work for me.
You mean your entire team can actually agree on which lines the curly braces should be, so you can share a single file forcing those? Wow. 🙂
@Unkulunkulu the point would more be, that even if they don’t agree, they all use the same convention to get consistent code.
I’ll try it, thanks Grant
I posted this a while back – http://markstar.co.uk/blog/2009/flashplatform/flex/code-formatting-for-flex-builder-3/
It should definitely be part of Flash Builder as standard. It makes it much easier to pick up someone else’s code!
“an option to mark … protected members as @private”
No, no, no! This is pure evil. Protected members are exposed to others, therefore they should be properly documented. Anyone who does this should be banned from API development for life. And that includes those at Adobe who indulge in this practice within the Flex framework. All this achieves is forcing folk to delve into the code to work out what these methods do.
If a method is not intended for use by others, make it private or internal, don’t bodge it by making it accessible and then trying to hide it.
Nitpicking but wish there was a way to enforce tabbed spacing BEFORE ‘:’on all your declared public, protected, private class variables so that they all line up.
public var myMC :MovieClip
private var _customClass :MyClass
private var _formatted :Boolean = true;
Re: David Arno
There are can often be two sets of API Documentation a developer will want to build… one for advanced users and one for straight application development.
It is perfectly acceptable, even advisable, under certain circumstances to hide unnecessary information to your users.
This practice is far from evil, and in the right circumstance can even be benevolent.
Thanks for the writeup.
The release notes (which include brief installation instructions) are hung off of the main project page, but SourceForge helpfully doesn’t include a link on the main download page and hides the link I added behind the “Show project details” button.
Regarding ASDoc options. There are some options on the page titled “ASDoc Generation”, but they basically let you control which functions/properties get ASDoc added to them when you generate comments for the entire file. Also, you can adjust the text in the templates to some extent, although there’s no help, and no filtering by visibility modifier.
Regarding lining up variable declarations: there is an option to not disturb existing whitespace around declarations, but not to line them up, since that would require multiple passes through the source code.
Also, I believe that FlexFormatter has mxml attribute reordering features that are not available in other Flex tools.
In general, bugs/requests should be added through the bug tracker. I am unlikely to stumble across posts like this dependably. http://sourceforge.net/tracker/?group_id=248408&atid=1126569
i’ll try it out and see…
FlexFormatter is a cool plugin, I am using it for almost an year. I like the feature to format the source on Save, so you press Ctrl + S or Ctrl + Shift + S and source file is formatted.
hey grant –
thanks so much for sharing 🙂
The only unacceptable thing for me is that it overwrites “Ctrl + S and Ctrl + Shift + S for this formatting.”
Which is the same standard key combination for search and replace, or search troughout all the project/files. A very often used feature by many.
Why don’t I see an “import” button in the preferences?
Looks promising, but I get “formatting failures” on many files I run it on. I didn’t think my code was that bad! 😉
I wanted to follow up on my last post. I’ve used the plug-in a bit more, and have had quite a bit of success with it. There were a few files that were “funky”, but I was doing some non-standards stuff with the code there. I’m going to follow up with the developer about the issue I had, but overall it’s a solid plug-in, and I’ve recommended it to my development team.
The lastest version 0.7.2 seems not to work with Flash Builder 4. 🙁
Thanks for the code contribution. Nice features!
Using gskinner’s instructions, the plug-in wasn’t listed in Flash Builder 4 after adding the update site. After consulting with the plug-in developer, I learned all that was needed was to uncheck the “Group items by category” and the plug-in was listed. I could then install it and it runs fine.