Description
Bug, feature request, or proposal:
feature
What is the expected behavior?
I would like to be able to reuse some already existing small components (like mat-card-title
) to take more benefit from the lib while creating some specific views.
What is the current behavior?
Some components are/look too limited and they have too few examples in the docs to a beginner understand what can be done.
What are the steps to reproduce?
n/a
What is the use-case or motivation for changing an existing behavior?
Looking at the docs I could only create three types of lists (none of them was the one I wanted)
These are some implementations that I couldn't find in the docs nor implement:
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
TS ~2.5, Ng ~5.1 and NgMat 5.0.2
Is there anything else we should know?
This site has some good examples of things I would like to see in the docs:
http://bitmap9.github.io/materialmockups/
And this site has some very good implementations: https://tina-material-tree.firebaseapp.com/
I found it trought the "tree view" feature "sneak peak" link in the README file, I know that a lot of people here know these example sites, but they are very hard to find because most of times the reader don't realise that these sites have so many good implementations.
Some styles are very similar between components like cards, tiles and lists and we cannot take benefit of the already existing items because they are too specific. For example, I cannot use the mat-card-title
nor the mat-card-image
in a tile because they were made for the card component, but the typografy and the internal layout of both would be the same.
Ignoring the use case, but considering the layout itself, in this example taken from material guidelines the internal layout from both card and tile are exactly the same, the tile even looks lika a flat card or something else.
Also in some web examples we can see that tiles have exactly the same internal layout that cards do: