Materialize Moving Forward

[ryanrapini]

Hey all,

I'm coming here from the discussion here.

I am happy to start providing pull requests. There are several minor issues that I would love to be fixed in the short term, as I have been using materialize in a very mature Laravel/Vue project in production for the last 4+ years. If there's a confirmation that this is in fact the place to put pull requests and that they will be accepted here instead of stagnating, I'd like to help.

Let me know if there is some sort of organization/trello/work board that i can see.

[khashashin]

@LoganTann same question. It may look pointless, but in my opinion, to get more contributors, you should say that there are new features or bug fixes in this repo, even if only 2 lines of code was changed, to get people to start use this repo instead.

[DanielRuf]

There is at least a nightly CI job, see https://github.com/materializecss/materialize/actions/runs/689172656

So you can already get nightly builds.

Writing changelogs and coordinating all this is not that easy, especially when you work full time in a company.

Any help is very welcome. If you can help us, feel free to take a look at the open issues, PRs, propose that you want to help with the release(s), and so on and I will invite you to the relevant teams.

[ChildishGiant]

I'm happy to write up all the changes and do all the chores required for a release when the time comes (hopefully soon 😉)

[TomFreudenberg]

Dear Allie, Daniel @ChildishGiant @DanielRuf

I was using materializecss for a number of projects but always stay at the 0.x releases - patched by myself while Dogfallo didn't merged anything. I was always very happy with materializecss while it worked and worked and worked.

Starting with a new project I would like to use react-materialize and align that with this repository. But before proceeding I would like to ask if you could give me your current expectation about stability of this repo (v1-dev) in comparison to the old materialize-css@1.0.0-rc.2 branch.

Do you think it is ok to start already a production ready project on this branch?

In general I am willing to support and patch and bring in feedback but for the moment it should work mostly already.

Thanks for your information in advance Tom

[DanielRuf]

Do you think it is ok to start already a production ready project on this branch?

v1.0.0 of materializecss was already published in the past. See https://www.npmjs.com/package/materialize-css

v1-dev (also used by the original materialize repo) is the latest version - on our fork we use the same plus our changes (fixes), which are released as v1.1.0-alpha.

A fork is a copy of an already existing project which is continued by the community. We do not start from scratch and do not plan to do so.

[TomFreudenberg]

Hi Daniel @DanielRuf

thanks for your comment. I know that a fork is the copy of an existing repo but in case of materializecss I haven't touched any of the v1.x releases in any project.

So for that my question is: Is it "safe" to go on with v1.0 or also already with v1.1.-alpha.

Just to get your personal opinion.

Thanks for a clarification and feedback. Tom

[DanielRuf]

So for that my question is: Is it "safe" to go on with v1.0 or also already with v1.1.-alpha.

This should be safe imo.

Afaik many have worked with the v1.0 version and v1.1-alpha includes many bugfixes for problems in v1.0. At work we have used materialize v1.0 in a big project and so far the requirements could be met.

[TomFreudenberg]

Thanks Daniel - so I will proceed!

[MacGyer]

Hey guys,

is this project still moving forward? Will there be any stable release in the near future?

Thanks for getting back and stay safe.

[DanielRuf]

Hi @MacGyer,

we can need any help that we can get. Opensource software lives from the contributions of volunteers. Currently I do not and can not invest any time in opensource projects anymore. The members of the @materializecss/members-write-access can push and make new releases and everyone of @materializecss/members can make reviews.

[MacGyer]

@DanielRuf Thanks for clarifying.

I am a PHP guy, so unfortunately wouldn't be of much help. Was just a question out of curiosity, because I am maintaining a Yii2 implementation of Materialize :)

[Smankusors]

@DanielRuf Thanks for clarifying.

I am a PHP guy, so unfortunately wouldn't be of much help. Was just a question out of curiosity, because I am maintaining a Yii2 implementation of Materialize :)

wow that's cool 😳

anyway if you have any issues with materializecss, feel free to create an issue here 😉

ehm... but unfortunately I'm no longer employed in a place where materializecss is used. So I also don't have time to fix it. But if anyone else creates a PR, I will happily review it and merge it.

We're also planning to release the 1.1.0-beta version soon

[TomFreudenberg]

Very sad to see this component going down in usage but as far as more and more are using frameworks like react and MUI or Tailwind or whatever - it will be necessary once to move existing software forward to better and more active supported libraries.

That is the pitty in use of OpenSource - no one is paid so it happens from time to time that things are going down.

