You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, sorry but i won't define all the bugs because... let's being honest, this library is full of bugs/tricks that shouln't be used.
You can see that the chart/grid isn't adapting automatically depending on the size of the text area, and even though I can adapt it easily in a common resolution (like 1920x1080), it quickly stops being adapted when the resolution size grows higher and higher because the developer used many amateur tricks (padding, margin, translate XY) without taking into account the evolution of our world/resolution, which makes it very difficult to create a scalable web design integrating Apexcharts.
I don't think that I need to add more information such as code or something else because it's purely a bug caused by a deprecated manner of coding. At least, the developer should create a X axis text using a flexible div that is adapting itself
depending of the height that least between the bottom of the whole chart div and the bottom of the grid, the Y axis is also not scalable but less problematic.
So I'm probably going to move to Echarts after one year to lose my mind because of this bugged library.
This is a good library because it's lite (edit: i found that i can create a custom build easily with echarts which make it as lite as apexcharts for my needs), but it's for amateurs / not adapted for the scalable design which is the next generation of digital design. Don't fool me by talking about how the OSs have a default zoom, i don't use the default zoom, many people don't, the future is without it, and therefore the actualy "responsive" manner of coding is not a good manner and not adapted to the whole reality nor the future.
Thanks for considering adapting your chart.
(look on the pics, i used 2 different resolution but i can't adapt the charts using one mathematical formulation just because
of how this chart is using many amateur front-end tricks not based on percentage of the size of the parent element or not always. And on these pics i already worked a bit to make it scalable, otherwise it was worst that what you can see.... )
If the dev could give more information about all the defaults padding/margin and their values, which are added during the creation of the charts, so i could remove them all and create my own formulation, then it would be pretty nice. Thanks.
The text was updated successfully, but these errors were encountered:
Merfyn007
changed the title
Not scalable chart because of useless padding/magin/translateXY + tricks
Not scalable chart because of useless and default padding/magin/tricks
Apr 4, 2024
Merfyn007
changed the title
Not scalable chart because of useless and default padding/magin/tricks
Not scalable charts because of useless and default padding/magin/tricks
Apr 4, 2024
Merfyn007
changed the title
Not scalable charts because of useless and default padding/magin/tricks
Not scalable charts because of default padding/magin/tricks
Apr 4, 2024
Hello, sorry but i won't define all the bugs because... let's being honest, this library is full of bugs/tricks that shouln't be used.
You can see that the chart/grid isn't adapting automatically depending on the size of the text area, and even though I can adapt it easily in a common resolution (like 1920x1080), it quickly stops being adapted when the resolution size grows higher and higher because the developer used many amateur tricks (padding, margin, translate XY) without taking into account the evolution of our world/resolution, which makes it very difficult to create a scalable web design integrating Apexcharts.
I don't think that I need to add more information such as code or something else because it's purely a bug caused by a deprecated manner of coding. At least, the developer should create a X axis text using a flexible div that is adapting itself
depending of the height that least between the bottom of the whole chart div and the bottom of the grid, the Y axis is also not scalable but less problematic.
So I'm probably going to move to Echarts after one year to lose my mind because of this bugged library.
This is a good library because it's lite (edit: i found that i can create a custom build easily with echarts which make it as lite as apexcharts for my needs), but it's for amateurs / not adapted for the scalable design which is the next generation of digital design. Don't fool me by talking about how the OSs have a default zoom, i don't use the default zoom, many people don't, the future is without it, and therefore the actualy "responsive" manner of coding is not a good manner and not adapted to the whole reality nor the future.
Thanks for considering adapting your chart.
(look on the pics, i used 2 different resolution but i can't adapt the charts using one mathematical formulation just because
of how this chart is using many amateur front-end tricks not based on percentage of the size of the parent element or not always. And on these pics i already worked a bit to make it scalable, otherwise it was worst that what you can see.... )
If the dev could give more information about all the defaults padding/margin and their values, which are added during the creation of the charts, so i could remove them all and create my own formulation, then it would be pretty nice. Thanks.
The text was updated successfully, but these errors were encountered: