Re: [flexcoders] Flex2.0: MXMLC compiler is a big pain during migration from 1.5 to 2.0

Mon, 20 Mar 2006 17:27:33 -0800

i updated the templates to reflect beta 2 btw. will still work with beta 1 as well.

On 3/20/06, Michael Schmalle < [EMAIL PROTECTED]> wrote:
>6. Modified Void to void for all the functions. (this is the stupidest thing in the world)

No it's not. as you can see null has always been null. Just like Void should have been void.

They are getting it consistent, you should be happy!

Peace, Mike


On 3/20/06, Johannes Nel < [EMAIL PROTECTED]> wrote:
what i forfot to say with betya 2 being released soon, i am not certain what parts of the unit test template will break. so just keep that in mind


On 3/20/06, Johannes Nel <[EMAIL PROTECTED]> wrote:
if you had unit tests everything would be linked autmatically to the compiler. a good argument for best practises no...
anyway, i suggest you check out this:
http://www.lennel.org/blog/2006/03/02/an-advantage-of-unit-testing-with-flex2as3/

and this: someone said beta 2 is being released pretty soon
http://www.lennel.org/blog/2006/02/27/building-unit-tests-in-eclipse-from-an-ant-script-for-asunit/
to do that automatically for you.
you can grab flex unit and modify the templates for that as well.

to run ant you need to install the plugin version into a normal eclipse btw (Adobe please add ant support to the non plugin version!!)


On 3/20/06, t_msreddy <[EMAIL PROTECTED]> wrote:
I am trying to migrate an application that we developed in Flex 1.5 to Flex 2.0.
 
These are the steps I followed:
1. Created a project in Flex 2 builder with empty content.
2. Copied MXML folders/files
3. Copied AS folders/files and Cairngorm 2 packages
4. Modified all my AS files to follow the new package  convention
5. Made sure all the vars have a datatype defined.
6. Modified Void to void for all the functions. (this is the stupidest thing in the world)
 
Now my real problem with Flex 2 builder is that it doesnt really show the compilation problem in AS files until you try to instantiate the object in MXML files. Now I have a ClientVO.as class until I do the following in MXML file, I wouldnt know what the real problem in ClientVO.as is:
                     
                  var client : ClientVO = new ClientVO();
 
Please, save me some nightmares by  suggesting or sharing your experiences in working with Flex 2.0 or during migration from Flex 1.5 to Flex 2.0
 
 


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com



SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice

YAHOO! GROUPS LINKS








--
j:pn
http://www.lennel.org


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com



SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice

YAHOO! GROUPS LINKS





--
What goes up, does come down.


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com



SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice

YAHOO! GROUPS LINKS





--
j:pn
http://www.lennel.org


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com



SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice

YAHOO! GROUPS LINKS



Reply via email to