-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathum_modules.html
61 lines (57 loc) · 4.46 KB
/
um_modules.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
<!DOCTYPE html>
<html>
<head>
<title>skarphed - Documentation</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="static/logo_32.png" rel="icon" type="image/png">
<link href="static/mainsite.css" rel="stylesheet" type="text/css">
</head>
<body>
<div id="body_overlay" >
<header>
<div id="headercontent">
<a class="bclink" href="http://skarphed.org">
<img src="static/logo_32.png" alt="skarphed" style="float:left; margin-right: 10px;"></a>
<a class="bclink" href="index.html">Documentation
</a>
<a class="bclink" href="user_man.html">
→ Users Manual
</a>
<a class="bclink" href="um_overview.html">
→ Modules and Widgets
</a>
</div>
</header>
<div id="space_content">
<span class="headerlink_nohover"><h2> Modules and Widgets </h2></span>
<p>
Modules extend the functionality of your <em>skarphed-core</em>. To be precise: without a module, your <em>skarphed-core</em> won't be able to render a single bit of content. Modules classically are, e.g. a blog, a forum, or a menu.
</p>
<h3>Installing Modules</h3>
<p>
<em>Modules</em> is a direct sub-object of <em>skarphed-core</em> in the object-tree and you can open the <em>Modules</em>-objectpage via doubleclicking it. If the <em>skarphed-repo</em> that you chose for this <em>skarphed-core</em> is working properly, you see a list on the right side that contains all its available modules. The list on the left side shows all installed modules (which is empty in fresh <em>skarphed-core</em>-installations). Install or uninstall module simply via drag and drop to the opposite side. Be aware that <em>skarphed-core</em> considers module installations and uninstallations an operation and therefore the operation daemon must be active.
When the installationprocess succeded, you should see the module again, but this time at the opposite side. At the same time it is now displayed as a sub-object of <em>Modules</em> in the object-tree.
</p>
<h3>Widgets</h3>
<p>
Now you have a widget installed but you want to use it on your page. To achieve this you first have to create a widget. Why are widgets necessary? Simply because, for example you could eventually need. Two distinct blogs on two different thematics on your website. Or you want to have two user-chats on two different topics. In smaller setups it will be very rare to have more than one widget of each module, but widgets offer the possibility to go further. Think of modules as of a factory that produces widgets, and of widgets as cars (things that you can actually touch and work with) that are the products of these factories.
</p>
<h3>Creating a widget </h3>
<p>
Right mouseclick on the module that you want to create a widget of and click <em>Create Widget...</em>. You will be asked to enter the name for the new widget. Do so and click <em>OK</em>. Now you have a new widget as sub-element of the module in the object-tree.
</p>
<h3>Deleting a widget</h3>
<p>
You can delete a widget by right mouseclicking it and clicking on <em>Delete ... </em> in the context menu.
</p>
<h3>Configuring modules and widgets</h3>
<p>
By doubleclicking on modules and widgets in the object-tree you can open their respective object-pages. Please refer to the module's documentations how to use them.
</p>
</div>
<footer id="space_footer"></p><a href="../imprint.html">Imprint / Impressum</a></p>
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.
</footer>
</div>
</body>
</html>