Flash Builder 4 Beta 2

Vera
Any updates on release date? If not, any advice on what step to take when trial period runs out, which, in my case, only a couple more days? Thanx.
sbliss

sbliss,
Please see my answers inline:
1. If spend the $249.00 for Flex Builder 3.0 license in order to get Flash Builder 4.0 extension, how much else would to pay to get FB 4.0 upon release?
I don't have an official answer on the upgrade price from FB3 to FB4, however, I would expect it to be in the ballpark of what we had for FB2 to FB3 (please see our current upgrade offerings here).
2. I understand Flash CS5 Pro will also be coming out soon. (a) Why separate and not as a bundle?
Unfortunately, we can't discuss various packaging options before they are officially announced, but we are definitely looking to provide customers good combinations of our tools.
(b) What will be the ideal situation to be in, from a developer's standpoint? In other words, should it be Flash CS5 Pro or Flash Catalyst? Your advice is highly appreciated.
Quoting from Catalyst FAQ:
How is Flash Catalyst different from Flash Professional?
Flash Catalyst is an interaction design tool, based on the Flex 4 framework that is focused on creating expressive interfaces and interactive content without writing code. Flash Catalyst is an approachable tool for designers who want to rapidly create Flash content that is organized into pages or “states”. It is also ideally suited for projects that may need to be extended by developers who use Flash Builder 4. Flash Professional is the industry-leading tool for creating engaging interactive experiences across the multi-screen environment. Learn more about Flash CS4 Professional on Adobe.com.

Similar Messages

Can't Uninstall Flash Builder Beta 1

Hi,
I installed Flash Builder Beta 1 a few months ago and now I can't seem to uninstall it. Everytime I run the uninstall script, Uninstall Adobe Flash Builder Beta, it begins, prompts me for my admin password, starts loading the Flash Builder app screen, but then the uninstaller exits without removing the application. Is there some step that I'm missing or an alternative way to remove the application? The trial has expired and is pretty much useless with Beta 2 out. Any help regarding this matter would be very much appreciated
Thanks in advance,
Randy

If you are using Windows you should be able to have the option of uninstalling it from the following: Start>Control Panel>Programs and Features window, instead of the uninstall executable.

Nightly SDK and Flash Builder Beta

I am using Flash Builder Beta and have tried different nightly builds (ie. 4.0.0.9437, 4.0.0.9417, 4.0.0.9188) and have the same issue - when going into Design View I receive several warnings:
Design View could not load fiber_rb.swc. It may be incompatible with this SDK, or invalid. (DesignSWFLoader.ERROR_LOAD_VERIFY).
The same error for: fiber.swc, serializers_rb.swc and sparks.swc.
Does anybody have a fix besides two workspaces with diff. sdks?
There have been some other discussions in regards to this but with no fix.
First ... Adobe talks of using nightly builds with instructions.
Second ... when users have problems such as above a standard reply is "this has been fixed in an internal build". How does that help us?
Third ... in Flex Bug and Issue Management System this was a reply -
Heidi Williams - [08/04/09 05:40 PM ]
I don't think we want to spend time on encouraging users to use newer SDKs with DV of Beta 1. There are probably lots of things that won't work so they should either just get on prerelease or wait for the next Beta.
Fourth ... prerelease is not open any more and I for one am unfortunately not on it. FWIW - I do own a Flex Builder 3 license.
I understand Flash Builder is a Beta program, but why talk of nightly sdk releases and using Flash Builder if there are issues and unavailable internal builds. And if Adobe is working on bug fixes, along with changes such as the Rename List, why not give users access to those internal builds? At least licensed users. Let everyone keep up to date!

Hi,
Form early in the piece it was acknowledged that nightly builds would not work corrrectly with design view. As there will be a second beta in a matter of days now It would be best to wait for that. The builds from the pre-release program have shown a great amount of improvements across the board so I am sure the end of August(hopefully) beta release will be pretty good and make a lot of people happy.
I use locally compiled sdks that I update every night and things are working reasonably well. So just hold on for a little longer and enjoy the second beta release when it arrives.
David.

Attempting to use flash builder beta 2 with beta 1 sdk

Hi,
I'm running into a few issues migrating a project I've started in Flash Builder Beta 1.
The biggest mistake I probably made was uninstalling Beta 1 and I can't seem to find where to re-download it. Is it available somewhere?
It would not be necessary except for the fact that I'm catching errors trying to use Flash Builder Beta 2 with the 4.0.0.7219 sdk.
When I set my compiler to use the beta 1 sdk, Flash Builder first throws an internal build error. Then I can't return to properties > flex compiler, getting a "could not accept changes error." Below is the log output.
I plan to migrate my project to Beta 2, but would love to do it in a separate workspace...
Any help, suggestions much appreciated!
Seth
Here's what's in my log:
!ENTRY org.eclipse.ui 4 0 2009-10-07 10:15:14.268
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NoClassDefFoundError: flex2/tools/oem/OEMException$CircularLibraryDependencyException
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
    at java.lang.Class.getConstructor0(Class.java:2671)
    at java.lang.Class.newInstance0(Class.java:321)
    at java.lang.Class.newInstance(Class.java:303)
    at com.adobe.flexbuilder.project.sdks.FlexSDK.createSDKDependentImplementation(FlexSDK.java: 846)
    at com.adobe.flexbuilder.project.sdks.FlexSDK.createSDKDependentImplementation(FlexSDK.java: 831)
    at com.adobe.flexbuilder.project.actionscript.internal.ActionScriptProjectSettings.computeCo mpilerLibraryPath(ActionScriptProjectSettings.java:1249)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.applySettings(ASBuilder.java:3 20)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.setup(ASApplication Builder.java:67)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.setup(ASItemBuilder.java:5 4)
    at com.adobe.flexbuilder.project.compiler.BuilderFactory.createBuilder(BuilderFactory.java:8 0)
    at com.adobe.flexbuilder.project.compiler.BuilderFactory.createCompilerArgumentValidator(Bui lderFactory.java:64)
    at com.adobe.flexbuilder.project.ui.properties.CompilerPropertyPage.validateCompilerArgument s(CompilerPropertyPage.java:792)
    at com.adobe.flexbuilder.project.ui.properties.CompilerPropertyPage.validate(CompilerPropert yPage.java:929)
    at com.adobe.flexbuilder.project.ui.properties.CompilerPropertyPage.access$4(CompilerPropert yPage.java:921)
    at com.adobe.flexbuilder.project.ui.properties.CompilerPropertyPage$4.modifyText(CompilerPro pertyPage.java:674)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1561)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1585)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1566)
    at org.eclipse.swt.widgets.Text.sendModifyEvent(Text.java:1769)
    at org.eclipse.swt.widgets.Text.setText(Text.java:2230)
    at com.adobe.flexbuilder.project.ui.properties.CompilerPropertyPage.copyVersionIntoEditBoxes (CompilerPropertyPage.java:693)
    at com.adobe.flexbuilder.project.ui.properties.CompilerPropertyPage.updateFlashPlayerOptions (CompilerPropertyPage.java:652)
    at com.adobe.flexbuilder.project.ui.properties.CompilerPropertyPage.update(CompilerPropertyP age.java:910)
    at java.util.Observable.notifyObservers(Observable.java:142)
    at java.util.Observable.notifyObservers(Observable.java:98)
    at com.adobe.flexide.editorcore.ui.sdks.FlexSDKChooserControl$2.widgetSelected(FlexSDKChoose rControl.java:665)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1561)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1585)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1570)
    at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1360)
    at org.eclipse.swt.widgets.Link.sendMouseEvent(Link.java:639)
    at org.eclipse.swt.widgets.Control.sendMouseEvent(Control.java:2978)
    at org.eclipse.swt.widgets.Control.sendTrackEvents(Control.java:3073)
    at org.eclipse.swt.widgets.Control.kEventControlTrack(Control.java:2104)
    at org.eclipse.swt.widgets.Widget.controlProc(Widget.java:375)
    at org.eclipse.swt.widgets.Display.controlProc(Display.java:862)
    at org.eclipse.swt.internal.carbon.OS.SendEventToEventTarget(Native Method)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3051)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
    at org.eclipse.jface.window.Window.open(Window.java:801)
    at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:157)
    at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionI tem.java:583)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
    at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java :411)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1561)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1585)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1570)
    at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1360)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3482)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3068)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

