Flash Builder, Design area resolution gone?...

Hi, maybe is a simple one but trying with no luck in the Flash Builder Trial, looking in the documentation,
cannot see where is the design area, in flex 3 was easy lets say know how the components looked like
in 2000x1000 for example just putting there the value.
where is this located in Flash Builder
thanks.

Nope, he's right, it's not there for me either.
This is what he is talking about. I do anticipate this being an annoyance for me once I switch to FB4 at work.
In this case, just a VBox container with width/height both set to 100%. The main Application container had no w/h set, but I don't imagine that mattering.

Similar Messages

Flash Builder Design view

Hi all,
I have also an issue when trying to view a component in the Flash Builder 4 Design View (running on Eclipse 3.5 SP-2).
The design view does not open and I get an error message. When I look into the Eclipse "Error Log" view I see the following stack trace and session data as shown below...
I appreciate any hint what is going wrong here...
Thanks!
Paul
java.lang.NullPointerException
at com.adobe.flexbuilder.mxml.editor.design.internal.MXMLDesignView4Commander.getDesignSurfa ce(MXMLDesignView4Commander.java:61)
at com.adobe.flexbuilder.mxml.editor.design.internal.MXMLDesignView4Commander.setFrameRate(M XMLDesignView4Commander.java:124)
at com.adobe.flexbuilder.designview.DesignViewPart$DesignShellListener.shellActivated(Design ViewPart.java:353)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:82)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1008)
at org.eclipse.swt.widgets.Decorations.WM_ACTIVATE(Decorations.java:1615)
at org.eclipse.swt.widgets.Shell.WM_ACTIVATE(Shell.java:2086)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3943)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1578)
at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2010)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4619)
at org.eclipse.swt.internal.win32.OS.MessageBoxW(Native Method)
at org.eclipse.swt.internal.win32.OS.MessageBox(OS.java:2892)
at org.eclipse.swt.widgets.MessageBox.open(MessageBox.java:207)
at com.adobe.flexbuilder.mxml.editor.design.MXMLDesignPart.startDesignView(MXMLDesignPart.ja va:208)
at com.adobe.flexbuilder.mxml.editor.design.MXMLDesignPart.<init>(MXMLDesignPart.java:68)
at com.adobe.flexbuilder.mxml.editor.design.MXMLDesignEditor.initializePlayer(MXMLDesignEdit or.java:1411)
at com.adobe.flexbuilder.mxml.editor.design.MXMLDesignEditor.initializeDesignView(MXMLDesign Editor.java:1576)
at com.adobe.flexbuilder.mxml.editor.design.MXMLDesignEditor.setFocus(MXMLDesignEditor.java: 1736)
at org.eclipse.ui.part.MultiPageEditorPart.setFocus(MultiPageEditorPart.java:1119)
at org.eclipse.ui.part.MultiPageEditorPart.setFocus(MultiPageEditorPart.java:1101)
at com.adobe.flexbuilder.mxml.editor.MXMLEditor.setFocusIfActive(MXMLEditor.java:674)
at com.adobe.flexbuilder.mxml.editor.MXMLEditor.activateDesignEditor(MXMLEditor.java:638)
at com.adobe.flexbuilder.mxml.editor.MXMLEditor.activateDesignEditor(MXMLEditor.java:621)
at com.adobe.flexbuilder.mxml.editor.MXMLEditor.pageChange(MXMLEditor.java:489)
at com.adobe.flexbuilder.editorcore.editor.CodeAndDesignEditor.setActivePage(CodeAndDesignEd itor.java:684)
at com.adobe.flexbuilder.mxml.editor.MXMLEditor.setActivePage(MXMLEditor.java:544)
at com.adobe.flexbuilder.editorcore.editor.CodeAndDesignEditor$1.clicked(CodeAndDesignEditor .java:454)
at com.adobe.flexide.editorcore.ui.controls.ButtonBar.clicked(ButtonBar.java:289)
at com.adobe.flexide.editorcore.ui.controls.AbstractButton.sendClickEvent(AbstractButton.jav a:41)
at com.adobe.flexide.editorcore.ui.controls.ToggleButton.handleChange(ToggleButton.java:79)
at com.adobe.flexide.editorcore.ui.controls.ToggleButton.mouseDown(ToggleButton.java:66)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
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:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Session Data:
eclipse.buildId=unknown
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product

