Hello,

I haven’t tested Fuse with Universal but there are couple DOM related stuff going on so I’m pretty sure it wouldn’t work out of the box. I’ll add this to my todo list and see what can be done to provide support for Angular Universal.

Cheers

Thanks.

Thank you.

1. I don’t have any immediate plans for strict mode but will do in the future.

2. Refresh token must be implemented on server side, there is nothing can be done on client side to implement it, please read our documentation. http://angular-material.fusetheme.com/docs/guides/authentication/jwt

3. No need to remind this, Fuse has constantly been updated for past 6 years with either new features or compatibility updates. I never stopped releasing updates, why would it be the case now?

4. Navigation (and other data) are already coming from API. It’s a MockAPI and data is stored in files but we don’t read them as files, they are already working like APIs. Please read the documentation: http://angular-material.fusetheme.com/docs/core-features/libraries/mock-api

Hello,

Form validation is done by Angular and since all fields are using Angular Material form fields, you have full validation capabilities. You can check Angular Material’s docs for managing error messages: https://material.angular.io/components/form-field/overview

And for actual validation, you can check Angular’s docs: https://angular.io/guide/form-validation

Cheers

Sounds great, thank you! Since I see some core developers of ngx-translate are involved to this project: do you think both libraries (Angular build in i18n and transloco) will parallel satisfy their user’s needs? Or will Angular offer runtime i18n and Transloco will die, too? Not that it matters, I’m just interested

Even if Angular provides runtime language switching, there is still a lot of overhead in order to start using translations. It’s not as straightforward as adding couple json files, loading them and then start translating the content via directives or pipes.

The main reason Angular team brought the main dev of ngx-translate was to simplify the translations and runtime language switching but as 99% of corporate backed libraries, Angular is also suffering from corpo-mind processes.

You can’t just delete everything, start over, implement the things they should have been from the start, create a pull request and bam!, you implemented the thing. No, unfortunately, that’s not the case.

First you have to propose your thing, it must be reviewed by 100 different people before even it’s accepted and if you are lucky, you get to work on that thing but with constant need of updating your supervisors, answering stupid questions, changing your comment on line #871 because it’s not explaining the thing enough and all that shenanigans. That’s why you can still see open bug reports from 2014 and some of them is pretty crucial too.

Anyways, the whole point is, I don’t think Angular will have a proper built-in i18n solution, ever. And even if they do it, believe me, it’s not going to be easy like Transloco or any other 3rd party libraries. Google likes over engineering

3rd party libraries on the other hand, even if one fades away, another one will pop up using a similar way allowing you to use a similar data structure and easy migration, like the ngx-translate -> Transloco example.

Thanks for asking by the way, it’s good to have this kind of conversations time to time.

Thank you SO much for your very detailed and well-founded answer! Totally with you and already excited to see all those new features in your template! I’m planning to migrate my applications in about two months, hope most of my required features are done by that!

Anyways, I appreciate your great work here, thank you!

Hello,

I added this to my todo list as I mentioned before and will visit it in near future.

Cheers

Hello,

this advanced search did you mean my suggestion or no becuase i want make Overlay

No, that’s a different thing.

As I said before, your suggestion is on my list already, there is already a strict roadmap that we have prepared so you have to be patient about it.

Cheers

Hello,

Yes, Scrumboard will be included in the new version. It will probably take couple weeks to finish so it should be here in a month or so.

Cheers

Hello,

Fuse currently only available for Angular and React.

Cheers

Hello,

1. This is a very good question as I completely forgot about that behavior, so thank you!

I’ll implement that and include it either in the next update or the one that will come after. And if you want to keep the sticky header in some cases, it would be very easy and can be done by just removing couple Tailwind classes.

2. This is already in my list and will be implemented very soon.

Cheers!

Just like always, thank you very much for your super fast response! And estimations when these two features will make it to the new Fuse?

No promises, just estimations …

They probably will be ready in a week or two.

Hello,

You can use our Github repo. If you haven’t requested an invitation, you can do it here: http://www.withinpixels.com/themes/fuse-github

