Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:architecture:user_interface
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
development:architecture:user_interface [2017/08/02 17:59] – [Mix-ins] demiankatz | development:architecture:user_interface [2020/03/04 13:40] – [CSS Inheritance] demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== User Interface Customization ====== | ====== User Interface Customization ====== | ||
- | // This page refers to VuFind 2.x and later; | + | :!: // This page refers to VuFind 2.x and later; |
VuFind uses a theme system to isolate the user interface from the business logic, and to make it easy to customize the software' | VuFind uses a theme system to isolate the user interface from the business logic, and to make it easy to customize the software' | ||
Line 67: | Line 67: | ||
The way CSS inheritance works requires a few notes. | The way CSS inheritance works requires a few notes. | ||
- | * Always use Zend Framework's $this-> | + | * Always use [[development: |
* Watch out for @import statements in your CSS files. | * Watch out for @import statements in your CSS files. | ||
Line 94: | Line 94: | ||
The average VuFind user will probably not have much need to use mix-ins; however, this feature is useful for sharing functionality between VuFind instances. By creating a Zend Framework module full of custom code and a theme mix-in containing custom templates and assets, it should be possible to isolate entire custom features and share them between institutions without having to significantly change core VuFind code. | The average VuFind user will probably not have much need to use mix-ins; however, this feature is useful for sharing functionality between VuFind instances. By creating a Zend Framework module full of custom code and a theme mix-in containing custom templates and assets, it should be possible to isolate entire custom features and share them between institutions without having to significantly change core VuFind code. | ||
+ | |||
+ | ==== Mix-Ins and Inheritance ==== | ||
+ | |||
+ | Note that when you load a mix-in into a custom theme, the custom theme' | ||
===== Icon Libraries ===== | ===== Icon Libraries ===== |
development/architecture/user_interface.txt · Last modified: 2024/04/24 18:14 by emaijala