wok diff adobe-air-sdk/description.txt @ rev 22710

updated f3 (2.2 -> 7.2)
author Hans-G?nter Theisgen
date Wed Jan 22 09:41:20 2020 +0100 (2020-01-22)
parents
children
line diff
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/adobe-air-sdk/description.txt	Wed Jan 22 09:41:20 2020 +0100
     1.3 @@ -0,0 +1,88 @@
     1.4 +[Adobe Integrated Runtime (AIR)](https://en.wikipedia.org/wiki/Adobe_Integrated_Runtime)
     1.5 +is a cross-platform runtime environment developed by Adobe Systems for building
     1.6 +rich Internet applications using Adobe Flash, Adobe Flex, HTML, or Ajax, that
     1.7 +can be deployed as desktop applications.
     1.8 +
     1.9 +
    1.10 +Installing an AIR Application
    1.11 +-----------------------------
    1.12 +
    1.13 +Download the application, and unzip it to `/opt/airapps/<appname>`. To run it
    1.14 +you can use the command
    1.15 +
    1.16 +    $ /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/
    1.17 +
    1.18 +
    1.19 +Making it executable
    1.20 +--------------------
    1.21 +
    1.22 +You can also make an executable by creating a file in /usr/local/bin:
    1.23 +
    1.24 +    #!/usr/bin/sh
    1.25 +    /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/
    1.26 +
    1.27 +The app might need parameters (voddler) so then the script can look like:
    1.28 +
    1.29 +    #!/usr/bin/sh
    1.30 +    /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/ -- ${@}
    1.31 +
    1.32 +Then chmod the file so that it can execute:
    1.33 +
    1.34 +    $ chmod +x filename
    1.35 +
    1.36 +Now you have installed an application in AIR. Yes it is this silly :P
    1.37 +
    1.38 +
    1.39 +Removing the application
    1.40 +------------------------
    1.41 +
    1.42 +Delete the application folder in `/opt/airapps`. Also delete the executable if
    1.43 +you created one.
    1.44 +
    1.45 +
    1.46 +Running binaries that use AIR
    1.47 +-----------------------------
    1.48 +
    1.49 +Some applications using Adobe AIR can come with their own binaries included. In
    1.50 +this case, it's often better to run these binaries, rather than bypassing them
    1.51 +using adl, to not lose any extra functionality these binaries might provide.
    1.52 +These binaries will require some work however, before they can be used with the
    1.53 +Adobe AIR SDK.
    1.54 +
    1.55 +First of all, binaries will look for Adobe AIR, rather than the Adobe AIR SDK.
    1.56 +There seems to be no way to change where to look, so you're going to have to
    1.57 +symlink the Adobe AIR runtime provided with the SDK to the default location
    1.58 +that binaries follow:
    1.59 +
    1.60 +    # ln -s /opt/adobe-air-sdk/runtimes/air/linux/Adobe\ AIR/ /opt/Adobe\ AIR
    1.61 +
    1.62 +With this, the binaries should be able to detect your Adobe AIR installation.
    1.63 +It will leave you with two Adobe AIR folders in  /opt, which is dirty but there
    1.64 +seems to be no way around this for now.
    1.65 +
    1.66 +Another problem you'll run into is that whenever the AIR runtime starts a
    1.67 +process, it'll check whether you have accepted the EULA, something that is not
    1.68 +included with the SDK. Since it can't determine that you did, it then tries to
    1.69 +run the Adobe AIR Updater, which is ALSO not included in the SDK runtime,
    1.70 +causing the binary to fail and hang. To avoid this you're going to have to
    1.71 +manually accept the EULA.
    1.72 +
    1.73 +Warning: By creating the following file you are most likely accepting the
    1.74 +[Adobe AIR End User License Agreement](http://www.adobe.com/products/eulas/air_eula.html).
    1.75 +Make sure to read this agreement, and do not perform this work-around if you do
    1.76 +not agree with it.
    1.77 +
    1.78 +
    1.79 +To manually accept the EULA, use this command:
    1.80 +
    1.81 +    echo -n 2 > ~/.appdata/Adobe/AIR/eulaAccepted
    1.82 +
    1.83 +After this, you should clear the check and the binary should run normally.
    1.84 +
    1.85 +---
    1.86 +
    1.87 +This information has been shamelessly copied from this page:
    1.88 +https://wiki.archlinux.org/index.php/Adobe_AIR
    1.89 +
    1.90 +Content is available under GNU Free Documentation License 1.3 or later unless
    1.91 +otherwise noted.