docs (#313)

Author: davidhozic

docs/images/daf-gui-front.png

@@ -13,7 +13,8 @@ While the Schema tab allows user to pre-define a schema, the GUI also has a sect
 
 Live view allows users to view and update objects that are currently loaded into the framework.
 It allows users to modify the original object parameters and then reinitialize the object to use those same
-parameters. This can be done by clicking on the *Update* button.
+parameters. This can be done by clicking on the *Update* button. Next to the *Update* button, there is a 
+*Refresh* button which will reload the GUI with updated values.
 
 If an object does not have a *Update* button, that means the object is not directly supported for live modifications.
 In the latter case, users must click the *Save* button, until edit for an object, which supports 
@@ -23,7 +24,7 @@ to the list.
 
 .. image:: ./images/gui-live-view-edit-account.png
     :align: center
-    :width: 15cm
+    :width: 10cm
 
 
 At the top of the *Live view* tab, there's also an *Execute* button with a dropdown menu. It allows you to define a new

docs/source/guide/GUI/images/gui-live-view-add-object.png

@@ -23,6 +23,7 @@ GUI structure
 The GUI consists of:
 
 - START and STOP buttons starting and stopping DAF's core,
+- Optional modules tab - Where you can install optional functionallity
 - Schema definition tab - Where you can define accounts, guilds, messages & type of logging:
 
   - Accounts - Section for defining your accounts (and guilds and messages).

docs/source/guide/GUI/images/gui-live-view-edit-account.png

@@ -194,6 +194,14 @@ The *Load all at start* checkbox causes (when checked) the GUI to load all the a
 button in the top left corner is pressed. If the checkbox is not checked, accounts can be loaded by
 selecting them in the list and then clicking on the *Load selection to live* button.
 
+The *Preserve state on shutdown* checkbox sets the ``save_to_file`` parameter inside :func:`~daf.core.run` to True if checked
+or False if not checked. Basically this means that if the checkbox is checked, DAF will save the accounts list (and guilds, messages, ...)
+to a binary file on DAF shutdown and every 2 minutes to prevent data loss on force shutdown.
+When starting DAF again, the same list will be loaded from file into DAF.
+
+State preservation is not really meant as a shilling feature where you can define the schema statically inside the GUI and save it to a JSON file,
+but it's meant to be used in case DAF will have accounts, guilds, messages dynamically added while it's running (added in *Live view*).
+
 If *Import from live* is pressed, the GUI will copy the accounts loaded inside daf into our list.
 
 Logger is automatically loaded at start and cannot be changed for a different logger without stopping the framework first.

docs/source/guide/GUI/images/gui-load-accounts-bnts.png

@@ -82,6 +82,16 @@ Function :func:`~daf.core.run` accepts many parameters but there is only one tha
 
         daf.run(accounts=accounts)
 
+.. _objects_in_file_ref:
+.. note::
+    
+    DAF also supports the accounts list to be **saved to file** or **restored from file** on startup.
+    
+    This behaviour can be enabled by setting the ``save_to_file`` parameter to ``True``.
+    Please note that when this is set to ``True``, the framework will first load the accounts from file
+    and then also load accounts present in the ``accounts`` parameter, which will result in *Account already added*
+    warnings if the same account has been backed up to file before.
+
 
 After you've successfully defined your accounts list and started the framework with :func:`~daf.core.run`, the framework will run on it's own and there is nothing you need to do
 from this point forward if basic periodic shilling with text messages is all you desire.