Code Monkey home page Code Monkey logo

main's People

Contributors

alexlmeow avatar chao1995 avatar damithc avatar edmundmok avatar eugenepeh avatar fzdy1914 avatar gachia avatar j-lum avatar kychua avatar lejolly avatar limmlingg avatar lixiaoooowei avatar m133225 avatar mightycupcakes avatar ndt93 avatar okkhoy avatar pierceandy avatar pyokagan avatar q-gabe avatar reignofcomputer avatar rinder5 avatar sijie123 avatar sqwq avatar verylazyboy avatar vivekscl avatar wingedevil avatar yamgent avatar yamidark avatar yl-coder avatar zhiyuan-amos avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

main's Issues

Follow-Up-System: Implementation

Allow users to create a follow-up entry with a specific patient so they are notified after some time when some time has passed or when the patient's medicine has run out.

[Deleted]

Enable reminders to work on a schedule, set-up expiration, and allow calling the MOTD on demand.

Add Reminder Panel for Reminder system

  1. Add the Reminder Panel to display the Reminder system as specified in UI design
  2. Assist Jason with integration of Reminder system to the Reminder Panel
  3. Finish any leftover goals from v1.2

Feedback on week 9 project progress for CS2103T-F12-2

Team progress for v1.2

  • Issue tracker setup:
    • type.* labels setup (:heavy_check_mark: well done!)
    • priority.* labels setup (:heavy_check_mark: well done!)
    • severity.* labels setup (:heavy_check_mark: well done!)
  • Milestones setup:
    • Milestone v1.2 setup(:heavy_check_mark: well done!)
    • Milestone v1.3 setup(:heavy_check_mark: well done!)
    • Milestone v1.4 setup(:heavy_check_mark: well done!)
  • Some issues marked as type.Story e.g., #39 #11 (:heavy_check_mark: well done!)
  • Some issues prioritized using priority.* labels e.g., #65 #64 #63 (:heavy_check_mark: well done!)
  • Milestone v1.2 managed systematically
    • A suitable deadline set [2019-10-16] (:heavy_check_mark: well done!)
    • Issues/PRs allocated to it #67 #61 #60 (:heavy_check_mark: well done!)
    • All issues in it are closed (:heavy_check_mark: well done!)
    • Milestone closed (:heavy_check_mark: well done!)
    • Code tagged as v1.2 (:heavy_check_mark: well done!)
  • Build passing (checked at this commit, based on the build history reported by Travis) (:heavy_check_mark: well done!)
  • Some issues assigned to milestone v1.3 e.g., #65 #64 #63 (:heavy_check_mark: well done!)
  • Updated User Guide for v1.2 (:+1: Kudos!)

Individual progress of @Q-gabe for v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #53 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the v1.2 milestone #53 #41 #53 (:heavy_check_mark: well done!)

Individual progress of @SQwQ for v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #54 #50 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the v1.2 milestone #54 #50 #27 (:heavy_check_mark: well done!)

Individual progress of @ReignOfComputer for v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #58 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the v1.2 milestone #61 #60 #59 (:heavy_check_mark: well done!)

Individual progress of @gachia for v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #68 #55 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the v1.2 milestone #44 #13 (:heavy_check_mark: well done!)

Individual progress of @Wingedevil for v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #56 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the v1.2 milestone #56 #56 #16 (:heavy_check_mark: well done!)

Tutor: @AyushChatto

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-18 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

[Deleted]

Allow users to have more granular control over the follow-up appointments set, such as cancelling them.

Feedback on week 10 project progress for CS2103T-F12-2

Team progress for mid-v1.3

Mid-milestone progress reports are FYI only. They are not graded.

  • Milestone v1.3 managed systematically
    • A suitable deadline set [2019-10-30] (:heavy_check_mark: well done!)
    • Issues/PRs allocated to it #87 #86 #85 (:heavy_check_mark: well done!)
  • A new jar file has been released on GitHub. (:exclamation: try to do by next milestone)

Individual progress of @Q-gabe for mid-v1.3

  • Has issues assigned or PRs authored for the v1.3 milestone #76 #76 #49 (:heavy_check_mark: well done!)
  • Merged PRs that update Java/FXML files during the past week e.g., (:exclamation: try to do by next milestone)
  • Merged PRs that update the Developer Guide files during the past week e.g., #84 #76 (:heavy_check_mark: well done!)
  • Merged PRs that update puml/png files files during the past week e.g., (:exclamation: try to do by next milestone)

Individual progress of @SQwQ for mid-v1.3

  • Has issues assigned or PRs authored for the v1.3 milestone #75 #71 #86 (:heavy_check_mark: well done!)
  • Merged PRs that update Java/FXML files during the past week e.g., #71 (:heavy_check_mark: well done!)
  • Merged PRs that update the Developer Guide files during the past week e.g., #77 #75 (:heavy_check_mark: well done!)
  • Merged PRs that update puml/png files files during the past week e.g., #75 (:heavy_check_mark: well done!)

Individual progress of @ReignOfComputer for mid-v1.3

  • Has issues assigned or PRs authored for the v1.3 milestone #83 #82 #81 (:heavy_check_mark: well done!)
  • Merged PRs that update Java/FXML files during the past week e.g., #83 #82 #58 (:heavy_check_mark: well done!)
  • Merged PRs that update the Developer Guide files during the past week e.g., #81 #57 (:heavy_check_mark: well done!)
  • Merged PRs that update puml/png files files during the past week e.g., 0b80d15 c49dd57 #81 (:heavy_check_mark: well done!)

Individual progress of @gachia for mid-v1.3

  • Has issues assigned or PRs authored for the v1.3 milestone #85 #78 #85 (:heavy_check_mark: well done!)
  • Merged PRs that update Java/FXML files during the past week e.g., #78 #68 (:heavy_check_mark: well done!)
  • Merged PRs that update the Developer Guide files during the past week e.g., #78 (:heavy_check_mark: well done!)
  • Merged PRs that update puml/png files files during the past week e.g., #78 (:heavy_check_mark: well done!)

Individual progress of @Wingedevil for mid-v1.3

  • Has issues assigned or PRs authored for the v1.3 milestone #80 #87 #80 (:heavy_check_mark: well done!)
  • Merged PRs that update Java/FXML files during the past week e.g., #80 (:heavy_check_mark: well done!)
  • Merged PRs that update the Developer Guide files during the past week e.g., #80 (:heavy_check_mark: well done!)
  • Merged PRs that update puml/png files files during the past week e.g., #80 (:heavy_check_mark: well done!)

Tutor: @AyushChatto

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-25 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Revise UserGuide.adoc for readability

Revise UG to further fit recommendations from 4.2 Writing User Guides slides from CS2101.

  • Increased use of "'you' language" instead of passive form.
  • Addition of guide screenshots and pictures would be nice to increase the readability and comprehension of the UG.
  • Increased whitespace and use of break lines between logical chunks to not overwhelm reader.
  • Possible inclusion of a glossary.

Feedback on week 6 project progress for CS2103T-F12-2

Progress of this week

  • Team org and repo set up with the correct names

  • Product website available at the expected URL(:heavy_check_mark: well done!)

  • PR created from team repo to our repo(:heavy_check_mark: well done!)

Individual progress of @Q-gabe

  • Team repo forked to your GitHub account https://github.com/q-gabe/main (:exclamation: try to do by next milestone)

  • A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

  • A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @SQwQ

  • Team repo forked to your GitHub account https://github.com/sqwq/main (:heavy_check_mark: well done!)

  • A branch named tutorial-removing-field exists in your fork (:heavy_check_mark: well done!)

  • A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @ReignOfComputer

  • Team repo forked to your GitHub account https://github.com/reignofcomputer/main (:heavy_check_mark: well done!)

  • A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

  • A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @gachia

  • Team repo forked to your GitHub account https://github.com/gachia/main (:heavy_check_mark: well done!)

  • A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

  • A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Individual progress of @Wingedevil

  • Team repo forked to your GitHub account https://github.com/wingedevil/main (:exclamation: try to do by next milestone)

  • A branch named tutorial-removing-field exists in your fork (:exclamation: try to do by next milestone)

  • A branch named tutorial-adding-command exists in your fork (:exclamation: try to do by next milestone)

Tutor: @AyushChatto

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-20 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Feedback on week 7 team project progress for CS2103T-F12-2

Team progress for v1.1

  • Product website available at the expected URL(:heavy_check_mark: well done!)
  • PR created from team repo to our repo(:heavy_check_mark: well done!)
  • README page:
    • Some parts not related to your product are removed(:heavy_check_mark: well done!)
    • se-education.org acknowledged(:heavy_check_mark: well done!)
    • Ui.png has been updated(:heavy_check_mark: well done!)
  • Product website title changed to match your product(:heavy_check_mark: well done!)
  • User Guide: some content has been updated(:heavy_check_mark: well done!)
  • Developer Guide: some content has been updated(:heavy_check_mark: well done!)
  • Team repo git tagged as v1.1(:heavy_check_mark: well done!)

