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.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 »
2101
Announcements / Re: Things that are broke
« on: April 16, 2010, 07:58:40 am »
The 11th plague of Egypt:
Good point. That was my bad.
The command line is
svn co https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev enigma-dev
That line will invoke SVN to download ENIGMA for you in its entirety, except libzlib.a, which I provided by URL. If you downloaded RapidSVN, its interface will be a little easier. Go to the Repository menu, and select Checkout. Provide the URL https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev, and specify where you want it downloaded.
It is ultimately best if you run it from terminal, as that will provide useful debug info.
Good point. That was my bad.
The command line is
svn co https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev enigma-dev
That line will invoke SVN to download ENIGMA for you in its entirety, except libzlib.a, which I provided by URL. If you downloaded RapidSVN, its interface will be a little easier. Go to the Repository menu, and select Checkout. Provide the URL https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev, and specify where you want it downloaded.
It is ultimately best if you run it from terminal, as that will provide useful debug info.
2102
Announcements / Re: Things that are broke
« on: April 16, 2010, 07:00:48 am »
Freezway--
Your latest problem seems to be that, although the parse completed successfully, it entirely missed sprite functions. I will devise something to display a list of all available functions, if Ism will implement GM's button for it (Sorry Ism, you'll have to create a windowed text box again if we're to get this piece of information).
When you are ready, Ism, I will implement these:
And yes, Ism, I know we're in dire need of better coordination, but the people here most inclined to be as coordinated as you and I right off the bat all have computers that just run ENIGMA and LGM, and run them well. I can tell from the output messages what's wrong with the project, so I don't need to distribute a test game to make them run.
Your latest problem seems to be that, although the parse completed successfully, it entirely missed sprite functions. I will devise something to display a list of all available functions, if Ism will implement GM's button for it (Sorry Ism, you'll have to create a windowed text box again if we're to get this piece of information).
When you are ready, Ism, I will implement these:
Code: [Select]
const char* first_available_resource(); //Returns the name of the first resource on the list, or "" otherwise.
bool resource_isFunction(); //Returns whether the resource can be called as a function
int resource_argCountMin(); //Returns the minimum number of arguments to the function; the names cannot be fetched.
int resource_argCountMax(); //Returns the maximum number of arguments to the function; again, the names cannot be fetched.
bool resource_isTypeName(); //Returns whether the resource can be used as a typename.
bool resource_isGlobal(); //Returns whether the resource is nothing but a global variable.
const char* next_available_resource(); //Returns the name of the next resource on the list, or "" otherwise.
bool resources_atEnd(); //Returns whether we're really done iterating the list
And yes, Ism, I know we're in dire need of better coordination, but the people here most inclined to be as coordinated as you and I right off the bat all have computers that just run ENIGMA and LGM, and run them well. I can tell from the output messages what's wrong with the project, so I don't need to distribute a test game to make them run.
2103
Announcements / Re: Things that are broke
« on: April 15, 2010, 10:21:53 pm »Please be aware that SourceForge is undergoing upgrade work April 17th and 18th between 0500 and 1300 UTC. All components of the site are down except for the external file mirrors. This includes all SVN repositories. You can follow the site status through their website here or through @sfnet_ops -a2h
Procedure in general is as follows: (Subject to revision; pay attention)
Note: This is only for people who wish to test but do not wish to wait for "stable test," meaning "at least moderately workable pile of fail."
IRC Channel
ENIGMA has an IRC channel set up on Freenode. Predictably, it is called #enigma-dev. This link may take you there.
Revision 4.1 - Added a Linux dependency.
Revision 4.2 - Added note about running LGM from terminal
Revision 4.3 - Added Java Linux package name for the sake of sanity
Dependencies
If you are on Windows, do the following:
- Install an SVN client (either the command line version, or a visual one like RapidSVN or Tortoise)
- Install Code::Blocks ( www.codeblocks.org )
- After checking out the SVN (see "Getting ENIGMA"), Copy this to ENIGMAsystem/additional/zlib/: http://dl.dropbox.com/u/1052740/libzlib.a
If you are on Linux, you will need the following packages:
- g++
- libgl1-mesa-dev (or similar)
- zlib1g-dev (SHOULD be installed already, but Ism's wasn't)
- codeblocks
- svn / rapidsvn / tortoise
- Java (I -strongly- recommend sun-java6-jre)
Getting ENIGMA to Work
Getting ENIGMA
-Check out the SVN repository via the most applicable of the following:
---From command line, you will use svn co https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev enigma-dev )
---From RapidSVN, go to the Repository menu, and select Checkout. Provide the URL https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev, and specify where you want it downloaded.
-The above will begin downloading ENIGMA. Let it finish.
-Go to ./trunk/
-Go to ./CompilerSource/
-Open the Code::Blocks project. Find the drop down box that likely reads "Release." If you're on Linux, set it to "Release-Linux."
-Hit compile (blue gear)
-Done, go back up to Trunk
Running ENIGMA Itself (LGM)
-Run LateralGM, best done with a terminal via "java -jar lateralgm16b4.jar" -- This terminal should have +++++++++++++ at the bottom.
---If it does not, or if that errors, paste output here.
------If the terminal errors that java is not a valid application, then you are on Windows.
------Find "java.exe" and add its directory to your PATH variable from the control panel.
-Make something simple (like a single object drawing a graded circle; that's what I've been using as a preliminary test)
-Under the "Enigma" menu, hit "Run"
-Check the terminal window (the one I hope you used to run LGM) for syntax errors.
---If there is one that you don't think is correct, post it here. (I'm currently developing the syntax checker).
-Your code has now been secretly translated to C++ behind your back.
Testing the Game You Just "Ran"
-Open trunk/ENIGMAsystem/SHELL/ENIGMAengine.cbp in Code::Blocks
-Select your OS from the dropdown box once more (Debug is faster to build, release will run fastest)
-Press Compile
---If anything errors and you think you followed the above correctly, right click the error list, select "Copy Contents to Clipboard," and paste them all here.
-Press run.
---If it doesn't behave as expected, describe what went wrong here
What now?
Repeat the step starting at "Make something simple" until you're sick of finding bugs.
The most immediate concern is that everyone can achieve a simple circle.
Common Errors
ENIGMA
error: ‘instdata’ was not declared in this scope
--This means you did not actually create a game from LGM (By clicking "Run") before trying to compile it, the compile failed due to syntax errors, or you restarted LGM in the meantime. It isn't really an error.
LateralGM
- SvnKit missing, corrupted, or unusable. Please download and place next to the enigma plugin in order to enable auto-update.
---This is not an error. It is a warning thrown by Enigma.jar, warning you that it's not able to update itself if you don't have SvnKit. Of course, Enigma doesn't need to update itself.
- Unable to load plugin: SvnKit.jar: null: Missing plugin entry point (LGM-Plugin)
- Unable to load plugin: jna.jar: null: Missing plugin entry point (LGM-Plugin)
---These are not errors. They are warnings thrown by LGM indicating that it can't load those files as LGM Plugins -- because they *aren't* LGM Plugins! Basically these are just reminders to the devs that we shouldn't just throw every darned file we need access to in the Plugins folder >_<
2104
Announcements / Things that are broke
« on: April 15, 2010, 10:20:20 pm »
Those who have checked out the repository and began testing can continue reporting things here.
Presently, the project is torn between platforms, and is in what I would call a pretty pathetic state.
So far this phase, I cannot say "what works, works well." Most of the previous releases, not a lot worked, but what did was at least mostly reliable. This time, I couldn't even get it compiling on multiple platforms right away due to the insane amount of differences between each. Removing hard-coded features has proven to make the project very needy; not to mention LGM also seems to be in a worse state than last release.
What I'm coping/dealing with now:
- ENIGMA freezes/LGM segfaults on some 64bit machines (likely the ones such that sizeof(size_t) isn't matching up with another aliased size; segfault may be due to JNA's sizes not matching up with C++'s after all). Freezway has basically confirmed it is a problem with 64bit systems, as it worked fine on a 32bit version of the same OS.
- LGM's code editor is even worse on Linux; it misaligns text with cursor when keywords/comments are italicized. Not to mention on this box, Java is slower than all beans. Over all, I'm deeming it 'half a head of hair short of unusable;' but the latter half of my hair should be ripped out by tomorrow evening.
- Allocations on this box (Ubuntu) are ridiculously slow, and I have reason to believe that the frame timing mechanism is FUBAR. I will investigate thoroughly when some other problems are resolved. The reason I believe it is the allocation is that the framerate resumes full speed (if chopped) when an instance is destroyed before each new one is created (Meaning the program doesn't have to dig for more space before allocating some).
Does anyone know of a flag for fast, careless allocations?
If those don't seem like big problems to you, I want you to counsel me.
Other than that though, the project is great, thanks for asking. <_<"
Again, following this post are the instructions (still subject to change) for checking out and testing ENIGMA. You will have to follow these in order to test until I deem that the project is stable enough to distribute zipped (aka, when those above errors are corrected--at least ENIGMA's).
As for me, I have a lot of math homework. I will devote the first half of tomorrow to that, and then I will be done for a little until I have to write a fifteen-page essay on Scientology, which I must say I am not looking forward to.
Presently, the project is torn between platforms, and is in what I would call a pretty pathetic state.
So far this phase, I cannot say "what works, works well." Most of the previous releases, not a lot worked, but what did was at least mostly reliable. This time, I couldn't even get it compiling on multiple platforms right away due to the insane amount of differences between each. Removing hard-coded features has proven to make the project very needy; not to mention LGM also seems to be in a worse state than last release.
What I'm coping/dealing with now:
- ENIGMA freezes
- LGM's code editor is even worse on Linux; it misaligns text with cursor when keywords/comments are italicized. Not to mention on this box, Java is slower than all beans. Over all, I'm deeming it 'half a head of hair short of unusable;' but the latter half of my hair should be ripped out by tomorrow evening.
- Allocations on this box (Ubuntu) are ridiculously slow, and I have reason to believe that the frame timing mechanism is FUBAR. I will investigate thoroughly when some other problems are resolved. The reason I believe it is the allocation is that the framerate resumes full speed (if chopped) when an instance is destroyed before each new one is created (Meaning the program doesn't have to dig for more space before allocating some).
Does anyone know of a flag for fast, careless allocations?
If those don't seem like big problems to you, I want you to counsel me.
Other than that though, the project is great, thanks for asking. <_<"
Again, following this post are the instructions (still subject to change) for checking out and testing ENIGMA. You will have to follow these in order to test until I deem that the project is stable enough to distribute zipped (aka, when those above errors are corrected--at least ENIGMA's).
As for me, I have a lot of math homework. I will devote the first half of tomorrow to that, and then I will be done for a little until I have to write a fifteen-page essay on Scientology, which I must say I am not looking forward to.
2105
Announcements / Re: Anaphase
« on: April 15, 2010, 08:03:24 pm »
Wonder if it incorrectly passes resource data as a result, causing your segfault. I can't be certain at this point. Have some other things to debug; hopefully I can soon reproduce that error.
It may also result from JNA's types versus C++'s, as I was worried about long ago... Ism assured me they were kept the same, but...
It may also result from JNA's types versus C++'s, as I was worried about long ago... Ism assured me they were kept the same, but...
2106
Announcements / Re: Anaphase
« on: April 15, 2010, 06:16:26 am »
freezway--
The ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ means it was successful. Running from LGM won't build the exe since the makefile isn't written; you'll have to build with Code::Blocks after you hit run.
I will add -fPIC to the Linux target. I don't understand why yours was the only one that complained about it.
The ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ means it was successful. Running from LGM won't build the exe since the makefile isn't written; you'll have to build with Code::Blocks after you hit run.
I will add -fPIC to the Linux target. I don't understand why yours was the only one that complained about it.
2107
Announcements / Re: Anaphase
« on: April 14, 2010, 09:15:56 pm »
Resolved: Replaced pertinent instances of size_t and unsigned with "pt," typedefed as the former.
Re-check out if this affects you.
Re-check out if this affects you.
2108
Announcements / Re: Anaphase
« on: April 14, 2010, 07:58:45 pm »
Procedure in general is as follows: (Subject to revision; pay attention)
Revision 0
-Have Code::Blocks and some SVN client, or a whole lot of creativity.
-Check out the SVN repository (from command line, use svn co https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev enigma-dev )
-Go to Trunk
-Go to CompilerSource
-Open the Code::Blocks project. Find the dropdown that likely reads "release." If you're on Linux, set it to "Release-Linux"
-Hit compile (blue gear)
-Go back up to Trunk
-Run LateralGM, best with a terminal via "java -jar lateralgm16b4.jar"
---If that errors, paste output here
-Make something simple (just a single object drawing a graded circle is what I've been using as a preliminary)
-Under the "Enigma" menu, hit "Run"
-Open trunk/ENIGMAsystem/SHELL/ENIGMAengine.cbp
-Select your OS from the dropdown box once more (Debug is faster to build, release will run fastest)
-Press Compile
---If anything errors and you think you followed the above correctly, right click the error list, select "Copy Contents to Clipboard," and paste them all here.
-Press run.
---If it doesn't behave as expected, describe what went wrong here
Repeat the step starting at "Make something simple" until you're sick of finding bugs.
The most immediate concern is that everyone can achieve a simple circle.
Revision 0
-Have Code::Blocks and some SVN client, or a whole lot of creativity.
-Check out the SVN repository (from command line, use svn co https://enigma-dev.svn.sourceforge.net/svnroot/enigma-dev enigma-dev )
-Go to Trunk
-Go to CompilerSource
-Open the Code::Blocks project. Find the dropdown that likely reads "release." If you're on Linux, set it to "Release-Linux"
-Hit compile (blue gear)
-Go back up to Trunk
-Run LateralGM, best with a terminal via "java -jar lateralgm16b4.jar"
---If that errors, paste output here
-Make something simple (just a single object drawing a graded circle is what I've been using as a preliminary)
-Under the "Enigma" menu, hit "Run"
-Open trunk/ENIGMAsystem/SHELL/ENIGMAengine.cbp
-Select your OS from the dropdown box once more (Debug is faster to build, release will run fastest)
-Press Compile
---If anything errors and you think you followed the above correctly, right click the error list, select "Copy Contents to Clipboard," and paste them all here.
-Press run.
---If it doesn't behave as expected, describe what went wrong here
Repeat the step starting at "Make something simple" until you're sick of finding bugs.
The most immediate concern is that everyone can achieve a simple circle.
2109
Announcements / Re: Anaphase
« on: April 14, 2010, 07:33:00 pm »
Anyone that would like to test at this point can checkout the SVN and operate the project. Windows users will need a copy of libzlib, available here:
http://dl.dropbox.com/u/1052740/libzlib.a
Place that in additional/zlib if you're on Windows, otherwise Code::Blocks will know what to do if you select the correct build target.
Furthermore, no one I've talked to is proficient enough in Make to write a makefile taking parameters to indicate which graphics system and window system to use (Like GRAPHICS=GL, or just _ instead of = if need be). That being the case, either write one and post it here, (specifying systems is as simple as selecting which directories to iterate for sources), or you can join everyone else and test it by pressing Run in ENIGMA, then building the game in Code::Blocks (from ENIGMAsystem/SHELL/ENIGMAengine.cbp). You must hit "Run" in ENIGMA first, or your sources will not be authored.
Furthermore, instance_create is behaving very slowly on Ubuntu when an instance has not been recently destroyed. This indicates to me that allocation of memory for the new instance is painfully slow for one reason or another. I'm looking into the problem; it could be anything.
So yes, if you're intelligent enough to get what's available working for you, please feel free. If you're not, or would prefer not to anyway, just wait until ENIGMA's to the developers' liking (That includes Ism and me).
http://dl.dropbox.com/u/1052740/libzlib.a
Place that in additional/zlib if you're on Windows, otherwise Code::Blocks will know what to do if you select the correct build target.
Furthermore, no one I've talked to is proficient enough in Make to write a makefile taking parameters to indicate which graphics system and window system to use (Like GRAPHICS=GL, or just _ instead of = if need be). That being the case, either write one and post it here, (specifying systems is as simple as selecting which directories to iterate for sources), or you can join everyone else and test it by pressing Run in ENIGMA, then building the game in Code::Blocks (from ENIGMAsystem/SHELL/ENIGMAengine.cbp). You must hit "Run" in ENIGMA first, or your sources will not be authored.
Furthermore, instance_create is behaving very slowly on Ubuntu when an instance has not been recently destroyed. This indicates to me that allocation of memory for the new instance is painfully slow for one reason or another. I'm looking into the problem; it could be anything.
So yes, if you're intelligent enough to get what's available working for you, please feel free. If you're not, or would prefer not to anyway, just wait until ENIGMA's to the developers' liking (That includes Ism and me).
2110
General ENIGMA / Re: ENIGMA on iPhone - Now legally impossible
« on: April 12, 2010, 10:51:10 pm »
"Unless you have to agree to some contract/EULA/something before using that phone. Then yes."
Fair use.
Fair use.
2111
Off-Topic / Re: Stencyl
« on: April 12, 2010, 06:07:12 pm »
Yep. No one's given them more heat than Luda and I for their... "unique" ideology. Especially in the sense that their website is the best feature of their software. ...
But yeah, I figure I'll leave critiquing them to people who actually care to test their software for the rest of their development.
But yeah, I figure I'll leave critiquing them to people who actually care to test their software for the rest of their development.
2112
Off-Topic / Re: Stencyl
« on: April 12, 2010, 04:20:27 pm »
Anyone care to "Join the Beta" and share thoughts?
2113
General ENIGMA / Re: ENIGMA on iPhone - Now legally impossible
« on: April 12, 2010, 04:14:13 pm »
"If apple wants to restrict who can put apps on their iPhone, it's their right."
On their store, yes. On their phone, no.
On their store, yes. On their phone, no.
2114
General ENIGMA / Re: ENIGMA on iPhone - Now legally impossible
« on: April 11, 2010, 09:47:00 pm »
"So what Apple does not want is for some other company to establish a de facto standard software platform on top of Cocoa Touch. Not Adobe’s Flash. Not .NET (through MonoTouch). If that were to happen, there’s no lock-in advantage. If, say, a mobile Flash software platform — which encompassed multiple lower-level platforms, running on iPhone, Android, Windows Phone 7, and BlackBerry — were established, that app market would not give people a reason to prefer the iPhone."
"We think John Gruber’s post is very insightful and not negative: ...
Steve"
Sounds like Noodle was right, to me.
Anyway, yes, ENIGMA clearly meets the definition of what they're trying to outlaw, but I believe you'll soon find that just because a wanna-be big, bad corporation wants to outlaw something, doesn't mean they're going to manage it. Take Yoyo's EULA as an example, not that I would suggest any of those morons have half the legal prowess of Apple. That said, however, what we have here seems to be a case of "Same shit, different company."
"We think John Gruber’s post is very insightful and not negative: ...
Steve"
Sounds like Noodle was right, to me.
Anyway, yes, ENIGMA clearly meets the definition of what they're trying to outlaw, but I believe you'll soon find that just because a wanna-be big, bad corporation wants to outlaw something, doesn't mean they're going to manage it. Take Yoyo's EULA as an example, not that I would suggest any of those morons have half the legal prowess of Apple. That said, however, what we have here seems to be a case of "Same shit, different company."
2115
General ENIGMA / Re: ENIGMA on iPhone - Now legally impossible
« on: April 11, 2010, 07:17:54 pm »
"In software engineering, a compatibility layer allows binaries for a legacy or foreign system to run on a host system."
That means WINE and the like. ENIGMA selects native code, and then compiles it natively. If anything, you should be arguing that it's a tool for "intermediary translation."
However, that particular clause illegalizes... practically everything.
That means WINE and the like. ENIGMA selects native code, and then compiles it natively. If anything, you should be arguing that it's a tool for "intermediary translation."
However, that particular clause illegalizes... practically everything.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 »