It lives!

JensAyton · Post by **JensAyton** » Sun Mar 11, 2007 11:28 pm

Ahh, right. *Thwaps Xcode and FileMerge for hiding that bit*

JensAyton · Post by **JensAyton** » Mon Mar 12, 2007 12:09 am

JS loading almost works now… although, now that I’ve seen that code, I’m going to redesign it (encapsulating all three script types in classes instead of the current special-casing). But not tonight. :-)

Post by **dajt** » Mon Mar 12, 2007 12:44 am

You're welcome to do that - I was putting it off, concentrating on other things.

My mods to Oolite - fast, cheap, good, choose any one of them.

JensAyton · Post by **JensAyton** » Mon Mar 12, 2007 7:00 am

Ain’t it always that way.

CaptKev · Post by **CaptKev** » Mon Mar 12, 2007 9:03 pm

@dajt, sorry to be such a pain but I'm having a bit of a problem adding a branch to the main trunk. What's the procedure for say adding the textured-planet branch (I can't even build libnoise.a for some reason).

Post by **dajt** » Mon Mar 12, 2007 11:58 pm

I don't understand the question - do you mean how to check out the branch, or how to use the textured-planets exe?

If you're trying to build textured planets you're in for an exciting ride. You need to build a very recent version of GCC and use that in preference to the GNUstep one, because it can't build C++ code (it is missing the C++ front end).

Ensure this is the first version of GCC in your path.

Then you should be able to make libnoise. libnoise is very plain C++ and should present no problems on any platform.

Then make a directory under the textured-planets directory, go into it and use the command "make -f ../makefile". I could not get the standard GNUstep build system to make C++ files, despite the fact it seems to be supposed to support them.

CaptKev · Post by **CaptKev** » Tue Mar 13, 2007 8:32 am

Hi dajt, sorry for not making myself clear and thanks for your reply.

What I was trying to do was add the textured planet and JavaScript code to the main trunk. I realise that libnoise.a and libjs32.a will be required, but I'm having trouble locating the code that will be required to be merged into the main trunk code.

I was trying to compile libnoise with 'MS Visual Studio .NET', so I'll get a copy of GCC and try again.

I'm probably trying to run before I can walk and the whole thing will be a complete waste of time!

JensAyton · Post by **JensAyton** » Tue Mar 13, 2007 8:38 am

I’m busy merging the JS code into the trunk, so don’t bother with that. Merging the textured planets could be problematic, since there’s a different set of textured-planet code in the trunk (pause and press T to activate it).

In fact, it’s probably not worth trying anything big right now, because the JavaScript merge has turned into a big rewrite of the scripting system with far-reaching consequences.

CaptKev · Post by **CaptKev** » Tue Mar 13, 2007 8:42 am

Okay I'll give that a try, thanks Ahruman.

Post by **dajt** » Tue Mar 13, 2007 8:50 am

Getting textured-planets with libnoise into the trunk would be tricky. I gave up trying to merge the trunk code into the textured-planets branch (which is effectively the same operation) because the trunk's planet texturing code and the libnoise texturing code obviously hit exactly the same parts of the PlanetEntity class. It was just too messy.

A silly idea has just occured to me. We could either abstract the planet texture generators behind an interface to give options for which texture generator to use, or put them into a separate processes which use something like shared memory to transfer the generated texture.

The first idea is cleaner from a design point of view but the second idea avoids linking C++ code into the game.

But I'm having nothing to do with it ;)

JensAyton · Post by **JensAyton** » Tue Mar 13, 2007 9:00 am

Oh, right. That “we”.

Post by **dajt** » Wed Mar 14, 2007 3:46 am

Well, come on. I had the idea, someone else (not naming names) implements it. Surely that is "we"?

;-)

JensAyton · Post by **JensAyton** » Wed Mar 14, 2007 1:30 pm

The royal we are planning to focus on code cleanup for a while (didja guess?), on the basis that enhancing cleaned-up code is easier than enhancing messy code and then cleaning up the now-even-messier code. I have little say in what other wes do.

CaptKev · Post by **CaptKev** » Wed Mar 14, 2007 2:45 pm

Any chance of reducing the visibility of those annoying Front/Aft/Port/Starboard messages with the code below?

Code: Select all

- (void) drawMessage
{
	if (message_gui)
		[message_gui drawGUI:0.2 forUniverse:self drawCursor:NO];
}

JensAyton · Post by **JensAyton** » Sun Mar 18, 2007 3:38 pm

Well, I’ve tried to set up the Windows build (under emulation, urgh) so I can test and verify stuff, but I’ve hit a significant snag: mingw says it can’t find svn. Since I can’t work out a way to reference files outside C:\GNUstep\Development\msys\1.0\, I don’t see how it would be expected to find it. There would seem to be a step missing from the wiki (and no, it’s not the “install svn” step).