summaryrefslogtreecommitdiffstats
path: root/app/view
diff options
context:
space:
mode:
Diffstat (limited to 'app/view')
-rw-r--r--app/view/sysconf/default.view.php23
-rw-r--r--app/view/sysconf/user.modal.view.php30
2 files changed, 33 insertions, 20 deletions
diff --git a/app/view/sysconf/default.view.php b/app/view/sysconf/default.view.php
index 74dfd79..a4dade9 100644
--- a/app/view/sysconf/default.view.php
+++ b/app/view/sysconf/default.view.php
@@ -19,29 +19,12 @@
</head>
<body>
- <!-- Page modal content -->
- <div id="modalUser" class="modal fade" tabindex="-1" role="dialog">
- <div class="modal-dialog" role="document">
- <div class="modal-content">
- <div class="modal-header">
- <button type="button" class="close" data-dismiss="modal"><span aria-hidden="true">&times;</span></button>
- <h4 class="modal-title">User Accounts</h4>
- </div>
-
- <div class="modal-body">
- <p>Scrott implements a very flexible permissions and access-control system. It all starts with users' accounts. Users can create and maintain objects, but share them and allow others access if they so choose using a scheme similar to unix file permission modes. Since Scrott objects form an object hierarchy, permissions from 'higher' objects will cascade down. Meaning a non-trusted user may control an issue (since they likely opened it) in your pad, but have no access to the pad itself.</p>
- </div>
-
- <div class="modal-footer">
- <button type="button" class="btn btn-primary" data-dismiss="modal">Close</button>
- </div>
- </div>
- </div>
- </div>
-
+ <?php include "view/sysconf/user.modal.view.php"; ?>
<div class="container">
<div class="jumbotron">
<h2 class="text-center">
+ <a href="#" data-toggle="modal" data-target="#userModal"><span class="glyphicon glyphicon-user"></span></a>&nbsp;&nbsp;&nbsp;
+
<a href="#" data-toggle="modal" data-target="#modalUser"><span class="glyphicon glyphicon-user"></span></a>&nbsp;&nbsp;&nbsp;
<a href="#" data-toggle="modal" data-target="#modalGroup"><span class="glyphicon glyphicon-th"></span></a>&nbsp;&nbsp;&nbsp;
<a href="#" data-toggle="modal" data-target="#modalPad"><span class="glyphicon glyphicon-edit"></span></a>&nbsp;&nbsp;&nbsp;
diff --git a/app/view/sysconf/user.modal.view.php b/app/view/sysconf/user.modal.view.php
new file mode 100644
index 0000000..b3650b0
--- /dev/null
+++ b/app/view/sysconf/user.modal.view.php
@@ -0,0 +1,30 @@
+<div id="userModal" class="modal fade" tabindex="-1" role="dialog">
+ <div class="modal-dialog" role="document">
+ <div class="modal-content">
+ <div class="modal-header">
+
+ <button type="button" class="close" data-dismiss="modal">
+ <span aria-hidden="true">&times;</span>
+ </button>
+
+ <h4 class="modal-title">User Accounts</h4>
+
+ </div>
+
+ <div class="modal-body">
+ <p>Scrott implements a very flexible permissions and access-control system. It all
+ starts with users' accounts. Users can create and maintain objects and share them
+ with other users if they choose. This is done with a mechanism similar to unix
+ file permission modes. Scrott objects form a hierarchy, so permissions from 'higher'
+ objects will cascade down. This means that a non-trusted user may control an issue
+ in your pad, but have no access to the pad itself.</p>
+ </div>
+
+ <div class="modal-footer">
+ <button type="button" class="btn btn-primary" data-dismiss="modal">
+ Close
+ </button>
+ </div>
+ </div>
+ </div>
+</div>