Inspiring

Question

Are people just not using the broken "UXP developer tools?"

Forum|Forum|7 months ago
June 23, 2025
2 replies
1589 views

I’m writing a plug-in for InDesign, but I keep losing my JS code changes when I close the tool or ID crashes.

But in the editor, the code is marked as dirty when I make changes; and then that’s cleared when I “save” it. But if I look at the JS file on disk (using the dev tool’s “Open folder” command), it doesn’t reflect my changes.

There’s no “show in Explorer” option in the context menu in the left pane of the UXP tool, and “Copy link address” doesn’t work; it just copies the filename, not the path. And the “Filesystem” tab is useless: It contains nothing, and the “add folder to workspace” button does nothing.

So… are people just using some other tool and still littering their code with alerts to debug?

P

Philip Buckley

Participating Frequently

Hi,

I have posted a reply to your message in the Creative Cloud Developers Forum . . . assuming that it is you using "OscarG" as a username there! 😉

Philip

T

Thomas_CalvinAuthor

Inspiring

Yeah I wish Adobe would consolidate all of its "accounts." Oh well!

P

Philip Buckley

Participating Frequently

Hi Thomas,

There are two tabs at the top – Developer Workspace and Playground. I've never used the Playground tab, but I use the Developer Workspace tab all the time – to load, watch, and debug the plugins I am developing. I'm creating UXP plugins for InDesign. In my experience the UXP Developer Tools program works fine. I'm wondering how you have things set up and what your expectations of the program are.

Philip

T

Thomas_CalvinAuthor

Inspiring

Hi Philip,

Thanks for the reply. I'm using Developer Workspace also.

My expectations are to do exactly what you're doing. But the editor is not saving the code, despite claiming to.

If I edit something and press Save, I expect it to do so.

D

Dirk Becker

Legend

Oh yeah, it's clear at this point that the "editor" in "Developer Tools" is BS.

And agreed: The whole thing is pretty half-assed. I really wanted to use it for the debugger, because of the aforementioned lack of console output from stand-alone scripts. And it looked like it might be OK, but ID locks up more than half the time after you want to stop and reload anyway.

And what's with the lack of a "Run" or "Go" button? The environment is just so clumsy and irritating to use.

Are you aware of today's Developers Live event?

Beyond that, UDT also has a dedicated category in the separate Creative Cloud Developer forum, which also has an InDesign specific category (mostly covering InDesign UXP).

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded