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?
Why Open Source ESTK?
- So the community can take care of its own needs
- It has become more important with CEP development
- Because it's not being maintained anymore?
Posted 1 year ago
I do not agree. Many photoshop scripters use ESTK for their retoucher teams. Even if they also build HTML5 extensions like me.
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).
Many—if not all—of us are coding in third-party editorsMany 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).
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.
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.
(Edited)
