search

material-components / material-components-web

Modular and customizable Material Design UI components for the web
https://material.io/develop/web
MIT License
17.14k stars 2.15k forks source link

Investigate making Data Table component #57

Open traviskaufman opened 7 years ago

traviskaufman commented 7 years ago

Spec reference: https://material.io/go/design-data-tables

Copied from https://github.com/google/material-design-lite/issues/4504

AndryHTC commented 5 years ago

@kfranqueiro thank you very much for your reply. Really, Vaadin implements material design, so I don't think is off topic... What I mean is that it is a shame that after years of development a lot of essential components are still in a pre-alpha status.

Come on... You are Google, not independent developers who use their free time. The Changelog is not as rich as expected, with very minimal changes to components that already work very well: you can not hide behind these justifications ...

Many people have invested time and resources to implement the MDC library, obtaining only an incomplete and fragmented design

MrSimmmons commented 5 years ago

@AndryHTC Don't be so harsh. Yes they may Google, but all good things take time. Any large project always end up being more complex the more you get into it. And the dev team could easily just focus on making new components, but then this liberty wouldn't be as bug free and robust as it is today

Anyone knows that the more you get into a project, you discover things that you could have done better in the past, so you would want to change it now so it doesn't hang over you for the rest of the development process. Especially when it comes to infrastructure where the more you ignore it, the bigger the problem becomes. Which is part of the reason why there hasn't been much change in the past 2 months.

Firstly, we had Christmas break so the gap in development is understandable. Everyone needs a break after all. And secondly for the past month now the team has been working hard on moving the entire liberty over to TypeScript instead of regular Javascript which will have a number of great improvements down the line. This is something that will take along time to finish as @kfranqueiro has said on numerous occasions. You can check out the progress on that here and this is expected to take most, if not all of Q1 2019

Just because they are Google, doesn't mean that they can just throw a bunch of resources at a project and it comes out fine. Plus, they are doing this for free for everyone! If this was paid software, then I can kinda see where you are coming from. But it's not. So I don't think we can complain about how fast or how slow they work. The team will work at a pace that is right for them.

If you really want a data table that much @AndryHTC that you are prepared to ban mouth the dev team for it, then maybe you should either try to make it your self to see how hard it is, or use another material framework like Angular Material, Material Lite or even Materialize. There are a ton of great options that have all of the components ready to be used.

I just think that if anything, we should congratulate the Dev team for sticking with us and ensuring that all of our questions and issues get answered. I can say with confidence that this dev team has been the most engaged dev team that I have eve worked with when it comes to communicating with their community and listening / acting on feedback and suggestions. So, well done MDC Web team. This resources truly is amazing. :tada::tada::tada:

AndryHTC commented 5 years ago

You should take off your dress of MDC developer, and feel more like an MDC user.

Keep in mind that I didn't say you are not doing anything, or that the components ARE neglected (also if... believe me, they seems. Talking with other developers that check components not so often, they asked me if the project is still under development or if was abandoned): this is the sensation of the users when year after year, wait for components that are always in a pre-alpha state..........

If you think how went with Material design Lite.... It's easy to understand that our disappointment are not the 2 months of slow development...

Sure, thank you for all your hard work... But again these are not a justification

Hope in next months all the preventive optimizations will bear fruit

