Scheduler: Remove obsolete 'Scheduler' class

[senf.git] / Console / Mainpage.dox

diff --git a/Console/Mainpage.dox b/Console/Mainpage.dox
index b0440b0..b1636e3 100644 (file)
--- a/Console/Mainpage.dox
+++ b/Console/Mainpage.dox
@@ -87,7 +87,7 @@
             .name("someServer");
 
         // Run the scheduler
-       senf::Scheduler::instance().process();
+       senf::scheduler::process();
     }
     \endcode
 
@@ -118,12 +118,12 @@
     \see \ref console_testserver for a complete example application
 
 
-    \section intro_usage Access
+    \section intro_usage Using the Console: Configuration files, Network console, ...
 
     There are several ways to access the node tree:
     \li By parsing configuration files
     \li By parsing command line parameters
-    \li By providing interactive console access
+    \li By providing interactive or non-interactive network console access
 
     \see console_access
 
@@ -138,7 +138,7 @@
     \see \ref node_tree
 
 
-    \section intro_commands Registering console/config commands
+    \section intro_commands Implementing console/config commands
 
     The console/config language does not define, how arguments are passed to the commands, it just
     tokenizes the input and passes the tokens to the commands which then handle the
@@ -366,7 +366,7 @@
     \code
     // Create a console/config aware object and place it into the node tree
     FooObject foo;
-    senf::console::add("foo", foo.dir);
+    senf::console::root().add("foo", foo.dir);
 
     // Open configuration file
     senf::console::ConfigFile cf ("/etc/myserver.conf");
@@ -449,7 +449,7 @@
            .name("myserver");
 
         // You need to enter the scheduler main-loop for the server to work
-        senf::Scheduler::instance().process();
+        senf::scheduler::process();
        
         // Alternatively enter the main-loop via the PPI
         // senf::ppi::run();