The official source of product insight from the Visual Studio Engineering Team
To make the HTML markup more legible, the product team decided to attach each Behavior via a W3C-compliant data-vs-interactivity attribute. Arguments are passed via a human-readable JSON object in a separate referenced file. All Behaviors on the page are initialized when the application loads and WinJS.UI.processAll() executes.
To create their own Behaviors, developers can use the same schema used for WinJS controls. OAM (Open Ajax Metadata) describes reusable functional components and is very legible to anyone familiar with extensible markup languages. Once added to the Blend installation directory, this allows your custom Behavior to appear in the Asset panel.
To fully understand Behaviors, you must also understand Actions. Behaviors describe an event while Actions describe the consequence of an event. A good way to think about it is this:
“When [Behavior] happens, do [action]”
Behaviors are attached to individual page elements in the HTML Properties panel, using the controls in the Behaviors category:
The controls in the Behaviors category can be used to: 1) Add new Behaviors, 2) Add or removes Behaviors and Actions and 3) Configure the selected Action or Behavior. When a Behavior is added to an element, a data-vs-interactivity attribute is added to it which contains the name of the Behavior that is attached.
Behaviors act as triggers, defining what criteria need to be met in order to cause one or more of its associated Actions to fire. One example is the EventTriggerBehavior, which can be set to trigger on different events, e.g. the OnClick event of an element. In this case, whenever that element is clicked, all the actions associated with that Behavior will be run.
By default, the element to which the Behavior is attached will be the source and target elements for the behavior. Being able to retarget the source of your behavior or the target of your action will be a very common task. To allow a behavior to listen to elements other than what it is attached to or have actions target other elements, you can make use of the sourceSelector and targetSelector properties.
Behaviors and Actions can be combined in a variety of ways to affect page elements, either directly or indirectly by using the targetSource and srouceSelector to target or attach Behaviors to other elements on the page.Behaviors and Actions are attached to page elements and can be configured in Blend using the HTML Attribute panel.
Its too bad that we still don't have ability to draw non-rectangular shapes in Windows Store using XAML. visualstudio.uservoice.com/.../3794118-non-rectangular-shapes-in-windows-rt-and-windows-p
I was so much hopeful that you guys would consider bringing Windows.UI.XAML.UIElement.Clip to Windows Store. I understand it would be a resource hog for WOA devices, but don't we need something glamorous in our ecosystem, something like.. Mitsu's (ex-softie) book control.. wpfbookcontrol.codeplex.com.
We can build similar thing in in WinJS project, then why cant we have the similar ability in XAML. Pseudo-clipping using rectangular shape is the only option and its the most unlikely one to be approved due to excessive resource consumption!
Please fake the clipping internally if you have to and provide us with syntactic sugar to support non-rectangular geometry. And more people will support our ecosystem! 8-)
In Behaviours ,which class i can use "To select a photo from computer and save it as profile picture"