So if you change a passage and click a button, an event PassageChanged might fire.
The ScriptureDisplay module might be listening and then it would fire off to JSword an event saying "I need a new passage please". At the same time the history module would fire off an event saying "A new list of articles is required for this new scripture reference". After a short while 2 events would come back, one saying "Here's the new passage" and one saying "here's the new list of articles".
The second of these might be of interest to the ScriptureModule and it would be listening for it. "There's a new list of articles, therefore I can try highlighting some different things in the passage".
etc.
Does that make sense?
Chris
2009/9/30 Tyndale STEP Project <TyndaleSTEP@gmail.com>
Chris, your Event-driven approach sounds fantastic. If I understand
it correctly, this means all the responses can be driven by keyboard
and selection, without totally rewriting the page, and it provides a
quick-n-easy method for providing drop-down suggestion lists when
someone starts typing. Have I understood correctly?David IB
--
Posted By Tyndale STEP Project to Tyndale STEP - Programming on 9/30/2009 02:57:00 AM
No comments:
Post a Comment