You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tutorials/android-device-debugging.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,11 @@ To enable "Developer mode":
15
15
- Tap **Build number** several times and you should see a dialog that says "you're X taps away from being a developer".
16
16
- Continue tapping the build number until the developer mode is enabled.
17
17
18
+
:::note
19
+
The specific loction of the **Build number** can vary based on the manufacturer and android version. You may have to explore your settings a bit to find it.
20
+
:::
21
+
22
+
18
23
To enable USB debuging:
19
24
20
25
- Go to the settings menu
@@ -24,8 +29,9 @@ To enable USB debuging:
24
29
25
30
You will now be able to connect a usb cable to your device and use the `adb` tool to install applications (APKs) and access the device logs.
26
31
27
-
28
-
32
+
:::note
33
+
When you first connect a new computer using USB, depending on the Android version you may have an authorisation dialog appear to authorise the connection to the computer.
Copy file name to clipboardExpand all lines: docs/tutorials/device-logs.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,8 @@ Getting access to the device logs often yields additional information when attem
10
10
11
11
On Android it is relatively simple to get the device logs. The debugger command line utility (`adb`/`adb.exe`) can be used to output the logs along with installing your application and is packaged as part of AIR at `AIRSDK/lib/android/bin`. If you have installed the Android SDK you can also use the version from there.
12
12
13
-
> Note: It is important you have set your device into debug mode.
13
+
> Note: It is important you have set your device into debug mode. See [Android Device Debugging](android-device-debugging.md).
14
+
14
15
15
16
### macOS (OSX)
16
17
@@ -19,12 +20,18 @@ To access the logs:
19
20
- open a Terminal
20
21
- run `adb logcat`
21
22
22
-
You can get more relevant information by using grep to filter the logs. For example, we often use the following:
23
+
24
+
#### Filtering
25
+
26
+
You can control the output by using `grep` to filter the logs. For example, we often use the following:
Copy file name to clipboardExpand all lines: docs/tutorials/getting-started-flashbuilder4.5.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,21 @@
1
1
---
2
-
title: Getting Started - Flash Builder 4.5
2
+
title: Flash Builder 4.5
3
3
sidebar_label: Flash Builder 4.5
4
4
---
5
5
6
+
:::warning
7
+
Flash Builder is no longer supported by our extensions. Flash Builder links directly into the legacy build methods of the AIR SDK and as such cannot support the latest Android features and won't work with our extensions any longer.
8
+
9
+
You may be able to use it as an editor but the packaging process won't work. You'll need to use the AIR SDK directly to package your application. We encourage you to move to a more modern development environment.
10
+
:::
11
+
12
+
:::caution
13
+
Last release: Adobe Flash Builder 4.5, released in May, 2011.
14
+
15
+
Adobe Flash Builder reached end of core support in 2017 and end of extended support in 2019.
16
+
:::
17
+
18
+
6
19
An AIR Native Extension (ANE) is a single file with the extension `ane`. This file contains all of the native and actionscript libraries that are implemented by this extension. You don’t need access to a separate SWC file or to the source code to be able to use the ANE.
7
20
8
21
Here we will add the extension to your build process so that your application can use the functionality provided by the extension.
Copy file name to clipboardExpand all lines: docs/tutorials/getting-started-flashbuilder4.7.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,20 @@
1
1
---
2
-
title: Getting Started - Flash Builder 4.6/4.7
2
+
title: Flash Builder 4.6/4.7
3
3
sidebar_label: Flash Builder 4.6/4.7
4
4
---
5
5
6
+
:::warning
7
+
Flash Builder is no longer supported by our extensions. Flash Builder links directly into the legacy build methods of the AIR SDK and as such cannot support the latest Android features and won't work with our extensions any longer.
8
+
9
+
You may be able to use it as an editor but the packaging process won't work. You'll need to use the AIR SDK directly to package your application. We encourage you to move to a more modern development environment.
10
+
:::
11
+
12
+
:::caution
13
+
Last release: Adobe Flash Builder 4.7, released in Dec, 2012.
14
+
15
+
Adobe Flash Builder reached end of core support in 2017 and end of extended support in 2019.
16
+
:::
17
+
6
18
## Add the Extension
7
19
8
20
An AIR Native Extension (ANE) is a single file with the extension `ane`. This file contains all of the native and actionscript libraries that are implemented by this extension. You don’t need access to a separate SWC file or to the source code to be able to use the ANE.
Copy file name to clipboardExpand all lines: docs/tutorials/ios-icons-assets-car.md
+50-23Lines changed: 50 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,30 +24,46 @@ Contents:
24
24
-[Supporting previous versions of iOS](#supporting-previous-versions-of-ios)
25
25
26
26
27
+
## Creating the Asset Catalogue
27
28
28
-
## Method 1 Command Line
29
29
30
-
:::note
31
-
You will need a macOS machine with Xcode 9+ for this method to generate the `Assets.car` file
30
+
### Method 1: AIR-ImageScripts
31
+
32
+
:::tip Recommended Approach
33
+
You will need a macOS machine with Xcode and imagemagik for this method, however the files can be transferred afterwards.
32
34
:::
33
35
34
-
This is the method we prefer as it is simpler to update and create than having to drag files into Xcode. We have a script that downloads the required assets, resizes an icon and launch screen image appropriately and calls the xcode utilities to generate the Assets.car (and launch screen).
36
+
This is the method we prefer as it is simpler to update and create than having to drag files into Xcode. We have a script that downloads the required assets, resizes an icon and launch screen image appropriately and calls the xcode utilities to generate the Assets.car (and launch screen).
35
37
36
38
The script is available in the [AIR-ImageScripts repository](https://github.com/distriqt/AIR-ImageScripts)
37
39
38
40
You will need to have installed `imagemagick` and the **xcode command line utilities** (see details in the repository if you need help installing them).
39
41
40
-
To use it, create an `icon.png` file that is a high resolution icon file (we suggest 1024x1024) and a `launch.png` launch screen image (we suggest a large 2732x2732 pixel image). Place them in a directory and open a terminal at this location. You can either clone the repository and use the `generate.sh` script directly or call it as below:
42
+
To use it you will need to create 4 files for your icon. We require a foreground and background for your main icon so we can correctly create the adaptive icons for various situations. Then also a monochrome version of your foreground icon for themed environments and then a complete alternative icon to be used in dark situations on iOS.
43
+
44
+
These four base images are used to construct the icons for each of the platforms:
45
+
46
+
-`icon-foreground.png`: should be a transparent icon with no background which will be layered over the background and centered on the launch image
47
+
-`icon-background.png`: should be a filled image which constitutes the background of adaptive icons and the launch image (generally a solid colour)
48
+
-`icon-monochrome.png`: similar to the foreground icon except this should be monochrome and will be tinted by the OS to colour match the user's theme
49
+
-`icon-dark.png`: a specific dark image to be used as the dark icon on iOS
50
+
51
+
All of these files should be high resolution (we suggest 1024x1024)
52
+
53
+
Next create a `launch.png` launch screen image (we suggest a large 2732x2732 pixel image).
54
+
55
+
Place all these files in a directory and open a terminal at this location. You can either clone the repository and use the `generateIcons` script directly or call it as below:
Once complete this will have generated an `out` directory that contains
47
62
48
63
-`Assets.car` your asset catalogue
49
64
-`LaunchScreen.storyboardc` directory is your custom launch screen storyboard
50
-
-`icons` directory containing icon images sized for AIR.
65
+
-`icons` directory containing icon images sized for AIR
66
+
-`res` folder containing adaptive icons for Android
51
67
52
68
Copy these into your application as you require.
53
69
@@ -80,11 +96,11 @@ You can use the `icons` directory in your application descriptor by adding the f
80
96
</icon>
81
97
```
82
98
83
-
## Method 2 Using Xcode
99
+
###Method 2: Using Xcode
84
100
85
-
>
86
-
> Note: You will need a macOS machine with Xcode 9+ for this method to generate the `Assets.car` file
87
-
>
101
+
:::note
102
+
You will need a macOS machine with Xcode for this method to generate the `Assets.car` file
103
+
:::
88
104
89
105
Firstly you will need to open Xcode and create a new application
90
106
@@ -124,7 +140,11 @@ Firstly you will need to open Xcode and create a new application
124
140
125
141
126
142
127
-
## Method 3 Online tool
143
+
### Method 3: Online tool
144
+
145
+
:::caution
146
+
We do not recommend this approach as it can cause issues depending on your AIR developer license. This approach can miss resources required by the AIR SDK and cause your application to crash.
147
+
:::
128
148
129
149
This is the simplest way if you are a Windows developer.
130
150
@@ -147,16 +167,18 @@ You do this by ensuring that it is in the root of your applications source and s
147
167
148
168
## Simple Launch Screen
149
169
150
-
To simplify migration to launch storyboards we have created a simple storyboard that pulls an image from your `Assets.car` and aspect fills it to the screen. You will add a single image to your `Assets.car` alongside your application icons. (If you followed the instructions above this will be the `LaunchImage.png` you added.)
170
+
To simplify migration to launch storyboards we have created a simple storyboard that pulls an image from your `Assets.car` and aspect fills it to the screen. You will add a single image to your `Assets.car` alongside your application icons.
171
+
172
+
The AIR Image Scripts process above should have generated this launch screen for you.
173
+
151
174
152
175
Download this zip file and extract the `LaunchScreen.storyboardc`. Add it to your application and ensure it is packaged at the root level of your application alongside your `Assets.car`.
> `LaunchScreen.storyboardc` is a directory but will appear as a "file" (package) on macOS
158
-
>
159
-
179
+
:::note
180
+
`LaunchScreen.storyboardc` is a directory but will appear as a "file" (package) on macOS
181
+
:::
160
182
161
183
Add the following to the `InfoAdditions` node in your application descriptor:
162
184
@@ -170,17 +192,22 @@ That is all, you have now implemented a launch storyboard.
170
192
171
193
172
194
173
-
## Supporting previous versions of iOS
195
+
## Launch images
174
196
175
-
You must also make sure that you include the icons in your application using the icon tags in the application descriptor xml.
176
-
This ensures that older versions of iOS still have the correct icons packaged and that other platforms still have the appropriate app icons.
197
+
:::note
198
+
This is no longer relevant as the minimum iOS version supported by new apps should support the launch screen approach and the default images are no longer required.
199
+
:::
177
200
201
+
Recently Apple changed the supported names of the files for the default / launch images. Make sure you have correctly added the default images according to the Adobe docs:
Recently Apple changed the supported names of the files for the default / launch images. Make sure you have correctly added the default images according to the Adobe docs:
206
+
### Supporting previous versions of iOS
207
+
208
+
209
+
You must also make sure that you include the icons in your application using the icon tags in the application descriptor xml.
210
+
This ensures that older versions of iOS still have the correct icons packaged and that other platforms still have the appropriate app icons.
Copy file name to clipboardExpand all lines: docs/tutorials/ios-launchscreens.md
+16-12Lines changed: 16 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,20 +20,23 @@ Contents:
20
20
-[Adding to AIR](#adding-to-air)
21
21
22
22
23
-
# Method 1
23
+
##Method 1
24
24
25
-
This simple method uses a prebuilt storyboard which pulls an image from your `Assets.car` and fill the screen keeping the aspect ratio (your image may be cropped on some devices depending on the resolution).
25
+
:::tip Recommended Approach
26
+
:::
26
27
27
-
We have included these instructions as part of the [Icons, Launch Storyboards and the Assets Catalog](ios-icons-assets-car.md#method-1-command-line) guide.
28
+
This simple method uses a script we have written that builds upon a prebuilt storyboard to show an image from your `Assets.car`and fill the screen keeping the aspect ratio (your image may be cropped on some devices depending on the resolution and the image).
28
29
30
+
We have included these instructions as part of the [Icons, Launch Storyboards and the Assets Catalog](ios-icons-assets-car.md#method-1-air-imagescripts) guide.
29
31
30
-
# Method 2
31
32
32
-
Using Xcode
33
+
## Method 2
33
34
34
-
>
35
-
> Note: You will need a macOS machine with Xcode 9+ for this method to generate the `Assets.car` file
36
-
>
35
+
This method uses Xcode directly.
36
+
37
+
:::note
38
+
You will need a macOS machine with Xcode for this method to generate the `Assets.car` file
39
+
:::
37
40
38
41
As this process is tightly integrated with generating the `Assets.car` (asset catalog) containing your application icons, we will go through adding the icons first.
39
42
@@ -70,7 +73,7 @@ Now you have added the application icons we move onto adding the launch storyboa
70
73
71
74
72
75
73
-
## Centered Icon
76
+
###Centered Icon
74
77
75
78
Firstly we need to add the image resource to your asset catalog.
76
79
@@ -116,7 +119,7 @@ Firstly we need to add the image resource to your asset catalog.
0 commit comments