Quasar Admin CRM Template
-
@dobbel Thank you. I will consider your feedback.
-
@jitendra16 What is the issue with the scrollbar? I believe that is the default browser scrollbar. If you reduce the records per page (In pagination), it should go away. By the way, which OS/Browser you are using.
-
@mayank091193 MacOs sierra -> chrome. Yes i know what you are saying but it does not look good. If a page content is lengthy then I want this scrollbar inside the q-page-container so that it comes below the header not aside.
-
@jitendra16 I have done this and pushed. Please get the latest code from Github.
-
@mayank091193 Noted thank bro
-
@mayank091193 Thank you, now it looking good.
-
@mayank091193  Is there any methods to make it optimized
-
@sanjee Hey, it looks like the image upload was failed. I am unable to view the screenshot.
-
@mayank091193
Is there any methods to make it optimized -
@sanjee Well, the Quasar Framework is IE optimized but some of the third party libraries that I have used may not be IE optimized. The only way to make it work is to test it on the IE and see what errors it is giving. Then the fixes can be applied.
-
-
Here is a solution to make apexcharts work correctly in IE. may be useful for you.
-
@mayank091193
Finally, IE is worked after removed third party library. -
@sanjee Okay, nice!
-
As much as this might go against some people’s grain, I wish Quasar would remove IE10 support completely and I wish the consuming devs would also just look away and tell their bosses, we can’t use this great tech, because we are still using crap IE11. As long as us developers bend over backwards to make IE11 work, then the need to move away from it (which should be just plain common sense anyway) will never happen. It is holding us back from offering some real cool additions and anything that holds up progress needs to retire, especially since it should have been years ago anyway.
My 2 cents.
Scott
-
@s-molinari Very well said, Scott!! I completely agree with you.
-
Unfortunately a lot of people are forced by their company to use only IE11, and because of that , me as developer will have to support it.
This will continue (at least) until October 14, 2025.( end of IE11 support)
The demand for IE compatibility will not disappear anytime soon i am afraid…
-
@dobbel said in Quasar Admin CRM Template:
Unfortunately a lot of people are forced by their company to use only IE11, and because of that , me as developer will have to support it.
In the context of IE11 support I would be totally OK it this was available commercially in Quasar. The IE11 support is needed ONLY in business context, with already established user base, where the technical constraints decide about what is profitable and what is not.
In the context of open source no developer builds apps with target for IE11 in 2020.Why this would be best?
- Because it could from one side (open source) give more momentum to push Quasar into new territories - for example - web workers, drag’n’drop, bootstrap/firebase integration which would bring more people into the project.
- Because core developers could make some money for they work in terms of quasar.COM not only quasar.DEV
and this influx of money and security for core developers again would bring more safety the Quasar project as a whole.
Essentially - if you use Quasar to get money just toss a coin to your witch… sorry - your core Quasar developer haha
-
Hi @mayank091193! You have added particlesjs from CDN in index.template file, Do you know how to use the package from node_modules.
<script src="~/node_modules/particlesjs/src/particles.js"></script> I have added this but its not working. Do you know any other webpackconfig -
In the context of IE11 support I would be totally OK it this was available commercially in Quasar.
I wonder how many other devs (and companies) would agree.
Scott
