What are you building with SQLPage ?
n/a - this feature request was stumbled upon as developing another feature
What is your problem ? A description of the problem, not the solution you are proposing.
with #1370 and a little bit of #1371 we should be able to support rendering 3D charts. off top not sure what I would use it for, but I could see this being useful for folks using SQLPage to show research data or correlation across 3 groups
What are you currently doing ? Since your solution is not implemented in SQLPage currently, what are you doing instead ?
n/a - this feature request was stumbled upon as developing another feature
Describe the solution you'd like
A clear and concise description of what you want to happen.
todo :: add psudocode + SQLPage example of a 3D chart
Describe alternatives you've considered
n/a - this feature request was stumbled upon as developing another feature
Additional context
Points keep their z value instead of being rebuilt as {x, y}, so nothing visible changes but we do less work. This also means SQLPage should now be able to handle 3D charts but I think that's better scoped for another PR to properly test and fix any other straggling issues in the codebase.
#1370 (comment)
What are you building with SQLPage ?
n/a - this feature request was stumbled upon as developing another feature
What is your problem ? A description of the problem, not the solution you are proposing.
with #1370 and a little bit of #1371 we should be able to support rendering 3D charts. off top not sure what I would use it for, but I could see this being useful for folks using SQLPage to show research data or correlation across 3 groups
What are you currently doing ? Since your solution is not implemented in SQLPage currently, what are you doing instead ?
n/a - this feature request was stumbled upon as developing another feature
Describe the solution you'd like
A clear and concise description of what you want to happen.
todo :: add psudocode + SQLPage example of a 3D chart
Describe alternatives you've considered
n/a - this feature request was stumbled upon as developing another feature
Additional context
#1370 (comment)