ATK Theme Templates: Difference between revisions

← Older edit Newer edit →

Revision as of 15:04, 28 February 2008

Below is a list of default templates and their explanation.

This will be a list of all styles that can be overidden on a page

actionpage.tpl: Render a generic action. Renders actionpage.tpl for the desired action. This includes the given block(s) and a pagetrial, but not a box.
action_$action.tpl
action.tpl
body.tpl
body_pda.tpl
box.tpl
debug.tpl
dialog.tpl
dispatch.tpl
editform.tpl: This template renders the form in edit pages.
extendableshuttle.tpl
field.tpl
integratededitform.tpl
list.tpl
login.tpl
menu.tpl: the template for the menu
page.tpl: $atkpage->m_content, having already been assigned within the render function, will be wrapped in page.tpl if it exists (e.g. $this->m_content= $ui->render('page.tpl',array('content'=>$this->m_content))) This is for stuff on the outermost edges of a page, but still within the body tags. This means usually intranet templates, or overall site templates within which the application is supposed to fit. Note that if you use the frameset option to construct the UI (app.php), then you will unfortunately get the edges on each frame. In this case you would want to preserve the frameset as scaffolding with some minimal default theme, but for the app you can change the theme per module in the module constructor in module.inc: function mod_Status() { global $g_theme; $g_theme["Name"] = "my_status_theme"; } This would wrap just the application in the intranet theme for example.
panetabs.tpl
recordlist.tpl
searchform.tpl
simplesearch.tpl
smartcriterium.tpl
smartsearchform.tpl
statusbar.tpl
tabbededitform.tpl
tabs.tpl
top.tpl
viewform.tpl

@@ Line 19: / Line 19: @@
 ;login.tpl:
 ;menu.tpl:the template for the menu
-;page.tpl:$atkpage->m_content,  having already been assigned within the render function,  will be wrapped in page.tpl if it exists ''(e.g. $this->m_content= $ui->render('page.tpl',array('content'=>$this->m_content)))''  This is for stuff on the outermost edges of a page,  but still within the body tags.  This means usually intranet templates,  or overall  site templates within which the application is supposed to fit.  Note that if you use the frameset option to construct the UI (app.php),  then you will unfortunately get the edges on each frame.  In this case you would want to preserve the frameset as scaffolding,  but for the app you can change the theme per module in the module constructor in module.inc:   ''function mod_Status() { global $g_theme;  $g_theme["Name"] = "my_status_theme"; }''
+;page.tpl:$atkpage->m_content,  having already been assigned within the render function,  will be wrapped in page.tpl if it exists ''(e.g. $this->m_content= $ui->render('page.tpl',array('content'=>$this->m_content)))''  This is for stuff on the outermost edges of a page,  but still within the body tags.  This means usually intranet templates,  or overall  site templates within which the application is supposed to fit.  Note that if you use the frameset option to construct the UI (app.php),  then you will unfortunately get the edges on each frame.  In this case you would want to preserve the frameset as scaffolding with some minimal default theme,  but for the app you can change the theme per module in the module constructor in module.inc:   ''function mod_Status() { global $g_theme;  $g_theme["Name"] = "my_status_theme"; }''  This would wrap just the application in the intranet theme for example.
 ;panetabs.tpl:
 ;recordlist.tpl: