Coder Social home page Coder Social logo

cs2103-ay1819s2-w13-3 / main Goto Github PK

View Code? Open in Web Editor NEW

This project forked from nus-cs2103-ay1819s2/addressbook-level4

1.0 5.0 5.0 20.85 MB

The Infinity Machine - A safe place to store your research materials.

Home Page: https://cs2103-ay1819s2-w13-3.github.io/main/

License: MIT License

Shell 0.35% Java 98.70% CSS 0.93% HTML 0.02%
java nus application storage

main's Introduction

The Infinity Machine

Build Status Build status Coverage Status Codacy Badge

Ui

What is it about?

Have you ever faced the problem of not having a place to store all the information you search online or the notes you take? Well, we have! Therefore, through our application, The Infinity Machine, we have created a platform where the storing and retrieving of textual information such as research materials can be done efficiently. It also allows you to apply custom made tags and descriptions for easy categorization, search and retrieval. Other useful functionalities implemented are: - Bibliography generator - Panic/unpanic mode - Restore command - History command and many more!

Target Users

Tech-savvy university students or researchers who love to use the Command line Interface and wish to organize and tag research information or any other data that they may wish to store for a long time, frequently performing basic operations such as adding, editing, deleting and searching an entry.

Acknowledgements

Licence : MIT

main's People

Contributors

case141 avatar zhiyuan-amos avatar suriruhani avatar yamgent avatar fterh avatar pyokagan avatar damithc avatar toondragon avatar doittomorrow avatar m133225 avatar mightycupcakes avatar yamidark avatar rinder5 avatar limmlingg avatar eugenepeh avatar chao1995 avatar vivekscl avatar yl-coder avatar lejolly avatar pierceandy avatar ndt93 avatar okkhoy avatar edmundmok avatar kychua avatar alexlmeow avatar lixiaoooowei avatar verylazyboy avatar nicholaschuayunzhi avatar cheec avatar apoorva17 avatar

Stargazers

 avatar

Watchers

James Cloos avatar  avatar  avatar  avatar  avatar

main's Issues

Keeping track of research material

As a researcher, I want to be able to find relevant material I have come across before easily so I do not have to spend time looking for them again

Feedback on week 7 project progress

Subject: feedback on week 7 project progress

See v1.1 progress guide for more details of the activities mentioned below.

Team progress

  • Team org and repo set up correctly (:heavy_check_mark: well done!)
  • PR created from team repo to AB-3 or AB-4 (:heavy_check_mark: well done!)
  • Auto-publishing set up for the team repo (:heavy_check_mark: well done!)
  • README page:
    • Ui.png has been updated (:heavy_check_mark: well done!)
    • Parts not related to your product are removed (:heavy_check_mark: well done!)
    • se-edu/addressbook-level4 acknowledged (:exclamation: try to do by next milestone)
  • 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 @darrendragonlee

  • Used forking workflow:
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • darrendragonlee.png uploaded and linked from AboutUs page in png format (change image to png if presently in different format) (:heavy_check_mark: well done!)

Individual progress of @case141

  • Used forking workflow:
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • case141.png uploaded and linked from AboutUs page in png format (change image to png if presently in different format) (:heavy_check_mark: well done!)

Individual progress of @suriruhani

  • Used forking workflow:
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • suriruhani.png uploaded and linked from AboutUs page in png format (change image to png if presently in different format) (:heavy_check_mark: well done!)

Individual progress of @fterh

  • Used forking workflow:
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:exclamation: try to do by next milestone)
  • fterh.png uploaded and linked from AboutUs page in png format (change image to png if presently in different format) (:heavy_check_mark: well done!)

Individual progress of @DoItTomorrow

  • Used forking workflow:
    • Created PRs link (:heavy_check_mark: well done!)
    • Gave review comments to other PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:exclamation: try to do by next milestone)
  • doittomorrow.png uploaded and linked from AboutUs page in png format (change image to png if presently in different format) (:heavy_check_mark: well done!)

Tutor: @ewaldhew

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-03-06 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.

As a user I want to be able to add aliases for commands

E.g. I want to use "a" as a shortcut for "add"

  • Implement command to add alias (e.g. alias <command> <alias>)
  • Implement command to remove alias (e.g. alias-rm <alias>)
  • Implement command to list all aliases (e.g. alias-ls)
  • Initialize aliasManager with default aliases
  • Handle duplicate aliases gracefully
  • Disallow aliasing alias commands
  • Check for null inputs for all methods (and handle gracefully)
  • Persistent storage
  • Only allow alphabets
  • Unit tests
  • Integration tests with SourceManagerParser
  • Refactor SourceManagerParser metacommand error messages (and add to tests)
  • Update help command
  • Refactor MetaCommandParsers to take in their own keyword, to display in usage error messages
  • Logging
  • AliasManager interface (with ConcreteAliasManager implementation) for DIP
  • Update user guide (persistence, regex validation)
  • Support dependency injection
  • Alias-clear command
  • Update dev guide (seq diagram, update class diagram, regex)
  • Set up tags in adoc documents for cross-references
  • More tests (pairwise unit testing, integration tests, make use of dependency injection)

