Re: [flexcoders] Flex Builder 2 to Flex Buiulder 3 IDE changes: some good, some bad

2008-05-30 Thread Joseph Balderson
Uncheck these two:

Window > Preferences > Flex > Editors > ActionScript Code
 > Keep imports organized
 > Remove unused imports when organizing

Problem solved.
___

Joseph Balderson | http://joeflash.ca
Flex & Flash Platform Developer | Abobe Certified Developer & Trainer
Author, Professional Flex 3 (coming Winter 2008)
Staff Writer, Community MX | http://communitymx.com/author.cfm?cid=4674



mr_j_harris wrote:
> I upgraded from Flex Builder 2 to Flex Builder 3- to be able to use
> the AdvancedDataGrid was the driver behind the decision.
> 
> The first thing I noticed was in the debugger, variables window,
> yellow highlighting on the modified variables. Nice!
> 
> The second thing I noticed was the source-code mode editor's
> propensity to re-organize my 'import' statements.  This I didn't
> appreciate.  Oh, sure, it's a little organized - alphabetical,
> respecting hierarchy.
> There was an option to do this in Flex Builder 2, called 'organize
> imports' or something.
> 
> However, I liked my imports arranged like this, in three or four groups:
> 
> #1 system level (flash, mx etc)
> 
> #2 '3rd party' level; (cairngorm for example)
> 
> #3 utility-level - homebrew - perhaps built with parts from layers 1 &
> 2, but not application specific
> 
> #4 application level - dto, event, control, command objects specific
> to the application.
> 
> 
> Call me neurotic, but this way I can can glance at the groups and see
> what this file is about.  So, please leave my imports alone!
> 
> 
> -- [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --
> Flexcoders Mailing List
> FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> Search Archives: 
> http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links
> 
> 
> 
> 


[flexcoders] Flex Builder 2 to Flex Buiulder 3 IDE changes: some good, some bad

2008-05-30 Thread mr_j_harris

I upgraded from Flex Builder 2 to Flex Builder 3- to be able to use
the AdvancedDataGrid was the driver behind the decision.

The first thing I noticed was in the debugger, variables window,
yellow highlighting on the modified variables. Nice!

The second thing I noticed was the source-code mode editor's
propensity to re-organize my 'import' statements.  This I didn't
appreciate.  Oh, sure, it's a little organized - alphabetical,
respecting hierarchy.
There was an option to do this in Flex Builder 2, called 'organize
imports' or something.

However, I liked my imports arranged like this, in three or four groups:

#1 system level (flash, mx etc)

#2 '3rd party' level; (cairngorm for example)

#3 utility-level - homebrew - perhaps built with parts from layers 1 &
2, but not application specific

#4 application level - dto, event, control, command objects specific
to the application.


Call me neurotic, but this way I can can glance at the groups and see
what this file is about.  So, please leave my imports alone!


-- [EMAIL PROTECTED]