Good luck to all here and see you somewhere else in future.

Cheers Tom

[doughballs]

I was a big, big fan of Materialize when I started out as a developer and really enjoyed helping the community, but as time went by I found the need for a framework of any kind receding. I was writing a ton of overrides and leaning on the framework so little that I decided to just go DIY, which suits my control freak tendencies. I have a lot of builds that I maintain that use it but going forwards I’m framework agnostic…

[jshster]

I was a big, big fan of Materialize when I started out as a developer and really enjoyed helping the community, but as time went by I found the need for a framework of any kind receding. I was writing a ton of overrides and leaning on the framework so little that I decided to just go DIY, which suits my control freak tendencies. I have a lot of builds that I maintain that use it but going forwards I’m framework agnostic…

Hey guys,

is this project still moving forward? Will there be any stable release in the near future?

Thanks for getting back and stay safe.

I would love to help out as I use Materialize almost exclusively in my projects now. I actually haven't run into many issues but maybe that's the simplicity of my implementations.

I would love to help out but I've never worked on an Open Source project before and I honestly don't know where to start. Usually I'm told go and view the PRs and work from there but to be honest I'm still a bit dumb - where do I go from there?

I anyone has a few minutes to guide me I'd be happy to start ripping in, given that I work with the thing on a daily basis.

Josh

[TomFreudenberg]

I use Materialize almost exclusively in my projects now. I actually haven't run into many issues

Same as me - we had used meteorjs or jekyll (depends on requirements) and materializecss for about 5 years for any project. That worked well and we were happy. Some of the first implementation are still in use by our customers even nearly 7 yo old.

Since 2020 we went over to GatsbyJs and mostly NextJs - So using react, we switched to MUI currently stable v5. That works out of the box and there is great support and contiously development.

So - it's a pitty - but we are out.

MaterializeCSS was a great experience - Thanks for all the work

[mxdpeep]

People using Materialize CSS (I am running a dozen websites using it, so it will be tough tasks to migrate it all for free) often move to BeerCSS https://www.beercss.com/.

Filip Oščádal https://mxd.cz https://mxd.cz

On Mon, Mar 21, 2022 at 1:23 PM Tom Freudenberg @.***> wrote:

I use Materialize almost exclusively in my projects now. I actually haven't run into many issues

Same as me - we had used meteorjs or jekyll (depends on requirements) and materializecss for about 5 years for any project. That worked well and we were happy. Some of the first implementation are still in use by our customers even nearly 7 yo old.

Since 2020 we went over to GatsbyJs and mostly NextJs - So using react, we switched to MUI currently stable v5. That works out of the box and there is great support and contiously development.

So - it's a pitty - but we are out.

MaterializeCSS was a great experience - Thanks for all the work

— Reply to this email directly, view it on GitHub https://github.com/materializecss/materialize/issues/2#issuecomment-1073828368, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXWJ7KVOEGK4EI73ZQLVBBS53ANCNFSM4OWEBJ7A . You are receiving this because you were mentioned.Message ID: @.***>

[mxdpeep]

I have switched to 1.1 alpha and everything works fine so far, will test the nightly build soon too.

Filip Oščádal https://mxd.cz https://mxd.cz

On Tue, May 4, 2021 at 7:29 PM Daniel Ruf @.***> wrote:

So for that my question is: Is it "safe" to go on with v1.0 or also already with v1.1.-alpha.

This should be safe imo.

Afaik many have worked with the v1.0 version and v1.1-alpha includes many bugfixes for problems in v1.0. At work we have used materialize v1.0 in a big project and so far the requirements could be met.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/materializecss/materialize/issues/2#issuecomment-832114635, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXVFXHB7R3OIZO3GUOTTMAVH5ANCNFSM4OWEBJ7A .

[LoganTann]

I have switched to 1.1 alpha and everything works fine so far, will test the nightly build soon too. Filip Oščádal https://mxd.cz https://mxd.cz

Yep, our fork brings almost only bug fixes, so it should even be more stable than the official 1.0 There are only few breaking changes for security reasons.

[mxdpeep]

Well done! ❤️

Filip Oščádal https://mxd.cz https://mxd.cz

On Wed, Mar 23, 2022 at 11:04 AM ShinProg (Logan Tann) < @.***> wrote:

I have switched to 1.1 alpha and everything works fine so far, will test the nightly build soon too. Filip Oščádal https://mxd.cz https://mxd.cz https://mxd.cz https://mxd.cz

