Maintaining uigen.exe and uigen.exe templates

For real-world applications, uigen.exe is used only a few times. Since it is not a round-trip tool, uigen.exe is invoked only for building prototypes. As soon as one prototype has reached a halfway satisfactory maturity, developers take it from there and don't use uigen.exe from that point on.

uigen.exe is used more extensively by re-motion beginners. They experiment with uigen.exe and build prototypes for multiple toy applications.

Most use of uigen.exe makes the re-motion instructor, because uigen.exe is a significant component in re-motion classes. Since classes are a delicate and important affair, that uigen.exe should better work, and for a most recent version of re-motion, to boot. What's more, since the PhoneBook web application is the central component of re-motion's documentation, the documentor maintaining the PhoneBook app is also the logical
choice for maintaining uigen.exe and its templates.

An impression what this work looks like can be seen from the author's change history in the uigen.exe project.

In other words, since an up-to-date uigen.exe is of most importance to the re-motion documentor/trainer, maintaining uigen.exe is also the task of the documentor/instructor.

What's more, templates (as the entire uigen.exe) is developed and tested with the PhoneBook web application as its test-bed. So uigen.exe fuses these closely related tasks together:

  • adapting the PhoneBook to a new re-motion version
  • working with uigen.exe, making sure it is compatible with both re-motion and the PhoneBook sample code
  • teaching people how to use uigen.exe with the PhoneBook web application