bicomponent.xml

来自「ajax 框价．是个好工具．javascript 矿家．可以用在任何平台．」· XML 代码 · 共 1,308 行 · 第 1/4 页

				<link class="BiComponent">BiComponent[]</link>
			</type>
		</property>
		<property name="canSelect" get="true" set="true">
			<description>Whether textual content is selectable</description>
			<type>Boolean</type>
		</property>
		<property name="enabled" get="true" set="true">
			<description>Whether the component is enabled or not. When this is changed the
 component fires the <link>enabledchanged</link> event.
 A disabled component cannot recieve focus.</description>
			<type>Boolean</type>
		</property>
		<property name="isEnabled" get="true">
			<description>This is true when the component is <link>enabled</link> and all
 its ancestors are also <link>enabled</link>.</description>
			<type>Boolean</type>
		</property>
		<property name="capture" get="true" set="true">
			<description>This is true when the component is set to capture all mouse events even if
 the mouse pointer is outside the component.</description>
			<type>Boolean</type>
		</property>
		<property name="accessKey" get="true" set="true">
			<description>The key, in combination with the Alt key, that will activate the component.</description>
			<type>String</type>
		</property>
		<property name="contextMenu" get="true" set="true">
			<description>If set then this is the menu that will be shown
 when the user right clicks (or uses some othe UI mechanism) to bring up
 a context menu. Set this to <code>null</code> when no contex menu
 is desired.</description>
			<type>
				<link class="BiMenu">BiMenu</link>
			</type>
		</property>
		<property name="name" get="true" set="true">
			<description>The name does not have any real meaning except that it can be useful to
 identify the component</description>
			<type>String</type>
		</property>
		<property name="toolTip" get="true" set="true">
			<description>Sets the tool tip to show when the user hovers the component.
 Setting this to null prevents a tooltip from beeing shown (unless
 <link>toolTipText</link> is set.</description>
			<type>
				<link class="BiToolTip">BiToolTip</link>
			</type>
		</property>
		<property name="toolTipText" get="true" set="true">
			<description>Sets the tool tip text to show when the user hovers the component.
 This allows a simple plain text tool tip to be shown. This property
 is preferred over the <link>toolTip</link> property when the extra
 functionality provided by the <link class="BiToolTip">BiToolTip</link>
 instance is needed.</description>
			<type>String</type>
		</property>
		<property name="rightToLeft" get="true" set="true">
			<description>Describes whether the component should be be layed out to support
 locales using right-to-left fonts. If this is set to <code>null</code>
 then the <link>rightToLeft</link> property for the parent component
 is used.</description>
			<type>Boolean</type>
		</property>
		<property name="created" get="true">
			<description>This becomes true when the HTML element representing the
 component gets created. From a pure UI perspective this can be
 seen as when there is a visual representation created and available
 on the screen.</description>
			<type>Boolean</type>
		</property>
		<property name="command" get="true" set="true">
			<description>Commands are used to make more than one component trigger the
 same action. Commands also synchronize different properties on
 the components using the command.<link class="BiComponent">BiComponent</link> only synchronizes
 the <link>enabled</link> property with the command. Sub classes
 that have a value property usually synchronizes that as well.</description>
			<type>
				<link class="BiCommand">BiCommand</link>
			</type>
		</property>
		<property name="dropDataTypes" get="true" set="true">
			<description>The data type that are supported when dropping on the component</description>
			<type>String[]</type>
		</property>
		<property name="cssClassName" get="true" set="true">
			<description>The CSS class name for the element representing the component.
 This should be used with caution since in some cases this might give unrespected results.</description>
			<type>String</type>
		</property>
		<property name="appearance" get="true" set="true">
			<description>Sets the appearance on the component. This allows a theme to do custom
 styling of the component.</description>
			<type>String</type>
		</property>
	</properties>
	<events>
		<event name="resize">
			<description>This event is fired when a created component
 									changes its size.</description>
			<type>
				<link class="BiEvent">BiEvent</link>
			</type>
		</event>
		<event name="enabledchanged">
			<description>This is fired when the <link>enabled</link>
 										property is changed.</description>
			<type>
				<link class="BiEvent">BiEvent</link>
			</type>
		</event>
		<event name="create">
			<description>This event is fired when the component has been
	 								created and inserted into the document. When it is
									fired it is quaranteed that the component has been
									inserted into a <link class="BiApplication">application
									window</link> and at that time it has a visual representation.</description>
			<type>
				<link class="BiEvent">BiEvent</link>
			</type>
		</event>
		<event name="losecapture">
			<description>This event is fired if the component has taken
 									the capture but for some reason lost it.</description>
			<type>
				<link class="BiEvent">BiEvent</link>
			</type>
		</event>
		<event name="scroll">
			<description>When the user scrolls the component scroll
 									events are continuously fired.</description>
			<type>
				<link class="BiEvent">BiEvent</link>
			</type>
		</event>
		<event name="focus">
			<description>This is fired when the component becomes focused.</description>
			<type>
				<link class="BiFocusEvent">BiFocusEvent</link>
			</type>
		</event>
		<event name="focusin" bubbles="true">
			<description>This event is fired when the component becomes focused.
 									This event is fired before the <link>focus</link> event
                                  and unlike the <link>focus</link> event it bubbles up
                                  to the parent component.</description>
			<type>
				<link class="BiFocusEvent">BiFocusEvent</link>
			</type>
		</event>
		<event name="focusout" bubbles="true">
			<description>This event is fired when the component loses focus. This
 									event is fired before the <link>blur</link> event and
                                  unlike the <link>blur</link> event it bubbles up to the
                                  parent component.</description>
			<type>
				<link class="BiFocusEvent">BiFocusEvent</link>
			</type>
		</event>
		<event name="blur">
			<description>This is fired by a focused compinent when it loses focus.</description>
			<type>
				<link class="BiFocusEvent">BiFocusEvent</link>
			</type>
		</event>
		<event name="keydown" bubbles="true">
			<description>This event is fired by the component when it is focused
 										and the user presses down a key on the keyboard. This event
                                      then bubbles up to ancestors.</description>
			<type>
				<link class="BiKeyboardEvent">BiKeyboardEvent</link>
			</type>
		</event>
		<event name="keypress" bubbles="true">
			<description>This event is continuously fired by the component when it
 										is focused and the user holds down a key on the keyboard.
                                      This event then bubbles up to ancestors.</description>
			<type>
				<link class="BiKeyboardEvent">BiKeyboardEvent</link>
			</type>
		</event>
		<event name="keyup" bubbles="true">
			<description>This event is fired by the component when it is focused
 										and the user releases a key on the keyboard. This event
                                      then bubbles up to ancestors.</description>
			<type>
				<link class="BiKeyboardEvent">BiKeyboardEvent</link>
			</type>
		</event>
		<event name="click" bubbles="true">
			<description>When the user clicks on a component it fires this event.
 										This event bubbles to the ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="contextmenu" bubbles="true">
			<description>This event is fired when the user wants to show the context
 										menu. This is usually done by right clicking on the component
                                      but can be done in several different ways depending on the
                                      users operating system. This event bubbles to the ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="dblclick" bubbles="true">
			<description>When the user double clicks on a component it fires this event.
 										This event bubbles to the ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="mousedown" bubbles="true">
			<description>This is fired when the user presses down a mouse button on a
 										component. This event bubbles to the ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="mousemove" bubbles="true">
			<description>This is fired when the user moves the mouse and the pointer
 										is over the current component. This event bubbles to the
                                      ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="mouseout" bubbles="true">
			<description>This event is fired when the mouse pointer leaves the component.
 										<link class="BiMouseEvent" field="relatedTarget">relatedTarget</link>
                                      can be used to find the component that was entered.
                                      This event bubbles to the ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="mouseover" bubbles="true">
			<description>This is fired when the mouse pointer enters a component.
 										<link class="BiMouseEvent" field="relatedTarget">relatedTarget</link>
                                      can be used to find the component that was left.
                                      This event bubbles to the ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="mouseup" bubbles="true">
			<description>This is fired when the user releases a mouse button on the
 										component. This event bubbles to the ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="mousewheel" bubbles="true">
			<description>This event is fired when the user scrolls the mouse wheel over the
 										component. This event bubbles to the ancestors.</description>
			<type>
				<link class="BiMouseEvent">BiMouseEvent</link>
			</type>
		</event>
		<event name="dragstart" bubbles="true">
			<description>This event is fired when the user starts to drag a component.
 									Call <link class="BiDragEvent" field="startDrag">startDrag</link>
                                  on the event object to initiate a drag'n drop session.
                                  This event bubbles to the ancestors.</description>
			<type>
				<link class="BiDragEvent">BiDragEvent</link>
			</type>
		</event>
		<event name="dragover" bubbles="true">
			<description>When doing drag'n drop this is fired when the user drags over
									the component. This is similar to <link>mouseover</link> except
                                  that it only happens on valid drop targets during a drag'n drop
                                  sessions. The <link class="BiDragEvent" field="relatedTarget">relatedTarget</link> points to the component
                                  of the drag'n drop session that was left (if any).
                                  This event bubbles to the ancestors.</description>
			<type>
				<link class="BiDragEvent">BiDragEvent</link>
			</type>
		</event>
		<event name="dragout" bubbles="true">
			<description>When doing drag'n drop this is fired when the mouse pointer
 									leaves the component. This is similar to <link>mouseout</link>
                                  except that it only happens on valid drop targets during a
                                  drag'n drop sessions. The <link class="BiDragEvent" field="relatedTarget">relatedTarget</link> points to the component
                                  of the drag'n drop session that was entered (if any).
                                  This event bubbles to the ancestors.</description>
			<type>
				<link class="BiDragEvent">BiDragEvent</link>
			</type>
		</event>
		<event name="dragmove" bubbles="true">
			<description>When doing drag'n drop this is fired when the mouse pointer
 									moves over the component. This is similar to <link>mousemove</link>
                                  except that it only happens on valid drop targets during a
                                  drag'n drop sessions.
                                  This event bubbles to the ancestors.</description>
			<type>
				<link class="BiDragEvent">BiDragEvent</link>
			</type>
		</event>
		<event name="dragdrop" bubbles="true">
			<description>This is fired when the user drops something on the component.
 									This is only fired by valid drop targets for the drag'n drop
                                  session. The <link class="BiDragEvent" field="relatedTarget">relatedTarget</link> points to the source
                                  of the drag'n drop session.
                                  This event bubbles to the ancestors.</description>
			<type>
				<link class="BiDragEvent">BiDragEvent</link>
			</type>
		</event>
		<event name="dragend" bubbles="true">
			<description>This is fired on the component that the user started the drag on
 									when the drag and drop session ends. If the drag'n drop was
                                  successful then the <link class="BiDragEvent" field="relatedTarget">relatedTarget</link> is the component
                                  where the drag'n drop started. If the drag'n drop failed the
                                  <link class="BiDragEvent" field="relatedTarget">relatedTarget</link>
                                  is <code>null</code>.
                                  This event bubbles to the ancestors.</description>
			<type>
				<link class="BiDragEvent">BiDragEvent</link>
			</type>
		</event>
	</events>
	<remarks>
	</remarks>
</class>