Re: [bug-gtypist] GTypist for Beginners

[Felix Natter]

Tim Marston <address@hidden> writes:

> Hi,

hello Tim,

> How about this for an extension of option I)...
>
> * We write a tutorial, as per I).
>   - We wouldn't need to introduce any special script commands or extra
>     command-line switches.
>   - A simple/small tutorial will be enough IMO - gtypist isn't very
>     complicated! And there's always the '--help' option available, as
>     with all GNU software.

Yes, for some things we can and should refer the user to the manual.

> * This tutorial shows up immediately when gtypist starts. Since it
>   would be generic "help" information about the whole program, it
>   needn't be part of a script. It could be built in to the main program
>   as a gettext string. (The down-side to this is that it would be good
>   to get some translations to other languages before release.)
>
> * We implement a config file and switch to GNU gengetopt, both of which
>   are on the TODO list anyway. (I'll put my name down for this.)

Yes, that looks very useful and cool!

Then I will take care of writing the component for the "beginner
tutorial" which allows to scroll vertically.

> * We can introduce a config-only option (i.e., there is no command-line
>   switch) that disables/skips the beginner tutorial. When the tutorial

Not sure if this is possible with gengetopt. Another solution would
be to have only a *long* option.

>   is showing, you can either select a "Close" button, or you can select
>   a "Close, and don't show again!" button. Choosing the latter button

Ok, so we have a Scrollbar (only usable via keyboard of course) and
"Start typing" (space/enter) and "Don't show this message again (ESC)"
(Escape) buttons.

>   updates the config file to disable the tutorial in future.
>
> In addition to this, perhaps we could review the default setting for the
> "-e/--errors-max" option. I'm happy to change it, but it would be nice
> to have some idea what other typist projects are using, or what are
> "acceptable" error-rates in the touch typing world. Does anyone have any
> input on this?

I think another thing that would be nice is to add more colors to
the UI (maybe optional). For instance, we could use green+red in
drills/speedtests. What do you think?

Finally, you could output smileys if a new personal best score is
achieved and so on.

Best Regards,
-- 
Felix Natter