Difference between revisions of "HowTo:Create Application-Specific Help"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 25: Line 25:


===Loading a Specific Page Into the Help Tab===
===Loading a Specific Page Into the Help Tab===
From a button:
When the Help button is clicked, code is invoked to find the Help tab, and effectively, reach an arm out from behind the screen, grab the mouse, and click on that tab!
 
Here is the function that does that:
::<syntaxhighlight lang="javascript" enclose="div">
::<syntaxhighlight lang="javascript" enclose="div">
<script>
<script>
Line 35: Line 37:
</script>
</script>
</syntaxhighlight>
</syntaxhighlight>
::--{{TBD|Show relative URL to get to a JSP page}}
::{{TBD|Show relative URL to get to a JSP page}}


From a link in a displayed page:<br>{{TBD|does a relative link "just work"?}}  
::{{TBD|On click code for the button}}


{{TBD|Needed?}}
:* --To display link-target in the Help tab:
:* --To display link-target in the Help tab:
:: function to search for the iFrame and change the src attribute:
:: function to search for the iFrame and change the src attribute:

Revision as of 22:04, 12 August 2015

WorkInProgress.gif

Work In Progress:
This page is under development.

About Application-Specific Help

The information here in the support wiki is intended primarily for application builders, admins, and installers. But end-users need information that is specific to the application they are using--and that is where application-specific help comes in.

In this article, we assume that you know how to add a button to a form, and that you know how to create an interface tab that displays a single HTML page of information. (The important point is to make sure that your help pages have no headers, so that links work.) With those basics in hand, you can go on to create context-sensitive help pages for your application.

Learn more:

Working with Application-Specific Help

Here, we assume that you want to display different pages, depending on the user's current location--so you'll be wiring help buttons that appear on different forms so they display different pages in the help tab. (You may even use JavaScript to go to different help pages, under different conditions.)

Going to the Help Tab

  • --get the ID of the Web Tab, or inspect the tab element to get iFrame ID
  • --Find the Help tab and use {element}.click to click the tab!
<script>
function goToHelpTab() {
   document.getElementById("...HELP TAB ID...").click();
}
</script>

Loading a Specific Page Into the Help Tab

When the Help button is clicked, code is invoked to find the Help tab, and effectively, reach an arm out from behind the screen, grab the mouse, and click on that tab!

Here is the function that does that:

<script>
function go(loc) {
   var helpTab = document.getElementById('...HELP TAB ID...')
   helpTab.src = loc; // Where the loc is any URL on the web
   helpTab.click;
}
</script>
__TBD: Show relative URL to get to a JSP page__
__TBD: On click code for the button__

__TBD: Needed?__

  • --To display link-target in the Help tab:
function to search for the iFrame and change the src attribute:
onclick() in the anchor to invoke the function and pass target
--loc.href="pages/PAGE_NAME"
--works for pages hosted in the platform
--does not work for external pages (use the external site option, for that)