It is located in index.js to maintain a global variable of it and it is better allocated there than inside MissionContainer

Does not work for building yet, will look into solutions

Allows us to create more than one window on electron and linking them all to one html file without collision.

This works for building the app too, not just on development.

Next step is to update the new mission window to display whatever information is necessary for mission selected. See #45

Finding issues with geolocation, will fix

See the following thread: electron/electron#16139

This issue is fixed in the following thread, but wont be released until Electron 5: electron/electron#15618

MissionContainer has the logic and list of missions that the MissionWindow will be using.

Any information (mission has started, paused, completed, etc) in the MissionWindow will be retrieved from the MissionContainer

Travis CI had a small error with badge, needed to specify branch.

Currently has vulnerabilities, will be fixed in svg/svgo#1089

Note: when importing files (import X from './X'), and there are two files X.js and x.css, the program will import the CSS file (when intended to import the JS file).

This will cause an error in the program. The solution is to not name the CSS file as JS files.

Took a while to figure out since all code looked normal. Ill get working on getting structure up (will do Takeoff as an example)

Needs more work:
1. Create a general mission jsx class, since these classes seem to have similar logic.
2. Create some jobs. Its likely that jobs will need a general class too.

These general classes, by the way, should be superclasses to be extended from.

… to run

More logic. Should not affect building other missions. Just understand to forward mission index to mission jsx classes to be able to return that index to mission container to complete missions (and be able to run more than one mission at a time).

See #56.

Needs a lot of styling. Needs more logic.
 - Logic to add parameters from jobs to Orchestrator through startJob.
 - Logic to filter out unrelated veihicles while mission window is open. I might work on this next.

There are minor logic issues still. Will push anyway to share.
 - Buttons might not be properly turned on/off
 - PropTypes need to be fixed

Current version struggles to keep mission window state as well as job state.

The mission window can only keep track of one misison at a time, but it should be able to keep track of all missions. If I start one mission and start another, the mission window will forget all information about the first mission. There should be a fix to this.

Work in progress.

Note: I realized Leaflet loves to maky a lot of things any type, and our linter doesnt like that

We will use https://github.com/yagajs/leaflet-cached-tile-layer for our Cached Tile Layer

Control TypeScript added, will continue on my PC

Added react-leaflet-control to declaration files. Moved the declaration file to root of repository, named as global.d.ts.

I got brain cancer from doing this

Helps with seeing what the variables are when hovering over them.

CachedTileLayer doesnt work right now and will fix soon.

I dont think I'll work on integrating TypeScript with mission window. I'll let @maquino123 and @tnleang handle that

TypeScript support

Fixed README too

DictionaryList makes more sense than ListDict, since this is a dictionary of lists, not a list of dictionaries.

Also edited/fixed comments to help with the `atom-typescript` plugin when hovering over variables.

Re-allocated declaration files.

Turned on a check that will crash the program before loading if MAPBOX_TOKEN is not defined.

From their repository:

The version range of TypeScript currently supported by this parser is >=3.2.1 <3.4.0.

… local system

Will fix the issues in a little bit.

This commit should fail the build test.

- Adding return types to all functions (seems to finally show up to my system after upgrading to typescript-eslint v1.6

- Added functions to DictionaryList so that tsc does not throw an error

- Fixed some comments

Needs unit tests

Needs unit tests

You ready to merge yet @maxwey :^)

Also updated .travis.yml script to run tests one at a time.

`npm test` can be left so that the developer can use it whenever necessary.

Added signatures to json imports in src/static.

Added electron to import's core-modules so we don't need to put "eslint-disable-line import/no-extraneous-dependencies" on every electron import.

Mapped vehicles in order before passing it from vehicle container to vehicle table to increase performance from O(n^2 logn) to O(nlogn).

Changed "listener" terminology in UpdateHandler to "handler".

Changed updateVehicles and updateMessages notification to take multiple
parameters instead of an array of vehicles/messages through parameter
destrucutring.

Added logic to static/index.ts to set startLocation and export that as a
LatLngZoom instead of having other classes figure out that location.
Also changed order of importing files in the same file, will add
documentation on the order local files should be imported.

Added disconnection time constant to static/vehicle.json that is also
exported throughs static/index.ts.

Changed Vehicle interface in util/types.ts to VehicleUpdate. Will
eventually change this to UpdateMessage (see the JSON protocol) and will
add typings for all other messages too (when Vehicle is done being
implemented, the user interface will take in the Vehicle objects instead
of UpdateMessages).

Added failsafe measures to updateVehicles function.

Functions without arrow notation will struggle to access
private/instance variables in classes. Also added a default export to
util/util.ts

Integrated class to the rest of the class. The Vehicle class is created
using a message (which has an sid field), which will output a
VehicleObject that can be sent to the user interface (through
ipcRenderer) and can be used then.

Added definitions for Messages and Jobs too.

Help my soul

Tested with XCTU, it works. Everything else that needs to be created is
all logic in Orchestrator and MessageHandler (and also recreate
Missions).

Changed exports in static/index so that the variables can be seen as configuration files when imported to other files. Will cause less confusion to the developer.

Moved all source types to a `src/types` folder. Note this is different from external module typings, which will contain types for external modules.

Commented out things that do not work right now because of these changes, and will fix them back once I have the time.

Added typings to all tasks and messages.

TODO:

Fix code that I have commented with code that works for it now.

Finish the type guard functions in src/types/messages. @tnleang can you help me with this?

Fix documentation for all of this. Perhaps add a `docs` folder in root?

Fixed one small thing with connect message as well as removed the requirement for an errorMessage when a vehicle is in an error state.

Also removed the requirement for an error field in badMessage message, but we will be filling that field in whenever we send a badMessage. This is in the case a vehicle does not provide an error field in the badMessage message.

Got lazy commenting the code at the end but screw it. I think I commented the important parts, but commenting all code is better.

Also removed unnecessary and blatantly obvious comments.

Comments that describe each function would make this file better, but this should be the final version. Lets hope that no changes are needed in the future

Also updated QuickScan Task definition

Updated to this commit

https: //github.com/NGCP/GCS/commit/5e1bd6a8eeeabe3284d9fea0ad416431e61ab571#diff-9c8de213580183bcd8fa27b3fdefce6b
Co-Authored-By: Maxence Weyrich <[email protected]>

Was working on Mission, but I'll give it a rest. Will do it tomorrow

Mission parameters is a mix of information required, as well as options.

A selected number of missions can be chosen to perform at once, but since the output of one mission goes into the input of the next, the user only needs to add mission info for the first mission. The user will need to input mission options for all missions, however.

…ameters)

Also decided to make all information in `ISRSearchMissionParameters` required.

The UI should just fill in 0 for all of those fields if the option for that is off. The Mission class will ignore the parameters completely.

Need sleep will finish tomorrow, as well as Orchestrator

MessageHandler will forward all messages to the Orchestrator to acknowledge, as MessageHandler does not know if the message's source vehicle is connected or not.

- Converting missionWindow from js to ts
- Reorganize jobs directory

- deleted missionContainer in mainWindoow

`eslint-plugin-import` causes TypeError issues

import-js/eslint-plugin-import#1322

I'm tired time to sleep

Went on with Max's definition of handleUnresponsiveVehicle.

Added support to add tasks to a job by a certain comparison criteria (allows for obtaining the next task in a different way).

Ensured that activeVehicleMapping ONLY has the vehicles that are doing a job that relates to the mission. Any other vehicles are completely ignored for the mission (this is in the case the user interface sends extra jobs that are irrelevant to the mission over to the constructor). Doing this allows us to not have to check all the time if the job in the activeVehicleMapping is a related jobType or not. It simply is.

Added support to keep track of vehicles of a mission by having a callback on the update messages that are sent from the vehicles.

Will read through the code one more time before starting to implement other missions + Orchestrator

Small logic changes here and there too, nothing significant.

Also converted all files to TypeScript/TypeScript React files.

Made MessageHandler ignore whether or not the message type field is capitalized or not.

Made completionCallback of Mission class return a MissionParameter, not MissionInformation.

Modified stop() function of Mission class. Will need to modify naming of functions/variables in this class even more, its very unreadable.

Added "stopMission" support to ipc.ts.

Renamed locations.json to location.json.

Added disconnect() support to Vehicle. It is not possible to disconnect the vehicle from the Orchestrator through vehicle.update().

Fixed logic for acknowledgement messages in MessageHandler.

Fixed logic for stopping sending messages in MessageHandler.

Simplified logic in Mission to log parameters whenever a mission completes.

Changed lastConnectionTime to update to the time field in the messages.

Added more typings/functions.

Will add the original authors to this commit

Co-Authored-By: Maxence Weyrich <[email protected]>
Co-Authored-By: Kedwin Chen <[email protected]>

Really need to divide the message.ts file to different files.

Will add the rest of the files tomorrow.

Co-Authored-By: Maxence Weyrich <[email protected]>
Co-Authored-By: Kedwin Chen <[email protected]>

Again will need to clean code. Should work

Noticed indexing was wrong in startNextMission so I fixed that.

Final fix to logic of MessageHandler's receivingMessage function. It should only forward the first message of a certain ID to the Orchestrator, but acknowledge all valid messages.

Added check to Orchestrator to check Mission's vehicles before calling mission.update()

Did check on all vehicle states before assigning jobs in Mission (instead of checking states while assigning jobs).

Added check for new message for bad messages too.

Fixed logic in Orchestrator to set completionParameters of this mission to the starting parameters for next mission.

Logic in Mission will be to send stop to all vehicles if the stop() function is called while the Mission status is not "ready". If Mission status is "initializing" it will also stop sending current messages.

Added logic to Vehicle's status handler to remove the callback when it disconnects, as the other callback should not happen if the vehicle is too late to accept its job.

…nParameters

Throws an error, and mission will stop if undefined is returned.

Allocated the fat messages.ts file into many files that make more sense.

Removed float hex, as we will use compression with msgpack to make things work.

Also removed "options" from StartMessage as I believe this is difficult to handle in other languages (C in particular).

Not sure why

Mission Window + Missions need work

Fixes #64