ENIGMA Development Environment
Website is in read-only mode due to a recent attack.

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.


Messages - Josh @ Dreamland

1066
Issues Help Desk / Re: Svnkit error/enigma isn't ready yet
« on: May 13, 2012, 11:59:56 AM »
TGMG has it set up and working with Additional/ on Windows, as far as I know.

As for Linux. Ubuntu 10.04 has problems with sound because its Alure libraries are woefully out of date. 12.04 and other up-to-date distros have problems with the parser because I haven't the time to fix it at the moment due to college coursework. If you happen to still have 11.10 or 11.04 installed, just clone the git repository and run TGMG's install.py; it will download LGM and the plugins. Then you'll be good to go.

If his install.py doesn't work, I'll write a bash script to wget the stuff. We've had nothing but installation issues since we switched to Git, since we don't have the ability to upload binaries to it anymore.

1067
Issues Help Desk / Re: Svnkit error/enigma isn't ready yet
« on: May 13, 2012, 12:38:49 AM »
I have updated the link. It should have been http://dl.dropbox.com/u/1052740/ENIGMA-Releases/ENIGMA-R984-SVN.zip.

We are working on a more sophisticated release system for Windows. It is difficult to devise one, since we can not rely on the version control system to store libraries and binaries anymore.

I've all but begged ENIGMA's Windows maintainers to upload their Additional/ folder as a zip archive somewhere, but the request keeps going unnoticed.

1068
Issues Help Desk / Re: Svnkit error/enigma isn't ready yet
« on: May 12, 2012, 10:11:26 PM »
If ENIGMA isn't ready yet, it's likely still being compiled. LGM takes care of that on first run. Give it a bit to finish; check the terminal/console window for output to see if it's doing anything.

As for the SVNkit error, if you used the prepackaged zip, don't worry about it. If that's the case, and you have SVNKit in your plugins folder, just remove it.

1069
Proposals / Re: Options Panel for LGM
« on: May 06, 2012, 09:30:04 PM »
Don't forget the JE options panel. It needs included.

1070
General ENIGMA / Re: Open Pandora Port
« on: May 06, 2012, 09:27:37 PM »
Sure. We could use to know what progress you've had with the compiler portion of it. Do ENIGMA and LateralGM both start up and run okay on Pandora?

1071
Proposals / Re: Options Panel for LGM
« on: May 06, 2012, 08:59:32 AM »
Damn it, polygone.

Anyway, the options panel. Things it should contain.


THE

EXTERNAL

SPRITE

AND

IMAGE

EDITOR

NAMES




Just for a start.

Also, I'd not mind theme information, if that's not too tricky. You know, Windows look and feel shit.

1072
Proposals / Re: LGM Automatic Saving
« on: May 03, 2012, 09:25:38 AM »
Whoa. Who said anything about temp?  And who said anything about backups?
An autosaved file belongs in ~/.programname, or %APPDATA%/programname. I am certain Java has a feature to fetch that.
If you want the files to be "temporary," then put them in ~/.lgm/temp. Clean out that folder on confirmed, successful exit (meaning not when LGM just dies because the user pressed X).

On launch, if the folder is not empty, ask the user "Would you like to restore...?" and display a list, like Firefox and OOo do. Emphasis on OOo. The Java one.

If you're not going to prompt for close on pressing X, IsmAvatar, it might be a good idea to autosave before you unceremoniously exit.

1073
Proposals / Re: LGM Automatic Saving
« on: May 01, 2012, 12:21:36 AM »
Often, IsmAvatar, it's every N minutes. The storage is a trickier problem, since LGM doesn't create a ~/.lgm (or AppData folder on Windows).

1074
Issues Help Desk / Re: file_exists() doesn't work in Linux???
« on: May 01, 2012, 12:19:22 AM »
It probably hasn't been implemented. It's as simple as this:

Code: (C++) [Select]
#include <unistd.h>
#include <sys/stat.h>
bool file_exists(string file) {
  stat sb;
  return stat(file.c_str(), &sb) >= 0;
}

1075
Issues Help Desk / Re: Missing 'Make' file
« on: April 30, 2012, 02:18:08 PM »
Strange... I will have to change that CreateProcess wrapper to go through bash, then, I guess. It's strange; having those two directories in your system path should be enough to make basic binaries work.

All the same; I have reports of the system mkdir being invoked instead of MSYS' on Windows, too; piping all calls through bash should fix both issues.

1076
Proposals / Re: LGM Automatic Saving
« on: April 30, 2012, 01:47:42 PM »
Considering Ism has evaporated, no.

If she comes back, you can put in a feature request.

1077
Issues Help Desk / Re: Missing 'Make' file
« on: April 30, 2012, 08:10:17 AM »
Fascinating; it seems that when ENIGMA makes its calls, the environment Bash creates isn't being sent to them. This is probably to do with the fact that ENIGMA was designed to be configured and run from the Windows command prompt (rather than from bash's environment).

See if setting path: C:\MinGW\bin;C:\MinGW\Msys\1.0\bin; in gcc.ey works as a quick-fix (this is what ENIGMA.exe would have set it to in the Windows environment).

If that doesn't work, I will have to modify ENIGMA's exec() function on Windows to just pipe commands through Msys bash in all cases.

1078
Issues Help Desk / Re: Missing 'Make' file
« on: April 30, 2012, 12:21:47 AM »
I just noticed, that doesn't appear to be Windows' command prompt. Are you running bash? If so, have you tried running LGM from that terminal?
You can do this by calling java -jar lgm*.jar in ENIGMA's directory.

1079
Issues Help Desk / Re: Missing 'Make' file
« on: April 29, 2012, 10:49:51 PM »
Interesting; everything appears to be in working order. I suppose I should have had you try make --version, too, in retrospect. It should probably work; if it does not, that's the problem, and changing "make" to "mingw32-make" in gcc.ey may help.

If make --version does work, then it's a bug in LGM's ENIGMA plugin.

1080
Issues Help Desk / Re: Missing 'Make' file
« on: April 29, 2012, 09:45:44 PM »
The issue with the old ENIGMA.exe is that it used MinGW-get to install MinGW. That program has since stopped working, and we've been tossing ideas back and forth about what to do about that ever since. We usually have people install MinGW manually instead. Can you confirm that you have a complete MinGW and binutils distribution installed?

According to that gcc.ey, you should be able to run GCC from the command prompt just by typing "gcc". Could you tell me what running gcc --version prints? Also, you should be able to do the same thing for binutils/msys tools such as rm. According to that gcc.ey, rm --version should work, too.