skyeskie/ayso-schedules

Multiplatform PhoneGap app for viewing schedules for Wichita-area AYSO Regions

ayso-schedules's Issues

Favorite teams

Let users save teams, and quickly provide a view of just those teams.

Bug Report

Have method to report app bugs and incorrect phone numbers.

Add in testing for mobile

Setup the auto build script to test used mobile device, either through emulator or attached device

Initial build automation

Initial compile, test, and build.

• HTML packaging
• JavaScript file inclusion to HTML
• TypeScript compile
• Automated testing

Basic unit testing

Unit test Angular 2 components to verify functionality.
Preferably > 90% coverage

Implement FieldView

Ideally keep SVG embed.

Coverage notice

Put notice(s) for which teams schedules aren't covered.
No info for

• 105 U6
• 208 U10, U8, U6
• 253 U6
• 491 U8, U6

Twitter for Cancellations

Add screen to pull cancellations from a specific (hardcoded) Twitter account.

Game view thumbnails

Show thumbnail / minimaps of the region and field.

Get screenshots

Take screenshots of the app working, for app store submission.

Automated dependency update

Make sure easy update of dependencies (in npm) and test on rebuild

Form binding

Implement data binding via Angular 2 for all forms

Color favorite teams

Highlight the team name in list view when it's a favorite team.

Involves

1. Create new pipe
   • Access saved teams list
   • Colorize if input matches one of those
2. Add pipe to app
   • Two teams list
   • One team list
   • Select team

Add in mobile app framework

• Cordova
• Select UI framework
  • Ionic (replace Bootstrap)
  • Bootstrap 4 (rework styling)

Split Screen

Add split-screen capability.
Promising plugin:
https://github.com/asyraf9/jquerymobile-splitview

Settings format

Format the settings page to make it cleaner.

Change favorite switch to toggleable star icon

Currently select favorite team is Flip Toggle Switch. Change to a toggleable star (probably manually code) more or less equivalent to button with star icon and no text.

This is a split from #4 since the buttons built-in to jQuery Mobile weren't being toggle-friendly.

Make MapView fill the viewport

Currently set to hardcoded height

Release android

• Create APK
• Re-run test plan on physical device(s)
• Sign APK
• Publish APK

Map centering

Embedded map doesn't re-center on selection new region.

Streamline watch functions

Currently a full webpack recompile is used on any changes for local testing (or Karma testing).
Minimize this work so that it's a quicker reload.

End to end testing

Add tests for full navigation of the app

Extend game detail page

Show coach info on game detail page

Handle offline status

Need fallback for following views:

• Initial configuration
  • This should block app initialization
• Cancellations / Twitter
• Google maps
  • Optionally, include static offline image

Map integration

Have device launch native maps for directions to facilities.
iOS -- use phonegap/phonegap-plugins/iOS/MapKit
Android -- use WebIntent to launch native

Auto-set week to current week

In WeekView and advanced filter, automatically determine the current week.
Current week is determined by (highest priority first)

• Week number for current date
• Week number for next upcoming date in data
• Max week number (ie, after end of season)

Bye weeks receive page

A bye week from the team listing links to a game detail page. These should not link forward, but be read-only list items.

Field Maps

Add field maps for each region. Include link from home (or close) and tie-in from game view.

Use radio buttons on forms

Angular 2.0.0-beta.3 doesn't handle radio buttons well, so currently using select dropdowns
Once lands in Angular2, switch back to button radio.

Game format

Format the game info screen to make it cleaner,
Also make sure links are in to Field Map and Directions Map

Switch jQuery Mobile to 1.3.0

With new release (and bugfixes), update jQuery-mobile library.

Refine multi-region handling

• Enable/disable multi-region handling at user level
  Primary use case would be for single-region use. Could simplify data access
• Switch between regions easily, keeping default
  Currently only have in searches
• Have better x-region navigation - /region/:number/ prefix

Android testing

Final testing and release for version 2.0

Test plan

Run all views

• Init config
  • Normal run
  • Offline run
• Home
• Settings
  • Change region
  • Force update
  • App reset
• Schedules
  • Schedules menu
  • Current week
    • Navigate first to last and back
  • Find team
    • Team view
  • Advanced search
    • Results week only
    • Results week + age
    • Results week + gender
    • Results week + region
    • Results all filters
• Game detail
  • Bye game
  • Two teams
  • Coach TBD (211B)
• Favorites
  • No favorites
  • 1 favorite
  • 5 favorites
• Cancellations
  • Offline
  • Twitter
• Regions
  • Region list menu
  • Map offline
  • Region 49
    • Map
    • Field view
  • Region 105
    • Map
    • Field view
  • Region 208
    • Map
    • Field view
  • Region 253
    • Map
    • Field view
  • Region 491
    • Map
    • Field view

Field map scaling

Add UI controls to zoom in/out as well as enable touch-drag to pan.

(We SVGs for a reason. And not just the 'I don't want to generate a hundred PNGs for each device density reason')

Can select span in filters

< Span > tag can be selected seperately from parent < li > tag, which will apply the active state only to the < Span > tag, and not the full button from < li >.

Need to fix it so only the full < li > object will receive the ui-active class.

Unit test components

• 1-team game list
• 2-team game list
• title bar
• week bar

Bind settings view actions to backend

Currently it just looks pretty but doesn't do anything.

Need to save settings (default region) and connect to DAO for refreshing.
Largely blocked by #27

Rework routing to be more modular

Break apart route definitions so that they're contained within the files instead of all at root level.
Additionally, have an 'up' functionality in addition to the 'home' in title bar

Loading progress for all async

Show some sort of progress bar, since several asynchronous operations. Under current implementation, should be near-synchronous, though, so minor UI issue.

Will be more relevant for a server round-trip implementation.

Implement initial configuration for first load

Need to have a way to set defaults on initial load, then proceed to home
Should also navigate here after a reset.

Additionally, should intercept routes and send here if no settings, then continue onto route after settings implemented.

Calendar export

Export team schedule to device calendar.

Implement DAOs completely

Currently just have dummy stubs for all the Data Access Objects.
Need to make them actually read in data from somewhere and store configuration.

Wire up phone call function

Phone call currently not implemented. Implement as Pipe and use where shown (for consistency).

Form styling

Pick UI platform and convert all forms to be within that style.

Unit test init of all view components

Make sure all templates compile by unit testing views.
Need to see if can find manner for this to work easily, as currently cumbersome with lots of injection

Setup continuous integration

Use some online CI tool to auto-run tests (one of those that integrate with Github)

Data Update

Enable app to poll server for updates and receive only new/changed records.

Refine dependency injection

Fully setup the Angular 2 dependency injection

Change Home button to Up/Back

Navigate up hierarchy rather than directly to home

Text sizing

Make sure text sizing is good on different devices. Default jQuery Mobile is too small.