Flexviewer 2.0 / Flash Builder 4 help

[deleted-user-KvGhOT8slQTw]

Can anyone give a quick step by step on importing code from the code gallery into Flash Builder 4, compiling it, and then dropping the files in the correct location within the Flexviewer 2 folder tree? I�??m very new to Flex and definitely not a programmer, but would like to take advantage of the widgets that have been placed in the code gallery. I tried to take the �??Flex Map Printing Utility�?� from the code gallery and compile it in Flash Builder 4 and cannot get it to work. My assumption was that I had to compile to create the .swf file, drop the .swf into the widget folder, and then modify the config file. I am thinking that I am not compiling correctly or I am not putting the files in the correct location. Any help is greatly appreciated!

[RobertScheitlin__GISP]

eeharrison,

   Well about 99.8% of all the widgets in the code gallery are developed for the 1.x version of the flex viewer (aka SFV). You can not use any of the 1.x widgets in the new FlexViewer 2.0... The whole base that the 1.x widgets were built for is different (i.e AGS Flex 1.x API and Flex 3.x SDK). I would say that the widgetdevelopers (like myself) are going to wait until the FlexViewer 2.0 is no longer beta before they start re-developing widgets.

[deleted-user-KvGhOT8slQTw]

With that being said, is it possible to compile those widgets in Flashbuilder 4 for use in Flexviewer 1.3? I noticed the ability to use the 3.5 SDK, but still not sure where to drop the output files in the 1.3 folder structure.

[RobertScheitlin__GISP]

Eric,

   Yes you can use FlashBuilder 4 with the SFV 1.3 as long as you do as you mentioned and use the 3.x SDK and the 1.3 AGS API. As far as where to drop the output, there seems to be a little confusion there on your side. What you need to do in Import the whole SFV 1.3 source files as a project into your FlashBuilder 4 development environment. Then as you build the project and debug it the compiled swfs will be in the bin-debug folder of your project and when you are happy with your development then you export a release build and then the compiled swfs are in your bin-release folder and are ready to be copied to your web server.

[CarmenDurham]

Robert,

We have a FlexViewer app 1.3 that has been extensively altered from the original.

Is it reasonably possible to take the existing SFV 1.3 app and upgrade it to use FlashBuilder 4, SDK4 with ESRI Flex API 2.0?  Or will it be a nightmare?  Or not even possible?

We also have some plain Flex Apps (not Flex Viewer).

Would it be better to just use:

• For FlexViewer 1.3 - just load into FlashBuilder 4 but use 1.3 api and 3.5 SDK


• For other plain Flex apps: load into FlashBuilder 4, but convert them to 2.0 API and 4.0SDK?

Thanks,

[BjornSvensson]

ignore ...

[RobertScheitlin__GISP]

Carmen,

  Migrating a 1.3 SFV app to 2.0 is possible but absolutely a nightmare.

    YES - For FlexViewer 1.3 - just load into FlashBuilder 4 but use 1.3 api and 3.5 SDK
    YES - For other plain Flex apps: load into FlashBuilder 4, but convert them to 2.0 API and 4.0SDK?

Migrating a non-SFV app to the 2.0 API and FlashBuilder 4 is not very hard.

[CarmenDurham]

Thanks Robert!

I realize I should have put this in another thread as it wasn't totally related to the original question.  Just got in too much of a hurry yesterday.

I'm rating it well for the answer you provided to me above.

Carmen

[MattMoyles]

Is there any update on when the next beta or RC version of 2.0 will be out?

[RobertScheitlin__GISP]

Matt,

   they must be getting ready to release as they are talking about adding fixes to the 2.1 version when they speak of fixes.