AIR Package Manager

hydroper

It's not really important, but pointing to ASDoc or Haxe Dox recipient on package registry would be cool

ma

@hydroper Good call , I'll make sure there is a separate documentation link in place for the packages.

ma

Small update for anyone interested, we have released the first beta. It's has all the package management utilities in place but there's only a few packages in the repository currently.

But would welcome any feedback!

https://github.com/airsdk/apm

joshtynjala

ma Congrats on the first beta!

I saw this in the installation instructions:

we need to add the AIR SDK to your PATH environment variable

Can you add more ways to specify the path to the AIR SDK? Maybe an optional config file somewhere? Maybe also an optional command line option? Since I have to juggle many SDKs (AIR, Flex, Feathers, Royale) and often multiple versions of each, I try to avoid adding any of them to environment variables.

joshtynjala

To avoid setting any environment variables for now, I modified the apm shell script to use an absolute path to adl:

/path/to/AIRSDK/bin/adl -profile extendedDesktop -cmd "$SCRIPT_DIR/apm.xml" -- -workingdir "`pwd`" $@

A similar workaround for the Windows .bat file should look something like this:

C:\path\to\AIRSDK\bin\adl -profile extendedDesktop -cmd "%~dp0\apm.xml" -- -workingdir "%cd%" %*

Obviously, this would need to be re-done every time I download a new version of apm, but it's good enough for now.

ma

@joshtynjala Yeah exactly right, you can modify the script to point to your installation. The need to make it available on the path was just simplifying the installation for most developers so the script can launch adl anywhere.

We are still working on this process, eventually I hope to have the AIR SDK actually produce an executable independent of the AIR SDK but that's not working consistently at the moment.

Daniel

Congrats from me as well, Michael! I'm really looking forward to this – this will make AIR development feel much more modern immediately!

Thanks to your excellent documentation and help, Starling is already part of the repository!
After setting up a project with apm init, install it via

apm install starling # → gets SWC library
# or
apm install starling-source # → gets source

Hurray! That's how it's supposed to be. You made a developer happy. 😁🥳😎

Daniel

And BTW, this installs Starling 2.7! I've used this opportunity to finally push a new version out into the wild. 😁
A blog post will follow ... eventually. 😜

mfrasier

Daniel Daniel Talk about a low key announcement 😀

Bilbosax

I haven't had time to take a deep dive into the documentation yet, but how does this package manager know whether we have access to the packages that we are tying to install? In other words, if I want to use it to install the Distriqt In-App Billing ANE and dependencies and create a descriptor file, how does it know whether we have subscription permissions to use the ANE??

ma

Bilbosax Currently this is handled rather basically. You can add a github access token and the package manager will fail to install a package if you can't access the repository.

leokan23

So the source option means that I can add as package libraries which were too confusing to make to .swc?

Also just throwing ideas here, might be nice to have a dedicated site for apm packages (like pub.dev for flutter) and maybe on a later version AIR SDK can grab the packages directly some how like:

AIR Descriptor

<apmExtensions>
   <extensionID>com.google.protobuflite</extensionID>
</apmExtensions>

Then sdk runs apm get to get the needed packages before compiling

Or even better make them use yaml:

dependencies:
   firebase_core: 1.2.0
   starling: 2.7.0

joshtynjala

leokan23 might be nice to have a dedicated site for apm packages (like pub.dev for flutter)

Like this? https://repository.airsdk.dev

ma

leokan23 Yep already underway with the repository site as Josh mentioned. It's just a basic backend for the client at the moment but we'll slowly add features to it.

Regarding the idea to scan your existing app descriptor, I'll add that to the list. 🙂 It's a good idea. Anything like this, feel free to add as an "enhancement" to the issues on the repository.

With the yaml idea, we chose a json format for the project, you can add your packages in manually:

...
"dependencies": [
        "com.package.example:1.0.0",
]
...

https://github.com/airsdk/apm/wiki/ProjectDefinition

leokan23

Awesome 🙂 there is already an APM Repository. ma JSON is also good. Yaml is basically the same so either work fine.

It is so nice to see apm starting.

MyFlashLabs

ma Congrats for the Beta launch 🍻 Although I have shut down MyFlashLabs and have shifted my concentrations to other stuff. I'd be more than happy to help developing this tool any time that I find 👏

ma

We just released the latest beta (v0.0.5), it's at a pretty functional level now I believe. Key points:

Project setup and initialisation;
Package installation and management;
Ability to "check and install updates" for apm directly;
Application descriptor generation;
There are over 50 packages in the repository and we should have the majority of distriqt's in there within the next month;
Harman will be pushing their PlayAssetDelivery ANE there shortly;

My favourite feature is the app descriptor generation. We have complete manifest additions / info additions / entitlements merging working so you can generate and update all the key parts for your application descriptor.

Really looking for real world testers so if anyone is keen to try it out, reach out and I'll help get you started!

I'm planning on doing some walkthroughs over the next few weeks of normal use cases too which hopefully will be a good starting point.

inverse

ma Will it manage three separate descriptors for desktop, ios and android?

leokan23

ma congrats for the new release.

I will add it in our latest app which use Firebase and Onesignal and see how it goes.

ma

inverse you can use apm to insert the additions into any specified app descriptor, it doesn't generate separate descriptors for each platform though. Perhaps could you explain your usage here a bit more so I can understand the need?

ma

leokan23 hey, those are the 2 extensions I'm planning on getting done next week so will be available soon.

« Previous Page Next Page »