Re: [MiNT] [RFC] AES extension for games

[Paul Wratt <paul.wratt@gmail.com>]

2009/12/13 Vincent Rivière <vincent.riviere@freesbee.fr>:
> Le 12/12/2009 14:27, Patrice Mandin a écrit :
>>
>> I would like to avoid hooking any system vector at all.
>
> Very good.
> Let's specify, implement and use new clean APIs or extensions to get rid of
> all hardware dependencies.
>
> --
> Vincent Rivière
>
Yes, I would like to see a work toward AES 5.0 as a stable release of
"all new extensions". What else is needed (I have gone blank :( )

Dont leave the Joysticks out (of AES), there is no reason why it can
not be used in the same way Keyboard and mouse are (by XaAES at least,
focus, navigation). A joystick driver should not be a problem until
you start dealing with PCI/ISA (on the sound card), if you go that
far. Probably more important is to keep in mind that (soon) usb
joysticks will be a posibility.

Hmm this just made me realise something. Xbox joysticks are usb
joysticks. But unlike Windows, Xbox does not use USB driver or OS, so
it has to talk directly to the usb, but still in a clean way
(supported by Win32). I am sure I know where to find a usb stack
written in C and its only about a page long... (including
handler/driver) and that code has to support hubs, at least to the
first level (the Xbox joystick is actually a hub with sub units)

I would like to use advance "events" in a desktop, these would be good
to have, especially if it could be deemed an HID API, allowing
addition of more than just that mentioned above (keyboard mouse and
joystick)...

If the extension was to have "hi level" and "low level" parts to the
API, to cover both ways of programming, this would be good also, as
long as it does not cause confusion..

What else is needed, and what else would make (or qualify as) a good
or valid extension.. like say 32bit argb image tranform with optional
background texture combine, and/or (alpha) masking.. new or extended
(game related) form widgets (? - I dont know, but it sounds good :)

Paul