Web   ·   Wiki   ·   Activities   ·   Blog   ·   Lists   ·   Chat   ·   Meeting   ·   Bugs   ·   Git   ·   Translate   ·   Archive   ·   People   ·   Donate
summaryrefslogtreecommitdiffstats
path: root/boards/login.xml.in
diff options
context:
space:
mode:
authorBruno Coudoin <bcoudoin@src.gnome.org>2005-08-02 22:51:58 (GMT)
committer Bruno Coudoin <bcoudoin@src.gnome.org>2005-08-02 22:51:58 (GMT)
commitcd31974f8a1c3316873d7eaa14778fd66afa5656 (patch)
tree32af54779e1f024023ed6a4b8c7120f080c91d1c /boards/login.xml.in
parentee122043afa0d73d4fe6951cee734e0bc74b56be (diff)
- Fixes several issue in src/boards/python.c. No more craches.
- Prepared the login screen but empty for now - Renamed reread_xml by reread_menu - Now the noxrandr param is 'almost' persistant in the config file 'almost' because until you enter and quit the gcompris config panel, it is not saved. This is very dangerous becaus after that there is no way to put back xrander in since there is no --withxrandr switch. WARNING: This need more works !!
Diffstat (limited to 'boards/login.xml.in')
-rw-r--r--boards/login.xml.in21
1 files changed, 21 insertions, 0 deletions
diff --git a/boards/login.xml.in b/boards/login.xml.in
new file mode 100644
index 0000000..eff5df4
--- /dev/null
+++ b/boards/login.xml.in
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<GCompris>
+ <Board
+ name="login"
+ type="python:login"
+ section="none"
+ icon=""
+ author="">
+ <_title>GCompris login screen</_title>
+ <_description>Select or enter your name to log in GCompris</_description>
+ <_prerequisite></_prerequisite>
+ <_goal>By identifying in GCompris, we are able to provide specific reporting for each kids.</_goal>
+ <_manual xml:space="preserve">In order to activate the login screen, you must
+first add users in the administration part of GCompris.
+You access the administration part by running 'gcompris -a'.
+In the administration, you can create different profiles. In each profiles
+you can have a different set of users and select which activities are available to them.
+To run Gcompris in a specific profile, you can run 'gcompris -p profile' where 'profile'
+is the name of a profile as you created it in the administration.</_manual>
+ </Board>
+</GCompris>