# \[Feature-789\] Perspective component extensibility

**URL:** <https://forum.inductiveautomation.com/t/feature-789-perspective-component-extensibility/29459>\
**Category:** Ignition\
**Created:** [October 28, 2019, 7:14pm UTC](https://forum.inductiveautomation.com/t/feature-789-perspective-component-extensibility/29459 "2019-10-28T19:14:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 28, 2019, 7:24pm UTC](https://forum.inductiveautomation.com/t/feature-789-perspective-component-extensibility/29459/2 "2019-10-28T19:24:11Z")

</div>

Basically, no. A deliberate design decision was made early in Perspective’s development to _not_ allow arbitrary Javascript to be written by someone in the designer - which would be your way to access “internals” like you can in Java Swing (caveat: not really, because React is in the way, but basically).

On the plus side, adding an external component to Perspective is, generally, easier than Vision - personally, I’d like to add some kind of easy builder that handles the (minimal) Java portions required and makes it easier for front-end-ey folks to just supply their own JS code much more easily.

---

_[View the full topic](https://forum.inductiveautomation.com/t/feature-789-perspective-component-extensibility/29459)._