TrackTrek: Difference between revisions
Jump to navigation
Jump to search
(New page: TrackTrek was meant to be a track meet data entry and reporting application, but did not get far due to being sparsely developed for free over one and a half years. At the time, I did not ...) |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
TrackTrek was meant to be a track meet data entry and reporting application, but did not get far due to being sparsely developed for free over one and a half years. | TrackTrek was meant to be a track meet data entry and reporting application, but it did not get far due to being sparsely developed for free over one and a half years. I was in high school at the time, and I did not have sufficient experience with requirements elicitation, scoping, and budgeting, leading to the eventual abandonment of the project. Fortunately, the project did expose me to {{Tech:Java}} programming as well as its [http://en.wikipedia.org/wiki/Abstract_Window_Toolkit abstract window toolkit (AWT)] and socket networking capabilities. | ||
This project was developed using [http://en.wikipedia.org/wiki/Visual_J%2B%2B Microsoft Visual J++], which permitted the [http://en.wikipedia.org/wiki/Class_file Java class files] to be compiled into [http://en.wikipedia.org/wiki/Portable_Executable EXE files] for use with Microsoft's Java virtual machine, which is now defunct. | |||
==Download== | ==Download== | ||
Latest revision as of 14:36, 14 October 2007
TrackTrek was meant to be a track meet data entry and reporting application, but it did not get far due to being sparsely developed for free over one and a half years. I was in high school at the time, and I did not have sufficient experience with requirements elicitation, scoping, and budgeting, leading to the eventual abandonment of the project. Fortunately, the project did expose me to Java programming as well as its abstract window toolkit (AWT) and socket networking capabilities.
This project was developed using Microsoft Visual J++, which permitted the Java class files to be compiled into EXE files for use with Microsoft's Java virtual machine, which is now defunct.
