Hi Shaun, In answer to your question a developer should use neither approach. Instead, it is best for a developer to draft a design document long before he/she writes the first line of code. He/she will already have sounds, graphics, and speech ready to go and begin joining them with the code. In other wordsfully plan out what sounds go with what graphics, and answerhow much memory is needed, what is esentual and not esentual, make accessibility and graphics both a priority, and during the design faze blend them together as best as possible.
shaun everiss wrote: > It then brings up an interesting question. > Do we either > 1. make the games accessible for the blind then add graphics, or get > 2 the graphical parts done and try and match graphics with music, sfx > and speech. > The second probably is harder but better, ofcause you would have fun > matching everything up. > Probably you could have user contests on matching up said graphics > with sounds, and all could do that. > A text file with descriptions for those that have no sight and > graphics for those that do have sight. > Would be interesting on what the sighted and non sighted people would > think of what sounds for different events were. > _______________________________________________ Gamers mailing list .. [email protected] To unsubscribe send E-mail to [EMAIL PROTECTED] You can visit http://audyssey.org/mailman/listinfo/gamers_audyssey.org to make any subscription changes via the web.
