Initial commit.

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at pablo.edronkin@yahoo.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# SQLC - Guidelines for contributors.
+
+
+## Overview:
+
+Thanks for reading these guidelines; nothing fancy or complicated here, so
+please take your time to review the info listed below. 
+
+
+## Read first:
+
+* /~https://github.com/PESchoenberg/SQLC/blob/master/README.md
+
+* /~https://github.com/PESchoenberg/SQLC/blob/master/CODE_OF_CONDUCT.md
+
+
+## Conventions:
+
+* Try to be brief and to the point regarding your requests and proposals.
+
+* Write clear and orderly code while respecting the general coding style of the
+project.
+
+* You need to have a verified signature. See
+https://help.github.com/articles/managing-commit-signature-verification/
+
+* Nothing is written in stone. New guidelines might come into effect at any
+time. Review the docs from time to time to keep up.
+
+

COPYING

@@ -0,0 +1,9 @@
+This work is based on the Orbiter Space Flight Simulator and derived code by Dr. Martin Schweiger et al. Hence, all developments and expansions made by myself on these files are based on the work of the aforementioned authors and the applicable terms of use, copyright ownership and licenses applicable to this work are those established by the authors of the original code.
+
+- Please visit http://orbit.medphys.ucl.ac.uk/ for more info on Orbiter and its terms of use.
+
+- Email me at pablo.edronkin(at)yahoo.com for questions and comments.
+
+
+Pablo Edronkin
+

README.md

@@ -0,0 +1,67 @@
+# SQLC - Multi function display for the DGIIIAI Delta Glider.
+
+
+
+
+## Overview:
+
+SQLC is an MFD specfically designed to interact with the onboard expert system
+that runs the DGIIIAI Delta Glider for Orbiter Space Flight Simulator.
+
+
+## Dependencies:
+
+* Orbiter Space Flight Simulator 2010 (OSFS) or newer 
+- http://orbit.medphys.ucl.ac.uk/
+
+* MS Visual Studio 2010 or higher with OpenMP compatibility.
+
+* Sqlite3 - https://www.sqlite.org/index.html
+
+* DGIIIAI - /~https://github.com/PESchoenberg/DGIIIAI.git
+
+
+## Installation:
+
+* Backup your original Orbiter installation or install a new one before
+installation.
+
+* Carefully review the contents of the compressed file of this project
+in order to see what will be copied.
+
+* Make sure that you already have installed DGIIIAI
+
+* Copy the contents of \orbiter folder into your Orbiter simulator main folder.
+
+
+## Uninstall:
+
+* You will have to manually remove the files provided. Therefore it is
+advisable that you install this project on a development installation of
+Orbiter instead of you main one.
+
+
+## Usage:
+
+* Enable this MFD as any other standard MFD or dll for OSFS.
+
+* Load one of the provided scenarios. The ship will soon start acting on its
+own.
+
+
+## Credits and Sources:
+
+* Dr. Martin Schweiger, for OSFS.
+
+* Credits for the original DGIII and MFD template files are kept as in the
+original versions.
+
+* Please notify me in case that I have missed some credits.
+
+
+
+## License:
+
+* Please read the contents of file COPYING for license info.
+
+

orbiter/orbitersdk/samples/SQLC/SQLC/mfdparams.h

@@ -0,0 +1,9 @@
+#ifndef __MFDPARAMS_H
+#define __MFDPARAMS_H
+
+//MFD API params
+
+const int NUM_BUTTONS = 11;
+//const int MAX_NUMBER_OF_PAGES=55;
+
+#endif // !__MFDPARAMS_H