Create a flex 'design view'

Hi
is it possible to create a page using flex 3 which is similar to the design view in the flex builder.
essentially what we are planning to do is that we want to provide the user an ability to design a page.
Does flex provide the users the design view as a component that can be used in a page.
av.

You just go thorugh following links where you will find what you want:
http://www.flashchemist.com/?p=123
http://flex.org/software/components
http://fleksray.org/adobe_flex_components_en.html#popuptoolbar
http://fleksray.org/adobe_flex_components_en.html#Auto%20Complete
http://flexsamples.blogspot.com/
http://weblogs.macromedia.com/pent/archives/flex_solutions/index.html
http://flex.org/showcase/
http://www.adobe.com/devnet/flex/?navID=samples
http://examples.adobe.com/flex2/inproduct/sdk/explorer/explorer.html
Thanks.

Similar Messages

  • Unable to create Tables in design view

    One of the two problems I am having (the other will also be
    posted) is that I am no longer able to use Design View to Insert
    Tables at all - I get the following error message: (I made a
    printscreen of the error but not sure how to embed the picture in
    this post so here is the message verbatim).
    "While executing objectTag, the following JavaScript error(s)
    occured:
    At line 26 of file "Macintosh HD:Applications:Macromedia
    Dreaweaver 8:Configuration
    bjects:Common:Table.htm":
    Type Error: cmdDOM.parentWindow.createTableStr is not a
    function"
    I can create tables only if I type the html for them by hand
    into the code pane. The file that the error message references does
    exist, and appears to look fine (code-wise). I've also tried
    uninstalling and reinstalling DW8, removing and recreating the
    Configuration Folder as well as the site prefs and site definitions
    - nothing has cured this problem.
    I am using DW8 v. 8.0.2 on a Mac Quad G5 running OS X 10.4.6.
    I am positive that I did not have this problem, or any of the other
    current problems, with DW MX , and I installed DW8 as a stand-alone
    app so that I could still use MX if needed. This and the other
    problems don't occur with MX but I would really like to get them
    solved because 8 offers other benefits that I want to be able to
    use.
    I'm wondering if anyone else has had this problem and managed
    to find a fix for it.

    One of the two problems I am having (the other will also be
    posted) is that I am no longer able to use Design View to Insert
    Tables at all - I get the following error message: (I made a
    printscreen of the error but not sure how to embed the picture in
    this post so here is the message verbatim).
    "While executing objectTag, the following JavaScript error(s)
    occured:
    At line 26 of file "Macintosh HD:Applications:Macromedia
    Dreaweaver 8:Configuration
    bjects:Common:Table.htm":
    Type Error: cmdDOM.parentWindow.createTableStr is not a
    function"
    I can create tables only if I type the html for them by hand
    into the code pane. The file that the error message references does
    exist, and appears to look fine (code-wise). I've also tried
    uninstalling and reinstalling DW8, removing and recreating the
    Configuration Folder as well as the site prefs and site definitions
    - nothing has cured this problem.
    I am using DW8 v. 8.0.2 on a Mac Quad G5 running OS X 10.4.6.
    I am positive that I did not have this problem, or any of the other
    current problems, with DW MX , and I installed DW8 as a stand-alone
    app so that I could still use MX if needed. This and the other
    problems don't occur with MX but I would really like to get them
    solved because 8 offers other benefits that I want to be able to
    use.
    I'm wondering if anyone else has had this problem and managed
    to find a fix for it.

  • NetBeans - Creating TreeNodes in design view

    Not 100% sure if this is the right spot...
    I've always enjoyed netbeans for creating Java applications not only for it's syntax highlighting, and auto-completion, but for it's design view. It's a lovely area where you can design the GUI instead of coding it, which makes the process of creating applications very easy.
    My issue is that I need to create a tree. So I click on the Tree Swing component and place it in the page. Works fine, but now I need to add a tree model to it so that it actually works for how I want it to work. I've been told there's a treenode component somewhere (the GUI also hints toward it), but I can't find that. Can someone inform me where it is?

    smarttart62 wrote:
    Not 100% sure if this is the right spot...Nope. It's for questions about Java programming. If you want to ask questions about how to use Netbeans then a Netbeans forum would be better. Here's one that I found:
    http://www.netbeans.org/community/lists/top.html

  • How-To/Sample code to tie up class variable to MXML component created in Design view

    This is a very noob question but I've been searching through the documentation for the last 2 hours and can't seem to find anything helpful.  I have a SWFLoader created in the design view.  I have all my app code in an <fx:Script> with all my functions and variable in a CDATA tag.  All I want to do is hookup the SWFLoader created in the design view with a private var in my ActionScript. 
    I also have two separate states for my app, and I want the same SWFLoader to be visible in both states. Can someone point me to some useful sample code or documentation??
    Any help is much appreciated.

    Sun has recommendations for naming conventions. Class names should start with a capital letter. You should avoid using class names that are the same as classes provided in the SDK. Following these conventions will make it easier for people to help you. For example, you should not use file, nor should you use File. It's better to use MyFile, replacing My with something that makes sense to your application (SeniorFile?).
    Also, check the Formatting Help link when posting for a desciption on how to use the code tags for posting code.
    1. You need to establish references between your classes. One way is to have a constructor that has a JMenuBar argument.
    2. You can not add a file to a JMenuBar because a JMenuBar adds a JMenu. I don't think you want file to extend JMenu. It may be better for file to have a JMenu.
    I haven't tried to compile this code so no guarantees - just trying to show you an approach.
    public class Senior extends JFrame {
       public Senior() {
          JMenuBar bar = new JMenuBar();
          MyFile file = new MyFile(bar);
    //whatever else you need
    public class MyFile {
       public MyFile(JMenuBar mbar) {
          JMenu menu = new JMenu();
          mbar.add(menu);

  • Design view in SharePoint Designer 2013

    This looks like a deal killer for me to move to SharePoint 2013 because the missing of design view in the new SharePoint Designer. Here is the way I do list development In SharePoint 2010:
    (1)   
    Create and deploy a custom ui web part in Visual Studio.
    (2)   
    Create additional “New”, “Edit” and “Display” list forms and set them as the default forms in SharePoint Designer.
    (3)   
    Edit the new created forms in design view.
    (4)   
    Locate and hide the original web part.
    (5)   
    Insert my custom web part proper location.
    Only code view is available in SharePoint Designer 2013, I do not know how to hide the default web part and insert my web part (which is deploy to the farm) in code. There are suggestions to use other edit tool to edit web pages. I am not sure
    (1)   
    How to access these form/page in SharePoint.
    (2)   
    How to insert SharePoint web part to the form/page.
    I really appreciate if you can help me out.

    Hi,
    Base on the description, you created web part in Visual Studio and created forms using design view in SharePoint Designer 2010. Now you want to access  the forms and insert the web part to SharePoint 2013 page.
    By default in SharePoint Designer 2013, to add new forms, we can only custom forms in code view. For more information:
    How to Create Custom Forms Using SharePoint Designer 2013:
    http://community.bamboosolutions.com/blogs/sharepoint-2013/archive/2012/09/20/how-to-create-custom-forms-using-sharepoint-designer-2013.aspx
    To insert the web part, we can follow these steps:
    Save this .webpart file to your computer.
    Open the site in the browser, and go to the page on which you would like to place your web part.  With the page in edit mode, click the Page tab, and the Insert tab.  Click
    Web Part.
    On the left side, under the web part categories, click the
    Browse… button under Upload a web part.  Browse to that .webpart file you saved at step1.
    Click Upload.
    Click to insert a web part again, and then you’ll see it in the Imported Web Parts category.  Click Add to add the web part to your page.
    Best Regards,
    Linda Li

  • Custom Components and Properties in Flex Builder Design View

    How do I create a custom component with custom properties
    that renders well in Flex Builder design view?
    This is a simple HelloWorld example of what I am trying
    below. Here is the HelloWorld.mxml file:
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Canvas xmlns:mx="
    http://www.adobe.com/2006/mxml"
    width="500" height="500">
    <mx:Script><![CDATA[
    [Bindable]
    public var message:String;
    ]]></mx:Script>
    <mx:Label x="100" y="100" text="{message}" />
    </mx:Canvas>
    And then when I use it in another mxml file, the design view
    does not show the label with the 'Hello World' value - instead it
    just shows {message} in design view where the label is located.
    When I run it as a compiled app in flash, the 'Hello World' is
    displayed correctly:
    -- HelloWorldTest.mxml --
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Canvas xmlns:mx="
    http://www.adobe.com/2006/mxml"
    xmlns:views="mypackage.*" width="500" height="500">
    <views:SimpleLine message="Hello World."/>
    </mx:Canvas>

    design view does not do any variable assignments or function
    evaluations, so you won't be able to see it even if you don't use a
    custom component.

  • Custom Canvas Shape visible in design view of flex builder

    I have a library which has custom controls. I have a BubbleCanvas class with the following constructor.
          super();
          var style:CSSStyleDeclaration;
          this.setStyle("backgroundImage", canvasBackground);
          this.setStyle("backgroundSize", "100%");
          var btnSave:LinkButton = new LinkButton();
          style = new CSSStyleDeclaration();
          style.setStyle("horizontalCenter", 0);
          style.setStyle("bottom", 20);
          btnSave.label = "save";
          btnSave.styleDeclaration = style;
          btnSave.addEventListener(MouseEvent.CLICK, btnSave_Click);
          this.addChild(btnSave);
          var btnClose:LinkButton = new LinkButton();
          style = new CSSStyleDeclaration();
          style.setStyle("horizontalCenter", 0);
          style.setStyle("top", 5);
          btnClose.label = "close";
          btnClose.styleDeclaration = style;     
          btnClose.addEventListener(MouseEvent.CLICK, btnClose_Click);
          this.addChild(btnClose);
          this.addEventListener(FlexEvent.CREATION_COMPLETE, BubbleForm_CreationComplete);
          this.width = 600;
          this.height = 300;
    canvasBackground is a png image with transparency so that the form is shaped  like a
    conversation bubble.
    Now at run time everything works great, what I would like is to have the  control
    look like a conversation bubble in the design view of flex.
    Oh I only want actionscript code, since the flex sdk controls are all
    actionscript. This is partly acedemic for me.
    Thanks,
    Greg

    > The content is there, but not the 'look' we have created.
    PS how are you referencing the CSS styles? Don’t forget in design view it DW and Contribute will not run any dynamic variables i.e. #stylePath#/this.css you have to use absolute paths. This is sometimes a common issue in deisgn view.

  • FB3 - Flex 4 (Gumbo) SDK - Design View Problem

    Hi.
    I have just downloaded and installed the nightly build of
    Flex 4 SDK (Build 4.0.0.4005) for use with my Flex Builder
    3.0.194161. When I create the simplest of flex applications as
    shown below and set the Flex compiler to use the Flex 4 SDK. When I
    try to switch to design view I get the following error:
    ' This component is based on Application, which is not a
    visual component. Switch to source mode to edit it. '
    If i change the flex comiler settings to use Flex 3 SDK it
    works fine. I would like to start developing for the Flex 4 SDK.
    Does anyone know of a solution to this problem?
    Thanks
    Barry.

    close all project and then close the FB and restart FB.

  • What is the replacement for design view in in flex builder 4.7 for cs extension builder?

    Because design view is not available in flash builder than what is the use of extension builder in UI designing now we have to do design UI with xml which is very time consuming and boring  if there is any replacemnt for it than please help me .1 more thing i want to know is that when i make new default project in extension builder(flash builder 4.6) than it also not able to load design mode errror is
    C:\Program Files\Adobe\Adobe Flash Builder 4.6\eclipse\plugins\com.adobe.cside.libsinstaller_2.0.0.4-33034\archive\cslibs\2.0\4.5\re lease\apedelta.swc- not respondingSWC file failed to load. Any component dependent on this SWC file will not be displayed in the Design Mode.The SWC may have failed to load because of:
    *  Incompatible definitions caused by usage of a different SDK version
    *  Missing referred class definitions

    I have researched this quite considerably and my understanding is that Adobe have no intention of supporting Design View any more for Extension Builder.  In my opinion a very disappointing decision and one that is hard to comprehend.
    The best workaround I can find is to create the majority of your design in a parallel, non Extension Builder, project and then convert/import your design into your Extension.  This is by no means as satisfactory as having Design View for the Extension you are writing but it is better than simply creating your layout by guess work/trial and error.
    Although this has not been announced by Adobe, I have a suspicion that the reason they have decided not to put any further resources into fixing Design View is that Extension Builder as we know it is going to be abandoned soon, probably replaced with an HTML5/JavaScript method of building extensions.  My concern with this is that, other than wanting reassurances that there will be backward compatibility support for old extensions, There will not be a way of compiling an extension in a way that prevents people from seeing your code.
    This is all speculation and I guess we will have to wait and see what happens.  Hope this has helped.

  • Flex 3 Design view disappears

    I have recently downloaded Flex Builder 3 for a trial. I have
    been happily exploring and building simple apps and suddenly I
    can't see the design view in any project or application. When I
    click the "Design" tab I see a grey blank area with no visible
    components.I unistalled/reinstalled the product but the problem
    remains. Am i overlooking something simple being a newbie or has
    anyone else had or is havin tghe same problem.

    try window --> perspective--> flex development

  • I have created numerous forms in Designer and for some reason, "Edit in Designer" from PDF, I cannot edit any of the fields in Design View.

    I have created numerous forms in Designer and for some reason, "Edit in Designer" from PDF, I cannot edit any of the fields in Design View.

    Is it possible you accidentally put the fields on the master page?

  • Flex Builder Design View  programmatic skinning

    I am writing programmatic skins, by extending
    ProgrammaticSkin class. If i apply these skins to mx:Button, i can
    see the skin in Flex Builder design view. But when i style my
    custom component with programmatic skins, Flex Builder design view
    does not show the skin, though the skin is applied when i run the
    application. Is there a way for me to write my custom classes
    (class Node extends UIComponent), and apply skins, so that i can
    see the skins in Flex Builder design view.

    Actually I found the answer to my question. You can find it
    in my blog.
    programmatic
    skinning in Flex Builder Design view

  • Design view not working after importing project from Flex Builder

    After importing a project from Flex Builder to Flash Builder I am no longer able to see anything in the design view. I am using the flex 4.5 sdk.
    Any idea how I can get this design view working? I heard it could have something to do with the metadata directory but am slightly lost here?...
    Adam

    Could you please provide more information as to what exactly are you importing. Also does Design View not lauch at all or does it give errors. Would it be possible for you to share the logs.
    Meanwhile you can try cleaning the workspace and importing again to see if that solves the issue.

  • I have a component like the following and it completely crashes the design view in flex builder

    I have a component like the following and it completely crashes the design view in flex builder.I can see anything in the layout. Everything compliles fine and looks normal in the outline view. Any ideas whats wrong. If I remove the AdvancedDataGridColumnGroup's all looks fine
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Panel x="353" y="34" width="1159" height="505.7" maxWidth="663" allowDrag="true" allowResize="true" allowClose="true" allowMaximize="true" allowMinimize="true" resizeEffect="Resize" moveEffect="Move" close="parent.removeChild(this)" maxHeight="680" layout="absolute" title="Back office list" xmlns:mx="http://www.adobe.com/2006/mxml">
        <mx:AdvancedDataGrid id="deals" displayItemsExpanded="true" dataProvider="{tradesResult}" width="100%" height="373" sortExpertMode="true" variableRowHeight="true" headerStyleName="smallHeader" editable="false" fontWeight="normal">
            <mx:columns>
                <mx:AdvancedDataGridColumn width="75">
                </mx:AdvancedDataGridColumn>
                <mx:AdvancedDataGridColumnGroup headerText="Client side">
                    <mx:AdvancedDataGridColumn dataField="Reference" headerText="Mon Ref" width="60" editable="true" wordWrap="true" showDataTips="true" textAlign="center"/>
                    <mx:AdvancedDataGridColumn dataField="clientside" headerText="MC Pr" textAlign="center" wordWrap="true" width="70">
                    </mx:AdvancedDataGridColumn>
                </mx:AdvancedDataGridColumnGroup>
                <mx:AdvancedDataGridColumnGroup headerText="Bank side">
                    <mx:AdvancedDataGridColumn dataField="bankDealRef" headerText="Bank Ref" width="70" editable="true" wordWrap="true" dataTipFunction="dataTipFuncNotes" showDataTips="true" textAlign="center"/>
                    <mx:AdvancedDataGridColumn dataField="Premium2" headerText="Bank Pr" width="55" editable="true" wordWrap="true" showDataTips="true" textAlign="center"/>
                </mx:AdvancedDataGridColumnGroup>
            </mx:columns>
        </mx:AdvancedDataGrid>
    </mx:Panel>

    Nikos,
    When using grouped columns you should change the <mx:columns> to <mx:groupedColumns>, I ran this example in a sandbox app and it works fine.
    EXAMPLE:
    <mx:AdvancedDataGrid id="deals" displayItemsExpanded="true" dataProvider="{flatData}" width="100%" height="373"
            sortExpertMode="true" variableRowHeight="true" headerStyleName="smallHeader" editable="false" fontWeight="normal">
           <mx:groupedColumns>
                <mx:AdvancedDataGridColumn width="75">
                </mx:AdvancedDataGridColumn>
                <mx:AdvancedDataGridColumnGroup headerText="Client side">
                    <mx:AdvancedDataGridColumn dataField="customer" headerText="Mon Ref" width="60" editable="true" wordWrap="true" showDataTips="true" textAlign="center"/>
                    <mx:AdvancedDataGridColumn dataField="product" headerText="MC Pr" textAlign="center" wordWrap="true" width="70">
                    </mx:AdvancedDataGridColumn>
                </mx:AdvancedDataGridColumnGroup>
                <mx:AdvancedDataGridColumnGroup headerText="Bank side">
                    <mx:AdvancedDataGridColumn dataField="revenue" headerText="Bank Ref" width="70" editable="true" wordWrap="true"
                        showDataTips="true" textAlign="center"/>
                    <mx:AdvancedDataGridColumn dataField="cost" headerText="Bank Pr" width="55" editable="true" wordWrap="true" showDataTips="true" textAlign="center"/>
                </mx:AdvancedDataGridColumnGroup>
            </mx:groupedColumns>
        </mx:AdvancedDataGrid>
    HTH,
    Kenny Yates

  • No Design View = Time to move on from Flex?

    I love Flash/Flex.
    I have been using it for a long time.  Nothing comes close to it in many was as a RIA development tool for making great cross platform apps (OSX/Windows/Linux/iOS/Android). (Not just games)
    However, over the last few years as the properganda from entities that would prefer to see Flash go away, has worked well, and only the people who know flash very well are those who have stayed.. As we understand what we get with flash and how alternatives don;t compare.
    Still, we are the only ones left as anyone starting out, considering the properganda, would not even consider flash anymore.
    I was hoping that flash would continue on with those in the know and the advantages would continue on while the rest of the brain washed community would eventually saw, "ah! why are we not using this.." as they realise the advantages of the cross platfom that flash is king in.
    (Cross platform tools will be the most important single issue as time goes on and the market fragments more and more)
    As the developers that have been fathful to the technology, even tho Adobe has forsaken us..  (And paid the price with  probably the bigest reputational damage in its history) One would expect Adobe had learnt from this..
    But unfortunatly not.  The drop of Design View in 4.7 is, unfortunatly, the decision that will break the developers will.  When we consider the reasons why a developer of RIA uses flex, it is the speed of developing the screens and layouts.  Design View is a key to this.  No design View = no future for the product.  Makes you wonder why they even bothered open sourcing the FLEX sdk.
    Consider this.  every, EVERY... IDE,  Windows, OSX, Android Qt, etc development tool has a design view.  Without it, your nothing but a interesting technology with productivity issues that leads you to never using it.
    And that is where we stand now going forward with Flash Builder...
    I understand that 4.7 is likely more for the game developers and design view is less important however... read on..
    We are now at the cross roads where, as some one who has been holding onto Flash as other tool sets do not compare.  Well. now they do, and in some ways even better.
    This decision will likely force the bulk of those holding on of the flash life boat to swim to another.  It will be such a distastful action to actionscript developers that even the flash Gaming plaltform efforts will likely be terribly damaged if not made irrelevant.
    You need a community of active developers utilsiing that technology if you plan to make it a vilable platform.  Especially for games as its so fickel.
    Killing of the quiet but arguably the most lines written protion of the development base..  Custom RIA apps..  You know not what you have done.
    Deisgn View does not need to do everything, but it needs to be there, so layouts are quck and easy to modify.  It needs to be supported again ASAP, or open sourced ASAP.  A decision has to be made, otherwise.
    Adobe Flash team, guess you'll be moving to the HTML5 dev teams in the very near future. (Or look for a new job..)
    James

    I think this has already been discussed, but I agree that dropping design view is a big problem.  There's a lot of propagandists in IT, sadly, who have ulterior motives when they discuss technologies because they want to promote their own horse in the race.  Attacking Flash (or Flex itself) was one type of dishonest behavior, but I guess another that applies to the Flex community itself was propagating the myth that "nobody uses design view", despite not having a shred of objective evidence to say this (that I've seen).  DV was the #1 thing that made FB stand out over other IDE alternatives, without it you might as well end the product line and let the current alternatives move in.
    I don't think DV can be made open source for technical/legal reasons.  And to be honest, it is a bit bloated & buggy anyway, so I don't care because I think it needs a re-do.  But I do hope someone (either Apache or Adobe, although the latter is probably a fantasy) realizes that developers doing serious UI work (something more complex than a mobile phone app with 4 buttons) require some method of rapidly prototyping and visualizing their UI.  Silverlight has Expression Blend and Sketchflow, JavaFX has Scene Builder, GWT has some design tool -- Flex needs to maintain something.  Probably the main thing keeping me in the Flex realm is just a form of "vendor-lock-in" now.
    Design View doesn't need to be a "design without code" solution that lets you specify every possible component attribute, align text, and specify a data source.  We can do that in MXML, and we can read ASdocs or use autocompletion just fine.  What's needed is an intuitive, fast, reasonably reliable way to visually confirm component layouts, with accurate styles, sizing and scrollbars.  The most essential user interaction is probably sizing & positioning of components and containers.  Maybe with some limited label/text setting shortcuts to help non-developer designers.  It doesn't need to be a plugin or built on Eclipse or anything overly bloated like that, a small standalone app that just does the essentials well is fine--even an AIR app.

Maybe you are looking for