From: Simon notifications@github.com Sent: Wednesday, February 6, 2019 11:30:59 PM To: material-components/material-components-web Cc: AndryHTC; Mention Subject: Re: [material-components/material-components-web] Investigate making Data Table component (#57)

@AndryHTChttps://github.com/AndryHTC Don't be so harsh. Yes they may Google, but all good things take time. Any large project always end up being more complex the more you get into it. And the dev team could easily just focus on making new components, but then this liberty wouldn't be as bug free and robust as it is today

Anyone knows that the more you get into a project, you discover things that you could have done better in the past, so you would want to change it now so it doesn't hang over you for the rest of the development process. Especially when it comes to infrastructure where the more you ignore it, the bigger the problem becomes. Which is part of the reason why there hasn't been much change in the past 2 months.

Firstly, we had Christmas break so the gap in development is understandable. Everyone needs a break after all. And secondly for the past month now the team has been working hard on moving the entire liberty over to TypeScript instead of regular Javascript which will have a number of great improvements down the line. This is something that will take along time to finish as @kfranqueirohttps://github.com/kfranqueiro has said on numerous occasions. You can check out the progress on that herehttps://github.com/material-components/material-components-web/milestone/17 and this is expected to take most, if not all of Q1 2019

Just because they are Google, doesn't mean that they can just throw a bunch of resources at a project and it comes out fine. Plus, they are doing this for free for everyone! If this was paid software, then I can kinda see where you are coming from. But it's not. So I don't think we can complain about how fast or how slow they work. The team will work at a pace that is right for them.

If you really want a data table that much @AndryHTChttps://github.com/AndryHTC that you are prepared to ban mouth the dev team for it, then maybe you should either try to make it your self to see how hard it is, or use another material framework like Angular Materialhttps://material.angular.io/, Material Litehttps://getmdl.io/ or even Materializehttps://materializecss.com/. There are a ton of great options that have all of the components ready to be used.

I just think that if anything, we should congratulate the Dev team for sticking with us and ensuring that all of our questions and issues get answered. I can say with confidence that this dev team has been the most engaged dev team that I have eve worked with when it comes to communicating with their community and listening / acting on feedback and suggestions. So, well done MDC Web team. This resources truly is amazing. 🎉🎉🎉

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/material-components/material-components-web/issues/57#issuecomment-461214245, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AcgtRN0M_o8a-7wo6kykntVC-QYjL6Unks5vK1ejgaJpZM4LEv2Z.

kfranqueiro commented 5 years ago

While I appreciate everyone's passion, I'd like to again ask that we try to keep the thread on-topic, and reiterate that I'm very much pressing for us to fulfill data tables during Q2 2019.

vguleaev commented 5 years ago

I wanted to create my personal project with MDC but decided to use Angular Material because of lack of Data tables components.. that's sad, hope you implement it soon

iFaxity commented 5 years ago

I gotta be honest. If there is so much outcry for a data table component. Then read the material guidelines and do an implementation yourselves. Or see how other material frameworks did it

It's not too hard. Especially because you only need CSS, otherwise just use Materialize or another open source version. There is at least one for every big framework.

Plus this repo is not very highly prioritized by Google or its employees because they probably have better stuff to do than making free stuff for other lazy developers.

It's very easy to just complain, a lot easier to find another solution. And don't worry, official implementation will probably arrive in the future. Until then, figure out a solution that works for you at the moment.

h4ndshake commented 5 years ago

Christian,

This is Googles design specification, their attitude towards other libraries that implement Material shows you just how much they think about other developers implementations of Material and how inadequate they are.

Also Google is getting free promotion of their design philosophy when people use their library. So it's not like they get nothing when people adopt their library.

Google has more than enough resources to get this done. And your response and Google's response has left a very bad taste in my mouth. If Google doesn't want to do the leg work on their own library, why even make it in the first place?

On Sat, Mar 2, 2019 at 6:51 AM Christian Norrman notifications@github.com wrote:

I gotta be honest. If there is so much outcry for a data table component. Then read the material guidelines and do an implementation yourselves.

It's not too hard. Especially because you only need CSS, otherwise just use Materialize or another open source version. There is at least one for every big framework.

Plus this repo is not very highly prioritized by Google or its employees because they probably have better stuff to do than making free stuff for other lazy developers.

It's very easy just complaining, a lot easier to find another solution.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/material-components/material-components-web/issues/57#issuecomment-468927191, or mute the thread https://github.com/notifications/unsubscribe-auth/AINGecjGECtNM36HrMYy-O9jd0rALjOoks5vSo_9gaJpZM4LEv2Z .

kfranqueiro commented 5 years ago

As previously stated, this component is in our Q2 plan. Since this thread is continuing to digress into non-constructive comments, I'm locking the conversation to contributors.