Directory

← Back

hydrofoil-shell

Barebone base for building Hypermedia-driven applications

Author

Contributors

Rating

Popularity

<100

hydrofoil-shell

UI-agnostic base element which can be used to build hypermedia-driven single page applications.

Implemented using lit-element

Installation

yarn add @hydrofoil/hydrofoil-shell

Usage

<hydrofoil-shell>

The core element, which manages a state (single resource representation).

This element is abstract. It does not:

  • handle of client-server interaction (doesn't load the resource)
  • does not render any shell UI
  • delegates the rending of resource representations to <lit-view> element

Using the element

In order to actually deploy a shell element simple steps are required:

  1. inherit from the base
  2. implement loadResourceInternal
  3. override renderMain to create some core app UI

Here's an example of how this would be done

import HydrofoilShell from '@hydrofoil-shell/hydrofoil-shell/hydrofoil-shell'
import {customElement, html} from 'lit-element'

@customElement('my-app-shell')
export default class MyAppShell extends HydrofoilShell {
  renderMain () {
    // call base to keep using <lit-view> to render the actual resource
    return html`
      <nav>Some static menu</nav>
      <section class=main>
        ${base.renderMain()}
      </section>
      <footer>Footer element</footer>
    `
  }

  loadResourceInternal (uri) {
    return fetch(uri)
  }
}

The base shell element does not implement the actual loading so that it's not being coupled with a single client library or API implementation. Still, instead of repeating the load method every time you should build a hydrofoil application, a mixin can be used instead to reuse the logic for loading the resources.

For example, Hydra APIs can be consumed by mixing in alcaeus-loader

+import AlcaeusLoader from '@hydrofoil-shell/alcaeus-loader`

@customElement('my-app-shell')
-export default class MyAppShell extends HydrofoilShell {
+export default class MyAppShell extends AlcaeusLoader(HydrofoilShell) {

-  loadResourceInternal (uri) {
-    return fetch(uri)
-  }
}

<hydrofoil-multi-resource-view>

A helper element, which helps manage multiple resource. Just as the base shell element, it only serves as a skeleton and needs to be inherited to actually serve as a presentation layer.

For examples check out the material design implementations hydrofoil-resource-tabs and hydrofoil-resource-accordion.

Usage

The element is controlled by standard DOM events. To add a resource to the ones displayed dispatch hydrofoil-append-resource from any child element.

child.dispatchEvent(new CustomEvent('hydrofoil-append-resource', {
  bubbles: true,
  composed: true,
  detail: {
    parent: currentResource,
    resource: nextResource,
  },
}))

Both parent and resource are mandatory. If parent is not the topmost resource on the stack all its current children will be replaced with nextResource.

To remove an element from the stack, dispatch hydrofoil-close-resource. This will also remove any other resources higher on the stack.

child.dispatchEvent(new CustomEvent('hydrofoil-append-resource', {
  bubbles: true,
  composed: true,
  detail: {
    resource: removedResource,
  },
}))
Examples
Before event After Note
1. resA hydrofoil-append-resource
- parent: resA
- resource: resB
1. resA
2. resB
Add resB to stack
1. resA
2. resB
hydrofoil-append-resource
- parent: resA
- resource: resC
1. resA
2. resC
Replace resB with resC
1. resA
2. resC
hydrofoil-append-resource
- parent: resC
- resource: resD
1. resA
2. resC
3. resD
Further append resD
1. resA
2. resC
3. resD
hydrofoil-close-resource
- resource: resC
1. resA Remove resC which also discards resD

Compatibility

(Loading compatibility data...)

Was this helpful? Need more help?
Leave a comment or a question below. You can also join the chat on Discord or ask questions on StackOverflow.

Version

Dependencies

  • @babel/core#^7.4.4
  • @babel/preset-env#^7.4.4
  • @lit-any/lit-any#^0.8.1
  • ld-navigation#^0.5.2
  • lit-element#^2.0.0
Released
2019-05-08
Maturity
IMPORTED
License
MIT License

Compatibility

Framework
Browser
Browser Independent

helium-animated-pages - Vaadin Add-on Directory

A light spiritual succesor to neon-animated-pages using only css animations helium-animated-pages - Vaadin Add-on Directory
# `` [![Published on webcomponents.org](https://img.shields.io/badge/webcomponents.org-published-blue.svg)](https://www.webcomponents.org/element/helium-animated-pages)[![npm version](https://badge.fury.io/js/helium-animated-pages.svg)](https://badge.fury.io/js/helium-animated-pages) ###### [API](https://github.com/alangdm/helium-animated-pages/wiki/API) | [Demo](https://helium-animated-pages.glitch.me/demo/) | [Using it in `pwa-starter-kit`](https://github.com/alangdm/helium-animated-pages/wiki/Usage-in-pwa-starter-kit) This is a light spiritual successor to the now deprecated [``](https://www.webcomponents.org/element/PolymerElements/neon-animation/elements/neon-animated-pages). It works with css animations and only depends on [lit-element](https://github.com/Polymer/lit-element) so you don't have to worry about including any heavy js libraries. This component takes care of the logic behind triggering the animations so that you can focus on making your views and your animations (or just use the animations included in the `sample-animations` folder if you don't want to bother with those either �.) It can be easily used in [pwa-starter-kit](https://github.com/Polymer/pwa-starter-kit/) and [here's how](https://github.com/alangdm/helium-animated-pages/wiki/Usage-in-pwa-starter-kit). To begin using it just follow this simple steps: - Install it: `npm i --save helium-animated-pages` - Import the script: In html: ```html ``` In a js module: ```javascript import 'helium-animated-pages/helium-animated-pages.js'; ``` - Create an instance of `` in your HTML page, or via any framework that [supports rendering Custom Elements](https://custom-elements-everywhere.com/) and start using it: ```html

Select a page

Page 1
Page 2
``` ## Credits Almost all sample animations and the overall flow of the page selection are based on an article by [Pedro Botelho@Codrops](https://tympanus.net/codrops/2013/05/07/a-collection-of-page-transitions/).
View on NPM
View on GitHub

helium-animated-pages version 0.1.1
### Dependencies * @polymer/lit-element#^0.4.0 * @webcomponents/webcomponentsjs#^1.0.20

helium-animated-pages version 0.2.0
### Dependencies * @polymer/lit-element#^0.4.0 * @webcomponents/webcomponentsjs#^1.0.20

helium-animated-pages version 0.3.0
### Dependencies * @polymer/lit-element#^0.4.0 * @webcomponents/webcomponentsjs#^1.0.20

helium-animated-pages version 0.4.0
### Dependencies * @polymer/lit-element#^0.5.1

helium-animated-pages version 0.4.1
### Dependencies * @polymer/lit-element#^0.5.1

helium-animated-pages version 0.4.2
### Dependencies * @polymer/lit-element#^0.5.1

helium-animated-pages version 0.5.0
### Dependencies * @polymer/lit-element#^0.6.2

helium-animated-pages version 1.0.0
### Dependencies * lit-element#^2.0.1

helium-animated-pages version 1.0.1
### Dependencies * lit-element#^2.0.1

Online