Theme management

Collaboration diagram for Theme management:

Modules
	Layout
	Default theme
	Jeff default theme Contains all the views, css, translations needed by the system. Every other theme has a fallback to the default when it lacks any resource.
	White theme
	Jeff white theme All missing resources fallback on the default theme.
Data Structures
interface	Itheme
	The common interface for all theme classes. More...
class	theme
	the primitive theme class More...

---

Detailed Description

Set of classes used to manage themes

Thanks to its modularity Jeff may support different themes, and the user may set which one to use, setting it as active.
All theme classes extends the theme class and implements the theme interface.

Every new installed theme "extends" the default one, in the sense that the new template may only override some features and all other stuffs (img, css, views, locales, js) falbacks to the default template, this way is quite fast to change for example only the template graphics because it's enough to create some images and rewrite the css stylesheet.

What follow is the list of features a theme might have

• css (under themes/theme_name/css/)
  • stylesheet.css: the main theme css
  • <template_name>.css: the specific global template css modules css: specific modules css
• js (under themes/theme_name/js)
  • themejs.js: the main theme javascript file (not present in the default theme)
  • <active_template>.js: the specific template js
• images (themes/theme_name/img)
  • the theme images
• locale (themes/theme_name/languages)
  • the files which contains the associative array used to translate strings
• view (themes/theme_name/view)
  • all the module's views, that is the module templates
• template files (themes/theme_name/) es public_home.tpl
  • all the global template files loaded and parsed by the template engine
• **<template_name>.php** (themes/theme_name) the specific theme class