Hello,
I reproduced your issue exactly as you stated. Unfortunately, it doesn't look like FB Beta 1 is publicly available. To get out of the broken state, you can go to your workspace preferences (not project properties) and under Flash Builder > Installed Flex SDKS, switch back to the 4.0 Beta 2 SDK that came with Builder.
I am going to ask around to see what the problem might be, as I am unfamiliar with the code that is causing this. There may or may not be a workaround, but regardless, I think we'd recommend that you upgrade your project from Beta 1 SDK to Beta 2.
Thanks,
Rob Brambley
Computer Scientist, Flash Builder

Workaround for using the latest nightly SDK 4.0 builds with Flash Builder Beta 2

The latest builds of SDK 4.0 have been updated in preparation for including playerglobal.swc for Flash Player 10.1. Flash Builder Beta 2 can not find playerglobal.swc due to the addition of the {targetPlayerMinorVersion} variable found in the flex-config.xml file.
When using recent nightly SDKs with Flash Builder Beta 2, please modify them as follows:
1) Rename the folder <nightly sdk location>/frameworks/libs/player/10.0 to "10"
2) Edit the file <nightly sdk location>/frameworks/flex-config.xml and remove ".{targetPlayerMinorVersion}" and save
When you restart Flash Builder, we will now find a correct location for playerglobal.swc, allowing for code hints and many other features to work properly.
Jason San Jose
Quality Engineer, Flash Builder

Bump.
As people continue to have problems with the nightly SDK 4 builds and Flash Builder Beta 2, please remember to use the workaround described at the top of this thread. Also see http://blogs.adobe.com/jasonsj/2010/02/workaround_for_using_the_latest_nightly_sdk_40_buil ds_with_flash_builder_beta_2.html.
Jason San Jose
Quality Engineer, Flash Builder

How to download Flash Builder beta on a bad connection?

I'm on a slow, unstable connection and 1gb is pretty hard to get without stalling and resuming multiple times, but resuming doesn't seem to work in labs for some reason - maybe my session times out? I usually use Free Download Manager to handle big files like this, but the security on labs downloads prevents me from using a download helper. Other Adobe software has a nice download program, but not the betas.
I'm specifically trying to get the Windows 64 bit Flash Builder with monacle for game development. I can't find a torrent for it (torrents also work beautifully on my crappy connection). I guess this is more a suggestion to Adobe labs - please put aside your security concerns and make it easier for us to download these huge files!

I use free manager download, but the link provided for flashbuilder does not work with it. I used "DownThemAll" plugin for firefox, it downloaded 75% but now the link to the flashbuilder 4.7 game edition (since 8th oct.2012) does not work at all for 2 days in a row, so I can't download it anyway.

Flash Builder Beta 2 locale en_GB problems ?

Hi
I have installed FB B2 and created a project but the application produces an error even before I've complied the app, the message is as follows
unable to open 'C:\Program Files\Adobe\Adobe Flash Builder Plug-in Beta 2\sdks\4.0.0\frameworks\locale\en_GB'
I can change the locale under Flex Complier to en_US and this sorts this error. But then the following error appears:
unable to open 'C:\Program Files\Adobe\Adobe Flash Builder Plug-in Beta 2\eclipse\plugins\com.adobe.flexbuilder.dcrad.nl1_4.0.0.253292\nl\en_GB\dcradSwcs\4.0\loc ale'
I have no idea what to do now, why has the en_GB locale been removed in FB B2 ??
Any help would be greatfully accepted
PS I have tried build 10485 of the SDK and get the same result.
Regards
Chris

Hi Chris,
Yes, it was a type. I meant the locale that FB uses as default on my PC: es_ES.
The steps to reproduce this ( using FB beta2 + LCDS3_beta3.war )
1) New Flex project "foobar" with J2EE server
2) Use tomcat 6.0.18 and lcds3_beta3.war
3) Finish
4) I add the project to my Tomcat instance
5) Build project and "boom":
Description Resource Path Location Type
unable to open W:\PATH_TO_WS\foobar\WebContent\WEB-INF\flex\locale\es_ES
Then, I go to my FB_beta2 installation and :
6) copylocale en_US es_ES
Then I copy the new brand es_ES locale into W:\PATH_TO_WS\foobar\WebContent\WEB-INF\flex\locale and I try to build the project again:
7) Build the project
I get something like :
Description Resource Path Location Type
unable to open 'C:\Archivos de programa\Adobe\Adobe Flash Builder Plug-in Beta
2\eclipse\plugins\com.adobe.flexbuilder.dcrad.nl1_4.0.0.253292\nl\es_ES\dcradSwcs\4.0\loca le' foobar Unknown Flex Problem
I get the feeling there is something that is breaking the project at the point Im adding the project to the Tomcat instance.
If you skip step 4) The project compiles successfully. As soon as you add the project to Tomcat, everything breaks.
What do you think?
A.

Flex and Flash Builder Beta Feedback Survey

Hey guys,
Please take 15 minutes to give feedback on the beta releases here. Your input is greatly appreciated. Please also pass this along to other individuals who might be using the betas.
Kind regards,
Vera

Hi Glenn,
I updated the link yesterday afternoon, but for some folks it seems to still be going to the old survey. I'll put a redirect on the old survey, but please try going to the survey here.
Vera

Flash Builder Beta 2 won't install

Hey, the installer is saying that "the version of this file is not compatible with the version of windows you're running". I'm running windows vista 64 bit, but have installed plenty of 32 bit apps just fine. I was able to install beta 1 just fine. I started the install process for beta 1 again, and it seems to start OK (though I don't want to continue and run the install of beta 1 over my current install).
Did the labs team overlook something in the installer in this round? Any workarounds I can use?
thanks

Yes i understand it might conflict, however, it did not conflict with beta 1. Do you or anyone else know if they did something in beta 2 that conflicts with cfEclipse? I'd hate to uninstall cfEclipse, install cfBuilder beta 2, and it still not work.
If nobody has any other ideas, i'll try this approach...then come January, i'll probably have to install cfEclipse back till we get the full blown cfBuilder.
thanks for the help
dan

Automation swcs missing from Flash Builder Beta

Hi,
I just noticed that automation swc files are missing in the Beta while they were present in Gumbo Preview. Does anyone know how to obtain these files? Is it perhaps OK to just copy these from earlier Gumbo installation?
Thanks,
TN.

Hello TN,
Did you refer to http://labs.stage.adobe.com/wiki/index.php/Flash_Builder_4:Release_Notes#Install_and_Confi gure_Flex_and_AIR_Automated_Testing?
Did you check the /frameworks/libs/automation directory for SDK4?
Thanks
Arijit

Flash Builder Beta 2 output folder issues

I have a project that was created in FB Beta were everything was working fine; just updated to FB Beta 2 (uninstalled FB Beta). With the existing project from FB Beta, I had to completely reset it up in FB Beta 2 (Data/Services, gateway.php, amf-config.ini, etc.). The problem is in the Project's properties output folder FB keeps setting it to -> bin; in setting up the project I specified bin-debug, in FB Beta I was using bin-debug, if I click on restore defaults it sets bin-debug, but when I go back to properties it's back to bin. I've never used bin in the past. I've also had where FB creates a bin folder to put the output in (this is inconsistent) and when it does my .php files that are in the services folder are deleted/removed. Pictures to describe are below.
I select Restore Defaults / or manually type in bin-debug/ also this is how the project was created
I go back to the projects properties and get this

