Skip to main content
S
SamLaundon
Inspiring
June 26, 2015
Answered

Installing Extension With Davide Barranca's Install Script

  • June 26, 2015
  • 1 reply
  • 2162 views

Davide Barranca has created a javascript that bypasses Adobe Extension Manager and allows you to create a script that installs extensions, scripts, ect. GO HERE for it.

My question is, I have two panels that I want to install with one script. Davide's script only allows one panel to be installed with the script. Is there a way to have another javascript run the first extension js script and then run the second extension script, so both install scripts are installed with one js script.

Thanks in advance for your help - Sam

This topic has been closed for replies.
Correct answer DBarranca

Hi Sam,

as a workaround you can duplicate the installer.jsx/ASSETS folder, and let the first installer.jsx call the second installer after he's done with the first panel, something like:

$.evalFile(File($.fileName).path + "/installer2.jsx");

this would basically chain the two installers (not very elegant I know!)

Also, you may want to have a look at the fine project of Max Penson here: Zxp Installer‌ which basically is his own native, open source version of Adobe Extension Manager (embedding the Adobe ExManCmd commandline utility which has not been discontinued like the GUI version).

For those living in a cave in the last week, Adobe Extension Manager doesn't support anymore CC2015, etc etc (see: HTML Panel Tips #17: CC2015 Survival Guide | Photoshop, etc.‌)

ZXP Installer works flawlessly, unless you've messed up the ExMan database with the CC app one (I happen to had them both screwed and it's been a majestic PITA for three days).

Shortly, Adobe has killed Extension Manager, transplanting his core into the CC app + the ExManCmd utility, both relying on the same database - Max is using the ExManCmd under the hood of his native application.

Myself, I've spent so many hours doing customer support for Extension Manager, that I personally prefer to use something different now - at least I can blame myself in case something goes wrong :-) but it's just a matter of personal preferences.

Hope this helps!

Davide Barranca

---

www.davidebarranca.com

www.cs-extensions.com

1 reply

DBarranca
DBarrancaCorrect answer
Legend
June 27, 2015

Hi Sam,

as a workaround you can duplicate the installer.jsx/ASSETS folder, and let the first installer.jsx call the second installer after he's done with the first panel, something like:

$.evalFile(File($.fileName).path + "/installer2.jsx");

this would basically chain the two installers (not very elegant I know!)

Also, you may want to have a look at the fine project of Max Penson here: Zxp Installer‌ which basically is his own native, open source version of Adobe Extension Manager (embedding the Adobe ExManCmd commandline utility which has not been discontinued like the GUI version).

For those living in a cave in the last week, Adobe Extension Manager doesn't support anymore CC2015, etc etc (see: HTML Panel Tips #17: CC2015 Survival Guide | Photoshop, etc.‌)

ZXP Installer works flawlessly, unless you've messed up the ExMan database with the CC app one (I happen to had them both screwed and it's been a majestic PITA for three days).

Shortly, Adobe has killed Extension Manager, transplanting his core into the CC app + the ExManCmd utility, both relying on the same database - Max is using the ExManCmd under the hood of his native application.

Myself, I've spent so many hours doing customer support for Extension Manager, that I personally prefer to use something different now - at least I can blame myself in case something goes wrong :-) but it's just a matter of personal preferences.

Hope this helps!

Davide Barranca

---

www.davidebarranca.com

www.cs-extensions.com

    S
    SamLaundonAuthor
    Inspiring
    June 27, 2015

    Hi Davide,

    Thanks for the info. I looked at Zxp installer and though it looks like it has possiblities, I like you method better. Unless I missed something, Zxp installer does not have an uninstaller like yours does.

    I actually was able to take your solution and make it work as one installer for two panels. I combined the two install scripts for each panel into one script. All I really had to do was have two different asset folders:

    ASSEST & ASSESTS to distinguish between the two panels. Works on both Windows 8 and Mac.

    One final note on what Adobe has been doing with 3rd party extensions. Though they say they support them, as you know they make it very difficult to get the extensions installed unless you go through Adobe Add-Ons where they take a sizable chunk of money if one is trying to sell the extension (on a $500 extension Adobe takes $143 - that is just not right). My users who buy my extension often do not have Photoshop. So by buying my extension they are directed to Adobe where they subscribe to Photoshop and Adobe gets another user through my extension. I am sure I am not the only extension developer out there who creates more customers for Adobe. Hello - Wake Up Adobe!

    Thanks again Davide, you have saved my ass again.

    Sam

    S
    SamLaundonAuthor
    Inspiring
    June 28, 2015

    More on the install Script by Davide Barranca.

    The beauty of this script is you do not need another app like Adobe Extension Manger to install the script. So all the user needs is photoshop plus the extension and the install script.

    My question is on a Mac and Windows I can choose which app opens the script. In my case I selected Photoshop CC 2015 on both Mac and Windows so when I double click the script the script will open in Photoshop and run. Is this just going to work on my computers? When a user downloads and runs the install script and double clicks it, will it automatically open Photoshop. It it does that is great. If it does not then I will have to include a readme to explain how to install the extension.

    Sam

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices