From: potatoes <bwi...@co...> - 2005-02-27 19:11:19
|
aed is a partially complete, full function Gui toolkit that renders under SDL. to me the most practical purpose for aed is as an easy drop-in Gui system for games, or other openGL apps. it in it's current form it is simply just another widget set, but because it renders in SDL converting it to render to a openGL window wouldn't be very hard. a themeable Gui library capable of providing the developer with already complete menu, hud, and console systems right from the start of development would be a very useful tool. our current openGL output simply gives a SDL_texture with the window to be used as a texture in the developers own openGL setup, which is slow and limits lots of openGL functionality. though aed uses SDL's 2d drawing api, which means low level rendering functions would need some rewriting to switch. but SDL's library is similar to many basic openGL commands, so it is very plausible. we could provide an easy to use and simple to implement framework for game makers. not something so encompassing as a game engine framework but something that will provide: * a way to open an openGL window. * forms capable of both simple and complex starting menus. * widgets to make a complete hud/in-game Gui. * forms loadable from XML * transparent client/server communication (easy with XML based forms) the differences between such a toolkit and aed's current status really aren't very big. most game Gui's aren't very complex. basic theming abilities and transparency are it's only aesthetic necessities, and a few widgets to help graphics programmers with commonly needed things(console, 3d functionality, etc...). unthemed aed would retain it's current non-flashy toolkit look, making it still very capable of normal program UIs. how does everyone feel about this? does this seem useful, practical, interesting? i'd be glad to hear from both people interested in it and people just reading. potatoes |