It is
similar to building components and more general frameworks: by no means an easy
task, but certainly a skill that can be learned. The main difference between building a
domain framework and more traditional frameworks is the target audience. The
???users??? of a domain framework will be the generator and its generated code, rather
than developers and their handwritten code. This solves a problem commonly
experienced by builders of traditional frameworks: they make a wonderful framework,
but people often misuse it??”or more often fail to take advantage of it or parts of it.
As the use of the domain framework is automated in the generator, domain
frameworks are used more consistently than traditional frameworks. This makes it
possible for them to go further than normal in removing duplication. For human
developers and traditional frameworks the cost of one developer learning a framework
feature must be recouped over the number of times that one developer uses that
feature. In a domain framework, only one developer need learn that feature, applying
it in the generator, yet the cost will be recouped over all developers using the
framework. Often, the framework developer will also be the generator developer, so
even that small cost becomes almost zero.
Thedomain framework also separates the generated code fromthe platform.
Pages:
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614