I see how some of that would be useful but it sounds very annoying to make. I'll let you handle it =)
I'd probably make something a little lower level and smaller in scope. It'd be a more convenient way to create and manage screen objects. The library wouldn't do a lot of useful things for you, it'd just make it easier for you to make useful things.
|
||||||||||||
An example of what I'm presently doing for my HUD lib:
- Parent and Child element interaction
- Movable and static windows and panes
- Scrollable bars with flexibility to apply to most elements
- Text display, which can be scrollable or not
Can be expanded to become a text input
- Grid display, like the .dmf grids. Can display a table of variable length and width with objects and/or strings.
Can be scrollable or not.
- Image display. For displaying individual objects and providing hooks for mouse interaction with the object.
The idea is to simply instantiate a bunch of HUD element objects and set parents to have an on screen interface that has similar functionality to .dmf.
There are countless examples of BYOND games that could use a non-.dmf interface.