How to merge an EmWi project in a multiple developer environment?

Description

If many developers work for one and the same EmWi project, it might become difficult to merge a project. This article describes some EmWi features to facilitate this work.

 

Solution

For big projects, EmWi offers some features to facilitate the working together of multiple developers.

 

A) Splitted attribute

Each Unit-brick in an EmWi project possesses the attribute 'Splitted'. If it is 'true', EmWi will create a folder <unit name>.EWU instead of a unit file. Within this folder each class, constant, enum, bitmap- and font resource will be stored in a separate file with extention <class name>.EWUI. As long as the programmers are not working for one and the same class, each programmer can check in/-out his class-file independently to the source code repository (version control tools like CVS, Subversion, VSS, etc.). It is possible to deactivate and activate the 'Splitted' attribute at any time.

 

B) Unit import

Programmers can develop parts of a project in an independent unit (even in an independent project) and the unit can later be imported in any other project.

E.g.: one programmer implements the unit ‘SettingsApi.ewu’ that covers an Audio- and VideControl class with properties Volume, Bass, Treble, Mute and Brightness, Saturation, Contrast, Zoom. He implements the native calls to the related ‘C’ code API functions in the OnSet/OnGet methods of the properties. Now the UI developers need to use the unit to do change the settings from the Audio- and Video menu. For this purpose he can import the module as follows:

-      Save the *.EWU file to be imported in your EmWi project folder.

-      Open the EmWi project and navigate to the project composer.

-      Add a new unit brick from the gallery ‘Defaults’ to your project.

-      Rename the unit to the Name of the *.EWU file to be imported.

-      A message appears in the Log-window of EmWi:

"[19.8.2010 14:59:27] Warning SettingsApi : The unit ‘SettingsApi’ has been changed outside Embedded Wizard. If you wish to reload this unit please double click on this message.”

-      After you have double clicked on this message a confirmation panel appears with the message:

"Do you really want to reload the unit ‘SettingsApi’?"

-      Confirm it by pushing the yes button.

-      Finished.

Now you have imported the external module successfully and you can use it in your project.

 

See also

 

Keywords

Version control, source code repository, merge, splitted, multiple developer environments, import, external modules, team