Yep, our fork brings almost only bug fixes, so it should even be more stable than the official 1.0 There are only few breaking changes for security reasons.

— Reply to this email directly, view it on GitHub https://github.com/materializecss/materialize/issues/2#issuecomment-1076178770, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXVCTGQ5RIRJPBERPPLVBLUELANCNFSM4OWEBJ7A . You are receiving this because you were mentioned.Message ID: @.***>

[blackjyn]

The beauty of Materialize is it's neutrality , I mean it is independent from other frameworks. But nowadays let's admit we are using JS frameworks extensively to build websites. However since Materialize is at the "critical condition", here's the alternative you might consider if you were really wish for "moving forward" from Materialize:

• Svelte : Svelte Material UI
• React : MUI
• Vue : Vuetify

I had assembled Materialize paid course material some 1-2 years ago , but given the project is abandoned so I got no more interest to publish it , hell not even interested to finish it.

[mxdpeep]

Vuetify looks really nice!

Filip Oščádal https://mxd.cz https://mxd.cz

On Wed, Mar 23, 2022 at 6:35 PM Igzo Valka Byzantine < @.***> wrote:

The beauty of Materialize is it's neutrality , I mean it is independent from other frameworks. But nowadays let's admit we are using JS frameworks extensively to build websites. However since Materialize is at the "critical condition", here's the alternative you might consider if you were really wish for "moving forward" from Materialize:

• Svelte : Svelte Material UI https://sveltematerialui.com/
• React : MUI https://mui.com/
• Vue : Vuetify https://github.com/vuetifyjs/vuetify

I had assembled Materialize paid course material some 1-2 years ago , but given the project is abandoned so I got no more interest to publish it , hell not even interested to finish it.

— Reply to this email directly, view it on GitHub https://github.com/materializecss/materialize/issues/2#issuecomment-1076615983, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXWQO6BD5M2NS73M6J3VBNI4JANCNFSM4OWEBJ7A . You are receiving this because you were mentioned.Message ID: @.***>

[wuda-io]

The beauty of Materialize is it's neutrality , I mean it is independent from other frameworks. But nowadays let's admit we are using JS frameworks extensively to build websites. However since Materialize is at the "critical condition", here's the alternative you might consider if you were really wish for "moving forward" from Materialize:

• Svelte : Svelte Material UI
• React : MUI
• Vue : Vuetify

I had assembled Materialize paid course material some 1-2 years ago , but given the project is abandoned so I got no more interest to publish it , hell not even interested to finish it.

Please dont speak for others, if you cant finish your project, then it is not the fault of Materialize. Not everyone wants to depend on some short living Frameworks which change every now and then so thats fine. Some projects want to use some light, nice independent CSS and JS which can simply be exchanged and be flexible without needing to refactor the whole system. I think that should also be the target of the whole project.

[wuda-io]

Maybe we should seek some funding for the project, I would be glad to help out as developer if my work is funded so I can invest time in it. Who would be interested in such a solution too an can provide some fixed amount of time developing it? Then we could set up some funding and project plan.

[mxdpeep]

I am moving to Beer.css for the server-side Mustache templating (PHP 8.1), and v3 of my CMS system will be powered by Vue.js and Vuetify - I need to learn some modern JavaScript shit :)))

Filip Oščádal https://mxd.cz https://mxd.cz

On Sat, Mar 26, 2022 at 9:17 AM Daniel Wurzer @.***> wrote:

Maybe we should seek some funding for the project, I would be glad to help out as developer if my work is funded so I can invest time in it. Who would be interested in such a solution too an can provide some fixed amount of time developing it? Then we could set up some funding and project plan.

— Reply to this email directly, view it on GitHub https://github.com/materializecss/materialize/issues/2#issuecomment-1079638072, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXSHXLFK6ICTM6NEOQDVB3BYDANCNFSM4OWEBJ7A . You are receiving this because you were mentioned.Message ID: @.***>

[wuda-io]

So you have to depend on 3 things rather than using 1 thing properly? Sounds not very efficient but good luck. Fortunately you got matetialize to work. What made you use beercss? And why on the Server?

[mxdpeep]

1) Vue and Vuetify are both in active and rapid development, I don't like React 2) server-side rendering is still a good option for Progressive Web Apps 3) Beer.css is also actively developed 4) I have no funds to invest into Materialize myself

Filip Oščádal 🍀📱

On Sat, Mar 26, 2022, 12:01 Daniel Wurzer @.***> wrote:

