1. Hmm. Okay, well glad it’s working now

2. The formatter does predefine some groups (effects, styles, properties, and events, I think). The groups are hardcoded (but modifiable) and I got them from crawling through the ASDoc for some Adobe classes. You can create your own groups or extend the ones I created. You can also use wildcards (java-style regex).

3. There is some explanation of how to use it in the ? settings on the pref dialog.

4. I did push a new plug-in that you may have some feedback on. It’s a simple plugin that emits asdoc comments for the current element or file. It’s a first cut, but if that capability is something you would find useful, then you are welcome to pull it down and ask questions/file bugs. It’s 2 jars in the “Test Code” package at the flexformatter site. I didn’t really have an set of requirements for it, so I’m still waiting to see if people consider it useful before I bundle it with the flex formatter code.

2. I’ve messed around with the attribute ordering, but haven’t applied any real policies to it. Will dig into it soon to see if I can make it do anything useful for me. I think ideally it would allow layouts similar to the Flex Properties panel:
Common
Style
Layout
Effects
Events
Other

Luckily our MXML has not been the bulk of our work so have not really been annoyed by this too much. But would be nice…

3. Import/Export right now, and yes Eclipse workspace settings management sucks. I’ll have to try the autosync from file setting as everything we do is in SVN.

Keep up the excellent work!

One thing to consider… Style Browser, so you can have some contributors upload their styles – then users can pick their favorite and download to their local settings…

A couple of questions for you:
1. Did you have problems with mxml or embedded xml? I’m just curious what I fixed.

2. If you do much mxml coding, have you tried (or do you care about) attribute ordering? There are some relatively recent changes (probably since 0.6.16) for grouping attributes together (like all namespace attrs). The ability to control attr ordering was there from the start, but it’s a little more useful now.

3. How are you sharing the settings with your team? Are you using Import/Export or did you try the new “auto sync from file” option? Eclipse doesn’t really provide a great way to share workspace-level settings, but this option would kind of work with CVS to keep options synchronized among team members when the options are tweaked.

I really need to update my Blog more. Grabbed your formatter couple months ago, was fairly unhappy with the stability (especially as I have a lot of XML code that it had a problem parsing). Grabbed the update a couple weeks ago and now it ROCKS. No show stoppers for me at all. We now share format configs around the team so everyone is on the same settings. Great work!

http://sourceforge.net/project/platformdownload.php?group_id=248408