I have the same problem, and can not get answer.
Today I try to use a standalone version, it‘s running good.
So, it may tell us that the problem may be only happen in the situation that using a plugin version FB4 and running on win 7.
If you just need flex and do not use j2ee, I suggest you using a standalone FB.

Flash Builder Design Mode: sea of grey w/ blue boxes...why?

Gentlepersons,
I added various controls to a tiny test application's MXML file in Flash Builder (Gumbo)'s design mode, ran the app, and all was well. Then I opened the file in design mode again, and all I could see was a sea of grey, with no controls visible. When I clicked on a control, a blue border would appear around it, but no other sign of the control was visible. I could drag new controls onto the sea of grey, but they were invisible too.
I have attached a screen shot of the "sea of grey," named "SeaOfGrey.tiff".
What the heck is this? Is there some "sea of grey" mode that I accidentally got into? How do I get out of it?
Thanks! :-)
Jim

Flash Builder - Design View - can't resize/move objects anymore.

So, I've downloaded the 60 day trial of Flash Builder 4. I've been working with it for about 2 days and everything has been going fine. However, for some unknown reason, my design view panel just suddenly stopped working properly. I see the components (and the gray outlines of my containers) I'm working with, but when I try to click on them, I do not get that blue resizing outline with the handles. I see the properties panel change when I click different components, but I get no outline. So, I can no longer resize in this view. I also can't move components/containers around. I can only click on them and watch the properties panel change. I do not believe I've hit any sort of option in the menus. I closed the application and started it up again with the same result. I even rebooted my machine and tried again. As of right now, this problem seems to be permanent. Any ideas? Thanks for your time.

I would recommend you post on the Flash Builder forum: http://forums.adobe.com/community/flash_builder

Flash Builder Design Issue!

This is a very annoying issue that im having. I have had Flash Builder 4 installed since the launch of CS5 and just started to use it. The problem im having is with the designer when constraining an object to the corners of the document.
Whats happens in the object goes off the canvas when constraing it to the right, left and top.
Here is an image of what im talking about.
http://papillongrafix.com/fb.png
whats happening and how can i fix it?

The issue does not seem to be present in FB 4.5 so i cannot give exact reason of the issue. Anyway you can see that the right alignment value is showing negative number in the text box. So you can adjust the value to a positive number which is suitable for your requirement

Flash Builder Design Preview Not Working With Catalyst Objects On Stage

Hi there,
I'm working with a flash catalyst component from a flex project library, and it will not preview in desing mode. Anyone ever run into this? It seems that it may be a memory issue as the custom components themselves will preview, but now a bunch of custom components all displayed in a view.
Any insight would be greatly appreciated! For now I'm back to guessing x & y coords...

Going to answer my own thread here. This issue doesn't seem to be with Flash Builder, I think the issue lies in the browser not being able to register the button modes, namely Firefox 4. I've seen it happen in other browsers too, like Chrome, where the fix is to embed the swf as param.wmode = "window". Hope this helps someone out.

Flash Builder Design Mode Bug Workaround (!!!)