Individual progress of @Q-gabe for v1.1

  • Team repo forked to your GitHub account https://github.com/q-gabe/main (:heavy_check_mark: well done!)
  • Used forking workflow:
    • Created PRs #24 #23 #4 (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:exclamation: try to do by next milestone)
  • Merged updates to documents(:heavy_check_mark: well done!)
  • q-gabe.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @SQwQ for v1.1

  • Team repo forked to your GitHub account https://github.com/sqwq/main (:heavy_check_mark: well done!)
  • Used forking workflow:
    • Created PRs #3 #1 (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:exclamation: try to do by next milestone)
  • Merged updates to documents(:exclamation: try to do by next milestone)
  • sqwq.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @ReignOfComputer for v1.1

  • Team repo forked to your GitHub account https://github.com/reignofcomputer/main (:heavy_check_mark: well done!)
  • Used forking workflow:
    • Created PRs #6 #5 (:heavy_check_mark: well done!)
    • Gave review comments to other PRs #23 (:heavy_check_mark: well done!)
  • Merged updates to documents(:exclamation: try to do by next milestone)
  • reignofcomputer.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @gachia for v1.1

  • Team repo forked to your GitHub account https://github.com/gachia/main (:heavy_check_mark: well done!)
  • Used forking workflow:
    • Created PRs #10 #7 #8 (:heavy_check_mark: well done!)
    • Gave review comments to other PRs #24 (:heavy_check_mark: well done!)
  • Merged updates to documents(:heavy_check_mark: well done!)
  • gachia.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @Wingedevil for v1.1

  • Team repo forked to your GitHub account https://github.com/wingedevil/main (:heavy_check_mark: well done!)
  • Used forking workflow:
    • Created PRs #9 (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:exclamation: try to do by next milestone)
  • Merged updates to documents(:exclamation: try to do by next milestone)
  • wingedevil.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Tutor: @AyushChatto

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-04 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Appointments generates with a non-semantic example

Screenshot 2019-10-31 at 3 04 52 AM

Think it might be better if Appointments would generate with something that actual event data, even if this is a placeholder for it. But for v1.3 I think other teams will be looking at it haha. ๐Ÿ˜“ Really low priority though, just my 2c.

Feedback on week 8 project progress for CS2103T-F12-2

Team progress for mid-v1.2

Mid-milestone progress reports are FYI only. They are not graded.

  • Issue tracker setup:
    • type.* labels setup (:heavy_check_mark: well done!)
    • priority.* labels setup (:heavy_check_mark: well done!)
    • severity.* labels setup (:heavy_check_mark: well done!)
  • Milestones setup:
    • Milestone v1.2 setup(:heavy_check_mark: well done!)
    • Milestone v1.3 setup(:heavy_check_mark: well done!)
    • Milestone v1.4 setup(:heavy_check_mark: well done!)
  • Some issues marked as type.Story e.g., #39 #11 (:heavy_check_mark: well done!)
  • Some issues prioritized using priority.* labels e.g., #44 #40 #39 (:heavy_check_mark: well done!)
  • Milestone v1.2 planned:
    • A suitable deadline set [2019-10-16] (:heavy_check_mark: well done!)
    • Issues allocated to it #44 #43 #42 (:heavy_check_mark: well done!)
  • Build passing (checked at this commit, based on the build history reported by Travis) (:heavy_check_mark: well done!)

Individual progress of @Q-gabe for mid-v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #41 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone #41 #41 #33 (:heavy_check_mark: well done!)

Individual progress of @SQwQ for mid-v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #27 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone #27 #40 #38 (:heavy_check_mark: well done!)

Individual progress of @ReignOfComputer for mid-v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #31 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone #21 #19 (:heavy_check_mark: well done!)

Individual progress of @gachia for mid-v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #43 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone #44 #13 (:heavy_check_mark: well done!)

Individual progress of @Wingedevil for mid-v1.2

  • Merged PRs that updated Java/FXML files during the past week e.g., #42 (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone #15 (:heavy_check_mark: well done!)

Tutor: @AyushChatto

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-11 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.