afsmeira / ff-adventure-sheet Goto Github PK

After setting the stat values in the 'New Character' activity, an AdventureStat should be created and (for now) the application should return to the 'Adventures' activity.

The button for finishing creating the new character should be in the action bar (or top bar). It should be a checkmark and maybe have a copy of 'Done' or 'Finish'.

Right now we are using Picasso's placeholder and error features to set images while the book cover is load or when the book cover fails to load, respectively.

The images being used are just auto-generated application images, so we should use appropriate images instead.

See BookAdapter and AdventureAdapter.

Although the list of supported books is small and not expected to change, it would be helpful to let the user search over them.

Consider what fields should be searched and what queries should be supported.

Consider adding a tags describing the overall content/style of the book (e.g. fantasy, sci-fi, robots, horror, etc) that would filter the list of books, given some UI input.

The UI of the Adventure cards is very rough, and it's mostly a draft. The original purpose was to unblock development of other features.

The objective of this task is to imagine and implement a better UI for Adventure cards.

Use GitHub's capabilities to configure a CI pipeline for this project.

Class hierarchy can be improved. Some classes can be interfaces instead or even sealed classes.

The 'NewCharacterActivity' should simply display a list of the stats available for this Adventure, as text views.
Pressing the back button should go back to the 'NewAdventure' view (this behavior is not temporary).

The typed ids would be simple wrappers around the real ids (Long in most cases).

This entity represents the materialization of a Stat for a given playthrough.

After some time, a user can have many created Adventures and it will be hard to find a particular adventure. In that spirit, Adventure cards should be searcheable.

Consider the fields that can be searched and what type of queries to allow.

Consider filtering based on adventure features (e.g. whether the adventure was completed - with or without success - or not, etc).

Create a basic 'Adventure Sheet' activity that displays the current character stats,as read from the DB.

This activity will be the new entrypoint of the application. It will list the existing adventures to allow the user to continue playing them.
Adding to that this activity will allow for the creation of new adventures.

As a starting point, the main activity of the application should display the available books in a grid.

Create views that allow the user to set/update the value of a Stat

Add both UI and unit tests.

The application needs to be able to read and convert AdventureStat to proper typed objects.

The tests should include test cases with all stat types.

Define the domain data model for the application.

When creating a new character and setting the initial stat values, it would be nice to have a dice roll fature available since many stats are computed using dice.

Possible UI representation:

• A button in the action bar that adds the dice roll to the focused stat (it does nothing if the focused stat does not support int values).
• A button in each in stat that addes the dice roll to its value.

Some kotlin docs are using @param while others are not, for no apparent reason. Improve and standardize documentation.

The UI of the Book grid is very rough, and it's mostly a draft. The original purpose was to unblock development of other features.

The objective of this task is to imagine and implement a better UI for Book grip. It would be very nice if it could somehow be harmonized with the Adventure cards UI (issue #8)

The application should come with a pre-built database and should be able to load and access that database.

Right now, the data model for Stat is already created, as well as the database values for it. However it's not being read from the DB and it should.