/program/themes/sophia/sophia.class.php - the class that implements the theme
Located in /program/themes/sophia/sophia.class.php (line 27)
Theme | --ThemeSophia
Inherited from Theme
Theme::$area_id
Theme::$area_record
Theme::$breadcrumb_addendum
Theme::$breadcrumb_separator
Theme::$config
Theme::$content
Theme::$domain
Theme::$dtd
Theme::$html_head
Theme::$http_headers
Theme::$jumps
Theme::$messages_bottom
Theme::$messages_inline
Theme::$messages_top
Theme::$node_id
Theme::$node_record
Theme::$preview_mode
Theme::$quickbottom_separator
Theme::$quicktop_separator
Theme::$silent_mode
Theme::$text_only
Theme::$theme_id
Theme::$theme_record
Theme::$title
Theme::$tree
show footer text, maybe some quicklinks and 'powered by'
construct an output page in HTML
This constructs a full HTML-page, starting at the DTD and ending with the html closing tag.
The page is constructed using nested DIVs, the layout is taken care of in a separate style sheet. All knowledge about the structure of the page is contained in this routine.
The performance of the script (# of queries, execution time) is calculated as late as possible, to catch as much as we can. Therefore the construction is done in two parts and performance is calculated last.
The contents of the various DIVs is constructed in various helper routines in order to make this routine easy to read (by humans that is). The various helper routines all are called with a string of space characters; this should improve the the readability of the page that is generated eventually.
Note that the routine $this->get_div_messages() does in fact generate its own DIV tags. This is done in order to completely get rid of the message DIV, we do not even want to see an empty DIV if there are no messages.
The same logic applies to the breadcrumb trail.
construct the submenu starting at $menu_id OR the first breadcrumb in the top level menu
this constructs an 'infinitely' nested set of submenus, starting at $menu_id or at the first breadcrumb in the top level menu (if any). If there are no suitable nodes, an empty string is returned.
this is largely the same routine as parent::get_menu(). Difference is that here we may add a menu title to the menu IF the first item in the breadcrumb trail is a visible section
construct a top level menu (navigation bar) as an unnumbered list (UL) of list items (LI)
this walks through the top level of the menu tree and creates a link for each node with a distinct class for every LI This allows for buttons in different shapes and colours.
By default the theme comes with three different shapes (see also style.css):
Inherited From Theme
Theme::Theme()
Theme::add_content()
Theme::add_html_header()
Theme::add_http_header()
Theme::add_message()
Theme::add_meta()
Theme::add_meta_http_equiv()
Theme::add_popup_bottom()
Theme::add_popup_top()
Theme::add_stylesheet()
Theme::calc_breadcrumb_trail()
Theme::construct_tree()
Theme::dump_subtree()
Theme::get_address()
Theme::get_bazaar_style_style()
Theme::get_bottomline()
Theme::get_content()
Theme::get_div_breadcrumbs()
Theme::get_div_messages()
Theme::get_html()
Theme::get_html_head()
Theme::get_jumpmenu()
Theme::get_lines()
Theme::get_logo()
Theme::get_menu()
Theme::get_navigation()
Theme::get_popups()
Theme::get_properties()
Theme::get_quickbottom()
Theme::get_quicklinks()
Theme::get_quicktop()
Theme::node2anchor()
Theme::queue_alert()
Theme::send_headers()
Theme::send_output()
Theme::set_preview_mode()
Theme::show_tree_walk()
Documentation generated on Tue, 28 Jun 2016 19:12:03 +0200 by phpDocumentor 1.4.0