Thanks for the reply David.
when you change the folder back to bin-debug does the package explorer update to indicate the change has been made ?
Every time that I go into the projects preference under the output folder it always shows bin, but it inconsistently removes bin-debug and creates a bin folder and removes bin-debug. Every time that I'm in properties I always make sure that I save with bin-debug set, so package explorer does show bin-debug.
Also have you tried to manually name the output path outside of Flashbuilder then edit the actionscriptproperties file to to new path.
I've always used bin-debug so I didn't have to manually name; actionscriptproperties does show bin-debug also.
I don't know if you wanted me to try a new folder to see what happens? I haven't, I'd rather figure out why bin is always set.
Thanks for the help and the reply,
John

Difference between flash builder beta and flash builder beta 2 webservice.

hey guys... got a quick weird question, im using a lot of webservices, and i immidiately noticed the new thing in the interospection wizard, there is a new field in the wizard called "Data type package", i was wondering what that field is exactly??
i never noticed anything like that in the previous versions of flex,
from my understanding it just sticks all the main components under "valueObjects"
Thanks in Advance

so let's say you have some php service and it returns a collection of objects through amf.
for example your php has something like:
$array = new array();
$car1 = new car();
$car1->year = 2009;
$car1->model = 'ford';
$car1 = new car();
$car1->year = 2005;
$car1->model = 'audi';
$array[] = $car1;
$array[] = $car2;
return $array;
well, when FB receives this data (when your return the config type) it will recognize that you're returning a collection of objects, specifically a collection of car objects that contain two properties (year:int and model:String).
FB will offer to generate the Flex car class for you and you can store this autogenerated class in your valueObject folder (or whatever folder you want).
does that answer your q??
- e

Flash Builder 4 - Beta / Design view sporadic at best

Okay, so I have installed the beta, and running through the Catalyst / Flash BUilder 4 tutorial, all is well, unitl i try to get the imprted fxp file to consistently display in the design mode. Not only that, but switching from code view to design view will break it just about 95% of the time, and then it will not display the created items that the tutorial has you put on them (i.e. the databinds to the names, etc etc).
Has anyone else experienced this? Other than a few little things like this, so far so good guys(ADOBE).
Thanks,
Craig Newroth

eh_adobe wrote:
Please be aware that using a newer SDK with Flash Builder Beta's Design View may have unpredictable results. I can't say specifically since I don't know what version you tried and what your document contained, but... let's pretend for a second that the SDK changed something in a component - its name, its package, or any method or properties in it. Design View was compiled with a specific version of the SDK, and would not know about that change, and so might not react very well to the document. Yes this is not ideal, but it's hard to avoid when the SDK is changing rapidly (at some point it will settle down, and this won't be an issue). We can look at ways to mitigate this.
I have had less unpredicatable results with recent builds of the SDK the latest being build 7988- I basically update from the svn trunk every 2-3 days look through the changes run the checkintests just to make sure all is ok then see what happens to be small testbed apps, I have been doing this for several months. I don't mind the IDE not dealing with the changes as long as it tells me why it can't. But the code should not break the IDE. Also i'm getting a little confused as some of the responses to some issues (not the design mode one) in this forum have suggested seeing what happens with updated SDK's.
Anyway I have reverted everything back to a standard FB4 install and the first thing that happened yet another new flaw in design mode rears its head, no errors but this time a visually definable issue. The component appears as a 1 dimension line in the top left hand corner of the design editor window, not even on the design view working canvas. Attached is a screen shot and the associated code that caused it. Please note the IDE didn't draw the big red ring around the visual glitch so thats one less bug to worry about.
     the app.
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/halo" minWidth="1024" minHeight="768">
     <s:HSlider x="50" y="50" width="200" height="30" skinClass="skins.HSliderSkin"/>
</s:Application>
     skin part A.
<?xml version="1.0" encoding="utf-8"?>


