blob: 3043187e2b2486018b3f660a901aea6d2ad86e44 (
plain)
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
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
|
<html>
<head>
<title>Konquer the Web with Quanta!</title>
<link rel="stylesheet" href="konq.css" type="text/css" />
<link rel="stylesheet" href="quanta.css" type="text/css" />
</head>
<body BGCOLOR=#3679AD LEFTMARGIN=0 TOPMARGIN=5>
<a name="top"></a>
<div style="position:absolute; left: 0px; top: 5px; right: 0px; bottom: 500px;">
<table BORDER=0 WIDTH=100% CELLPADDING=0 CELLSPACING=0 CELLPADDING=0>
<colgroup>
<col WIDTH=170>
<col WIDTH=20>
<col WIDTH=309>
<col WIDTH=*>
</colgroup>
<tr HEIGHT=24>
<td BGCOLOR=#505050 ALIGN=RIGHT><img width="77" height="22" src="aniquanta.gif" border="0"></td>
<td class="deco" BGCOLOR=#505050 COLSPAN=3>Konquer the Web with Quanta!</td>
</tr>
<tr>
<td WIDTH=190 COLSPAN=2 ROWSPAN=2> </td>
<td BGCOLOR=#DDDDDD><img WIDTH=309 HEIGHT=77 SRC="quantahdr.png"></td>
<td BGCOLOR=#DDDDDD BACKGROUND="lines.png"><img src="webdev.png" width="135" height="77" border="0"></td>
</tr>
<tr>
<td COLSPAN=2 BGCOLOR=#505050 ALIGN=RIGHT HEIGHT=22>
<table BORDER=0 CELLPADDING=0 CELLSPACING=0 CELLPADDING=0>
<tr>
<td HEIGHT=20 class="menu"> <a class="menu" HREF="intro.html">Introduction</a> </td><!-- Introduction -->
<td HEIGHT=20 class="menu">|</td>
<td HEIGHT=20 class="menu"> <a class="menu" HREF="faq.html">FAQ</a> </td><!-- Introduction -->
<td HEIGHT=20 class="menu">|</td>
<td HEIGHT=20 class="menu"> <a class="menu" HREF="tips.html">Tips</a> </td><!-- Tips -->
<td HEIGHT=20 class="menu">|</td>
<td HEIGHT=20 class="menuactive"> Where we're going </td>
<td HEIGHT=20 class="menu">|</td>
<td HEIGHT=20 class="menu"> <a class="menu" HREF="developer.html">Developer Info</a> </td><!-- Specifications -->
<td HEIGHT=20 class="menu"> </td>
</tr>
</table>
</td>
</tr>
<tr>
<td COLSPAN=2 WIDTH=190></td>
<td COLSPAN=2 class="shadow1" HEIGHT=9 COLSPAN=4></td>
</tr>
<tr>
<td COLSPAN=2 WIDTH=190></td>
<td COLSPAN=2 HEIGHT=41 COLSPAN=4></td>
</tr>
</table>
<!-- end of header -->
<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0 CELLPADDING=0>
<TR>
<TD WIDTH=190></TD>
<TD class="trans" BGCOLOR=#D0DFEC>
<TABLE WIDTH= 100% BORDER=0 CELLPADDING=0 CELLSPACING=0 CELLPADDING=0>
<TR>
<TD HEIGHT=20 WIDTH=20> </TD>
<TD> </TD>
</TR>
<TR>
<TD WIDTH=20> </TD>
<TD VALIGN=TOP>
<!-- here comes the content -->
<P><H2>Quanta Plus Templates<H2></P>
<p class="minihdr">Template description
</p>
<p>Templates are basically skeleton documents, code snippets and files to link to. Quanta
uses templates fundementally as a standard file system with enhanced organization and interfacing.
You can copy, move or link any repository currently on your system into the templates tree.
Think of Quanta templates as having roughly the limitations to your imagination that your file system
has.
</p>
<p>Templates exist in nested directories. There is no limit to how deep you can nest them however
within any given directory Quanta expects a consistent action for the base template type described
below. Additionally templates allow for <i>pre</i> and <i>post</i> text to be concatonated to
non document type templates. This facilitates tag creation. The next update after the introduction
is scheduled to add the ability to pass variables to the text such as image size information to
assist in tag creation.
</p>
<p class="minihdr">Template types
</p>
<p>Currently templates are limited to being one of the following types of objects:
<ul>
<li>Document </li>
<li>Text to insert in a document </li>
<li>A file to link to from a document </li>
</ul>
Documents can be any type of document. Generally you would want to nest more specific or diverse
documents in subdirectories. Here you can make a basic framework for what you do and deliver it
to your work in an organized fashion and realize much better effiency. Text insertion could be
anything from a snippet of code to a script or whatever you might wish to use. Note also this overlaps
the ability to insert text blocks as an action which can be triggered from the toolbar. Linked files
can be binary, PHP class libraries or whatever.
</p>
<p class="minihdr">Template scope
</p>
<p> Templates are scoped into three general categories: Global, Local and Project.
<ul>
<li>Global - Available to all folks all the time. </li>
<li>Local - Available to a specific user (maybe others if they can see it where it
exists in the file system). </li>
<li>Project - Available to the associated project only. </li>
</ul>
</p>
<p class="minihdr">Creating templates
</p>
<p>Create a document structure that you love (XML, HTML, DocBook, etc.) and
click on File->Save as Template->Save as Local/Project Template.
</p>
<p> Once this is done, you'll notice that (even if it's saved as a Project template)
the template does NOT show in the project tab view. Look into the templates view
to find your template under the Project templates tab.
</p>
<p>Additinoally if you look at your options with the Right Mouse Button (RMB) you
will see complete file management tools for creatind directories or copying and pasting
templates from one location to another.
</p>
<p class="minihdr">Using templates with Projects
</p>
<p>Project templates allow you to be more tightly focused. You can create headers, footers
or go dynamic with PHP include files and link them. Additionally there are some very
cool things we took into consideration when using templates in projects.
<ul>
<li>When creating a project you can opt to copy over all global and user templates. </li>
<li>Legacy project get default templating abilities so nothing is lost </li>
<li>You can choose where to locate your template files so they can be in your server root
and easy to upload or you can make them secure to link to below server root which is a
very cool trick </li>
<li>When linking to a file not in the project templates you will be prompted to copy
the file to the project templates prior to linking. This will prevent broken links on upload. </li>
<li>You always have control where you place your templates so you can choose to move them.
However Quanta does not track this so you will need to change links. This is a good
task for kfilereplace which we are setting up to plug in as a kpart. </li>
</ul>
</p>
<p class="minihdr">Templates conclusion
</p>
<p>Our goal with templates is to extend them to include multi file "concept" templates useful
for things like placing an order or creating an about section, Ideally this will be a tool for
making your work more productive and dynamic. An eventual goal is to have a structural template
design mode to deal with site layout and structure which you could use to design and interactively
update your sites. If you would like to be involved contact us.
</p>
<br>
<IMG WIDTH=16 HEIGHT=16 BORDER=0 SRC="more.png"> <A HREF="developer.html">Continue</A>
<!-- End of text -->
</TD>
<TD WIDTH=20> </TD>
</TR>
<TR>
<TD HEIGHT=20 WIDTH=20> </TD>
<TD> </TD>
</TR>
</TABLE>
</TD>
<TD WIDTH=20> </TD>
</TR>
<TR>
<TD HEIGHT=91 COLSPAN=3> </TD>
</TR>
</TR>
</TABLE>
<TABLE WIDTH=100% BORDER=0 CELLSPACING=0 CELLPADDING=0>
<TR>
<TD class="end" WIDTH=*> </TD>
<TD WIDTH=204><A HREF="http://www.kde.org"> <IMG WIDTH=204 BORDER=0 HEIGHT=57
SRC="kdelogo2.png"></A></TD>
</TR>
<TR>
<TD HEIGHT=50 COLSPAN=2> </TD>
</TR>
</TABLE>
</div>
</BODY>
</HTML>
|
