Product Versions Supported
Points to Hit
The points your demo gets across
Things that may go wrong
- Open index.html and review its contents.
- The bulk of the file is style information, which you can collapse
- The prototype.js and effects.js external script references
- The various named elements: page, sidebar, sidebar-items, content, header, about, about-content, getting-started
- Just before the closing <body> tag, add the following:
<sc^ - to complete <script> and the closing </script> tag
var sb = $("^ - NetBeans provides code-completion for the named elements in the file. Select sidebar.
Effect.^ - look at all the possible effects. Select one such as Fade
- The code should look as follows:
- Refresh the browser and watch the sidebar fade away
Go To Declaration
- Ctrl-click the Fade function to navigate to its declaration in effects.js
- Highlight the element argument to show Mark Occurrences
- Instantly rename the element argument to something else
- Open the Task List to see the warning hints (6 for effects.js at the time of this writing)
- Double-click one such as "Code has no side effects" - this often times just a semi-colon.
- Mouse over the light-bulb to see the balloon tip.
- Delete the semi-colon to clear the warning.
- Show that alt-Enter can be used to disable the hint
- Anywhere effects.js type:
foo = "A String"
bar.^ - show the code-completion for bar - including Prototype methods
bar = foo
bar.^ - Notice how now only String methods are provided.
- Notice the code completion for hasAttribute() has a strike-through and the Internet Explorer icon is grayed out as hasAttribute() isn't supported by IE.
- Return to the code completion for hasAttribute() and notice the strike-through has gone away.
These are the necessary steps to take in order to successfully run the demo again on the same machine.
- Turn IE back on in the Browser Compatibility dialog