08.28.08

LOTS of Flex 4/Gumbo Information

Posted in Flex at 8:22 am by Saran

The links to the Flex 4 specs, architecture docs, API, and includes some informational videos.

http://www.mikechambers.com/blog/2008/08/27/everything-there-is-to-know-about-flex-4-gumbo/

08.21.08

Flex Builder Linux Alpha 4 Released on Labs

Posted in Flex at 4:13 pm by Saran

The fourth prerelease version of Adobe Flex Builder for Linux is now available for download on Adobe Labs. Flex Builder for Linux is an Eclipse plugin version of the software that you can use to build Flex applications on Linux. See the release notes for more information regarding the alpha.

New Gumbo Specs posted to opensource.adobe.com site

Posted in Flex at 4:12 pm by Saran

http://opensource.adobe.com/wiki/display/flexsdk/Gumbo

Adobe releases Flex Builder 3.0.1 and Flex SDK 3.1

Posted in Flex at 3:46 pm by Saran

Flex Builder and the Flex SDK 3.1 are now available: “Introducing Flex SDK 3.1 and Flex Builder 3.0.1″.

For a complete list of bug fixes, check out SDK: Fixed Bugs in 3.1, 3.0.1 FBFixedBugs and DMV 3.0.1 Fixed Bugs.

08.11.08

Flash/ Flex Error

Posted in AS3, Flex at 8:17 am by Saran

ActionScript 3 Error: 1038: Target of break statement was not found.

ActionScript 3 Error #1038 Description:
A break statement is used only with loops. They will not work in if statements. This is directly from the documentation:

Appears within a loop (for, for..in, for each..in, do..while, or while) or within a block of statements associated with a particular case in a switch statement. When used in a loop, the break statement instructs Flash to skip the rest of the loop body, stop the looping action, and execute the statement following the loop statement. When used in a switch, the break statement instructs Flash to skip the rest of the statements in that case block and jump to the first statement that follows the enclosing switch statement.

In nested loops, break only skips the rest of the immediate loop and does not break out of the entire series of nested loops. To break out of an entire series of nested loops, use label or try..catch..finally.

The break statement can have an optional label that must match an outer labeled statement. Use of a label that does not match the label of an outer statement is a syntax error. Labeled break statements can be used to break out of multiple levels of nested loop statements, switch statements, or block statements. For an example, see the entry for the label statement.

Pay attention to the last two paragraphs if you want to break all the way out of a function/method rather than just the loop that the break statement is inside then you need to use label. A very handy but seldom used method

Flex / Flash Error #1038 Fix:
Make sure that your break statement is within a valid loop such as for, while, switch statements, etc… Another alternative is to use a return statement without any parameters. Warning: Using return will break out of the function entirely and will not execute any code after the if statement. return is typically used as the last line of code in a function.

Bad Code:

if (totalScore < 10)
{
finalMsg = “Sorry!<br /> You need more practice”;
break;
}
else if (totalScore < 20)
{
finalMsg = “Congratulations!<br /> You kept yourself and others safe”;
break;
}

Good Code:

if (totalScore < 10)
{
finalMsg = “Sorry!<br /> You need more practice”;
return;
}
else if (totalScore < 20)
{
finalMsg = “Congratulations!<br /> You kept yourself and others safe”;
//break can be removed to get rid of the error;
}

This should help you resolve Flex / Flash Warning #1038

ActionScript 3 Error #1061: Call to a possibly undefined method addEvent through a reference with static type flash.utils:Timer.

ActionScript 3 Error #1061 Description:
AS3 error 1061 appears when you have misspelled a property or function and have not assigned a value to it. If you haven’t properly typed the Object to begin with you will get AS3 Error 1069. See the examples below. AS3 error 1061 is actually pretty nice to work with because it tells you exactly which method/property didn’t work and it tells you which object it didn’t work on.

Flash / Flex Error 1061 Fix:
Find the object listed in the error and then check the spelling after the dot.

Bad Code 1:

var t:Timer = new Timer(1000, 60);
t.addEvent(TimerEvent.TIMER, Tick);

Good Code 1:

var t:Timer = new Timer(1000, 60);
t.addEventListener(TimerEvent.TIMER, Tick);

Related ActionScript Error(s):
Flash / Flex Error 1069
- You will get AS3 Error 1069 instead of 1061 if you don’t properly type your object before referencing a property on it. For example var t:Timer = new Timer(1000, 60);
t.addEvent(TimerEvent.TIMER, Tick); will give error 1061 but var t = new Timer(1000, 60);
t.addEvent(TimerEvent.TIMER, Tick); will give Error 1069.
Flash / Flex Error 1119 -
The dreaded AS 3 Error 1119
Flash / Flex Error 1056
- This is the error you will get if you try and call a property with a misspelled name in the same way as calling a property with a misspelled name.

ReferenceError: Error #1069: Property addEvent not found on flash.utils.Timer and there is no default value.

ActionScript 3 Error #1069 Description:
AS3 error 1069 appears when you have misspelled a property or function and have not assigned a value to it. If you have properly typed the Object to begin with you will get AS3 Error 1061. See the examples below. AS3 error 1069 is actually pretty nice to work with because it tells you exactly which method/property didn’t work and it tells you which object it didn’t work on.

Flash / Flex Error 1069 Fix:
Find the object listed in the error and then check the spelling after the dot.

Bad Code 1:

var t = new Timer(1000, 60);
t.addEvent(TimerEvent.TIMER, Tick);

Good Code 1:

var t = new Timer(1000, 60);
t.addEventListener(TimerEvent.TIMER, Tick);

This should help you resolve Flex / Flash Error #1069

Thanks and as always Happy Flashing

Curtis J. Morley

