I'm chipping away at a colour module, although I've been distracted with work the last little bit.
I'm not convinced that D needs a custom GUI library though. That's a behemoth effort. I tend to think a quality and well-maintained Qt binding/wrapping would be a much more useful tool for us to have. It's kind of a de-facto standard for portable gui these days. It will also retain interoperability with other existing C/C++ code (of which there is much), etc. It will also get us mobile UI as a freebie, which is a market we really want to get amongst. You can't really overlook the man years in Qt, and the maturity of the ecosystem. On 28 January 2015 at 08:04, Rikki Cattermole via Digitalmars-d <digitalmars-d@puremagic.com> wrote: > I have dream! A dream, dream dream. A dream to see GUI's easy to use in D! I > must admit it will be hard, but it's time. Prime time I mean! > > Now enough gabble. > I'm proposing to get Devisualization.Window PR'd into phobos. > > This cannot happen right now. It's blocked on many fronts. > 1) Objective-C bridge. The most obvious one for OSX > 2) An image definition depends on color > 3) OpenGL loading mechanism such as Derelict-GL3 > 4) X11 bindings for posix (easy not an issue) > 5) More WinAPI bindings (easy not an issue) > 6) Cocoa bindings (easy not an issue, just dependent on the bridge) > 7) A color definition > > So this idea will take a long time to happen, and that's ok. > > First off, Derelict-Util/Derelict-GL3 is a biggy here. Its old code, lets > admit it. Its also a standard for loading shared library functions. > So Mike Parker, would you be willing for this to be PR'd? And if so, are we > ok with this? > > Manu Evans has said he is working on a color module, any update on that? > Jacob Carlborg, how far off is the objective-c bridge? Has any definitions > to e.g. Cocoa been started either? > > Once we have a color definition then it'll be time to start work on an image > definition/implementation. > There is a few already present, ae, dlib and Devisualization.Image exist. > The color implementation will change, but most of the code should not for > each. > Anyone willing to start working on something? > > The benefits of this will greatly outweigh the work that this will take to > do and maintain. Just having a standard window + context interface will > greatly make GUI toolkits more interchangeable. Not to mention for game > development.
