AGTEK R & D Wiki

This is an old revision of the document!

---

Mumble Mumble… early thoughts of the configuration file format.

<configuration type="SmartTrack">
   <job>
      <cycleline name="line1">n,m,p  n,m,p  n,m,p  n,m,p  n,m,p  n,m,p  n,m,p</cycleline>
      <haulpath name="path1">n,m,p  n,m,p  n,m,p  n,m,p  n,m,p</haulpath>\
      <warningarea name="area1">n,m,p  n,m,p  n,m,p  n,m,p  n,m,p  n,m,p  n,m,p  n,m,p  n,m,p</warningarea>
   </job>
   <ui>
      <settings visible="true">
      <filelist visible="true">
      <gps visible="true">
         <northup value="true">
         <usecompass value="true">
      </gps>
      <preferences visible="true">
         <screen visible="true">
         <machine visible="true">
         <login visible="true">
      </preferences>
      <screenblanking value="10">
      <statistics visible="true">
   </ui>
</configuration>

Notes:

• Cycleline, haulpath, and warningarea may have zero or more instances.
• Other values have precisely one entry.

The current thinking is that the server traffics in the XML format, while the client applications have helper objects to deal with it. A model is similar to the Bundle class in Android that lets you do things like:

   boolean gpsIsVisible = config.getBoolean("ui.gps.visible", true);
   double blankspeed = config.getDouble("ui.screenblanking.visible", 37.5);

Helper classes for the config object would be coded for Java and C++.