…
The key issue is that on a really efficient stroke, you have a significant flat area on top of the curve. And if you want text to be readable on a 7" screen while people are moving up andd down the slide, it is pretty hard to read if the font becomes smaller. It gets in the way of that curve and distracts.
There are more key indicators here that are relevant. RP3 and EXR show the drive length on the X-axis. Physically correct, but for our current GUI not ideal. So it is an additional tile. I think when you want to really do a nice job, you'd make the force curve even bigger, put the peak force on the y-axis and the drive distance on the x-axis, and show what the peak is in percentage on the x-axis as well. But I think that should be part of a fundamental rethink how the GUI is designed, as you want a more integrated (but more flexible) approach.
As @DXCanas rightfully indicated, it is about the shape itself, so it should focus on that. Making that as easily readible as possible is key. Adding large readible text in the same tile would go against that. So removing large texts that block that hopefully smooth curve is a good step in my book. I guess perhaps a slightly smaller font on the axis might also be appropriate.
Why not remove the peak force from the graph and give it its own tile.
I mean we can have a peak tile but that will take a space of a tile. I think this is a decision of the user whether it accepts a slightly smaller peak font (that does not overlap) or sacrifice as full tile for something that is readable.
We just saved them a tile as well by this PR. In essence, if people are keen to see it, they can do now for "free".
Key thing here is being able to read it when returning to the catch. The old solution was interesting but never good to read (in all honesty, as my PM5 still is connected as well, I read that data via the PM5-ErgData interface). On ErgData it has its own tile. I think having it on a place where people can see it without obstruction from other elements (a curve intersecting) would make it a cleaner interface. I actually would introduce two tiles: Peak Force and Average Force, as their combination essentially determines the stroke efficiency (the closer they are together, the better). If people really are focussed on stroke efficiency I would put the force curve the Peak and Average force tiles next to each other. Especially on a larger tablet with 12 rows, that would work well.
If you look at more elaborate setups (i.e. using EXR) pace, distance, time, strokerate, force curve, drive distance etc.. is all in the HUD, essentially offloading them from the monitor. This would free up the monitor's tiles to show the more detailed metrics. So I would focus more on that scenario.
Originally posted by @JaapvanEkris in #170 (comment)
…
The key issue is that on a really efficient stroke, you have a significant flat area on top of the curve. And if you want text to be readable on a 7" screen while people are moving up andd down the slide, it is pretty hard to read if the font becomes smaller. It gets in the way of that curve and distracts.
There are more key indicators here that are relevant. RP3 and EXR show the drive length on the X-axis. Physically correct, but for our current GUI not ideal. So it is an additional tile. I think when you want to really do a nice job, you'd make the force curve even bigger, put the peak force on the y-axis and the drive distance on the x-axis, and show what the peak is in percentage on the x-axis as well. But I think that should be part of a fundamental rethink how the GUI is designed, as you want a more integrated (but more flexible) approach.
As @DXCanas rightfully indicated, it is about the shape itself, so it should focus on that. Making that as easily readible as possible is key. Adding large readible text in the same tile would go against that. So removing large texts that block that hopefully smooth curve is a good step in my book. I guess perhaps a slightly smaller font on the axis might also be appropriate.
We just saved them a tile as well by this PR. In essence, if people are keen to see it, they can do now for "free".
Key thing here is being able to read it when returning to the catch. The old solution was interesting but never good to read (in all honesty, as my PM5 still is connected as well, I read that data via the PM5-ErgData interface). On ErgData it has its own tile. I think having it on a place where people can see it without obstruction from other elements (a curve intersecting) would make it a cleaner interface. I actually would introduce two tiles: Peak Force and Average Force, as their combination essentially determines the stroke efficiency (the closer they are together, the better). If people really are focussed on stroke efficiency I would put the force curve the Peak and Average force tiles next to each other. Especially on a larger tablet with 12 rows, that would work well.
If you look at more elaborate setups (i.e. using EXR) pace, distance, time, strokerate, force curve, drive distance etc.. is all in the HUD, essentially offloading them from the monitor. This would free up the monitor's tiles to show the more detailed metrics. So I would focus more on that scenario.
Originally posted by @JaapvanEkris in #170 (comment)