How Enstone makes his ModMenu's

How Enstone makes his ModMenu's (Just brainstorming/ how I would do it if i where him)

#------------------------------------------Using ControlConsole/TMAPI------------------------------------------#

#) Note*: ControlConsole.pkg installs a config file @location: /dev_flash/sys/internal/config.cfg
#) Also Note*: ControlConsole.pkg allows "sys_dbg syscalls" and CCAPI edits the branch at that address to modify the code flow	using > ccapi.sprx and that config.cfg file.

#1) Made CCAPI + Controlconsole.pkg (✓)
#1) First create a C++ ModMenu that calls functions via ControlConsole(.pkg), and compiles it.

#2) Create a C#/VB/Managed C++ executable. (.NET based application)
Including login authentication (which may also be done in another C++ library via P-Invoking/Not likely, but plausible) (or PHPscript, More likely)
In the code of the (.NET) executable, it explicit-Invokes (/marsalls) the C++ CLI Modmenu, which P-Invokes CCAPI.DLL.

So...#: .NET EXE -> C++ CLI modmenu -> CCAPI.DLL

NOTE* This is just me brainstorming. Even if he doesn't do it this way, this way would be smart.
REASON: Since the C++ CLI Modmenu is native, and his CCAPI.DLL is native, the source is safe. While using the .NET aspect of it to get the look and feel of nice GUI, using a designer for convenience and efficiency.

OVERALL:
The modmenu's GUI's are programmed in .NET (CLR) -based language.
The modmenu's code itself is native, and invoked explicitly (/marsalls) via .NET (CLR).

Offa da dome by: BaSs_HaXoR