Navigation
BMP provides the following built-in events for navigating your answerSpace.
A more future-proof, maintainable, and easier scheme would look like:
Link Type | Description |
---|---|
<a keyword="k1" ...> | link to K1</a> // for backwards compatibility only |
<a interaction="myinteraction" ...> | link to myinteraction</a> |
<a category="mycategory" ...> | link to mycategory</a> |
<a masterCategory="mymastercategory" ...> | link to mymastercategory</a> |
<a back> | go back</a> |
<a home> | go home</a> |
<a login> | go to login</a> |
Passing Arguments
When encountered, these links should be post-processed so that they perform as expected when the user clicks them.
Here's an example with an $args[0] being passed:
<a interaction="nextInteraction" _0="myArgument">Next Interaction</a>
Note that you don't actually type "args" in the link, you just type an underscore (_) and anything after that will be the key in the $args array.
Note that you do need to be careful with quotes, but then you always had to be careful with quotes. If there are double-quotes in your argument string, then enclose the argument in single-quotes, and vice versa.
Javascript Events
Available Functions
goBackTocategoriesView();goBackToHome(); goBackToKeywordListView(); goBackToKeywordView(); goBackToMasterCategoriesView(); goBackToTopLevelAnswerView(); // note - these functions require arguments showAnswerView(); showCategoriesView(); showLoginView(); showSecondLevelAnswerView();