[#FB-8297] Source code formatter

Flex Builder

Source code formatter

Created: 07/13/07 01:29 AM Updated: 05/30/08 03:40 PM

Component/s:

General Eclipse UI

Security Level:

Public (All JIRA Users )

Severity:	Usability Issue
Reproducibility:	Every Time
Discoverability:	High
Found in Version:	Moxie M3 (Beta 2)
Milestone:	I6
Affected OS(s):	All OS Platforms - All
Steps to Reproduce:	« Hide Steps to reproduce: 1. Go to Source menu item 2. There is not format action Expected Results: There really should be a code formatter. When copy-pasting code around a file, MXML/AS3 code gets messy really fast. A formatter would really help a lot to keep your code readable. Workaround (if any): Show » Steps to reproduce: 1. Go to Source menu item 2. There is not format action Expected Results: There really should be a code formatter. When copy-pasting code around a file, MXML/AS3 code gets messy really fast. A formatter would really help a lot to keep your code readable. Workaround (if any):
Language Found:	English
Bugbase Id:	none
Triaged:	Yes
Regression:	No
QA Owner:	Mac Martine
Fixed Version:	(Planning) Post Moxie - Next Build
Confirmed Version:	Moxie M3 (Beta 2) - 178196
Participants:	Dasa Paddock, Heidi Williams, Larry McLister, Leen Toelen, Leif Wells, RJ Owen, Tanya Dimalsky, Tim Buntel and Tony Fendall

All

Comments

Sort Order:

[ Permlink | « Hide ]

Heidi Williams - [07/31/07 11:40 AM ]

QRB deferred for Moxie.

[ Permlink | « Hide ]

Leif Wells - [04/16/08 11:45 AM ]

If you are seriously considering implementing a source formatter, please consider the following requests:

1) Make it possible for us to set team standards for source formatting so that we can control the order of our MXML attributes.
For instance:
Format attributes to always list "x" before "y"
Format attributes to always list "width" and "height" after "x" and "y"
Format code to always place a line break after "x", "y", "width" and "height" keeping those attributes on a single line

Items like these can make standardizing code a little easier in teams.

2) Make it possible for us to create and set templates for new MXML and ActionScript files so we may be able to control things like copyright notices when a file is created.

[ Permlink | « Hide ]

Leif Wells - [05/20/08 06:09 PM ]

Tim, if you want to discuss how this issue effects me, feel free to contact me at any time (leif [dot] wells [at] gmail [dot] com).

[ Permlink | « Hide ]

RJ Owen - [05/20/08 11:51 PM ]

This issue is partially addressed by adding Snippets to Flex Builder. However, this is a rather difficult process for the average user and doesn't provide the same depth of functionality that a real source formatter would. Snippets also change on a per-workspace basis and the user has to create them all from scratch at least once anyway. I'd love to see something of the same level as Java's source formatter - it'd be a huge plus for me.

[ Permlink | « Hide ]

Tony Fendall - [05/21/08 05:19 PM ]

Adding Leif's comments, it would be nice if it would always put the "id" attribute first

[ Permlink | « Hide ]

Dasa Paddock - [05/23/08 10:49 AM ]

It'd be great if it had an option to format the code according to the coding conventions at:
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions

[ Permlink | « Hide ]

Larry McLister - [05/30/08 03:40 PM ]

moved to I6