From 666e0b115b9dada5a85dba28a47b1f85241b24f8 Mon Sep 17 00:00:00 2001 From: Grey-Echo Date: Fri, 31 Mar 2017 17:21:54 +0200 Subject: [PATCH 1/6] Small tweaks to README.md --- docs/README.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/docs/README.md b/docs/README.md index 84296d89f..32527e2f5 100644 --- a/docs/README.md +++ b/docs/README.md @@ -29,7 +29,7 @@ There are 3 different ways how you can use MOOSE, each with a different engageme -## 2.1) Use MOOSE as a normal user +## 2.1) Use MOOSE as a Mission Designer Refer to the detailed **[Usage Guide](Usage_Guide.html)** for more information. @@ -39,11 +39,11 @@ Refer to the detailed **[Usage Guide](Usage_Guide.html)** for more information. Beta testers of MOOSE are requested to install additional software. -As a return or as a reward, missions designers get: +As a return or as a reward, testers get: - * New developed features for the next MOOSE release can be tested and incorporated in your missions. - * You can evaluate and contribute on the stability of the next release. - * Your mission design becomes very flexible. New features are dynamically added once delivered into your missions. + * Newly developed features planned for the next MOOSE release can be tested and incorporated in your missions early. + * You can evaluate and contribute to the stability of the next release. + * Your mission creation workflow becomes very flexible. New features are dynamically added to you missions. Please read the detailed **[Beta Test Guide](Beta_Test_Guide.html)** for more information. @@ -94,15 +94,14 @@ You'll need to browse to the right MOOSE Class within the inheritance tree struc ## 4.1) MOOSE Demonstration Missions -The framework comes with [demonstration missions](https://github.com/FlightControl-Master/MOOSE_MISSIONS), -that you can try out and helps you to code. +The framework comes with demonstration missions which can be downloaded [here](https://github.com/FlightControl-Master/MOOSE_PRESENTATIONS/releases), that you can try out and helps you to code. These missions provide examples of defined use cases how the MOOSE framework can be utilized. Each test mission is located in a separate directory, which contains at least one .lua file and .miz file. The .lua file contains the mission script file that shows how the use case was implemented. You can copy/paste code the code snippets from this .lua file into your missions, as it will accellerate your mission developments. You will learn, see, and understand how the different MOOSE classes need to be applied, and how you can create more complex mission scenarios by combining these MOOSE classes into a complex but powerful mission engine. -These exact test missions are also demonstrated at the demo videos in the YouTube channel. +Some of these exact test missions are also demonstrated in a video format on the [YouTube channel](https://www.youtube.com/channel/UCjrA9j5LQoWsG4SpS8i79Qg). @@ -287,4 +286,4 @@ Trust I've spent hours and hours investigating, trying and writing and documenti Hope you think the idea is great and useful. Thank you! -FC \ No newline at end of file +FC From 6de01e3303a50e3a407fc70d3d38a91616f6b29e Mon Sep 17 00:00:00 2001 From: Grey-Echo Date: Fri, 31 Mar 2017 17:45:43 +0200 Subject: [PATCH 2/6] Small tweaks to Usage_Guide.md --- docs/Usage_Guide.md | 29 ++++++++++++----------------- 1 file changed, 12 insertions(+), 17 deletions(-) diff --git a/docs/Usage_Guide.md b/docs/Usage_Guide.md index ec28dc0c3..90afd885b 100644 --- a/docs/Usage_Guide.md +++ b/docs/Usage_Guide.md @@ -6,11 +6,9 @@ and use MOOSE within your missions. ## 1.1) MOOSE framework at GitHub You can find the source of [MOOSE framework on GITHUB](https://github.com/FlightControl-Master/MOOSE/). -It is free for download and usage, but it is under license of the GNU 3.0 open source license policy. -The MOOSE development uses the GITHUB service to enforce and control a structured development within a growing community. -GITHUB enforces a structured approval process, release and change management, and a communicative distribution and deployment. -The MOOSE framework development is considered an open source project, where contributors are welcome to contribute on the development. -Some key users have already started with this process. Contact me if you're interested to contribute. +It is free for download and usage, since it is released under the GNU 3.0 open source license policy. +Although the MOOSE contributors and tester are using the GitHub service to enforces a structured approval process, release and change management, and a communicative distribution and deployment, you, as a mission designer, don't need to mess with it. Still, if you are interrested intesting the latest features of MOOSE of in adding your own, you can read the [relevant](http://flightcontrol-master.github.io/MOOSE/Beta_Test_Guide.html) [guides](http://flightcontrol-master.github.io/MOOSE/Contribution_Guide.html) and/or contact FlightControl +The MOOSE framework development is an open source project, and as such, contributors are welcome and encouraged to contribute on the development.Some key users have already started with this process. ## 1.2) Eclipse LDT @@ -46,7 +44,8 @@ The delivery of MOOSE follows a structured release process. Over time, new featu 1. If you don't have JAVA yet, you may have to install [java](https://www.java.com/en/download) first. 2. Download and Install [Eclipse LDT](https://eclipse.org/ldt) on your Windows 64 bit system. -Now you should have a working LDT on your system. +TNow you should have a working LDT on your system. +Don't skip this step, LDT is a game-changer. Don't believe us ? Well we challenge you to test and tell us what you think ! Once you tried coding with intellisense, you won't go back ! ## 2.3) Configure your LDT for the usage of MOOSE. @@ -66,7 +65,7 @@ When you open EclipseLDT for the first time, it will ask you where to put your * ### 2.3.2) Create a new **Project** in LDT. -Here we will create a **New Project** called **Moose_Framework** in your LDT environment. +Here, we will create a **New Project** called **Moose_Framework** in your LDT environment. The project details are already defined within the MOOSE framework repository, which is unzipped on your local MOOSE directory on your PC. We will link into that directory and automatically load the Project properties. @@ -184,7 +183,7 @@ the file that contains all the lua code using the Moose framework using your mis ## 2.4.2) Create your first Mission file -In the MOOSE package, a file named **Moose.lua** can be found. +In the root of the MOOSE package, a file named **Moose.lua** can be found. In order to create or design a mission using the MOOSE framework, you'll have to include this **Moose.lua** file into your missions: @@ -269,6 +268,8 @@ This will activate a script that will automatically re-insert your mission .lua ## 2.4.4) Create folder links into your "My Missions" folder in Saved Games/DCS/Missions. +***TODO : Detail how hard links work, explain how they help the wworkflow*** + This trick will save you a lot of time. You need to install the tool ... to create easily new links. Select from the following possible links that can be created to save you time while browing through the different folders to include script files: @@ -279,13 +280,7 @@ Select from the following possible links that can be created to save you time wh # 4) Demonstration Missions -The framework comes with [demonstration missions](https://github.com/FlightControl-Master/MOOSE_MISSIONS), -that you can try out and helps you to code. -These missions provide examples of defined use cases how the MOOSE framework can be utilized. Each test mission is located in a separate directory, which contains at least one .lua file and .miz file. -The .lua file contains the mission script file that shows how the use case was implemented. -You can copy/paste code the code snippets from this .lua file into your missions, as it will accellerate your mission developments. -You will learn, see, and understand how the different MOOSE classes need to be applied, and how you can create -more complex mission scenarios by combining these MOOSE classes into a complex but powerful mission engine. - -These exact demonstration missions are also explained at the demo videos in the YouTube channel. +The framework comes with demonstration missions which can be downloaded [here](https://github.com/FlightControl-Master/MOOSE_PRESENTATIONS/releases), that you can try out and helps you to code. +These missions provide examples of defined use cases how the MOOSE framework can be utilized. Each test mission is located in a separate directory, which contains at least one .lua file and .miz file. The .lua file contains the mission script file that shows how the use case was implemented. You can copy/paste code the code snippets from this .lua file into your missions, as it will accellerate your mission developments. You will learn, see, and understand how the different MOOSE classes need to be applied, and how you can create more complex mission scenarios by combining these MOOSE classes into a complex but powerful mission engine. +Some of these exact test missions are also demonstrated in a video format on the [YouTube channel](https://www.youtube.com/channel/UCjrA9j5LQoWsG4SpS8i79Qg). From a49c5b2deafb64e85a3bfbe46981bba07f3c8168 Mon Sep 17 00:00:00 2001 From: Grey-Echo Date: Fri, 31 Mar 2017 22:52:14 +0200 Subject: [PATCH 3/6] Hope this works --- docs/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/README.md b/docs/README.md index 32527e2f5..56c645be6 100644 --- a/docs/README.md +++ b/docs/README.md @@ -287,3 +287,4 @@ Hope you think the idea is great and useful. Thank you! FC + From 9085838189bf9a94eb8bfa62c8450f0f2825e30b Mon Sep 17 00:00:00 2001 From: Sven Van de Velde Date: Sat, 1 Apr 2017 08:41:27 +0200 Subject: [PATCH 4/6] Set theme jekyll-theme-architect From c910a7a29b4f997caa5b0a231d320bf2f5eb8048 Mon Sep 17 00:00:00 2001 From: Sven Van de Velde Date: Sat, 1 Apr 2017 08:51:11 +0200 Subject: [PATCH 5/6] Set theme jekyll-theme-merlot --- docs/_config.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_config.yml b/docs/_config.yml index 3397c9a49..c50ff38da 100644 --- a/docs/_config.yml +++ b/docs/_config.yml @@ -1 +1 @@ -theme: jekyll-theme-architect \ No newline at end of file +theme: jekyll-theme-merlot \ No newline at end of file From bd0c78492a93ab7848c6b1a1b35d955b6e1aabea Mon Sep 17 00:00:00 2001 From: Sven Van de Velde Date: Sat, 1 Apr 2017 08:52:49 +0200 Subject: [PATCH 6/6] Set theme jekyll-theme-architect --- docs/_config.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_config.yml b/docs/_config.yml index c50ff38da..3397c9a49 100644 --- a/docs/_config.yml +++ b/docs/_config.yml @@ -1 +1 @@ -theme: jekyll-theme-merlot \ No newline at end of file +theme: jekyll-theme-architect \ No newline at end of file