Hi !
Featured games (90)
games approved by the League of Dukes
Games in Showcase (753)
Games in Android Showcase (228)
games submitted by our members
Games in WIP (842)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
    Home     Help   Search   Login   Register   
Pages: [1]
  ignore  |  Print  
  Independent Window Toolkit  (Read 1243 times)
0 Members and 1 Guest are viewing this topic.
Offline zingbat

Senior Devvie

Medals: 1

Java games rock!

« Posted 2004-08-16 16:44:41 »

Is there  any way to work with native windows and events in java without having to use awt ? Something like a third party api that let us use to cygnusx or win32 apis with a binding.

Have you guys considering the possibility of making jogl independent of awt ? By a means similar to the one i described above. Or perhaps a more flexible sytem using Device and Driver interfaces that could be extended to make use of different window native apis at player choice.

For instance a set of interfaces like this, simple and direct to the point:

LocatorDevice - Something that signals a position on screen, handles locator device events

KeyboardDevice - Similar to a keyboard or a keypad, handles keyboard events

WindowDevice - opens/closes native windows, handles clipping, activate, deactivate, hidden, shown, visible area, events for show, hide, active, inactive, etc

ScreenDevice -  Handles screen resolution, capabilities, switch resolutions, color mode, frequency, etc

TimeDevice - Handles time measures, can be clocked to call several clalback methods at certain times, can show current time measure with great precision required for games.

Measure - Information sampled directly from a device showing its status.

Event / EventQueue - Information gathered from devices set to event mode.

Device - This matches a logical or real device (WindowDevice is a logical one). A device can be made active/inactive, set to sample mode only, set to event mode and sample mode. (See book CG from Foley).

DeviceController - Controller for collecting events from all devices in the EventQueue.

GraphicsDevice - Allows access to the framebuffer, raster operation and provides a set of primitive 2d and 3d operations to build upon.

DeviceConfiguration - For device configuration.

This are interfaces, the real classes would be put in subpackages like win32 or cynusx and would extend this. A factory or some other method would allow the programmer to select which subpackage to use.
Pages: [1]
  ignore  |  Print  

ivj94 (581 views)
2018-03-24 14:47:39

ivj94 (45 views)
2018-03-24 14:46:31

ivj94 (372 views)
2018-03-24 14:43:53

Solater (60 views)
2018-03-17 05:04:08

nelsongames (107 views)
2018-03-05 17:56:34

Gornova (148 views)
2018-03-02 22:15:33

buddyBro (690 views)
2018-02-28 16:59:18

buddyBro (90 views)
2018-02-28 16:45:17

xxMrPHDxx (492 views)
2017-12-31 17:17:51

xxMrPHDxx (729 views)
2017-12-31 17:15:51
Java Gaming Resources
by philfrei
2017-12-05 19:38:37

Java Gaming Resources
by philfrei
2017-12-05 19:37:39

Java Gaming Resources
by philfrei
2017-12-05 19:36:10

Java Gaming Resources
by philfrei
2017-12-05 19:33:10

List of Learning Resources
by elect
2017-03-13 14:05:44

List of Learning Resources
by elect
2017-03-13 14:04:45

SF/X Libraries
by philfrei
2017-03-02 08:45:19

SF/X Libraries
by philfrei
2017-03-02 08:44:05 is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!