Read and parse launch arguments.
+ launch arguments need to follow this syntax:
+
<player1_instance> <player2_instance> [nogui]
+
<arg> -> mandatory parameter
+ [arg] -> optional parameter
+ player_instance values are: "Human" or "Random"
+ nogui to launch the game in terminal or nothing to launch in graphical interface
Returns an array containing the constants of this enum type, in
+the order they are declared.
+
+
Returns:
+
an array containing the constants of this enum type, in the order they are declared
+
+
+
+
+
+
valueOf
+
public staticDirectionvalueOf(java.lang.String name)
+
Returns the enum constant of this type with the specified name.
+The string must match exactly an identifier used to declare an
+enum constant in this type. (Extraneous whitespace characters are
+not permitted.)
+
+
Parameters:
+
name - the name of the enum constant to be returned.
+
Returns:
+
the enum constant with the specified name
+
Throws:
+
java.lang.IllegalArgumentException - if this enum type has no constant with the specified name
+
java.lang.NullPointerException - if the argument is null
reference every shot on the opponent board, left and middle side of the Triplet reference the coordinates and the
+ right side if this move hit or not an opponent ship
check if ship position and direction are valides and does not overlap on other vessels
+ add the ship to player ships list and return true if valid
+ false otherwise
reference every shot on the opponent board, left and middle side of the Triplet reference the coordinates and the
+ right side if this move hit or not an opponent ship
check if ship position and direction are valides and does not overlap on other vessels
+ add the ship to player ships list and return true if valid
+ false otherwise
This model (interface -> abstract class(es) -> concrete classes) prevent hard code.
+
This is the only object which interact with other object
+ Allows an outside person from the project to easily change the code or to add a view easily without modifying
+ existing classes
check if ship position and direction are valides and does not overlap on other vessels
+ add the ship to player AbstractPlayer.ships list and return true if valid
+ false otherwise
check if ship position and direction are valides and does not overlap on other vessels
+ add the ship to player AbstractPlayer.ships list and return true if valid
+ false otherwise
This model (interface -> abstract class(es) -> concrete classes) prevent hard code.
+
This is the only object which interact with other object
+ Allows an outside person easily change the code or add a view easily without modifying existing classes
This API (Application Programming Interface) document has pages corresponding to the items in the navigation bar, described as follows.
+
+
+
Overview
+
The Overview page is the front page of this API document and provides a list of all packages with a summary for each. This page can also contain an overall description of the set of packages.
+
+
+
Package
+
Each package has a page that contains a list of its classes and interfaces, with a summary for each. These pages may contain six categories:
+
+
Interfaces
+
Classes
+
Enums
+
Exceptions
+
Errors
+
Annotation Types
+
+
+
+
Class or Interface
+
Each class, interface, nested class and nested interface has its own separate page. Each of these pages has three sections consisting of a class/interface description, summary tables, and detailed member descriptions:
+
+
Class Inheritance Diagram
+
Direct Subclasses
+
All Known Subinterfaces
+
All Known Implementing Classes
+
Class or Interface Declaration
+
Class or Interface Description
+
+
+
+
Nested Class Summary
+
Field Summary
+
Property Summary
+
Constructor Summary
+
Method Summary
+
+
+
+
Field Details
+
Property Details
+
Constructor Details
+
Method Details
+
+
The summary entries are alphabetical, while the detailed descriptions are in the order they appear in the source code. This preserves the logical groupings established by the programmer.
+
+
+
Annotation Type
+
Each annotation type has its own separate page with the following sections:
+
+
Annotation Type Declaration
+
Annotation Type Description
+
Required Element Summary
+
Optional Element Summary
+
Element Details
+
+
+
+
Enum
+
Each enum has its own separate page with the following sections:
+
+
Enum Declaration
+
Enum Description
+
Enum Constant Summary
+
Enum Constant Details
+
+
+
+
Tree (Class Hierarchy)
+
There is a Class Hierarchy page for all packages, plus a hierarchy for each package. Each hierarchy page contains a list of classes and a list of interfaces. Classes are organized by inheritance structure starting with java.lang.Object. Interfaces do not inherit from java.lang.Object.
+
+
When viewing the Overview page, clicking on "Tree" displays the hierarchy for all packages.
+
When viewing a particular package, class or interface page, clicking on "Tree" displays the hierarchy for only that package.
+
+
+
+
Deprecated API
+
The Deprecated API page lists all of the API that have been deprecated. A deprecated API is not recommended for use, generally due to shortcomings, and a replacement API is usually given. Deprecated APIs may be removed in future implementations.
+
+
+
Index
+
The Index contains an alphabetic index of all classes, interfaces, constructors, methods, and fields, as well as lists of all packages and all classes.
+
+
+
Serialized Form
+
Each serializable or externalizable class has a description of its serialization fields and methods. This information is of interest to those who implement rather than use the API. While there is no link in the navigation bar, you can get to this information by going to any serialized class and clicking "Serialized Form" in the "See Also" section of the class description.
You can search for definitions of modules, packages, types, fields, methods, system properties and other terms defined in the API, using some or all of the name, optionally using "camel-case" abbreviations. For example:
+
+
j.l.obj will match "java.lang.Object"
+
InpStr will match "java.io.InputStream"
+
HM.cK will match "java.util.HashMap.containsKey(Object)"
reference every shot on the opponent board, left and middle side of the Triplet reference the coordinates and the
+ right side if this move hit or not an opponent ship
check if ship position and direction are valides and does not overlap on other vessels
+ add the ship to player AbstractPlayer.ships list and return true if valid
+ false otherwise