<s:SparkSkin xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark"
       minHeight="11" minWidth="100"
       alpha.disabled="0.5">
    <fx:Metadata>
    <![CDATA[
      * @copy spark.skins.default.ApplicationSkin#hostComponent
         [HostComponent("spark.components.HSlider")]
    ]]>
    </fx:Metadata>
    <fx:Script>
        /* Define the skin elements that should not be colorized.
           For slider, the skin itself is colorized but the individual parts are not. */
        static private const exclusions:Array = ["track", "thumb"];
      * @copy spark.skins.SparkSkin#colorizeExclusions
        override public function get colorizeExclusions():Array {return exclusions;}
    </fx:Script>
    <s:states>
         <s:State name="normal" />
         <s:State name="disabled" />
    </s:states>
    <fx:Declarations>
     
        <fx:Component id="dataTip">
            <s:MXMLComponent minHeight="24" minWidth="40" y="-34">
                <s:Rect top="0" left="0" right="0" bottom="0">
                         <s:fill>
                              <s:SolidColor color="0x000000" alpha=".9"/>
                         </s:fill>
                         <s:filters>
                             <s:DropShadowFilter angle="90" color="0x999999" distance="3"/>
                        </s:filters>
                    </s:Rect>
                    <s:SimpleText id="labelElement" text="{data}"
                         horizontalCenter="0" verticalCenter="1"
                         left="5" right="5" top="5" bottom="5"
                         textAlign="center" verticalAlign="middle"
                         fontWeight="normal" color="white" fontSize="11">
                </s:SimpleText>
            </s:MXMLComponent>
        </fx:Component>
     </fx:Declarations>
    
    <s:Button id="track" left="0" right="0" top="0" bottom="0"
              skinClass="skins.HSliderTrackSkin"/>
    
    <s:Button id="thumb" top="1" bottom="1" width="{hostComponent.height*1.5}" skinClass="skins.HSliderThumbSkin"/>
</s:SparkSkin>
     Skin Part B
<?xml version="1.0" encoding="utf-8"?>


<s:SparkSkin xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark">
    <fx:Metadata>
    <![CDATA[
      * @copy spark.skins.default.ApplicationSkin#hostComponent
         [HostComponent("spark.components.Button")]
    ]]>
    </fx:Metadata>
    <s:states>
        <s:State name="up" />
        <s:State name="over" />
        <s:State name="down" />
        <s:State name="disabled" />
    </s:states>
    
    <s:Rect left="0" right="0" top="0" bottom="0" radiusX="{hostComponent.height/2}" radiusY="{hostComponent.height/2}">
        <s:fill>
            <s:SolidColor color="0x4F4F4F" />
        </s:fill>
    </s:Rect>
     
     <s:Rect left="0.5" right="0.5" top="0.5" bottom="0.5" radiusX="{hostComponent.height/2}" radiusY="{hostComponent.height/2}">
          <s:stroke>
               <s:LinearGradientStroke rotation="90" weight="1">
                    <s:GradientEntry color="0x000000" alpha="0" />
                    <s:GradientEntry color="0x000000" alpha="0.33" />
               </s:LinearGradientStroke>
          </s:stroke>
          <s:fill>
               <s:LinearGradient rotation="90">
                    <s:GradientEntry color="0xFFFFFF"
                                      color.over="0xE5E5E5"
                                      color.down="0x999999" />
                    <s:GradientEntry color="0xD8D8D8"
                                      color.over="0x7D7D7D"
                                      color.down="0x555555" />
               </s:LinearGradient>
          </s:fill>
     </s:Rect>
     
</s:SparkSkin>
     Skin Part C
<?xml version="1.0" encoding="utf-8"?>


