Motorola E680 Technical Manual - Page 29

JSR 184

Page 29 highlights

9 JSR 184 9 JSR 184 Overview JSR 184 Mobile 3D API defines an API for rendering three-dimensional (3D) graphics at interactive frame rates, including a scene graph structure and a corresponding file format for efficient management and deployment of 3D content. Typical applications that might make use of JSR 184 Mobile 3D API include games, map visualizations, user interface, animated messages, and screen savers. JSR 184 requires a J2ME device supporting MIDP 2.0 and CLDC 1.1 at a minimum. Mobile 3D API The Motorola E680 contains full implementation of JSR 184 Mobile 3D API (http://jcp.org/en/jsr/detail?id=184). The Motorola E680 has also implemented the following: • Call to System.getProperty with key - microedition.m3g.version will return 1.0, otherwise null will be returned. • Floating point format for input and output is the standard IEEE float having a 8-bit exponent and a 24-bit mantissa normalized to 1.0, 2.0. • Implementation will ensure the Object3D instances will be kept reference to reduce overhead and possible inconsistency. • Thread safety • Necessary pixel format conversions for rendering output onto device • Support at least 10 animation tracks to be associated with an Object 3D instance (including animation controller) subject to dynamic memory availability. 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107

9
JSR 184
29
9
JSR 184
Overview
JSR 184 Mobile 3D API defines an API for rendering three-dimensional (3D) graphics at
interactive frame rates, including a scene graph structure and a corresponding file format
for efficient management and deployment of 3D content. Typical applications that might
make use of JSR 184 Mobile 3D API include games, map visualizations, user interface,
animated messages, and screen savers. JSR 184 requires a J2ME device supporting
MIDP 2.0 and CLDC 1.1 at a minimum.
Mobile 3D API
The Motorola E680 contains full implementation of JSR 184 Mobile 3D API
(
http://jcp.org/en/jsr/detail?id=184
). The Motorola E680 has also implemented the
following:
Call to
System.getProperty
with key – microedition.m3g.version will return
1.0, otherwise null will be returned.
Floating point format for input and output is the standard IEEE float having a 8-bit
exponent and a 24-bit mantissa normalized to 1.0, 2.0.
Implementation will ensure the Object3D instances will be kept reference to
reduce overhead and possible inconsistency.
Thread safety
Necessary pixel format conversions for rendering output onto device
Support at least 10 animation tracks to be associated with an Object 3D instance
(including animation controller) subject to dynamic memory availability.