Related ActionScript Error(s):
Flash / Flex Error 1061
- You will get AS3 Error 1069 instead of 1061 if you don’t properly type your object before referencing a property on it. For example var t:Timer = new Timer(1000, 60);
t.addEvent(TimerEvent.TIMER, Tick); will give error 1061 but var t = new Timer(1000, 60);
t.addEvent(TimerEvent.TIMER, Tick); will give Error 1069.
Flash / Flex Error 1119
Flash / Flex Error 1056
- This is the error you will get if you try and call a method with a misspelled name in the same way as calling a property with a misspelled name.

ActionScript 3 Warning: 1102: null used where a int value was expected.

ActionScript 3 Warning#1102 Description:
This warning is pretty good at describing what is happening but is needs to add a little to explain why. This error will appear when you try and force a variable to be a certain Type within a predefined function. For example if you have a variable like _minute below

Flex / Flash Warning1102 Fix:
Find where you are using null and make sure that you are using the proper value

Bad Code:

var TargetDate:Date = new Date(_year, _month, _date, _hour, _minute=null);

or

var TargetDate:Date = new Date(_year, _month, _date, _hour, _minute=”10″);

or

var TargetDate:Date = new Date(_year, _month, _date, _hour, _minute=false);

Good Code:

var TargetDate:Date = new Date(_year, _month, _date, _hour, _minute=10);

Warning:
You will not get this error with the code below even though it seems like the same as the code above. The smart folks at Adobe put in logic that will accommodate for numbers-as-strings and also boolean which will result in the number 0.  The AS3 Warning will will only show when you assign an non-permitted variable within the parameters of a method call. The code below will output a valid date. Direct assignment in quotes will be translated into a valid Number not an int. False shows up as 0 in the date.

var TargetDate:Date = new Date(_year, _month, _date, false, “10“);


This should help you resolve Flex / Flash Warning #1102

Flash / Flex Error #2078: The name property of a Timeline-placed object cannot be modified.

ActionScript 3 Error #1061 Description:
The MovieClip or Button that you have on the stage cannot be changed with code. It already has a name so you can’t change it. If you are visiting this page my guess is that you are thinking that you have a dynamic movieClip that you named with code, yet you probably have one with the same name on the stage already.

Flash / Flex Error 1061 Fix:
Stop trying to change a named object on the stage that already has one.

Bad Code:

myMovieClip.name = “Bob”;

08.01.08

BlazeDS Developer Guide Updated

Posted in Flex at 7:37 am by Saran

An updated PDF version of the BlazeDS Developer Guide is available at:

http://livedocs.adobe.com/blazeds/1/blazeds_devguide/blazeds_devguide.pdf
This revised Developer Guide contains all of the content from the new LiveCycle Data Services 2.6 Developer Guide that applies to BlazeDS.

Note: Only the PDF version of the Developer Guide is updated. The Livedocs HTML is not updated.

07.29.08

Flex in a Week is available

Posted in Flex at 6:08 am by Saran

Flex in a Week is a week-long, video based online training program for developers. This self-paced program is free and is intended to help developers accelerate their Flex learning. The training will eventually be a full 5-day program, however they are launching with the first three days which will provide developers with enough learning to get them started using Flex.They will complete the remaining two days of content over the coming weeks.

07.24.08

Flex Gumbo API Reference available

Posted in Flex at 7:10 am by Saran

The ASDoc API reference for Flex Gumbo, the next version of Adobe Flex, is now available at http://livedocs.adobe.com/flex/gumbo/langref/.

For general information about Gumbo, see the Gumbo page.ᅠ

07.15.08

Learn About Gumbo: The Next Version of Flex

Posted in Flex at 7:10 am by Saran

Gumbo is the code name of the next version of Flex. New information about Gumbo has been made available on the Gumbo page of the Flex Open Source site.ᅠ

Highlights of the new information about Gumbo include the following:

Themes of the Release
Gumbo is being planned around three primary themes:

  • Design in Mind
    A framework for continuous collaboration between designer and developer.
  • Developer Productivity
    Improve compiler performance and add productivity enhancements.
  • Framework Evolution
    Take advantage of the new Flash Player capabilities and add features required by common use-cases.

Recorded Presentations

White Paper: An Introduction to the Gumbo Component Architecture
This white paper provides a comprehensive look into our plans for the next version of Flex.

Gumbo Feature Specifications
Read, and comment on, the recently published specifications for Gumbo. Currently, there are eight specs available, with more on the way.

Summary Version of Gumbo Themes
Here is a summary version of the themes of Gumbo, the next version of Flex. Details of these Gumbo themes and other plans for the next version of Flex can be found on the Gumbo page of the Flex Open Source site.ᅠ

Design in Mind
A framework for continuous collaboration between designer and developer. We’re planning the following:

  • A framework designed for continuous collaboration between designer and developer.
  • Building out the MXML language to provide more toolability.
  • Creating a format that describes vector graphics in XML that closely matches what Flash Player is doing.
  • A new component and skinning architecture that will allow easy “skinnability” of components.
  • Improvements in experience-oriented features such as states, effects, and layouts.

Developer Productivity
Improve compiler performance and add productivity enhancements. New builds are showing compiler performance improvements. Gumbo will add the following:

  • Two way data binding
  • Automation support for Flex components in AIR
  • CSS improvements

Framework Evolution
Take advantage of the new Flash Player capabilities and add features required by common use-cases:

  • New text features available from Flash Player 10
  • Bi-directional and vertical text.
  • New, nicely skinnable video component

06.26.08

Flex 3 Compiler Design

Posted in Flex at 5:13 pm by Saran

please visit http://blogs.adobe.com/pfarland/2008/06/using_amf_with_flashneturlload.html

« Older entries