<s:SparkSkin xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark">
    <fx:Metadata>
    <![CDATA[
      * @copy spark.skins.default.ApplicationSkin#hostComponent
         [HostComponent("spark.components.Button")]
    ]]>
    </fx:Metadata>
    <s:states>
        <s:State name="up" />
        <s:State name="down" />
        <s:State name="over" />
        <s:State name="disabled" />
    </s:states>
     
    <s:Rect left="-1" right="-1" top="0" bottom="-1" radiusX="{hostComponent.height/2}" radiusY="{hostComponent.height/2}">
        <s:fill>
            <s:LinearGradient rotation="90" >
                 <s:GradientEntry color="0x000000" alpha="0.55" />
                 <s:GradientEntry color="0xFFFFFF" alpha="0.55" ratio="0.8" />
            </s:LinearGradient>
        </s:fill>
    </s:Rect>
    
    <s:Rect left="0" right="0" top="1" bottom="0" radiusX="{hostComponent.height/2}" radiusY="{hostComponent.height/2}">
        <s:fill>
            <s:SolidColor color="0xCACACA" />
        </s:fill>
    </s:Rect>
     
     <s:Rect left="0" right="0" top="0" bottom="0" radiusX="{hostComponent.height/2}" radiusY="{hostComponent.height/2}">
          <s:fill>
               <s:SolidColor alpha="0"/>
          </s:fill>
     </s:Rect>
</s:SparkSkin>

Debug icon gone from Flash Builder 4 Beta 2

Gentlepersons,
In previous versions of Flex Builder (including Flash Builder Beta 1) there was a handy debugger-launcher icon in the upper-left corner of Flash Builder's main window. It looked like a green bug. That icon is missing from Flash Builder Beta 2 (or at least, it ain't there in my just-installed copy of Flash Builder Beta 2).
How do I get that handy icon back?
Thanks! :-)
Jim Plamondon

If you right-click the toolbar you can get to the 'Customize perspective' dialog.
From there make sure commands >> flash run/debug option is checked.
Oddly, there is no "Flash run/debug" option to check.
Please see the attached picture.
Note that I am running Flash Builder Beta 2 (build 253292) on Eclipse 3.4.2 (build M20090211-1700) on Max OS X (version 10.5.8).
Thanks!
--- Jim

Changes from Flash Builder 4 Beta 2 to Flash Builder 4 Premium

I have a Flex app that started in Flash Builder 4 Beta 2 and when the beta expired, we bought Flash Builder 4 Premium.
Before, when programmatically changing the selected index of a Spark DropDownList, the change handler was called, so in cases where I didn't want that to happen, I had to remove the event listener and add it again after a small setTimeout.
In the new version, it seems that when I change the selected index programmatically, the change handler is not called, so if I want it to be called, I have to call it manually, which is also fine. I just want to confirm that this different behavior was an actual change that was made and isn't caused by some kind of other change I made to my code.
Is there a list of feature changes from the beta to the release version? Thanks!
-Travis

If you right-click the toolbar you can get to the 'Customize perspective' dialog.
From there make sure commands >> flash run/debug option is checked.
Oddly, there is no "Flash run/debug" option to check.
Please see the attached picture.
Note that I am running Flash Builder Beta 2 (build 253292) on Eclipse 3.4.2 (build M20090211-1700) on Max OS X (version 10.5.8).
Thanks!
--- Jim

Upgrade from Flash Builder 4 Beta 2 to Flash Builder 4 Premium

Hi guys,
How do i just upgrade from Beta 2 to premium? Does the install utility for Premium take care of it? or do I need to some how uninstall and install Flash Builder 4 premium? I currently have Flash Builder 4 Beta 2 installed as a plugin to my current Eclipse IDE, and I do not want to start all over again as there are quite of few settings/plugins already installed in Eclipse that I want to keep, and not waste more time duplicating the whole process.
Thanks
Jay

If you right-click the toolbar you can get to the 'Customize perspective' dialog.
From there make sure commands >> flash run/debug option is checked.
Oddly, there is no "Flash run/debug" option to check.
Please see the attached picture.
Note that I am running Flash Builder Beta 2 (build 253292) on Eclipse 3.4.2 (build M20090211-1700) on Max OS X (version 10.5.8).
Thanks!
--- Jim

Flash Builder 4 Beta 2

Similar Messages

Maybe you are looking for