Skip to content
This repository has been archived by the owner on Dec 12, 2020. It is now read-only.

"Add task" screen should using texting keyboard #41

Closed
rhussmann opened this issue Oct 24, 2011 · 3 comments · Fixed by #44
Closed

"Add task" screen should using texting keyboard #41

rhussmann opened this issue Oct 24, 2011 · 3 comments · Fixed by #44

Comments

@rhussmann
Copy link
Contributor

Summary

The "add task" screen should use the standard texting keyboard to facilitate faster text entry.

Discussion

I understand that the current keyboard provides somewhat faster access to characters designating context and project (@ and +, respectively). However, the majority of my time is spent entering task text, not the attribute characters. I find myself consistently frustrated when adding TODOs, fighting the muscle memory I've developed with the standard keyboard. As this is a workflow I frequently perform (adding new tasks), it should fit the standard keyboard model.

In addition, the button in the upper right-hand corner should read "Add," not "Done," as done has special meaning within the context of todo.txt Touch.

I'll happily claim this one if we agree this bug is valid.

Supporting images

@mcguiresm
Copy link
Contributor

Just on a quick test if you add textView.keyboardType = UIKeyboardTypeDefault; after textView.inputAccessoryView = accessoryView; in TaskEditViewController.m that will change the keyboard to the desired one.

@rhussmann
Copy link
Contributor Author

Fair enough, just wanted to make sure this was okay, as a group, before making a move on it.

@mcguiresm
Copy link
Contributor

There was feedback on there being no ":" that would be used for due dates or times with the current keyboard layout.

rhussmann added a commit to rhussmann/todo.txt-touch-ios that referenced this issue Oct 25, 2011
Upper right-hand button says "Add".
Closes todotxt#41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants