ENIGMA Development Environment

Your idea is really great but it will be really difficult because GML is a toy language written by yoyo just to waste your time. You are way way better off learning any other langauge.

If you really want to then yeah of course you can hack together some GML to read gmk format with file_binary_read functions and chr() and ord(). Robert linked ismavatar's description of the gmk format that is really confusing but its accurate once you figure out what she means. http://ismavatar.com/lgm/formats/gmformat8.txt

GMK versions are 800,810 and 820 I think for GM8. Not much difference except I heard they added shaders to 820. 701 and 702 for GM7 with some encryption. 600 and 620 for GM6.

Theres a lot of fields that only exist in certain versions of the format for each resource, usually 800+, 600+, 440 only, 530 only, 430-600, 530-702. Theres usually a field before resource fields called GM version needed for the following info that will tell you what version of the resource you should use.

GMX is simple because its just a bunch of XML files in directories. The values for things like event number are the same as gmk and are in enigma source. I don't think theres much difference between GMX versions. GMZ is just a 7z compressed (not a zip) archive of a GMX folder.

You read about my new CLI http://enigma-dev.org/forums/index.php?topic=1476.0
It is supposed to be a format converter besides a compiler. I have python code for reading gmk 800+ and writing gmk 810, egm, gmx, and gmz and I want to add older gmk versions 600 and 702 and gmx/egm writing. I linked to other files that you should look at to get the format. If you need more help I can try to explain the format better than ismavatar's file. Try reading my the CLI code in the file CliClass.py it should sort of tell you how to try reading those file types.

https://github.com/DatZach/Gmk
https://github.com/RobertBColton/LateralGM/blob/master/org/lateralgm/file/GmFileReader.java

EGM is just a folder or a zipped folder with a bunch of files that josh invented the formats for. You need EEF, e-yaml and apng, besides the binary room format that is close to gmk room format.
https://github.com/enigma-dev/enigma-dev/blob/master/pluginsource/org/enigma/file/EEFReader.java
https://github.com/enigma-dev/enigma-dev/blob/master/pluginsource/org/enigma/file/ApngIO.java

For executables there are decompilers for older GM8 I think but why would you need to convert from them?

I think that the entire enigma library itself should be written in GML as much as possible. But GML needs to be changed into a better langauge first. So I think its a good idea but GML needs to be more powerful first.

New IDE in development written in python.

http://tinypic.com/view.php?pic=345yofs&s=5


http://tinypic.com/view.php?pic=9u5jit&s=5


Requires Python 2.7 or 3 and PyQt4 installed on linux.

Download Instructions for Windows
download zip from here https://github.com/sssstest/GameEditor/archive/master.zip
or run
git clone https://github.com/sssstest/GameEditor.gitYou need python from http://python.org/download/ and you need PyQt4 from http://www.riverbankcomputing.com/software/pyqt/download
PyQt5 hasn't been tested and probably doesn't work yet.

Download Depenencies
x86
http://python.org/ftp/python/2.7.5/python-2.7.5.msi
http://sourceforge.net/projects/pyqt/files/PyQt4/PyQt-4.10.3/PyQt4-4.10.3-gpl-Py2.7-Qt4.8.5-x32.exe

x64
http://python.org/ftp/python/2.7.5/python-2.7.5.amd64.msi
http://sourceforge.net/projects/pyqt/files/PyQt4/PyQt-4.10.3/PyQt4-4.10.3-gpl-Py2.7-Qt4.8.5-x64.exe

Once you have python and PyQt4 installed you can run the GameEditor ide by running ide.py from windows explorer or from the command line.

Supports reading GameMaker and ENIGMA game formats:
GMK version 800+ (reading and writing), GMX, GMZ, EGM
Writing gmk is suppored but disabled for safety right now. You should keep backups just in case.

The command line interface cli.py is for converting and compiling games on the command line

usage: cli.py [-h] [-o WRITEFILE] [-c CODE] [-r] [-t] [FILE.GMK]

