Hi Kenn,
thank you for your answers!
We'll update the Capability Matrix UI according to your design related
suggestions. It will be implemented in a way that allows you to rather
easily change its text content, remove/add columns and rows etc. :)
Kind regards,
Agnieszka
On Wed, Jan 6, 2021 at
Very good questions. Answers inline.
On Wed, Jan 6, 2021 at 8:16 AM Agnieszka Sell
wrote:
> Hi Kenneth,
>
> Thank you for your feedback about the Capability Matrix! I have several
> questions about it:
>
> *Feedback: I think we can also remove rows that are not started or not
> complete in the
Hi Kenneth,
Thank you for your feedback about the Capability Matrix! I have several
questions about it:
*Feedback: I think we can also remove rows that are not started or not
complete in the Beam Model, and remove the Beam Model column.*
Question: If we remove the Beam model column the whole
Thanks Kenn, this is super helpful.
On Mon, 21 Dec 2020 at 09:57, Kenneth Knowles wrote:
> For the capability matrix, part of the problem is that the rows don't all
> make that much sense, as we've discussed a couple times.
>
> But assuming we keep the content identical, maybe we could just
For the capability matrix, part of the problem is that the rows don't all
make that much sense, as we've discussed a couple times.
But assuming we keep the content identical, maybe we could just have the
collapsed view and make the table selectable where *just* the selected cell
controls content
Hi folks, another page that's getting a refresh this time around is the
Capability Matrix, which is one of the most critical pages for users as
they evaluate the current support for each of the Beam runners.
The situation we'd like to get your input on is: How do we optimize the
expanded version
