jobara / touchtype Goto Github PK

Create a new branch with files/structure necessary for packaging a blackberry webworks app.

Allow an integrator to change the method of notification. Currently it is hard coded to an alert

There should be an event fired after cancel has been called. This will allow users to perform different actions when cancel is called.

Upgrade to Infusion 1.4 when it is released. Start working from a pre-release version till then if needed.

Make it possible to show a live udpated WPM score.

Possibly with a subcomponent that uses the setInteveral or a recursive setTimeout
https://developer.mozilla.org/en/DOM/window.setInterval

You should be able to cancel the test. This should be able to be triggered by an element (i.e. onscreen button) and focus being lost from the textfield.

This should do the following:

1. clear the timer
2. clear the textfield
3. rebind the event to start the test
4. make sure the textfield is enabled

The default notification says AdjustedWPM instead of Adjusted WPM

Currently the message only says the wpm number, without any explanation or anything.

After upgrading to use IoC a bunch of functions were made public. There should be unit tests written for all of these now public functions.

Rewrite the component using IoC.

This should help reduce code, improve flexibility, and etc.

The test should be configurable to a user defined length. There should be options to specify the length of the test. This also means that the test should be able to handle calculating the typing speed in WPM when the test is not a minute in length (could be more or less than a minute).

Move existing html to a demo directory and update it to make it a proper demo.

Create the initial implementation of touchType. This is a blanket issue that should be replaced by specific ones once the initial implementation is in place.

A user should be able to provide a path to any text, the component itself should take it in and sanitize it as needed. This should probably be a public function.

Currently the test will automatically cancel on blur. The problem with this is that if someone wanted to setup a "Done" button using the that.finish, the test would cancel before the button could trigger done. This will be particularly useful if the test is sufficiently long that all typing is done before the time expires.

Make the timer a subcomponent so that it can be swapped in and out for other timing functions if needed.

Notify the user when the test is finished, return the score and reset the test.

Need to set the sample text to some default value to handle the case where finish is called before it is set. Currently it causes an error when it tries to call the calculateWPMStats which in turn calls the toArray function. If sampleText hadn't been set yet, the toArray function throws an error when trying to call the split function

Currently the afterStart and afterFinished events call that.start and that.finish respectively. However, based on the names one would expect these functions to call the events. Look at how to make these thing more semantically correct.

Should have an afterTextRendered event so that we know when the text has been displayed. Currently we only know when the text has been fetched. Since registering multiple listeners to the same event will not guarantee an order of which are triggered, the text may not be rendered before other listeners fire.

Currently only the wpm is passed, but number of errors and unadjusted score would also be good.

Disable the text field when the test is finished. Otherwise the user can keep typing forever for no reason.

Move the textfield to the top of the page, remove the wpm as this will be alerted, and focus the textfield on page load.

Break out the url's to the text into the defaults structure, this will allow me to fix the issue where the unit tests can't be run because of the differing relative paths.

Add the initial structure of the project, to initialize the repo

Add specific styles to make the blackberry version look nice.

Need to draw up some wireframes/mock-ups of a new design for the blackberry app.

Suggested new features have included:

• Options
• Different Texts
• Live score