Difference between revisions of "Setting Up a MIRC Development Environment"
Jump to navigation
Jump to search
(Created page with "<b>UNDER CONSTRUCTION</b> This article describes the development environment that was used to develop the MIRC software, including CTP and TFS. It is not the only way that it co...") |
|||
| Line 4: | Line 4: | ||
There are three key modules in the MIRC software: | There are three key modules in the MIRC software: | ||
| − | * <b><tt>Util</tt></b> contains the embedded server, common servlets, and a | + | * <b><tt>Util</tt></b> contains the embedded server, common servlets, and a collection of utility classes. |
* <b><tt>CTP</tt></b> contains the CTP application, including. | * <b><tt>CTP</tt></b> contains the CTP application, including. | ||
* <b><tt>MIRC</tt></b> contains the CTP plugin that implements the teaching file system. | * <b><tt>MIRC</tt></b> contains the CTP plugin that implements the teaching file system. | ||
Revision as of 14:20, 13 December 2012
UNDER CONSTRUCTION
This article describes the development environment that was used to develop the MIRC software, including CTP and TFS. It is not the only way that it could have been done, and it is certainly not a sophisticated approach; it is just the way that I did it. The intended audience for this article is software engineers who are extending or maintaining the code.
There are three key modules in the MIRC software:
- Util contains the embedded server, common servlets, and a collection of utility classes.
- CTP contains the CTP application, including.
- MIRC contains the CTP plugin that implements the teaching file system.
All the software is available on GitHub at https://github.com/johnperry.
The best approach is to fork the Util, CTP, and MIRC2 repositories and check out the code onto your development system.
Each module has an Ant build.xml file to build it. The build files expect a directory structure like this:
- Development
- Util
- CTP
- MIRC2