You can also just download the theme from your Downloads tab again.

Cheers

Hello,

The reason is “to evolve”.

Previous design was maintained for 3 years and it started to fail in a lot of cases (technology wise). In that 3 years, browsers changed, devices changed, technology changed, trends changed … this can go forever. So, we had to catch up.

People tends to forget about that this is a business. As all businesses, you have to evolve and change if you want to stay in the market.

Of course there are a lot of benefits of the new version, it’s not just a design update, I re-wrote the whole thing from scratch using newer solutions, libraries, coding styles, and etc.

Do you know why I didn’t add anything to the previous version for a long time? Because it got to a point that anything I try to add or change or modify would break tons of other stuff. Start up and recompile times were already pretty bad and anything I add pretty much made the theme unusable. So, things had to change and they did.

While doing the update, it would be unwise to keep the previous design as it was “old”. I mean, even you used the word “old” when you are talking about the previous version, not “previous”

Cheers

Thank you very much for your detailed answer that I totally agree with and like – makes me know I’ve chosen the right template

Since I’m not really a WebDesigner I can’t tell what flaws the old one had and what are the key features of the new one. Have you made a list of those changes? And is there maybe a list of “functional breaking changes”? Things you need to know / take care of yourself since the new one does not contain these features yet or isn’t going to?

What are the reasons to prefer Tailwind over MaterialDesign? Is it (going to be) outdated? Or just a personal decision? And what was the decision for modifying MatFormFields that heavily? Guess that makes it hard for many people to move to the new one.

So many questions … Anyway: thank you pretty much! Love the new one just like I loved the old one! Keep up the great work

We don’t have any migration guides as it’s not possible to do a full migration, you basically have to start over if you want to move your app over to the new version.

Tailwind and Material Design are two different things. Fuse still follows a lot of rules from Material Design but it does it loosely. And Material Design is not the Material Design from 2014 anymore, you can pretty much do all kinds of different designs and still call it Material.

Tailwind on the other hand doesn’t provide any defaults so it’s up to you to create a design and apply it.

Everything I did on Fuse was a choice. MatFormFields look terrible by default so I changed it. It’s just a cosmetic change, I don’t agree you as it doesn’t require any technical or programmatic or api changes, you just use MatFormField as before and we style it using good old CSS.

Cheers

Hello,

We use Angular Material components, you can check their official docs to see all available components that you can use with Fuse: https://material.angular.io/components/categories

Cheers

Hello,

I’m not sure what could be the issue here. Check if you have spaces in your project path (in folder names) and if you do, move your project. Spaces can cause issues on project paths.

Other than that, it’s a very generic error message that doesn’t give a lot of information and we definitely don’t have this issue on our side.

Cheers

Hello,

No immediate plans for adding animations to the router but I will add this to our todo list to look at it in the future.

Cheers

Hello,

Fuse uses Angular Material components, you can check their official guides and documentation to see what’s available: https://material.angular.io/

Cheers

Hello,

Please use our support ticket system at https://withinpixels.ticksy.com for your support requests and we will get back to you as soon as possible.

Cheers

Yes of course you can do that. Please check the navigation documentation over here: http://angular-material.fusetheme.com/docs/core-features/components/navigation

If you have any detailed questions, you can ask them over our support ticket system at https://withinpixels.ticksy.com

Cheers

Hello,

No problem, just published the old version over here: https://upbeat-roentgen-d33a40.netlify.app

Thank you for your kind words, I’m glad you like the new version.

Cheers

Thank you so much!

Hello,

For your first question, please use our support ticket system at https://withinpixels.ticksy.com and I’ll get back to you as soon as possible.

As for the other theme you saw, it’s using the same core with Fuse, and belongs to me so no worries. That one will follow a different path with updated design so if you like the current design of Fuse, stick with Fuse.

Cheers!

Hello,

Yes, missing apps will be added in the next couple of weeks.

Cheers

Hello,

Make sure you have the latest LTS version of Node installed and then try running it again, it will fix your issue.

Cheers