For example, the version of Java in which the watch
example was originally written did not contain any useful service to handle timed
events such as alarms. Thus, we implemented such a service ourselves as part of our
domain framework. The more recent versions of Java, however, do provide a similar
mechanism, meaning that it could be part of the platform if the watch implementation
only needed to support more recent versions of Java.
Without any deep theoretical discussion about what is the border between framework
and platform, we shall use the following de?¬?nitions here: The platform is
considered to include the hardware, operating system (Windows or Linux here), Java
programming language withAWTclasses, and environment to test our generated code
(e.g., a web browser with Java runtime). The domain framework consists of any
additional components or code that is required to support code generation on top of
this platform. The architecture of the watch domain framework??”as de?¬?ned in this
way??”is shown in Fig. 9.12 (solid line arrows indicate a specialization relationship,
while dotted line arrows indicate inclusion relationships between the elements).
The domain architecture of the watch example consists of three levels. On the
lowest level, we have those Java classes that are needed to interface with the target
platform.
Pages:
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402