Results 1 to 3 of 3

Thread: OpenML major Omission : user input standardisation

  1. #1
    Email address no longer exists
    Join Date
    Jun 2002
    Marseille, France

    OpenML major Omission : user input standardisation

    First I want to congratulate the Kronos group for the OpenML initiative. I find it very credible, and I am sure this is a major step for the evolution of digital media and GUIs. I would also say : it was about time !!! We all needed some kind of cross platform directX, this has always been a major issue for the industry.

    But OpenML makes, to my opinion, a huge omission : there is no proposition for standardisation of user input devices, such as joystick, mouse, and keyboard with low level access.
    From the game programer's point of view, this is a major issue, because, whenever we want to port a game, this is code we have to rewrite, and it is different for each platform. This is like reinventing the wheel every time.

    Not only talking about games, there are many applications requiring the use of joysticks while designing sound for films : operators make the sound move in 3D for dolby 5.1 using joysticks.
    Think about it : With user IO discovery, you can program 100% of a game using OpenGL and OpenML : user IO, graphics and sound.
    Without user IO discovery, you can forget about the OpenML portability, and have to go for platform specific code.
    After all, why wouldn't jostick's makers release OpenML drivers, so joysticks could also be used on Linux and MacOs (which would open them new markets), just like 3D boards manufacturers release OpenGL Drivers ?

    At last, unifying APIs for Network and 3DSound would also definatly be a big plus to OpenML...


    Alban Cousiniť

  2. #2
    Email address no longer exists
    Join Date
    Jun 2002
    france, sophia antipolis

    Re: OpenML major Omission : user input standardisation

    don't think there is a openML omission : ML means media lib it's purpose is multimedia not input....
    it's true that there is a lack in Open*L api of an "unified" input mechanism but at this point (in "()" directX concurent):
    openGl : 2D/3D graphic api (direct3D)
    openAl : 2D/3D audio api
    (??don't know if direct sound can do all openAl can do??)
    openML : streaming related api (directshow)
    Xlib:GLX /win32?? : input handling (direct input)

    Xlib has more option that's why i'd rather use it.... myabe there will be an openIL (input library) that will emulate Xlib on win32 (which could be done without a lot of overhead since the only part of Xlib we need is input event handling and windows creation/modification, all other GLX part is already done in windows "GLX" (don't remember the name) )

  3. #3
    Junior Member
    Join Date
    Aug 2002

    Re: OpenML major Omission : user input standardisation

    I have already started such a project, but think it's better to make it a part of OpenML - to use well-thought-out dmSDK architecture. see my post about OpenML SDK.
    Details via email
    Sincerely, Dmitry.

Similar Threads

  1. user event limitations
    By RlyDontKnow in forum OpenCL
    Replies: 5
    Last Post: 05-09-2011, 03:04 PM
  2. user clipping plane
    By wycwang in forum OpenGL ES
    Replies: 1
    Last Post: 10-18-2007, 07:09 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Proudly hosted by Digital Ocean