I've been fighting this annoyance since FB4 came out, and while I still don't think that custom/embedded fonts in design view are fixed by this, I've been able to reproduce this "fix" (workaround) to get design view to show fonts/theme correctly under some very specific circumstances on two separate PCs.
If anyone from Adobe sees this I'd like to know whether this sounds familiar or is possibly logged as a bug already somewhere in JIRA.. if not I could probably do that as long as it won't be a wasted effort.
The problem:
You're using a Halo theme but certain CSS settings (specifically and possibly limited to FONTS) don't work properly in design view even though they work fine in Flash. Essentially this makes design view practically useless since choice of font family, size, and weight can effect component sizing if you aren't hard-coding component sizes (ugh)... ruining your efforts to use design view for UI design if your UI has any level of complexity (or uses absolute positioning at all).
The specific circumstances seem to be:
You're using the Halo theme (you have no special 'skinning' requirements and want Halo defaults w/only CSS customizations)
You've upgraded a Flex 3 project to Flex 4 SDK (not sure if this is needed to reproduce the issue)
Using a regular non-embedded font (embedded fonts still do crap out, but even this 'workaround' doesn't fix that problem)
You're using swc library files such as the Swiz lib, Mate, Flexlib, etc. (I think it's ANY swc, not specific to any one)
This may also only apply when using an "mx only" project (no Spark), since we're using Halo here
The two part fix (as far as I can tell you need BOTH before design view works correctly):
In .actionScriptProperties, add the following bolded line after the compiler tag like so:
</compiler>
<theme themeIsDefault="false" themeIsSDK="true" themeLocation="${SDK_THEMES_DIR}/frameworks/themes/Halo"/>
<applications>
(I think this may only apply to 'upgraded' projects, as the line does seem to be present in newly created FB4 Halo projects. My guess is that an "upgraded" project should have such a line added, but doesn't get it due to an oversight/bug.)
The somewhat painful, and definitely odd part. Remove all your SWC library files from /libs. Grab the source code for the libraries and drop them into your project's /src folder as if you'd written them yourself. (This may require some research and knowledge on special requirements to build the libs, such as with Swiz's compiler metadata compiler settings which you need to put into your project's settings.) After you get things set up right and the project compiles again, doing a refresh of design view should finally give you proper looking Halo controls and fonts so they look identical to the Flash runtime view.
Why this works, I've no idea. I suspect it has something to do with that stupid and annoying (and supposedly 'harmless') design mode warning message you get when you include a library like Swiz or Mate in your project. (Design mode could not load xxxxxxxxxxxxx.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)) - this warning doesn't break your application, people seem to think it's just a harmless warning..but is it breaking design view?
If anyone has any idea what's going on here, why this 'fixes' the problem (a better work around), or has any other insight I'd love to hear it. The combo of needing to do two things (in my specific case) to fix the problem really made this a ROYAL PAIN, I still can't believe I found it.

Hi Fernando, sorry for the delayed response. CSS Design Mode is not available for Flex 4 projects, but it is still available in Flex 3 projects. The reason for this is that designing components in Flex 4 is often a lot different, since it relies highly on the new spark skinning architecture. There is, however, an Appearance panel available in design view which supplies a set of the main inheriting styles. Setting these styles in the Appearance panel will result in assigning values to a global style selector.
I hope this helps,
Rob

How to make colors look same in illustrator and Flash Builder

We had a designer build out our UI using Adobe illustrator, and then tried to replicate the same hex color and alpha codes in Flash Builder- colors are looking very different on the same machine
We have used basic web colors but the problem persists. Any pointers on why this could happen?

Thanks Joan... we managed to figure out the cause to a large extent- problem
arisen by the way the layers were built in Illustrator vs Flashbuilder. I
still have the following questions, that we are currently handling via a
workaround
a) when I try to skin the container using SkinnableContainer, the skin
doesn't take effect- but works, when I use same skin with a BorderContainer.
Any idea of why this is so?
The code used is as below
<s:BorderContainer id="Banner" height="15%" width="100%"
skinClass="mySkins.newskin1">
<mx:Image id ="logo" source="assets/graphics/logo.png"
x="{0.018Banner.width}" y ="{.09Banner.height}"
height="{Banner.height*0.7}" maintainAspectRatio="true"
width="{Banner.width*0.085}"/>
<s:Label x="{0.065Banner.width }" y ="{.293Banner.height}"
fontFamily="Copperplate" fontSize="34" kerning="on" color="#666666"
text="EUREKA WORLD"/>
<s:Label x="{.88Banner.width}" y ="{.293Banner.height}" fontFamily="Arial"
fontSize="14" kerning="on" color="#666666" text="Help | Log Out"/>
<s:Label x="{.865Banner.width}" y ="{.45Banner.height}" fontFamily="Arial
Bold" fontSize="18" kerning="on" color="#666666" text="Welcome Gauri"/>
</s:BorderContainer>
Skin attached
b) we are trying to replicate the design from Illustrator(exported in fxg
format) and replicate in FlashBuilder. We would like to name the objects
meaningfully so we can connect the front-end with names in the fxg code.
Currently we see an objID. How do we name objects in Illustrator?
c) When we use a mx:vbox within a repeater to display contents of an array,
we had trouble skinning this for background color- compromise we reached was
to have the background color in the mx:vbox with a skinclass for the border
and shadow
Regards

