destiny team mailing list archive

[Ian Crotty <archangel114@xxxxxxxxx>]

This e-mail is mostly for Tom's benefit as he will be my partner in crime on
this last leg of the journey but I wanted everyone to see what will be going
on and so we have an archived record of whats happening.

As Zach mentioned, the linking of all the parts needs to be done.  We have
to be able to launch all of these from one application to the other.  I do
have to make a small change to the SleuthsGUI class and turn it into a
widget rather than a main window.  This should alleviate my previous problem
of launching it.  I would have taken care of this sooner but I've been
otherwise preoccupied with other class work.

In talking to Zach about how to properly get Sleuths to work without hard
coding each scenario, I believe we decided on having XML files for this.
Allow me to elaborate.  Based on which tool you have selected it will flag a
type of interaction, i.e. magnifying glass.  This interaction will then be
linked with something that you interact with on the screen, more than likely
an area listed int he XML file that when clicked on will then output the
desired clue, also stored in an XML file, to the window so the students can
read it.  This ability needs to get added in.  I have the Sleuths docs done
and mapped on and I will go ahead and share them with the rest of you now.
 In sharing them I have given you all write access.  I do ask that any
changes you made please do so in a different color font so I can distinguish
your work from mine.

I will be working on getting more of the functionality of the SleuthsGUI
class.  Tom, if you would please work on getting all of the various elements
together and launchable from each other. The same basic structure still
applies [LoginWindow -> NewAccountDialog -> CharacterCreation -> LoginWindow
-> Menu -> ScenarioSelection -> SleuthsGUI].  Also if you would start
looking into setting up the XML in a way that would be conducive to what we
are doing.  Much thanks.

That is all from me for now I believe.  Have a good night and I'll see some
of you tomorrow.

Ian Crotty
UTS Hardware Technician
Ball State University


On Tue, Feb 23, 2010 at 3:44 PM, Zach Elko <zachelko@xxxxxxxxx> wrote:

> *Zach/Doug - Battleship/Frogger/Installer*
>
> Some things off the top of my head (not a complete list):
>
>    - Frogger needs to start using a state machine to transition between
>    different game modes properly
>    - In-game menus for both games
>    - Battleship needs to start making use of the question manager
>    - The HUD in Battleship needs to be click-able so that they can select
>    which question to attempt
>    - All of the game logic for Battleship needs implemented (shouldn't be
>    much, though)
>    - Ways to install the games need to be explored, tested, and tweaked
>    - Various bug fixes listed in the tracker
>
> *
> Ian/Tom - Sleuths*
>
> Some things off the top of my head (not a complete list):
>
>    - All of the menu functionality needs to work. This includes logging
>    in, avatar creation/editing, scenario selection, returning to the main
>    screen, etc...
>    - Tool selection needs to be implemented
>    - Tool interaction needs to be implemented
>    - Hints need to be gathered and recorded by the game
>    - Various bug fixes listed in the tracker
>
>
>
> *Andy - Bug tracking, Building levels for Frogger, Making question sets
> for Frogger and Battleship*
>
> Some things off the top of my head (not a complete list):
>
>    - Keep hammering away at all applications to find issues, or to come up
>    with suggestions for improvement
>    - Using Doug's level builder, create levels for Frogger with varying
>    enemies and backgrounds
>    - Using Doug's question manager and the text book(s) for the course,
>    come up with some applicable question sets for both Frogger and Battleship,
>    in both Math and English. I advise starting a thread to the list to discuss
>    how we want to attack the English questions and such. It'll be a group
>    decision, but you're responsible for making sure it gets done.
>
>
> *General Stuff*
>
>    - All classes need UML
>    - Updating old classes means updating their UML
>    - All classes need unit tests (always! we're graded on this!)
>    - If you can help someone else out, do so.
>    - Don't disappear. Volunteer your services, ask for help, offer
>    suggestions, file bug/suggestion reports, etc... There is *always* something
>    you could be doing.
>
>
> Zach J. Elko
> Ball State University Unified Technology Support
> Certified Hardware & Software Technician
>
> _______________________________________________
> Mailing list: https://launchpad.net/~destiny
> Post to     : destiny@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~destiny
> More help   : https://help.launchpad.net/ListHelp
>
>