Copyright Notice

The material presented in this site, including any documents, design, text, or information available for viewing or downloading, and within the restrictions and rights imposed by Google, is the copyrighted work of ECE 465 Group 1. Any copying or duplication of site surely constitutes a violation of the GMU honor code, and these activities will be punished to the maximum extent allowed by the GMU Honor Committee. By viewing this site and/or notice, you consent to monitoring and reporting of your browsing activities.  Group 1 reserves the right to immediately alert intelligence agencies of your activities, and you will be subjected to extraordinary rendition or be tried in a military tribunal, unless our ECE 465 professor pleads on your behalf and decides that another reasonable course of action is appropriate.

584days since
Project Presentation

Home‎ > ‎Project Issues‎ > ‎

JTree and threading

posted Mar 23, 2008 12:20 PM by Brandon Thomson   [ updated Apr 4, 2008 10:30 AM by WERNER DUBON ]
Currently the JTree for statistics display has been implemented, but based per our principal software developer, the implementation is extremely messy because we did not look up the appropriate way to do it and simply made a class called "LocalStatisticsContainer" that holds all the data and the tree nodes.

The principal software developer is beginning to regret implementing this project in Java. Ruby would have been a better choice.

He has not been very disciplined about creating threads, and instead opted for a random approach. As a result there are a lot of corner cases that will put the application in an undesirable state. Actually at the moment there are a lot of obvious cases that will put the application in an undesirable state.
Our team lead estimates that we are about 45% done with phases 2 and 3 of the project code.

 
This screenshot gives you an idea of threading and statistics implementation.