| Child pages (Children Display)toc | |
|---|---|
|
|
Navigation
In order to avoid future issues with links, and to facilitate better navigation around answerSpaces, it would be desirable to implement a unified scheme for hyperlinks.
Currently, users are coached to build links that work in the static client, and these links are (sometimes clumsily) converted into JavaScript calls in the dynamic client.
A more future-proof, maintainable, and easier scheme would look like:
<a keyword="k1" ...>link to K1</a> // for backwards compatibility only
<a interaction="i1" ...>link to I1</a>
<a category="c1" ...>link to C1</a>
<a masterCategory="m1" ...>link to M1</a>
<a back>go back</a>
<a home>go home</a>
<a login>go to login</a>
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.
...
|