Trace() not working with embedded SWFs created with Flash Builder

I have just migrated to Flash Builder 4.5 with the 4.5.1 SDK.
I have an application that loads a lot of child SWFs into it - some of which are created with Flash, some are created with Flash Builder.
I am noticing now that my trace() statements that are called from within SWFs produced with Flash Builder that are loading as child SWFs into my main SWF are NOT appearing. However, trace() statements called from within SWFs produced with Flash that are loading as child SWFs into my main SWF ARE appearing.
This is an extremely major problem and has short-circuited my debugging/development.
Any recommendations, workarounds, or suggestions?

If the child SWFs were created by performing an "Export Release Build", then trace() statements would be omitted.
You can control this by setting the -omit-trace-statements compiler argument (in Project properties -> Flex Compiler -> Additional Compiler Arguments).
-Anirudh

Adobe Flash Builder 4.5 Premium Edition

I need a link to download the above captioned version of Flash Builder.

iMacs are great machines. The Adobe CS suite will work on any new or older iMac. iMacs have great video cards as well. I would suggest that once you buy the iMac, add more memory. Buying it directly from Apple is quite expensive but places like Other World Computing sell excellent memory at great prices. I don't work for them, but I am a long time customer. I love my iMac. The screen is just fabulous.

Simple Flip Book in Flash Builder

I built this simple Flip Book in Flash Builder starting with Flash Catalyst...I guess the big issue is that when I make these components...they work well at z=0, but when I change z things don't work...why? Definitely needs a fix...everything is below (source, demo, book blog, video):
Source: http://lv3d.googlecode.com/files/FlipBook.zip
Demo: http://www.professionalpapervision.com/demos/flipbook/
Book Blog
Video

