-
Notifications
You must be signed in to change notification settings - Fork 3
Meeting Notes
- [February 4th 2014](#wiki-February 4th 2014)
- [February 11th 2014](#wiki-February 11th 2014)
- [February 25th 2014](#wiki-February 25th 2014)
- [March 4th 2014](#wiki-March 4th 2014)
- [Match 11th 2014](#wiki-March 11th 2014)
- [Match 18th 2014](#wiki-March 18th 2014)
- [Match 25th 2014](#wiki-March 25th 2014)
Attendance: ALL
-
Standup meetings.
-
Requirements should be divided up between everyone.
-
Storyboard should be 8ish pictures long with a distinct flow.
-
Do not use Eclipse to generate UML.
-
UML should be medium detail. Public methodes other classes are using. Atributes that the getters and setters use and then do not list the getter and setter methodes.
-
Should have model/view/controller parts.
-
Citations for terms, URL and date.
-
Definitions that are relevant to the project, that mean something in the context of the project.
-
No SQL.
-
Expected to write tests for every use case, does not need to compile.
-
Only test code will exist no project code yet.
-
Test cases should be linked to the use cases. Issue tracker and links from wiki into the code.
- jmaps for our Mapping system (Google Maps overlay)
- Work on release planning
- Finish all test cases
- Finish Glossary
- Finish Story-boarding
- ElasticSearch API focus (PRIORITY)
- On new connection - get new comments(refresh). Every INTERVAL - get new comments(refresh).
- (Left out sorting, editing, saving, and favorites)
- 5, 6, 7, 8, 9, 10, 16, 17, 18, 20, 21
- Views: Root comment view, Comment/Reply view, Account Settings view, New Comment/reply view
- Controllers: Comment Controller, Web Controller, Location Controller, Cache Controller(FUTURE PROJECT)
- DONE Merge UML diagrams.
- DONE Change Controller -> View on UML.
- DONE Make sure UML method names are the same as Test Case names/functions.
- DONE Fix up Mockups - Say what is a button, etc.
- DONE Make sure we can see all the Mockup image files and information on Wiki/UI_Mockups.
- DONE Ensure that the Wiki is linked better; Test Case should link to the page for it.
- DONE Ensure each Test Case has a NUMERICAL value attached to it.
- DONE Add definitions from the nouns in User Stories.
- Josh will demo the code for himself. Master @ 4pm will be imported into Eclipse. Thus make sure it works!! Remove, git clone, import, and run!
- Tests must ALL compile, only the test cases for the use cases for the user stories. HALF.
- Refactor our code to suit new UML.
- Design patterns in UML! Design patterns in 301 lecture.
- Marked on addressed feedback.
- Add names to our release plan.
- Nothing is self-explanatory in a UI Mockup.
- Sort controller should go in the model.
- The adapter is like a model.
- Change QueueController as it is NOT a Controller. It is a part of the model.
- Not every view needs a controller, each controller needs a model (can be shared).
- Read only view does not need a controller.
- Add all the functions into the UML.
- DONE BrowseCommentReplies - MATT
- DONE ReplyToComment - MATT
- DONE AddPictureToComment - BRYCE -> Changed due to intents but it still returns Bitmap
- DONE Sorting! - TYLER
- DONE Add to UML - ALL
- DONE Work on XML - JAMES
- Get some PROGRESS BARS!
- Hit Refresh -> GetAll
- Have a separate History cache
- No internet connection? Say so, wait for Refresh() with hasInternet()
- Get Edit comments from local cache done!
- IDs of replies problem. Parallel Arrays?
- List of comments is transient?
- Given ID, get all replies from elasticsearch.
TYLER - SORT
MATT - CACHE THAT STORES SEARCH HISTORY, NEW COMMENTS.
STEVE - ELASTICSEARCH
JAMES - BROWSE VIEWS
BRYCE - FIX ELASTICSEARCH ONE THREAD TO SEARCH BEFORE DIES( LOGGED WARNING). HELP OTHERS, FIX UP GUI. ADD SMALL BITMAP TO LARGER BITMAP IMAGEVIEW.
- DONE - Parallel Arrays only good with FORTRAN.
- DONE - Local branch, master Branch, both new & renctly pulled then merge and push.
- DONE - Have two scrolls views on the screen at once. LinearLayout and give them weights! Fixes the sizing and scrolling problem within viewing a comment.
- DONE - Make sure to add all the functions to UML, change direction of arrows, add all the classes!!!
- DONE - Ensure anything that CHANGES the model, make a controller.
- DONE - View -> Controller -> Model
- DONE - James and Matt doing cache.
- DONE - Updating UML is as stuff is added good.
- DONE - CommentListController does not "have a" ElasticSearchSearchResponse type token it uses a ElasticSearchSearchResponse it uses.
- Tyler will work on moc location
- Matt will implement update comment in cache
- Bryce will implement map for selecting a new location
- James will implement favorites and bookmarks
- Considering doing tags as our new addition.
- FIX UML, things in the UML that arnt in the code and vise-vera... :(
- Make sure UML connections are RIGHT!
- Code has MVC problems, fix them.
- Lost points for tests, 22 use cases, 10 tests!
- Dont comment out old test cases, let them fail.
- Dont have loadsave code in the views.
- References must HAVE dates, even just use the date we used it.
- Dont read in data as a giant stream, just give the inputstreamreader to gson.
- Attributes should be private in this course.
- Pushing comments to ES should be a part of the model not the controller.
- Update comment should be in the controller not the model.
- Pass a reference by putting reference in singleton. Reference that I wanted to get. ESid through to intent and get the comment from the model instead of serialized comment.
- CreateCommentActivity is non-viewy, Edit is viewy. The view should send info from widgets to controller. The controller should send to model and then model to elastic search.
- Cannot get past start screen on horizontal devices, fix it. We can make it verticle only!
- REMOVE THE BACK BUTTON AT THE TOP.
- SETTINGS MENU ITEM DOES NOTHING.
- Use case 4 functionality was missing, apparently we need DATE AND SCORING SYSTEM?
- Fix the URLs from the use cases to the correct location in tests.
- Have a username that is consistant.
- Say who uses GETPARENTID, say why it is useful, when it is used and important, etc for use cases.
- Ask Hindle if we should have used a Date AND Score or OR?? Might get extra mark if its OR.
- Improve Use Case 8 - ReplyToComment to be more in-depth.
- Use Case 14 - Test code to test that users that are not ME can EDIT.
- Test steps as in the flow of the mockup.
- Have the code working properly by the 1st of April.
- LIVE demonstration on the 8th to Hindle. JUST PESENT THE FEATURES OF THE APPLICATIONS.
- Have someone controlling it on the projector while we talk about it.
- Put score in the glossary.
- Scoring system 1/(age*distance)
- Matt write tests NOW, implement favs
- Steve network listener, pushing/pulling profiles, wiki
- James bookmarks, encapsulating all the data into a user profile
- Tyler check for provider
- Code only worth 3 points out of the total score. Look at the rubrik more often, focus on the OTHER THINGS. UML, Wiki, refactoring, Josh's comments, video.
- Step-by-step refactoring issues: We say this method was too long... did this... etc. Using the X factoring method, and it created this and that.
- Add refactoring section to wiki!
- Used car salesman promotional video?
- We can use the emulator.
- Show the usecase features without making it obvious.
- James refactor, cleaning up UML
- Bryce work on test cases, refactoring
- Tyler Help page
- Steve refactoring, UML
- Matt work on videos,
- Make sure to mention support for older API's in presentation
- We look good