You need to inject the dependency into your app, like so .module('MyApp', ['ngMaterial']), and make sure the js for ngMaterial is loaded in your index.html. Just rewriting ".module('MyApp', ['ngMaterial'])" in the codepen seems to do the trick

Yes . I too had the same issues. The effect is purely dependent on the dimension of the object. for eg a 512*512 image gave me perfect circled ripple effect and a rectangular button on the bottom of the screen gave me oval/ellipsed effect. so i added a small square...

The problem is that you have this: <html lang="en" ng-app="StarterApp"> And this: angular.module('sliderDemo1' Either they should both be StarterApp or they should both be sliderDemo1: <html lang="en" ng-app="StarterApp"> angular.module('StarterApp' Or <html lang="en" ng-app="sliderDemo1"> angular.module('sliderDemo1' Also note that the HTML references {{rating}} which is never defined. That seems like a mistake...

Short answer: Add the following to your css: .md-toolbar.md-tall { max-height: 0px; } CodePen: http://codepen.io/anon/pen/WvodLL Long answer: Angular material's toolbar (md-toolbar) has a height of 64px. Angular actually sets the height, min-height and max-height to 64px. The tall toolbar (md-toolbar.md-tall) has double that height (and min-/max-height as well). See https://github.com/angular/material/blob/master/src/components/toolbar/toolbar.scss...

Ok I figured it out. Turns out you do have to set the background to a drawable (thanks @Nilesh), but there was something wrong with the drawable I was setting it to. I used this: <?xml version="1.0" encoding="utf-8"?> <layer-list xmlns:android="http://schemas.android.com/apk/res/android"> <item> <shape android:shape="oval"> <solid android:color="@color/al_color_accent_orange_light"/> </shape> </item> </layer-list> as my...

Purpose of having different styles.xml is that you can add changes specific to the Android version. But then you need to maintain same changes in both the files. If you are testing your application on device having Android version 5.0 lollipop then style defined in v21/styles.xml will reflect in your...

itemBackground, itemIconTint and itemTextColor are simple xml-attributes that can be set, though you have to use a custom prefix instead of the android: one. Example <android.support.v4.widget.DrawerLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" android:id="@+id/drawer_layout" android:layout_width="match_parent" android:layout_height="match_parent" android:fitsSystemWindows="true"> <!-- Other layout views -->...

StateListAnimator is an Animator launched when a state has been changed. It's possible to implement that on older versions of Android. I'm working on backporting those in Carbon, but for now the library supports only elevation animation. To implement a state animator extend a View, and override drawableStateChanged: 397 @Override...

I suggest to you to use FloatingActionButton included in Android Design Support Library. Simply add compile 'com.android.support:design:22.2.0' to your Gradle file, and use the FloatingActionBar view class into your layout! Example: <android.support.design.widget.FloatingActionButton android:layout_width="wrap_content" android:layout_height="wrap_content" android:clickable="true" android:src="@drawable/your_drawable" /> ...

The standard ScrollView is only meant to be used as a parent. You need change the scrollview to a android.support.v4.widget.NestedScrollView. An example can be seen in the reference documentation for AppBarLayout....

You can use android:background="?android:attr/selectableItemBackground" to get a rectangular ripple. Alternatively, you can create your own drawable. Here's the XML for the framework's selectable item background: drawable/item_background_material.xml: <ripple xmlns:android="http://schemas.android.com/apk/res/android" android:color="?android:attr/colorControlHighlight"> <item android:id="@android:id/mask"> <color android:color="@android:color/white" /> </item> </ripple> ...

The FloatingActionButton from this library extends ImageView which extends View: https://github.com/makovkastar/FloatingActionButton/blob/master/library/src/main/java/com/melnykov/fab/FloatingActionButton.java It is not a subclass of the Android Button. Cast instead to FloatingActionButton: FloatingActionButton myButton = (FloatingActionButton) findViewById(R.id.fab); ...

Here's the way I managed to do this, I don't think that's the best solution though if anyone finds a better way please feel free to post the answer. <android.support.design.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" android:id="@+id/main_content" android:layout_width="match_parent" android:layout_height="match_parent" android:fitsSystemWindows="true"> <android.support.v4.view.ViewPager android:id="@+id/viewpager"...

I was able to recreate exactly what you are looking to implement. I am using the this Library for the tabs. This is the view I have created: Import Library Through Dependencies or Download Project and Import Manually compile 'com.jpardogo.materialtabstrip:library:1.0.9' styles.xml <resources> <style name="AppTheme" parent="Theme.AppCompat.Light.NoActionBar"> <item name="colorPrimary">@color/primary</item> <item name="colorPrimaryDark">@color/primary_dark</item> </style>...

It is possible to make the snackbar appear on top of the screen using this: Snackbar snack = Snackbar.make(parentLayout, str, Snackbar.LENGTH_LONG); View view = snack.getView(); FrameLayout.LayoutParams params = (FrameLayout.LayoutParams)view.getLayoutParams(); params.gravity = Gravity.TOP; view.setLayoutParams(params); snack.show() Note: The animation from the snackbar begins from the bottom and surges up to the top...

Thanks to @anil Finally i find two way for problem : change source file encoding in Settings>File Encoding : if problem not resolve : First way + Using Strings from resources (R.String.nameOfString) instead type them directly in Java source code ...

You can rely on Angular to do the validation for this, rather than the browser. Here's my forked example: http://codepen.io/anon/pen/rVGLZV Specifically: <button type="submit" ng-disabled="myForm.$invalid">submit</button> To keep the submit button disabled until the form is valid and, <form novalidate name="myForm"> To name the form and tell the browser not to do...

You can use the style="?android:attr/borderlessButtonStyle" as a Button's style. This will give you a flat style look and will work on any pre-lollipop devices too. Reference: http://developer.android.com/reference/android/R.attr.html#borderlessButtonStyle If you are not interesed in backward compactibility then use can use the Raised Button which has the ripple effect and requires a...

I don't know what's your approach, but if you need a good FAB I can recommend this library Clans/FloatingActionButton This library requires Android API Level 14+; its easy to use and you no need to worry about Google FAB design or Lollipop target and include goods animations and very fast...

Is there no way for me to force NavigationView to stop tinting my icons? There sure is. You can do so programmatically using NavigationView.setItemIconTintList. And you can do so in your XML layout by using the NavigationView.itemIconTint attribute. Programmatically yourNavigationView.setItemIconTintList(null); From XML <android.support.design.widget.NavigationView ... app:itemIconTint="@android:color/black" ... /> Results ...

as you can see from your own code ('setBackground') , you're setting the ripple as a BACKGROUND that's why it's being drawn on the background. ImageView on android API 21 added this "hack" for the ripple android:drawSelectorOnTop="true". But the library you're using didn't add the same hack to it. There's...

I was looking into animations with md-list today. I simplified your code and adjusted the layout to get it to work. I also updated to latest material and angular 1.4.1. This should be enough to get u started: http://plnkr.co/edit/y1SClyHOT2GEnXvdhvlf?p=preview ...

The Toolbar is a generic component that can be added to any part of your UI - when used as the primary action bar for branding, navigation, and actions, it is called an App Bar. From the metrics on the App Bar, the correct heights are: Mobile Landscape: 48dp Mobile...

Taking a hint from @Zielony's answer I did the following: 1) Instead if using an ActionBar or ToolBar I built my own layout (basically a RelativeLayout with burger menu, search and other menu buttons and a EditText for search) 2) Used a theme without an ActionBar, placed my custom layout...

I find a solution. I made the following update to my layout: Linear Layout ToolBar Linear Layout (id: parentScroll) SlidingTabLayout ViewPager Frame Layout (id: parent) So when I need to hide all the tabs and the ViewPager, in order to inflate a new Fragment in the Frame Layout, I do...

You can pass the $scope of your controller to your $mdDialog as an example below $mdDialog.show({ parent: angular.element(document.body), template: tmpl, scope: $scope, controller: 'myCtrl' }); Check plunkr : http://plnkr.co/edit/0hFWEyWdetTXcPLPkbmQ?p=preview To move application logic to factory you will be doing something like this $scope.upload = factory.upload(files,$scope.username); and factory will have method...

Question 1 Add android:fitsSystemWindows="true" to your AppBarLayout, CollapsingToolbarLayout, and to your ImageView. I'm guessing a part of your image is below the status bar (due to these lines being missing) which is why you can't see the top of the image. Question 2 collapseMode="pin" only affects how the Toolbar reacts...

Sorry about my earlier answer, I thought you were not getting the modal to work at all... You used some CSS rules that affect the responsiveness and width of the modal, and for center aligning the content in the modal you just need another rule. Just modified the CSS, replaced...

Here is a complete list of all the material design colors you will ever need. If you're looking for good color combinations for your app, then check out Material Palette Edit: Here is an XML file containing all(?) of the Material design colors....

The best way is add it in your AndroidManifest file. You can apply a theme to any activity by including android:theme inside <activity> inside manifest file. For example: <activity android:theme="@android:style/Theme.Dialog"> <activity android:theme="@style/CustomTheme"> And if you want to set theme programatically then use setTheme() before calling setContentView() and super.onCreate() method inside...

Well, the is an alternative solution provided by this website. It's include preety much a good number of icons such as social buttons. http://materialdesignicons.com/getting-started You just have to add this css link to get the icons and add them as classes <link href="css/materialdesignicons.min.css" media="all" rel="stylesheet" type="text/css" /> and <i class="mdi...

I haven't used the Ionic Material tool much, but agree it is primarily a fun dev tool and not ready for production (not that it might be eventually, but its certainly not as field tested as Ionic itself). Can Ionic and jQuery work together? Sure. Its really can Angular and...

you can use a ListPopupWindow, submitting your custom adapter, through which you can control the layout of every single row of the ListPopupWindow. As for a normal PopupWindow you have to provide an anchor view and additionally you have to call setContentWidth on the instance of ListPopupWindow, which sets the...

After a lot of research, I've found the proper way to use FAB with no issues. Use the code below as template: <android.support.design.widget.FloatingActionButton xmlns:app="http://schemas.android.com/apk/res-auto" android:id="@+id/your_id" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_alignParentBottom="true" android:layout_alignParentRight="true" android:layout_marginBottom="@dimen/floating_button_margin_bottom" android:layout_marginRight="@dimen/floating_button_margin_right"...

If you are using Android Support Library revision 22.2, be aware that floating toolbars are not backward-compatible and appcompat takes control over ActionMode objects by default. so this will only work on Android-M preview you can test by creating AVD M-preview emulator. Here this link shows Behavior change...

The CircleImageView is a private class of the support library and cannot be used. But it is easy to create this effect yourself without the CircleImageView. You just need to define a <shape /> drawable with a transparent circle in the middle similar to this: <shape android:innerRadius="0dp" android:shape="ring" android:thicknessRatio="1" android:useLevel="false"...

This is not possible with existing version of angular material (v0.9.0) but is targeted to v0.10.0. See more information here: https://github.com/angular/material/issues/2802#issuecomment-101764802 However, there is a Angular directive that might be used as a workaround. https://github.com/dcohenb/angular-clear-input...

Designing the Toolbar: Looking at these specifications and guidelines from Google, I managed to setup my extended Toolbar how I wanted using the correct specifications and measurements. In my case, I was using Fragments to change the main content (where the Views inside the extended Toolbar would also be different),...

If you check source code of Toolbar and Toolbar's custom attributes, there are only a few attributes you can use to customize Toolbar, but logo is not one of them: titleTextAppearance subtitleTextAppearance navigationIcon ... Toolbar.setLogo(resId) seems to be the only option at the moment....

You need to add app:layout_behavior="@string/appbar_scrolling_view_behavior" to your NestedScrollView - this marks the class which should be positioned below the AppBarLayout (and hence, below the CollapsingToolbarLayout).

Ok. So I found a great way to change the color dynamically for things like the new cards feature on Material Design. A how-to can be found here. This code allows you to generate the palette synchronously when you have access to the underlying image loading thread. To have access...

Simply remove: <item name="android:windowTranslucentStatus">true</item> from the "BATheme", or change it in: <item name="android:windowTranslucentStatus">false</item> if there a styles.xml with that parameter set as true....

Width is: Mobile: Width = Screen width − 56 dp Maximum width: 320dp Maximum width applies only when using a side nav on the left. When using a panel on the right, the panel can cover the full width of the screen. http://www.google.com/design/spec/layout/structure.html#structure-side-nav Height is determined by the aspect ratio...

I found my problem, it wasnt clearly in my question because i didnt posted the AbstractActivity class, where I was already calling the setContent method, so the problem was that I was calling setContent twice.. Thanks for your help.

Right, I have come up with a similar look to show that this sort of thing is possible via CSS only. You will notice some differences, some of which maybe the way I coded this but you get the point. So here it is! Note: Stackoverflow's code snippets don't...

I am author of Transitions-Everywhere, so maybe i can help. Any real reasons to use different fragments in this case? Fragment transitions are not backported for now, i doesn't have to much free time for this. You can perform transition this way: TransitionSet transitionSet = new TransitionSet(); transitionSet.addTransition(new Slide(Gravity.BOTTOM)); transitionSet.addTransition(new...

As for Snackbar,it acts like a Toast but is different with a Toast. Snackbars are shown on the bottom of the screen and contain text with an optional single action. They automatically time out after the given time length by animating off the screen. In addition, users can swipe them...

This is known by Google and will be fix soon in the next version of the Design Support Library, see this issue: FAB Appears as a square on API 16. It should only concern API 16. The workaround, proposed in the same thread, is to add app:borderWidth="0dp" to your FAB....

Try adding <item name="android:windowTranslucentStatus">false</item> <item name="android:fitsSystemWindows">false</item> to either values/styles.xml or values-v21/styles.xml. When you define a style for a certain API level it will be applied not only to that version, but also to all higher versions, unless explicitly specified otherwise....

As you are using appcompat you can add this to the XML for your navigation drawer item android:background="?attr/selectableItemBackground". This should provide the ripple effect on Lollipop devices and a fallback grey highlight for older devices....

The solution to do that is pathInterpolator and the name of this effect is Curved Motion. Animations in material design rely on curves for time interpolation and spatial movement patterns. With Android 5.0 (API level 21) and above, you can define custom timing curves and curved motion patterns for animations....

The Design Support Library only provides some components introduced by Material Design. To use the Material Design theme, you have to use AppCompat Support Library (or set your minSdkVersion to 21 or higher). So even if you are developing for API 21+, you still won't have access to those components...

Materialize datepicker is a modified pickadate.js picker. Accodging to their API docs, this is how to set the picker: Get the picker: var $input = $('.datepicker').pickadate() // Use the picker object directly. var picker = $input.pickadate('picker') Set the date: // Using arrays formatted as [YEAR, MONTH, DATE]. picker.set('select', [2015, 3,...

You can use limited features from material design in pre-lollipop versions. No Path Animations and such. Check out this link to see which features can be backported. http://android-developers.blogspot.com/2014/10/appcompat-v21-material-design-for-pre.html Although now it is appcompat-v22 which is the latest SDK released by Google....

Looking at the source for NavigationView, they currently do not support any custom rendering of the menu items (See NavigationMenuPresenter and NavigationMenuAdapter). Hopefully they expose more functionalities soon as I want to set a custom font on the menu items but am unable to without using reflection.

You can use the support libraries to backport some features introduced with the last api (for example 21) to old devices running a previous api level. For example, API21 introduced a new widget, the Toolbar. This widget can be used only in device with API >=21. With the appcompat rel.21...

On Lollipop versions it's fine but it's not working at all when I deploy on a device with API lower than v21, I still see the black status bar and the primaryDark is totally ignored. Is it the right way? Your primary dark is ignored on all pre-lolipop devices...

Is like a pre-load of the next tab for performance optimization? Yes. How can I avoid it? Don't use ViewPager. The idea behind ViewPager is that the user can swipe between pages. That requires the pages on either side of the current page to be loaded, so the animation...

What am I missing? Action bar tabs were deprecated in Android 5.0, last fall. Can someone point me in the right direction for developing a tabbed application. Use TabLayout, though this is a very new addition to the Android Support libraries. Or, use ViewPager with your favorite tabbed indicator,...

I believe you need to make your ListView implement both ScrollingView and NestedScrollingChild interfaces. It's not the easiest thing, but you should be able to do it if you look at RecyclerView's source code. It makes use of a NestedScrollingChildHelper and you should be able to do the same....

Make sure you have the correct dependency to the Android Design Support Library. It's easy to choose the wrong one - because it seems that Google postet two different dependency strings: At the time of this answer, the Android developer blog (and the comment by user hungryghost) had the correct...

There's no stock Android implementation of FAB, but I've used this implementation of FAB's in couple of my projects and its working great and supports the material greatness! so given the fact that there's no FAB implementation on Android, you should go for a 3rd party implementation By shifting views...

You are creating all the Material Design CSS & Jquery by yourself? Otherwise, I found Material Design textarea like you mentioned in here: Source: http://materializecss.com/forms.html Check out their Textarea part....

It's called CollapsingToolbarLayout (it's very easy to implement), check new Design Support Library: http://developer.android.com/reference/android/support/design/widget/CollapsingToolbarLayout.html http://android-developers.blogspot.com/2015/05/android-design-support-library.html...

Which version are you using? If you are using the latest version, there are no separate built-in themes in angular material design, as they used to be. You will have to configure themes in your app config, as below. The below example changes the primary pallette to blue for default...

Polymer is not equal to material design. It's only a library that makes developing web components a lot easier. It won't stop you from creating new components that follow other design guidelines (although currently the paper-elements make most of the UI web components provided by Polymer). And as for styling,...

You are looping the creation of a static ID tag, and because you shouldn't have duplicates of an ID, it is throwing an error. Lines causing the issue: <template repeat="{{data}}" > <core-localstorage id="storage" name="codelab-app-storage" value="{{data}}"></core-localstorage> </template> ...

As mentioned by @shkschneider, this is a known bug. Github user @ljubisa987 recently posted a Gist for a workaround: https://gist.github.com/ljubisa987/e33cd5597da07172c55d As noted in the comments, the workaround only works on Android Lollipop and older. It does not work on the Android M Preview....

Scrollbar thumb color is set to the android:colorAccent attribute in your app theme. You are sure that is set and is correct, right? Note that if you're using AppCompat, you will have to exclude the android: prefix from the attribute. You can find more information on available color attributes here....

What you're looking for is a translucent status bar. When you have this configured you're able achieve this effect. Make also sure to remove the actionbar as I do in my example down below, otherwise you'll have to make it transparent. Change your v21/themes.xml file to this: <style name="Theme.MyTheme" parent="Theme.AppCompat.Light.NoActionBar">...