MACROMEDIA CONTRIBUTE 3-DEPLOYING CONTRIBUTE Guida Utente Pagina 95

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 142
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 94
NavMap
Components User's Guide
95
select
property, which limits the navigation buttons to only those assets to which the
indexfile
metadata field is assigned and set to
Yes
.
NavMap
The NavMap component retrieves information about each node in a site structure, which
you can then use to generate navigation menus to those nodes. You can define any HTML
or JavaScript in the NavMap component, which will then be generated for every node in
the structure when you preview or deploy the asset that contains the component.
How the NavMap Component Works
The NavMap component can store any combination of HTML and JavaScript (or other
standard markup), which will be repeatedly generated for each node in a particular site
structure. The code that the component generates for each node can include any of the
following properties, which are defined in the component as data field macros:
The node name
, which is also the asset name
You can use this to insert the name of the target asset on a navigation button. To
insert the asset name, the component must include the
$node.name
macro. When
you preview or deploy the component, Collage replaces
$node.name
with the actual
asset name.
The URL to the node
, relative to the HTML file that contains the component
You can use the node URL to generate the link to the asset, from a navigation button.
To insert the url, the component must include the
$node.url
macro. When you
preview or deploy the component, Collage replaces
$node.url
with the actual path to
the asset.
The level in the site structure
to which the node belongs
You can use the level value, in combination with custom JavaScripts or other logic, to
define unique behavior or formatting for navigation links to nodes at different levels in
<nexus:component classid="nexus/components/Navbar"
code="$nexusComponents" nodes="Current CurrentLevel
ParentLevel" display="vertical" navigation="pubfolders"
select="indexfile" root="/Website/Content"
orderbycode="1AN" orderonmetadata="Priority">
<node:active>
[<a href="$node.url">$node.name</a>]
</node:active>
<node:inactive>
[<a href="$node.url">$node.name</a>]
</node:inactive>
</nexus:component>
Navigation buttons will
be ordered first by the
Priority metadata field,
in ascending order, and
then by the asset name
Priority metada field
can be used to order
navigation buttons
Vedere la pagina 94
1 2 ... 90 91 92 93 94 95 96 97 98 99 100 ... 141 142

Commenti su questo manuale

Nessun commento