Input is very welcome, both regarding the UX as well as how to evaluate it properly. Currently I'm working on the "backend" parts with most GUI/UX coming later in the project so me and the mentors have not really discussed those parts that much yet. I'd very much appreciate to hear your thoughts on the UX, and I'm sure the same goes for my mentors (Sebastian Koslowski and Marc Lichtman). I'm available in the chat as Oscar Ekholm (oscekh) if you'd like to discuss it further on there.
I'm very interested in your View only mode project. I wish you luck with it.
Is your proposed solution ("secure default behaviour with user settings to disable, or potentially modify the View-Only mode") fixed, or is there scope for input? If it is already fixed how do you plan to evaluate it's usability?
If it is of help, I'd be happy to chat about the UX design, and how it's usability might be tested.
On 11 June 2021 17:24:43 CEST, Oscar Ekholm <email@example.com> wrote:
>I have now published the first blog post for my GSoC work on the GRC
>View-Only Mode. This week I have mainly worked at saving evaluated
>of parameters in the grc-file. You can read about it here:
>I will be posting an update on the blog each Friday, with a
>announcement on this list.
>On Mon, May 24, 2021 at 11:19 AM Oscar Ekholm <firstname.lastname@example.org> wrote:
>> I've been accepted to work with GnuRadio for this year's Google
>> Code. I will be working on implementing a GRC View-Only Mode, which
>> security feature disabling execution of block parameters in untrusted
>> I will be posting weekly progress updates on my blog:
>> If you are interested in reading more about the View-Only mode it is
>> described further in my project proposal:
>> Please reach out if you have any questions, advice or thoughts you
>> Best regards,
>> Oscar Ekholm