Some hacks to make launchApp() work from the shell

AtkinsSJ commented 7 months ago

Add the shell's puter.app_instance_id to the shell iframe src. This makes puter.js thinks Phoenix is an app, and tries to post its messages. It also means the terminal receives response messages and can pass them back.
In the message event listener, pass any messages we don't handle, either up to the Puter GUI, or down to Phoenix, so they can communicate.

I think ideally, we would somehow launch Phoenix as a child app, and it would get some kind of direct connection to Puter, in addition to its connection to Terminal.

cc: @KernelDeimos

AtkinsSJ commented 7 months ago

~See also https://github.com/HeyPuter/puter.js/pull/8 which is required to let Phoenix know the app has launched and it can proceed.~

EDIT: It's merged! :tada:

AtkinsSJ commented 7 months ago

Discarding in favour of #9, making Phoenix a child app of Terminal, which renders this obsolete. (And is much less hacky!)

HeyPuter / terminal

Some hacks to make launchApp() work from the shell #8