Parsing a string variable as baseURL

October 25, 2011, 6:05 pm

≫ Next: Flash Builder improvements, Syntax coloring, Custom format, Auto close

≪ Previous: How to setup Flex SDK with latest AIR SDK?

I want to use a httpService request to read an XML file which retreives data from the xml file which is the path i want to parse to the Super_Sample1 Class / Function rather than having it as a hard coded path.

I can read the XML file and display the path in a text field.

Once the XML file resoonse is received it then triggers the HTTPService to receive the data using the path from the XLM file.

I get an error when ever I modify the hard coded path to a variable like the {mypath.lastResult} which is where the XML path is returned to.

I hope I explained this clear enough.

Any suggestions on parsing this path to the Function shown below?

package services.sample1

{

import com.adobe.fiber.core.model_internal;

import com.adobe.fiber.services.wrapper.HTTPServiceWrapper;

import mx.rpc.AbstractOperation;

import mx.rpc.AsyncToken;

import mx.rpc.http.HTTPMultiService;

import mx.rpc.http.Operation;

[ExcludeClass]

internal class _Super_Sample1 extends com.adobe.fiber.services.wrapper.HTTPServiceWrapper

{

// Constructor

public function _Super_Sample1()

{

// initialize service control

_serviceControl = new mx.rpc.http.HTTPMultiService("http://ibm/sample01-debug/"); <<<<<< This is what I want to replace with a string variable

var operations:Array = new Array();

var operation:mx.rpc.http.Operation;

var argsArray:Array;

operation = new mx.rpc.http.Operation(null, "Operation");

operation.url = "mytest.php";

operation.method = "GET";

operation.resultType = Object;

operations.push(operation);

_serviceControl.operationList = operations;

preInitializeService();

model_internal::initialize();

}

//init initialization routine here, child class to override

protected function preInitializeService():void

{

}

/**

* This method is a generated wrapper used to call the 'Operation' operation. It returns an mx.rpc.AsyncToken whose

* result property will be populated with the result of the operation when the server response is received.

* To use this result from MXML code, define a CallResponder component and assign its token property to this method's return value.

* You can then bind to CallResponder.lastResult or listen for the CallResponder.result or fault events.

* @see mx.rpc.AsyncToken

* @see mx.rpc.CallResponder

* @return an mx.rpc.AsyncToken whose result property will be populated with the result of the operation when the server response is received.

public function Operation() : mx.rpc.AsyncToken

{

var _internal_operation:mx.rpc.AbstractOperation = _serviceControl.getOperation("Operation");

var _internal_token:mx.rpc.AsyncToken = _internal_operation.send() ;

return _internal_token;

}

↧

Flash Builder improvements, Syntax coloring, Custom format, Auto close

February 19, 2014, 5:29 am

≫ Next: FlashBuilder 4.7 wont publish to Samsung Galaxy Note 10.1 but will publish to Samsung Galaxy S4

≪ Previous: Parsing a string variable as baseURL

Hello,

I'm trying Flash Builder 4.7 but I see there is missing features in the Softaware.

I didn't found this important features in the preferences and I think you could add this new features in the new version of FB:

Syntax coloring like Flash Professional: Coloring the AS3 keywords properties and methods like (addChild, x, y, width, height, etc.)
Custom format code. In FB 4.7 there no way to custom the format code in AS3 but you can do it for Java.
AutoClose : Inserts matching bracket, paren, brace or quote
A list of color themes

I hope it will help to improve this software.

Cheers.

↧

FlashBuilder 4.7 wont publish to Samsung Galaxy Note 10.1 but will publish to Samsung Galaxy S4

February 22, 2014, 3:55 pm

≫ Next: Unable to start Flash Builder 4.5

≪ Previous: Flash Builder improvements, Syntax coloring, Custom format, Auto close

OS: WIndows 7 x64

Hardware: ATI Radion 65xxx series HD, 12GB DDR3, Galaxy Note 10.1 & Galaxy S4

Android 4.1.2 is on the Tablet and 4.2.2 is on the mobile.

Software: Adobe CC (Full) - FlashBuilder 4.7 - AIR for android on both devices 4.x installed

Flashbuilder modification 1: APACHE FLEX Latest downloaded and installed into SDK directory

Flashbuilder modification 2: AIR 4.0 SDK downloaded and installed into eclipse plugins flash compiler directory

Dev test 1: (success)

Built test application to test some Away3D 4.x programming and interaction on AIR.

Result: Flash Player opened SWF and all appeard fine.

Dev test 2: (success)

Created new project - Flash Mobile - merged dev test 1 code into project and compiled on Galaxy S4

Result: FlashBuilder recognised device, installed apk and ran it just fine (AIR 4.x is already installed on device)

Dev test 2b: (failure)

Still using project dev test 2, I unplugged the Galaxy S4 and pluggined in the Galaxy Note 10.1. Pressed debug.

Result: Flashbuilder didn't get any further than displaying the message "Launching: Determining the device on which to install the application..."

Dev test 2c: (failure)

Closed FlashBuilder, unplugged device, CTRL + ALT + DEL then end tasked all ADB processes. Re-opened FlashBuilder, plugged Tablet back in and pressed debug again.

Result: Sat on "Launching: Installing application on device" heard windows noise for unplugged usb device sound?!!?? Waited.. and waited and eventually got the message "Launching 'Away3DIsometricBlockBuilder' has encountered a problem. Error occurred while installing the application: rm failed for /data/local/tmp/Away3DIsometricBlockBuilder.apk, No such file or directory

protocol failure

- waiting for device -"

Dev test 2d: (success)

Unplugged device, end tasked all ADB.exe instances and plugged in galaxy s4 and pressed debug.
Result: Success!

Dev test 2e: (failure)
Unplugged all devices, end tasked all ADB.exe instances and shut down flashbuilder. Opened a command prompt window and adb version = 1.0.31. Downloaded Goolge Android SDK x64 and removed existing android installation folder I had already and extracted files there. Opened SDK Manager and installed the latest Android 4.4 SDK and some other tools etc. Now I went looking for where adb exists. Found the ones relevant to FlashBuilder 4.7 and checked which version they were. SDK used version was 1.0.31 and the AIR eclipse plugins ADB version was also 1.0.31. Checked fresh installed adb version from Google Android SDK and it was also v 1.0.31. Tried a manual install on the device of the apk. Re-opened FlashBuilder re-connected device (tablet) and pressed debug.
Result: Got to Launching 57%, windows made usb disconnection sound and it got no further and popped up the error window which was detailed in "Dev test 2c" above. Device shows connected windows explorer no longer shows device.

Dev test 2f: (failure)

Unplugged device, end tasked all adb.exe instances. Plugged device back in.
Check 1: Windows shows android device plugged in GT-N80810
Check 2: Opened admin rights dos window and typed in adp devices - found 1 at some address
Check 3: adb version = 1.0.31

Check 4: apk file exists

Execute manual install: adp install -r package_name.apk

Result:

-- in dos window --

protocol failure

- waiting for device -

rm failed for /data/local/tmp/apkname.apk, No such file or directory

Dev test 3: (failure)

Created a new flashbuilder 4.7 ActionScript Mobile AIR Project

Name: TabletTest01

Permissions: Internet, Write external storage, wake lock, access network

Auto reorient: yes

Full screen: yes

Added code: trace("hello world");

Pressed debug

Set launch method: on device

Build target = device

Click apply then debug

Result: Same as error shows in 2c

Dev test 3b: (success)

Rebooted pc, rebooted device plugged back in after flashbuilder was running and pressed debug.

Result: sucess traced out "hello world" to console!

Dev test 3c: (failure)

Added code: trace("YYYYYYYYYYYYYYYYYYEEEEEEEEESSSSS!");

Pressed debug.

Result: FAILURE! Same as error shows in 2c

Adobe or anyone know how to fix this issue? or even what is going on?!

I'm tempted to flash the Galaxy Note with Android 4.2.2 or 4.4 google stock rom, to see if it fixes any problems...
However it wouldn't be a true Galaxy Note 10.1 test device anymore, which was the point in buying the thing.

The only things which stand out in all this to me are:

1. The tablet disconnects mid way through the debug publish process, but sometimes the galaxy s4 does also but it doesn't stop it from working?! Timing issue with compiler and data transfer timings? Missing apk file in data temp directory?

2. Android 4.1.2 is on the Tablet and 4.2.2 is on the mobile, could it be an issue with the AIR SDK not correctly handling 4.1.2 where as it is fine with 4.2.2?

Maybe I should have gone the way of the virtual machine... :\

My next tests will be to root the device (odin) and see if I can copy over APK files for installation via the file browser on the device as at the moment APK file transfer is blocked (I don't have the apk copying issue on a non-rooted galaxy s4 however).

Anyone got anything?

PS. Adobe - Image upload doesn't work on this forum editor (chrome).

↧

Unable to start Flash Builder 4.5

June 30, 2011, 6:04 am

≫ Next: No longer able to debug with iPad simulator

≪ Previous: FlashBuilder 4.7 wont publish to Samsung Galaxy Note 10.1 but will publish to Samsung Galaxy S4

I am unable to start Flash Builder. Right at the splash screen I get an error saying to look in the log file, but I don't see where the problem is in the log file. Could anyone help me out. I'll post the log error file.

!SESSION 2011-06-30 09:03:22.543 -----------------------------------------------

eclipse.buildId=I20100608-0911

java.version=1.6.0_16

java.vendor=Sun Microsystems Inc.

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 4 0 2011-06-30 09:03:28.440

!MESSAGE An unexpected runtime error has occurred.

!STACK 0

org.eclipse.swt.SWTError: No more handles

at org.eclipse.swt.SWT.error(SWT.java:4109)

at org.eclipse.swt.SWT.error(SWT.java:3998)

at org.eclipse.swt.SWT.error(SWT.java:3969)

at org.eclipse.swt.widgets.Widget.error(Widget.java:468)

at org.eclipse.swt.widgets.TaskBar.createHandle(TaskBar.java:99)

at org.eclipse.swt.widgets.TaskBar.<init>(TaskBar.java:92)

at org.eclipse.swt.widgets.Display.getSystemTaskBar(Display.java:2499)

at org.eclipse.ui.internal.Workbench$TaskBarDelegatingProgressMontior.getTaskItem(Workbench. java:300)

at org.eclipse.ui.internal.Workbench$TaskBarDelegatingProgressMontior.handleTaskBarProgressU pdated(Workbench.java:316)

at org.eclipse.ui.internal.Workbench$TaskBarDelegatingProgressMontior.worked(Workbench.java: 265)

at org.eclipse.ui.internal.Workbench$StartupProgressBundleListener.bundleChanged(Workbench.j ava:417)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImp l.java:919)

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)

at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue. java:149)

at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEventPrivileged(Framework .java:1349)

at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Framework.java:1300 )

at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:380)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284)

at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)

at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:265)

at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLa zyStarter.java:106)

at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java :453)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoade r.java:216)

at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:393)

at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:3 3)

at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:466)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.jav a:107)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClassInternal(Unknown Source)

at com.adobe.flexbuilder.standalone.FlashBuilderWorkbenchAdvisor.createWorkbenchWindowAdviso r(FlashBuilderWorkbenchAdvisor.java:56)

at org.eclipse.ui.internal.WorkbenchWindow.getWindowAdvisor(WorkbenchWindow.java:3483)

at org.eclipse.ui.internal.WorkbenchWindow.fireWindowOpening(WorkbenchWindow.java:1295)

at org.eclipse.ui.internal.WorkbenchWindow.<init>(WorkbenchWindow.java:408)

at org.eclipse.ui.internal.tweaklets.Workbench3xImplementation.createWorkbenchWindow(Workben ch3xImplementation.java:31)

at org.eclipse.ui.internal.Workbench.newWorkbenchWindow(Workbench.java:1881)

at org.eclipse.ui.internal.Workbench.access$14(Workbench.java:1879)

at org.eclipse.ui.internal.Workbench$21.runWithException(Workbench.java:1199)

at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)

at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)

at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1567)

at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2548)

at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)

at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

at com.adobe.flexbuilder.standalone.FlashBuilderApplication.start(FlashBuilderApplication.ja va:108)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

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:369)

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:619)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)

at org.eclipse.equinox.launcher.Main.run(Main.java:1407)

!ENTRY org.eclipse.ui.workbench 4 0 2011-06-30 09:03:28.442

!MESSAGE