ToLuist is a Java desktop address book application created during the course of CS2103T Software Engineering in AY2016/2017 Semester 2.
Programmer, mainly responsible for features such as:
February 19, 2017 - April 13, 2017
Koh Lewis
Louis Lai
Melvin Tan
Powerpoint
Eclipse (Java)
Created for CS2103, our team started with an initial prototype of an address book application. Our job was to build up from it to create a todo list application. We were given the persona of a power user who uses Comand-Line Interface input as their preference. As such, we designed our application with that in mind, ensuring that the features enhance the todo list in the minds of this user.
As the user uses the application, there will be a lot of information which the application will carry. It is important that the user is able to access all this information and to navigate through different items easily. We have two main ways to filter data for the user.
Firstly, we have a find command which allows users to search through the information. The user can type in a word and the application will show the user items with that keyword. We also implemented a tagging system, allowing users to tag items with specific keywords for easier categorization. This also allows users to refine their search, whether they are looking for items of a specific name or items of a specific tag.
Secondly, we have a sorting command and feature which automatically sorts the items into convenient lists for the user. We provide five ways of sorting the list, and they are all applied together. The user is able to change which sort parameter has higher priority, allowing them to decide which is more important to them individually. In addition to list sorting, we also split the items into multiple lists. We categorize the lists into four different categories, making it easy for the user to focus on different items as and when they need to. If they want to see all the items, they can choose to go to the 'all' list instead and forgo this feature.
Our application has many different commands for users to use. As such, it may be hard for users to remember what command performs what actions. As such, we have included an extensive help function for users to refer to. By typing 'help', users can see all the available commands which they can enter.
Furthermore, by typing 'help [command]', they are able to see detailed information about the command they are looking for information on. This includes different ways of using the command, as well as examples which the user can follow so that they can see how to use the command.
Without using the help command, our application still provides guidance to users. When typing in the beginning of a command, the application will try to predict what the user wants to type, and show options which show some of the available actions the user can take. When a command is typed, the application will show other parameters which the user may want to use as well, asissting the user in completing the command.
As the user uses the application, they will end up inputting many commands. This can get tiresome for the user, especially when they know what they want to achieve but have to enter a long sequence to enact it. We have two main methods for dealing with this situation.
Firstly, the prediction strategy explained in the previous section also acts as a quick-complete. When an option appears in the suggestions panel, the user can use 'tab' to automatically type in that phrase.
Secondly, we keep a 'history' of user inputs. The user can easily cycle through past messages using the 'up' and 'down' arrow keys, giving them quick "templates" which they have created before and can make adjustments to, to perform new actions. In addition to this, the prediction feature also includes the words used in the history, allowing the user to quickly reuse key words over and over again.