Constructors, accessors, database links, and serialization are
often made up of the same few lines of code, with the only variation being the name of
the piece of data in question. Second, many of today??™s systems require multiple types
of code ?¬?les for one conceptual entity: a C# interface, data service class, database
table de?¬?nition, database stored procedures, and so on. When these are written by
hand, the names and other details of the attributes of the entity must be duplicated
across all these ?¬?les, but in the model each is represented only once.
In addition to code ?¬?les, or code-like ?¬?les such as database table de?¬?nitions, there
are also often various other ?¬?les required as output from a model. For example, the
Symbian S60 platform can require as many as 27 ?¬?les for a simple ???Hello world???
application: menu and UI de?¬?nition ?¬?les, localization ?¬?les, application descriptor
?¬?les, icon lists, and so on. Some of these can be generated directly from the
information in the top-level model of the application; others such as the localization
?¬?les must recurse through all the models with UI information. This is easy for a
crawler or API-based generator: they can simply open a new stream for each ?¬?le and
walk the structure of the models to visit all the required information.
Pages:
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562