... | ... | @@ -26,7 +26,7 @@ Following from above, all sub solutions are designed to be as generic as possibl |
|
|
The user interface is constructed with the help of one from of a handful of _templates_. The most important being `workflow.html`, while the entry point to the application is via the `menu.html`template. Other templates are `edit_authority.html` which is used to edit all fields relevant for a resource type, in addition to comparing and merging two resources, and `report.html`, which presents the data from all tabs as one sectioned page, for an overview over catalogue data describing a Publication.
|
|
|
|
|
|
### Ractive.js
|
|
|
Catalinker uses [Ractive.js](http://www.ractivejs.org/) web framework, developed by the Guardian newspaper. Its main purpose is two-way binding between input fields and javascript object structures, suitable for rendering a complex user interface backed by an application state.
|
|
|
Catalinker uses [Ractive.js](http://www.ractivejs.org/) web framework, developed by the Guardian newspaper. Its most prominent feature is two-way binding between input fields and values in javascript object structures, suitable for rendering a complex user interface backed by an application state.
|
|
|
### main.js
|
|
|
Most of the functionality in Catalinker is in main.js. It has grown from its humble beginnings in the old catalinker mentioned earlier to a quite large chunk of javascript code. Some parts and functions are more complex than others, and cater for more than one concern. No doubt should the file be divided into smaller modules and perhaps utilize Ractive's component support, but because of the incremental nature of the development process followed, and perhaps laziness, it has not come to this yet. However, most functions are kept small and with descriptive names, and the structure is roughly the same as from the beginning, only with more features added.
|
|
|
|
... | ... | |