Archive for the ‘Flex’ Category
You are currently browsing the archives for the Flex category.
5
Mar
2012
Flex & SAP: SAP Gateway as dataService plugin
Follow these steps in order to set up SAP GAteway as one of the data service objects in your Adobe Flex builder.
Prerequisites
- Fully installed version of Adobe Flex builder version 4.5
Installation instructions
- Download the SAP Gateway plug-in from Adobe [link here]
- Start Flex Builder using as an Administrator
- Once started select Help – Install New Software option from the header menue
- Specify the location of the file that you’ve downloaded from Adobe website
- Select the appropriate version to be installed
- Accept the terms and complete the configuration process
- The system will begin the installation process, upon completeion you will have to restart your Flex Builder instance
- Once Flex Builder is re-installed you will see SAP Gateway as one of the available data models
For more information on the subject you can reference the following links:
- Flash Builder Plug-in for SAP NetWeaver getting started guide
- Getting Started with Flash Builder Plug-in for SAP NetWeaver Gateway Services video
- Getting Deeper with Flash Builder Plug-in for SAP NetWeaver Gateway Services video
- Sap Netweaver Gateway Developer Tools
15
Jul
2011
MXML: “true && true” error
Stumbled across this strange error while doing some development. I’ve needed to determine the enable function of a button based on two boolean conditions and as a result created the following bit of code:
<com:Component enabled=”{booleanA && booleanB}”/>
The compiler didn’t like what I’ve put together and threw the following error: The entity name must immediately follow the ‘&’ in the entity reference.
At first I litteraly thought that I’ve forgotten how to code and trivially tried a simple if statement in a <fx:Script> tag – that worked without a problem. I’ve also tried to see if the or ”||” operator worked within the enabled attribute – which it did. My last thought before searching for a solution online was that the latest version of Adobe Flex had a bug in it.
Some of the solution that I’ve discovered are:
- use ;& instead
- use (booleanA) ? (booleanB):false
- use !(!active1 || !active2)
I found the third option to be quite amusing though in general the root cause of the problem is the XML parsing of the MXML code. Once you understand it should be straight forward.
16
Jan
2011
Adobe Flex: smooth out the images – scaleContent
When you’re dealing with a situation that requires the use of the following image settings:
width="100%"
height="100%"
scaleContent="true"
maintainAspectRatio="true"
You can find your self in a situation where the loaded content will result in a pixelated bitmap. Simply add a complete event handler to your image component and update the contents of the event in the following way:
var lv_btmp:Bitmap = ((event.target as Image).content as Bitmap);
if ( lv_btmp != null )
lv_btmp.smoothing = true;
this will smooth out the image that you have loaded.
29
Nov
2010
FLEX: BlackBerry SDK basic compilation error [locale]
When I tried creating a new project with the BlackBerry sdk I ran in to the following error:
Description Resource Path Type LocationUnable to resolve resource bundle "collections" for locale "en_US".Flex Problem Unknown
Although annoying I quickly found a solution:
- Go to the Project Properties
- Navigate to Flex Compiler
- And type in the following line
-library-path+="C:\Program Files\Adobe\Adobe Flash Builder 4\sdks\
blackberry-tablet-sdk-0.9.0\frameworks\locale\en_US"
28
Nov
2010
FLEX: convert HTML format to RichText
If you are working with rich text editors you will run in to a situation where you have to format an HTML string to RichText value.
Following code can accomplish this:
gc_ta_bio.textFlow =
TextConverter.importToFlow( "<h1>Your String</h1>,
TextConverter.TEXT_FIELD_HTML_FORMAT )
Where the MXML control will look something like this:
<s:RichEditableText id="gc_ta_bio" />
18
Oct
2010
Flash Cross-Domain policies
A nice introduction to what the cross-domain policy are all about
11
Mar
2009
AMFPHP + Flex 3 = Error [unable to open 'services-config.xml']
While trying to configure the AMFPHP set up with the Flex 3 framework I ran in to a problem while setting up the services-config.xml.
I’ve created the file in the root directory and specified in the Flex Compiler [Additional compiler arguments] the following string -locale en_US -services “services-config.xml”.
As soon as I clicked OK an error popped up with a message unable to open ‘services-config.xml’. After trying varying things I was able to figure out that the problem was with the location of the file. Simply placing the file at the root of the directory wasn’t the right location. I needed to put the file in the same directory as the main MXML executable – after that the program worked as expected.
2
Mar
2009
Gumbo effects comming soon
Gumbo: the next release of Adobe Flex SDK interface will has some interesting and useful features. The idea of developing custom controls [like buttons or menues] which slide in and out based on mouse interaction can be problematic to build. The logic of incomplete slide ins and slide outs along with the gittery screen can cause the application to look unpolished.
All of this is about to change as you can see in this video describing the new sequence functionality that will be available in the next release. Have a look at the more complex sequences.
PS: seems that the new release will be hitting the shelf sometime in the second half of 2009.
2
Mar
2009
Adobe Flex online tutorials
A great collection of tutorials for anyone who is interested in learning how to work with Adobe Flex. The lessons cover everything from the basics of Flex Builder to more complicated topics like building run time shared libraries. Have a look and learn something new.
2
Feb
2009
xCelsius: a half baked solution
Before I begin let me just say that I am a big supporter of what Adobe has done with the Flex application. As a result I’ve tried to be un-biast and explicit about my opinion.
I have a few concerns regarding a new product xcelsius. Despite impressive results there are fundamentals shortcommings that will become evident while working with the application.
- Flexibility
- The product is designed strictly to follow a particular approach. This methodology is quite unintuitive and requires the developer to put additional effort when designing the model. The structure is rigid and sometimes confusing. Most of the time it feels like you are trying to create a workaround forcing the intuitive solution in to the Xcelsius model.
- Functionality
- Overall the product looks like a 1/2 backed solution. It is an implementation that is driven by the components provided with the standard load [some are not sufficient in terms of what is expected from a developer's point of view]. The platform is designed to rely on Microsoft Excel but lacks capability to take advantage of basic Excel advantages [like Visual Basic enhancements], the solution is restricted to support only a handful of Microsoft Excel functions/formulas.
- Maintainability & Support [This I believe is a major issue going forward with this solution.]
- The application has no debugger.
- Everything is linked to a Excel cells which can have complicated formulas. IE: cell A references cell B that references C which sums cells D through E which in it self point to cell F.
- During the training we’ve agreed that we would want to call the database to load information directly. This would eliminate the above mentioned complicated point. But still – the developer will be left with a BLANK spreadsheet where one would have to guess where and how the cells are referenced. In laymen’s terms: try figuring out where Matrix!$D$21:$O$21 is coming from.
Overall this is just another attempt to market Adobe’s ability to present data, an attempt that failed miserably.
