Thank you for your continued assistance.
I was just now watching your video on Bootstrap Collapse.
By “applicable slideshow of charts grouped by unit of measurement,” I mean 1) the user chooses a gender/age-group from a drop-down menu or via a check-box. Then, 2) they can view the nutritional profile - final results - as a series of charts with each nutrient amount compared to those benchmarks relevant to that nutrient and user’s demographic.
But that sounds convoluted. Let me simplify the problem with one small example…
Fiber is reported in grams. Folate is reported in micrograms. One gram is 1,000,000 micrograms. It does not look professional or meaningful to convert both nutrients to milligrams and cram it all on one graph.
Beyond that, different users have different needs. A grown male needs twice the magnesium than a young female. So my initial thought was I need to…
- Let the user select a gender and age group, and then
- View the results as a series of graphs “grouped by units of measurement.”
By that, I mean one graph for those nutrients reported in micrograms, Another for milligrams. Another for grams. Another for international units…and so on by placing those graphs in a slideshow or carousel.
Or better option if one exists.
Does that make any sense? I hope so.
Different users need to see the results in different contexts and, based on how the data is reported, I cannot place it all on one bar chart. It needs 4-5 bar charts for each demographic.
Or maybe there is a way to keep it on one graph (chained callbacks?) that changes as the user plays with the demographics?
Well, that would be the best solution probably.
Then, there is the three-step process to producing those results.
- Paste the recipe in the text area.
- Edit the initial analysis.
- Generate the final results (nutritional profile).
This process - the code - works great, but it is all crammed on to one page right now. The user has to scroll too much and think too hard to enjoy the experience, which is very important to me. It needs to be fun.
For that reason, I am currently looking at Accordions/Collapses in DASH Plotly, and wondering how would related callbacks and functions work in a format where they are separated by tabs? Do I place the app layout, function and callback inside the AccordionItem tag? As you must know, I could chew you ear off.
There is some documentation out there, but not a lot. I understand the basic mechanics. The challenge is applying that logic to my project’s unique needs without tons of examples to review. I could just generate the final report and be done with it, but I put seven-eight months of work into this project.
If this is overwhelming or difficult to decipher, I apologize. I did not know a single line of Python eight months ago, so it is an overwhelming amount of information to learn and apply. That makes it difficult for me to articulate.
Please feel free just to point me in the right direction with a link to the best video or template.
I’ve just worked so hard on this project. It must be a polished and special project before I publish it.