Merge pull request #27 from WebPlatformForEmbedded/development/METROL-949

Renaming WPEFramework to Thunder

Author: MFransen69

.gitignore

@@ -4,4 +4,4 @@ Launcher.json
 Makefile
 cmake_install.cmake
 install_manifest.txt
-libWPEFrameworkLauncher.so
+libThunderLauncher.so

CMakeLists.txt

@@ -2,7 +2,7 @@ cmake_minimum_required(VERSION 3.3)
 
 project(Launcher)
 
-find_package(WPEFramework)
+find_package(Thunder)
 
 set(MODULE_NAME ${NAMESPACE}${PROJECT_NAME})
 

Launcher.cpp

@@ -1,7 +1,7 @@
 #include "Launcher.h"
 #include <inttypes.h>
 
-namespace WPEFramework {
+namespace Thunder {
 
 ENUM_CONVERSION_BEGIN(Plugin::Launcher::mode)
 
@@ -192,4 +192,4 @@ bool Launcher::ScheduleParameters(const Config& config, string& message, Core::T
 
 } //namespace Plugin
 
-} // namespace WPEFramework
+} // namespace Thunder

Launcher.h

@@ -5,7 +5,7 @@
 #include <linux/cn_proc.h>
 #include <vector>
 
-namespace WPEFramework {
+namespace Thunder {
 namespace Plugin {
 
 class Launcher : public PluginHost::IPlugin {
@@ -767,7 +767,7 @@ class Launcher : public PluginHost::IPlugin {
     // The lifetime of the Service object is guaranteed till the deinitialize method is called.
     const string Initialize(PluginHost::IShell* service) override;
 
-    // The plugin is unloaded from WPEFramework. This is call allows the module to notify clients
+    // The plugin is unloaded from Thunder. This is call allows the module to notify clients
     // or to persist information if needed. After this call the plugin will unlink from the service path
     // and be deactivated. The Service object is the same as passed in during the Initialize.
     // After theis call, the lifetime of the Service object ends.
@@ -792,5 +792,5 @@ class Launcher : public PluginHost::IPlugin {
 };
 
 } //namespace Plugin
-} //namespace WPEFramework
+} //namespace Thunder
 

README.md

@@ -6,12 +6,12 @@ Plugin to "Launch" linux applications and scripts
 
 ### How to launch a script/application
 
-1. Build launcher plugin. It create /usr/lib/wpeframework/plugins/libWPEFrameworkLauncher.so and /root/etc/WPEFramework/plugins/Launcher.json
+1. Build launcher plugin. It create /usr/lib/thunder/plugins/libThunderLauncher.so and /root/etc/Thunder/plugins/Launcher.json
 
    Generated Launcher.json contains,
    ```
    {
-     "locator":"libWPEFrameworkLauncher.so",
+     "locator":"libThunderLauncher.so",
      "classname":"Launcher",
      "precondition":[
        "Platform"
@@ -25,7 +25,7 @@ Plugin to "Launch" linux applications and scripts
    E.g. to run command < `du -a /etc` >
    ```
    {
-      "locator":"libWPEFrameworkLauncher.so",
+      "locator":"libThunderLauncher.so",
       "classname":"Launcher",
       "precondition":[
         "Platform"
@@ -42,7 +42,7 @@ Plugin to "Launch" linux applications and scripts
    E.g. to run < `du -a /etc -h` >
    ```
    {
-      "locator":"libWPEFrameworkLauncher.so",
+      "locator":"libThunderLauncher.so",
       "classname":"Launcher",
       "precondition":[
         "Platform"
@@ -139,7 +139,7 @@ Note:
 
    ```
    {
-      "locator":"libWPEFrameworkLauncher.so",
+      "locator":"libThunderLauncher.so",
       "classname":"Launcher",
       "precondition":[
         "Platform"
@@ -162,5 +162,5 @@ E.g.
 
 3. Create testapp3.json by copying Launcher.json (cp Launcher.json testapp3.json) and update with proper commands and options/values
 
-4. Run WPEFramework
+4. Run Thunder