# Display a window from one project in another project

**URL:** <https://forum.inductiveautomation.com/t/display-a-window-from-one-project-in-another-project/3951>\
**Category:** Ignition\
**Created:** [February 3, 2012, 3:50pm UTC](https://forum.inductiveautomation.com/t/display-a-window-from-one-project-in-another-project/3951 "2012-02-03T15:50:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@Robert](https://forum.inductiveautomation.com/u/Robert)\
**Post date:** [February 3, 2012, 3:50pm UTC](https://forum.inductiveautomation.com/t/display-a-window-from-one-project-in-another-project/3951/1 "2012-02-03T15:50:59Z")

</div>

We have customers with several projects on the same gateway. Each project has a number of common screens and a few custom screens. It would be really nice to be able to place all the common window in a common project so we only have to make a change in one place.

I know about retarget, but in this case we have a tab strip on a header. Some of the tabs open common screens, some open custom screens. Also, a number of the common screens are actually popups.

So what I’m looking for is `openWindowFromProject('project','window')` to open a foreign window in this project.

![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:") have to think how to handle common scripts the foreign window might reference ![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:")

---

<div class="post-metadata">

**Author:** ![AlexW](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@AlexW](https://forum.inductiveautomation.com/u/AlexW)\
**Post date:** [April 16, 2012, 5:07pm UTC](https://forum.inductiveautomation.com/t/display-a-window-from-one-project-in-another-project/3951/2 "2012-04-16T17:07:41Z")

</div>

+1

Would allow another means of flexibility in handling the problem described here  
[viewtopic.php?f=70&t=7952&p=25043#p250](http://www.inductiveautomation.com/forum/viewtopic.php?f=70&t=7952&p=25043#p250)

This way I could have plant specific projects for Ignition, and have a master project tieing in these various projects so that the wide area project delve into these subproject screens in a seamless manner