This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
31
Proposals / Documenting stuff in a more centralized location
« on: May 20, 2010, 11:03:39 am »
I'd like to see Enigma stuff documented, and in a more centralized location. That is to say, "searching the forums to see where feature X is explained and debated" does not count.
Some things that need documenting:
Scope. Especially since I apparently can't use global.myvar, and had to find that out the hard way.
Typing.
Global Locals supported, and how much they are supported. E.g. the fact that direction, speed, hspeed and vspeed are all linked up, but they are not linked up to x/y.
Other intended differences between Enigma and GM not selectable by an option in the options pane.
Some things that need documenting:
Scope. Especially since I apparently can't use global.myvar, and had to find that out the hard way.
Typing.
Global Locals supported, and how much they are supported. E.g. the fact that direction, speed, hspeed and vspeed are all linked up, but they are not linked up to x/y.
Other intended differences between Enigma and GM not selectable by an option in the options pane.
32
General ENIGMA / LGM <-> Enigma Revision Compatibility List
« on: April 19, 2010, 04:42:52 pm »
This is mostly useful to devs, especially ones like me, who maintain a woring copy of both LGM and Enigma, checked out separately, or just users who want to try out custom LGM revisions - or for people who don't trust the LGM included with Enigma. Whatever the case, it's useful to me, and I wanted to put it somewhere, so don't troll about it not being useful.
This chart will tell you which revisions of LGM and Enigma are compatible. Notice, most likely, Enigma will include an LGM which is already compatible. Sometimes, one or the other will break and a certain revision simply won't be "compatible" at all.
I also only started keeping track of compatibility at a certain revision, hence why it doesn't go back any further.
*All LGM revisions are Versioning Branch only. All Enigma revisions are Trunk only.
This chart will tell you which revisions of LGM and Enigma are compatible. Notice, most likely, Enigma will include an LGM which is already compatible. Sometimes, one or the other will break and a certain revision simply won't be "compatible" at all.
I also only started keeping track of compatibility at a certain revision, hence why it doesn't go back any further.
LGM | ENIGMA | Reason for incompatibility |
427 | 180 | |
428 | 181-187 | CodeFrame syntax checking supported |
429-now | 188-now | Changed CodeFrame code editor field name. Accessed for syntax checking. |
*All LGM revisions are Versioning Branch only. All Enigma revisions are Trunk only.
33
Announcements / First R4 game, VERSION 2, despite everything being unimplemented
« on: April 18, 2010, 10:15:27 pm »
This is Catch the Clown, except that you don't have to "click" the clown, you just need to mouse-over him.
Catch the Clown.
The objective of the game is simple: To move your mouse over the moving clown as many times as possible, and thus increase your score. Yes, there is score. If there wasn't a score, it wouldn't really be a game. Each time you successfully catch the clown, he moves faster.
http://dl.dropbox.com/u/9975312/Games/Catch_the_Clown.gmk
~5 KB
Working since ENIGMA SVN Revision 244. Still working great since the move to GIT and since revision 4900aa6.
Coded entirely in LGM. Sprites stolen from the original.
Can you beat my highscore (in the screenshot)?
Features:
Sprites, Movement, Increasing difficulty, random redirection, changing background colors, bouncing off walls, able to be caught my mouse-over, score, displaying score in title bar
Lacking (due to limitations of Enigma at this time):
Clicking, Backgrounds, Sounds/Music
Version 1, which was created prior to sprite support (by showing a circle, without movement) is still available for reference.
http://www.IsmAvatar.com/other/mouse_to_ball.gm6
Catch the Clown.
The objective of the game is simple: To move your mouse over the moving clown as many times as possible, and thus increase your score. Yes, there is score. If there wasn't a score, it wouldn't really be a game. Each time you successfully catch the clown, he moves faster.
http://dl.dropbox.com/u/9975312/Games/Catch_the_Clown.gmk
~5 KB
Working since ENIGMA SVN Revision 244. Still working great since the move to GIT and since revision 4900aa6.
Coded entirely in LGM. Sprites stolen from the original.
Can you beat my highscore (in the screenshot)?
Features:
Sprites, Movement, Increasing difficulty, random redirection, changing background colors, bouncing off walls, able to be caught my mouse-over, score, displaying score in title bar
Lacking (due to limitations of Enigma at this time):
Clicking, Backgrounds, Sounds/Music
Version 1, which was created prior to sprite support (by showing a circle, without movement) is still available for reference.
http://www.IsmAvatar.com/other/mouse_to_ball.gm6
34
Announcements / Trunkification (svn rearranged)
« on: November 29, 2009, 03:15:02 pm »
For those of you who have been keeping up with or checking out from the SVN (all 3 of you...), as of r51 there's been a small change which should be a welcoming move to anyone who's ever used SVN before. We've split Enigma up into trunk, tags, and branches.
This move came after we realized that serprex was apparently trying to create a branch but we didn't have the t/t/b structure in place.
What this means:
> If you don't use the SVN, this means nothing to you.
> If you checked out from the SVN already and do a regular svn update or svn commit, you will need to do a one-time svn switch
> svn switch https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/trunk
> If you wish to check out a fresh copy of enigma from the SVN, you'll need to append /trunk to the URL.
> svn co https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/trunk enigma-dev
> If you wish to work on or check out the branch that serprex seems to want to work on, you can do an svn switch to the branch:
> svn switch https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/branch/enigma-dev
What are branches, tags, and trunk?
Developers sometimes like to copy the entire project to a few locations so they can keep backups or work on changes without screwing up other parts.
A Tag is a stable copy. This is usually used to tag releases and betas with specific revisions. There can be multiple tags, and they are usually pretty stable, and usually don't change.
A Trunk is the main copy. This is where all the main development goes on. There is only one trunk, and it is moderately stable/unstable. Usually for stable versions, you will be recommended to a specific revision number.
A Branch is a specific development copy. When someone wants to try an experiment or implement a new big feature, they will oftentimes create a branch and work on it there, so that they don't disturb the main development (trunk) with their changes until they are done, and they merge it back with the trunk. There can be multiple branches going on at once, and they are usually quite unstable.
More advanced things:
> Creating new branches, or merging the existing branch back with the original project, should be as simple as calls to svn copy and svn merge, respectively. The SVN Book should be a handy resource here, particularly the chapter on Branching and Merging:
> http://svnbook.red-bean.com/en/1.0/ch04.html
These changes and their explanations courtesy of
-IsmAvatar
This move came after we realized that serprex was apparently trying to create a branch but we didn't have the t/t/b structure in place.
What this means:
> If you don't use the SVN, this means nothing to you.
> If you checked out from the SVN already and do a regular svn update or svn commit, you will need to do a one-time svn switch
> svn switch https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/trunk
> If you wish to check out a fresh copy of enigma from the SVN, you'll need to append /trunk to the URL.
> svn co https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/trunk enigma-dev
> If you wish to work on or check out the branch that serprex seems to want to work on, you can do an svn switch to the branch:
> svn switch https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev/branch/enigma-dev
What are branches, tags, and trunk?
Developers sometimes like to copy the entire project to a few locations so they can keep backups or work on changes without screwing up other parts.
A Tag is a stable copy. This is usually used to tag releases and betas with specific revisions. There can be multiple tags, and they are usually pretty stable, and usually don't change.
A Trunk is the main copy. This is where all the main development goes on. There is only one trunk, and it is moderately stable/unstable. Usually for stable versions, you will be recommended to a specific revision number.
A Branch is a specific development copy. When someone wants to try an experiment or implement a new big feature, they will oftentimes create a branch and work on it there, so that they don't disturb the main development (trunk) with their changes until they are done, and they merge it back with the trunk. There can be multiple branches going on at once, and they are usually quite unstable.
More advanced things:
> Creating new branches, or merging the existing branch back with the original project, should be as simple as calls to svn copy and svn merge, respectively. The SVN Book should be a handy resource here, particularly the chapter on Branching and Merging:
> http://svnbook.red-bean.com/en/1.0/ch04.html
These changes and their explanations courtesy of
-IsmAvatar
35
General ENIGMA / SourceForge updates
« on: October 08, 2009, 04:31:37 pm »
As of this posting, Enigma is hosted on SourceForge.
Recently, SourceForge added OpenID support, and just today they released GoogleID support. Which means that for those of you who have an account at google or gmail, that is your GoogleID.
I think I screwed up, because it's not working quite right for me.
Anyways, this is exciting news for anyone who's been following OpenID.
Recently, SourceForge added OpenID support, and just today they released GoogleID support. Which means that for those of you who have an account at google or gmail, that is your GoogleID.
I think I screwed up, because it's not working quite right for me.
Anyways, this is exciting news for anyone who's been following OpenID.
36
Issues Help Desk / Enigma returns "3"? Solved
« on: April 07, 2008, 09:43:24 pm »
What does Error Code 3 mean?
Quote
Compiling with G:\ENIGMA\compileEGMf.exe
Compiler threw an error code: 3
37
General ENIGMA / Version Numbering
« on: April 07, 2008, 11:33:14 am »
I'm not sure what "standard" you're using that you've decided to name it "alpha 1 revision 1"
Why don't you go with the dot notation that everyone else seems to be using.
major.minor[.build[.revision]]
For example, LGM is 1.5.7.1 (or .2 is what I named the version I gave josh for Enigma, although it's not a real LGM release), that means Major 1, Minor 5, build 7, revision 1.
So you could call it
0.1.1 or 1.0.1 or 1.1, or even if you consider it really really minor, 0.1.0.1 or 1.0.0.1
http://en.wikipedia.org/wiki/Versioning#Numeric
Why don't you go with the dot notation that everyone else seems to be using.
major.minor[.build[.revision]]
For example, LGM is 1.5.7.1 (or .2 is what I named the version I gave josh for Enigma, although it's not a real LGM release), that means Major 1, Minor 5, build 7, revision 1.
So you could call it
0.1.1 or 1.0.1 or 1.1, or even if you consider it really really minor, 0.1.0.1 or 1.0.0.1
http://en.wikipedia.org/wiki/Versioning#Numeric