echistyakov / gauchogrub2 Goto Github PK

Add SettingsActivity and relevant logic (for both the compat activity and regular activity) utilizing SharedPreferences

Needs to cover the following options:

1. Default Dining Common (dropdown)
2. Default Dining Common Override via Geolocation (toggle, also disables Default Dining Common)
3. Favorites Notification (toggle)
4. Default Filter for Menu

The default dining commons options should be grouped together following android material design practices.

@andrewtran1995 @echistyakov

1. Determine standards for handling state related information for activities and fragments
2. Determine java variable naming standards
3. Determine xml string variable naming standards
4. Determine xml layout id naming standards

Sugar ORM basic docs

1. Create new folder for models
2. Refactor/remove existing caching methods as necessary to handle the changes
3. Handle the following db objects:
4. MenuItem
5. MenuItemType
6. MenuCategory
7. Meal
8. Menu
9. Rating
10. Favorite

Be sure to document fully using javadoc

Implement feature where geolocation overrides default dining common (may be turned on in Settings).

We need to pre-populate the database with static data on the first application launch.
(Dining Commons, Repeated Events, Meal Types)
Repeated events can be taken from here: https://github.com/echistyakov/GauchoGrub/blob/develop/GauchoGrubDataParser/src/RepeatedEvents.csv

Readme.md needs to be updated to contain:

• the determined choices for best practices in #5
• standards for branch naming
• information from/relating to #13, including some proguard setup information and basic information about the keystore setup

@echistyakov please handle the last part of the aforementioned items to reference in README.md

Research UI practices and options

• Android Material Design Guidelines
• Other Android applications for food
• Existing design libraries

Create Photo resources of dining commons for use in application UI

Research Gradle Release practices including minifyEnabled and proguardFiles

Update Notification Service to new API specs, I believe it was written with android 4.4 in mind pre-support libraries.

Probably need to convert to some sort of support library notification system.

Add requery schema to the db package with the following constraints

1. Remove all ratings related tables/fields from the original schema
2. Add a schema for Favorites

Determine the cause of and fix the implementation of the DiningCamsFragment

Move functionality into new Navigation Layout activity.

@echistyakov look into the removal of ByteArrayBuffer and replace it as necessary. It no longer seems to be a relevant class?

like here in WebUtils:

private byte[] readByteStream(InputStream stream) throws IOException {
        BufferedInputStream reader = new BufferedInputStream(stream);
        ByteArrayBuffer response = new ByteArrayBuffer(100000);
        byte[] buffer = new byte[1024];
        int length;
        while ((length = reader.read(buffer)) != -1) {
            response.append(buffer, 0, length);
        }
        reader.close();
        return response.toByteArray();
    }

Create UI Wireframes for implementing layouts and UI-relevant functionality.

Create a new Service, potentially an IntentService that can parse the menus from the html page.

In the develop branch, strip to only models and services that we can re-use, keep everything on the master branch.