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 »
766
Announcements / Re: Things that are broke
« on: April 16, 2010, 12:19:02 am »
The following are not errors:
* 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 >_<
A few other notes
LateralGM branched between the Trunk and a branch called Versioning. This branch allowed me to develop better GM7 and GM8 support, which is necessarily unstable since it's incomplete (hence the 'branch' status). This allows stable development and more finalizations to be done on the trunk to allow it to finally become LGM1.6 release, while development continues for the Versioning branch (Which is not a necessary part of the 1.6 release).
Due to Enigma having very high demands on experimental and progressive features, I was forced to take Enigma off of the Trunk and into the Versioning . branch (See Versioning Disclaimer). As such, there may be some bugs, especially pertaining to GM7 or GM8 files. Do feel free to report any bugs you come across either here or on the LGM forum, but do realize that it may just be something I'm still working on.
Due to a change in the support of the file format, there have also been some important changes to the information that I eventually pass off to Enigma (the structure of the information doesn't change. Think of it like a captcha - you read numbers in an image, and then type them in the text box. Now imagine that the captcha uses a different, fancier technique, but still displays the same numbers, so you still type the same numbers in the text box. LGM is the captcha. The structure passed into the DLL is the textbox). This new information may cause some incompatibilities (like it may be harder to read the captcha).
Versioning Disclaimer: Notice, I'm not saying I switched to the Versioning branch because that's where I can just dump all my experimental and broken features. The features I implement are very well thought out, and implemented fully, not broken. However, they are progressive in the nature that they change the way LGM works internally, and in very progressive ways. Before making such changes, I always think them out as thoroughly as possible and think of what it could possibly break - as well as using some nifty Java/Eclipse tools to look up references to the code to see what all could break - and then I test that to ensure that it has not broken. So again, these features are not "experimental" or subject to breaking LGM - I'm not running with scissors. They are just progressive because they change LGM in ways that I am not yet ready to change the Trunk. Think of the trunk as a conservative, if you will. It just wants to work and get things done, even if it means ad-hoccing stuff. But it'll keep trucking along in its old ways until either it gets to release, or it becomes overcome by the progressives (e.g. I merge the branch back in)
@freezway: I don't have access to a 64 bit system, and I don't know if Josh does either. If you could, see if you can't isolate the cause to a small change - like if adding an object causes the seg fault.
I would have liked to have had a session where, instead of saying "omg, something works, now let's run with it and see if we can compile games", we could have instead done a full print out of as much information as possible from a game obtained through the dll, just for testing. Then we'd try out passing in different variations of resources - like just one room, and then multiple rooms, and then just one object, and then a room and an object - etc. As it stands now, it's very difficult to debug a seg fault or a crash, because nothing is isolated. We're just running with it and saying "zomg, something failed somewhere, but we did 200 things, so we don't know where."
* 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 >_<
A few other notes
LateralGM branched between the Trunk and a branch called Versioning. This branch allowed me to develop better GM7 and GM8 support, which is necessarily unstable since it's incomplete (hence the 'branch' status). This allows stable development and more finalizations to be done on the trunk to allow it to finally become LGM1.6 release, while development continues for the Versioning branch (Which is not a necessary part of the 1.6 release).
Due to Enigma having very high demands on experimental and progressive features, I was forced to take Enigma off of the Trunk and into the Versioning . branch (See Versioning Disclaimer). As such, there may be some bugs, especially pertaining to GM7 or GM8 files. Do feel free to report any bugs you come across either here or on the LGM forum, but do realize that it may just be something I'm still working on.
Due to a change in the support of the file format, there have also been some important changes to the information that I eventually pass off to Enigma (the structure of the information doesn't change. Think of it like a captcha - you read numbers in an image, and then type them in the text box. Now imagine that the captcha uses a different, fancier technique, but still displays the same numbers, so you still type the same numbers in the text box. LGM is the captcha. The structure passed into the DLL is the textbox). This new information may cause some incompatibilities (like it may be harder to read the captcha).
Versioning Disclaimer: Notice, I'm not saying I switched to the Versioning branch because that's where I can just dump all my experimental and broken features. The features I implement are very well thought out, and implemented fully, not broken. However, they are progressive in the nature that they change the way LGM works internally, and in very progressive ways. Before making such changes, I always think them out as thoroughly as possible and think of what it could possibly break - as well as using some nifty Java/Eclipse tools to look up references to the code to see what all could break - and then I test that to ensure that it has not broken. So again, these features are not "experimental" or subject to breaking LGM - I'm not running with scissors. They are just progressive because they change LGM in ways that I am not yet ready to change the Trunk. Think of the trunk as a conservative, if you will. It just wants to work and get things done, even if it means ad-hoccing stuff. But it'll keep trucking along in its old ways until either it gets to release, or it becomes overcome by the progressives (e.g. I merge the branch back in)
@freezway: I don't have access to a 64 bit system, and I don't know if Josh does either. If you could, see if you can't isolate the cause to a small change - like if adding an object causes the seg fault.
I would have liked to have had a session where, instead of saying "omg, something works, now let's run with it and see if we can compile games", we could have instead done a full print out of as much information as possible from a game obtained through the dll, just for testing. Then we'd try out passing in different variations of resources - like just one room, and then multiple rooms, and then just one object, and then a room and an object - etc. As it stands now, it's very difficult to debug a seg fault or a crash, because nothing is isolated. We're just running with it and saying "zomg, something failed somewhere, but we did 200 things, so we don't know where."
767
Announcements / Re: Anaphase
« on: April 15, 2010, 03:57:40 pm »Quote from: freezway
LGM now runs... but i cant use enigma. it says its now missing JNANo it doesn't. It says JNA is not a plugin. This is correct.
768
Announcements / Re: Anaphase
« on: April 14, 2010, 10:15:53 pm »
The following is an example of non-erroring output:
Code: [Select]
$ java -jar lgm16b4.jar
Java Version: 10600 (1.6.0_15)
Loading lib files in /home/ismavatar/Desktop/enigma-dev/lgm16b4.jar
01_move.lgl 02_main1.lgl 03_main2.lgl 04_control.lgl
05_score.lgl 06_extra.lgl 07_draw.lgl
SvnKit missing, corrupted, or unusable. Please download and place next to the enigma plugin in order to enable auto-update.
Initializing Enigma: Intializing Parsers.Probing for GCC...
GCC located. Path: `'
Successfully loaded GCC definitions
Unable to load plugin: jna.jar: null: Missing plugin entry point (LGM-Plugin)
769
Off-Topic / Re: Challenge
« on: April 14, 2010, 01:47:46 pm »
Holy wow, this is some good shit. Thanks for sharing, man.
771
Off-Topic / Re: I have seen the future... and it is bad.
« on: April 12, 2010, 02:39:45 pm »
Net neutrality isn't about customers, it's about content and accessibility to websites. While I have no doubt they are neutral when it comes to their customers, they have a reputation for being unfair, discriminatory, throttling, and even censoring content not consistent with their tastes. And they do so in anything but a transparent way.
772
Off-Topic / Re: I have seen the future... and it is bad.
« on: April 12, 2010, 11:20:55 am »
Lol, never use "google" and "net neutrality" in the same sentence again.
Also, I don't see what's so wrong with charging by the byte. It's a great policy for those of us who use very little internets. The cheapest internet in my area is $65/mo, which gives me speeds I'll never use. I already enjoy cheap Gas and Electric utility prices because they charge by the Dekatherm and KilowattHour (respectively). About time my internet bill dropped price as well, even if it does mean that I can't just auto-transfer $65/mo due to variable pricing now.
Also, I don't see what's so wrong with charging by the byte. It's a great policy for those of us who use very little internets. The cheapest internet in my area is $65/mo, which gives me speeds I'll never use. I already enjoy cheap Gas and Electric utility prices because they charge by the Dekatherm and KilowattHour (respectively). About time my internet bill dropped price as well, even if it does mean that I can't just auto-transfer $65/mo due to variable pricing now.
773
Announcements / Re: Anaphase
« on: April 10, 2010, 03:08:22 pm »
I have no objections to using JNI, and would have liked to have used it in the first place, but I was never able to get it to work.
774
Announcements / Re: Anaphase
« on: April 10, 2010, 01:35:25 pm »
Not necessarily. It's just that each solution brings a new problem.
775
Announcements / Re: Anaphase
« on: April 10, 2010, 01:20:20 pm »
Output redirection is where you print something to stdout, but instead of it being printed to the console, it gets redirected to something else, like a file or a window.
In the context of Enigma, the problem is that before, when I ran Enigma as an executable, output was put in a stream, rather than printed to stdout, and I could decide what to do with it. Now that enigma is a dll, it uses Java's stdout, so I need to redirect my own stdout to wherever I want it to go, and then put it back to terminal output afterwards.
The problem with this is that it's *my* stdout, which means that if *I* want to print something while I'm redirecting Enigma's stdout, it means that *my* output also gets redirected. This is a non-issue if I just redirect output, call the dll, and then reset output - but it's not as simple as that, because calling the dll can take time, which means that LGM would freeze while it's waiting for the dll, and you wouldn't see the output until the dll finishes, when it all comes at once.
To solve *that* problem, I would normally thread enigma (run it in its own thread, or simultaneous to LGM, rather than freezing and waiting for it to finish). However, that solution means that while I have output redirected and while Enigma is running, LGM is also running and could potentially produce output. If it does so, said output will be redirected, which is undesirable.
In the context of Enigma, the problem is that before, when I ran Enigma as an executable, output was put in a stream, rather than printed to stdout, and I could decide what to do with it. Now that enigma is a dll, it uses Java's stdout, so I need to redirect my own stdout to wherever I want it to go, and then put it back to terminal output afterwards.
The problem with this is that it's *my* stdout, which means that if *I* want to print something while I'm redirecting Enigma's stdout, it means that *my* output also gets redirected. This is a non-issue if I just redirect output, call the dll, and then reset output - but it's not as simple as that, because calling the dll can take time, which means that LGM would freeze while it's waiting for the dll, and you wouldn't see the output until the dll finishes, when it all comes at once.
To solve *that* problem, I would normally thread enigma (run it in its own thread, or simultaneous to LGM, rather than freezing and waiting for it to finish). However, that solution means that while I have output redirected and while Enigma is running, LGM is also running and could potentially produce output. If it does so, said output will be redirected, which is undesirable.
776
Announcements / Re: Anaphase
« on: April 09, 2010, 02:16:10 pm »
Yes.
{
JTextArea a = new JTextArea();
add(a);
}
{
JTextArea a = new JTextArea();
add(a);
}
777
Announcements / Re: Anaphase
« on: April 09, 2010, 01:48:11 pm »
JNA is LGPL.
Also, what's so wrong with our code editor anyways?
Also, what's so wrong with our code editor anyways?
778
Issues Help Desk / Re: Map loading
« on: April 07, 2010, 04:05:41 pm »
LGM uses threads to load the Game Information and Game Settings frame, and then waits for them if the user requests them. It cut an entire 2 seconds off the LGM load time, and chances are the user won't click on one of those in the first 2 seconds.