(2) The code for the domain framework components is generated. This is an
unusual step, since normally any domain framework code ?¬?les would already
be present on the developer??™s local disk or referenced from a network share.
For the purposes of the Watch example as part of an evaluation package,
however, we had to provide the framework code ?¬?les and make sure they
were installed in an appropriate place. The easiest way to do this was simply
to include them as textual elements along with the models. This way we
ensured that all required components were available at the time of
compilation, and we also had control over the inclusion of platform-speci?¬?c
components.
(3) The code for logical watches and watch applications is generated. The state
machines areimplementedbycreatinga data structure thatde?¬?nes eachstate, transition,
and display function, alongwith their contents. For each action, the code
generator creates a set ofcommands that are executedwhenthe action is invoked.
(4) The generated code is compiled and executed as a test environment for the
target platform. Basically, this step requires only the execution of the scripts
created during the ?¬?rst step.
How was the code generator implemented then? Each generator in MetaEdit+ is
associated with a certain modeling language and can thus operate on models made
according to that speci?¬?c language.
Pages:
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392