https://cse125.ucsd.edu/cse125/2013/cse125g1/api.php?action=feedcontributions&user=Anish&feedformat=atomSpartacats - User contributions [en]2024-03-28T08:22:28ZUser contributionsMediaWiki 1.27.0https://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=652Anish2013-06-04T07:25:04Z<p>Anish: /* Week 10 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Projectile weapons' logic (not committed)<br />
<br />
'''Failed'''<br />
*Didn't have time to finish all weapon logic<br />
*Start another task<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Getting to be great<br />
<br />
== Week 7 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*All weapon logic done<br />
<br />
'''Failed'''<br />
*Testing<br />
*More work<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Great<br />
<br />
== Week 8 ==<br />
'''Goals'''<br />
*Combine all weapon logic<br />
*Test weapons<br />
<br />
'''Accomplished'''<br />
*Weapon logic implemented<br />
*On going testing<br />
<br />
'''Failed'''<br />
*Still buggy<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Good<br />
<br />
== Week 9 ==<br />
'''Goals'''<br />
*Continued testing<br />
*Debugging any other issues<br />
<br />
'''Accomplished'''<br />
* :'(<br />
<br />
'''Failed'''<br />
*Didn't do much<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Family problems and sick<br />
<br />
== Week 10 ==<br />
'''Goals'''<br />
* Testing the game<br />
* Fixing any lingering bugs<br />
<br />
'''Accomplished'''<br />
* A finalized game<br />
<br />
'''Failed'''<br />
* Do or die<br />
<br />
'''Next weeks goals'''<br />
* Summer :D<br />
<br />
'''Morale'''<br />
* Got this!</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=651Anish2013-06-04T07:24:52Z<p>Anish: /* Week 10 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Projectile weapons' logic (not committed)<br />
<br />
'''Failed'''<br />
*Didn't have time to finish all weapon logic<br />
*Start another task<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Getting to be great<br />
<br />
== Week 7 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*All weapon logic done<br />
<br />
'''Failed'''<br />
*Testing<br />
*More work<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Great<br />
<br />
== Week 8 ==<br />
'''Goals'''<br />
*Combine all weapon logic<br />
*Test weapons<br />
<br />
'''Accomplished'''<br />
*Weapon logic implemented<br />
*On going testing<br />
<br />
'''Failed'''<br />
*Still buggy<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Good<br />
<br />
== Week 9 ==<br />
'''Goals'''<br />
*Continued testing<br />
*Debugging any other issues<br />
<br />
'''Accomplished'''<br />
* :'(<br />
<br />
'''Failed'''<br />
*Didn't do much<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Family problems and sick<br />
<br />
== Week 10 ==<br />
'''Goals'''<br />
* Testing the game<br />
* Fixing any lingering bugs<br />
<br />
'''Accomplished'''<br />
* A finalized game<br />
<br />
'''Failed'''<br />
* Do or die<br />
<br />
'''Next weeks goals'''<br />
* Summer!<br />
<br />
'''Morale'''<br />
* Got this!</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=650Anish2013-06-04T07:20:33Z<p>Anish: /* Week 9 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Projectile weapons' logic (not committed)<br />
<br />
'''Failed'''<br />
*Didn't have time to finish all weapon logic<br />
*Start another task<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Getting to be great<br />
<br />
== Week 7 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*All weapon logic done<br />
<br />
'''Failed'''<br />
*Testing<br />
*More work<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Great<br />
<br />
== Week 8 ==<br />
'''Goals'''<br />
*Combine all weapon logic<br />
*Test weapons<br />
<br />
'''Accomplished'''<br />
*Weapon logic implemented<br />
*On going testing<br />
<br />
'''Failed'''<br />
*Still buggy<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Good<br />
<br />
== Week 9 ==<br />
'''Goals'''<br />
*Continued testing<br />
*Debugging any other issues<br />
<br />
'''Accomplished'''<br />
* :'(<br />
<br />
'''Failed'''<br />
*Didn't do much<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Family problems and sick<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=649Anish2013-06-04T07:20:07Z<p>Anish: /* Week 9 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Projectile weapons' logic (not committed)<br />
<br />
'''Failed'''<br />
*Didn't have time to finish all weapon logic<br />
*Start another task<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Getting to be great<br />
<br />
== Week 7 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*All weapon logic done<br />
<br />
'''Failed'''<br />
*Testing<br />
*More work<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Great<br />
<br />
== Week 8 ==<br />
'''Goals'''<br />
*Combine all weapon logic<br />
*Test weapons<br />
<br />
'''Accomplished'''<br />
*Weapon logic implemented<br />
*On going testing<br />
<br />
'''Failed'''<br />
*Still buggy<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Good<br />
<br />
== Week 9 ==<br />
'''Goals'''<br />
*Continued testing<br />
*Debugging any other issues<br />
<br />
'''Accomplished'''<br />
*:'(<br />
<br />
'''Failed'''<br />
*Didn't do much<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Family problems and sick<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=648Anish2013-06-04T07:14:22Z<p>Anish: /* Week 8 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Projectile weapons' logic (not committed)<br />
<br />
'''Failed'''<br />
*Didn't have time to finish all weapon logic<br />
*Start another task<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Getting to be great<br />
<br />
== Week 7 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*All weapon logic done<br />
<br />
'''Failed'''<br />
*Testing<br />
*More work<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Great<br />
<br />
== Week 8 ==<br />
'''Goals'''<br />
*Combine all weapon logic<br />
*Test weapons<br />
<br />
'''Accomplished'''<br />
*Weapon logic implemented<br />
*On going testing<br />
<br />
'''Failed'''<br />
*Still buggy<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Good<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=559Anish2013-05-21T06:25:32Z<p>Anish: /* Week 7 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Projectile weapons' logic (not committed)<br />
<br />
'''Failed'''<br />
*Didn't have time to finish all weapon logic<br />
*Start another task<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Getting to be great<br />
<br />
== Week 7 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*All weapon logic done<br />
<br />
'''Failed'''<br />
*Testing<br />
*More work<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Great<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=558Anish2013-05-21T06:25:13Z<p>Anish: /* Week 7 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Projectile weapons' logic (not committed)<br />
<br />
'''Failed'''<br />
*Didn't have time to finish all weapon logic<br />
*Start another task<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Getting to be great<br />
<br />
== Week 7 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*All weapon logic done<br />
<br />
'''Failed'''<br />
*None<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Great<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=507Anish2013-05-14T09:19:29Z<p>Anish: /* Week 6 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
'''Goals'''<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Projectile weapons' logic (not committed)<br />
<br />
'''Failed'''<br />
*Didn't have time to finish all weapon logic<br />
*Start another task<br />
<br />
'''Next weeks goals'''<br />
*TBD<br />
<br />
'''Morale'''<br />
*Getting to be great<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=506Anish2013-05-14T08:52:18Z<p>Anish: /* Week 5 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this week. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
TBD<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=427Anish2013-05-07T09:18:09Z<p>Anish: /* Week 5 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons' logic<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
*Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this weekend. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
TBD<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=426Anish2013-05-07T09:16:23Z<p>Anish: /* Week 5 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
'''Goals'''<br />
*Armor implementation<br />
*Understand weapon logic<br />
**Weapons themselves<br />
**Class structure<br />
*Hammer out details for each weapon<br />
*Complete weapon logic for all weapons<br />
<br />
'''Accomplished'''<br />
*Armor to be put on hold<br />
*Understanding of weapons and weapon systems<br />
*Most projectile weapons<br />
<br />
'''Failed'''<br />
*Didn't complete all weapons' logic<br />
**Still some questions around specific weapon properties<br />
<br />
'''Next weeks goals'''<br />
*Finish weapon logic<br />
*Help out anywhere else<br />
**Start screen<br />
<br />
'''Morale'''<br />
*Moving forward. Be harder to work this weekend. I will be in Texas for cousin's wedding<br />
<br />
== Week 6 ==<br />
TBD<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=350Logging2013-04-30T18:56:25Z<p>Anish: /* Initialize */</p>
<hr />
<div>===Levels===<br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
===Functions===<br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
===Include===<br />
The beginning of each file should have: <br/><br />
<br />
#include "../LibLogger/liblogger.h"<br />
#include "../LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
===Initialize===<br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
ZeroMemory(&fileInitParams, sizeof(tFileLoggerInitParams));<br />
fileInitParams.fileName = L"Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile, &fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
===Deinitializing===<br />
DeInitLogger()<br />
<br/><br />
<br />
===Control Logging===<br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
===Example===<br />
'''file.cpp:'''<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry(L"main");<br />
LogDebug(L" Debug message... ");<br />
LogInfo (L" int val = %d ", 9);<br />
// ......<br />
LogFatal(L" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry(L"main", 10);<br />
DeInitLogger();<br />
return 0;<br />
}<br />
<br/><br />
'''Log output:'''<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
===More Information===<br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=349Logging2013-04-30T18:56:13Z<p>Anish: /* Example */</p>
<hr />
<div>===Levels===<br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
===Functions===<br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
===Include===<br />
The beginning of each file should have: <br/><br />
<br />
#include "../LibLogger/liblogger.h"<br />
#include "../LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
===Initialize===<br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
ZeroMemory(&fileInitParams, sizeof(tFileLoggerInitParams));<br />
fileInitParams.fileName = "Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile, &fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
===Deinitializing===<br />
DeInitLogger()<br />
<br/><br />
<br />
===Control Logging===<br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
===Example===<br />
'''file.cpp:'''<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry(L"main");<br />
LogDebug(L" Debug message... ");<br />
LogInfo (L" int val = %d ", 9);<br />
// ......<br />
LogFatal(L" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry(L"main", 10);<br />
DeInitLogger();<br />
return 0;<br />
}<br />
<br/><br />
'''Log output:'''<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
===More Information===<br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=348Logging2013-04-30T18:44:50Z<p>Anish: /* Initialize */</p>
<hr />
<div>===Levels===<br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
===Functions===<br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
===Include===<br />
The beginning of each file should have: <br/><br />
<br />
#include "../LibLogger/liblogger.h"<br />
#include "../LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
===Initialize===<br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
ZeroMemory(&fileInitParams, sizeof(tFileLoggerInitParams));<br />
fileInitParams.fileName = "Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile, &fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
===Deinitializing===<br />
DeInitLogger()<br />
<br/><br />
<br />
===Control Logging===<br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
===Example===<br />
'''file.cpp:'''<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
DeInitLogger();<br />
return 0;<br />
}<br />
<br/><br />
'''Log output:'''<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
===More Information===<br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=347Logging2013-04-30T18:43:59Z<p>Anish: /* Include */</p>
<hr />
<div>===Levels===<br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
===Functions===<br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
===Include===<br />
The beginning of each file should have: <br/><br />
<br />
#include "../LibLogger/liblogger.h"<br />
#include "../LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
===Initialize===<br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
ZeroMemory(&fileInitParams, sizeof(tFileLoggerInitParams));<br />
fileInitParams.fileName = L"Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile, &fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
===Deinitializing===<br />
DeInitLogger()<br />
<br/><br />
<br />
===Control Logging===<br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
===Example===<br />
'''file.cpp:'''<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
DeInitLogger();<br />
return 0;<br />
}<br />
<br/><br />
'''Log output:'''<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
===More Information===<br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=346Logging2013-04-30T18:41:18Z<p>Anish: /* Example */</p>
<hr />
<div>===Levels===<br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
===Functions===<br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
===Include===<br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
===Initialize===<br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
ZeroMemory(&fileInitParams, sizeof(tFileLoggerInitParams));<br />
fileInitParams.fileName = L"Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile, &fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
===Deinitializing===<br />
DeInitLogger()<br />
<br/><br />
<br />
===Control Logging===<br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
===Example===<br />
'''file.cpp:'''<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
DeInitLogger();<br />
return 0;<br />
}<br />
<br/><br />
'''Log output:'''<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
===More Information===<br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=345Logging2013-04-30T18:28:34Z<p>Anish: /* Example */</p>
<hr />
<div>===Levels===<br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
===Functions===<br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
===Include===<br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
===Initialize===<br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
ZeroMemory(&fileInitParams, sizeof(tFileLoggerInitParams));<br />
fileInitParams.fileName = L"Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile, &fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
===Deinitializing===<br />
DeInitLogger()<br />
<br/><br />
<br />
===Control Logging===<br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
===Example===<br />
'''file.cpp:'''<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry(L"main");<br />
LogDebug(L" Debug message... ");<br />
LogInfo (L" int val = %d ", 9);<br />
// ......<br />
LogFatal(L" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry(L"main", 10);<br />
DeInitLogger();<br />
return 0;<br />
}<br />
<br/><br />
'''Log output:'''<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
===More Information===<br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=344Logging2013-04-30T18:28:25Z<p>Anish: /* Example */</p>
<hr />
<div>===Levels===<br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
===Functions===<br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
===Include===<br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
===Initialize===<br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
ZeroMemory(&fileInitParams, sizeof(tFileLoggerInitParams));<br />
fileInitParams.fileName = L"Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile, &fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
===Deinitializing===<br />
DeInitLogger()<br />
<br/><br />
<br />
===Control Logging===<br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
===Example===<br />
'''file.cpp:'''<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry(L"main");<br />
LogDebug(L" Debug message... ");<br />
LogInfo (L" int val = %d ", 9);<br />
// ......<br />
LogFatal(L" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry(L"main", 10);<br />
DeInitLogger()<br />
return 0;<br />
}<br />
<br/><br />
'''Log output:'''<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
===More Information===<br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=338Anish2013-04-30T05:24:22Z<p>Anish: /* Week 4 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
'''Goals'''<br />
*Study for and pass my MS Comprehensive Exam<br />
<br />
'''Accomplished'''<br />
*TOOK THE EXAM!<br />
*Recovered<br />
<br />
'''Failed'''<br />
*Hopefully not the exam<br />
<br />
'''Next weeks goals'''<br />
*Fine tuning log messages<br />
*Want to be much more involved<br />
**Looking at Weapon Logic<br />
<br />
'''Morale'''<br />
*GREAT! I'm full speed ahead for 20 DPS<br />
<br />
== Week 5 ==<br />
TBD<br />
<br />
== Week 6 ==<br />
TBD<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=285Logging2013-04-23T06:57:14Z<p>Anish: /* Logging */</p>
<hr />
<div>===Levels===<br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
===Functions===<br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
===Include===<br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
===Initialize===<br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
memset(&fileInitParams,0,sizeof(tFileLoggerInitParams)); <br />
fileInitParams.fileName = "Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile,&fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
===Deinitializing===<br />
DeInitLogger()<br />
<br/><br />
<br />
===Control Logging===<br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
===Example===<br />
'''file.cpp:'''<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
return 0;<br />
}<br />
<br/><br />
'''Log output:'''<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
===More Information===<br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=284Logging2013-04-23T06:54:45Z<p>Anish: /* Logging */</p>
<hr />
<div>== Logging ==<br />
'''Levels'''<br/><br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
<br />
'''Functions'''<br/><br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
'''Include'''<br/><br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
'''Initialize'''<br/><br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
memset(&fileInitParams,0,sizeof(tFileLoggerInitParams)); <br />
fileInitParams.fileName = "Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile,&fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
'''Deinitializing''' <br/><br />
DeInitLogger()<br />
<br/><br />
<br />
'''Control Logging''' <br/><br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br/><br />
<br />
'''Example:''' <br/><br />
file.cpp:<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
return 0;<br />
}<br />
<br/><br />
Log output:<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br/><br />
<br />
'''More Information'''<br/><br />
LibLogger Main Page: http://liblogger.sourceforge.net/main.html <br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=283Logging2013-04-23T06:52:53Z<p>Anish: /* Logging */</p>
<hr />
<div>== Logging ==<br />
'''Levels'''<br/><br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
'''Functions'''<br/><br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
'''Include'''<br/><br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br />
'''Initialize'''<br/><br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
memset(&fileInitParams,0,sizeof(tFileLoggerInitParams)); <br />
fileInitParams.fileName = "Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile,&fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
'''Deinitializing''' <br/><br />
DeInitLogger()<br />
<br/><br />
<br />
'''Control Logging''' <br/><br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br />
<br />
'''Example:''' <br/><br />
file.cpp:<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
return 0;<br />
}<br />
<br/><br />
Log output:<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br />
<br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=282Logging2013-04-23T06:50:14Z<p>Anish: /* Logging */</p>
<hr />
<div>== Logging ==<br />
'''Levels'''<br/><br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is at the Trace level <br/><br />
<br/><br />
'''Functions'''<br/><br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
'''Include'''<br/><br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
'''Initialize'''<br/><br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
memset(&fileInitParams,0,sizeof(tFileLoggerInitParams)); <br />
fileInitParams.fileName = "Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile,&fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
'''Deinitializing''' <br/><br />
DeInitLogger()<br />
<br/><br />
<br />
'''Control Logging''' <br/><br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br />
<br />
Example:<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
return 0;<br />
}<br />
<br/><br />
Output:<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br />
<br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=281Logging2013-04-23T06:49:54Z<p>Anish: /* Logging */</p>
<hr />
<div>== Logging ==<br />
'''Levels'''<br/><br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is on the Trace level <br/><br />
<br/><br />
'''Functions'''<br/><br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
'''Include'''<br/><br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
'''Initialize'''<br/><br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
memset(&fileInitParams,0,sizeof(tFileLoggerInitParams)); <br />
fileInitParams.fileName = "Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile,&fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
'''Deinitializing''' <br/><br />
DeInitLogger()<br />
<br/><br />
<br />
'''Control Logging''' <br/><br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br />
<br />
Example:<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
return 0;<br />
}<br />
<br/><br />
Output:<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br />
<br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Logging&diff=280Logging2013-04-23T06:49:35Z<p>Anish: Created page with "== Logging == '''Levels'''<br/> There are 6 levels in logging: # Fatal # Error # Warning # Info # Debug # Trace #*Function Messages should be appropriately set to the correct..."</p>
<hr />
<div>== Logging ==<br />
'''Levels'''<br/><br />
There are 6 levels in logging:<br />
# Fatal<br />
# Error<br />
# Warning<br />
# Info<br />
# Debug<br />
# Trace<br />
#*Function<br />
<br />
Messages should be appropriately set to the correct level as logging levels can be turned on and off from a header file.<br/><br />
NOTE: Function logging is on the Trace level <br/><br />
<br/><br />
'''Functions'''<br/><br />
int ''LogTrace'' (const char *fmt,...) <br/><br />
int ''LogDebug'' (const char *fmt,...) <br/><br />
int ''LogInfo'' (const char *fmt,...) <br/><br />
int ''LogWarn'' (const char *fmt,...) <br/><br />
int ''LogError'' (const char *fmt,...) <br/><br />
int ''LogFatal'' (const char *fmt,...) <br/><br />
int ''FuncLogEntry'' (const char *funcName) <br/><br />
int ''FuncLogExit'' (const char *funcName, const int lineNumber) <br/><br />
<br/><br />
For each logging function, you simply put what you would normally for printf(). <br/><br />
For FuncLog, put the name of the function and for FuncLogExit, lineNumber is the line number the function exited on. <br/><br />
In the log, the name of the function will show up along with '{' for the reader to know all messages after are from within the function until '}' is seen. <br/><br />
<br/><br />
<br />
'''Include'''<br/><br />
The beginning of each file should have: <br/><br />
<br />
#include "../Shared/LibLogger/liblogger.h"<br />
#include "../Shared/LibLogger/file_logger.h"<br />
<br />
As well, any file where the log is initialized needs to include: <br/><br />
#include <memory.h><br />
<br/><br />
<br />
'''Initialize'''<br/><br />
The following code is used to initialize the logger: <br />
tFileLoggerInitParams fileInitParams;<br />
memset(&fileInitParams,0,sizeof(tFileLoggerInitParams)); <br />
fileInitParams.fileName = "Logs/LOGNAME.log"; <br />
fileInitParams.fileOpenMode = AppendMode; <br />
InitLogger(LogToFile,&fileInitParams);<br />
<br/><br />
The logs will be stored in the folder "Resources/Logs" <br/><br />
If you would like to see a new set of logs each time (overwrite all previous logs) omit the line with 'AppendMode'. <br/><br />
<br/><br />
<br />
'''Deinitializing''' <br/><br />
DeInitLogger()<br />
<br/><br />
<br />
'''Control Logging''' <br/><br />
You can attach a Module Name to logs by associating files under a module name in a header file. This allows you to also control the level of logs that show up if any at all. <br/><br />
More information can be found [http://liblogger.sourceforge.net/PAGE_MODULE_NAME.html here]. <br/><br />
<br />
<br />
Example:<br />
int main(int argc, char** argv)<br />
{<br />
FuncLogEntry("main");<br />
LogDebug(" Debug message... ");<br />
LogInfo (" int val = %d ", 9);<br />
// ......<br />
LogFatal(" Fatal error has occured, ptr %#x ", 0XABCD );<br />
// .... other log functions. ........<br />
FuncLogEntry("main", 10);<br />
return 0;<br />
}<br />
<br/><br />
Output:<br />
----- Logging Started on 04/20/13 17:27:40 -----<br />
{ main<br />
[D]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:4: Debug message...<br />
[I]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:5: int val = 9<br />
[F]:c:\users\me\documents\ucsd 12-13\liblogger-0.2\liblogger\src\testapp\file.cpp:main:7: Fatal error has occured, ptr OXABCD<br />
main : 10 }<br />
<br />
<br/><br />
LibLogger Tutorial: http://liblogger.sourceforge.net/page_tutorial.html</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Main_Page&diff=279Main Page2013-04-23T05:40:41Z<p>Anish: /* Project Development */</p>
<hr />
<div>[[file:Takingdamage.png|thumb|250px|Weekly Screenshot]]<br />
<br />
== About the Game ==<br />
[[Description]]<br />
<br />
[[Features]]<br />
<br />
[[Controls]]<br />
<br />
== Design ==<br />
[[Design Ideas]]<br />
<br />
== Art ==<br />
[[Concept Art]]<br />
<br />
[[Object Models]]<br />
<br />
[[Terrain Models]]<br />
<br />
== Project Development ==<br />
[[Group Management]]<br />
<br />
[[Development Roles]]<br />
<br />
[[Tools]]<br />
<br />
[[Testing]]<br />
<br />
[[Documentation]]<br />
<br />
[[Logging]]<br />
<br />
== Schedule ==<br />
=== Progress Screenshots ===<br />
[[Progress Screenshots]]<br />
<br />
=== Milestones ===<br />
[[High Level View]]<br />
<br />
[[Weekly View]]<br />
<br />
=== Group Reports ===<br />
[[Group Reports]]<br />
<br />
=== Individual Reports ===<br />
[[Amer]]<br />
<br />
[[Anish]]<br />
<br />
[[Erik]]<br />
<br />
[[Helen]]<br />
<br />
[[Jimmy]]<br />
<br />
[[Nico]]<br />
<br />
[[Stephanie]]<br />
<br />
[[Theresa]]</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=278Anish2013-04-23T05:40:06Z<p>Anish: </p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*Wiki page on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
TBD<br />
<br />
== Week 5 ==<br />
TBD<br />
<br />
== Week 6 ==<br />
TBD<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=273Anish2013-04-23T04:22:22Z<p>Anish: /* Week 3 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
'''Goals'''<br />
*Implement logging functionality<br />
*Provide team STRAIGHT FORWARD logging instructions <br />
<br />
'''Accomplished'''<br />
*Got liblogger up and running within our project<br />
**Edited necessary files to fit our project<br />
**Required working with dev to fix VS2012 issues<br />
*PowerPoint on how to use logging tool<br />
<br />
'''Failed'''<br />
*To do more :(<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Not well - MS Comprehensive Exam Saturday eating up all my time<br />
<br />
== Week 4 ==<br />
TBD<br />
<br />
== Week 5 ==<br />
TBD<br />
<br />
== Week 6 ==<br />
TBD<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=215Anish2013-04-16T09:14:02Z<p>Anish: /* Week 2 */</p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Understand server-side logic and client-side interactions<br />
*Investigate and determine best logging method<br />
*Implement logging functionality<br />
<br />
'''Accomplished'''<br />
*Better understanding of server logic and requirements (definitely more known unknowns)<br />
*Logging:<br />
**Visual Studio built in logging investigation - better for build, not run-time<br />
**Standard C++ printing using cerr sent to log file - messy, no levels, hard to disable<br />
**Liblogger library is 3rd party logging library with ability to log to console, file, and server - levels, clean, group capabilities<br />
<br />
'''Failed'''<br />
*Have not implemented logging - problem with including it with our project in VS (Have contacted developer and waiting for response)<br />
*Fallen behind on recent server-side implementations<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*Things are getting complicated fast and have to work harder to keep up, but good progress is being made<br />
<br />
== Week 3 ==<br />
TBD<br />
<br />
== Week 4 ==<br />
TBD<br />
<br />
== Week 5 ==<br />
TBD<br />
<br />
== Week 6 ==<br />
TBD<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anishhttps://cse125.ucsd.edu/2013/cse125g1/index.php?title=Anish&diff=208Anish2013-04-16T08:30:33Z<p>Anish: </p>
<hr />
<div>== Week 2 ==<br />
'''Goals'''<br />
*Simple DummyClient-EchoServer network<br />
*Integrate EchoServer with RealClient<br />
<br />
'''Accomplished'''<br />
*Client Server communication protocol detailed<br />
*Multiple clients on server<br />
*Simple RealServer to let Client move using logic on server<br />
*Simple UFO movement physics<br />
<br />
'''Failed'''<br />
*Have not implemented disconnect and timeout for clients.<br />
<br />
'''Next weeks goals'''<br />
*Don't know yet<br />
<br />
'''Morale'''<br />
*It's going well. <br />
<br />
== Week 3 ==<br />
TBD<br />
<br />
== Week 4 ==<br />
TBD<br />
<br />
== Week 5 ==<br />
TBD<br />
<br />
== Week 6 ==<br />
TBD<br />
<br />
== Week 7 ==<br />
TBD<br />
<br />
== Week 8 ==<br />
TBD<br />
<br />
== Week 9 ==<br />
TBD<br />
<br />
== Week 10 ==<br />
TBD</div>Anish