Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to CEP 11 ? #9

Open
sneaker333 opened this issue Oct 6, 2023 · 5 comments
Open

Upgrade to CEP 11 ? #9

sneaker333 opened this issue Oct 6, 2023 · 5 comments
Labels
enhancement New feature or request

Comments

@sneaker333
Copy link

I've tried installing this extension on an M1 ARM iMac and Photoshop 24.70 and found that it is possible to use the current release version but only if Photoshop is set to open under Rosetta due to the extension being classed as 'legacy'. It appears that CEP 11 is supported natively on ARM Photoshop, but not being a CEP developer I don't know what is involved to get this plugin to support it - is this something which is easily achievable or far more involved ?

@schroef
Copy link
Owner

schroef commented Oct 6, 2023

Well we could to just bump the version in the manifest file, this holds the data like name and app and versions needed.

I thought m1 arm would only run the new plugins. As far what I read about it.

I can make a an edit and tag you when I made this edit

@sneaker333
Copy link
Author

Maybe Adobe changed their mind over phasing out CEP for now .... it appears that it's still a current way of developing extensions and the latest version (11.1+) supports ARM ... https://blog.developer.adobe.com/cep-11-now-in-prereleases-446c0d2b76d5

@schroef
Copy link
Owner

schroef commented Oct 6, 2023

No they highly motivate dev's to transition to UXP. Kinda weird, since it still doesnt support everything CEP can do.

PS i dont see anyway why this version would not run properly. I mean this extension doesnt use nodejs and the settings it is supported to any photoshop from 2014 up.

About that CEP running natively, that is actually a custom chromium engine packed inside Photoshop. its basically the core of Google Chrome they use to run CEP panels

@schroef
Copy link
Owner

schroef commented Oct 6, 2023

What i can try is to use the 'csinterface' file v11 and check if other scripts are needed for this. Im shooting a bit in the dark with that, i cant test that high version of a photoshop

@schroef
Copy link
Owner

schroef commented Nov 7, 2023

@sneaker333
You tryout this branch, ive used CEP 11. Some state there is a CEP 11.1 version, but inside the csinsterface.js file it still says its v11.0.0. Perhaps they mean the Chromium engine on which CEP is running inside Photoshop

https://github.com/schroef/AnimDessin2/tree/cep-11-tryout/com.sbaril.animdessin2
You need to manually install this, on the main page you can read how to do this

Please not that CSSX needs to be 11

Debugging Unsigned Extensions
If you are in the midst of development and want to bypass the need to sign your extensions, you can bypass the check for extension signatures by editing the CSXS preference properties file, located at:

  • Win: regedit > HKEY_CURRENT_USER/Software/Adobe/CSXS.11, then add a new entry PlayerDebugMode of type "string" with the value of "1".

  • macOS: In the terminal, type: defaults write com.adobe.CSXS.11 PlayerDebugMode 1 (The plist is also located at /Users/<username>/Library/Preferences/com.adobe.CSXS.11.plist)

These entries will enable debug extensions to be displayed in the host applications. Please note that, CSXS.11 is given with the assumption that, you are developing the extension for CEP 11. If you are developing extension for previous version of CEP, replace 11 with corresponding version number.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants