Documentation, templates, and examples should default to "embedded" as the primary mode about moose HOT 14 CLOSED

There are solutions for automatic file synchronization. I am using goodsync as a sync tool.
It copies the *.lua files automatically from my MOOSE package to the Scripts\Moose directory in the program files folder.

The embedded file is indeed a PIA, that is why i started with dynamic loading in the first place :-) Believe me, i've searched for all the options, and had to do some lua tricks to make the dynamic loader work ...

FC

from moose.

But i am hearing you... You suggest to emphasize the "embedded" loading as the only option...
I think you're right. I should emphasize this more in the documentation.

Embedded loading first, and only for those who are developing (and extending) Moose, dynamic loading is used, which is a more advanced loading method.

Also, maybe indeed we can setup a process to automatically copy the Moose_Embedded.lua file into a mission file before publishing... I think this can be easily done with a zip tool installed.

from moose.

This sounds good.

Also, I think even when developing, we should definitely test with the embedded files. So the workflow is: edit MOOSE Lua, generate embedded file, and then the mission files load the embedded file. That way, we are testing the actual file that 99% of people (non MOOSE developers) will use. With good file syncrhonization and scripts, this should all be in the background. Eventually, do away with dynamic loading (two ways of using MOOSE makes maintenance/debugging etc. tricky)

from moose.

I should note that I am currently having a lot of difficulty in getting even a simple mission to work with embedded MOOSE. Dynamic is no problem. But "Do Script File" with "MOOSE/Loaders/Moose_Load_Embedded.lua" does not work. Directly "Do Script File" with "MOOSE/Embedded/Moose_Embedded.lua" also does not work. "Do Script File" with "MOOSE/Loaders/Moose_Load_Dynamic.lua" works fine. Still trying to figure this out.

from moose.

I should note that I am currently having a lot of difficulty in getting even a simple mission to work with embedded MOOSE. Dynamic is no problem. But "Do Script File" with "MOOSE/Loaders/Moose_Load_Embedded.lua" does not work. Directly "Do Script File" with "MOOSE/Embedded/Moose_Embedded.lua" also does not work. "Do Script File" with "MOOSE/Loaders/Moose_Load_Dynamic.lua" works fine. Still trying to figure this out.

I'll check it too... Haven't tested it.

from moose.

Again, got my accounts mixed up! Sorry. Above is me again ....

[Edit: removed above post and reproducing here]

Also, maybe indeed we can setup a process to automatically copy the Moose_Embedded.lua file into a mission file before publishing... I think this can be easily done with a zip tool installed.

If this can be automated, along with auto-generation of the Moose_Embedded file, then the dynamic loading can be deprecated.

But even if not, as I suggest above, I think a workflow in which following any editing of the MOOSE library, the library gets "compiled" into single embedded file, and this is the file that is loaded in the mission, would guarantee that all our testing/experimentation/mission-building is done using code/files that will generally be available to most people.

from moose.

Related to:

But "Do Script File" with "MOOSE/Loaders/Moose_Load_Embedded.lua" does not work. Directly "Do Script File" with "MOOSE/Embedded/Moose_Embedded.lua" also does not work.

I think i found the solution.
Reload the latest Moose_Embedded.lua file from the Moose\Embedded folder.

recheck pls.

from moose.

Before i forget. Nice to meet you Jeet. You're welcome to join.
Would this automatic including of the moose_embedded.lua file be something you could investigate?
The problem is with your following statement:

and this is the file that is loaded in the mission,

cannot be done when your mission is open. You would have to close your mission, and reload it again after the embedded file got included. That is why i started with dynamic loading...

Once a mission is "finished" or ready for a release, the embedded file could be added. I think indeed that process can be further automated.

from moose.

Nice to meet you, too!

OK, I do not understand this.

So here is the process:

1. Go to Mission Editor
2. create new mission
3. Create new trigger: ONCE, no condition, ACTION = "Do Script File", with file = "MOOSE/Embedded/Moose_Embedded.lua"
4. Create new trigger: ONCE, condition = time > 2 (though I have also tried nothing here), ACTION = "Do Script File", with file = "my_mission.lua"
5. Fly

You are saying the above is wrong?

from moose.

It is not wrong. it is good, if you want only to use embedded loading, which is fine.
If you can make a trick to get every time ALL the mission file get updated with a new embedded.lua file, once i've changed some moose code, then that would be great.
Even the mission file you currently have open in your mission editor, without having to reload it..

from moose.

Ah yes, but for some reason, the above does not seem to work for me. Still trying to figure it out!

from moose.

Jeet, i have completely reworked the loading method and have implemented a tool that can replace the MOOSE version in a batch of DCSW mission files residing in a couple of directories.
Now the embedded is the standard method. Dynamic is still supported, but not anymore documented. It is for developer purposes only.

Have a look at the main site here:
http://flightcontrol-master.github.io/MOOSE/

from moose.

Definitely will be helpful getting people to use this!

from moose.

Done, now only one file needs to be included, which is Mooe.lua.

from moose.