Download Chora User Manual

TARA Systems
Project file (EWP)
3 Project file (EWP)
Each Chora program must be described by a project file. This file specifies what a
Chora program consists of and how the Chora compiler should ultimately translate it
to ANSI C.
A project file must always begin with a $version directive. This directive informs the
Chora compiler of the syntax used in the project file, and is intended for the future file
extensions. The directive is followed by the version number. For example:
$version 5.0
If the Chora compiler does not recognize the version number given, the translation is
aborted with an error message.
After the $version directive follows the actual listing of the project's components.
These include:
 Units  Each unit file used in the Chora program must be defined explicitly in the
project file. Only in this way can the Chora compiler access all relevant units. The
definition of a unit comprises the indication of where within the file system the
.EWU unit file may be found.
 Profiles  A profile describes the settings of the desired target platform. The
target platform is determined from the name of the so-called Platform Packages.
A Platform Package is an Embedded Wizard extension that must be supplied by
TARA Systems GmbH for each target platform. Besides the name of the Platform
Package used, a profile may contain a set of settings and macro definitions.
 Macros  A macro stores any character string under a unique reference name.
By using this reference name, the contents of the macro (the character string
stored there) can be used in definitions of classes, methods, and so on. A macro
is always defined within a profile; thus, a macro is valid only when the
corresponding profile has been specified when launching the Chora compiler.
Macros defined in other profiles are ignored.
 Languages  Defining languages determines the countries for which the GUI is
localized. The localization makes it possible to develop an GUI in German,
English, Japanese and so on.
 Styles  The styles are used to identify different variants of the GUI application.
Such multivariant GUI application may change its appearance and behaviour at
the runtime. This feature provides a simple way for the development of GUI
applications with different skins and themes.
3.1 Units
A unit is always introduced using the keyword unit, followed by the name of the unit
itself:
unit Core
{
attr Directory = ..\Mosaic;
}
Embedded Wizard
Chora User Manual
Copyright TARA Systems GmbH
www.embedded-wizard.de
Page 9