Edge case: alias alias a

Communications overview

As a user, I would like to be able to have an overview of any recent communications with my contacts at a glance.

Modify AB4 User Interface to suit Infinity Machine

  • change UI color
  • reflect source details when user clicks on source from list
  • assign default icon to source
  • allow users to choose different types of icons when adding a source
  • update UI when users pin something
  • allow users to add headings to certain sections of the source #198

As a user I can list all my research

So I can have an overview of everything I have saved.

  • The user should also have an option to specify how many of the 'most recent' entries he wants to list, eg. list 20 should list the latest 20 entries

Feedback on week 8 project progress

Subject: feedback on week 8 project progress

See mid-v1.2 progress guide for more details of the activities mentioned below.
Mid-milestone progress reports are FYI only. They are not graded.

Team progress

Folow up from v1.1

  • Auto-publishing set up for the team repo and the website is available at link (:heavy_check_mark: well done!)
  • README page:
    • Parts not related to your product are removed (:heavy_check_mark: well done!)
    • se-edu/addressbook-level[3/4] acknowledged (:exclamation: try to do by next milestone)
    • Ui.png has been updated (:heavy_check_mark: well done!)

Recommended progress for the upcoming milestone

  • Issue labels* set up e.g., type.* and priority.* (:heavy_check_mark: well done!)
  • All future milestones v1.2, v1.3, v1.4, created (:heavy_check_mark: well done!)
  • Issues marked as type.Story e.g., link (:heavy_check_mark: well done!)
  • Some issues prioritized using priority.* labels e.g., link (:heavy_check_mark: well done!)
  • Milestone v1.2 planned
    • A suitable deadline** set (:exclamation: try to do by next milestone)
    • Issues allocated to v1.2 e.g., link (:heavy_check_mark: well done!)
  • Build passing link (:heavy_check_mark: well done!)

*Remember to use the format specified, else it will not be picked up by the bot
**Remember that the deadline is the midnight before your tutorials

Individual progress of @darrendragonlee

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @case141

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @suriruhani

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @fterh

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @DoItTomorrow

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:exclamation: try to do by next milestone)

Tutor: @ewaldhew

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-03-13 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 6 project progress

Subject: feedback on week 6 project progress

See v1.1 progress guide for more details of the activities mentioned below.

Team progress

  • Team org and repo set up with the correct names (:heavy_check_mark: well done!)
  • PR created from team repo to AB-3 or AB-4 (:heavy_check_mark: well done!)

Individual progress of @darrendragonlee

  • Used forking workflow:
    • Team repo forked to your GitHub account (:heavy_check_mark: well done!)
    • PRs created to update Java code (:heavy_check_mark: well done!)
    • PRs created to update documents (:heavy_check_mark: well done!)

Individual progress of @case141

  • Used forking workflow:
    • Team repo forked to your GitHub account (:heavy_check_mark: well done!)
    • PRs created to update Java code (:heavy_check_mark: well done!)
    • PRs created to update documents (:heavy_check_mark: well done!)

Individual progress of @suriruhani

  • Used forking workflow:
    • Team repo forked to your GitHub account (:heavy_check_mark: well done!)
    • PRs created to update Java code (:exclamation: try to do by next milestone)
    • PRs created to update documents (:heavy_check_mark: well done!)

Individual progress of @fterh

  • Used forking workflow:
    • Team repo forked to your GitHub account (:exclamation: try to do by next milestone)
    • PRs created to update Java code (:exclamation: try to do by next milestone)
    • PRs created to update documents (:exclamation: try to do by next milestone)

Individual progress of @DoItTomorrow

  • Used forking workflow:
    • Team repo forked to your GitHub account (:exclamation: try to do by next milestone)
    • PRs created to update Java code (:exclamation: try to do by next milestone)
    • PRs created to update documents (:exclamation: try to do by next milestone)

Tutor: @ewaldhew

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-02-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.

As a user I would like to be able to search for research materials

So that I can easily retrieve the information using various categories and have it displayed in an indexed fashion with all details displayed.

  • search the sources by title (and their combination)
  • search the sources by a combination of tags, title, details, sources, and types (CONJUNCTION)
  • search the sources by a combination of tags, title, details, sources, and types (DISJUNCTION)
  • search the sources by a combination of tags, title, details, sources, and types (NEGATION)
  • make the search be able to match parts of words
  • make the search be able to match closely related words

Search by tags/categories

As a user, I would like to be able to search by the tags/categories of any particular information so that I can find the same type of material that I need.

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.