So you have to depend on 3 things rather than using 1 thing properly? Sounds not very efficient but good luck. Fortunately you got matetialize to work. What made you use beercss? And why on the Server?

— Reply to this email directly, view it on GitHub https://github.com/materializecss/materialize/issues/2#issuecomment-1079662418, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXQ6LNVVPI3JCACYMX3VB3U7JANCNFSM4OWEBJ7A . You are receiving this because you were mentioned.Message ID: @.***>

[mxdpeep]

BTW Beer.css is 70 kB only

Filip Oščádal 🍀📱

On Sat, Mar 26, 2022, 12:21 Filip Oščádal @.***> wrote:

1) Vue and Vuetify are both in active and rapid development, I don't like React 2) server-side rendering is still a good option for Progressive Web Apps 3) Beer.css is also actively developed 4) I have no funds to invest into Materialize myself

Filip Oščádal 🍀📱

On Sat, Mar 26, 2022, 12:01 Daniel Wurzer @.***> wrote:

So you have to depend on 3 things rather than using 1 thing properly? Sounds not very efficient but good luck. Fortunately you got matetialize to work. What made you use beercss? And why on the Server?

— Reply to this email directly, view it on GitHub https://github.com/materializecss/materialize/issues/2#issuecomment-1079662418, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXQ6LNVVPI3JCACYMX3VB3U7JANCNFSM4OWEBJ7A . You are receiving this because you were mentioned.Message ID: @.***>

[wuda-io]

Yes beer is cool, but i would miss all the components, like multiselect etc. so i can not use it. I think this project is awesome, so i will contribute here and push this forward. I think only the design needs some facelift, and some improvements, but the rest looks good 👍

[DanielRuf]

For any task there is a fitting tool, or multiple. You can all use what is best and fits your requirements, stack, team knowledge and so on.

I am only aware of one big customer on our side where we have an old Materialize v1 version (not the one from the fork). Other projects are mostly built in React and use Tailwindcss and custom components.

Maintaining opensource software is still a hard job and in most cases you get not paid for it. If you want to start some funding @wuda-io then it should be probably done with https://opencollective.com/.

[blackjyn]

Please dont speak for others, if you cant finish your project, then it is not the fault of Materialize.

I never blame anyone. The reason I stop making it, is that why should I selling a course about a framework when the FW itself has no clear progress, no clear maintenance and no clear future? I won't selling "fraud" course about FW that even the original creators are no longer care about.

Materialize has clearly been abandoned and if that's hurt you, its all on you whether you accept it or not.

[mxdpeep]

I feel you, bro. 🍀❤️

Moving forward with a different toolset is my only option. 😂

Yes, making open source is hard...

Filip Oščádal 🍀📱

On Sun, Mar 27, 2022, 06:52 Igzo Valka Byzantine @.***> wrote:

Please dont speak for others, if you cant finish your project, then it is not the fault of Materialize.

I never blame anyone. The reason I stop making it, is that why should I selling a course about a framework when the FW itself has no clear progress, no clear maintenance and no clear future? I won't selling "fraud" course about FW that even the original creators are no longer care about.

Materialize has clearly been abandoned and if that's hurt you, its all on you whether you accept it or not.

— Reply to this email directly, view it on GitHub https://github.com/materializecss/materialize/issues/2#issuecomment-1079839055, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXWY2XAOUVCLECGC223VB7SRPANCNFSM4OWEBJ7A . You are receiving this because you were mentioned.Message ID: @.***>

[TomFreudenberg]

@blackjyn - nothing to add

[wuda-io]

Yeah you can leave and use other tools. But if it has no future then why are you looking up this project, come here and tell people what you think? If you dont have anything to contribute thats fine but you should have some respect for other projects. I dont even know what you want... Would you be using Materialize when there is a fixed release plan or what are your concerns?

[DanielRuf]

@wuda-io please let's stay calm. I see no problems with recommendations for actively maintained solutions =)

I already had this case more than once, especially when I stopped maintaining and contributing to Foundation Sites after the original team wasn't working on it anymore.

Frontend is an area where things move fast and it is helpful when others tell us what solutions they use to know their needs. As maintainer you often do not see or want to see how things are changing. That's ok.

I see no disrespectul behavior. Please change your tone and let's move on together. If this does not help I will have to lock and moderate this issue here.

[wuda-io]

Yes I see your point. But what is the solution? I suggest that we make a release plan. Next version should be 1.2 and from then every 3 or 6 month we should make the next release. What do you think?

