* Started clearing everything out * WIP: Scaffolded the main loading flow See README.md. Measurements, content creation, then menus. * Hooked up some menu bindings * Set up webpack entry points The test shows it seems to work! * End-to-end tests working Directly comparing innerHTML to ensure faked menus match up to the real ones. * Vertical height assumptions: working * Added DI-d class names and styles * Dependency-injected styles into the elements FSP now specifies all its styles within the inline JS. You no longer need the large CSS files bundled with index.html to view the menus. * Added max height of container size to option lists * Added correct values to multi selects * Added old values to saveable store saving * Fixed resetSize: it'll fully reset menu contents now * Significantly simplified MenuStores No more pinning or transition times! They were just confusing and make the test surface much too big. * Added styles for select inputs * Documented everything * Used offsetTop instead of boundingArea.top for getAvailableContainerSize * Build fixes: requirejs types as dev-dependency; inputSelect stub styles * Removed @types/requirejs dev dependency See https://github.com/DefinitelyTyped/DefinitelyTyped/issues/21310.
5.4 KiB
UserWrappr
Creates configurable HTML displays over flexible-sized contents.
UserWrappr adds two features for wrapping HTML contents:
- Sizing of the content area within the available window space
- Delayed creation of content menus from readable schemas
Usage
const userWrapper = new UserWrappr({
createContents: (size: IAbsoluteSizeSchema) => {
return YourContentCreationLogic(size).canvas;
}
});
userWrapper.createDisplay(document.querySelector("#YourElementContainer"));
Details
UserWrappr prioritizes creating the contents as soon as possible.
When you call createDisplay, the following happen in order:
- View libraries (MobX+React) start to load.
- A visual approximation of your menus is placed at the bottom of the area.
- Contents are created in the remaining usable area.
- Once view libraries are loaded, real menus created using them to replace the fake menus.
Menus
It's assumed that your menus will exist below your content. Hovering over a menu title with a mouse will open the menu the content.
Each menu's schema must contain a title: string and options: IOptionSchema[].
Options will be created in top-to-bottom order within their parent menu.
The allowed option types, as indicated by the type member of the option schemas, are:
"action": Simple triggerable action with anaction: () => voidcallback."boolean": Stores an on/off value."multi-select": Stores multiple options within preset values. Needs:options: string[]: Given preset values.selections: number: How many of the preset options must be chosen at once.
"number": Stores a numeric value. May specifymaxand/orminvalues."select": Stores one of some presetoptions: string[]."string": Stores a string value.
All schema types except "action" store their TValue type and must also provide:
getInitialValue(): TValue: returns an initial state for the value.saveValue(newValue: TValue, oldValue: TValue): void: saves a new state for the value.
See OptionSchemas.ts for the full definitions.
Styles
UserWrappr will provide some default styles to its elements to position them.
You can override them by passing in a styles object keying preset identifiers to their CSS styles.
Although they're not used internally, you can also customize which class names are added to elements by passing a classNames object mapping preset identifiers to their class names.
Both styles and classNames will only override with provided values.
See ClassNames.ts for default class names and Styles.ts for preset identifiers and their default values.
API
Optional Parameters
classNames: IClassNames: Class names to use for display elements.createElement: (tagName: string, properties: IElementProperties): Creates a new HTML element.defaultSize: IRelativeSizeSchema: Initial size to create contents at (by default, 100% x 100%).getAvailableContainerHeight: Gets how much height is available to hold contents (by default,window.innerHeight).menuInitializer: string: RequireJS path to the menu initialization script.menus: IMenuSchema[]: Menus to create inside the menus area.styles: IStyles: Styles to use for display elements.requirejs: RequireJS (AMD) API to load scripts.
See IUserWrappr.ts for specifications on the parameters.
Examples
Giving each menu title a .my-menu-title class and color: red CSS style:
const userWrapper = new UserWrappr({
classNames: {
menuTitle: "my-menu-title"
},
createContents: () => { /* ... */ },
styles: {
menuTitle: {
color: "red"
}
}
})
Creating a menu with mute and volume inputs for a GameStartr's AudioPlayr:
const game = new GameStartr(/* ... */);
const userWrapper = new UserWrappr({
createContents: (size: IAbsoluteSizeSchema) => {
game.reset(size);
return game.canvas;
},
menus: [
{
options: [
{
getInitialValue: (): boolean => game.audioPlayer.getMuted(),
saveValue: (value: boolean): void => {
game.audioPlayer.setMuted(value);
},
title: "Mute",
type: OptionType.Boolean
},
{
getInitialValue: (): number => Math.round(game.audioPlayer.getVolume() * 100),
maximum: 100,
minimum: 0,
saveValue: (value: number): void => {
game.audioPlayer.setVolume(value / 100);
},
title: "Volume",
type: OptionType.Number
}
],
title: "Sound"
}
]
});