Hi,
After thinking about your solution and doing some testing I have two comments...
(1) I'm concerned that your change may not be congruent with Flash Catalyst and its logical flow, and
(2) The solution did not solve the problem. I fear I have not explained myself well. So here is a video on the problem...
http://www.youtube.com/watch?v=wg-pUX6lpuM
And if anyone wants to know how to install a new SDK in Flash Builder. Here is a video on that too
http://www.youtube.com/watch?v=OhHxPK_p2jQ
Best Regards,
Mike
From: [email protected]
To: [email protected]
Subject: RE: Simple Flip Book in Flash Builder
Date: Sat, 6 Feb 2010 15:51:36 +0000
Thanks so much I really appreciate the comment...I'm digesting and testing it!!!
From a PV3D and Away3D perspective...one of the difficulties I've run into is that in Flash Builder there are three ways to do 3D...MXML (from Flash Catalyst), Matrix Manipulation using update display, and dot syntax methods (hey which one do I use?). It's really difficult to get the same visual effects in Flash Builder that you get in PV3D and Away3D, but in doing so you don't have to run your processor so hard and can do more. And you can't beat how easy it is to work with Flash Catalyst...you can develop 3D 10 times faster...
That means I'm taking my lumps while things are being repaired and developed. But that's the business...thanks again for your comments.
Just one more comment...I've built the data-driven case of the book for 3 pages using FB data wizard:
Part 1: http://www.youtube.com/watch?v=WzKba9qyrp0
Part 2: http://www.youtube.com/watch?v=xz9htZXYZyU
Part 3: http://www.youtube.com/watch?v=_Nyeg4_zuXo
Part 4: http://www.youtube.com/watch?v=uG_uUIHSyqU
...in the multi-page case I will actually turn the pages into a particle system and treat the 3D a little differently...I'll take a real good look at your suggestions below then.
Best Regards,
Mike
Date: Fri, 5 Feb 2010 14:18:03 -0700
From: [email protected]
To: [email protected]
Subject: Simple Flip Book in Flash Builder
Mike,
Steven Shongrunden played around with your original FlipBook example and noticed that it doesn't work the same in the current builds as it did in Beta2. The problem is that we changed the behavior of the 3D effects recently, to fix this bug:
http://bugs.adobe.com/jira/browse/sdk-24993
Basically, 3D effects used to side-effect the 3D properties of objects and persist their changes on the objects after transitions were over. This is different from the way that the rest of the effects work, where we install the proper end-state values in the objects when transitions end.
This means that if you do a Rotate3D with angleYTo="180", that we'll do that rotation during the effect ... and then wipe out that change when the transition ends.
There are two workarounds for this situation. The first, which is the way to go in general and definitely for Catalyst users, is to have 2-sided objects. So instead of simply seeing the back of the front cover, the user would see the front of a completely different object (the inside cover page, if you like). Then the transition should rotate both objects (the cover to 180 and the inside object to 0), then make the old object disappear and the new object appear at the right times (like at 90 degrees). So when the values are restored to the front cover upon transition end they will not be visible because the object is not visible.
The workaround for coders is to actually tell the states the values that the object should have. So if you actually want to rotate the object around y, then set that information in the states so that we won't blow it away when the transition ends. In fact, you could even set it in the states and not in the effect and we'll run the transition automatically. This is really the best approach for state transitions in general: tell the states what values the objects should have, and tell the transitions what effects to run, then the effects will automatically figure out the values to animate from/to.
The trick with this workaround is that the 3D effects affect the post-layout properties by default, and setting those values is not as obvious as setting pre-layout properties on the object.
Here's an example of how to do this for the cover component:
     <components:frontCoverCustomComponent x="0" y="0" id="frontcovercustomcomponent1"   click="frontCoverCustomComponent_clickHandler()">
        <components:postLayoutTransformOffsets.State2>
            <s:TransformOffsets rotationY="180"/>
        </components:postLayoutTransformOffsets.State2>
    </components:frontCoverCustomComponent>
I added this code to your custom component (and left the transition code as-is) and it now works as expect. It's still a bit weird to see the back of a two-dimensional object, so using two objects for anything that you'll see flipped is still a good thing to do in any case (as someone else suggested on this thread).
Chet.
>

Stage Video Using Flash Builder 4.51

Hi,
I am using Flash Builder 4.51, and I cannot get StageVideo to run. My machine is capable of playing StageVideo as I tested the Big Buck Bunny example and saw the change when flicking between StageVideo and normal Video.
Flash Builder shows that the build that I have is 4.5.1.313231. All the tutorial examples I have seen are built using Flex Hero build 18623 which I believe is earlier. So my question is was StageVideo removed somehow when Flash Builder 4.5 and 4.51 were released?
If it should work on 4.5.1, can anybody give me some tips on what to check or provide some minimal code and instructions to get the expression stage.stageVideos.length to be something different to 0?
I have changed made sure the wrapper uses wmode="direct", I am using version 11 of the Flash Player, I have a parameter on the compiler for " -swf-version=11".
When I export the swf from Flash Builder to my web page I still can't get StageVideo to work either locally or on the server.
I've run out of ideas with this one.
Any ideas?

