run processes as applets about twili HOT 6 CLOSED

This is currently blocked on applet services. I may want to see if there is a way to register an existing process as an applet, or if I can launch processes through applet services and hide them from crash handling a different way.

from twili.

CreateSelfLibraryAppletCreatorForDevelop sounds promising, but it gives me error 0x7a880 on hardware (2.0.0 console). Might take some work to figure out if there's a way around that.

from twili.

If we're going to be having applet services launch our processes, there are a number of problems, for which to solve we will likely have to depend on Atmosphere-PM/LDR.

I don't see a way to get pm to not signal a crash event, unless we were willing to race NS, hoping we get to use pm:shell#ClearProcessNotificationFlag before NS receives the crash event. This seems like a bad idea™ to me and would likely be somewhat fragile. We'll have to either make Atmosphere-PM hide the crash event, or look into whether there's any way to get ns to not trigger a fatal error upon receiving a crash event. ns:dev sounds promising.

from twili.

I've gotten nx-hbmenu to work under Twili by using a combination of two processes. Turns out, applet services don't much care who calls OpenApplicationProxy. Because of this, we can use one process to open the application proxy, retrieve IDebugFunctions, and close the application proxy. Then, we can launch the main application (in this case, nx-hbmenu). The application will wait for the "acquire foreground" message. We can cause this message to be sent by using IDebugFunctions to OpenMainApplication, and then calling IApplicationAccessor#RequestForApplicationToGetForeground.

Problems:

• qlaunch gets confused by there being an application running
• exiting the application freezes up UI
• I'm not really sure how OpenApplicationProxy actually works. Does it create a new IntegratedApplication object every time? Does the IApplicationAccessor returned by IDebugFunctions#OpenMainApplication access a different application object, or is it the same one every time shared by multiple processes opening the application proxy?
  • Because of this, I'm not sure when exactly I can RequestForApplicationToGetForeground and have it work

from twili.

Temporary solution, for 3.0.0+:

• Override creport with a stub to notify Twili when a process crashes instead of causing a fatal error.
• Override album with a stub ("shadowbeast")
  • Control Mode: The first instance of shadowbeast runs in control mode, where it receives messages from Twili that tell it to launch more shadowbeast instances whenever Twili receives an NRO to be run in applet mode.
  • Host Mode: Any instances of shadowbeast launched by the control instance will connect to Twili, query the size of the NRO, use svcMapPhysicalMemory to allocate a buffer, and then have Twili map in the NRO. Shadowbeast host mode combines the function of Twili's process creation and HBABIShim.

from twili.

Finally works 🎉

from twili.