Define and document naming conventions and rename misaligned classes - Githubissues

FlightControl-Master / MOOSE

Mission Object Oriented Scripting Environment (MOOSE) for lua mission scripting design in DCS World

http://flightcontrol-master.github.io/MOOSE/

GNU General Public License v3.0

290 stars 94 forks source link

Define and document naming conventions and rename misaligned classes #2091

Open kaltokri opened 8 months ago

kaltokri commented 8 months ago

Some examples:

Fsm / Atis / Fox vs. AWACS / CSAR / CTLD. AI.AI_A2A_Gci vs. AI.AI_A2G_BAI. -> I suggest upper case for all acronyms.
Why Ops.OpsGroup / Ops.OpsTransport / Ops.OpsZone instead Ops.Group / Ops.Transport / Ops.Zone ?
Core.MarkerOps_Base -> Core.MarkerOpsBase ?
Ops/Intelligence.lua is class Ops.Intel. Rename file to Ops/Intel.lua
Ops.Airwing = Ops.AirWing.lua

ToDos:

We need to define a naming convention.
It must be documented
Check which parts are misaligned to the naming convention
Check if we can change the misaligned parts without breaking downwards compatibility
If a chenage will break downwards compatibility, we need to decide: Do it / don't do it / do it only in development branch