Re: CEP panels create dialog window

erinferinferinf · ‎May 29, 2019

I asked around a bit, and apparently there's no "Dialog" object inside of "regular" Illustrator ExtendScript: [InDesign has a more] sophisticated scripting interface so it has it's 'own' ScriptUI built-in and also ScriptUI could be used in it as well - whereas in Illustrator we've just got the regular ScriptUI available Thanks to Silly-V

erinferinferinf · ‎May 21, 2019

Hi Lavie, Here are two beginner-ish guides for getting started with CEP extensions that you might find useful: GitHub - Adobe-CEP/Getting-Started-guides: Getting Started guides and samples for CEP extensions GitHub - Adobe-CEP/CEP-Resources: Tools and documentation for building Creative Cloud app extensions with CEP The ExtendScript VSCode plugin is so new it might not get mentioned in either guide. As for: Could you please point me to al list of all the VSCode plugins I'd need to start maintaining/writing CC Extensions, and documentation for the process? Theoretically you could just build with this one, but others have found this plugin helpful: ExtendScript - Visual Studio Marketplace. It's up to date and actively maintained. The web is filled with lists like this one, blog entries by developers recommending general VSCode plugins. The only ones from that list that I have tried are ESLint and Prettier. Sometimes it's necessary to disable and enable certain VSCode plugins, depending on what you're doing. A couple days ago this person mentioned their own bootstrapping tool, which I haven't tried yet, and it will probably generate something complicated from the looks of it: https://forums.adobe.com/message/11065508#1106550z I hope this is helpful!

erinferinferinf · ‎May 20, 2019

Hi bagonterman, You shouldn't have to sign in or sign up to medium.com to read that article. Here is a "Friend Link" that ought to guarantee you can read it. Unfortunately that's the only page with UXP information at the moment, but we hope to have more articles about it soon, and better support pages. To give you some idea, here are the Adobe XD docs. Adobe XD's APIs are built on UXP, which is continuing to evolve. XD's documentation doesn’t yet differentiate between “UXP APIs” and “Xd APIs,” so, for now, the easiest way to make the distinction is this: UI and anything that looks like a Node or Web API is UXP. File I/O and anything behind require("uxp") is also UXP. Everything else is XD. (commands, scenegraph, application, etc.) I hope this is helpful! I'm not pleased with medium.com either, and hope that we will eventually migrate the Tech Blog content to a new home. However, that is unlikely within this calendar year. Kind Regards, Erin

erinferinferinf · ‎May 20, 2019

Hi mlavie, Welcome to the wonderful world of Visual Studio Code! You're definitely going to want to install our new ExtendScript Debugger plugin, which takes over some of the functionality of ExtendScript ToolKit. Why weren't you using ExtendScript ToolKit instead of Extension Builder 3? Was ESTK too new for your purposes? Unfortunately, the ExtendScript Debugger plugin is not the most stable yet, it's brand new. Fortunately, a new build is coming out this week, at least in our prerelease group. Definitely join that group, there are many expert CEP developers in it who can help answer your questions. Also, here are some tips for getting started on our blog. By the way, the following steps are good standard troubleshooting, as well as troubleshooting "Error ##15 Can't initialize target." Make sure the ESTK stand-alone application is closed Close the target application (example: Photoshop) Close Visual Studio Code Make sure there are no VS "Code Helper" processes in the Activity Monitor (Mac) or Task Manager (Windows) Restart Visual Studio Code Does it work then? If not, does a reboot help? You can let ask us questions and give feedback here in this forum.

erinferinferinf · ‎May 16, 2019

Hi Tim! I just saw a pull request for a more specific error message, so we're working on this. Meanwhile... In the current version only one instance of the plugin works at a time. So you can't have two VSCode workspaces open, with one targeting InDesign and the other targeting Photoshop. Have you tried following the following troubleshooting steps? Make sure the ExtendScript ToolKit stand-alone application is closed Close the target application (or in your case all the target applications) Close Visual Studio Code Make sure there are no VS "Code Helper" processes in the Activity Monitor (Mac) or Task Manager (Windows) Restart Visual Studio Code Does it work then? If not, does a reboot help? Let us know!

erinferinferinf · ‎May 15, 2019

Or this one! GitHub - Adobe-CEP/Getting-Started-guides: Getting Started guides and samples for CEP extensions

erinferinferinf · ‎May 15, 2019

