My Final Exams

[TheComputerM]

My final exams are coming up, so I am unable to maintain for the next few months, this project will not be deprecated/abandoned and I will continue once my finals are over.

[98mux]

Good luck with your exams!

[Florian-Schoenherr]

I wish you success!

[TheBeachMaster]

Kick them ... 💪

[homimickey]

All the best 👍👍👍

[itsdonnix]

Good Luck!! Wish you all the best buddy!!

[nateshmbhat]

can we close this issue ? @TheComputerM

[TheComputerM]

Nah, I still have more exams to go.

[EwertonBello]

Good Luck!

[adisaljusi]

You said that we should use svelterial instead of materialify. There haven't been any commits since nearly a month for svelterial and it doesn't look mature enough to be used in production. Is this information still up-to-date?

[TheComputerM]

Don't worry I am making changes to my local copy.

[sdolke]

Hi,

this issue states that "this project will not be deprecated/abandoned" while the comment on the home page is "Svelte Materialify is soon to be deprecated in favour of svelterialjs." Will Svelte Materialify being continued or is it dead?

[TheComputerM]

Svelte Materialify is essentialy dead as I am rewriting components using modern svelte features such as svelte:fragment and CSS vars <Component --var="" />

[sdolke]

That's really a shame. I found this library very promising and well done. In particular it is very easy to use.

Is it really (really?) necessary to rewrite the whole project and throw away all the work done so far? Using new features and technology is always a good thing but new technology and stuff comes up all the time. Before you will be done with the new project maybe there is some new stuff out there again and then you restart one more time and never get anything finished.

Would it not be better to evolve the current project step by step, reuse some stuff that was done in the last years and stick to the current community? This would also bring the advantage that there would be no waiting time until the new implementation is ready to use. Beside that, even though keeping up with the latest technology is important, stability and sustainability are very important values as well when creating a successful library.

However, if you really decide to stop to continue, is there any chance that you can handover the project owner ship to one of the other main developers? @Florian-Schoenherr is the one with the second most commits in this project, may be he is willing to continue it and to steer the further development?

[TheComputerM]

Just to clarify I am not rewriting the project, just copy pasting and making some changes. SCSS changes are more like rewrites as I am using BEM conventions fully.

There are going to be some API changes as I have learnt more about how people use svelte libs so yeah. Like for example a textfield. A number input does not work properly in it so I am changing the way to use it.

[sdolke]

If it's not a complete rewrite would it then not even make more sense to do that in the existing project? What is the purpose of starting a new one?

There are some changes in the master branch submitted after the last version. Will there be another release that contains these changes?

[TheComputerM]

The whole project structure is rewritten, components are divided into separate packages and the docs are completely in SvelteKit instead of sapper. Not a complete rewrite as in the source code of components is still almost the same.

[SARFEX]

How are your exams? :)