bbweb/d-md-components

A pack of components according to Google's Material Design based upon mdl (getmdl.io)

d-md-components

A pack of components according to Google's Material Design based upon mdl (getmdl.io)

Uses css from material-design-lite - Material Design Components in CSS, JS and HTML.
Version: 1.0.2
License: Apache-2.0
Copyright: 2015 Google, Inc.
Link: https://github.com/google/material-design-lite

Tested with above version, file in repository.

Usage

Including

var mdlComponents = require('d-md-components');

app.component(mdlComponents.ComponentName);

Components

• Checkbox
• CheckboxTextfield
• Dialog
• Pagination
• Select
• Slider
• Snackbar/Toast
• Tabs
• Textfield

d-md-components's Issues

Update dialogs README with info about classes for content

Add support for adding a custom class to all components (where sane)

See 084b2ae for how I did it for textfield. This should probably be done in all components. All READMEs should also be updated accordingly.

Add derby-validator support for checkbox-textfield combo

Add derby-validator support for checkboxes and select

And also, check the textarea component

textarea is missing some styles

Specifically:
textarea {
overflow: hidden
resize: none
}
which should be in the component, and not up to the user (imo)

Add docs for each component missing it.

Progress bar and spinner

We should implement components for the progress bar and a spinner. We already have working version of this, but for cleaner/more DRY code it'd be nice to keep them in this module instead.

Implement persistent helper text

At the absolute bottom of https://www.google.com/design/spec/components/text-fields.html#text-fields-required-fields there's a video, where one field has a persistent help text. We should implement support for this. The need rose form a real scenario in one of our projects. I concluded to remove it until we have this solution for it. There are still some questions about what to with errors in such scenario (we should probably discuss), but I can imagine that this will popup again.

textfield does not get proper start height if not visible initially

Solution for when field is empty: Set height to auto if scrollHeight === 0. However, we still don't have a solution for whenever there's a lot of text in the field (as auto only goes so far in such scenarios). One solution to this is to say in the README that the user needs to trigger a function whenever the textarea becomes visible. atm. there is no publicly facing method for this (although _maybeExpand exists - aka. there should be an action for that with a good name).

Further, it would be nice to be able to specify if the textarea should auto-adjust it's height or not.