Sorry your browser is not supported!

I am begining work on a Dyniamic Relational Database Management System for use in a game, all created with DBPro.

The first step will be the editor. Under my current plans, I can see that it will be possible to build an editor/ mapper that supports plugins for multiple events, and, hopefully, I will find a way to implement DBPro Scripting, as well.

The goal is to create an all in one system without the performance issues of previous all in one editors.

The main feature that I will be giving the most of my time to is the ability for DBPro coders to write and implement plugins, as well as sets of instruction to be applied to objects within their end product.

This tool will have to capacity to produce many types of games, but each product will be run from a single executable that will act as a key to access the database.

I would post more now, but there is much work to do before any specific details about the mechanics of this engine should go public, if indeed they ever do. Wish me luck in my endeavors

Good luck...

Mammoth undertaking. I wonder if you want to check out MrTAToad's MySQL plugin, it's pretty fast Although the end user would have to have it running :/

Yes, it is rather annoying have to get the user to create the DB first. However, as no-one has moaned about it, I haven't bothered to sort it.

I only recently got DBPro in... I have been working on the general Program Flow Chart for this program for awhile, holding back on a few specifics until I got DBPro in...

One thing that disappointed me about DB that I had hoped would be better in DBPro has to do with the documentation. Specifically, type-o's aside, I had expected the DBPro documentation to list the limits for certain commands. For example, what is the polygon limit for a matrix, or the limit to be rendered at one time...

I see that DBPro has past polygonal limits removed, however, creating the algorythms to guide users in the program as to how many polygons their matrix will have, and how far they are from a practical limit they are, will be a bit more of a chore than I expected. This could have been avoided with documentation stating the video memory used by each matrix polygon...

Then again, DBPro is a beginer's language, so it probably wasn't meant for anything like what I am doing

So far, I am impressed, despite the few bits of unanticipated work ahead

I will check out MrToad's plugin 8) May come in handy, but this database will be more toward the propretiered side, as I want to specify each field and relation precisely. What makes it dynamic will be the programs's ability to guide the end user, as they work, and the ability of the database to adjust its own size according to user input.

Odd how complex ideas are always held up by simple things, don't ya think? 8)

Yes - the simplest things are usually the most complex...