Skip to content

Commit

Permalink
Merge pull request #136 from 3m0W33D/master
Browse files Browse the repository at this point in the history
Update broken table and fix class diagram for DG
  • Loading branch information
3m0W33D authored Oct 27, 2021
2 parents 14a9f2d + b113681 commit b7ab962
Show file tree
Hide file tree
Showing 7 changed files with 16 additions and 16 deletions.
11 changes: 10 additions & 1 deletion docs/DeveloperGuide.md
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,14 @@ Import the coding style xml file into your IntelliJ IDEA.

### 3.1 Architecture

![](attachments/MainInit.png)

Initialization of all the classes required for Terminus class to run

![](attachments/MainLogic.png)

Main loop logic of Terminus

### 3.2 UI Component
![](attachments/UIClassDiagram.png)

Expand Down Expand Up @@ -466,7 +474,8 @@ Custom commands and Command Parsers should be easy for others to implement.
| Approach | Pros | Cons|
| --- |---|---|
| Single Command Parser with all Commands inherit from a single `Command` Class, a large switch statement to separate commands.| Easy to implement and `execute` function for each class has higher flexibility as they can have different arguments| When extending to multilevel workspace can be tedious to implement.|
| Multiple Command Parsers each with its own set of commands, require separate managing. | Easy to create new workspace and add command specific the to workspace.| Implementation can be tedious and difficult to upgrade and manage.
| Multiple Command Parsers each with its own set of commands, require separate managing. | Easy to create new workspace and add command specific the to workspace.| Implementation can be tedious and difficult to upgrade and manage. |

Eventually the team decide to go with the second implementation, as we require multi-level
workspaces and would like to create our own workspace for each feature. Aside from that the
`Command` provide common functionality that many commands need hence reducing repetition of code.
Expand Down
Binary file modified docs/attachments/Content.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/attachments/MainInit.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/attachments/MainLogic.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/attachments/Module.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
5 changes: 4 additions & 1 deletion docs/uml/Content.puml
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
@startuml
skinparam classAttributeIconSize 0
hide circle

Content <|-- Note
Content <|-- Link
Expand All @@ -21,7 +23,8 @@ class ContentManager <T extends Content> {
+ setContent(contents: ArrayList<T> ): void
}
!endsub
abstract class Content {

abstract class "{abstract}\nContent" as Content{
# name: String
# data: String
}
Expand Down
16 changes: 2 additions & 14 deletions docs/uml/Module.puml
Original file line number Diff line number Diff line change
@@ -1,20 +1,8 @@
@startuml
'https://plantuml.com/class-diagram



'abstract class DGS
'abstract AbstractCollection
'interface List
'interface Collection
'
'List <|-- AbstractList
'Collection -- AbstractCollection
'
'Collection <|- List
'AbstractCollection <|- AbstractList
'AbstractList <|-- ArrayList

skinparam classAttributeIconSize 0
hide circle

NusModule -> "1" ContentManager: noteManager
NusModule -> "1" ContentManager: linkManager
Expand Down

0 comments on commit b7ab962

Please sign in to comment.