Game Development Reference
In-Depth Information
< Configuration xmlns:xsd="
http: // www . w3 . org /2001/ XMLSchema
"
xmlns:xsi=
"
http: // www . w3 . org /2001/ XMLSchema - instance
" >
<Projects>
<Project serverUrl="tcp://YourAwesomeServer:20000
/CruiseManager.rem"
projectName="Level Editor" />
</Projects>
<PollPeriodSeconds>5</PollPeriodSeconds>
<BuildTransitionNotification showBalloon="true">
<Sound />
<BalloonMessages>
<BrokenBuildMessage>
<Caption>Broken build</Caption>
<Message>The level editor is broken</Message>
</BrokenBuildMessage>
<FixedBuildMessage>
<Caption>Fixed build</Caption>
<Message>The level editor has been fixed</Message>
</FixedBuildMessage>
<StillFailingBuildMessage>
<Caption>Build still failing</Caption>
<Message>The level editor is still broken.</Message>
</StillFailingBuildMessage>
<StillSuccessfulBuildMessage>
<Caption>Great work</Caption>
<Message>The level editor has been updated!
Please update.</Message>
</StillSuccessfulBuildMessage>
</BalloonMessages>
</BuildTransitionNotification>
<TrayIconDoubleClickAction>ShowStatusWindow
</TrayIconDoubleClickAction>
</Configuration>
Listing 4.8.
CCTray config file.
The tags that we want to modify to make custom messages are the
<project>
and
<BalloonMessage>
tags. The “serverURL” attribute is the TCP connection
to the CCNet server. In addition to specifying the server, you have to let CCTray
know what project it is watching. The “projectName” attribute handles this. Once
that block is finished, we can change the messages for the build status notifications.
The messages we can change are
<FixedBuildMessage>
,
<BrokenBuildMessage>
,
<StillBrokenMessage>
,
<StillSuccessfulMessage>
.
Each message tag has a
<caption>
and
<message>
tag for the balloon notification
that will be displayed. The
<message>
tag is the one to modify if you want to let
people know to sync up for a new version of a tool.
