Input: [Name] Outcome [Type] Outcome [Description]

Output: The BioAssay activity outcome

AID 490156 - Induction of human NQO1 activity in mouse Hepa-1c1c7 cells at 25 uM after 48 hrs relative to control - PubChem BioAssay Summary


Input: [TID] 1 [Name] Fold change activity comment [Type] String [Description]

Output: Fold change activity comment

AID 490156 - Induction of human NQO1 activity in mouse Hepa-1c1c7 cells at 25 uM after 48 hrs relative to control - PubChem BioAssay Summary


Input: [TID] 2 [Name] Fold change standard flag [Type] Integer [Description]

Output: Fold change standard flag

AID 490156 - Induction of human NQO1 activity in mouse Hepa-1c1c7 cells at 25 uM after 48 hrs relative to control - PubChem BioAssay Summary


Input: [TID] 3 [Name] Fold change qualifier [Type] String [Description]

Output: Fold change qualifier

AID 490156 - Induction of human NQO1 activity in mouse Hepa-1c1c7 cells at 25 uM after 48 hrs relative to control - PubChem BioAssay Summary


Input: [TID] 4 [Name] Fold change published value [Type] Float [Description]

Output: Fold change published value

AID 490156 - Induction of human NQO1 activity in mouse Hepa-1c1c7 cells at 25 uM after 48 hrs relative to control - PubChem BioAssay Summary


Input: [TID] 5 [Name] Fold change standard value [Type] Float [Description]

Output: Fold change standard value

AID 490156 - Induction of human NQO1 activity in mouse Hepa-1c1c7 cells at 25 uM after 48 hrs relative to control - PubChem BioAssay Summary


Input: [Entity] Account [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Bill [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Bill Payment [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Class [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Company Meta Data [Create] no [List] no [Delete] no [Fetch by ID] no [Other] load [Update]

Output: no


Input: [Entity] Credit Memo [Create] n/a [List] n/a [Delete] n/a [Fetch by ID] n/a [Update]


Input: [Entity] Customer [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Employee [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Entitlement [Create] n/a [List] n/a [Delete] n/a [Fetch by ID] n/a [Other] status [Update]


Input: [Entity] Invoice [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Other] invoice_as_pdf [Update]

Output: yes


Input: [Entity] Item [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Journal Entry [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Job [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Payment [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Payment Method [Create] no [List] no [Delete] no [Fetch by ID] no [Update]

Output: no


Input: [Entity] Sales Receipt [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Sales Rep [Create] no [List] no [Delete] no [Fetch by ID] no [Update]

Output: no


Input: [Entity] Sales Tax [Create] no [List] no [Delete] no [Fetch by ID] no [Update]

Output: no


Input: [Entity] Sales Term [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Ship Method [Create] no [List] no [Delete] no [Fetch by ID] no [Update]

Output: no


Input: [Entity] Sync Activity [Create] n/a [List] n/a [Delete] n/a [Fetch by ID] n/a [Update]


Input: [Entity] Sync Status [Create] n/a [List] n/a [Delete] n/a [Fetch by ID] n/a [Update]


Input: [Entity] Time Activity [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Tracking Class [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Entity] Vendor [Create] yes [List] yes [Delete] yes [Fetch by ID] yes [Update]

Output: yes


Input: [Service name] PDBeView [Replacement service] The new search box at the top of the page [Description]

Output: Text based and advanced PDB searching tool


Input: [Service name] PDBstatus [Replacement service] The new search box at the top of the page [Description]

Output: Search system to query status of PDB entries


Input: [Service name] Gene ontology browser [Replacement service] The new search box at the top of the page [Description]

Output: Browse, list and analyse the structural knowledge embodied in the PDB based on gene ontology


Input: [Service name] Enzyme browser [Replacement service] The new search box at the top of the page [Description]

Output: Browse, list and analyse the structural knowledge embodied in the PDB based on enzyme classification


Input: [Service name] Structure folds browser [Replacement service] The new search box at the top of the page [Description]

Output: Browse, list and analyse the structural knowledge embodied in the PDB based on structure folds in CATH database


Input: [Service name] Protein families browser [Replacement service] The new search box at the top of the page [Description]

Output: Browse, list and analyse the structural knowledge embodied in the PDB based on protein family data from Pfam database


Input: [Service name] Taxonomy browser [Replacement service] The new search box at the top of the page [Description]

Output: Browse, list and analyse the structural knowledge embodied in the PDB based on taxonomy data from NCBI taxonomy database


Input: [Service name] Compound browser [Replacement service] The new search box at the top of the page [Description]

Output: Browse, list and analyse the structural knowledge embodied in the PDB based on chemical component data inthe PDB


Input: [Service name] PDBeLite Retired service [Replacement service] Not supported please use the search box at the top of this page [Description]

Output: Search system based on the relational database


Input: [Service name] PQS-Quick Retired service [Replacement service] Not supported please use Quaternary structure service [Description]

Output: A simple protein quaternary structure search


Input: [Service name] PDBeMapQuick Retired service [Replacement service] The new search box at the top of the page or the PDBe API [Description]

Output: Quick access to cross-reference information to external databases based on PDB id


Input: [Service name] Search OCA Deprecated service [Replacement service] Not supported please use the search box at the top of this page [Description]

Output: OCA form-based system for searching PDB


Input: [Service name] PDBeTemplate Retired service [Replacement service] Not supported [Description]

Output: Local residue interactions in the PDB


Input: [Service name] PDBeAnalysis Retired service [Replacement service] Not supported [Description]

Output: Validation and analysis of PDBe data


Input: [Service name] NMR Representative Retired service [Replacement service] Not supported [Description]

Output: Representative model from NMR ensemble


Input: [Service name] Olderado Retired service [Replacement service] Not supported [Description]

Output: Clustering information for NMR entries in the PDB


Input: [Service name] LeView Retired service [Replacement service] Not supported [Description]

Output: 2D representations of ligands and their environments and binding interactions for PDB entries


Input: [Service name] Analysis Retired service [Replacement service] Not supported [Description]

Output: Validation and analysis of PDBe data


Input: [Service name] Connect Retired service [Replacement service] Not supported [Description]

Output: Query system to access to covalently connected residue pairs


Input: [Service name] PDBeDatabase Retired service [Replacement service] Not supported [Description]

Output: Direct SQL based query access to PDBe database


Input: [Service name] Template Retired service [Replacement service] Not supported [Description]

Output: Local residue interactions in the PDB


Input: [Code] 1 [Explanation] Dynamically allocated memory on the gateway is exhausted. This condition may indicate a temporary overload or a memory leak caused by faulty software. [Category] 181 [Descriptor]

Output: No memory

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 2 [Explanation] Packet or buffer memory is exhausted. This condition may indicate a temporary overload or a memory leak caused by faulty software. [Category] 181 [Descriptor]

Output: No buffers

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 3 [Explanation] Call is rejected because default or configured CPU usage threshold has been exceeded. [Category] 181 [Descriptor]

Output: CPU high

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 4 [Explanation] Call is rejected because default or configured memory usage threshold has been exceeded. [Category] 181 [Descriptor]

Output: Low memory

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 5 [Explanation] No dial peer satisfied the match criteria for accepting or handling the call. This condition usually indicates a dial peer misconfiguration. [Category] 128 [Descriptor]

Output: No dial peer match

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 6 [Explanation] There were insufficient DSP resources to handle the call. [Category] 182 [Descriptor]

Output: No DSP resource

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 7 [Explanation] An error occurred on a socket interface. [Category] 179 [Descriptor]

Output: Socket error

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 8 [Explanation] Media (RTP/RTCP) inactivity timer expired for the call. [Category] 185 [Descriptor]

Output: RTP inactivity error

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 9 [Explanation] Invalid arguments passed to a function. This condition usually indicates an internal software error. [Category] 180 [Descriptor]

Output: Invalid arguments

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 10 [Explanation] Some unexpected event was received while in a state that was inappropriate for processing such an event. [Category] 180 [Descriptor]

Output: Invalid State

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 11 [Explanation] The software timed out waiting for some response or event to happen. [Category] 179 [Descriptor]

Output: Timeout

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 12 [Explanation] An internal process communication error occurred. This condition usually indicates some software error, but may also mean that some process was not running because of misconfiguration. [Category] 178 [Descriptor]

Output: Inter-process communication

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 13 [Explanation] An internal software error occurred. Report the entire IEC string, including the diagnostic code field, to customer support. [Category] 180 [Descriptor]

Output: Software error

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 14 [Explanation] The gateway or signaling interfaces are being taken out of service (forcefully or gracefully). A possible cause may be the signaling interface required to support the call has already been administratively shut down. [Category] 187 [Descriptor]

Output: Gateway or interface OOS

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 21 [Explanation] An outbound dial peer could not be used because the configured maximum number of connections for the dial peer had been reached. [Category] 181 [Descriptor]

Output: Dial peer connections exceeded

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 22 [Explanation] An outbound dial peer could not be used because the configured numbering type did not match the type specified in the call. [Category] 28 [Descriptor]

Output: Incompatible number type

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 23 [Explanation] The system failed to select an available interface among the trunk group specified for use by a matching dial peer. [Category] 182 [Descriptor]

Output: Trunk-group select fail

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 24 [Explanation] An error occurred in processing caller ID information. [Category] 180 [Descriptor]

Output: Caller-ID processing failure

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 25 [Explanation] A resource needed to service the call was busy. [Category] 181 [Descriptor]

Output: Resource busy

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 26 [Explanation] The system could not find an application to take the incoming call. Check your call application and dial peer configurations. [Category] 180 [Descriptor]

Output: No application

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 27 [Explanation] The event points to a session application that no longer exists and is being discarded. [Category] 180 [Descriptor]

Output: Application no longer exists

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 28 [Explanation] An incoming call setup indication was received, bearing the same globally unique identifier (GUID) as a call in existence. The call is being rejected because a loop is suspected. [Category] 180 [Descriptor]

Output: Incoming loop

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 29 [Explanation] An incoming call was rejected because configured call spike thresholds were exceeded. [Category] 181 [Descriptor]

Output: Call spike threshold

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 30 [Explanation] A matched dial peer could not be used to find an inbound application because the permission setting on it blocked its use as an inbound dial peer. As a result, no application could be found to handle the call. [Category] 181 [Descriptor]

Output: Inbound dial peer blocked

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 31 [Explanation] A matched dial peer could not be used to place the call because the configured permission on it contradicted its use as an outbound dial peer. [Category] 181 [Descriptor]

Output: Outbound dial peer blocked

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 32 [Explanation] The maximum number of handoffs between applications for a single call has been exceeded. Check your application scripts to make sure there is no infinite loop within the applications. [Category] 180 [Descriptor]

Output: Handoff depth reached

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 33 [Explanation] A call handoff attempt between applications failed because the applications were incompatible. Tcl IVR 1.0 applications are incompatible with Tcl IVR 2.0 or VXML applications. [Category] 180 [Descriptor]

Output: Incompatible apps for handoff

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 34 [Explanation] A matched dial peer could not be used for the outbound leg because there was no appropriate interface for the dial peer type. This condition may be a software or configuration error. The tag identifier for the problematic dial peer is provided in the diagnostic field (the last component) of the six-part IEC string. Check your dial peer configuration. [Category] 180 [Descriptor]

Output: No dial peer interface

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [Code] 35 [Explanation] Some data structure or process that should have been created at system initialization is missing. Report the IEC to customer support. [Category] 180 [Descriptor]

Output: System init error

Cisco IOS Voice Troubleshooting and Monitoring -- Cisco VoIP Internal Error Codes - DocWiki


Input: [File Type] .MUS [Description] Music data [Where to copy...] CACHE folder [Should I copy to hard disk?]

Output: Reduces CD access significantly if copied to hard disk as music is read in regularly. Should improve scenes containing lots of sound effects.


Input: [File Type] .SCN [Description] Code and graphics [Where to copy...] CACHE folder [Should I copy to hard disk?]

Output: Scene load times reduced if copied to hard disk - no other benefit. n.b. some critical scenes are already copied to hard disk during installation.


Input: [File Type] .CDP [Description] Graphic sequences [Where to copy...] CACHE folder [Should I copy to hard disk?]

Output: Smoothes out brief pauses while loading extra graphics within a scene.


Input: [File Type] .BMV [Description] 'B movies' [Where to copy...] CACHE folder [Should I copy to hard disk?]

Output: Only copy to hard drive if the movies are playing badly or sound shuts off. Movie pre-load times are also reduced if the movies are copied.


Input: [File Type] .SMP [Description] Speech [Where to copy...] CD1 or CD2 folder [Should I copy to hard disk?]

Output: Only copy to hard drive if you are experiencing regular sound glitches.


Input: [File Type] .IDX [Description] Speech index [Where to copy...] CD1 or CD2 folder [Should I copy to hard disk?]

Output: Loaded once only - can stay on CD.


Input: [File Type] .TXT [Description] Sub-title text [Where to copy...] CD1 or CD2 folder [Should I copy to hard disk?]

Output: Loaded once only - can stay on CD.


Input: [Parameter] id [Value] Unique identifier [Description] Used to link TWISTYSHOW, TWISTYHIDE and TWISTYTOGGLE [Remark]

Output: required


Input: [Parameter] link [Value] Link label [Description] Show link label [Remark]

Output: optional


Input: [Parameter] mode [Value] "div" or "span" [Description] Specify if the Twisty Show link will use a or a tag. Note that if the contents contains block elements such as div, mode should be div as well to create valid HTML markup. [Remark]

Output: optional, defaults to


Input: [Parameter] img [Value] Image url [Description] Specify the url of an image that will be displayed at the right side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. [Remark]

Output: optional, defaults to no image


Input: [Parameter] imgleft [Value] Image url [Description] Specify the url of an image that will be displayed at the left side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. [Remark]

Output: optional, defaults to no image


Input: [Parameter] imgright [Value] Image url [Description] Specify the url of an image that will be displayed at the right side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. [Remark]

Output: optional, defaults to no image


Input: [Parameter] remember [Value] "on", "off" [Description] If "on", the Twisty state is remembered the next time the page is shown. If "off", the stored setting will be cleared. Note: when used, think carefully about a unique name (id) for the Twisty, otherwise the cookie that is set might affect other Twisties with the same name. Also note that only interaction is stored, not the state of the Twisty when left unclicked. [Remark]

Output: optional, no default


Input: [Parameter] start [Value] "hide" or "show" [Description] Initial state of the Twisty; this will override any setting stored in a cookie (see remember). [Remark]

Output: optional, default no initial state


Input: [Parameter] firststart [Value] "hide" or "show" [Description] Initial state of the Twisty the first time the visitor gets to see the Twisty; this will NOT override cookie settings (see remember). [Remark]

Output: optional, default no initial state


Input: [File] blur_effect.js [Role] Class [Description]

Output: Main class source

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [File] blur_effect.packed.js [Role] Class [Description]

Output: Main class packed

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [File] blur_effect.jquery.js [Role] Class [Description]

Output: Jquery plugin

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [File] captcha.jpeg [Role] Data [Description]

Output: Captcha image

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [File] captcha_example.html [Role] Example [Description]

Output: An idea for captchas

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [File] example.html [Role] Example [Description]

Output: Different examples on using object

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [File] jquery_example.html [Role] Example [Description]

Output: Different examples for jquery

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [File] simple_example.html [Role] Example [Description]

Output: Simple example blured text

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [File] wce.jpg [Role] Data [Description]

Output: Image for examples

Blur effect: Apply the blur effect to HTML page elements - JS Classes


Input: [Parameter Name] lbruleid [Required] true [Description]

Output: the ID of the load balancer rule

Apache CloudStack | The Power Behind Your Cloud


Input: [Parameter Name] maxmembers [Required] true [Description]

Output: the maximum number of members in the vmgroup, The number of instances in the vm group will be equal to or less than this number.

Apache CloudStack | The Power Behind Your Cloud


Input: [Parameter Name] minmembers [Required] true [Description]

Output: the minimum number of members in the vmgroup, the number of instances in the vm group will be equal to or more than this number.

Apache CloudStack | The Power Behind Your Cloud


Input: [Parameter Name] scaledownpolicyids [Required] true [Description]

Output: list of scaledown autoscale policies

Apache CloudStack | The Power Behind Your Cloud


Input: [Parameter Name] scaleuppolicyids [Required] true [Description]

Output: list of scaleup autoscale policies

Apache CloudStack | The Power Behind Your Cloud


Input: [Parameter Name] vmprofileid [Required] true [Description]

Output: the autoscale profile that contains information about the vms in the vm group.

Apache CloudStack | The Power Behind Your Cloud


Input: [Parameter Name] fordisplay [Required] false [Description]

Output: an optional field, whether to the display the group to the end user or not

Apache CloudStack | The Power Behind Your Cloud


Input: [Parameter Name] interval [Required] false [Description]

Output: the frequency at which the conditions have to be evaluated

Apache CloudStack | The Power Behind Your Cloud


Input: [Offset] 0 [Type] int [Size] 4 [Description] The magic number which identifies the file as a star catalogue. 0xde0955a3 [Name]

Output: Magic

Header Record


Input: [Offset] 4 [Type] int [Size] 4 [Description] This describes the type of the file, which defines the size and structure of the Star Data record for the file. [Name]

Output: Data Type

Header Record


Input: [Offset] 8 [Type] int [Size] 4 [Description] The file format major version number [Name]

Output: Major Version

Header Record


Input: [Offset] 12 [Type] int [Size] 4 [Description] The file format minor version number [Name]

Output: Minor Version

Header Record


Input: [Offset] 16 [Type] int [Size] 4 [Description] Sets the level of sub-division of the geodesic sphere used to create the zones. 0 means an icosahedron (20 sizes), subsequent levels of sub-division lead to numbers of zones as described in section Zones [Name]

Output: Level

Header Record


Input: [Offset] 20 [Type] int [Size] 4 [Description] The low bound of the magnitude scale for values in this file. Note that this is still an integer in Stellarium's own internal representation [Name]

Output: Magnitude Minimum

Header Record


Input: [Offset] 24 [Type] int [Size] 4 [Description] The range of magnitudes expressed in this file [Name]

Output: Magnitude Range

Header Record


Input: [Offset] 28 [Type] int [Size] 4 [Description] The number of steps used to describes values in the range [Name]

Output: Magnitude Steps

Header Record


Input: [Attribute] name [Default] no default [Required or Optional] required [Description]

Output: Set this attribute to the unique String name that references this stored procedure query.

Difference between revisions of "Using EclipseLink JPA Extensions (ELUG)" - Eclipsepedia


Input: [Attribute] hints [Default] empty QueryHint array [Required or Optional] optional [Description]

Output: Set this attribute to an array of javax.persistence.QueryHint instances.

Difference between revisions of "Using EclipseLink JPA Extensions (ELUG)" - Eclipsepedia


Input: [Attribute] resultClass [Default] void.class [Required or Optional] optional [Description]

Output: Set this attribute to the Class of the query result.

Difference between revisions of "Using EclipseLink JPA Extensions (ELUG)" - Eclipsepedia


Input: [Attribute] resultSetMapping [Default] empty String [Required or Optional] optional [Description]

Output: Set this attribute to the String name of the javax.persistence.SQLResultSetMapping instance.

Difference between revisions of "Using EclipseLink JPA Extensions (ELUG)" - Eclipsepedia


Input: [Attribute] procedureName [Default] no default [Required or Optional] required [Description]

Output: Set this attribute to the String name of the stored procedure.

Difference between revisions of "Using EclipseLink JPA Extensions (ELUG)" - Eclipsepedia


Input: [Attribute] returnsResultSet [Default] true [Required or Optional] optional [Description]

Output: Set this attribute to the boolean value of false to disable the return of the result set.

Difference between revisions of "Using EclipseLink JPA Extensions (ELUG)" - Eclipsepedia


Input: [Attribute] parameters [Default] empty StoredProcedureParameter array [Required or Optional] optional [Description]

Output: Set the value of this attribute to an array of @StoredProcedureParameter instances to define arguments to the stored procedure.

Difference between revisions of "Using EclipseLink JPA Extensions (ELUG)" - Eclipsepedia


Input: [Parameter] id [Value] Unique identifier [Remark] required [Description]

Output: Used to link TWISTYSHOW, TWISTYHIDE and TWISTYTOGGLE.


Input: [Parameter] mode [Value] "div" or "span" [Remark] optional, defaults to [Description]

Output: Specify if the Twisty Toggle section will use a or a tag. Note that if the contents contains block elements such as div, mode should be div as well to create valid HTML markup.


Input: [Parameter] class [Value] CSS class name [Remark] optional, default none [Description]

Output: Class for content div or span


Input: [Parameter] linkclass [Value] CSS class name [Remark] optional, default none [Description]

Output: Class for link


Input: [Parameter] remember [Value] "on", "off" [Remark] optional, no default [Description]

Output: If "on", the Twisty state is remembered the next time the page is shown. If "off", the stored setting will be cleared. Note: when used, think carefully about a unique name (id) for the Twisty, otherwise the cookie that is set might affect other Twisties with the same name. Also note that only interaction is stored, not the state of the Twisty when left unclicked.


Input: [Parameter] start [Value] "hide" or "show" [Remark] optional, default no initial state [Description]

Output: Initial state of the Twisty; this will override any setting stored in a cookie (see remember).


Input: [Parameter] firststart [Value] "hide" or "show" [Remark] optional, default no initial state [Description]

Output: Initial state of the Twisty the first time the visitor gets to see the Twisty; this will NOT override cookie settings (see remember).


Input: [Parameter] noscript [Value] "hide" [Remark] optional, default content is shown with no JavaScript [Description]

Output: Make content hidden in case use does not have JavaScript on


Input: [Method name] getApplication [Description]

Output: Get a application object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getConfig [Description]

Output: Get a configuration object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getSession [Description]

Output: Get a session object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getLanguage [Description]

Output: Get a language object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getDocument [Description]

Output: Get a document object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getUser [Description]

Output: Get an user object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getCache [Description]

Output: Get a cache object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getACL [Description]

Output: Get an authorization object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getDbo [Description]

Output: Get a database object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getMailer [Description]

Output: Get a mailer object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getFeedParser [Description]

Output: Get a parsed XML Feed Source

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getXMLParser [Description]

Output: Get an XML document

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getXML [Description]

Output: Reads a XML file.

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getEditor [Description]

Output: Get an editor object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getURI [Description]

Output: Return a reference to the JURI object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getDate [Description]

Output: Return the JDate object

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [Method name] getStream [Description]

Output: Creates a new stream object with appropriate prefix

Difference between revisions of "API15:JFactory" - Joomla! Documentation


Input: [remedy] The file "META.yml" is missing from this distribution. META.yml is needed by people maintaining module collections (like CPAN), for people writing installation tools, or just people who want to know some stuff about a distribution before downloading it. Add a META.yml to the distribution. Your buildtool should be able to autogenerate it. [metric]

Output: has meta yml


Input: [remedy] The distribution hasn't got a Changelog (named something like m/^chang(es?|log)|history$/i. A Changelog helps people decide if they want to upgrade to a new version. Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions. [metric]

Output: has changelog


Input: [remedy] This distribution does not have a license defined in the documentation or in a file called LICENSE Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution. [metric]

Output: has human readable license


Input: [remedy] Does not have license information in any of its source files Add =head1 LICENSE and the text of the license to the main module in your code. [metric]

Output: has license in source file


Input: [remedy] This distribution does not 'use strict;' (or its equivalents) in all of its modules. Note that this is not about the actual strictness of the modules. It's bad if nobody can tell whether the modules are strictly written or not, without reading the source code of your favorite clever module that actually enforces strictness. In other words, it's bad if someone feels the need to add 'use strict' to your modules. Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written. [metric]

Output: use strict


Input: [remedy] The documentation for this distribution contains syntactic errors in its POD. Note that this metric tests all .pl, .pm and .pod files, even if they are in t/. See 'pod_message' in the dist error view for more info. Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite. [metric]

Output: no pod errors


Input: [remedy] This distribution uses a module or a dist that's not listed as a prerequisite. List all used modules in META.yml requires [metric]

Output: prereq matches use


Input: [Endpoint] /datasets [Description]

Output: A dataset is the primary grouping for data at NCDC.

Web Services API (version 2) Documentation | Climate Data Online (CDO) | National Climatic Data Center (NCDC)


Input: [Endpoint] /datacategories [Description]

Output: A data category is a general type of data used to group similar data types.

Web Services API (version 2) Documentation | Climate Data Online (CDO) | National Climatic Data Center (NCDC)


Input: [Endpoint] /datatypes [Description]

Output: A data type is a specific type of data that is often unique to a dataset.

Web Services API (version 2) Documentation | Climate Data Online (CDO) | National Climatic Data Center (NCDC)


Input: [Endpoint] /locationcategories [Description]

Output: A location category is a grouping of similar locations.

Web Services API (version 2) Documentation | Climate Data Online (CDO) | National Climatic Data Center (NCDC)


Input: [Endpoint] /locations [Description]

Output: A location is a geopolitical entity.

Web Services API (version 2) Documentation | Climate Data Online (CDO) | National Climatic Data Center (NCDC)


Input: [Endpoint] /stations [Description]

Output: A station is a any weather observing platform where data is recorded.

Web Services API (version 2) Documentation | Climate Data Online (CDO) | National Climatic Data Center (NCDC)


Input: [Endpoint] /data [Description]

Output: A datum is an observed value along with any ancillary attributes at a specific place and time.

Web Services API (version 2) Documentation | Climate Data Online (CDO) | National Climatic Data Center (NCDC)


Input: [Shortcut Key] t [Action] Add a new item to the current list [Definition]

Output: Add

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] c [Action] Complete the selected task/s [Definition]

Output: Complete

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] p [Action] Postpone the selected task/s by one day if they have a due date [Definition]

Output: Postpone

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] d [Action] Change the due date of the selected task [Definition]

Output: Due Date

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] f [Action] Change the repeat of the selected task [Definition]

Output: Repeat

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] g [Action] Change the time estimate of the selected task [Definition]

Output: Time Estimate

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] s [Action] Change the tags for the selected task [Definition]

Output: Tags

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] u [Action] Change the URL for the selected task [Definition]

Output: URL

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] l [Action] Change the location for the selected task [Definition]

Output: Location

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] y [Action] Add a note to the selected task [Definition]

Output: Add Note

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] r [Action] Rename the selected item [Definition]

Output: Rename

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] z [Action] Undo the last action [Definition]

Output: Undo

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] 1 [Action] Set the priority of the selected task/s to 1 [Definition]

Output: Priority 1

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] 2 [Action] Set the priority of the selected task/s to 2 [Definition]

Output: Priority 2

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] 3 [Action] Set the priority of the selected task/s to 3 [Definition]

Output: Priority 3

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] 4 [Action] Set the selected task/s to have no priority [Definition]

Output: No Priority

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Action] Delete the currently selected task(s) [Definition]

Output: Delete

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] a [Action] Select all items in the current list [Definition]

Output: Select All

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] n [Action] Select none of the items in the current list [Definition]

Output: Select None

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] k [Action] When on a list, move the cursor up [Definition]

Output: Move Up

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] j [Action] When on a list, move the cursor down [Definition]

Output: Move Down

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] i [Action] When on a list, select an item [Definition]

Output: Select Item

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] h [Action] Switch between tabs (e.g. Task and Notes) [Definition]

Output: Switch Tabs

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Shortcut Key] m [Action] Toggle multi-edit mode on or off (default is off); Smart Add must be disabled in Settings. [Definition]

Output: Multi-edit

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Action] Save input and move to the next input field [Definition]

Output: Tab

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Action] Remove the cursor from the current input field [Definition]

Output: Escape

Remember The Milk - Help › What are the keyboard shortcuts?


Input: [Type] string [Description] Gets or sets the promotion group to change from. [Required] True [Attribute]

Output: from


Input: [Type] string [Description] Gets or sets the promotion group to change to. [Required] True [Attribute]

Output: to


Input: [Type] string [Description] Gets or sets the entity involved in the operation. [Required] True [Attribute]

Output: entity


Input: [Type] string [Description] Gets or sets the project database to utilize during the operation. [Required] True [Attribute]

Output: projectdatabase


Input: [Type] bool [Description] Determines if task failure stops the build, or is just reported. The default is true. [Required] False [Attribute]

Output: failonerror


Input: [Type] bool [Description] If true then the task will be executed; otherwise, skipped. The default is true. [Required] False [Attribute]

Output: if


Input: [Type] bool [Description] Gets or sets a value indicating whether the operation should include subprojects. [Required] False [Attribute]

Output: includesubprojects


Input: [Type] string [Description] Gets or sets the password to use when connecting to the project database. [Required] False [Attribute]

Output: password


Input: [Type] string [Description] Gets or sets the project path to utilize during the operation. [Required] False [Attribute]

Output: projectpath


