Please update your repo to get the updated version of the example document. A small change was needed.
Zach J. Elko Ball State University Unified Technology Support Certified Hardware & Software Technician On Sat, Mar 13, 2010 at 1:58 PM, Zach Elko <[email protected]> wrote: > O.K., the design for the Tool-Object interactions in Sleuths has been > finalized. > > Every scenario will have an Interactions.xml file associated with it. > > The XML file would be full of <interaction> </interaction> tags. They'll > look like this: > > // Interaction for Tool 1 with Object 1 > <interaction> > <id>1-1</id> > <hint>You find blood on the window.</hint> > </interaction> > > // Interaction for Tool 1 with Object 3 > <interaction> > <id>1-3</id> > <hint>You find a hair under the pillow</hint> > </interaction> > > So, in the game, they will select a tool and that gives us a tool id. Then, > they click on something, that gives us an object id. We put the two together > into the form of toolID-objectID, use that as the lookup into the XML. If > something is found, we give them that hint. If not, the interaction does > nothing. > > Ian, with your scenario documents, you or someone of your choosing should > be able to create these documents with ease for all of the scenarios. Just > keep the tool ids consistent across all scenarios and once you decide on a > numbering of the tools, send out a message to the list showing what they > are. That way, when Doug and I are implementing the parsing within Sleuths, > we'll know which tool is which. > > If anyone has any questions, comments, or suggestions, just let me or > someone else know. > > Zach J. Elko > Ball State University Unified Technology Support > Certified Hardware & Software Technician >
_______________________________________________ Mailing list: https://launchpad.net/~destiny Post to : [email protected] Unsubscribe : https://launchpad.net/~destiny More help : https://help.launchpad.net/ListHelp
