On 7/11/2014 7:58 p.m., luminousone wrote:
On Friday, 7 November 2014 at 06:42:24 UTC, Rikki Cattermole wrote:
On 7/11/2014 7:38 p.m., luminousone wrote:
On Friday, 7 November 2014 at 06:29:14 UTC, Rikki Cattermole wrote:
On 7/11/2014 6:56 p.m., luminousone wrote:
I have been working on a media library, it still has a long way to go,
but I figured its about time I shared what I am doing.
If I could possibly convince a few people out their to give'er a once
I use XCB/XLIB/GLX directly, so I am not just simply wrapping SDL or
SFML. And I am using XCB for event handling and opening windows.
Threading should work much more reliably, due to the use of XCB.
I am releasing the library under the BSD license,
Its a good start.
But instead of creating the window itself manually would you consider
using DWC ?
DWC is more or less done. But I need help with my plans for a game dev
framework in D.
If you're interested in helping with that please give me an email
XLIB is an absolute train wreck when it comes to threading, call
XPollEvent outside your draw thread will most likely segfault.
As well I need control of the opengl contexts, as I want to separate
drawing and loading into separate threads.
I need both good threading support, and control over my opengl contexts
to fulfill the goals I have set for myself.
That said, it is a nice looking library. But it would not fulfill my
Fair enough. Threading is a major issue with those low level api's.
I eventually want to build a entity system, and make use of
parallel_foreach, or fibers/routines, and have a loading thread that can
get assets in an async fashion.
Large voxel/cube-voxel systems and mega texturing interest me, I feel
like a small team could develop a big game with tools built around a
XCB mostly solves the threading issues that XLIB suffers from, However
XCB has poor support for the input extensions, as of yet nothing that
replaces xlookupstring, I hope to find a good work around at some point,
but it seems good "enough" for my needs.
Also I am not sure of how well XXf86vm extension is supported for full
screen access, As I have yet to implement full screen windows.
Its a learning experience, however so I can't complain to much!
Interesting, just out of interest have you thought about separating it
out and work independently of GUI's for e.g. game servers? Or would that
abstract it to the point of non-usefulness?