Input: [Type] string [Description] Gets or sets the location of the PVCS binary command-line tools. [Required] False [Attribute]

Output: pvcsbin


Input: [Type] int [Description] The maximum amount of time the application is allowed to execute, expressed in milliseconds. Defaults to no time-out. [Required] False [Attribute]

Output: timeout


Input: [Type] bool [Description] Opposite of if. If false then the task will be executed; otherwise, skipped. The default is false. [Required] False [Attribute]

Output: unless


Input: [Type] string [Description] Gets or sets the user ID to use when connecting to the project database. [Required] False [Attribute]

Output: userid


Input: [Type] bool [Description] Determines whether the task should report detailed build log messages. The default is false. [Required] False [Attribute]

Output: verbose


Input: [Type] string [Description] Gets or sets the workspace to use when connecting to the project database. [Required] False [Attribute]

Output: workspace


Input: [Press] WINDOWS [To]

Output: Display or hide the Start menu.

United States Patent and Trademark Office


Input: [Press] CTRL + ESC [To]

Output: Display or hide the Start menu (same as WINDOWS).

United States Patent and Trademark Office


Input: [Press] CTRL + ALT + DELETE [To]

Output: Display Windows Security screen or Windows Task Manager.

United States Patent and Trademark Office


Input: [Press] WINDOWS + BREAK [To]

Output: Display the System Properties dialog box.

United States Patent and Trademark Office


Input: [Press] WINDOWS + D [To]

Output: Show the desktop.

United States Patent and Trademark Office


Input: [Press] WINDOWS + M [To]

Output: Minimize all windows.

United States Patent and Trademark Office


Input: [Press] WINDOWS + SHIFT + M [To]

Output: Restore minimized windows.

United States Patent and Trademark Office


Input: [Press] WINDOWS + E [To]

Output: Open My Computer with Windows Explorer.

United States Patent and Trademark Office


Input: [Press] WINDOWS + F [To]

Output: Search for a file or folder.

United States Patent and Trademark Office


Input: [Press] CTRL + WINDOWS + F [To]

Output: Search for computers.

United States Patent and Trademark Office


Input: [Press] WINDOWS + F1 [To]

Output: Display Windows Help.

United States Patent and Trademark Office


Input: [Press] WINDOWS + L [To]

Output: Lock your computer if you are connected to a network domain, or switch users if you are not connected to a network domain.

United States Patent and Trademark Office


Input: [Press] WINDOWS + R [To]

Output: Open the Run dialog box.

United States Patent and Trademark Office


Input: [Press] ALT + TAB(s) [To]

Output: Switch between open windows. While holding the ALT key down, you can press TAB several times to navigate through the system display of each previously used window.

United States Patent and Trademark Office


Input: [Press] ALT + SHIFT + TAB(s) [To]

Output: Similar to ALT + TAB(s), switch backward between open windows. You can switch between moving backward or forward by holding or releasing the SHIFT key.

United States Patent and Trademark Office


Input: [Press] ALT + ESC(s) [To]

Output: Cycle the input focus through the windows in the order that they were opened; compare to ALT + TAB.

United States Patent and Trademark Office


Input: [Press] ALT + SHIFT + ESC(s) [To]

Output: Similar to ALT + ESC(s), cycle focus backward through windows. You can switch between moving backward or forward by holding or releasing the SHIFT key.

United States Patent and Trademark Office


Input: [Press] PRINT SCRN [To]

Output: Copy an image of the screen.

United States Patent and Trademark Office


Input: [Press] ALT + PRINT SCRN [To]

Output: Copy an image of the current window.

United States Patent and Trademark Office


Input: [Press] Left ALT + SHIFT [To]

Output: Switch input languages or keyboard layouts (available and configurable when the user installed multiple keyboard layouts through Regional and Language Options in Control Panel).

United States Patent and Trademark Office


Input: [Press] CTRL + SHIFT [To]

Output: Switch keyboard layouts or input languages (available and configurable when the user installed multiple keyboard layouts through Regional and Language Options in Control Panel).

United States Patent and Trademark Office


Input: [Press] CTRL or left ALT + SHIFT + ~, number (0-9), or ` accent key [To]

Output: Use hot key for input languages (available and configurable when the user installed multiple keyboard layouts through Regional and Language Options in Control Panel).

United States Patent and Trademark Office


Input: [Press] WINDOWS + V [To]

Output: [Speech recognition] Toggle listening status of the microphone.

United States Patent and Trademark Office


Input: [Press] WINDOWS + C [To]

Output: [Speech recognition] Correct recognized text strings.

United States Patent and Trademark Office


Input: [Press] WINDOWS + T [To]

Output: [Speech recognition] Toggle speech dictation mode.

United States Patent and Trademark Office


Input: [Press] WINDOWS + H [To]

Output: [Handwriting] Open or close handwriting pad.

United States Patent and Trademark Office


Input: [Press] WINDOWS + number [To]

Output: Activate function reserved for OEM use.

United States Patent and Trademark Office


Input: [Name] REQ_NEXT_PAGE [Description]

Output: Move to the next page.


Input: [Name] REQ_PREV_PAGE [Description]

Output: Move to the previous page.


Input: [Name] REQ_FIRST_PAGE [Description]

Output: Move to the first page.


Input: [Name] REQ_LAST_PAGE [Description]

Output: Move to the last field.


Input: [Name] REQ_NEXT_FIELD [Description]

Output: Move to the next field.


Input: [Name] REQ_PREV_FIELD [Description]

Output: Move to the previous field.


Input: [Name] REQ_FIRST_FIELD [Description]

Output: Move to the first field.


Input: [Name] REQ_LAST_FIELD [Description]

Output: Move to the last field.


Input: [Name] REQ_SNEXT_FIELD [Description]

Output: Move to the sorted next field.


Input: [Name] REQ_SPREV_FIELD [Description]

Output: Move to the sorted previous field.


Input: [Name] REQ_SFIRST_FIELD [Description]

Output: Move to the sorted first field.


Input: [Name] REQ_SLAST_FIELD [Description]

Output: Move to the sorted last field.


Input: [Name] REQ_LEFT_FIELD [Description]

Output: Move left to a field.


Input: [Name] REQ_RIGHT_FIELD [Description]

Output: Move right to a field.


Input: [Name] REQ_UP_FIELD [Description]

Output: Move up to a field.


Input: [Name] REQ_DOWN_FIELD [Description]

Output: Move down to a field.


Input: [Name] REQ_NEXT_CHAR [Description]

Output: Move to the next char.


Input: [Name] REQ_PREV_CHAR [Description]

Output: Move to the previous char.


Input: [Name] REQ_NEXT_LINE [Description]

Output: Move to the next line.


Input: [Name] REQ_PREV_LINE [Description]

Output: Move to the previous line.


Input: [Name] REQ_NEXT_WORD [Description]

Output: Move to the next word.


Input: [Name] REQ_PREV_WORD [Description]

Output: Move to the previous word.


Input: [Name] REQ_BEG_FIELD [Description]

Output: Move to the beginning of the field.


Input: [Name] REQ_END_FIELD [Description]

Output: Move to the end of the field.


Input: [Name] REQ_BEG_LINE [Description]

Output: Move to the beginning of the line.


Input: [Name] REQ_END_LINE [Description]

Output: Move to the end of the line.


Input: [Name] REQ_LEFT_CHAR [Description]

Output: Move left in the field.


Input: [Name] REQ_RIGHT_CHAR [Description]

Output: Move right in the field.


Input: [Name] REQ_UP_CHAR [Description]

Output: Move up in the field.


Input: [Name] REQ_DOWN_CHAR [Description]

Output: Move down in the field.


Input: [Name] REQ_NEW_LINE [Description]

Output: Insert or overlay a newline.


Input: [Name] REQ_INS_CHAR [Description]

Output: Insert a blank at the cursor.


Input: [Name] REQ_INS_LINE [Description]

Output: Insert a blank line at the cursor.


Input: [Name] REQ_DEL_CHAR [Description]

Output: Delete character at the cursor.


Input: [Name] REQ_DEL_PREV [Description]

Output: Delete character before the cursor.


Input: [Name] REQ_DEL_LINE [Description]

Output: Delete line at the cursor.


Input: [Name] REQ_DEL_WORD [Description]

Output: Delete blank-delimited word at the cursor.


Input: [Name] REQ_CLR_EOL [Description]

Output: Clear to end of line from cursor.


Input: [Name] REQ_CLR_EOF [Description]

Output: Clear to end of field from cursor.


Input: [Name] REQ_CLR_FIELD [Description]

Output: Clear the entire field.


Input: [Name] REQ_OVL_MODE [Description]

Output: Enter overlay mode.


Input: [Name] REQ_INS_MODE [Description]

Output: Enter insert mode.


Input: [Name] REQ_SCR_FLINE [Description]

Output: Scroll the field forward a line.


Input: [Name] REQ_SCR_BLINE [Description]

Output: Scroll the field backward a line.


Input: [Name] REQ_SCR_FPAGE [Description]

Output: Scroll the field forward a page.


Input: [Name] REQ_SCR_BPAGE [Description]

Output: Scroll the field backward a page.


Input: [Name] REQ_SCR_FHPAGE [Description]

Output: Scroll the field forward half a page.


Input: [Name] REQ_SCR_BHPAGE [Description]

Output: Scroll the field backward half a page.


Input: [Name] REQ_SCR_FCHAR [Description]

Output: Scroll the field forward a character.


Input: [Name] REQ_SCR_BCHAR [Description]

Output: Scroll the field backward a character.


Input: [Name] REQ_SCR_HFLINE [Description]

Output: Horizontal scroll the field forward a line.


Input: [Name] REQ_SCR_HBLINE [Description]

Output: Horizontal scroll the field backward a line.


Input: [Name] REQ_SCR_HFHALF [Description]

Output: Horizontal scroll the field forward half a line.


Input: [Name] REQ_SCR_HBHALF [Description]

Output: Horizontal scroll the field backward half a line.


Input: [Name] REQ_VALIDATION [Description]

Output: Validate field.


Input: [Name] REQ_NEXT_CHOICE [Description]

Output: Display next field choice.


Input: [Name] REQ_PREV_CHOICE [Description]

Output: Display previous field choice.


Input: [File:] .htpasswd [Used for:]

Output: Basic Authentication (htaccess) users file with username and encrypted password pairs


Input: [File:] debug.txt [Used for:]

Output: Program-generated messages useful for debugging


Input: [File:] mime.types [Used for:]

Output: Recognized file formats


Input: [File:] warning.txt [Used for:]

Output: Diagnostic messages for identifying problems


Input: [File:] _default/.changes [Used for:]

Output: Per web record of topic changes


Input: [File:] _default/.mailnotify [Used for:]

Output: Per web timestamp of most recent email notification


Input: [File:] _default/WebChanges.txt [Used for:]

Output: Display most recent topic changes in web


Input: [File:] _default/WebChanges.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] _default/WebHome.txt [Used for:]

Output: Default web home page


Input: [File:] _default/WebHome.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] _default/WebIndex.txt [Used for:]

Output: Lists all topics in a web


Input: [File:] _default/WebIndex.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] _default/WebLeftBar.txt [Used for:]

Output: Left navigation bar for PatternSkin


Input: [File:] _default/WebLeftBar.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] _default/WebNotify.txt [Used for:]

Output: Subscribe/unsubscribe to web changes email alert


Input: [File:] _default/WebNotify.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] _default/WebPreferences.txt [Used for:]

Output: Per web Preference Settings


Input: [File:] _default/WebPreferences.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] _default/WebSearch.txt [Used for:]

Output: Per web search options


Input: [File:] _default/WebSearch.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] _default/WebStatistics.txt [Used for:]

Output: Generates web usage statistics


Input: [File:] _default/WebStatistics.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] _default/WebTopicList.txt [Used for:]

Output: Lists all topics in a web in compact format


Input: [File:] _default/WebTopicList.txt,v [Used for:]

Output: Revisions history (RCS)


Input: [File:] ... [Used for:]


Input: [keyword] BEGIN [stack effect] none [description]

Output: marks the beginning of a loop


Input: [keyword] ENDIF [stack effect] none [description]

Output: ends a conditional block IF…ENDIF


Input: [keyword] ELSE [stack effect] none [description]

Output: begins the alternative block in IF…ELSE…ENDIF


Input: [keyword] GOTO label [stack effect] none [description]

Output: goes to the label label (define it with label:)


Input: [keyword] IF [stack effect] -1 [description]

Output: enters the conditional block if the argument is true (non-zero) in IF…ENDIF or IF…ELSE…ENDIF


Input: [keyword] REPEAT [stack effect] none [description]

Output: marks the end of a loop


Input: [keyword] SUB name [stack effect] none [description]

Output: defines a subroutine name


Input: [keyword] WHILE [stack effect] -1 [description]

Output: jumps to the end of a loop if the argument is false (zero)


Input: [Property] Version [Type] String [Description] Display version information of ActiveXperts Networking Component [Read/Write]

Output: Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] Build [Type] String [Description] Display build information of ActiveXperts Networking Component [Read/Write]

Output: Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] Module [Type] String [Description] Module name of ActiveXperts Network Component [Read/Write]

Output: Read

ActiveXperts Networking Component - Network components for developers


Input: [Property] LicenseStatus [Type] String [Description] License Status of ActiveXperts Network Component [Read/Write]

Output: Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] LicenseKey [Type] String [Description] License Key of ActiveXperts Network Component [Read/Write]

Output: Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] LastError [Type] Number [Description] Result of the last called method [Read/Write]

Output: Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] LogFile [Type] String [Description] Log file; use it for troubleshooting purposes [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] Server [Type] String [Description] hostname or IP address of the XenServer host [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] ServerAccount [Type] String [Description] Account used to authenticate with the XenServer host [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] ServerPassword [Type] String [Description] Password used to authenticate with the XenServer host [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] ServerUseSSL [Type] Boolean [Description] Specifies how to connect: secure/SSL (default) or not secure [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] ServerPort [Type] Number [Description] Specifies which TCP port is used to connect to the Xen host [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] ProxyServer [Type] String [Description] Proxyserver to use to establish an HTTP connection with the XenServer host [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] ProxyAccount [Type] String [Description] Account used to authenticate with the proxyserver [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Property] ProxyPassword [Type] String [Description] Password used to authenticate with the proxyserver [Read/Write]

Output: In/Out

ActiveXperts Networking Component - Network components for developers


Input: [Name] Query [Sample values] xbox [Type]

Output: String

Bing Search API | Microsoft Azure Marketplace


Input: [Name] Adult [Sample values] Moderate [Type]

Output: String

Bing Search API | Microsoft Azure Marketplace


Input: [Name] Latitude [Sample values] 47.603450 [Type]

Output: Double

Bing Search API | Microsoft Azure Marketplace


Input: [Name] Longitude [Sample values] -122.329696 [Type]

Output: Double

Bing Search API | Microsoft Azure Marketplace


Input: [Name] Market [Sample values] en-US [Type]

Output: String

Bing Search API | Microsoft Azure Marketplace


Input: [Name] NewsCategory [Sample values] rt_Business [Type]

Output: String

Bing Search API | Microsoft Azure Marketplace


Input: [Name] NewsLocationOverride [Sample values] US.WA [Type]

Output: String

Bing Search API | Microsoft Azure Marketplace


Input: [Name] NewsSortBy [Sample values] Date [Type]

Output: String

Bing Search API | Microsoft Azure Marketplace


Input: [Name] Options [Sample values] EnableHighlighting [Type]

Output: String

Bing Search API | Microsoft Azure Marketplace


Input: [Test Program] static_assert_test.cpp [Expected to Compile] Yes [Description]

Output: Illustrates usage, and should always compile, really just tests compiler compatibility.


Input: [Test Program] static_assert_example_1.cpp [Expected to Compile] Platform dependent. [Description]

Output: Namespace scope test program, may compile depending upon the platform.


Input: [Test Program] static_assert_example_2.cpp [Expected to Compile] Yes [Description]

Output: Function scope test program.


Input: [Test Program] static_assert_example_3.cpp [Expected to Compile] Yes [Description]

Output: Class scope test program.


Input: [Test Program] static_assert_test_fail_1.cpp [Expected to Compile] No [Description]

Output: Illustrates failure at namespace scope.


Input: [Test Program] static_assert_test_fail_2.cpp [Expected to Compile] No [Description]

Output: Illustrates failure at non-template function scope.


Input: [Test Program] static_assert_test_fail_3.cpp [Expected to Compile] No [Description]

Output: Illustrates failure at non-template class scope.


Input: [Test Program] static_assert_test_fail_4.cpp [Expected to Compile] No [Description]

Output: Illustrates failure at non-template class scope.


Input: [Test Program] static_assert_test_fail_5.cpp [Expected to Compile] No [Description]

Output: Illustrates failure at template class scope.


Input: [Test Program] static_assert_test_fail_6.cpp [Expected to Compile] No [Description]

Output: Illustrates failure at template class member function scope.


Input: [Test Program] static_assert_test_fail_7.cpp [Expected to Compile] No [Description]

Output: Illustrates failure of class scope example.


Input: [Test Program] static_assert_test_fail_8.cpp [Expected to Compile] No [Description]

Output: Illustrates failure of function scope example.


Input: [Test Program] static_assert_test_fail_9.cpp [Expected to Compile] No [Description]

Output: Illustrates failure of function scope example (part 2).


Input: [Indice] version_number [Value description]

Output: cURL 24 bit version number


Input: [Indice] version [Value description]

Output: cURL version number, as a string


Input: [Indice] ssl_version_number [Value description]

Output: OpenSSL 24 bit version number


Input: [Indice] ssl_version [Value description]

Output: OpenSSL version number, as a string


Input: [Indice] libz_version [Value description]

Output: zlib version number, as a string


Input: [Indice] host [Value description]

Output: Information about the host where cURL was built


Input: [Indice] features [Value description]

Output: A bitmask of the CURL_VERSION_XXX constants


Input: [Indice] protocols [Value description]

Output: An array of protocols names supported by cURL


Input: [Attribute] collapse [Type] boolean [Description]

Output: Whether to collapse children elements of an item menu (by default). Default value is: false.


Input: [Attribute] ref [Type] String [Description]

Output: A reference to a pre-defined menu item, such as a report (specified by the report goal name). Any elements explicitly given override those from the pre-defined reference.


Input: [Attribute] name [Type] String [Description]

Output: The name to display for the link.


Input: [Attribute] href [Type] String [Description]

Output: The href to use for the link.


Input: [Attribute] img [Type] String [Description]

Output: The source location of an image.


Input: [Attribute] position [Type] String [Since] 1.0.1 [Description]

Output: Where to place the image regarding the displayed name (left or right). Default value is: left.


Input: [Attribute] alt [Type] String [Since] 1.0.1 [Description]

Output: The alt to use for the image.


Input: [Attribute] border [Type] String [Since] 1.0.1 [Description]

Output: The border to use for the image.


Input: [Attribute] width [Type] String [Since] 1.0.1 [Description]

Output: The width to use for the image.


Input: [Attribute] height [Type] String [Since] 1.0.1 [Description]

Output: The height to use for the image.


Input: [Attribute] target [Type] String [Since] 1.0.1 [Description]

Output: Where the new document will be displayed when the user follows a link, i.e. _blank opens the new document in a new window.


Input: [Attribute] title [Type] String [Since] 1.3.0 [Description]

Output: The title to use for the image.


Input: [Description] Factory interface for creating elements for an index-based access data structure such as a List. [Interface]

Output: AutoPopulatingList.ElementFactory

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] A reference to an ConcurrentReferenceHashMap.Entry contained in the map. [Interface]

Output: ConcurrentReferenceHashMap.Reference

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] A strategy for handling errors. [Interface]

Output: ErrorHandler

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Extension of the Map interface that stores multiple values. [Interface]

Output: MultiValueMap

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Strategy interface for String-based path matching. [Interface]

Output: PathMatcher

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Strategy interface for persisting java.util.Properties, allowing for pluggable parsing strategies. [Interface]

Output: PropertiesPersister

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Strategy interface used to resolve replacement values for placeholders contained in Strings. [Interface]

Output: PropertyPlaceholderHelper.PlaceholderResolver

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Callback interface invoked on each field in the hierarchy. [Interface]

Output: ReflectionUtils.FieldCallback

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Callback optionally used to filter fields to be operated on by a field callback. [Interface]

Output: ReflectionUtils.FieldFilter

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Action to take on each method. [Interface]

Output: ReflectionUtils.MethodCallback

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Callback optionally used to filter methods to be operated on by a method callback. [Interface]

Output: ReflectionUtils.MethodFilter

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Simple strategy interface for resolving a String value. [Interface]

Output: StringValueResolver

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Description] Listener that is notified when the handle is being released. [Interface]

Output: WeakReferenceMonitor.ReleaseListener

org.springframework.util (Spring Framework 3.2.0.RC2 API)

Interface Summary


Input: [Interface] ActionParams [Description]

Output: An interface that is off the same format as the Map returned by Action.getParameters.

com.atlassian.jira.issue.transport (Atlassian JIRA 6.4.9 API)

Interface Summary


Input: [Interface] CollectionParams [Description]

Output: This is a field params with Lists as the value

com.atlassian.jira.issue.transport (Atlassian JIRA 6.4.9 API)

Interface Summary


Input: [Interface] FieldParams [Description]

Output: A parent interface for transport objects in JIRA.

com.atlassian.jira.issue.transport (Atlassian JIRA 6.4.9 API)

Interface Summary


Input: [Interface] FieldTransportParams [Description]

Output: This contains String > Collection of Transport Objects

com.atlassian.jira.issue.transport (Atlassian JIRA 6.4.9 API)

Interface Summary


Input: [Interface] FieldValuesHolder [Description]

Output: Key is the field id, the value contain Strings of a undetermined dimension

com.atlassian.jira.issue.transport (Atlassian JIRA 6.4.9 API)

Interface Summary


Input: [Interface] StringParams [Description]

Output: Field params where all values are collections of Strings

com.atlassian.jira.issue.transport (Atlassian JIRA 6.4.9 API)

Interface Summary


Input: [Variable] PBID_REFRESH [Description]

Output: wakeup time in seconds for pbid to run its checks

Difference between revisions of "PBI Manager/9.2" - PC-BSD Wiki

Table 7.47.2d: pbi_conf Variables [Tables 4]


Input: [Variable] PBI_INDEXREFRESH [Description]

Output: number of hours representing how often pbid refreshes the index and meta files from repos; default is every 24 hours

Difference between revisions of "PBI Manager/9.2" - PC-BSD Wiki


Input: [Variable] PBI_PROXYURL [Description]

Output: proxy server IP address

Difference between revisions of "PBI Manager/9.2" - PC-BSD Wiki


Input: [Variable] PBI_PROXYPORT [Description]

Output: proxy server port number

Difference between revisions of "PBI Manager/9.2" - PC-BSD Wiki


Input: [Variable] PBI_PROXYTYPE [Description]

Output: can be HTTP or SOCKS5

Difference between revisions of "PBI Manager/9.2" - PC-BSD Wiki


Input: [Variable] PBI_PROXYUSER [Description]

Output: username used to authenticate with proxy server

Difference between revisions of "PBI Manager/9.2" - PC-BSD Wiki


Input: [Variable] PBI_PROXYPASS [Description]

Output: password used to authenticate with proxy server

Difference between revisions of "PBI Manager/9.2" - PC-BSD Wiki


Input: [Name] Protocol field [Description]

Output: The protocol to use when communicating with the remote server. This can be: FTP TFTP SCP SFTP

Cisco UCS Manager GUI Configuration Guide, Release 1.4 - Managing Firmware [Cisco UCS Manager] - Cisco


Input: [Name] Server field [Description]

Output: The IP address or hostname of the remote server on which the catalog image resides.

Cisco UCS Manager GUI Configuration Guide, Release 1.4 - Managing Firmware [Cisco UCS Manager] - Cisco


Input: [Name] Filename field [Description]

Output: The name of the catalog executable you want to download.

Cisco UCS Manager GUI Configuration Guide, Release 1.4 - Managing Firmware [Cisco UCS Manager] - Cisco


Input: [Name] Path field [Description]

Output: The absolute path to the catalog image file on the remote server, if required. If you use SCP, the absolute path is always required. If you use any other protocol, you may not need to specify a remote path if the file resides in the default download folder. For details about how your file server is configured, contact your system administrator.

Cisco UCS Manager GUI Configuration Guide, Release 1.4 - Managing Firmware [Cisco UCS Manager] - Cisco


Input: [Name] User field [Description]

Output: The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP.

Cisco UCS Manager GUI Configuration Guide, Release 1.4 - Managing Firmware [Cisco UCS Manager] - Cisco


Input: [Name] Password field [Description]

Output: The password for the remote server username. This field does not apply if the protocol is TFTP.

Cisco UCS Manager GUI Configuration Guide, Release 1.4 - Managing Firmware [Cisco UCS Manager] - Cisco


Input: [Keyword] getter [Purpose] Defines behavior for when an object is indexed for property retrieval. [Special operation]

Output: Getters


Input: [Keyword] setter [Purpose] Defines behavior for when an object is indexed for property assignment or creation. [Special operation]

Output: Setters


Input: [Keyword] deleter [Purpose] Defines behavior for when an object is indexed for property deletion. [Special operation]

Output: Deleters


Input: [Keyword] legacycaller [Purpose] Defines behavior for when an object is called as if it were a function. [Special operation]

Output: Legacy callers


Input: [Keyword] stringifier [Purpose] Defines how an object is converted into a DOMString. [Special operation]

Output: Stringifiers


Input: [Keyword] serializer [Purpose] Defines how an object is converted into a serialized form. [Special operation]

Output: Serializers


Input: [Attribute] table [Type] String [Description]

Output: ORM : Name of the table

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] column [Type] String [Description]

Output: ORM : Name of the column to join our PK to in the join table (when only one column used)

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] primaryKey [Type] String [Description]

Output: ORM : Name of any primary key constraint to add for the join table

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] generatePrimaryKey [Type] String [Description]

Output: ORM : Whether to generate a PK constraint on the join table (when not specifying the name)

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] foreignKey [Type] String [Description]

Output: ORM : Name of any foreign-key constraint to add

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] generateForeignKey [Type] String [Description]

Output: ORM : Whether to generate a FK constraint on the join table (when not specifying the name)

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] index [Type] String [Description]

Output: ORM : Name of any index constraint to add

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] indexed [Type] String [Description]

Output: ORM : Whether the join column(s) is indexed

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] uniqueKey [Type] String [Description]

Output: ORM : Name of any unique constraint to add

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] unique [Type] String [Description]

Output: ORM : Whether the join column(s) has a unique constraint

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] columns [Type] Column[] [Description]

Output: ORM : Name of the columns to join our PK to in the join table (when multiple columns used)

DataNucleus Access Platform - JDO Annotations


Input: [Attribute] extensions [Type] Extension[] [Description]

Output: Vendor extensions

DataNucleus Access Platform - JDO Annotations


Input: [Type] directory [Description] The value for a directory-based environment variable. NAnt will convert it to an absolute path. [Required] False [Attribute]

Output: dir


Input: [Type] file [Description] The value for a file-based environment variable. NAnt will convert it to an absolute filename. [Required] False [Attribute]

Output: file


Input: [Type] string [Description] The name of a single Environment variable to set [Required] False [Attribute]

Output: name


Input: [Description] The value for a PATH like environment variable. You can use : or ; as path separators and NAnt will convert it to the platform's local conventions. [Required] False [Attribute]

Output: path


Input: [Type] string [Description] The literal value for the environment variable. [Required] False [Attribute]

Output: value


Input: [Type] bool [Description] Determines if task failure stops the build, or is just reported. The default is true. [Required] False [Attribute]

Output: failonerror


Input: [Type] bool [Description] If true then the task will be executed; otherwise, skipped. The default is true. [Required] False [Attribute]

Output: if


Input: [Type] bool [Description] Opposite of if. If false then the task will be executed; otherwise, skipped. The default is false. [Required] False [Attribute]

Output: unless


Input: [Type] bool [Description] Determines whether the task should report detailed build log messages. The default is false. [Required] False [Attribute]

Output: verbose


Input: [2] Click the Add button to add a new antenna for the selected location. When you click the Add button, the data fields change from inactive to active (gray to white). Complete all of the data fields, then click the Save button to save the new antenna. Repeat for each new antenna that you are adding. [0]

Output: Add


Input: [2] Click the Modify button to modify an existing antenna. To modify an existing antenna, first double-click its number from the Select Antenna list. The information for that antenna will appear in the data fields in gray. Then click the Modify button, and the data fields will become white, indicating that the information may be updated. Modify the antenna information as needed then click the Save button to save the changes to your antenna data. [0]

Output: Modify


Input: [2] Click the Delete button to delete an existing antenna. If you have already deleted an antenna during this filing session, you may reverse a delete action. When you click the deleted antenna on the Select Antenna list, this button becomes an Undelete button. To undelete a deleted antenna, highlight it and click the Undelete button. [0]

Output: Delete/ Undelete


Input: [2] Click the Save button to after adding or modifying an antenna to save your antenna information. [0]

Output: Save


Input: [2] Click the Clear button to cancel the current add or modify operation. [0]

Output: Clear


Input: [2] Click the Refresh button to reload antenna and location data. [0]

Output: Refresh


Input: [Widget Name] moviegrabber [Widget Type] buttonlist [Required?] Yes [Description]

Output: A list of the available movie grabber scripts.


Input: [Widget Name] tvgrabber [Widget Type] buttonlist [Required?] Yes [Description]

Output: A list of the available TV grabber scripts.


Input: [Widget Name] randomtrailercheck [Widget Type] checkbox [Required?] Yes [Description]

Output: A checkbox to enable random trailers before films.


Input: [Widget Name] trailernum [Widget Type] spinbox [Required?] Yes [Description]

Output: The number of random trailers to be played before a film.


Input: [Widget Name] unknownfilecheck [Widget Type] checkbox [Required?] Yes [Description]

Output: Enable/Disable display of unknown file types.


Input: [Widget Name] ok [Widget Type] button [Required?] Yes [Description]

Output: OK Button.


Input: [Widget Name] cancel [Widget Type] button [Required?] Yes [Description]

Output: Cancel Button.


Input: [Widget Name] helptext [Widget Type] textarea [Required?] Yes [Description]

Output: The help text for the selected item.


Input: [Widget Name] treeloadsmetacheck [Widget Type] checkbox [Required?] Yes [Description]

Output: Enable/Disable metadata loading in file browse mode.


Input: [Name] CustomAddCaseAction [Description]

Output: This action adds a case from an arbitrary solution and case type. It shows how you can build a custom action based on an existing IBM Case Manager action base class and action definition file.


Input: [Name] CustomAddToAttachmentAction [Description]

Output: This action adds a case document as an attachment. It shows how a custom action interacts with the action context to retrieve the context information and publish an event.


Input: [Name] CustomPageWidget [Description]

Output: This simple page widget shows the basic definition file format and the source code structure for defining a page widget. This widget also shows how to create a toolbar and a pop-up menu for a widget.


Input: [Name] CustomSearchWidget [Description]

Output: This page widget dynamically loads the case properties to search on using search API. It only searches on single value properties, not multi-value properties. It also does not search on date time fields.


Input: [Name] CommentWidget [Description]

Output: This page widget shows how to embed the Comment dialog box in a page widget. The widget coordinates with Case Toolbar page widget to save a case comment when the user saves a case. The widget also supports marking or clearing the dirty state of the page as case comments are added and saved.


Input: [Name] CustomCaseInfo [Description]

Output: This page widget provides a custom Case Information page widget that uses the CustomAddToAttachmentAction action. The widget shows how to specify a model object as part of the action context.


Input: [Name] CustomViewer [Description]

Output: This page widget shows how to customize an IBM Case Manager page widget.


Input: [Preference] extensions.firebug.showUserProps [Description] Toggles the display of user-defined object properties [Option]

Output: Show User-defined Properties


Input: [Preference] extensions.firebug.showUserFuncs [Description] Toggles the display of user-defined object methods [Option]

Output: Show User-defined Functions


Input: [Preference] extensions.firebug.showDOMProps [Description] Toggles the display of properties specified inside the DOM [Option]

Output: Show DOM Properties


Input: [Preference] extensions.firebug.showDOMFuncs [Description] Toggles the display of functions specified inside the DOM [Option]

Output: Show DOM Functions


Input: [Preference] extensions.firebug.showDOMConstants [Description] Toggles the display of constants specified inside the DOM [Option]

Output: Show DOM Constants


Input: [Preference] extensions.firebug.showInlineEventHandlers [Description] Toggles the display of inline event handlers [Option]

Output: Show Inline Event Handlers


Input: [Preference] extensions.firebug.showClosures [Description] Toggles the display of closures; See the Closure Inspector for more info on this [Option]

Output: Show Closures


Input: [Preference] extensions.firebug.showOwnProperties [Description] Specifies whether only an object's own properties shall be shown [Option]

Output: Show Own Properties Only


Input: [Preference] extensions.firebug.showEnumerableProperties [Description] Specifies whether only enumerable properties shall be shown [Option]

Output: Show Enumerable Properties Only


Input: [Preference] - [Description] Updates the display [Option]

Output: Refresh


Input: [Parameter] api_key [Required?] yes [Multiple?] no [Values] YOUR_API_KEY [Description]

Output: your API key. Only the API key that created a taste profile can update it

Taste Profile API Methods — The Echo Nest 4.2 documentation


Input: [Parameter] format [Required?] no [Multiple?] no [Values] json, xml, jsonp [Description]

Output: The desired format of the response

Taste Profile API Methods — The Echo Nest 4.2 documentation


Input: [Parameter] callback [Required?] Required if format is jsonp [Multiple?] no [Values] MyJSFunc [Description]

Output: the callback function for JSONP requests

Taste Profile API Methods — The Echo Nest 4.2 documentation


Input: [Parameter] id [Required?] yes [Multiple?] no [Values] CANVFPJ131839D8144 [Description]

Output: The ID of the taste profile

Taste Profile API Methods — The Echo Nest 4.2 documentation


Input: [Parameter] item [Required?] yes [Multiple?] yes [Values] kfw, ARK3D5J1187B9BA0B8, CAOFUDS12BB066268E:artist:kfw, 7digital-US:track:2930307 [Description]

Output: The id of the item(s) in the taste profile to be updated. This can be the simple item ID or the Rosetta ID of the item. The items must already be in the taste profile

Taste Profile API Methods — The Echo Nest 4.2 documentation


Input: [Parameter] skips [Required?] no [Multiple?] no [Values] 1 - 100 [Description]

Output: Increments the skip count for the specified item(s) by the given value

Taste Profile API Methods — The Echo Nest 4.2 documentation


Input: [Key] Up [Normal] Ch up [VDR] Crsr up [Channels] Crsr up [Timers] Crsr up [Edit/New] Crsr up [Recordings] Crsr up [Replay]

Output: Play

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Down [Normal] Ch down [VDR] Crsr down [Channels] Crsr down [Timers] Crsr down [Edit/New] Crsr down [Recordings] Crsr down [Replay]

Output: Pause

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Left [Normal] Prev group [VDR] - [Channels] Page up [Timers] Page up [Edit/New] Decrement [Recordings] Page up [Replay]

Output: Search back

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Right [Normal] Next group [VDR] - [Channels] Page down [Timers] Page down [Edit/New] Increment [Recordings] Page down [Replay]

Output: Search forward

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Ok [Normal] Ch display [VDR] Select [Channels] Switch [Timers] Edit [Edit/New] Accept [Recordings] Play [Replay]

Output: Progress disp.

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Menu [Normal] Menu on [VDR] Menu off [Channels] Menu off [Timers] Menu off [Edit/New] Menu off [Recordings] Menu off [Replay]

Output: Menu on

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Back [Normal] - [VDR] Menu off [Channels] VDR menu [Timers] VDR menu [Edit/New] Discard [Recordings] VDR menu [Replay]

Output: Recordings menu

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Red [Normal] - [VDR] Record [Channels] Edit [Timers] Edit [Edit/New] ABC/abc [Recordings] Play/Commands(2) [Replay]

Output: Jump

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Green [Normal] - [VDR] Language [Channels] New [Timers] New [Edit/New] Ins/Ovr [Recordings] Rewind [Replay]

Output: Skip -60s

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Yellow [Normal] - [VDR] Pause live [Channels] Delete [Timers] Delete [Edit/New] Delete [Recordings] Delete [Replay]

Output: Skip +60s

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] Blue [Normal] - [VDR] Stop/Resume [Channels] Mark [Timers] On/Off(1) [Edit/New] - [Recordings] Summary [Replay]

Output: Stop

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Key] 0..9 [Normal] Ch select [VDR] - [Channels] - [Timers] - [Edit/New] Numeric inp. [Recordings] Exec cmd(2) [Replay]

Output: Editing

Difference between revisions of "VDR User's Manual" - VDR Wiki


Input: [Property] actionPrefix [Type] string [Description] the prefix to the IDs of the actions. [Defined By]

Output: CWidget

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] controller [Type] CController [Description] the controller that this widget belongs to. [Defined By]

Output: CWidget

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] cssFile [Type] mixed [Description] the CSS file used for the widget. [Defined By]

Output: CMarkdown

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] id [Type] string [Description] id of the widget. [Defined By]

Output: CWidget

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] isFilter [Type] boolean [Description] whether this widget is used as a filter. [Defined By]

Output: CFilterWidget

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] markdownParser [Description] Returns the markdown parser instance. [Defined By]

Output: CMarkdown

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] owner [Type] CBaseController [Description] owner/creator of this widget. [Defined By]

Output: CWidget

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] purifyOutput [Type] boolean [Description] whether to use CHtmlPurifier to purify the generated HTML code. [Defined By]

Output: CMarkdown

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] stopAction [Type] boolean [Description] whether to stop the action execution when this widget is used as a filter. [Defined By]

Output: CFilterWidget

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] viewPath [Type] string [Description] Returns the directory containing the view files for this widget. [Defined By]

Output: CWidget

CMarkdown | Class Reference | Yii PHP Framework


Input: [Property] bubbles [Value]

Output: false

NetStream - Adobe ActionScript® 3 (AS3 ) API Reference


Input: [Property] cancelable [Value]

Output: false; there is no default behavior to cancel.

NetStream - Adobe ActionScript® 3 (AS3 ) API Reference


Input: [Property] currentTarget [Value]

Output: The object that is actively processing the Event object with an event listener.

NetStream - Adobe ActionScript® 3 (AS3 ) API Reference


Input: [Property] errorID [Value]

Output: A reference number associated with the specific error (AIR only).

NetStream - Adobe ActionScript® 3 (AS3 ) API Reference


Input: [Property] target [Value]

Output: The network object experiencing the input/output error.

NetStream - Adobe ActionScript® 3 (AS3 ) API Reference


Input: [Property] text [Value]

Output: Text to be displayed as an error message.

NetStream - Adobe ActionScript® 3 (AS3 ) API Reference


Input: [Statistic] result_set_queries [Scope] Connection [Notes] You may use it as an indirect measure for the number of queries PHP has sent to MySQL, for example, to identify a client that causes a high database load. [Description]

Output: Number of queries that have generated a result set. Examples of queries that generate a result set: SELECT, SHOW. The statistic will not be incremented if there is an error reading the result set header packet from the line.

Returned mysqlnd statistics: Result Set


Input: [Statistic] non_result_set_queries [Scope] Connection [Notes] You may use it as an indirect measure for the number of queries PHP has sent to MySQL, for example, to identify a client that causes a high database load. [Description]

Output: Number of queries that did not generate a result set. Examples of queries that do not generate a result set: INSERT, UPDATE, LOAD DATA, SHOW. The statistic will not be incremented if there is an error reading the result set header packet from the line.

Returned mysqlnd statistics: Result Set


Input: [Statistic] no_index_used [Scope] Connection [Description]

Output: Number of queries that have generated a result set but did not use an index (see also mysqld start option –log-queries-not-using-indexes). If you want these queries to be reported you can use mysqli_report(MYSQLI_REPORT_INDEX) to make ext/mysqli throw an exception. If you prefer a warning instead of an exception use mysqli_report(MYSQLI_REPORT_INDEX ^ MYSQLI_REPORT_STRICT).

Returned mysqlnd statistics: Result Set


Input: [Statistic] bad_index_used [Scope] Connection [Notes] If you want these queries to be reported you can use mysqli_report(MYSQLI_REPORT_INDEX) to make ext/mysqli throw an exception. If you prefer a warning instead of an exception use mysqli_report(MYSQLI_REPORT_INDEX ^ MYSQLI_REPORT_STRICT) [Description]

Output: Number of queries that have generated a result set and did not use a good index (see also mysqld start option –log-slow-queries).

Returned mysqlnd statistics: Result Set


Input: [Statistic] slow_queries [Scope] Connection [Notes] Not reported through mysqli_report() [Description]

Output: SQL statements that took more than long_query_time seconds to execute and required at least min_examined_row_limit rows to be examined.

Returned mysqlnd statistics: Result Set


Input: [Statistic] buffered_sets [Scope] Connection [Notes] Examples of API calls that will buffer result sets on the client: mysql_query(), mysqli_query(), mysqli_store_result(), mysqli_stmt_get_result(). Buffering result sets on the client ensures that server resources are freed as soon as possible and it makes result set scrolling easier. The downside is the additional memory consumption on the client for buffering data. Note that mysqlnd (unlike the MySQL Client Library) respects the PHP memory limit because it uses PHP internal memory management functions to allocate memory. This is also the reason why memory_get_usage() reports a higher memory consumption when using mysqlnd instead of the MySQL Client Library. memory_get_usage() does not measure the memory consumption of the MySQL Client Library at all because the MySQL Client Library does not use PHP internal memory management functions monitored by the function! [Description]

Output: Number of buffered result sets returned by normal queries. Normal means not prepared statement in the following notes.

Returned mysqlnd statistics: Result Set


Input: [Statistic] unbuffered_sets [Scope] Connection [Notes] Examples of API calls that will not buffer result sets on the client: mysqli_use_result() [Description]

Output: Number of unbuffered result sets returned by normal (non prepared statement) queries.

Returned mysqlnd statistics: Result Set


Input: [Statistic] ps_buffered_sets [Scope] Connection [Notes] Examples of API calls that will not buffer result sets on the client: mysqli_stmt_store_result [Description]

Output: Number of buffered result sets returned by prepared statements. By default prepared statements are unbuffered.

Returned mysqlnd statistics: Result Set


Input: [Statistic] ps_unbuffered_sets [Scope] Connection [Notes] By default prepared statements are unbuffered. [Description]

Output: Number of unbuffered result sets returned by prepared statements.

Returned mysqlnd statistics: Result Set


Input: [Statistic] flushed_normal_sets [Scope] Connection [Notes] Unbuffered result sets must be fetched completely before a new query can be run on the connection otherwise MySQL will throw an error. If the application does not fetch all rows from an unbuffered result set, mysqlnd does implicitly fetch the result set to clear the line. See also rows_skipped_normal, rows_skipped_ps. Some possible causes for an implicit flush: Faulty client application Client stopped reading after it found what it was looking for but has made MySQL calculate more records than needed Client application has stopped unexpectedly [Description]

Output: Number of result sets from normal (non prepared statement) queries with unread data which have been flushed silently for you. Flushing happens only with unbuffered result sets.

Returned mysqlnd statistics: Result Set


Input: [Statistic] flushed_ps_sets [Scope] Connection [Notes] Unbuffered result sets must be fetched completely before a new query can be run on the connection otherwise MySQL will throw an error. If the application does not fetch all rows from an unbuffered result set, mysqlnd does implicitly fetch the result set to clear the line. See also rows_skipped_normal, rows_skipped_ps. Some possible causes for an implicit flush: Faulty client application Client stopped reading after it found what it was looking for but has made MySQL calculate more records than needed Client application has stopped unexpectedly [Description]

Output: Number of result sets from prepared statements with unread data which have been flushed silently for you. Flushing happens only with unbuffered result sets.

Returned mysqlnd statistics: Result Set


Input: [Statistic] ps_prepared_never_executed [Scope] Connection [Notes] Prepared statements occupy server resources. You should not prepare a statement if you do not plan to execute it. [Description]

Output: Number of statements prepared but never executed.

Returned mysqlnd statistics: Result Set


Input: [Statistic] ps_prepared_once_executed [Scope] Connection [Notes] One of the ideas behind prepared statements is that the same query gets executed over and over again (with different parameters) and some parsing and other preparation work can be saved, if statement execution is split up in separate prepare and execute stages. The idea is to prepare once and cache results, for example, the parse tree to be reused during multiple statement executions. If you execute a prepared statement only once the two stage processing can be inefficient compared to normal queries because all the caching means extra work and it takes (limited) server resources to hold the cached information. Consequently, prepared statements that are executed only once may cause performance hurts. [Description]

Output: Number of prepared statements executed only one.

Returned mysqlnd statistics: Result Set


Input: [Statistic] rows_fetched_from_server_normal, rows_fetched_from_server_ps [Scope] Connection [Notes] See also packets_received_rset_row [Description]

Output: Total number of result set rows successfully fetched from MySQL regardless if the client application has consumed them or not. Some of the rows may not have been fetched by the client application but have been flushed implicitly.

Returned mysqlnd statistics: Result Set


Input: [Statistic] rows_buffered_from_client_normal, rows_buffered_from_client_ps [Scope] Connection [Notes] Examples of queries that will buffer results: mysqli_query(), mysqli_store_result() [Description]

Output: Total number of successfully buffered rows originating from a "normal" query or a prepared statement. This is the number of rows that have been fetched from MySQL and buffered on client. Note that there are two distinct statistics on rows that have been buffered (MySQL to mysqlnd internal buffer) and buffered rows that have been fetched by the client application (mysqlnd internal buffer to client application). If the number of buffered rows is higher than the number of fetched buffered rows it can mean that the client application runs queries that cause larger result sets than needed resulting in rows not read by the client.

Returned mysqlnd statistics: Result Set


Input: [Statistic] rows_fetched_from_client_normal_buffered, rows_fetched_from_client_ps_buffered [Scope] Connection [Description]

Output: Total number of rows fetched by the client from a buffered result set created by a normal query or a prepared statement.

Returned mysqlnd statistics: Result Set


Input: [Statistic] rows_fetched_from_client_normal_unbuffered, rows_fetched_from_client_ps_unbuffered [Scope] Connection [Description]

Output: Total number of rows fetched by the client from a unbuffered result set created by a "normal" query or a prepared statement.

Returned mysqlnd statistics: Result Set


Input: [Statistic] rows_fetched_from_client_ps_cursor [Scope] Connection [Description]

Output: Total number of rows fetch by the client from a cursor created by a prepared statement.

Returned mysqlnd statistics: Result Set


Input: [Statistic] rows_skipped_normal, rows_skipped_ps [Scope] Connection [Description]

Output: Reserved for future use (currently not supported)

Returned mysqlnd statistics: Result Set


Input: [Statistic] copy_on_write_saved, copy_on_write_performed [Scope] Process [Description]

Output: With mysqlnd, variables returned by the extensions point into mysqlnd internal network result buffers. If you do not change the variables, fetched data will be kept only once in memory. If you change the variables, mysqlnd has to perform a copy-on-write to protect the internal network result buffers from being changed. With the MySQL Client Library you always hold fetched data twice in memory. Once in the internal MySQL Client Library buffers and once in the variables returned by the extensions. In theory mysqlnd can save up to 40% memory. However, note that the memory saving cannot be measured using memory_get_usage().

Returned mysqlnd statistics: Result Set


Input: [Statistic] explicit_free_result, implicit_free_result [Scope] Connection, Process (only during prepared statement cleanup) [Notes] The free is always considered explicit but for result sets created by an init command, for example, mysqli_options(MYSQLI_INIT_COMMAND , ...) [Description]

Output: Total number of freed result sets.

Returned mysqlnd statistics: Result Set