Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 11 2016 19:26

    Splaktar on master

    fix(toast): apply theming corre… perf(icon): better handling of … fix(list): copy ng-show, ng-hid… and 49 more (compare)

  • Jun 15 2016 16:14

    Splaktar on v1.1.0-rc.5

    release: version 1.1.0-rc.5 (compare)

  • May 14 2016 05:55

    Splaktar on master

    feat(panel): initial implementa… update(panel): promise logic im… update(panel): add and remove p… and 44 more (compare)

  • May 05 2016 20:47

    Splaktar on v1.1.0-rc4

    release: version 1.1.0-rc4 (compare)

  • May 05 2016 20:47

    Splaktar on v1.1.0-rc3

    release: version 1.1.0-rc3 (compare)

  • May 03 2016 22:28

    Splaktar on es6-tutorial

    Prepare clean start Remove bow… install angular-material And i… working version of starter-app and 19 more (compare)

  • May 03 2016 22:22

    Splaktar on master

    Tutorial Readme updates Updates for Tutorial #2 Update README with tutorial ste… and 56 more (compare)

  • May 01 2016 22:56

    Splaktar on fixBlurryRightNavIe11

    fix(sidenav): rightNav button a… (compare)

  • May 01 2016 22:37

    Splaktar on master

    fix(dialog): don't clobber md-d… update version number in packag… update(changelog): sort so 1.1.… and 1 more (compare)

  • May 01 2016 22:34

    Splaktar on fixSideNavDemo

    docs(sidenav): leftNav text isn… (compare)

  • Apr 27 2016 04:14

    Splaktar on fixSideNavDemo

    docs(sidenav): invalid `md-whit… (compare)

  • Apr 27 2016 03:54

    Splaktar on master

    update(changelog): add missing … fix(toolbar): remove transition… fix(tests): Cleans up the DOM a… and 2 more (compare)

  • Apr 23 2016 01:32

    Splaktar on master

    update(docs): improve docs for … update(docs): renamed `md-text-… fix(list): clickable list-items… and 71 more (compare)

  • Apr 11 2016 03:20

    Splaktar on improveExtendThemeDoc

    update(docs): improve docs for … (compare)

  • Apr 11 2016 03:15

    Splaktar on improveExtendThemeDocs

    update(docs): improve docs for … (compare)

  • Apr 11 2016 02:57

    Splaktar on updateThemingDocs

    update(docs): renamed `md-text-… (compare)

  • Apr 11 2016 02:48

    Splaktar on master

    fix(demo, codepen): use secure … fix(build, layout): remove depr… update(build): remove stale bow… and 72 more (compare)

  • Apr 11 2016 02:48

    Splaktar on v1.1.0-rc2

    release: version 1.1.0-rc2 (compare)

  • Mar 19 2016 03:00

    Splaktar on master

    fix(checkbox): pointer events d… update(tests): remove disabled/… fix(datepicker): enable scrolli… and 20 more (compare)

  • Mar 13 2016 05:41

    Splaktar on v1.0.6

    Revert "fix(select): made selec… update(layout): add layout-nowr… fix(whiteframe): update breakpo… and 57 more (compare)

Guilherme Corte-Real
@guic-io
this material thing is the next flat scene
thanks for sharing :)
Andrew Koroluk
@Awk34
It looks like the alert modal only showing up on the top of a scrollable document is back
Eduardo Alejandro Pool Aké
@epool
I report a similar issue angular/material#632 but I'm not sure if it's the same problem
Reydi Sutandang
@reydi
How do we implement dropdown
Dave Gavigan
@dgavigan
Common question, but there is no dropdown implemented at this time @reydi. slated for a future release. see angular/material#78
Christophe Willemsen
@ikwattro
Hi, 1st thanks for the impressive work you do
2nd is there a way to modify only the interpolates of the dialog templates ?
and not the rest of the content of the dialog ?
Reydi Sutandang
@reydi
@dg1202 thanks, seems it sets for ver 0.7 milestone already
Paul Mougel
@PaulMougel
@reydi Looks like it is moved to 0.8 unfortunately!
bastienJS
@bastienJS
hello guys, what is the difference between angular/material and https://github.com/lumapps/lumX
Are both angularjs frameworks following googles material design specification is that correct?
Marcy Sutton
@marcysutton
Whoa this app is so cool!
@bastienJS Angular Material is led by Google and some core contributors (such as myself), while Lumx is by a separate effort for the time being. Lumx was built fast for their own purposes, but things like accessibility were not considered like they are in Angular Material. But yes, they are both based on the Material Design spec.
Georgi Georgiev
@gngeorgiev
@epool with 0.6.1 I have the same behavior with various components. If this is a mobile app do not worry as the scrollbar will not appear in the webview. If it is not you should search for a way to hide it for the time being
McKenzie Long
@mckenzielong
Hey, I am curious about this: https://groups.google.com/forum/#!topic/ngmaterial/4M86fKpQzN8 ripple going over top of text / icons. Seems like this isn't inline with the spec?
Stalin Pereira
@imatefx
hii guys, how can i use the themes provided in material.angular.org, even if i provide the md-theme it is using only the default theme
Ed Pelc
@epelc
@imatefx add md-theme="yourThemeName" to an element for its children to use your theme
Eduardo Alejandro Pool Aké
@epool
@imatefx you should import the styles .scss in case you didn't
Ed Pelc
@epelc
@marcysutton you here?
Marcos Pereira
@marcospgp
@epelc
Ed Pelc
@epelc
o hello
I just replied to your comment but I would say keep using it for now and perhaps open an issue about adding icon support to the radio groups
I think even though you and several other people may not care about accessibility it's a core aspect of the project and we need to respect that
Marcos Pereira
@marcospgp
Yea I completely agree
I just don't really think those are reasons to make something private, just make it all available and let people choose what rules to follow, still of course encouraging the best practices
but making the ripple effect a documented feature wouldn't really be considered encouraging a bad practice aha
Ed Pelc
@epelc
also I don't think its going away anytime soon so in the mean time you should be safe using it. It's just that formally documenting it is essentially like signing a contract which would be bad later down the line when we have no need for this
Marcos Pereira
@marcospgp
still, not up to me. as long as the directive itself is not removed, I'll be fine aha
yep exactly that aha
Ed Pelc
@epelc
The whole idea is that we would support all logical use cases which yours seems like a perfectly good one to extend the radio group for
Marcos Pereira
@marcospgp
Yea I would expand on that radio group idea if it would bring me any advantages, but right now it'd just be wasting time since the divs work well for me
Ed Pelc
@epelc
ok I'd suggest you just keep using it for now then. But I don't think it will be formally documented. I've also just asked for final consensus to close that issue.
Marcos Pereira
@marcospgp
wait a second