Open Source Extendscript Toolkit (ESTK)

  • 9
  • Idea
  • Updated 2 years ago
The Extendscript Toolkit is an inferior editor in comparison to the code editors we have come accustomed to. Many—if not all—of us are coding in third-party editors. The only thing ESTK is good for are its object browser and profiling tools, even though these also lack many features to todays standards.

Why Open Source ESTK?
  1. So the community can take care of its own needs
  2. It has become more important with CEP development
  3. Because it's not being maintained anymore?
Photo of Remco Janssen

Remco Janssen

  • 3 Posts
  • 0 Reply Likes
  • Hopeful

Posted 2 years ago

  • 9
Photo of Zack Lovatt

Zack Lovatt

  • 1 Post
  • 2 Reply Likes
+1 to this!

The community can do great things given a push; on the After Effects side, a few of us developers have recently made an online version of the documentation and done the legwork of keeping it updated -- -- this sort of initiative, if brought to the ESTK, can hopefully push progress on something that feels otherwise abandoned.
Photo of Pedro Marques

Pedro Marques

  • 163 Posts
  • 25 Reply Likes
I do not agree. Many photoshop scripters use ESTK for their retoucher teams. Even if they also build HTML5 extensions like me.
Many—if not all—of us are coding in third-party editors
Many are using ESTK. If you do not want to use it, ignore it.
I might be smarter that Adobe could give more support to those who want to be upgraded somehow for new third-party editors that have real connection with the all normal and hidden classes within photoshop (my case).
Photo of Remco Janssen

Remco Janssen

  • 3 Posts
  • 0 Reply Likes
It's impossible to ignore due to its object browser. You could use alert(), but that's not a serious alternative. I find it hard to imagine anyone working in ESTK on a daily basis.

I'd love to see a better solution to access the object manager for users that are not on ESTK, but still, open sourcing ESTK will be the fastest way to that solution IMO.