Software Organization

Documenting here the state of EXES software as Andreas heads off to greener pastures:

-  Best source of documentation is Andreas' Software Development Guide, filename 'EXES_software_development_guide_DRAFT.pdf'.  I've copied this file to the SaltLick server in the EXES lab, under the /Doc directory, and also on NSCKN under '5.0 Payload>Software>GUI'  Andreaas also provided a primer on using the svn repos, and that has been copied to SaltLick as well.


-  Our source code (both java and c++) are under subversion control at http://app.devzing.com/exes/subversion/ .  Presently Andreas, Matt, Curtis and I are able to access the subversion repositories.  If anyone else needs access, I have the admin login and can create new accounts.


-  Following Andreas' instruction, I have installed NetBeans on the Mac Mini in the EXES lab, and linked it with the subversion (svn) repository containing the java code.  After doing so I am able to build the GUI from source code on both the mac mini and on my linux machine.  I've verified that I can also make and check in software changes to the repository.


-  On the PC side, I have modified the directory structure on the host PC so that the development version of the code is written to C:\exesV2.  The current (~stable) version of the EXES software is in the C:\exes folder.  Once we are ready to 'release' EXES 2.0, I'll archive the present C:\exes folder and rename exesV2 to C:\exes, so that the latest stable release can always be found there.  We'll keep the MGT pointed into that folder as well, so that to run anything other than the latest release you'll have to dig for it a bit.


-  The Tortoise svn client Andreas installed for us now points to our svn repositories.  Only the \src and \build subfolders are synchronized.  In general, the \build directory needn't be updated via svn, as that will upload a bunch of uninteresting.obj files.  The \src directory should be kept up to date.


After setting this up, I checked out the code and then built a new version of the c++ app exes.exe.  Building this app places it in the \build directory, but we move it up to the next level directory (alongside \src and \build) to run.  At this point we are able to build new versions of the c++ and java gui from source, and I've verified that they work together.  I need to read more to understand the limitations of the development versions, but I plan to start using them going forward.