I don't think the topic of DirectX is such a sticky issue. How does Delphi handle DirectX headers? Dynamically! Of course it does, the whole API from Direct3D to DirectPlay DirectSound is a series of Dynamic Link Libraries.

Go fishing for fish with a fishing rod and/or net and hunt bears, moose and deer with a riffle. Not the other way around.

Any truely powerful game can always be improved upon by a good few in-line assembly routeens and good solid coding practices. This eliminates many speed bumps you may have by being innovative. Besides, like Delphi and it's predicessor Free Pascal and Lazarus will get better at these things. If you make maximum use of your resources you'll not run into too many problems that it will destroy your project.

The idea I had with the Game Edition and the way I think it should be approached is like that of a fully installed copy of Delphi with all those neat little component suites, Graphics Headers and libraries pre-installed and sitting in a common installed directory so you can simply do things like;


:arrow: Click on File -> New Project... -> Select 'OpenGL + OpenAL Game' icon
OR
:arrow: Click on File -> New Project... -> Select 'OpenGL + BASS Game' icon
OR
:arrow: Click on File -> New Project... -> Select 'JEDI-SDL Game' icon
OR
:arrow: Click on File -> New Project... -> Select 'DirectX Game' icon
ETC...


And these options within the Game Edition Menu will create a defualt set of code that like in Delphi will have your included uses clause with it's default listed libraires [size=9px](it'll change depending on your profile you selected when you made a new project.)[/size] The libaries will already be included in your Library Directory Search Paths from install AND the libraries and their sources will have their own set directories for those APIs or platforms supported.

The idea is to make game programming easier making a distrubution of sorts [size=9px](if not new product depending on what platforms and APIs the studio will support)[/size] that is for game development.

Ideally you would want to use already established libraries or capable projects already in place. Such as taking a copy of Lazarus, adding the latest JEDI-SDL package, popular+functional DirectX Headers, DGL's OpenGL headers, noeska's OpenAL headers and using other such open-source and established projects than to go reinvent the wheel... This may even aid to the ability to maintain alot of modularity in the use of APIs and Libraries in your projects.

The rest is pretty much splitting hairs and what you like and don't like. This is fine, but when creating something of thise effect as a multi-platform/multi-API solution, you want more options than less or you'll have less users than more. Thus less support, feedback, interest, life-span of product.


Are there actual interested parties in doing something like this? This is one of those projects that PGD may consider becomeing involved in via some kind of mirroring or page hosting, etc...