[wuda-io]

Also I think Materialize is not compareable to other big Frameworks. Because the whole Point of this Project is, that it does not require or depend on any framework.

For example if you want to make a small static website like a simple ContactPage, then I would not set up a whole React Project for that purpose, so I think we should not necessarily compare it to React, Vue or smth like this. But it is also nice that people are using it for bigger Projects.

We should keep in mind that this is a Design/Frontend Framework and it should stay that way. We should not handle any Data or Logic with Materialize (e.g. in the Autocomplete Input). I would be glad to help getting this Project back on track. Maybe you can give me some access to accept Pull Requests, then we can move faster from here.

[blackjyn]

Yes I see your point. But what is the solution? I suggest that we make a release plan. Next version should be 1.2 and from then every 3 or 6 month we should make the next release. What do you think?

:laughing: , so I think it is you that got the problem with MTFW. Me? I have no problem with it, thanks I did some projects with nice ca$h back in the day when MTFW was actively maintained.

I would be glad to help getting this Project back on track.

You can propose many solutions as you want, like bla bla bla bla... But welcome to the party, if you think you can maintain Open Source projects without any strong financial backups than you are a real hero.

At this modern era, most OSS projects that are actively maintained and developed got strong financial backups from commercial companies. Because behind every OSS projects there are real programmers (read: human) with their real life , with family to fed , with their prestigious time out of screen enjoying real life too.

Maybe you can give me some access to accept Pull Requests, then we can move faster from here.

Not only you can pull, you can even fork this repo and then develop, fix, release anything at your own. That's another solution I propose you: re-start all on your own , be hero and stop insulting others on their decision.

[blackjyn]

I see no disrespectul behavior. Please change your tone and let's move on together. If this does not help I will have to lock and moderate this issue here.

this is a must. :+1:

[wuda-io]

I already forked it and developed it further, thanks i already know that. But why start from 0 if we have already smth which is working and many people are interested in keeping moving.

Also a team is better, than developing alone. But if your only solution is to kill this project, than please go ahead. I think maybe i was a bit harsh, but what you say is also very disrespectful. But who cares? Make some $$ and keep hating. Cheers

[wuda-io]

😆 , so I think it is you that got the problem with MTFW. Me? I have no problem with it, thanks I did some projects with nice ca$h back in the day when MTFW was actively maintained.

So If you got no ca$h anymore, what went wrong? And what has it to do with maintence of MTFW? ... are you even a developer, or are you a "Buy my Course" Guy? So I think we have different PoV. Please clarify.

[blackjyn]

the only thing we need to clarify is : why do you so harsh to me? Are you OK? Do you need psychological treatment?

It is you that is go wrong all the time, messing with someone.

Are you even a developer or are you a "FUCK YOU DON"T MESS WITH MTFW Guy?"

Go to the doctor dude , before its too late.

[wuda-io]

Everything ok? 😂

[blackjyn]

Sorry @wuda-io , I got to block you soon. Coz you got a way too far. But mark my words : even if you tried to maintain MTFW, you are going to fail. Successful OSS projects only possible with healthy contributors not by psychos.

[wuda-io]

Ok thats fine. Thanks for your advice.

[blackjyn]

To @DanielRuf , thanks for your great initiative and effort.

After all of this, I'm on 2 surely my last projects ever that using MTFW from a loyal client since 2018, One is at this March 31st due date and another is at April 30th.

Not a good farewell party but I'm give up on MTFW. I can't contribute and collaborate with toxic people involved. For me it is now a lovely time to move on to Svelte Material UI.

Thank's @DanielRuf , sorry for the unstar and good luck :pray:

[DanielRuf]

Guys please refrain from fighting - otherwise I will lock this here. @blackjyn no further comments are needed, this is currently not helpful.

This and other things are reasons why I stopped contributing my free time to opensource projects and especially maintaining. Until today I thought that we could bring this project forward together. But if everyone is just fighting, then I will completely stop the project and archive it. I have no energy to argument in such a heated discussion.

As both of you probably won't stop I'm closing this one here. I hope you are ok in these hard times, because I'm not.

[DanielRuf]

Going to archive this repo since you won't see any future contributions as I will focus on more important things in life. Any stress is currently very toxic to me, my health and body.

I wish you all a great time with whatever you want to do, create and use.

[DanielRuf]

If any of the current @materializecss/maintainers want to bring this project forward, please contact me on LinkedIn.