If you are just exploring the existing defined behaviors in FP2003, easiest way is to experiment by applying them to elements in a
page
- the events and response associated w/ it are preset in the behavior definition files (the .htm and associated .js file)
For more detail you can browse the actual files used (do not edit them)
The predefined default ones are stored in:
C:\Program Files\Microsoft Office\Templates\1033\Behaviors11\ACTIONS
For example the Popup one uses POPUPMSG.HTM and POPUPMSG.JS
An article on creating or modifying the behaviors is in works and should be published (and announced here) before the end of the
month
| Hi Jon,
|
| Just trying to learn. I'm not even at the eperimental stage. Until I can see
| how something can be used it's very hard for me to beging thinking of a
| situation where I might apply it. I hope that makes sense. Thanks for your
| reply.
| | > Hi Gary,
| > a behaviour takes some action in response to an event. An event could be
| the
| > page loading, or the user moving his mouse over something/clicking
| something
| > etc.
| >
| > For example here's how one the behaviours (Popup message) would work
| >
| > <p onmouseover="FP_popUpMsg('mouse over event caused message popup
| > action')">some text</p>
| >
| > when you mouseover the text (event) a message pops up (action.) FP will
| > automatically add the script for this to the head of your page. Note -
| this
| > would fail in NN4. It only allows behaviours to be added to links - every
| > other browser gets it right.
| >
| > Did you have a specific task in mind or are you just experimenting?
| >
| > --
| > Cheers,
| > Jon
| > Microsoft MVP - FP
| >
| > | > > Has anyone written a tutorial regarding the Behaviors in 2003? I think
| the
| > > Behaviors are probably pretty flexible/powerful in but I am confused
| > > about what all they might be used for. "Help" and the "Beamer" article
| > > within Help aren't.
| > >
| > > The most definitive statement I could find in Help was, "A Behavior is a
| > > combination of an event and an action". That statement covers a lot of
| > > ground for non-programmers.
| > >
| > > What I'd like to know is, which behavior in combination with which event
| > > produces what action. Thanks.
| > >
| > >
| > >
| > >
| > >
| >
| >
|
|
