Moodle plugins directory: MooTyper

David, I thought I might have higher versions ready by now but I'm so new at programming php it is taking me a little longer than I'd hoped. I've been hung up for two days tracking down a permission error that goes back way before I took over, but I just figured it out a few minutes ago. I will need to do some more testing just to make sure, but hopefully will do a 2.7.1 release by Monday, Then I'll jump forward to 2.8 and 2.9. I really want to get to 3.0 before Moodle 3.1 gets released this spring.

I've been doing a lot of work on MooTyper, most of which doesn't really show up as it mostly has to do with needed modifications to the code for such things as logging events. For the past couple of days I've worked on a new keyboard layout, English(US), which you can see as a new screen shot near the top of this page. If you would like to try it out let me know. Also, if you use one of the other keyboard layouts and would like it updated similar to this one, let me know and I'll see about getting it done, too.

Yeah sorry about that.. the code must be terrible.

Actually Jaka, it's not too bad. It has mostly just been adding in things required by Moodle changing how things works, such as events for logging, and fixing deprecated ways things used to be done.

Just made an entry about an upcoming new version over at the discussion forum. https://moodle.org/mod/forum/discuss.php?d=209535#p1351478

Just added a new MooTyper 3.1 version that works with Moodle 2.9, 3.0, and 3.1 as well as PHP 7. If you do an update from a previous version, in the admin block for MooTyper you will see some new capabilities. If you click on Import exercise/category, you will see at least one new lesson added to those available for use when setting up a new MooTyper activity. If you have created your own lessons, there is also a link, Export/edit exercises, that takes you to the edit page where you can select lessons to download so you can save them or swap them with other MooTyper users.

I've also included some new keyboard layouts. If doing a new install they will automatically be available for use when setting up a new MooTyper activity. If you already use MooTyper there are two ways to get access to the new layouts. One is to uninstall MooTyper then reinstall it to get the new layouts to show up. Two, after updating MooTyper, manually add the new layout you want to use in the database table, mdl_mootyper_layouts. Just duplicate the last record, then edit the filepath, name, and jspath so it contains the name of the new layout.

NOTE: Currently, my testing of the new keyboard layouts is very limited and done by switching to different languages on my desktop computer using WIndows 10 and my regular keyboard. If you notice any problems be sure and let me know about it and I'll see what I can do to fix it.

Quang Viet Nguyen, dude, what do you think you are doing?! This is not how plugin versions should be released. Plese read the official development documentation: https://docs.moodle.org/dev/Main_Page

To all MooTYper users...I've been asked if it would be possible to change MooTyper to allow a user to continue typing without being forced to enter the correct character, after making a mistake. Is anyone else interested in this capability?

Changing this is very simple to do. See here: https://github.com/jl2035/al_moodle_mod_mootyper

Some coding is still needed. If you reload the page during some lesson, all characters that have already been entered are back to green, which is not perfect, but mistakes counter works ok.

There are also a few questions. Should we just change that, or allow teacher to choose between two modes when creating the activity? Which one should be default? Or should we just keep this out of the main branch and maintain in other repos? How many users would prefer the new mode over the old?

Hi Jaka, I already have a modified typer.js that allows continuous typing. Was just curious if anyone wanted the capability since, to make it into a setting, requires changing other files and adding a new field to the database. I have most of the work done except for the database mods. I haven't moved any of my development code to github yet is why you didn't see it.

I just did some updating today and checked the debugging section to get this output:

Warning: file_put_contents(mod/mootyper/styles.css): failed to open stream: Permission denied in /home/gnucr/public_html/courses/mod/mootyper/settings.php on line 144
Skip to main content

I'm not using MooTyper at the moment with any courses but wanted to shared and hope to get some advice for resolving .

I suspect it is a permissions problem. Your web server needs to have both read and write access to the styles.css file so it can implement your color selections for MooTyper.

Hi AL,

We found a few issues in the MooTyper css and scss, causing a breakdown in Boost-based themes. I know there is no version for Moodle 3.2 yet, but it might be nice to have fix for these:

webkit-border-radšius: 4px; ==> should be webkit-border-radius: 4px

and in declaring margin, on the final value it doesn't say px, but x.

Looking forward to a fix for these, so MooTyper can properly run in 3.2 with Boost-based themes.

Hi Joost,
Thanks for your interest in MooTyper. I had spotted those same problems, but have delayed putting out a new release as there is one other problem that I have not had a chance to track down yet due to working on other projects. The keyboard render does not look the same in Boost based themes, as it does with the Clean theme, and others. In Boost, all the keys for the on-screen keyboard seem to render much smaller. For anyone interested I have put the fixes Mentioned above, in the master branch at github.

Just released a new version MooTyper 3.1.4 that includes new backup capability, continuous typing, and limits the wpm rate to positive numbers only. Backup works for individual MooTyper activities as well as course backup, both with and without user data. The user data is only the grades table information. Continuous Type is now an optional setting. When off, a user must type the correct key before they can go on. Continuous Type when set to yes, will show the incorrectly typed letter and go on to the next. If a person made too many mistakes in the past, the corrected wpm could show as a negative number, which is misleading. This latest version limits the displayed corrected wpm to zero and higher, only.