iOS, move hipernate handling to LOkit interface

Hipernate means stopping LOkit but of course saving first if a
document is active

and returning means starting LOkit again.

for now the implementation is left as FIXME

Change-Id: Id9ea2b056e87caec13c1d3fe82d4623ca3901ef2

1 files changed, 22 insertions, 11 deletions

diff --git a/ios/LibreOfficeLight/LibreOfficeLight/DocumentController.swift b/ios/LibreOfficeLight/LibreOfficeLight/DocumentController.swift
index 39a49d2a01eb..c05da106344a 100755
--- a/ios/LibreOfficeLight/LibreOfficeLight/DocumentController.swift
+++ b/ios/LibreOfficeLight/LibreOfficeLight/DocumentController.swift
@@ -15,6 +15,28 @@ import UIKit
 // It is a delegate class to recieve Menu events as well as file handling events
 class DocumentController: UIViewController, MenuDelegate, UIDocumentBrowserViewControllerDelegate
 {
+    // Handling of Background (hipernate)
+    // iOS is not true multitasking, only 1 app can be active (foreground) at any time,
+    // therefore apps frequently are moved to the background.
+    // background really means hipernate by terminating all threads and solely keep the
+    // data
+
+    // Moving to hipernate
+    public func Hipernate() -> Void
+    {
+        BridgeLOkit_Hipernate()
+    }
+
+
+
+    // Moving back to foreground
+    public func LeaveHipernate() -> Void
+    {
+        BridgeLOkit_LeaveHipernate()
+    }
+
+
+
     // handling of PropertiesController
     // The PropertiesController is a left sidebar, that will scroll in when activated
     // The Controller handles manipulation of properties in the document
@@ -72,17 +94,6 @@ class DocumentController: UIViewController, MenuDelegate, UIDocumentBrowserViewC
         }
     }
 
-
-
-    // Handling of Background (hipernate)
-    public func Hipernate() -> Void
-    {
-    }
-
-    public func LeaveHipernate() -> Void
-    {
-    }
-
     // var currentDocumentName : String?