Hi Claudiu
I'm glad its working for you, that's encouraging.
I'm just trying to confirm that we are using the same setup. When you say you have installed the eclipse plugin, does that mean you install Flash Builder or are you using the Flex SDK through eclipse? I agree that FP11.2 is not the issue since StageVideo works if I run the Big Buck Bunny example.
Also, just to confirm we are talking about the same thing, if you create a new project in Flash Builder and put in the following two methods, are you able to get the "str" variable in the second method to show "Available". If so, what additional steps do you take after create project?
protected function application1_creationCompleteHandler(event:FlexEvent):void
this.systemManager.stage.addEventListener(StageVideoAvailabilityEvent.STAGE_VIDEO_AVAILAB ILITY, onStageVideoState);
private function onStageVideoState(event:StageVideoAvailabilityEvent):void
var str:String = event.availability;

Flash Builder 4 - design view - states basedOn + design area widget

Hello,
Since i updated my project from Flex 3 to Flash Builder (4), i have very annoying issues in the design area.
The one in Flex 3 was quite usefull, but the new version is not easy, and straight forward usable.
Here are the 3 issues:
- when i have states designed from another one, i use the basedOn mxml attribute, which was used in Flex 3 and still exist in SDK 4 states system.
But the designer view in Flash Builder don't take those basedOn properties in account!
What can i do? and is it a known bug?
- When i have at least one precific state, i must define a defautl state, in the new SDK. Ok, but in design view, i cant add a new component without making the change only for one state. I can only make the change for the default state, but it will not be taken in account for all the other states, like i can do in Flex 3.
What i want to be able to do this: making changes in design view without selecting ANY state.
Is it possible? How can i do?
- In flex 3, there were a design area widget to select the resolution used for the preview design.
It was very usefull when the application has very dynamic width and height.
In Flash Builder, this widget has been removed.
Why has it been removed? and how can i preview my mxml views wihtout changing width and height values?
Thanks.
Seb

The update has been improved in every other areas, so it is not that much important.
I just hope that the new release will fix that (as it has been answered to my post).
The only thing i don't like in new releases of FB is that when the architecture of SDK is aimed to seperate the work between design and code, they focused only on catalyst to create the tools to manipulate design, and they forgot to keep an easy way to do design app directly in FB (with the design view and the style properties of MXML in FB3). But i'm confident that they will give such a tool soon.
But for now, if you don't like the restriction of the new release, you can continue to work with Flex 3 for 0$! And even in Flex 4, you can create MX components for which the design view will work as before. The fact that tools can manage a mix between MX and Spark components is a great thing. It is up to you to choose which you need which its own advantages and drawbacks.
Xcode is real pain to use with outdated ergonomy. It is only usefull to code in Objective C which is another real pain to do.
XCode can be cheapper because all Apple products are quite expansive, so the software to create softwares for them can be much more cheapper.
And Apple get a good revenue share from AppStore, so again they can give a cheap soft to create apps. You also have to pay 100$ to be able to send app to appstore, in ly opinion the good price for XCode should be 0$, not even 80$!
Flash builder 4 is very stable, but if you don't like it, you can choose another tool. Main competitor has no designer at all!

"Design" section on Flash Builder. Where is it?

Where is the "design" section of Flash Builder?
I have the latest version 4.7 from my Adobe Cloud. One of the phone support giving me a call back couldn't connect to my computer to see my screen, and told me to download the 4.6 version instead... what??!!
I am stuck on "code" only mode in my Fb system and can't do anything. How do I find my "design" mode for Flash Builder?
Also..... The "Chat" support on Adobe doesn't seem to be working... Anybody of you is able to connect to "chat" with adobe?

Hi,
Ever since Flash Builder 4.7, they dropped Design View. That's why they told you to use Flash Builder 4.6 instead.
There are 3 Flash Builder alternatives:
The best Flash Builder alternative is FDT, but it does not support MXML Design View.
http://fdt.powerflasher.com/
The 2nd choice is IntelliJ IDEA, you can download a MXML Design View plugin, it's very cool.
http://www.jetbrains.com/idea/features/flex_ide.html
The 3rd choice is FlashDevelop, it's free and open sourced, but it's Windows only, and it does not support MXML Design View either.
http://www.flashdevelop.org/
DarkStone
2014-12-09

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>

Flash Builder, Design area resolution gone?...

Similar Messages

Maybe you are looking for