bagonterman wrote Can you tell me when Adobe will be updating there node version? And or when they will be ES6 compliant? This is a big topic! Right now, panels are built using CEP 9, which, as you know, is compatible with a certain version of node. CEP 9 came out around Adobe MAX last year. Although the CEP team might do a CEF upgrade at some point, there are not currently plans for CEP 10. Instead, we've begun a major transition from CEP to an ES6 compliant platform called UXP. UXP is being implemented on a product-by-product basis. There is not a date for InDesign to begin using UXP at this time. Several other products will come first. If you'd like to get news in advance, please join our Creative Cloud Developer prerelease program. Also, follow the Adobe Tech Blog and/or sign up for the monthly developer newsletter.

erinferinferinf · ‎May 14, 2019

Hi @bagonterman! I think you do, if you're using InDesign 2019, like in this chart: CEP-Resources/CEP 9.0 HTML Extension Cookbook.md at master · Adobe-CEP/CEP-Resources · GitHub Let us know if it works!

erinferinferinf · ‎May 13, 2019

Hi Max, That's what I thought at first, too. @bbb tried really hard to make that happen and it didn't pan out. I think the ExtendScript Visual Studio Code plugin was in the works before this error popped up. Sure, the plugin doesn't have all of the functionality of the original ESTK, but in the near future large parts of it will be open source. Eventually macOS will drop support for 32 bit applications, and ExtendScript ToolKit will stop working. For several months after I started at Adobe I tried to find someone who would repackage the ESTK .dmg installer, because as of High Sierra, you have to install it in a pretty hacky way. (It's also my understanding that ever since Retina displays came out, ESTK has just looked worse and worse... ) I never found anyone, and eventually the #1116 error popped up.

erinferinferinf · ‎May 13, 2019