input file with no options builds in debug mode and runs game

positional arguments:
  FILE.GMK      read file (gmk gm81 egm gmx gmz formats)

optional arguments:
  -h, --help    show this help message and exit
  -o WRITEFILE  convert to output file and exit (gmk ggg formats)
  -c CODE       empty game with object create event code
  -r            run game emode
You can test GML code with the cli using
python GameEditor/cli.py -c 'show_message("test");game_end();'That will create a game with 1 room and 1 object and the code in an event create action. On the terminal it will show
show_message: test

haha

If everyones forgotten, I found out that theres the GML function font_add that can create a font. It crashes ENIGMA right now because it never actually creates the fnt->texture, but someone should fix it for GM compatibility. That means ENIGMA has to have the ability to render a font on its own. That doesnt mean the compiler can do it though.

None of the game formats include glyph data I think, do they? Any program that reads game formats and compiles them with libcompileEGMf will have to be able to render the glyphs or the ENIGMA compiler will have to be able to render them.

The value for special vk_ keys is looked up from X keysym in enigma::keymap. The array enigma::usermap is set in ENIGMAsystem/SHELL/Platforms/xlib/XLIBwindow.cpp line 367:

for (int i = 'a'; i <= 'z'; i++) // 'a' to 'z' wrap to 'A' to 'Z'
      usermap[i] = i + 'A' - 'a';

In ENIGMAsystem/SHELL/Platforms/xlib/XLIBmain.cpp line 70 the result keycode should not be looked up through enigma::usermap because it changes lowercase to uppercase, corrupting the meaning of vk_ codes for numpad and function keys between vk_numpad1 = 97 and vk_f11 = 122. Diff fixes the problem:

--- a/ENIGMAsystem/SHELL/Platforms/xlib/XLIBmain.cpp
+++ b/ENIGMAsystem/SHELL/Platforms/xlib/XLIBmain.cpp
@@ -69,7 +69,8 @@ namespace enigma
                 return 0;
 
               if (!(gk & 0xFF00)) actualKey = enigma::usermap[gk];
-              else actualKey = enigma::usermap[(int)enigma::keymap[gk & 0xFF]];
+              else actualKey = (int)enigma::keymap[gk & 0xFF];
+              //else actualKey = enigma::usermap[(int)enigma::keymap[gk & 0xFF]];
               { // Set keyboard_lastchar. Seems to work without
                   char str[1];
                   int len = XLookupString(&e.xkey, str, 1, NULL, NULL);
@@ -91,7 +92,8 @@ namespace enigma
               return 0;
 
             if (!(gk & 0xFF00)) actualKey = enigma::usermap[gk];
-            else actualKey = enigma::usermap[(int)enigma::keymap[gk & 0xFF]];
+            else actualKey = (int)enigma::keymap[gk & 0xFF];
 
             enigma::last_keybdstatus[actualKey]=enigma::keybdstatus[actualKey];
             enigma::keybdstatus[actualKey]=0;

Keys affected were:

vk_numpad1 = 97,
  vk_numpad2 = 98,
  vk_numpad3 = 99,
  vk_numpad4 = 100,
  vk_numpad5 = 101,
  vk_numpad6 = 102,
  vk_numpad7 = 103,
  vk_numpad8 = 104,
  vk_numpad9 = 105,
  vk_multiply = 106,
  vk_add      = 107,
  vk_subtract = 109,
  vk_decimal  = 110,
  vk_divide   = 111,
  vk_f1  = 112,
  vk_f2  = 113,
  vk_f3  = 114,
  vk_f4  = 115,
  vk_f5  = 116,
  vk_f6  = 117,
  vk_f7  = 118,
  vk_f8  = 119,
  vk_f9  = 120,
  vk_f10 = 121,
  vk_f11 = 122,

Tracker screwed up my text but the issue is here http://enigma-dev.org/issues/index.php?id=194