| [ Index ] |
|
Code source de eGroupWare 1.2.106-2 |
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 2 <html><head> 3 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"><title>eGroupWare: eTemplates - Templates and Dialog-Editor</title> 4 5 <!-- $Id: etemplate.html 22855 2006-11-18 07:38:09Z ralfbecker $ --> 6 7 <style> 8 <!-- 9 h1,h2,h3,p,pre { color: black } 10 pre { border: 1px solid black; padding: 0.08in; font-family: monospace; background: #f0f0f0; } 11 span { color: darkblue; } 12 --> 13 </style></head> 14 15 <body> 16 <h1>eTemplate - Templates and Dialog-Editor for eGroupWare</h1> 17 <h3>by Ralf Becker <a href="#" onclick="document.location='mai'+'lto:RalfBecker'+unescape('%40')+'outdoor-training'+unescape('%2E')+'de'; return false;">RalfBecker 18 AT outdoor-training DOT de</a></h3> 19 <h3>Updated by Raphael Alla <a href="#" onclick="document.location='mai'+'lto:raphael'+unescape('%40')+'olineopensolutions'+unescape('%2E')+'com'; return false;">>raphael AT olineopensolutions 20 DOT com</a></h3> 21 <p>A developers tutorial how to write an application with the new eTemplates.<br /> 22 It is also an introduction how to write a eGW- and setup(3)-compatible app.</p> 23 <hr> 24 <h1>Introduction - The concept of the eTemplates</h1> 25 <p>The eTemplates 26 </p> 27 <ul> 28 <li>consist out of rows and cols with input-fields of several types</li> 29 <li>there is a dialog-editor (one part of the etemplate-app) to create the eTemplate</li> 30 <li>eTemplates can be (and are usually) nested, eg. a template-field can contain an other eTemplate</li> 31 <li>each field / cell of the template can have a label which is automaticaly run through lang() (the 32 content of the field can be run through lang() too)</li> 33 <li>the dialog editor can write all labels in a lang-file (mergeing it with the existing ones)</li> 34 <li>eTemplates have a name of the form app.function[.subtemplate] which is used to call them up</li> 35 <li>they can have further keys, on loading the class picks the most appropriate one for a user: 36 <ol> 37 <li>group: the id of a group if the template is just for that group (that allows admin to show differnt 38 views to each group)</li> 39 <li>lang: the 2 or 5 letter language code (or empty for a non-language specific template)</li> 40 <li>template set: they belong too (if the template-set key is empty it is an default-template)</li> 41 <li>version: version number like: '1.3.001'</li> 42 </ol> 43 </li> 44 <li>they are stored in an array and in serialized form in the db-table 'egw_etemplate' </li> 45 <li>the dialog editor can dump all templates of an app for distribution (so they can be in the CVS too)</li> 46 <li><p>they encapsulate differnt UI (User Interface) types from the app: at the moment only a HTML one is ready, 47 but a GTK one (using <a href="http://gtk.php.net/" target="_blank">php-gtk</a>, <b>running 48 as native app under linux and win32</b>) and XUL is under development.<br>Here is a first screenshot of the DB-Tools as native 49 Linux Application:</li> 50 </ul> 51 <img src="gtk.png" name="Graphic1" align="bottom" border="0" height="575" width="1049"> 52 </p> 53 <hr> 54 <h1>Tutorial / Example: a simple media database</h1> 55 <p>As an example we will run now through the necessary steps to 56 create a simple media database using eTemplates and other tools and 57 classes from the eTemplate app: db-tools and class.so_sql.inc.php.</p> 58 <p>Out media database should have the usual fields: name, author, 59 description, type: BOOK, CD, VIDEO and should be able to edit records 60 and search for them.</p> 61 <p>As a preaquistion you need to get / checkout the etemplate app, 62 install the app via setup/manage applications and enable your account 63 for using the app (Admin/User account: check eTemplates).</p> 64 <h2>1. Creating a new eGW app directory</h2> 65 <p>Each app need a name, eg. 'et_media'. We now need to create the 66 following directory structur above the eGroupWare dir: 67 </p> 68 <pre>et_media that has to be identical to our app-name 69 + setup files necessary for the setup Programm, give the webserver write-permission to that dir 70 + inc class-files 71 + templates templates, still needed to store the images and get around a lot of complains from the api 72 + default 73 + images here goes our images / icons</pre><h2> 74 2. creating et_media/setup/setup.inc.php</h2> 75 <p>That files contains the necessary information for setup to install 76 the app. 77 </p> 78 <pre><?php 79 $setup_info['et_media']['name'] = 'et_media'; 80 $setup_info['et_media']['title'] = 'eT-Media'; 81 $setup_info['et_media']['version'] = '1.2'; 82 $setup_info['et_media']['app_order'] = 100; // at the end 83 $setup_info['et_media']['tables'] = array('egw_et_media'); 84 $setup_info['et_media']['enable'] = 1; 85 86 /* Dependencies for this app to work */ 87 $setup_info['et_media']['depends'][] = array( 88 'appname' => 'phpgwapi', 89 'versions' => Array('1.2','1.3','1.4') 90 ); 91 $setup_info['et_media']['depends'][] = array( 92 'appname' => 'etemplate', 93 'versions' => Array('1.2','1.3','1.4') 94 );</pre><h2> 95 3. setting up the db-table with the db_tools and setup</h2> 96 <p>To enable setup to create a db-table for us and to supply the 97 <b>so_sql</b>-class with the necessary information, we need to define 98 the type and size of the fields / columns in our db-table.</p> 99 <p><br><br> 100 </p> 101 <p><img src="dbtools.jpg" name="Graphic2" align="left" border="0" height="340" width="950"><br clear="left"><br>We 102 can use the db-Tools from the etemplate application to create the 103 file for us: 104 </p> 105 <ol> 106 <li>start the etemplate app and click on the button up, right which says db-Tools</li> 107 <li>select Application: eT-Media</li> 108 <li>type 'egw_et_media' in the field in front of the [Add Table] button and click on the button</li> 109 <li>now use [Add Column] to create thenecessary fields as shown on the screenshot</li> 110 <li>Click on [Write Table] (you need to give the webserver write-permission to the setup-dir of et_media 111 or you will get an error message, leave the write-permission as it is necessary later on too, click on write again)</li> 112 <li>log out and log into setup and start manage applications</li> 113 <li>eT-Media is shown as not installed and only install is offerd, check it and submit</li> 114 <li><p>you can now log out from setup, the db-table is now created</li> 115 <li><p>In order to be able to use your eT-Media application, do not forget to give yourself access to it 116 (Admin/User account: check eT-Media)</li> 117 </ol> 118 <h2>4. creating an eTemplates for the edit-dialog</h2> 119 <p>Now we need a nice edit dialog and use the eTemplate editor to set 120 it up: 121 </p> 122 <ol> 123 <li>start the etemplate app and type <b>'et_media.edit'</b> in the name field. Save the template in order 124 to create it</li> 125 <li>an empty template is displayed. An eTemplate can be thought off as a “grid”. The first cell may be 126 a bit tricky to find, but will be highlighted when moving the mouse 127 over it. On my computer this cell appears in pink as illustrated below:</li> 128 <li><img src="step0.jpg" name="Graphic3" align="left" border="0" height="509" width="922"><br clear="left">Double 129 click on the pink spot will bring the following dialog:</li> 130 <li><img src="step1.jpg" name="Graphic7" align="left" border="0" height="544" width="851"><br clear="left">The 131 top row allows you to add column and rows to the template. We will need 2 columns and 6 rows</li> 132 <li>Create the following label in the first top left cell:</li> 133 </ol> 134 <img src="step2.jpg" name="Graphic8" align="left" border="0" height="533" width="853"><br clear="left"><br> 135 </p> 136 <br> 137 </p> 138 <ol start="6"> 139 <li>In the top right cell, we will create a user entry and call it “name”: this is the same name as thee column in our 140 egw_et_media table. This is important as those fields will be populated automatically for us by eGroupWare:</li> 141 <li><img src="step3.jpg" name="Graphic9" align="left" border="0" height="560" width="852"><br clear="left"> 142 <p>Complete the template as follows. The widget used for “type” is a 143 Selectbox, the one used for “description” is a textarea. Note 144 that the name of the input is “descr” and not description, as 145 this is the name of the column in the table. Finally on the last row 146 we have two widgets of type “Submitbutton” of names “read” 147 and “save” and of corresponding label.</p> 148 <p><img src="step4.jpg" name="Graphic4" align="left" border="0" height="380" width="922"><br clear="left"></p> 149 </li> 150 </ol> 151 <p>Then before moving to the next stage save the template as an XML 152 file by clicking on “Export XML”. Once again the server must have 153 write permissions on the directory.</p> 154 <h2>5. Setting up the index page</h2> 155 <p>The index page is only used if someone clicks on the navbar icon 156 (or on the black cross as we haven't supplied one so far).<br>Create 157 the file <b>/et_media/index.php</b> with the following content:</p> 158 <pre><?php 159 $GLOBALS['phpgw_info']['flags'] = array( 160 'currentapp' => 'et_media', 161 'noheader' => True, 162 'nonavbar' => True 163 ); 164 include('../header.inc.php'); 165 $GLOBALS['egw']->redirect_link('/index.php', 'menuaction=et_media.ui_et_media.edit'); 166 </pre> 167 <h2>6. The code for our application</h2> 168 <p>An eGroupWare application is organised around 3 application 169 layers:</p> 170 <ul> 171 <li> 172 the storage layer, managed by a “Storage Object” (so). 173 This object is responsible for handling all access to the storage 174 engine. We use the "stock" so_sql class for this, so we 175 need no extra so-object for the moment. 176 </li> 177 <li> 178 the business layer, managed by a “Business Ojbect” (bo). 179 This object is responsible for all the business logic. 180 The business object can extend the storage object, 181 to avoid passing the so-methods as stubs to the ui layer. 182 </li> 183 <li> 184 the user interface layer, managed by a “User Interface” 185 (ui) object. This object is responsible for all interaction with the 186 user, including displaying and gathering data to and from the user. 187 The ui object can extend the bo-object. 188 </li> 189 </ul> 190 <p>For this, we create 2 files in the “inc” directory, called 191 class.bo_et_media.inc.php and class.ui_et_media.inc.php. 192 In this simple application, the bo layer will be fairly minimal, 193 this said it is a good idea to create the application using the 194 right standards from the start.</p> 195 <p>Here is the file <b>/et_media/inc/class.bo_et_media.inc.php</b>: 196 </p> 197 <pre> 198 <?php 199 <span>/** 200 * eGroupWare editable Templates - Example media database (et_media) 201 * 202 * @license http://opensource.org/licenses/gpl-license.php GPL - GNU General Public License 203 * @package etemplate 204 * @subpackage et_media 205 * @link http://www.egroupware.org 206 * @author Ralf Becker <RalfBecker@outdoor-training.de> 207 */</span> 208 209 include_once (EGW_INCLUDE_ROOT . '/etemplate/inc/class.so_sql.inc.php'); 210 211 <span>/** 212 * Business object for et_media 213 */</span> 214 class bo_et_media extends so_sql 215 { 216 <span>/** 217 * Availible media types 218 * 219 * @var array 220 */</span> 221 var $types = array( 222 '' => 'Select one ...', 223 'cd' => 'Compact Disc', 224 'dvd' => 'DVD', 225 'book' => 'Book', 226 'video' => 'Video Tape' 227 ); 228 <span>/** 229 * Constructor initialising so_sql 230 * 231 * @return so_et_media 232 */</span> 233 function bo_et_media() 234 { 235 $this->so_sql('et_media','egw_et_media'); <span>// calling the constructor of the extended bo object</span> 236 $this->empty_on_write = "''"; 237 } 238 } 239 </pre> 240 <p>And finally the start of the 241 <b>/et_media/inc/class.ui_et_media.inc.php</b>:</p> 242 <pre> 243 <?php 244 <span>/** 245 * eGroupWare editable Templates - Example media database (et_media) 246 * 247 * @license http://opensource.org/licenses/gpl-license.php GPL - GNU General Public License 248 * @package etemplate 249 * @subpackage et_media 250 * @link http://www.egroupware.org 251 * @author Ralf Becker <RalfBecker@outdoor-training.de> 252 */</span> 253 254 include_once (EGW_INCLUDE_ROOT . '/et_media/inc/class.bo_et_media.inc.php'); 255 256 class ui_et_media extends bo_et_media 257 { 258 <span>/** 259 * Public functions callable via menuaction 260 * 261 * @var array 262 */</span> 263 var $public_functions = array( 264 'edit' => True, 265 ); 266 267 <span>/** 268 * Constructor 269 * 270 * @return ui_et_media 271 */</span> 272 function ui_et_media() 273 { 274 $this->bo_et_media(); <span>// calling the constructor of the extended bo object</span> 275 276 $this->tmpl =& CreateObject('etemplate.etemplate','et_media.edit'); 277 } 278 279 <span>/** 280 * Edit a media database entry 281 * 282 * @param array $content=null 283 * @param string $msg='' 284 */</span> 285 function edit($content=null,$msg = '') 286 { 287 if (is_array($content)) <span>// not first call from index</span> 288 { 289 if ($content['id'] > 0) 290 { 291 $this->read($content); 292 } 293 <span>//echo "<p>edit: content ="; _debug_array($content);</span> 294 $this->data_merge($content); 295 <span>//echo "<p>edit: data ="; _debug_array($this->data);</span> 296 297 if (isset($content['save'])) 298 { 299 $msg .= !$this->save() ? lang('Entry saved') : lang('Error: while saving !!!'); 300 } 301 } 302 303 <span>// now we filling the content array for the next call to etemplate.exec</span> 304 305 $content = $this->data + array( 306 'msg' => $msg 307 ); 308 $sel_options = array( 309 'type' => $this->types 310 ); 311 $this->tmpl->exec('et_media.ui_et_media.edit',$content,$sel_options,$no_button,array( 312 'id' => $this->data['id'] 313 )); 314 } 315 </pre> 316 <p> 317 The edit function is called from our index.php file or as callback 318 for this form / dialog. In that case $content is an array with the 319 content the user put into the fields of the dialog.</p> 320 <p>Let first have a look what happend if we called the first time (or 321 what we do to show the dialog again with the changed data):</p> 322 <ol> 323 <li>the $content array is set up with our internal data-array (which is empty on the first call) and the message</li> 324 <li>$sel_options has the options for our selectbox: the options are an array where the keys are the 325 values returned by the selectbox and the values are what the 326 selectbox shows to the user. As we can have more than one selectbox 327 in a dialog, the key in $sel_options need to be the same as the name 328 of the selectbox.</li> 329 <li>$readonlys: if a fieldname is set in $readonlys to True, its content is showed readonly 330 (for regular fields like type Text) or left out for buttons (we use this later to 331 show the delete-button only when an entry is loaded)</li> 332 <li>the array $preserv is preserved, which means its stored in the app's session-data and is delivered 333 back like the content of the fields to the callback-function. We use 334 it here to store the id of the entry. This is similar to use a 335 hidden input-field in a form, but it does not need to be serialized 336 by the app and is NOT transmitted to the user and back.</li> 337 <li><p>at last we call etemplate::exec to show the template with the 338 content from $content and set the function itself as callback for 339 the dialog / form.</li> 340 </ol> 341 <p>Now let's have a look what happens if the user submits the form 342 and our callback is called: 343 </p> 344 <ol> 345 <li>the callback (this function) is 346 not the submit-address of the form, the form get's always submitted 347 to the function <b>process_exec</b> of the etemplate class. This 348 function changes for some field-types the content (eg. a date-field 349 consists of 3 single fields, process_exec takes care that it is 350 delivered back as timestamp, as we set it in content before). It can 351 even submit the form back to the user if for a address-selection a 352 search for a pattern has to be performed and the matches are shown 353 to the user. In this case the callback is NOT called. The same is 354 true if an int field contains letters or is not within the minimum 355 or maximum set. <i>Not all of the is allready working, it will 356 follow in the next days/weeks.</i><br>For the specialist 357 process_exec uses $_POST and ignores $_GET set as query in the url.</li> 358 <li>the so_sql function data_merge, copies all values from $content, which are columns in the db-table, 359 in our internal data array. Values which are not real data, like 360 buttons pressed are not copied (!).</li> 361 <li>if $content['save'] is set, the [Save] button has been pressed ('save' is the name NOT the label of 362 the save button), in that case we use so_sql's save function to save 363 the content of our internal data-array to the db.</li> 364 <li>the same check is used for the [Read]: we uses the content of all fields to search db for matching 365 entries. The user can use wildcards to perform a search on all 366 field. The wildcards are '*' and '?', so_sql translates them into sql-wildcards.</li> 367 <li>if the search return False we just set our message var.</li> 368 <li>if something is found we use so_sql's init-function to set the data of the first match. Lateron 369 we will show a list if more than one entry is found.</li> 370 <li><p>after that the content array is filled again as discriped above.</li> 371 </ol> 372 <p>Now we are able to store entries in the db and retrive them by 373 searching the database for patterns in the different fields. You can 374 try your new application now. You can create new records and save 375 them. By just entering the name or author, the database will find the 376 corresponding match and populate the form for you.</p> 377 <p><br>We are only lacking some way to show if we get more than one 378 match on a search, that's what we are going to implement next:</p> 379 <h2>7. adding a list-dialog for the search-function</h2> 380 <p>First we need to create an other eTemplate to show the list: 381 <b>'et_media.show'</b> as follows. This is made of a label of name 382 “msg” (to display messages), an HorizontalRule widget, and a 383 Template widget: we will use a “sub template” called 384 et_media.show.rows to display the rows of the search function. I have 385 set the option of the template widget to “entry” as this is the 386 name we will use to access to the data in the sub-template. 387 </p> 388 <p style=""><img src="step5.jpg" name="Graphic5" align="left" border="0" height="561" width="843"><br clear="left"><br><br> 389 </p> 390 <p style="">The 'et_media.show.rows' template is 391 created as a 3x2 table. On the header row, two labels “Name” and 392 “Author” and one empty cell.</p> 393 <p>ond row, two labels of name $row}[name] and $row}[author]. In the last cell a 394 submitButton of label “Edit” and of name “edit[$row_cont[id]]” 395 </p> 396 <p><img src="step6.jpg" name="Graphic6" align="left" border="0" height="515" width="847"><br clear="left"><br><br> 397 </p> 398 <p>The class of the header row is “th” and the class of the 399 content row is “row”. eTemplate will automatically vary the 400 colors of the “row” class to provide a nice visual effect.</p> 401 <p>Here is a view of the et_media.show template once the two 402 templates have been created:</p> 403 <p><img src="step7.jpg" name="Graphic10" align="left" border="0" height="419" width="950"><br clear="left"><br><br> 404 </p> 405 <p>We need some code / a function in the class to call the template 406 and fill the content:</p> 407 <pre> 408 <span>/** 409 * Showing entries from the media database 410 * 411 * @param array $found 412 */</span> 413 function show($found=null) 414 { 415 if (!is_array($found) || !count($found)) 416 { 417 $this->edit(); 418 return; 419 } 420 array_unshift($found,false); <span>// change the array to start with index 1</span> 421 $content = array( 422 'msg' => lang('%1 matches on search criteria',count($found)), 423 'entry' => $found, 424 ); 425 $this->tmpl->read('et_media.show'); 426 427 $this->tmpl->exec('et_media.ui_et_media.edit',$content); 428 } 429 } 430 </pre><p> 431 This function is called by edit with the matches of a search:</p> 432 <ol> 433 <li>We build an array with all the matches, the index in that array is the row-number starting with 1(!) 434 ($entry = array('empty') + $found; would do the same).<br /> 435 The names in the data-row (last row) of 'et_media.show.rows' are like 436 '$row}[name]'. Variable expansion is performed on each name and 437 expands that for the first row to '1[name]' which addresses the name 438 in the first match.</li> 439 <li>$content contains again 'msg' which we set to the number of entris found and the above array with 440 the data of all rows under the key 'entry', as we put that in 441 Options for the field loading the sub-template 'et_media.show.rows'. 442 It not necessary to put something in Options-field / use a sub-array 443 for a sub-template, but it can be very helpful to organize a complex 444 content-array. (As an exercice you can remove 'entry' from the 445 Options-field and change the function arrcordingly).</li> 446 <li>we now explizitly read the template 'et_media.show' (the constructor reed 'et_media.edit') and 447 execute it again with the edit function as callback (because of 448 that, show does NOT need to be listed in public_functions)</li> 449 <li>as 'et_media.show.rows' contains only one data-row, but fieldnames with variables to expand, that row is autorepeated for as 450 many data we put into the content array (or the sub-array if we used the Options-field).</li> 451 </ol> 452 <p>To call the show function, we need to make some changes to the 453 edit-function too:</p> 454 <pre> 455 elseif (isset($content['read'])) 456 { 457 unset($content['id']); <span>// not set by user, so dont use for seach</span> 458 unset($content['read']); 459 $found = $this->search($content,False,'name,author'); <span>// searches by using the no-empty fields</span> 460 461 if (!$found) 462 { 463 $msg .= lang('Nothing matched search criteria !!!'); 464 } 465 elseif (count($found) == 1) 466 { 467 $this->init($found[0]); <span>// only one match --> show it in the editor</span> 468 } 469 else 470 { 471 $this->show($found); <span>// multiple matches --> use the show function/template</span> 472 return; 473 } 474 } 475 elseif (isset($content['entry']['edit'])) <span>// the callback from for the show function/template</span> 476 { <span>// the id is set via the button name of '$row_cont[id]'</span> 477 list($id) = each($content['entry']['edit']); <span>// note its not only ['edit'] !!!</span> 478 if ($id > 0) 479 { 480 $this->read(array('id' => $id)); 481 } 482 } 483 </pre> 484 <ol> 485 <li>the first part should be self-explaining, we call show with $found if it contain more than 486 one entry.</li> 487 <li>The show function uses edit as callback, the [Edit] buttons 488 in each row has 'edit[$row_cont[id]]' as name. If an [Edit] button 489 is pressed $content['entry']['edit'] is set to the id of the entry 490 of that row. We use that id to read the whole entry.</li> 491 </ol> 492 <p>This is what the new “show” template looks like:</p> 493 <p><img src="step8.jpg" name="Graphic11" align="left" border="0" height="349" width="950"><br clear="left"><br><br> 494 </p> 495 <p>While makeing this changes we can add a [Cancel] and [Delete] 496 button too:</p> 497 <pre> 498 elseif (isset($content['cancel'])) 499 { 500 $content = array(); <span>// clear the contents</span> 501 } 502 elseif (isset($content['delete'])) 503 { 504 $this->bo->so->delete($r_id); 505 $content = array(); <span>// clear the content</span> 506 } 507 508 $no_button = array( <span>// no delete button if id == 0 --> entry not saved</span> 509 'delete' => !$this->content['id']; 510 ); 511 </pre> 512 <ol> 513 <li>on cancel we just clear the internal data-array with so_sql's init function.</li> 514 <li>on delete we have to call so_sql's delete before (it deletes the db-row coresponding 515 with our internal data-array)</li> 516 <li><p>the last block checks if the id field is set (it can only be 517 set by a read or save) and disables the [Delete] button if not 518 ($this->db_key_cols[$this->autoinc_id] == 'id').</li> 519 </ol> 520 <p>Of course we have to add this buttons to the template 521 'et_media.edit'. I trust you can add 2 Submitbuttons with the names 522 'cancel' and 'delete', a Label and a nice helpmessages by now without 523 looking at a screenshot ;-).</p> 524 <h2>8. creating the english lang-file</h2> 525 <p>To get rid of the stars '*' behind each Label and to be able to 526 translate the app in other languages we need to create a 527 lang-file<br>There are 2 possibilties to create it automaticaly:</p> 528 <ol> 529 <li>Use the [Write Langfile] button in the eTemplate editor (put the app-name 'et_media' in the name-field 530 first)<br />That will NOT write the messages in the classes!!!</li> 531 <li>We can use the TranslationTools to scans our sources for lang('...') calls ([search new phrases] button).</li> 532 <li>Other phrases like the media types can be added manually via [Add] button in the Translation Tools.</li> 533 </ol> 534 <h2>9. dumping the eTemplate to a file for distribution</h2> 535 <p>To be able to put the eTemplates in CVS and to ship them with your 536 app, you need to dump them in a file first. 537 </p> 538 <p>This is done in the eTemplate editor by putting the app-name or an 539 template-name in the Name field and clicking on the button 540 [Dump4Setup]. This creates the file 541 <b>et_media/setup/etemplates.inc.php</b>. The etemplate-class loads 542 this file whenever it finds a new version automaticaly.</p> 543 <h2>10. further information</h2> 544 <p><b>Please note:</b> <i>all files of the et_media example can be found in the et_media sub-direcotry of 545 etemplate's doc directory. Symlinking or coping to the eGroupWare install directory, allows to 546 immediatly install it via setup.</i></p> 547 <ol> 548 <li>the <a href="reference.html">reference-documentation</a> of the eTemplates</li> 549 <li>for all functions and parameters of the <b>etemplate</b>-class(es) look in the 550 <a href="http://www.egroupware.org/egwdoc/li_etemplate.html" target="_blank">phpDocumentor docu of etemplate</a> 551 created from comments (yes there are comments) in the sources: 552 <ul> 553 <li><a href="http://www.egroupware.org/egwdoc/etemplate/api/etemplate.html" target="_blank">class.uietemplate.inc.php</a> 554 for the exec function</p></li> 555 <li><a href="http://www.egroupware.org/egwdoc/etemplate/api/boetemplate.html" target="_blank">class.boetemplate.inc.php</a> 556 for the variable replacement in names and about the autorepeat rows and columns</p></li> 557 <li><a href="http://www.egroupware.org/egwdoc/etemplate/api/boetemplate.html" target="_blank">class.soetemplate.inc.php</a> 558 for writeLangFile and all functions to read, store and dump an eTemplate</p></li> 559 </ul> 560 </li> 561 <li>for all functions and parameters of the <b>so_sql</b>-class look in the comments of the file 562 <a href="http://www.egroupware.org/egwdoc/etemplate/api/so_sql.html" target="_blank">class.so_sql.inc.php</a></li> 563 <li><p>for setup, the necessary files of an app or the format of 564 tables_current.inc.php look at the exelent <a href="../../setup/doc/setup3.html">docu 565 of setup3</a> in the doc-dir of the setup app. </li> 566 </ol> 567 <h2><i>That's it</i> - please write to our <a href="#" onclick="document.location='mai'+'lto:egroupware-developer'+unescape('%40')+'lists'+unescape('%2E')+'sf.net'; return false;">developers list</a> 568 or <a href="http://forum.egroupware.org/" target="_blank">developer forum</a>, 569 if you have further questions or comments about the tutorial or eTemplate.</h2> 570 </body></html>
titre
Description
Corps
titre
Description
Corps
titre
Description
Corps
titre
Corps
| Généré le : Sun Feb 25 17:20:01 2007 | par Balluche grâce ŕ PHPXref 0.7 |