With Angular you usually have only one page where different views of your application are shown (one view replaces another without reload https://en.wikipedia.org/wiki/Single-page_application). Of course if you have only have CSS and just a bit of code (like in MDL) you can't expect the same functionality like when you have a full-featured application framework like Angular where the components all make use of Angulars features.
On Monday, January 18, 2016 at 10:41:17 AM UTC+1, Sergei Struk wrote: > > MDL looks worse, also it provides much less features. I ask about Angular > Material, because I worry about application performance if I load it on > each page. > > On Monday, January 18, 2016 at 9:14:22 AM UTC+2, Günter Zöchbauer wrote: >> >> If you don't want to use Angular you can use MDL >> https://github.com/angular/angular/issues/4933 >> If you use Angular Material you have to use Angular anyway to configure >> and control the components. >> >> On Sunday, January 17, 2016 at 11:32:46 PM UTC+1, Sergei Struk wrote: >>> >>> I have usual multi-page project (about 30 separate pages). I'd like to >>> use Google Material Design for all of them. >>> I reviewed different solutions and found that Angular Material provides >>> the most appropriate one for my case. But Angular Material works only >>> together with basic Angular framework. >>> So I will need to load Angular on each page to use Angular material. Is >>> it good approach? As I understand basically Angular is used for single-page >>> applications. >>> >> -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
