Create separated candidate process to preload NUI (#245) accepted/tizen/unified/20200703.155019 submit/tizen/20200703.075955 submit/tizen_5.5/20200629.221218
author조웅석/Common Platform Lab(SR)/Principal Engineer/삼성전자 <ws77.cho@samsung.com>
Thu, 2 Jul 2020 02:33:16 +0000 (11:33 +0900)
committer이형주/Common Platform Lab(SR)/Staff Engineer/삼성전자 <leee.lee@samsung.com>
Thu, 2 Jul 2020 02:33:16 +0000 (11:33 +0900)
commit9cd33b548799aa1159403c599ff013c29fcb85a1
treeab9241c47f597a94bc913c2ec5dbdeb06319a8d7
parent4612d67f7a95eed0edf08f53a16a5c03fd18589a
Create separated candidate process to preload NUI (#245)

NUI cannot be preloaded with ElmSharp because those two UI related
module create window while preloading.

When multiple windows are created, it not only increases the memory usage,
but also affects the launching effect and splash screen.

So, create new candidate process for NUI

Assumption
  NUI app has their own apptype "dotnet-nui"
  There are two candidate process. One is for "ElmSharp" and The other is for "NUI"
  XSF is related to "ElmSharp"

Basic Operation
  Set extra value "TIZEN_UIFW" to bundle by loader script. (ElmSharp and NUI)
  Get extra value from bundle in the *__loader_create_cb function and set that to environment.
  Get environment in the preload() method in the Tizen.Runtime.cs
  Skip "ElmSharp" or "NUI" preloading by TIZEN_UIFW
Managed/Tizen.Runtime/Preloader.cs
NativeLauncher/CMakeLists.txt
NativeLauncher/dotnet-nui.debugger [new file with mode: 0644]
NativeLauncher/dotnet-nui.launcher [new file with mode: 0644]
NativeLauncher/dotnet-nui.loader [new file with mode: 0644]
NativeLauncher/dotnet.loader
NativeLauncher/launcher/exec/loader.cc
packaging/dotnet-launcher.spec