If you are new to Amethyst, you may want to watch this short tutorial. This will lead you through a simple project showing you how to design a user interface, edit your code and use the debugger.
For more videos, see The Amethyst Tutorials Page.
We’ve just uploaded a short video to explain how to link .NET web sites with Flex user interfaces using the integration of WebORB into Amethyst.
Bear in mind that one or two features in the video show new capabilities of the forthcoming release of Amethyst 1.5.
The second beta of Ruby In Steel 2, our Ruby and Rails IDE for Visual Studio 2010 is now available for download.
New features include:
Jruby 1.6 is now supported
Project synchronization now works correctly
Ruby 1.9.2p180 supported
Ruby Explorer reinstated
Ruby In Steel 2.0 supports several Ruby interpreters. You must be sure to use only one of these supported interpreters when using Ruby In Steel’s fast Cylon debugger. Information and downloads available on the Ruby In Steel Prerequisites page.
One of the new features of Amethyst 1.5 is its built in support for debugging and deploying Android applications.
Release Candidate #1 of Amethyst 1.5 is currently available for download HERE. You will need this build, or a later version, to use the Android visual design, deployment and debugging features. To help you get started, refer to the tutorial in this month’s (May 2011) Flash & Flex Developer’s Magazine available as a free download http://ffdmag.com. The code archive that goes with this series of articles can be downloaded HERE.
For more assistance on Flash for Android, see also the screencast tutorials on mobile development on the Amethyst Tutorials Page.
The May 2011 edition of Flash & Flex Developer’s Magazine includes an in-depth interview with Dermot Hogan, the chief architect of the Amethyst IDE for Visual Studio.
In the interview, Dermot explains some of the history and future plans for Amethyst. He explains why, in his opinion, Visual Studio is "the only truly industrial strength IDE" and he describes some of the work that has gone into adding support for mobile development of Flash Platform apps using Amethyst. You can download a free copy of the magazine from http://www.ffdmag.com.
SapphireSteel Software today released the first public preview of Amethyst 1.5, its visual development environment for the Adobe Flash Platform.
Amethyst 1.5 represents a major update to our Visual Studio-based IDE for Flash, Flex and AIR development. The last version of Amethyst (1.2) was released on February the 1st and is available from the Amethyst Download page. In the months since then we have released ten public betas leading towards this first preview of Amethyst 1.5. The preview software includes numerous bug fixes and enhancements suggested by our beta testers plus dozens of new features including:
Support for mobile (Android, Blackberry, iOS) development and deployment
Improved support of Flex 4 and 4.5 including Flex 4 states
New compiler service for faster compilation
Improved simultaneous debugging of mixed Flash/.NET and ASP Web site projects
Improved support of locales, non-English projects, RSLs
Substantially improved support for named Build configurations
Major improvements to the project importer (now imports Flash Builder properties and entire workspaces)
Support for very large projects
For a full list of changes and improvements (and also to download the 1st Preview of Amethyst 1.5) see the Amethyst Release History page.
Here is a short tutorial explaining how to use Amethyst 1.5 to create Adobe AIR multi-screen applications for Android.
Bear in mind that some of these features require the first public beta (or later) of Amethyst 1.5. At the time of writing, the latest beta of Amethyst 1.3 contains a subset of our Android development tools and a forthcoming beta of Amethyst 1.5, which will be released in a few days, adds the additional features shown in this video.
For more on Android development with Amethyst, refer to recent Blog posts:
The latest Amethyst beta includes a first release of tools to support mobile development.
Here’s a short video showing some of the features that will be added in the next beta...
The latest beta of Amethyst includes the first beta of some mobile tools which we have in development.
Programming and debugging apps for mobile devices is something that is likely to become increasingly important for Flash developers. I explained recently how to program, deploy and debug an Android app in Visual Studio using Amethyst.
We also plan to allow developers to target other mobile platforms such as Blackberry and iOS. In the first beta of our mobile development tools, there are quite a lot of different steps (too many!) you have to go through to set all the defaults and configuration options. We want to simplify this and make it much easier to build and deploy for one or multiple mobile platforms. I’ll have more to say about that shortly. In the meantime, here’s a sneak peek at a new wizard that should make it into our next beta release....
The latest (beta) release of Amethyst 1.3 includes preliminary support for mobile development on the Android, iOS and Blackberry platforms. Here I’ll guide you through the steps you need to take you create, deploy and debug your first mobile application from Visual Studio to the Android emulator.
Prerequisites and Installation
Before you are ready to start work on Android development there are certain tools and SDKs that you need to install.
The Android SDK
First download the Android SDK for Windows (the .exe installer is recommended):
Run it to install the SDK.
The Java JDK
If the Java JDK cannot be found the Android SDK installer will prompt you to download it. You may be prompted to download the Java SDK even if you already have it installed but it is not on the system path. If this is the case you need to add the JDK to the path.
To do that, open the Windows Control panel, open System and select Advanced System Settings. In the Settings dialog, click Environment Variables. Select PATH and click Edit. This is likely to show a long path in a small edit field. If necessary copy and paste the path into Notepad for editing. You need to make sure that \bin directory of the JDK is appended (after a semicolon) to the end of the path. On my system , I add this to the path:
Click OK several times to accept all your changes and close down the dialogs. Now try again with the Android installation. A dialog should confirm that it has found your JDK.
Create A Virtual Device
Carry on to the end of the Android SDK setup. At the end you will be prompted to install various packages. Accept the defaults and click Install.
When that’s complete you need to create a Virtual Device. select the ‘Virtual Devices’ option in the Android SDK and AVD Manager (which should already be running at this point but may also be load from the Start menu) . Click New. Enter a name such as Test and select a Target (e.g. Android 2.3.3 API level 10) the click Create AVD. Select the newly created device name and click Start and then Launch. It may take some time to start the Android emulator. When the emulator is ready it will display a start screen (with a background image and, usually, a little green android figure). If you see something else on the emulator, click its ‘Home’ button.
The AIR SDK
You also need to have the latest AIR SDK loaded (e.g. 2.6 or later). This is available here: http://www.adobe.com/products/air/sdk/
Once you’ve unzipped this (I’ll assume you’ve unzipped it to C:\AdobeAIRSDK), you need to install the runtime to your Android device or emulator. Here I am assuming you will be using the software emulator.
From the Windows Start menu, open a Command prompt (enter CMD) in the Start menu’s editable box. Change directory to the AIR Android emulator directory of the AIR SDK. e.g.
Add the Android SDK Platform Tools directory to your path (this is a temporary change as you will do this only once). e.g.
set PATH=%PATH%;C:\Program Files\Android\android-sdk\platform-tools
Run the Android debug Bridge (ADB) tool to install Runtime.apk.
adb install -r Runtime.apk
After a few moment, you should see ‘Success’ displayed at the command prompt. If not, you must check that you have set the path correctly and you are in the emulator directory which contains Runtime.apk then try again. Once you are successful you can close the command prompt.
Create and Debug an Android app
Now you are ready to create, deploy and debug an Android application. For the sake of simplicity, mine will be a simple ‘Hello world’ program. Bear in mind that the instructions here relate to the preliminary release (the first public beta) of Amethyst’s mobile tools (April, 2011). These will change – in some areas, probably quite significantly – in later releases. We will aim to make deployment and debugging a much simpler experience. But for now, be sure to follow these instructions carefully.
First, if it is not already running, load the Android SDK Manager from the Start menu. Create or select a virtual device (as explained earlier) from the list and click Start and Launch.
Wait until the emulator is loaded and initialized.
Now let’s create a very simple “Hello World” application. For simplicity we’ll do this as an ActionScript mobile application (though Amethyst also supports Flex/AIR mobile applications).
Start a new Project: Select File, New, Project.
Select Mobile, Mobile ActionScript Application.
If necessary, browse to a location and name the project.
Open the main application file (the ActionScript file that is created automatically by Amethyst – for example, in my project this is MobileActionScriptApplication2.as) and add this code to its constructor:
var textField:TextField = new TextField();
textField.text = "Hello, World!";
The TextField class needs to be imported. The simplest way to do this is to right-click TextField in the editor and select Organize Imports, Add Import.
This import statement will be automatically added:
Place a breakpoint on the final line (stage.addChild(textField)).
|NOTE: You must be using the Flex 4.5 SDK (or later). Make sure the SDK is set in the Application properties tab. Click the Browse button to select an SDK if necessary. Hint: You may add multiple SDKs globally using Tools, Options, Projects and Solutions, Amethyst. Click the Browse button next to Flex/default SDK Path and browse to add a new SDK.|
Select Project, Properties.
Click the Application tab.
Make sure Project type is ‘AIR’ and Deployment is ‘Android’.
The project will be reloaded in order to apply these changes,.
Select Project, Properties.
Click the Deploy Tab.
Browse to the Android SDK path (e.g. C:\Program Files\Android\android-sdk)
Make sure ‘Use emulator’ is checked.
Create a new key store or browse to use an existing one.
Note: A key store is required in order to allow an Android device to load your application.
To create a key store, click Create. Enter a name (e.g. ‘mykey’), a file name for the key store (e.g. ‘keyfile’) and a password (e.g. ‘mypassword’). Click OK.
If you see errors when creating a key store, check that you are using the Flex 4.5 SDK or later (set in the Application properties page) and try again.
The password you are using must be entered into the key store password field. This is done automatically.
Make sure that your Build Configuration is set to both Build and Deploy your application. Select Build, Configuration Manager. Alongside your Project’s name ensure that Build and Deploy are checked. Then click Close.
Also, make sure that the namespace in your xml configuration file is correct (you may receive a deployment error if it is not). This step is only likely to be needed while the Adobe AIR SDK is still in beta. Check this in the application tag of the xml file under the \config folder (in the Solution Explorer). For example, if you are using AIR 2.5 this should take this form:
If you are using AIR 2.6 it should be like this:
Your are now ready to build, deploy and debug your project. This can be done simply by pressing F5 (alternatively you may select each option in turn from the Build and Debug menus). The Android requires its daemon to be running. The first time you attempt to deploy, it may fail to synchronize in which case, just press F5 to try again.
The breakpoint will be hit and you can now use thee debugger.
Press F5 to continue and the program will display “Hello world!” on the Android emulator And you can now carry on debugging using the full range of debugging tools provided by the Amethyst ‘Cylon’ debugger. Here is a slightly more complex example: an Android-based adventure game being debugged in Amethyst...
More Blog Posts...0 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 |...