Material Design Lite lets you add a Material Design look and feel to your websites. It doesn’t rely on any JavaScript frameworks and aims to optimize for cross-device use, gracefully degrade in older browsers, and offer an experience that is immediately accessible.
Visit MDL's website to learn how to get started with MDL.
-
(New!) Theme color customization (See details below.)
-
(New!) Full access to SASS source code (See details below.)
-
Exports
componentHandler
globally (Client Only). -
It auto-upgrades everything for you by default, so you can sit back and relax.
-
Exports
MDl
globally on the client for changing settings in runtime.-
MDl.componentHandler
mirrorscomponentHandler
. -
MDl.settings
stores a copy of the loaded settings. You should not modify it. Treat this as readonly. -
MDl.autoUpgrade
stores the instance of the autoUpgrader. Read more about it below.
-
$ meteor add zodiase:mdl
(Important change since version 1.0.6_4
) After installing, create an empty settings file zodiase-mdl.json
under the root of your app. Without it most functions will be disabled.
Other than that, there is nothing special to do. Enjoy! :D
If you want to pick your own theme, like what the MDL team have here, here's how:
-
First pick your theme colors from that page. You would have to pick both the primary color and the accent color.
-
Note that on the lower part of that page, there's a link that basically tells you what colors you have picked.
- The link is always composed by
material.{primary}-{accent}.min.css
. I pickeddeep_orange
andblue
for example, and that link looks likematerial.deep_orange-blue.min.css
.
- The link is always composed by
-
Now create a
zodiase-mdl.json
file under the root of your app if you haven't already. This file stores the settings. -
In that setting file, compose a JSON document that looks similar to this:
{ "theme": { "primary": "deep_orange", "accent": "blue" } }
-
This will tell the package to load the corresponding theme file.
You can load up the SASS source code and define your own colors!
-
First you'd need to tell the package not to load any theme file.
{ "theme": false }
-
Define your own theme colors and load MDL's SASS code.
// mdl-theme.scss $color-primary: "0,0,0"; $color-accent: "255,255,255"; @import '{zodiase:mdl}/theme';
-
There you go!
-
There's a full range of variables you can customize. Check out MDL's variables to learn more.
They are all under {zodiase:mdl-assets}/src
so have fun!
One big thing this package does for you is auto-upgrading everything.
This feature is enabled by default. You can disable it within the settings file:
{
"patches": {
"autoUpgrade": false
}
}
Doing so would turn off the entire auto-upgrader to save memory. However, this also means that you can NOT use it later in runtime. When auto-upgrader is turned off, MDl.autoUpgrade === null
.
Aside from false
, autoUpgrade
can take one of the three other values: ["fullUpgrade"|"mutationOnly"|"none"]
, with "fullUpgrade"
being the default.
-
"fullUpgrade"
usescomponentHandler.upgradeAllRegistered()
when any mutation is observed. -
"mutationOnly"
usescomponentHandler.upgradeElements(mutation.target)
on mutations when any mutation is observed. -
"none"
does nothing. However the observer still stays in the memory.
While at runtime and the auto-upgrader is not turned off in the settings, MDl.autoUpgrade
is the instance of the auto-upgrader with the following interfaces:
-
MDl.autoUpgrade.getUpgradeStyle()
returns the current auto-upgrading style. -
MDl.autoUpgrade.setUpgradeStyle("fullUpgrade" | "mutationOnly" | "none")
sets the auto-upgrade style.
Note that at this point in runtime it is impossible to turn off auto-upgrader any more. So false
is not an acceptable value for .setUpgradeStyle()
.
-
Do not use MDL components at the top level of any templates or template event handlers may not work correctly.
-
Understand how MDL upgrades components and do not separate the necessary elements of a component into different templates unless you want to turn off auto-upgrading and do it manually.
The version of this package matches MDL's version to make it easy to perceive what version of MDL it contains. In addition, it has a fourth version number indicating revisions not related to MDL.
(MDL source is owned by Google and licensed under an Apache-2 license.)
© Xingchen Hong, 2015. Licensed under an Apache-2 license.