materialize
materialize copied to clipboard
Dogfalo
Where does Materialize stand today ? Why should one choose Materialize over other libraries ?
@Dogfalo It's almost a year since we release 1.0. Since Nov. 2018 till today there has been only a few ( less than 10 may be ) usable ( except patreon updates ) commits.
Can you please clear the air around the development of this project ? Also, it would be very helpful if we can bring-up the advantages of using Materialize over other frameworks, since this project has been stalled for a long time. MDC which released v 1.0 in Mar. 2019, has been actively moved towards v 4.0.alpha ( as of today stable is v 3.1.1 ).
I too also want to know this as I use this too much and I want to know if I need to look at switching to a framework thats still being worked on as this one is stalled
@DanielRuf It's been quite a while since the last update from @Dogfalo on #6243 . It's always great to hear that Materialize is progressing. But as a user the comparison between MDC and Materialize does pop-up. MDC is multi-platform and is being actively updated with features, bug fixes and security patches. I feel moving forward, we must clarify where does Materialize stand today ? What are it's fundamental strengths against other libraries ? ( there wasn't a match to Materialize back then, but that's not the case anymore ) ? And what's the plan for the coming releases ?
Hope you're getting the point.
@Praveen-Rai please see https://github.com/Dogfalo/materialize/issues/6438
@DanielRuf Thanks for linking the issue. So, things are moving ( on other branches ), it's just we aren't releasing. That's good to hear. Though we still need a roadmap and active release cycle. And as i said earlier we need to put up a document "Why use Materialize" or "Core Strengths of Materialize". Meanwhile i'll change the title of this issue.
Short answer: yes
The maintainers are just taking a break.
Thanks for pointing that out :) Awesome to hear stuff is still moving on with this Lib. I would hate to have to rewrite my site with another project. Can't wait for future updates. I also agree with @Praveen-Rai , a roadmap or similar would be of use
@Praveen-Rai
So, things are moving ( on other branches ), it's just we aren't releasing
I would be not so sure... I took a quick look at the other branches and most of them have not been updated since 2017. Some of the branches have one or two commits more than the master, but there is nothing worth mentioning.
See https://github.com/Dogfalo/materialize/compare/1.0.0...v1-dev (40 commits).
Also both maintainers take a break at the moment. There is no other person with merge permissions afaik (I was an active contributor for a long time).
@DanielRuf it's an indefinite break or you know when they will return?
Currently dropdowns and selects do not work on mobile, it's a very important issue.
I can not answer this.
Do you know what has to be fixed / changed? If so you can patch it and provide a PR. Did you already search all issues and PRs for relevant commits / patches?
@DanielRuf it's an indefinite break or you know when they will return?
Currently dropdowns and selects do not work on mobile, it's a very important issue.
Out of interest what version of Materialize are you using and where is are dropdowns failing for you? As I just tested it and I have dropdowns (and the internal selects) working fine on mobile with my setup using them (currently) within mobile side nav
@Lagicrus 1.0 last version, go to this link https://materializecss.com/select.html and try with your phone. Using the mobile testing tool of the browser console it work, but not from a real mobile device.
Just tested it on my device (Android, 8.1.0) and it works fine for both triggering the drop-down and choosing the options within
https://github.com/Dogfalo/materialize/issues/6412
https://github.com/Dogfalo/materialize/issues/6369
the second link has a video (not mine) showing whats happening on my device
Hey Andrew changes are happening look at the v1-dev and rollup branches
On Mon, Oct 7, 2019 at 1:08 PM Andrew Hoffmann [email protected] wrote:
It's been over a year, how long of a break is it going to be?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Dogfalo/materialize/issues/6441?email_source=notifications&email_token=AAVFVR7726NYU5E3ZCWZBJTQNOJMPA5CNFSM4IUJPSZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEARUJMI#issuecomment-539182257, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVFVR2JWQSPJMJRLL2ZC33QNOJMPANCNFSM4IUJPSZQ .
-- Doggy sends his greetings from Mars.
Hey Andrew changes are happening look at the v1-dev and rollup branches On Mon, Oct 7, 2019 at 1:08 PM Andrew Hoffmann @.***> wrote: It's been over a year, how long of a break is it going to be? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6441?email_source=notifications&email_token=AAVFVR7726NYU5E3ZCWZBJTQNOJMPA5CNFSM4IUJPSZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEARUJMI#issuecomment-539182257>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVFVR2JWQSPJMJRLL2ZC33QNOJMPANCNFSM4IUJPSZQ . -- Doggy sends his greetings from Mars.
Any idea when the changelog.MD will be updated so we can figure out whats been changed on those two branches? Thanks for the updates however :)
When a new release is done. Or check the commits.
New releases make sense rather than every commit thanks I was just looking for a consolidated overview rather than digging through the commits themselves
I am in the process of making the components being usable as separate imports. This requires a lot of changes however so it is not quite ready
@Dogfalo @DanielRuf Thanks for the updates. We must update all our near future plans in the Roadmap doc page. As far as the changes and releases are concerned, it will be much appreciated to focus on releasing the bug-fixes asap.
There are multiple feature requests ( e.g. #6282 ) in the backlog, sorting them out, will give us the clarity and opportunity to initiate discussions on the usage. And finally a document highlighting the core strengths of Materialize will help the consumers to make an apt choice.
"Are we there yet?" @Dogfalo @DanielRuf In 2020 should someone use this for new projects or just stay away?
No new release is OK, those issues(500+) might be fixed with next release in 202*. But why not review some of these existing pull request(182)? and/or at least bump minor version to some 1.0.* with those 48commits already in the branch. so that people don't waste time facing known issues when using the 2018 dist/cdn/npm. You have good, nice and clean framework, please don't clutter it with all this confusion.
Hi @AhnafCodes,
I'm just a normal contributor and I can not push to this repository.
Thanks for responding @DanielRuf, Are you aware if any of the fork -ed repository has these 48 commits in master and may be some other much needed pull request. Because, a lot has changed since 2018, just new version of browsers would introduce few issues and might need minor fixes and minor version updates.
@Dogfalo @DanielRuf @acburst
What is the official status of this project? You have all the right to take the well deserved after the release of v1. You created some awesome piece of code.
Is there any given roadmap for 2020? Or is this project being neglected and the creators are moving on to the next thing (which is totally fine)?
Just some honest words would be very welcome how and whether this project is going on.
Thanks in advance. Cheers.
@MacGyer please read the previous comments, I'm not a maintainer / collaborator, just a past long-term contributor.
I can not answer your questions.
@Dogfalo surely you owe us no explanation. We are here because we like and admire this Framework from you. At the same time folks like me and @MacGyer can't use this for our projects, if this remains stagnant. Like, We use bootstap 3.5 on an old project(from 2015-2016). we plan to upgrade that codebase, and we have been looking at this thread since November end. Now, we have decide to go with a less comprehensive css framework(Ta*****), only because we see its roadmap and it being actively maintained, in spite of the reservations we have about it.
No minor version update and 182 PR pending would keep away any new adopters and soon old timers too would flee.
March 2020 still no updates, no fixed bugs no nothing. Oh, but there is some push to sponsors in the footer. I guess I'll leave this framework which it was good at the beginning. Hope it recovers from it was a great framework that it was promising.
Any tips for an easy migration to a different framework? suggestions?
I just switched over to react and then used material-ui
Any tips for an easy migration to a different framework? suggestions?
I just switched over to react and then used material-ui
Thanks! I'm using Vue for a small project, so I'd rather find something which is suitable for that.
Any tips for an easy migration to a different framework? suggestions?
I just switched over to react and then used material-ui
Thanks! I'm using Vue for a small project, so I'd rather find something which is suitable for that.
A quick Google finds this which might be what you are looking for
Any tips for an easy migration to a different framework? suggestions?
I just switched over to react and then used material-ui
Thanks! I'm using Vue for a small project, so I'd rather find something which is suitable for that.
A quick Google finds this which might be what you are looking for
I ended up going for Vuetify - it's very nice :)
Why not https://github.com/material-components/material-components-web ? This is the best material you can get
"BIG NO" to Tronic, I wouldn't personal use Jquery in 2021 & beyond. So, wouldn't use a library which uses it as its base. Why? because the browser does all those Jquery things itself now. And browser when does something it does, it runs faster & better or will run better soon. Jquery surely has the compatibility and browser support(may be ie11) baggage, which might not be an issue for many of us today.
MaterialUI(react) has some big names behind it, but I don't find the CSS tag generation and insertion the right thing to do.
Now, my personal preference and reasons for it. Tailwind CSS, after using it for more than a year and seeing how it can be used to get minimal CSS footprint using PurgeCSS settings, I am happy with it.
If material design is not a concern, we have https://tailwindui.com/. It is paid, but not pricey and from creators for tailwind CSS. For Vue users there are free options like https://www.vue-tailwind.com/.
What about material design & React? you have https://material-tailwind.com/ for React for now and they plan to come out soon with Vue & Angular. CreativeTim, the agency behind it has some history and know-how of web development, so we can expect some quality.
"BIG NO" to Tronic, I wouldn't personal use Jquery in 2021 & beyond. So, wouldn't use a library which uses it as its base. Why? because the browser does all those Jquery things itself now. And browser when does something it does, it runs faster & better or will run better soon. Jquery surely has the compatibility and browser support(may be ie11) baggage, which might not be an issue for many of us today.
MaterialUI(react) has some big names behind it, but I don't find the CSS tag generation and insertion the right thing to do.
Now, my personal preference and reasons for it. Tailwind CSS, after using it for more than a year and seeing how it can be used to get minimal CSS footprint using PurgeCSS settings, I am happy with it.
If material design is not a concern, we have https://tailwindui.com/. It is paid, but not pricey and from creators for tailwind CSS. For Vue users there are free options like https://www.vue-tailwind.com/.
What about material design & React? you have https://material-tailwind.com/ for React for now and they plan to come out soon with Vue & Angular. CreativeTim, the agency behind it has some history and know-how of web development, so we can expect some quality.
Personally, for React I use https://material-ui.com/ / https://github.com/mui-org/material-ui