Glissando
A simple content slider for anything that needs to move.
For React and Mithril.
Features
- Efficient rendering: only 3 elements are rendered at a single time (the previous, current and next element).
- This results in a minimal memory footprint, so safe for mobile.
- Can be controlled with next/previous actions, jump to page action, with or without animation.
- Use with a router: use the router location to control the slider. Or use other app state.
- Query for state, subscribe to changes.
- The list of elements can be changed on the fly.
- Right-to-left language support, using mirrored transitions.
- Written in TypeScript.
Usage, demos and examples
API
Introduction
A glissando slider is created with 2 parts:
- A model that maintains internal state and provides methods to control the slider.
- A slider component that takes child elements as views. The component informs the model to update, for instance when the children have been changed.
The slider component can be used standalone or directed.
Standalone use
This is the simplest setup. Use control methods: next(), goTo(0), etcetera to update the model state.
Directed use
Application state is used to control the slider. An example of application state is a router with a unique page URL for each slide.
- Pass a list of location ids, for example: possible route paths.
- Pass the current location id, for example: the current route path.
When application state changes the current location id, the slider model will subsequently be updated. For example: the Next button invokes a new URL, and the new router path is used to set the location id, which then tells the slider to slide to that element.
Examples for both uses are shown in the React and Mithril documentation sections.
Slider model
const model: Glissando.Model = useGlissandoModel();Initial state
const initalState: Glissando.InitialState = {
index: 0,
sideViews: 1,
};
const model: Glissando.Model = useGlissandoModel(initalState);index can be set to another value than 0. Its value will be changed automatically when the number of children of the slider component does not match the index.
sideViews defines how many items are rendered. For value 1: the current, previous and next item. For value 2: one more item at each side.
Model methods
const model = useGlissandoModel();
const {
// Control:
next,
previous,
goTo,
// State:
hasNext,
hasPrevious,
isAnimating,
getState,
// State (directed use):
getLocation,
getPreviousLocation,
getNextLocation,
// Subscribe to changes:
getChanges,
} = model;next
Control
Moves the slider to the next item. It is not possible to go beyond the last item.
Regular use:
model.next();Disable animation:
model.next({ animate: false });previous
Control
Moves the slider to the previous item. It is not possible to go further back than the first item.
Regular use:
model.previous();Disable animation:
model.previous({ animate: false });goTo
Control
Moves the slider to the indicated index. It is not possible to go further back than the first item, or beyond the last item.
Regular use:
model.goTo({
index: 1
});Disable animation:
model.goTo({
index: 1,
animate: false
});hasNext
State
Returns whether it is possible to move the slider to a next position.
const hasNext: boolean = model.hasNext();hasPrevious
State
Returns whether it is possible to move the slider to a previous position.
const hasPrevious: boolean = model.hasPrevious();isAnimating
State
Returns whether it the slider is currently animating.
const isAnimating: boolean = model.isAnimating();getState
State
As selector
Returns the state object.
const state: Glissando.States = model.getState();
const index: number = model.getState().index;As stream
Subscribe to the state stream. The map function is called when the model is updated. Note that this includes updates even when the state has not changed. To get notified on changes only, use getChanges.
model.getState.map((s: Glissando.State) => {
// ...
});getLocation
State (directed use)
Returns the current location id. If no next location exist returns undefined.
const location: string = getLocation();getPreviousLocation
State (directed use)
Returns the previous location id. If no previous location exist returns undefined.
const previousLocation: string = getPreviousLocation();getNextLocation
State (directed use)
Returns the next location id. If no next location exist returns undefined.
const nextLocation: string = getNextLocation();getChanges
Subscribe to changes
Subscribe to the changed state stream. The map function is called when the model is updated and the new state differs from the previous state.
model.getChanges
.map((state: Glissando.State) => {
// ...
})When calling getChanges in the component's render loop (in React's function component and in Mithril's view function, add end(true) to stop listening to the stream:
model.getChanges
.map((state: Glissando.State) => {
// ...
})
.end(true); // prevent accumulation of stream subscriptionsWhen calling getChanges in Mithril's closure component (outside of view), do not end the stream.
Slider component
The GlissandoSlider receives the model and child elements: the items to slide.
There is no limit to the number of children. By default only the current, previous and next items are rendered. This can be expanded with initial state attribute sideViews.
Children can be changed dynamically.
Options
| Parameter | Required | Type | Description |
|---|---|---|---|
| model | required | GlissandoModel |
The slider model |
| children | required | Component children | The elements to slide |
| locations | optional | string[] |
(directed use) List of location ids, for example: possible route paths |
| location | optional | string |
(directed use) The current location id, for example: the current route path |
With React
Standalone use
import { GlissandoSlider, useGlissandoModel } from 'glissando-react';
const model = useGlissandoModel();
<GlissandoSlider model={model}>
<Page1 />
<Page2 />
<Page3 />
</GlissandoSlider>Directed use
const pages = ["page-1", "page-2", "page-3"];
const Slider = () => {
const match = useRouteMatch();
const currentPage = match.params.page;
return (
<GlissandoSlider model={model} locations={pages} location={currentPage}>
{pages.map(id => {
return <Page key={id} location={id} />;
})}
</GlissandoSlider>
);
};See also: Glissando usage with React
With Mithril
Standalone use
import { GlissandoSlider, useGlissandoModel } from 'glissando-mithril';
const model = useGlissandoModel();
m(GlissandoSlider, { model }, [
m(Page1),
m(Page2),
m(Page3),
]);Directed use
const pages = ["page-1", "page-2", "page-3"];
const Slider = {
view: ({ attrs }) => {
const { model } = attrs;
const currentPage = m.route.param('page');
return m(
GlissandoSlider,
{
model,
locations: pages,
location: currentPage,
},
pages.map(id =>
m(Page, {
key: id,
location: id,
}),
),
);
},
};See also: Glissando usage with Mithril
RTL support
Glissando automatically detects the reading direction. Set one of the parent's HTML attribute direction to "rtl".
Supported browsers
Glissando is tested on major browsers, Edge and Internet Explorer 11.
License
MIT
Shout out
Glissando uses the Meiosis state pattern for state management.

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