Hi Max, That's what I thought at first, too. @bbb tried really hard to make that happen and it didn't pan out. I think the solution that was in the works before this problem was to make this ExtendScript Visual Studio Code plugin. It doesn't have all of the functionality of the original ESTK, but in the near future large parts of it will be open source. I've seen many developers in the community try the new plugin, and keep using the old ToolKit. (Don't try to run both at the same time, by the way.) Eventually macOS will drop support for 32 bit applications, and ExtendScript ToolKit will stop working.

erinferinferinf · ‎May 13, 2019

Hi yehudan37348595, Have you checked to see if the debug mode is turned on or off on both the macOS system you checked it on that the Windows machine? Does the installation fail if you install via another method, like Anastasiy's Extension Manager? Sometimes people run into problems during the signing itself. ZXPSign doesn't like invisible files in your directory (like a .github directory or a .debug file). Others report problems with Windows filepath issues, or using non-English characters or spaces. Perhaps take a look at this blog entry, or our guide here, and see if those are helpful.

erinferinferinf · ‎May 08, 2019

Hi @query@mindfire, Could you provide some code examples of where your communication between your extension and plugin are breaking down? You could try reading Davide Barranca's Adobe Photoshop HTML Panels Development book, in which chapter 7 covers events, and the breakdown between host application events, CEP events, ExtendScript events, custom ExtendScript events that are sometimes called PlugPlug events, and panel events themselves. (Davide also offers courses and hangs out in this forum sometimes.) Because there are so many event types to listen for, a more concrete example of the workflow you're trying to accomplish might help us point you in the right direction, too.

erinferinferinf · ‎May 06, 2019

Hi @editsupport, We've found that Adobe Enterprise users seem to have problems with exmancmd and Exchange distributed extensions, throwing the 602 error and not working with Anastasiy's Extension manager. The fix for this is messy, and it doesn't originate from Adobe. One of our partners came up with this process to fix the same problem: 1. Quit all running Adobe Applications. 2. Quit all the process including the one for Creative Cloud from task manager. Look for it in the Task Manager. 3. Delete or Rename this file from local machine: Windows= C:\Users\<your_username>\AppData\Local\Adobe\OOBE\opm.db OR Mac OS = /Users/***/Library/Application\ Support/Adobe/OOBE/opm.db 4. Re-launch the Creative Cloud desktop app and sign in. 5. opm.db will be created again automatically. 6. The extension should automatically reinstall. This might take a couple of minutes we've heard 2 to 10 mins. If you don’t get notifications in your CC desktop client app, check for folder and files created at C:\Program Files (x86)\Common Files\Adobe\CEP\extensions that appear to be related to frame.io 7. If folder files are present then, try looking for them in Premiere 8. If step 6 fails, quit Premiere and try to re-acquire the addon. This means in the CC Exchange click uninstall and then install on the extension again. I'm very curious to see if this fix works for you.

erinferinferinf · ‎May 03, 2019

Hi there, So... I asked around and perhaps there is nothing particularly special about htts.requests in CC 2015. Have you had any luck following basic HTTPS file upload guides like this one? Let us know if you've made progress!

erinferinferinf · ‎Apr 23, 2019

Hi there sven-vm! When it comes to Premiere Pro, there are a few more public guides than with the other apps, so you're in luck. Have you seen this GitHub repo? It contains an official up-to-date Premiere sample panel. There's also this Premiere Pro Scripting Guide from Aenhancers.com. Let us know in this thread if you don't find what you're looking for! Usually @bbb chimes in on Premiere Pro questions. Good luck!

erinferinferinf · ‎Apr 19, 2019

Hi e-specdev, I'm sorry that the reply wasn't as helpful as you'd hoped. I'm on a team that's working to improve the developer experience for developers like yourself, and this kind of feedback is helpful. So the problem here is that a feature that you liked about listings on the Exchange has been removed: Previously you can publish it as private and then test installing as if you were a user logging on to Exchange. They took away the private option so I want to know how to try it prior to making it public! And now you're upset because you can't test the install of your .zxp in exactly the same way the Exchange will install it. Have I got that right? So in part, this is a feature request: "Add back the private publish feature" And two questions: "...how do I test my zxp since there is no longer a private option? When I create my listing and download the zxp during "preview" nothing happens; does preview actually install the extension or does the listing require publication first?" The review team tested your extension for you and assured you it worked. However, I can understand where you want a private preview option. tomzag sounds correct in answering "No" to this part: "does preview actually install the extension?" I'll note your feature request for the Exchange team.

erinferinferinf · ‎Apr 19, 2019

Hi Aysnandhini! This is a compatibility problem. Please refer to these two charts. InDesign 2015 uses CEP 6, which is only compatible with Node IO.js 1.2.0. Unfortunately, I don't know enough about Node to solve your problem, but hopefully this will point you in the right direction. You might also want to check out our article on running a Node server in a panel. Best of luck!

erinferinferinf · ‎Apr 12, 2019

The new release just came out, so please give it a try and let us know if it's improved!

erinferinferinf · ‎Apr 12, 2019

Hello there! VSCode 1.33 came out this week, and caused some problems with the ExtendScript Debugger plugin. Just in time, we have released version 1.0.1 of the plugin. This is the stable Windows release Other stability issues (cross-platform) have been addressed Compatible with VSCode 1.33 Here are some more notes, quoted from the Adobe Tech Blog: Changelog New features: Added support for continuing execution after clearing a runtime error. By default, a “Clear Runtime Error” dialog will be shown. If you don’t want to see the dialog every time, you can set the default behavior using the clearRuntimeError launch configuration. Set true to always continue execution, false otherwise. Now shows a “Save file” picker for Export to JSXBIN. Fixes: Fixed issues when running in Visual Studio Code 1.33.0. For example, scripts in earlier versions may have run only once for certain configurations. Fixed the case where ExtendScript Toolkit opened when $.writeln was used more than 500 times in a loop. Fixed a race condition which sometimes left the extension in an inconsistent state. Please continue to let us know about bugs and issues in this forum.

erinferinferinf · ‎Apr 12, 2019

This is a fine place to ask that question! DavideBarranca has some Action scripting in his HTML Panels book that you might find useful. He also links to this handy code in his github, which might be helpful for you. You'll need the name of the actions, as well as the name of the Action set they are in, and you should be able to call `app.doAction()` on a random one using some of Trevor's methods above.

erinferinferinf · ‎Apr 10, 2019

So if you're using the VSCode plugin on Windows, it's not a stable release, even though you can install it. The stable Windows build ought to be out by the end of the week. Also this week VSCode 1.33 broke the ExtendScript Debugger plugin entirely, the release at the end of the week ought to fix it. In general the next release ought to be more stable.

erinferinferinf · ‎Apr 09, 2019

Silly-V wrote By the way, it's super annoying how multiple windows of VSCode have to be closed and re-opened to switch the debug session to another product. Multiple debug sessions is a noted feature request. I think I got the latest VSCode add-on right, unless there's another place to get a new-er update? We're expecting an updated version tomorrow.

erinferinferinf · ‎Mar 15, 2019

Hi there filipinto! Is it the case that you used to be able to batch edit with Nik Color Efex before updating Photoshop or your Mac? If it's a Photoshop version problem, you could try re-installing a previous version of Photoshop using these instructions. Then you could try batching and at least narrow down the problem. Has anyone reading this thread tried contacting Nik Efex support with a link to this thread? I can tweet at them, but I'm not a paid user so I can't open a support request. Let me know what you try!

erinferinferinf · ‎Mar 06, 2019

Hi @riccardom15921476 , This particular forum is for plugins and extensions hosted on the Adobe Exchange. Are you making a plugin of some sort? Is this an Acrobat question? If so, the forum moderators might consider moving this post to Acrobat Scripting or the Acrobat SDK area. Regardless, here's an older thread about GetAnnots() that might be helpful. Hope this is helpful!

erinferinferinf · ‎Mar 05, 2019

Hi junkos87377808! That sounds annoying. Could you please clarify; when you say you can't download applications, are you talking about Creative Cloud apps (like Photoshop, etc.) that you can't download from the Creative Cloud desktop app (the drop down menu)? If so this is really the wrong forum area, this forum is about plugins and extensions in the Adobe Exchange... Are you talking about the Adobe Exchange specifically? Thanks!

erinferinferinf · ‎Feb 28, 2019

Wait a second, I wrote a lot of the FAQ... In the "Troubleshooting" section of the VSCode Marketplace page it's the first bullet point: Make sure the ESTK stand-alone application is closed Granted, in the VSCode app I found it's a lot of scrolling past large gifs to see that.

erinferinferinf · ‎Feb 28, 2019

Hi there wickedtall person! Sorry about how late this reply is... did you ever figure it out? I have a couple of resources that might help you out if you're still facing this issue. First of all, it's my understanding that topcoat is depreciated. You might want to try out spectrum-css, which was very recently open sourced. Here are the docs. Also check out this article on Spectrum by DBarranca As for quitting and restarting Photoshop to test the changes, that is, indeed, a slow and frustrating process. I wound up creating the following image in order to remember how it worked for this article: Turns out this is true for Photoshop, but in After Effects and Premiere Pro you only need to close and open your panel. Right now you're using CEP to build a Photoshop panel, but soon we how to bring UXP to Photoshop, which will, eventually, make the panel/extension development process much faster, with far fewer app restarts and easier-to-use UI elements. I know none of this directly answers your question but I hope it's somewhat helpful. Let me know! - Erin

erinferinferinf · ‎Feb 26, 2019

Hi Narayan, Sorry about the delayed response time. Have you seen this Chrome compatibility chart in the documentation? It might be helpful. Generally speaking, if this is a CEP problem or an InDesign problem, and it's fixed in the 2018 versions, usually there's not much you can do about the problems in 2017. That said, I'll also ask the the teams about your issue. Best, Erin

erinferinferinf · ‎Feb 26, 2019

Hi there David, Particle Builder is a third party plugin, right? Have you tried contacting Pixflow directly? I can try and get some other folks to weigh in on the problem but thought I'd ask about that first. Also what OS and version of AE are you using? Best, Erin

erinferinferinf · ‎Feb 26, 2019

Hi OhmsG! Have you seen our article on running a Node.js server in a panel? It might be helpful: https://medium.com/adobetech/how-to-build-a-node-js-server-in-a-panel-ba1d63ea67e2 I have also encountered that error, `cannot read property 'evalScript' of undefined`... Let me know if this helps!

erinferinferinf

erinferinferinf

Activity

Re: CEP panels create dialog window

Re: Continuing Developing Legacy Projects: Recomme...

Re: InDesign Extension sqlite3 looking in the wron...

Re: Continuing Developing Legacy Projects: Recomme...

Re: [ES Debugger] Can't launch script using Photos...

Re: Getting started?

Re: InDesign Extension sqlite3 looking in the wron...

Re: InDesign Extension sqlite3 looking in the wron...

Re: Extendscript Toolkit: Error Message "(#1116) C...

Re: Extendscript Toolkit: Error Message "(#1116) C...

Re: Self-signed Extension signature not valid on W...

Re: Photoshop Hybrid Extension

Re: ZXP not installable - return 602 error - enter...

Re: Socket hang up error with nodejs in indesign20...

Re: How to import downloaded files into Premiere p...

Re: ZXP download during listing preview

Re: Socket hang up error with nodejs in indesign20...

Re: Instabilities in VS Code ExtendScript Debugger

ExtendScript Debugger for Visual Studio Code 1.0.1...

Re: Random Selection of Actions with Script. Possi...

Re: Instabilities in VS Code ExtendScript Debugger

Re: (#15)Can't initialize target. [VSCode ES Debug...

Re: Nik Color Efex cannot batch edit with CC 2018 ...

Re: Error trying to set parameters in GetAnnots() ...

Re: Download problem

Re: (#15)Can't initialize target. [VSCode ES Debug...

Re: Button and Checkbox scope with Topcoat

Re: Error related to SSL/TLS version

Re: Problem with Particle Builder

Re: CEP illustrator run js file