Show Posts
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 »
226
Issues Help Desk / Re: Help With Installation Requested
« on: February 25, 2012, 05:53:35 pm »
HaRRiKiRi: the two pages are exactly the same. http://enigma-dev.org/download.htm uses the Wiki API to query http://enigma-dev.org/docs/Wiki/Install and display the contents (Wiki/Installation redirects to Wiki/Install). All links and content on all 3 of those pages will always be exactly the same. Update one (namely Wiki/Install), and the other 2 automatically update.
I have not read the rest of this topic yet. Just wanted to point that out.
Also, why are you unable to post in the Help Desk Section?
I have not read the rest of this topic yet. Just wanted to point that out.
Also, why are you unable to post in the Help Desk Section?
227
Off-Topic / Re: Introductions
« on: February 24, 2012, 08:28:35 pm »
Welcome to the project. I hope we can help you resolve your installation issues. We've been having a few of them latetly, so we've been spending some time trying to improve the process so it goes more smoothly in the future. It's to be expected, since the project isn't really done yet. But it's still *very* usable. Many users have already created a good number of games and even submitted them to some Game Maker competitions.
228
Announcements / Re: Main Progress [Stalled because we can't Git]
« on: February 24, 2012, 05:44:52 pm »
The awkwardness comes from the use of the word "things". Usually, "things" refers to a everything that you would usually use. Here, though, "things" actually refers to "the things that we keep running into". Basically, it's a difference between things = "everything" and things = "some things".
The point he was trying to make was that, for the purposes that we keep running into, GIT has a clear advantage. Whereas SVN "just works" and git is more complex (or steeper learning curve), once you get the hang of Git (which we have quickly done, since it was suddenly dumped on us, along with the help of those 1 or 2 wonderful git tutorials shared in the other topic), it's the clear winner, providing elegant solutions to things that we hacked around in SVN in the past - such as subprojects and forks.
And all this, considering that I was a diehard SVN fan, with a little loathing for the complexity (and documentation overflow) of git. Now I've converted pretty much all of my projects to Git. Read the tutorials from the other topic, and it's really not that much of a hastle after all.
EGit, on the other hand... that thing was a bugger to figure out.
Our current issue isn't so much that we can't Git (I just put that in the title to be funny), it's that we don't really understand the intent that Rusky was going with in deleting some of the stuff from the repository, and then he suddenly left, so now we kinda have to pick up his pieces. We've done fairly well, as you can see from this topic. Current issue is just the alure sound system, which he deleted, even though it was clearly modified from alure, so we don't have a clue what he did that for.
The point he was trying to make was that, for the purposes that we keep running into, GIT has a clear advantage. Whereas SVN "just works" and git is more complex (or steeper learning curve), once you get the hang of Git (which we have quickly done, since it was suddenly dumped on us, along with the help of those 1 or 2 wonderful git tutorials shared in the other topic), it's the clear winner, providing elegant solutions to things that we hacked around in SVN in the past - such as subprojects and forks.
And all this, considering that I was a diehard SVN fan, with a little loathing for the complexity (and documentation overflow) of git. Now I've converted pretty much all of my projects to Git. Read the tutorials from the other topic, and it's really not that much of a hastle after all.
EGit, on the other hand... that thing was a bugger to figure out.
Our current issue isn't so much that we can't Git (I just put that in the title to be funny), it's that we don't really understand the intent that Rusky was going with in deleting some of the stuff from the repository, and then he suddenly left, so now we kinda have to pick up his pieces. We've done fairly well, as you can see from this topic. Current issue is just the alure sound system, which he deleted, even though it was clearly modified from alure, so we don't have a clue what he did that for.
229
General ENIGMA / Re: ENIGMA IS A MAZE
« on: February 24, 2012, 05:28:30 pm »
Oh yeah, I forgot that Windows does the goofy WinMain thing. Xlib/Linux still uses main() though. Understanding the ordering of things there really just depends on understanding the underlying library - windows.h or X. It's not really our fault if those systems are a maze :-p
230
General ENIGMA / Re: ENIGMA IS A MAZE
« on: February 22, 2012, 11:38:04 pm »
Ah, in that case, you're dealing with platform-specific code, since we generate platform-specific exes (or elfs or apps), and initialization sets up platform-specific things (like the window). As you can probably figure out from the wiki, ENIGMAsystem/SHELL houses the game code. From there, logically, you would look in Platforms for platform specific code, and then identify your platform, and then seek out the respective main.cpp (Josh points them out).
Hope that helps.
Hope that helps.
231
General ENIGMA / Re: ENIGMA IS A MAZE
« on: February 22, 2012, 03:01:00 pm »
main() is a method for programs that compile into an exe. ENIGMA is a dll. DLLs have multiple external functions that another program will call. These are usually marked as `extern "C"`. In ENIGMA, we have a macro defining `dllexport` to the appropriate export flags. The main ones are defined in CompilerSource/main.cpp.
For an overview of the dll-exported functions, please see the Driver wiki page: http://enigma-dev.org/docs/Wiki/EnigmaDriver as well as the more general Backend page which covers everything lower-level from the Plugin's side: http://enigma-dev.org/docs/Wiki/Backend
For an overview of the dll-exported functions, please see the Driver wiki page: http://enigma-dev.org/docs/Wiki/EnigmaDriver as well as the more general Backend page which covers everything lower-level from the Plugin's side: http://enigma-dev.org/docs/Wiki/Backend
232
Announcements / Re: Main Progress [Stalled because we can't Git]
« on: February 20, 2012, 12:33:48 am »
I've added this section of the wiki, which should be enough to get things working:
http://enigma-dev.org/docs/Wiki/Install:Git#Additional_Dependencies
Those are the latest versions of LGM (JoshEdit branch), the Plugin, and JNA as of tonight. They can be interchanged with any compatible versions (some users have already been able to get it working by just using the jars from the last SVN revision, albeit obviously outdated now).
I have tested it and can confirm I can get a basic game running on Linux, provided you switch the Audio system to None (Enigma's OAL system is currently broken). Users have reported that Windows is currently broken (Also seems to be OAL-related - at any rate, not my fault, it seems). Also, it defaults to Clang on linux, which may or may not be your desired default - it worked fine for me, as did GNU GCC G++.
So, dev team, go.
http://enigma-dev.org/docs/Wiki/Install:Git#Additional_Dependencies
Those are the latest versions of LGM (JoshEdit branch), the Plugin, and JNA as of tonight. They can be interchanged with any compatible versions (some users have already been able to get it working by just using the jars from the last SVN revision, albeit obviously outdated now).
I have tested it and can confirm I can get a basic game running on Linux, provided you switch the Audio system to None (Enigma's OAL system is currently broken). Users have reported that Windows is currently broken (Also seems to be OAL-related - at any rate, not my fault, it seems). Also, it defaults to Clang on linux, which may or may not be your desired default - it worked fine for me, as did GNU GCC G++.
So, dev team, go.
233
Announcements / Re: Main Progress [Stalled because we can't Git]
« on: February 19, 2012, 01:17:18 am »
Good news: I got everything hooked together using the latest revisions of everything.
Current hold-up: LGM and enigma.jar are currently incompatible due to like 7 lines of code that reference systems that have changed in LGM (namely, Listener and JoshEdit).
Tomorrow, I'll fix that, and then build some binaries, and then get the ball rolling in the Dev department again (assuming I have correctly guessed what Rusky and RetroX had in mind). If this works, we'll start automating this build process (probably via EnigmaBot) and then Dev will be magical with free rainbows and tacos for everyone again.
Inb4 I get kidnapped tomorrow.
Current hold-up: LGM and enigma.jar are currently incompatible due to like 7 lines of code that reference systems that have changed in LGM (namely, Listener and JoshEdit).
Tomorrow, I'll fix that, and then build some binaries, and then get the ball rolling in the Dev department again (assuming I have correctly guessed what Rusky and RetroX had in mind). If this works, we'll start automating this build process (probably via EnigmaBot) and then Dev will be magical with free rainbows and tacos for everyone again.
Inb4 I get kidnapped tomorrow.
234
Announcements / Re: Main Progress [Stalled because we can't Git]
« on: February 11, 2012, 09:58:46 pm »
DarkAceZ: A large part of that is because they all pretty much just link to the old Install:SVN page, meaning that they only get as up-to-date as the SVN gets (which hasn't been updated since we started using Git, because all our commits have gone to git instead). When Install:Git is working, they will probably instead be directed to point at that (short term, until we get linux packages going).
235
Announcements / Main Progress [Stalled because we can't Git]
« on: February 11, 2012, 07:21:46 pm »
Just wanted to let you all in on a little update since we have moved to Git.
Rusky and RetroX have been infinitely helpful in getting us all up-to-speed in how-to-git, as well as getting the git in a semi-desirable state. That said, though, our git professionals seem to have been stretched to their capacities, so our developers are having a little bit of trouble figuring out how to install/build the latest ENIGMA rev from scratch. We're basically just waiting on our Git pros to update this page for us: http://enigma-dev.org/docs/Wiki/Install:Git ... Namely, lgm16b4.jar and enigma.jar were (intentionally) omitted from the repository, which makes it very difficult to run, because not just any version of those jars will work.
In the meantime, progress has been largely disjointed. For instance, Josh and I have been tweaking JoshEdit (which has its own git that we do know how to work). Josh also continues work on his new One Parser To Rule Them All. I've been catching up on other items on my Todo list, and will probably be working on some much needed upgrades to LGM's Room Editor soon. I've also figured out how to get EGit working in Eclipse, so I've been switching all my projects over that already use git. The IRC Bot has gotten several very nice updates to make understanding git revisions easier and such. There's been some slightly renewed interest in JEIE, so I might poke at that a little bit (at this point, the core is all there, it just needs a UI). TGMG has reported that 90% of the 64digits examples compile (with a blank function template for all currently unimplemented functions - primarily intended to test the compiler/parser), so that's always nice.
So that's why ENIGMA progress seems to have slowed to a crawl and no new builds are being made available - because we don't know how. But a lot of the side-branches are being filled in, so I expect that once we do figure out how, progress will explode. Until then, if you're looking for progress, look at the border projects, like JoshEdit and EnigmaBot and such.
For those of you trying to just do a standard install for using ENIGMA, you should be able to follow the normal Install page, which will give you one of the most recent builds we could get our hands on, with automatic updates disabled (which will probably be the norm from now on)
Rusky and RetroX have been infinitely helpful in getting us all up-to-speed in how-to-git, as well as getting the git in a semi-desirable state. That said, though, our git professionals seem to have been stretched to their capacities, so our developers are having a little bit of trouble figuring out how to install/build the latest ENIGMA rev from scratch. We're basically just waiting on our Git pros to update this page for us: http://enigma-dev.org/docs/Wiki/Install:Git ... Namely, lgm16b4.jar and enigma.jar were (intentionally) omitted from the repository, which makes it very difficult to run, because not just any version of those jars will work.
In the meantime, progress has been largely disjointed. For instance, Josh and I have been tweaking JoshEdit (which has its own git that we do know how to work). Josh also continues work on his new One Parser To Rule Them All. I've been catching up on other items on my Todo list, and will probably be working on some much needed upgrades to LGM's Room Editor soon. I've also figured out how to get EGit working in Eclipse, so I've been switching all my projects over that already use git. The IRC Bot has gotten several very nice updates to make understanding git revisions easier and such. There's been some slightly renewed interest in JEIE, so I might poke at that a little bit (at this point, the core is all there, it just needs a UI). TGMG has reported that 90% of the 64digits examples compile (with a blank function template for all currently unimplemented functions - primarily intended to test the compiler/parser), so that's always nice.
So that's why ENIGMA progress seems to have slowed to a crawl and no new builds are being made available - because we don't know how. But a lot of the side-branches are being filled in, so I expect that once we do figure out how, progress will explode. Until then, if you're looking for progress, look at the border projects, like JoshEdit and EnigmaBot and such.
For those of you trying to just do a standard install for using ENIGMA, you should be able to follow the normal Install page, which will give you one of the most recent builds we could get our hands on, with automatic updates disabled (which will probably be the norm from now on)
236
Announcements / Re: Update
« on: February 01, 2012, 07:00:55 pm »
Is there a like button, so I can like cheeseboy's status?
238
Issues Help Desk / Re: Help getting ENIGMA to behave
« on: January 22, 2012, 02:40:41 am »
The ascii art heaping pile of crap near the beginning indicates that something went wrong while ENIGMA was starting up. Josh will have to take a look at it.
Normally, when you see the ascii pile of crap, it means something went wrong just setting ENIGMA up, and you shouldn't even bother trying to compile/run a game, because it won't work.
The Stack Trace Exception is this: http://enigma-dev.org/docs/Wiki/No_internal_or_system_editor
Normally, when you see the ascii pile of crap, it means something went wrong just setting ENIGMA up, and you shouldn't even bother trying to compile/run a game, because it won't work.
The Stack Trace Exception is this: http://enigma-dev.org/docs/Wiki/No_internal_or_system_editor
239
Announcements / Re: New GitHub Repository
« on: January 15, 2012, 05:38:07 pm »
Thanks to Rusky, we were able to restore many lost svn revisions caused by herp-derping the svn repositories back in the day (adding the trunk/branches/tags folders) and herp-derp-git-importing them without accounting for that. Rusky fixed it, but we had to delete the git repositories and re-create them.
This will probably also mean that those of you who already checked out (cloned) either of the repositories will need to re-clone again, since they both now have a more complete history. Likewise, to anybody who was watching either of the repositories, you will need to re-watch them again.
Hopefully (cross our fingers) this will be the last time we have to do that. I'm sure you all understand - the initial setup/transfer can be a little unstable, but now that we have things going again, it should all be good.
Also, the guide a2h found is amazing. Perfect for my needs.
This will probably also mean that those of you who already checked out (cloned) either of the repositories will need to re-clone again, since they both now have a more complete history. Likewise, to anybody who was watching either of the repositories, you will need to re-watch them again.
Hopefully (cross our fingers) this will be the last time we have to do that. I'm sure you all understand - the initial setup/transfer can be a little unstable, but now that we have things going again, it should all be good.
Also, the guide a2h found is amazing. Perfect for my needs.
240
Announcements / Re: New GitHub Repository
« on: January 13, 2012, 08:22:59 pm »
In addition, LGM is moving to Git as well.
https://github.com/IsmAvatar/LateralGM
EnigmaBot already reflects these changes.
There has still been some debate on what to do with the Auto-Updater, though.
A few pages on the Wiki will probably need to reflect this as well - especially once we figure out what to do with the Auto-Updater.
https://github.com/IsmAvatar/LateralGM
EnigmaBot already reflects these changes.
There has still been some debate on what to do with the Auto-Updater, though.
A few pages on the Wiki will probably need to reflect this as well - especially once we figure out what to do with the Auto-Updater.