npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ivanvanderbyl/ember-material-components-slider

v0.77.1-alpha.2

Published

ember-cli addon for @material/slider.

Downloads

3

Readme

@ivanvanderbyl/ember-material-components-form

ember-cli addon for @material/slider.

Installation

ember install @ivanvanderbyl/ember-material-components-slider

Components

This package contains the following top-level components.

mdc-slider

Description

Add a Material Slider component to the parent element.

Usage

{{mdc-slider min=min
             max=max
             value=value
             discrete=[true|false]
             displayMarkers=[true|false]
             change=(action "change")
}}

Attributes

  • min - The minimum value for the slider.
  • max - The maximum value for the slider.
  • value - The current value of the slider.
  • label - The accessibility label for the slider.
  • discrete - Make the slider a discrete slider; default is false.
  • displayMarkers - Show markers on the slider (only if discrete=true)
  • change - The action f(value) called after slider value is committed.

Examples

{{mdc-slider min=0 max=100 value=value
             label="Select value"
             change=(action (mut selected))}}

Value vs. Change

The value attribute of the mdc-slider will change instantaneously as the slider is moved from side to side. The change action is called only when the slider stops moving. This means the user has selected a terminal value, and the slider is committing the value.

Layout Requests

There are cases when you will need to manually request the slider to update its layout in order for the component to function correctly. For example, if the slider is initially rendered of screen, say in a menu, and the menu is transitioned onscreen, then the slider will not slide. This is because the layout of the slider is based on its initial location, and not its new location on the screen. This is a known issue with the material-components-web slider component.

To address this concern/issue, the mdc-slider component has a requestLayout attribute that can be set to signal the component to update its layout. To use this attribute, its best to

  1. Have the mdc-slider component be a child of a Ember component (let's call it ParentComponent).
  2. Make the ParentComponent aware of when its layout has changed, such as listening for transitionend events and updating its internal state (e.g., openComplete).
  3. Share the ParentComponent data with its wrapped content (see Sharing Component Data with its Wrapped Content)
  4. Bind the requestLayout with the parent component openComplete state.

Here is an example illustrating this approach. Let's assume we have a menu that initially starts offscreen and then slides on screen.

{{#m-menu open=open as |m|}}
  {{mdc-slider min=0 max=100 value=50 requestLayout=m.isOpenComplete}}
{{/m-menu}}

{{#unless open}}
  <button {{action (mut open) true}}>open</button>
{{else}}
  <button {{action (mut open) false}}>close</button>
{{/unless}}

As shown in the example above, we have m-menu component. The m-menu component is sharing its data (i.e., state) with mdc-slider component. As the menu state changes (i.e., the open variable changes causing the menu location to transition), the slider will make a layout request at the end of the transition.

For completeness, here is the m-menu component implementation:

import Component from '@ember/component';
import layout from '../templates/components/issue7-menu';

export default Component.extend({
  layout,

  classNames: ['m-menu'],

  classNameBindings: ['open:m-menu-open'],

  open: false,

  isOpenComplete: false,

  _transitionEndListener: null,

  init () {
    this._super (...arguments);

    this._transitionEndListener = this._transitionEnd.bind (this);
  },

  didInsertElement () {
    this._super (...arguments);

    // Listen for the transition end event.
    this.element.addEventListener ('transitionend', this._transitionEndListener);
  },

  _transitionEnd () {
    // Update the open complete state.
    const isOpenComplete = this.element.classList.contains ('m-menu-open');
    this.set ('isOpenComplete', isOpenComplete);
  }
});

and here is the SASS for the component.

.m-menu {
  border: solid 1px;
  transform: translateX(-100%);
  transition: all .5s;

  &-open {
    transform: translateX(0);
  }
}