Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

For practical reasons, that is, reasons that have nothing to do
with software engineering, duplicates of directory trees
must be maintained:

The re-motion assembly directory is needed
for both

Each of these projects holds its own local copy of
the re-motion assembly directory.

The template tree is part of the
uigen.exe project. It is needed by the PhoneBook project,
so the latter keeps a copy of the former.

Each of these directory/tree copy must be identical to its
duplicate for every major release of re-motion.
They are intimately related to each other, because

For more background, see
Maintaining uigen.exe and uigen.exe templates.

For class-room training and the PhoneBook tutorial, the use of the
entire local re-motion project is not very practical. It is
much more practical to work with the re-motion build results,
i.e. the re-motion assemblies.

The responsibility of keeping the two template directories
in sync with each other falls on the PhoneBook/uigen.exe/template
maintainer (as explained in
Maintaining uigen.exe and uigen.exe templates).

See also
  • No labels