Feature Requests

Hi Today on my M1 the CreativeCloud was updated to Version 5.10.0.573When running in the command line:     "/Library/Application Support/Adobe/Adobe Desktop Common/RemoteComponents/UPI/UnifiedPluginInstallerAgent/UnifiedPluginInstallerAgent.app/Contents/MacOS/UnifiedPluginInstallerAgent" --list all       I got the following output Enabled       [PluginName] 1.4.2   On my x86-Mac with CC-Version 5.9.0.373, I get the following output:Enabled     [PluginName]       1.4.2.294 This means, that in the newer Version of CC the last Numbers of the Versions have disappeared.But this number is important, because it used to check whether a newer Version of the Plugin is available (I'm having a C++-Plugin and use UXP for the UI)Please bring the full version-number back.And, it would be nice if the version-Number of a Plugin can be shown also in the UI of Creative Cloud  

Hi, coders and Adobe members. Hi, looking at this thread: https://community.adobe.com/t5/photoshop-ecosystem-discussions/duplicate-one-layer-to-multiple-documents-images/m-p/11045121#M321918 , I see a trend that some users might share: trusting scripts. The OP is unsure about installing a script one could find online. I think that there are other issues: finding scripts, and understanding what they do, how to use them...   I really think that scripting is too scattered: There are scripts in this very forums, on private sites, on github, aescripts, etc. IMHO, there should be an Adobe repository of scripts and scriptlets that would be checked against malware, and organized, maybe integrated to the exchange? I know that it is a titanesque task, but it could be a huge benefit for the entire community. I know that ID has a panel with scritps from the community, and it should point to other scripts that users could download.   (I'm asking here, as most coders integrate scripts in t

Hello, We have an ECDSA (non-RSA) EV certificate we use to sign our code and we have no problem whatsoever using it for Java code signing (ECDSA has been supported in Java for a long time). However ZXPSignCmd refuses to use it:Error - Key is not in RSA format. Signing failed. ECDSA usage is more and more common and preferred to RSA these days so this is a missing functionality IMO. Is it possible to add suport for ECDSA in ZXPSignCmd? Thanks! 

Hi, I'm a semi-amateur developer who publishes a number of utility scripts for Bridge. I do have a listing on Exchange but it is WAY out of date, and my current versions are for the time being distributed on my Dropbox instead. This is mainly due to what I find to be an awkward and difficult official install process with zxp files and submitting updates. My main software is a script utility pack which is all in one folder, that is simply dropped into the Bridge Scripts folder. I also have a number of other specialized utilities, demos, and snippets that a user can install individually if they want. My suggestion is to overhaul the installation process and make it dead simple for both developers and end users to install from Exchange, especially when manual installation is simply drag and drop.   For those interested Bridge users, my Dropbox link is https://www.dropbox.com/sh/mg817g9a9ymbasi/AADTmXUVxmFfM58bcyYE7yiwa?dl=0