Apps

[evilC]

[Edit] So it seems that some of the functionality I mentioned is already present, so let me shift this slightly.

Ultimately, what I would love is some way that an "App" can be packaged including the dependencies into a single pkg file or whatever.

You then have a Setup.exe (still an ahk script though, but compiled) that serves as a "bootstrap" for ASPDM. Setup.exe contains ASPDM and can prepare the user's machine for ASPDM to do it's thing by doing such things as checking for horrible autohotkey.com ahk and advising user to remove it, or even containing a copy of AHK that is "known good" with the App.

The idea being, that even if the user as no net connection, they can install an ASPDM based "App" from one zip containing an EXE and a pkg.
Setup unpacks ASPDM and the dependencies, then kicks ASPDM off in a mode where it already has the Tool selected and the dependencies visible, the user just has to click "Install".

Once installed, and they have an internet connection, ASPDM can be used as normal to update etc.

If the user has a net connection while installing, and newer packages are available, give option to use packaged or downloaded.

This brings the user of a potential app neatly from "What is AHK?" land to the being user of an AHK App in one nice managed chain. As far as they are concerned, ASPDM is just the "Installer / Update manager" for the App.

[joedf]

Ahh, ok. So we need a sort of AppPacker tool, which pre-packages the package, all dependencies and ASPDM together...essentially, the App utilizes ASPDM as updater. It seems that adding a checkbox "Build as an App Package", would be cool idea.
Is that ok?