kikura

I just realised that I don't know what I'm supposed to be coding next!

You see, it goes like this. I start coding, then I decide what I need to code and I make it up as I go along.

THAT'S NO WAY TO CODE!!

So, I need a plan. First: basics, then: less basic.... hmmm, I think I need to give it some more thought.

So far, I've been doing the basics: setting up SVN, setting up my build system, then on to code:

• The Kernel
• The basic servers
  • EventServer (KeyEvent)
  • GraphicServer (only draws a single cube, forever)
  • RegistryServer (the factory for entities)
  • FileServer
  • ScriptServer
• Attrib & AttribHolder (dynamic setting/getting of attributes from instances - very cute!)
• Utilities (string stuff, parsing, etc)
• Simple scripting
• Pre-compile step to automatically write code for lua glue, attrib registration, entity registration, etc.

That's not a bad start, I think, but I still haven't decided where to go next.

For starters, I need to finish the scripting part - to finish Scriptable and to link it in with my pre-compile step and the AttribHolder class. I also have to decide how I'm going to do all the math classes too.

Once that is done, there's no delaying it, I have to really do my graphics!

But that's for another post... 

Watch out!

If you use GPL code in your commercial project, someone will end up finding out!

Though simple, and probably quite secondary, the FileServer is a very important part of the engine.

It makes sure that you can get to a file, and it makes sure that when you get it, it's correct.

A multitude of methods are available for accessing files. For the moment, I'm just implementing a priority search path. So, it tries to open the file from directory A (by appending the path to the search path entry), then directory B, and so on. That way, all my main (stable) data can be in directory B, and the stuff I want to test in directory A. So, when I ask for a file, it will usually not find it in directory A, and proceed to directory B. But the files that I'm testing out will be picked up before the stable ones. Win!

Another cool thing to add to a FileServer is the ability to serve packed files or remote files transparently, but I don't need that quite yet.

 

Hi,

I'm tALSit de CoD, and I've been asked to participate in an art instalation as principal coder.

We're still coming to grips on exactly what we want to do, but what is known is that it will involve some nice funky graphics, and that's where I come in.

I'm in the process of writing an engine with real-time graphics capabilities, but I'm writing it in a way that it's flexible to create, flexible to extend, portable and fast.

It's an OpenGL beast, and I'm making every attempt to make it run fine on Win32, Linux & Darwin.

Source code is available here (u: anon, p: ), so check it out and let me know what you think!