Main Progress [Stalled because we can't Git]

[IsmAvatar]

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)

[Josh @ Dreamland]

*rubs eyes and lies down*

[TheExDeus]

I also haven't quite understood the GIT thing. I plan to format my PC some time in the future, and it would be cool if I could commit the few surface functions I made. Though I could probably just upload them to this forum like I did in the past.
I haven't done a lot because there ain't much for me to do. Adding functions is great, but I kind of have all the functions I need. Also, Build Clear isn't done yet, so I can't have a non-console iconed .exe I could distribute.
On a different note though, I am working on optical touchscreens in my spare time (FTIR and the like), and  I have coded and ported blob detection and stuff like that to ENIGMA. So I can use ENIGMA to create cool multitouch applications now.

[DarkAceZ]

We're basically just waiting on our Git pros to update this page for us: http://enigma-dev.org/docs/Wiki/Install:Git ...

This page doesn't look much better for Linux: http://enigma-dev.org/docs/Wiki/Install#Linux

[IsmAvatar]

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).

Post made February 13, 2012, 11:40:08 am was deleted at the author's request.

[IsmAvatar]

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.

[RetroX]

For the record, I fixed the dependencies for the Install#Linux page. :V

[Josh @ Dreamland]

I'm still pretty annoyed about this whole operation, but since my focus is still on the parser, I'm not going to saw anyone's head off just yet.

[IsmAvatar]

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.

[ugriffin]

Not sure why you guys insist on using Git. The company I work for makes me use git for source control, I hate it with a passion. To me, SVN simply works better (much less bull to deal with).

[TheExDeus]

I also liked SVN better. But I still haven't really tried Turtoise so maybe it makes this thing easier.

[RetroX]

Not sure why you guys insist on using Git. The company I work for makes me use git for source control, I hate it with a passion. To me, SVN simply works better (much less bull to deal with).

Why, exactly? Git acts almost like a subset of SVN; anything that can be done with SVN can be pretty much done with Git. The extra levels of complexity make things a lot easier, and it's far easier to compare revisions (which is what revision control is for).

[luiscubal]

Git acts almost like a subset of SVN

You mean superset.

The extra levels of complexity make things a lot easier

I know what you mean, and it's true in many cases. However, the way you said it makes it sound awkward("more complexity = easier")

[IsmAvatar]

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.