Input: [No.] 2 [Value]

Output: Total number of messages in this room


Input: [No.] 3 [Value]

Output: Info flag: set to nonzero if the user needs to read this room's info file (see RINF command below)


Input: [No.] 4 [Value]

Output: Various flags associated with this room. (See LKRN cmd above)


Input: [No.] 5 [Value]

Output: The highest message number present in this room


Input: [No.] 6 [Value]

Output: The highest message number the user has read in this room


Input: [No.] 7 [Value]

Output: Boolean flag: 1 if this is a Mail> room, 0 otherwise.


Input: [No.] 8 [Value]

Output: Aide flag: 1 if the user is either the Room Aide for this room, or is a regular Aide (this makes access checks easy).


Input: [No.] 9 [Value]

Output: The number of new Mail messages the user has (useful for alerting the user to the arrival of new mail during a session)


Input: [No.] 10 [Value]

Output: The floor number this room resides on


Input: [No.] 11 [Value]

Output: The current“view” for this room (see views.txt for more info)


Input: [No.] 12 [Value]

Output: The default“view” for this room


Input: [No.] 13 [Value]

Output: Boolean flag: 1 if this is the user's Trash folder, 0 otherwise.


Input: [No.] 14 [Value]

Output: More flags associated with this room


Input: [No.] 15 [Value]

Output: Timestamp of the last write activity in this room (addition or deletion of messages, reconfiguration of room, etc)


Input: [Action Name] On Mouse Click [Touch Event] Emulated Mouse Event +300ms delay [Mouse Event]

Output: Mouse Click


Input: [Action Name] On Mouse Down [Touch Event] Emulated Mouse Event +300ms delay [Mouse Event]

Output: Mouse Down


Input: [Action Name] On Mouse Up [Touch Event] Emulated Mouse Event +300ms delay [Mouse Event]

Output: Mouse Up


Input: [Action Name] On Mouse Over [Touch Event] n/a [Mouse Event]

Output: Hover


Input: [Action Name] On Mouse Out [Touch Event] n/a [Mouse Event]

Output: End Hover


Input: [Action Name] On Drag [Touch Event] Tap and Drag [Mouse Event]

Output: Click and Drag


Input: [Option Window] Recording [Selection] Contents [Option]

Output: ID list selections by

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Text [Option]

Output: ID Menu selections by

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Mouse click if within object [Option]

Output: Record unsupported mouse drags as

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Record Object as text Auto record window size [Option]

Output: Window positions

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Put Robot in background [Option]

Output: While Recording

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Playback [Selection] Delay Between :5000 milliseconds [Option]

Output: Test Procedure Control

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] On Each window search [Option]

Output: Partial Window Caption

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Check – Match reverse captions Ignore file extensions Ignore Parenthesis [Option]

Output: Caption Matching options

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Test Log [Selection] Output Playback results to test log All details [Option]

Output: Test log Management

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] View test log after playback [Option]

Output: Update SQA repository

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Specify Test Log Info at Playback [Option]

Output: Test Log Data

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Unexpected Window [Selection] Check [Option]

Output: Detect

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Check [Option]

Output: Capture

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Select pushbutton with focus [Option]

Output: Playback response

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Abort playback [Option]

Output: On Failure to remove

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Wait States [Selection] Retry – 4 Timeout after 90 [Option]

Output: Wait Pos/Neg Region

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Retry – 2 Timeout after 120 [Option]

Output: Automatic wait

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Playback delay 100 millsec Check record delay after enter key [Option]

Output: Keystroke option

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Error Recovery [Selection] Abort Playback [Option]

Output: On Script command Failure

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Continue Execution [Option]

Output: On test case failure

Automated Testing Test Plan | KR Testing Solutions


Input: [Selection] Check all but last 2 [Option]

Output: SQA trap

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Object Recognition [Option]

Output: Do not change

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Object Data Test Definitions [Option]

Output: Do not change

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Editor [Option]

Output: Leave with defaults

Automated Testing Test Plan | KR Testing Solutions


Input: [Option Window] Preferences [Option]

Output: Leave with defaults

Automated Testing Test Plan | KR Testing Solutions


Input: [Class] BinaryMemcachedNodeImpl [Description]

Output: Implementation of MemcachedNode for speakers of the binary protocol.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] BinaryOperationFactory [Description]

Output: Factory for binary operations.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] GetAndTouchOperationImpl [Description]

Output: Implementation of the get and touch operation.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] GetlOperationImpl [Description]

Output: Implementation of the get and lock operation.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] GetsOperationImpl [Description]

Output: Implementation of the gets operation.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] KeyStatsOperationImpl [Description]

Output: A StatsOperationImpl.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] OptimizedSetImpl [Description]

Output: Optimized Set operation for folding a bunch of sets together.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] SASLAuthOperationImpl [Description]

Output: SASL authenticator.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] SASLBaseOperationImpl [Description]

Output: SASL authenticator.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] SASLStepOperationImpl [Description]

Output: A SASLStepOperationImpl.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] StatsOperationImpl [Description]

Output: A StatsOperationImpl.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] TapAckOperationImpl [Description]

Output: Implementation of a tap ACK operation.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] TapBackfillOperationImpl [Description]

Output: Implementation of a tap backfill operation.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] TapCustomOperationImpl [Description]

Output: Implementation of a custom tap operation.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] TapDumpOperationImpl [Description]

Output: Implementation of a tap dump operation.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] TapOperationImpl [Description]

Output: Abstract implementation of a tap operation.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [Class] TouchOperationImpl [Description]

Output: Operation to reset a timeout in Membase server.

net.spy.memcached.protocol.binary (couchbase-client 1.1-dp4 API)

Class Summary


Input: [type] string [default] am-fade [description] apply a CSS animation powered by ngAnimate [Name]

Output: animation

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] string [default] 'top' [description] how to position the tooltip - top | bottom | left | right | auto, or any combination like bottom-left or auto bottom-left. When "auto" is specified, it will dynamically reorient the tooltip. For example, if placement is "auto left", the tooltip will display to the left when possible, otherwise it will display right. [Name]

Output: placement

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] string [default] 'hover focus' [description] how tooltip is triggered - click | hover | focus | manual [Name]

Output: trigger

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] string [default] '' [description] default title value if titleattribute isn't present [Name]

Output: title

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] boolean [default] false [description] replace ng-bind with ng-bind-html, requires ngSanitize to be loaded [Name]

Output: html

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] number | object [default] 0 [description] delay showing and hiding the tooltip (ms) - does not apply to manual trigger type If a number is supplied, delay is applied to both hide/show Object structure is: delay: { show: 500, hide: 100 } [Name]

Output: delay

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] string | false [default] false [description] Appends the tooltip to a specific element. Example: container: 'body'. This option is particularly useful in that it allows you to position the tooltip in the flow of the document near the triggering element - which will prevent the tooltip from floating away from the triggering element during a window resize. [Name]

Output: container

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] string | DOMElement | false [default] false [description] Position the tooltip relative to a specific target element. [Name]

Output: target

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] path [default] false [description] If provided, overrides the default template, can be either a remote URL or a cached template id. It should be a div.tooltip element following Bootstrap styles conventions (like this). [Name]

Output: template

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] path [default] false [description] If provided, fetches the partial and includes it as the inner content, can be either a remote URL or a cached template id. [Name]

Output: contentTemplate

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] string [default] 'tooltip' [description] If provided, prefixes the events '.hide.before' '.hide' '.show.before' and '.show' with the passed in value. With the default value these events are 'tooltip.hide.before' 'tooltip.hide' 'tooltip.show.before' and 'tooltip.show' [Name]

Output: prefixEvent

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] string [default] '' [description] The tooltip instance id for usage in event handlers. [Name]

Output: id

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [type] string | object [default] { selector: 'body', padding: 0 } [description] Keeps the tooltip within the bounds of this element. Example: viewport: '#viewport' or { "selector": "#viewport", "padding": 0 } [Name]

Output: viewport

AngularStrap - AngularJS 1.2+ native directives for Twitter Bootstrap 3.


Input: [Structure] File Header [Located?] Beginning of file [Purpose]

Output: Overview of the file; controls layout of other sections


Input: [Structure] Optional Header [Located?] Follows file header [Purpose]

Output: For executables, used to store the initial %eip


Input: [Structure] Section Header [Located?] Follow optional header; count determined by file header [Purpose]

Output: Maintain location and size information about code and data sections


Input: [Structure] Section Data [Located?] Stored in section header [Purpose]

Output: Contains code and data for the program


Input: [Structure] Relocation Directives [Located?] Stored in section header [Purpose]

Output: Contain fixup information needed when relocating a section


Input: [Structure] Line Numbers [Located?] Stored in section header [Purpose]

Output: Hold address of each line number in code/data sections


Input: [Structure] Symbol Table [Located?] Stored in file header [Purpose]

Output: Contains one entry for each symbol this file defines or references


Input: [Structure] String Table [Located?] Follows symbol table [Purpose]

Output: Stores symbol names; first four bytes are total length


Input: [DeployJob] excludeDiscoveryJobs [1] boolean [2] True to exclude Component Discovery Jobs from the exported object, false to include them. [3]

Output: false

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] excludeComplianceJobs [1] boolean [2] True to exclude Compliance Jobs from the exported object, false to include them. [3]

Output: false

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] excludeSoftwareDeployJobs [1] boolean [2] True to exclude Software Deploy Jobs from the exported object, false to include them. [3]

Output: false

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] excludeDepotSoftware [1] boolean [2] True to exclude depot software objects from the exported object, false to include them. [3]

Output: true

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] excludeBlPackages [1] boolean [2] True to exclude BLPackages from the exported object, false to include them. [3]

Output: true

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] convertSoftlinks [1] boolean [2] True to convert BLPackage soft links to hard links, false to preserve the soft links. [3]

Output: false

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] includeGrammars [1] boolean [2] True to include referenced grammar files, false to exclude them. Note that setting this argument to false requires grammar file mapping on the importing system. [3]

Output: false

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] excludeTemplates [1] boolean [2] True to exclude component templates, false to include them. [3]

Output: false

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] excludeNSHScripts [1] boolean [2] True to exclude NSH scripts, false to include them. [3]

Output: false

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] excludeDepotFiles [1] boolean [2] True to exclude depot files, false to include them. [3]

Output: true

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [DeployJob] excludeNSHScriptJobs [1] boolean [2] True to exclude NSH Script Jobs, false to include them. [3]

Output: false

Exporting Jobs from Test and importing to Produ... | BMC Communities


Input: [Vocabulary] skos:semanticRelation [Descriptive Definition] Instance of owl:ObjectProperty Domain: skos:Concept Range: skos:Concept [Element]

Output: Semantic relationship

Advantages of thesauri representation with the Simple Knowledge Organization System (SKOS) compared with other proposed alternatives for the design of a Web-based thesauri management system

Table 4: Vocabulary and definitions of classes and properties for elements of semantic relationships


Input: [Vocabulary] skos:broaderTransitive [Descriptive Definition] Instance of owl:ObjectProperty Instance of owl:TransitiveProperty and Sub-property of skos:semanticRelation [Element]

Output: Broader transitive

Advantages of thesauri representation with the Simple Knowledge Organization System (SKOS) compared with other proposed alternatives for the design of a Web-based thesauri management system


Input: [Vocabulary] skos:narrowerTransitive [Descriptive Definition] Instance of owl:ObjectProperty Instance of owl:TransitiveProperty Defined as owl:inverseOf de skos:broaderTransitive Sub-property of skos:semanticRelation [Element]

Output: Narrower transitive

Advantages of thesauri representation with the Simple Knowledge Organization System (SKOS) compared with other proposed alternatives for the design of a Web-based thesauri management system


Input: [Vocabulary] skos:broader [Descriptive Definition] Instance of owl:ObjectProperty Not instance of owl:TransitiveProperty Sub-property of skos:broaderTransitive [Element]

Output: Generic broader

Advantages of thesauri representation with the Simple Knowledge Organization System (SKOS) compared with other proposed alternatives for the design of a Web-based thesauri management system


Input: [Vocabulary] skos:narrower [Descriptive Definition] Instance of owl:ObjectProperty Not instance of owl:TransitiveProperty Defined as owl:inverseOf de skos:broader Sub-property of skos:narrowerTransitive [Element]

Output: Generic narrower

Advantages of thesauri representation with the Simple Knowledge Organization System (SKOS) compared with other proposed alternatives for the design of a Web-based thesauri management system


Input: [Vocabulary] skos:related [Descriptive Definition] Instance of owl:ObjectProperty Instance of owl:SymmetricProperty Not instance of de owl:TransitiveProperty Sub-property of skos:semanticRelation Disjoint with skos:broaderTransitive [Element]

Output: Related

Advantages of thesauri representation with the Simple Knowledge Organization System (SKOS) compared with other proposed alternatives for the design of a Web-based thesauri management system


Input: [Syntax] %(:orask:) [Description] If a value for the shortcut cannot be determined automatically, the user is prompted when the command is invoked. The is text that will be displayed when the user is asked to enter a value. [Option]

Output: orask


Input: [Syntax] %(:else:) [Description] If a value for the shortcut cannot be determined automatically, then is used. [Option]

Output: else


Input: [Syntax] %(:lowercase) [Description] The interpolation result will all be lower cased. [Option]

Output: lowercase


Input: [Syntax] %(:uppercase) [Description] The interpolation result will all be upper cased. [Option]

Output: uppercase


Input: [Syntax] %(:capitalize) [Description] The first character of the interpolation result will be upper cased. [Option]

Output: capitalize


Input: [Syntax] %(:dirname) [Description] The parent directory of the resulting shortcut code. [Option]

Output: dirname


Input: [Syntax] %(:basename) [Description] The base name (leaf name) of the resulting shortcut code. [Option]

Output: basename


Input: [Range] 1xx [Purpose]

Output: Positive Preliminary Reply The request is being initiated and you should expect another reply before proceeding with a new command. (The user-process sending another command before the completion reply would be in violation of protocol; but server-FTP processes should queue any commands that arrive while a preceding command is in progress.) This type of reply can be used to indicate that the command was accepted and the user-process may now pay attention to the data connections, for implementations where simultaneous monitoring is difficult. The server-FTP process may send at most, one 1xx reply per command.

SmartFile | Business File Sharing and FTP Hosting


Input: [Range] 2xx [Purpose]

Output: Positive Completion Reply The request was successfully completed. A new request may now be initiated.

SmartFile | Business File Sharing and FTP Hosting


Input: [Range] 3xx [Purpose]

Output: Positive Intermediate Reply The command was accepted, but the request is being held in abeyance, pending receipt of further information. The user should send another command specifying this information. This reply is used in command sequence groups.

SmartFile | Business File Sharing and FTP Hosting


Input: [Range] 4xx [Purpose]

Output: Transient Negative Completion Reply The command wasn’t accepted and the request didn’t occur, but the error condition is temporary and the action may be requested again. The user should return to the beginning of the command sequence, if any. It is difficult to assign a meaning to “transient”, particularly when two distinct sites (Server- and User-processes) have to agree on the interpretation. Each reply in the 4xx category might have a slightly different time value, but the intent is that the user-process is encouraged to try again. A rule of thumb in determining if a reply fits into the 4xx or the 5xx (Permanent Negative) category is that replies are 4xx if the commands can be repeated without any change in command form or in properties of the User or Server (e.g., the command is spelled the same with the same arguments used; the user does not change his file access or user name; the server does not put up a new implementation.)

SmartFile | Business File Sharing and FTP Hosting


Input: [Range] 5xx [Purpose]

Output: Permanent Negative Completion Reply The command wasn’t accepted and the requested action didn’t occur. The User-process is discouraged from repeating the exact request (in the same sequence). Even some “permanent” error conditions can be corrected, so the human user may want to direct his User-process to reinitiate the command sequence by direct action at some point in the future (e.g., after the spelling was changed, or the user has altered his directory status.)

SmartFile | Business File Sharing and FTP Hosting


Input: [Range] 6xx [Purpose]

Output: Protected Reply The RFC 2228 introduced the concept of protected replies to increase security over the FTP communications. The 6xx replies are Base64 encoded protected messages that serves as responses to secure commands. When properly decoded, these replies fall into the above categories.

SmartFile | Business File Sharing and FTP Hosting


Input: [Field] basket [Description]

Output: Representation of a platform basket.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/token [Description]

Output: A 40 character token that can be created by a client programm and passed to the platform on basket retrieval. Can be used to later retrieve the same basket in case the basket id is not known. Token could be a session id for example.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/shop [Description]

Output: Reference to the shop for which you created that basket. Null means the basket belongs to no shop, i.e. to the Spreadshirt marketplace right now.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/user [Description]

Output: Reference to the user (customer) that owns that basket. Null means the basket belongs to no specific customer.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/basketItems [Description]

Output: List of basket items that are actually in the basket. See Basket Item for more details.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/links [Description]

Output: Different links, for example shop checkout link, platform checkout link or default checkout link that is calculated for the current basket.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/shipping [Description]

Output: Shipping data for basket.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/shipping/shippingType [Description]

Output: The selected shippingType.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/shipping/price [Description]

Output: The shipping price.

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/discounts [Description]

Output: List of discounts that apply and total discount value (for all basket items -> basket item discount x basket item quantity).

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/priceItems [Description]

Output: Total for all basket items only without shipping cost, discounts, etc. (for all basket items -> basket price item x basket item quantity).

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [Field] basket/priceTotal [Description]

Output: Total for basket with price of all items, discounts, shipping costs, etc..

Basket Resources - 1. API - Spreadshirt Developer Network


Input: [TraceCategory] Deprecation [TraceEvent] Deprecation Announcement [PackageName] sqlserver [XEEventName]

Output: deprecation_announcement

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Deprecation [TraceEvent] Deprecation Final Support [PackageName] sqlserver [XEEventName]

Output: deprecation_final_support

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Errors and Warnings [TraceEvent] ErrorLog [PackageName] sqlserver [XEEventName]

Output: errorlog_written

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Errors and Warnings [TraceEvent] EventLog [PackageName] sqlserver [XEEventName]

Output: error_reported

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Errors and Warnings [TraceEvent] Exception [PackageName] sqlos [XEEventName]

Output: exception_ring_buffer_recorded

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Errors and Warnings [TraceEvent] User Error Message [PackageName] sqlserver [XEEventName]

Output: error_reported

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Full text [TraceEvent] FT:Crawl Aborted [PackageName] sqlserver [XEEventName]

Output: error_reported

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Locks [TraceEvent] Deadlock graph [PackageName] sqlserver [XEEventName]

Output: xml_deadlock_report

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Locks [TraceEvent] Lock:Acquired [PackageName] sqlserver [XEEventName]

Output: lock_acquired

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Locks [TraceEvent] Lock:Deadlock [PackageName] sqlserver [XEEventName]

Output: lock_deadlock

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Locks [TraceEvent] Lock:Released [PackageName] sqlserver [XEEventName]

Output: lock_released

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Locks [TraceEvent] Lock:Timeout [PackageName] sqlserver [XEEventName]

Output: locks_lock_timeouts

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Locks [TraceEvent] Lock:Timeout (timeout > 0) [PackageName] sqlserver [XEEventName]

Output: locks_lock_timeout_greater_than_0

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Stored Procedures [TraceEvent] RPC Output Parameter [PackageName] sqlserver [XEEventName]

Output: rpc_completed

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Stored Procedures [TraceEvent] RPC:Completed [PackageName] sqlserver [XEEventName]

Output: rpc_completed

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Stored Procedures [TraceEvent] RPC:Starting [PackageName] sqlserver [XEEventName]

Output: rpc_starting

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Stored Procedures [TraceEvent] SP:Completed [PackageName] sqlserver [XEEventName]

Output: module_end

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Stored Procedures [TraceEvent] SP:Recompile [PackageName] sqlserver [XEEventName]

Output: sp_statement_starting

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Stored Procedures [TraceEvent] SP:Starting [PackageName] sqlserver [XEEventName]

Output: module_start

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Stored Procedures [TraceEvent] SP:StmtCompleted [PackageName] sqlserver [XEEventName]

Output: sp_statement_completed

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] Stored Procedures [TraceEvent] SP:StmtStarting [PackageName] sqlserver [XEEventName]

Output: sp_statement_starting

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] TSQL [TraceEvent] SQL:StmtCompleted [PackageName] sqlserver [XEEventName]

Output: sql_statement_completed

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] TSQL [TraceEvent] SQL:StmtRecompile [PackageName] sqlserver [XEEventName]

Output: sql_statement_starting

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] TSQL [TraceEvent] SQL:StmtStarting [PackageName] sqlserver [XEEventName]

Output: sql_statement_starting

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [TraceCategory] User configurable [TraceEvent] UserConfigurable [PackageName] sqlserver [XEEventName]

Output: user_settable

An XEvent a Day (20 of 31) - Mapping Extended Events to SQL Trace - Jonathan Kehayias


Input: [Key] access_token [Default Value] Empty [Description]

Output: This is the access token for an authorized user. You obtain this from API via OAuth


Input: [Key] redirect_uri [Default Value] Empty [Description]

Output: The redirect URI you defined when setting up your Instagram client


Input: [Key] client_ip [Default Value] Empty [Description]

Output: The IP address of the client. This is used to sign POST & DELETE requests. It's not required, but without the signing, users are more limited in how many likes/comments they can post in a given hour


Input: [Key] scope [Default Value] comments+relationships+likes [Description]

Output: The scope of your client's capability


Input: [Key] log_enabled [Default Value] TRUE [Description]

Output: Enable logging


Input: [Key] log_level [Default Value] DEBUG [Description]

Output: Log level. See Monolog Logger


Input: [Key] log_path [Default Value] ./instaphp.log [Description]

Output: Where the log file lives


Input: [Key] http_useragent [Default Value] Instaphp/2.0; cURL/{curl_version}; (+http://instaphp.com) [Description]

Output: The user-agent string sent with all requests


Input: [Key] http_timeout [Default Value] 6 [Description]

Output: Timeout for requests to the API.


Input: [Key] http_connect_timeout [Default Value] 2 [Description]

Output: Timeout for http connect


Input: [Key] debug [Default Value] FALSE [Description]

Output: Debug mode?


Input: [Key] event.before [Default Value] Empty [Description]

Output: Callback called prior to sending the request to the API. Method takes a single parameter BeforeEvent


Input: [Key] event.after [Default Value] Empty [Description]

Output: Callback called after a response is received from the API. Method takes a single parameter of CompleteEvent


Input: [Key] event.error [Default Value] Empty [Description]

Output: Callback called when an error response is received from the API. Method takes a single parameter of ErrorEvent.


Input: [Error Message] Challenge response failed. [Description] Incorrect Responses [Method]

Output: processChaRes

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Hint was not defined. [Description] does not set isError()==true, can be ignored as hint is not being used [Method]

Output: processChaRes

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] All fields are required. [Description] Empty response array [Method]

Output: processChaRes

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Passwords must match. [Description] Different new/confirm passwords [Method]

Output: processChgPwd

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] All fields are required. [Description] Empty new/confirm passwords [Method]

Output: processChgPwd

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Password does not meet the minimum numeric character requirement. [Description] If password does not meet AD complexity and has no numbers [Method]

Output: processChgPwd

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Password is too short. [Description] new password is not long enough [Method]

Output: processChgPwd

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Password attribute violation has been detected. [Description] If password is same as first, last, full, email or loginID [Method]

Output: processChgPwd

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Password is on the exclusion list. [Description] If password == ‘password’ or other value explicitly excluded [Method]

Output: processChgPwd

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Password does not meet the uppercase character minimum requirement. [Description] If password does not meet AD complexity and has no letters [Method]

Output: processChgPwd

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] [remote NullPointerException ] [Description] Password > 517 chars [Method]

Output: processChgPwd

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Password is not unique. [Description] if password used previously [Method]

Output: processUser

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Forgot password feature disabled. [Description] If password policy has forgotten password disabled [Method]

Output: processUser

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Answers to challenge response questions have not been set, or cannot be read at this time. [Description] Responses not saved [Method]

Output: processUser

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [Error Message] Account restrictions prevent you from logging in. See your administrator for more details. [Description] loginDisabled=true or lockedByIntruder=true [Method]

Output: processUser

RBPM Web Services - Developer Guide - Cool Solutions | NetIQ


Input: [code] 200 [type] Success [description]

Output: Request was fulfilled


Input: [code] 201 [type] Success [description]

Output: A new resource was created


Input: [code] 400 [type] Error [description]

Output: The request cannot be fulfilled


Input: [code] 404 [type] Error [description]

Output: Resource not found


Input: [code] 422 [type] Error [description]

Output: Validation failure


Input: [code] 500 [type] Error [description]

Output: An internal server error occurred


Input: [Control] START [Task]

Output: Start Media Center, or go to the Start menu if Media Center is already running.

best10 > PRODUCT > How do I use the RC197 remote


Input: [Control] UP [Task]

Output: Move to the item above.

best10 > PRODUCT > How do I use the RC197 remote


Input: [Control] DOWN [Task]

Output: Move to the item below.

best10 > PRODUCT > How do I use the RC197 remote


Input: [Control] LEFT [Task]

Output: Move to the item on the left, or move to the menu. If a slide show is playing, return to the previous picture.

best10 > PRODUCT > How do I use the RC197 remote


Input: [Control] RIGHT [Task]

Output: Move to the item on the right, or move from the menu to the folder items. If a slide show is playing, skip to the next picture.

best10 > PRODUCT > How do I use the RC197 remote


Input: [Control] OK [Task]

Output: Select the active item.

best10 > PRODUCT > How do I use the RC197 remote


Input: [Control] BACK [Task]

Output: Go to the previous screen.

best10 > PRODUCT > How do I use the RC197 remote


Input: [Control] MORE [Task]

Output: Show information about the selected item.

best10 > PRODUCT > How do I use the RC197 remote


Input: [Element Name] id [Data Type] Integer [Description]

Output: The id of the control. The id will couple the skin file to the code, so if we later on want to check that a user pressed a button, the id will be required and must be unique. For controls that will never be referenced in the code it is safe to set it to "1"


Input: [Element Name] description [Data Type] String [Description]

Output: An optional description of the control for your reference


Input: [Element Name] type [Data Type] String [Description]

Output: The type of the control, for instance "button", "label", "textbox" and all other controls.


Input: [Element Name] posX [Data Type] Integer [Description]

Output: The X-position on the window for this control


Input: [Element Name] posY [Data Type] Integer [Description]

Output: The Y-position on the window for this control


Input: [Element Name] width [Data Type] Integer [Description]

Output: The width of this control


Input: [Element Name] height [Data Type] Integer [Description]

Output: The height of this control


Input: [Element Name] onleft [Data Type] Integer [Description]

Output: The control id to move the focus to when the user moves left. If not specified (or zero) MediaPortal will find the closest control in that direction to move to. As of v1.7.0 Skin Settings and Skin Expressions are also supported.


Input: [Element Name] onright [Data Type] Integer [Description]

Output: The control id to move the focus to when the user moves right. If not specified (or zero) MediaPortal will find the closest control in that direction to move to. As of v1.7.0 Skin Settings and Skin Expressions are also supported.


Input: [Element Name] onup [Data Type] Integer [Description]

Output: The control id to move the focus to when the user moves up. If not specified (or zero) MediaPortal will find the closest control in that direction to move to. As of v1.7.0 Skin Settings and Skin Expressions are also supported.


Input: [Element Name] ondown [Data Type] Integer [Description]

Output: The control id to move the focus to when the user moves down. If not specified (or zero) MediaPortal will find the closest control in that direction to move to. As of v1.7.0 Skin Settings and Skin Expressions are also supported.


Input: [Element Name] colordiffuse [Data Type] Long [Description]

Output: Allows you to mix a color & a graphics texture. E.g. If you have a graphics texture like a blue button you can mix it with a yellow color diffuse and the end result will be green. Defaults to 0xFFFFFFFF


Input: [Element Name] dimColor [Data Type] Integer [Description]

Output: Color for a control when it is not focussed. Defaults to half transparent (0x60ffffff)


Input: [Element Name] onfocus [Data Type] String [Description]

Output: [Since 1.3] Executes a MediaPortal skin function when the control gains focus. See Skin Settings for more information.


Input: [Type] area [Description]

Output: Visualizes quantitative data with a fill between an axis and relevant data points.


Input: [Type] areaspline [Description]

Output: An Area Chart in which data points are connected by a curve.


Input: [Type] bar [Description]

Output: Visualizes bars positioned vertically along a category or time axis. The bars' lengths are proportional to the values they represent along a horizontal axis.


Input: [Type] column [Description]

Output: Visualizes bars positioned vertically along a category or time axis. The bars' lengths are proportional to the values they represent along a horizontal axis.


Input: [Type] combo [Description]

Output: Combination of line, marker and area chart. By default, there is no area fill. This is the default type for a Chart.


Input: [Type] combospline [Description]

Output: A combo chart in which the data points are connected by a curve.


Input: [Type] line [Description]

Output: Visualizes quantitative data on a graph by connecting relevant data points.


Input: [Type] markerseries [Description]

Output: Visualizes quantitative data by plotting relevant data points on a graph.


Input: [Type] pie [Description]

Output: A circular chart divided into wedges which represent data as a percentage of a whole.


Input: [Type] spline [Description]

Output: Visualizes quantitative data on a graph by connecting relevant data points with a curve.


Input: [menu item] Full screen [action]

Output: The window is enlarged to fill the entire screen, its borders are removed, and it is stacked on top of all other windows. The exact action depends on the window system of your computer. The menu option is changed to "Normal window" (see below).


Input: [menu item] Normal window [action]

Output: The window is reduced back to the its original size, with normal borders. The menu option is changed back to "Full screen" (see above).


Input: [menu item] Output view [action]

Output: Output to the stderr (standard error) the current values for the window and slab parameters, and the transformation matrix to be used in a transform command applied to all atoms to give the current view of the molecule. This feature allows the user to find a good view in an interactive fashion. The output text can be cut-and-pasted into the input file.


Input: [menu item] Reset view [action]

Output: Reset the view parameters (see above) to the original values before the interactive changes made by the user.


Input: [menu item] Re-read input file [action]

Output: Read the input file again, as if the program had been started from scratch. This allows the user to modify the input file using a text editor, and then quickly view the effect of the changes. If an error is encountered the input file, then interpretation stops, but the graphics objects rendered so far should be visible. This item will appear only if the command-line option -in has been used.


Input: [menu item] Quit [action]

Output: Quit the current session. The keyboard Esc key can also be used to quit the the current session.


Input: [Name] type [Req] M [Description] Image type, e.g. jpeg or png. [Type]

Output: string


Input: [Name] file [Req] O [Description] Image file path. If specified, the data is ignored unless the file cannot be loaded. [Type]

Output: string


Input: [Name] data [Req] O [Description] Name of a data section defined as a child of the report element. [Type]

Output: string


Input: [Name] scale [Req] O [Description] Scaling mode: cut, fill (adjust image to the box) or grow (adjust the box to the image.) [Type]

Output: string


Input: [Name] proportional [Req] O [Description] If True (default), image or box proportions are kept with fill and grow scaling modes. [Type]

Output: boolean


Input: [Name] embed [Req] O [Description] If True (default), the image is embedded in the PRP file. [Type]

Output: boolean


Input: [Property:] Cast Shadows [Function:]

Output: If enabled, the mesh will create shadows when a shadow-casting Light shines on it. The options are On and Off to enable/disable shadows, Two Sided to allow shadows to be cast from either side of the mesh (ie, backface culling is not taken into account) and Shadows Only (ie, the shadows should be visible but not the mesh itself).


Input: [Property:] Receive Shadows [Function:]

Output: If enabled, the mesh will display any shadows being cast upon it.


Input: [Property:] Materials [Function:]

Output: A list of Materials to render the model with.


Input: [Property:] Use Light Probes [Function:]

Output: Enable probe-based lighting for this mesh.


Input: [Property:] Use Reflection Probes [Function:]

Output: Enable probe-based reflections for this mesh.


Input: [Property:] Anchor Override [Function:]

Output: A Transform used to determine the interpolation position when the light probe or reflection probe systems are used.


Input: [Term] Organization [Mapping] org:Organization1 [Definition]

Output: A group with a common purpose or reason for existence that goes beyond the set of people belonging to it, e.g. a social, commercial or political structure


Input: [Term] name [Mapping] skos:prefLabel [Definition]

Output: A primary name, e.g. a legally recognized name


Input: [Term] alternate name [Mapping] skos:altLabel [Definition]

Output: An alternate name, e.g. a trading or colloquial name


Input: [Term] former name [Mapping] opengov:otherName [Definition]

Output: A former name, e.g. a pre-merger name


Input: [Term] identifier [Mapping] org:identifier [Definition]

Output: An issued identifier, e.g. a DUNS number, GLN, etc.


Input: [Term] classification [Mapping] org:classification [Definition]

Output: An organizational category, e.g. charity, committee, etc.


Input: [Term] parent organization [Mapping] org:subOrganizationOf2 [Definition]

Output: The organization that contains this organization


Input: [Term] geographic area [Mapping] opengov:area [Definition]

Output: The geographic area to which the organization is related


Input: [Term] one-line description [Mapping] dcterms:abstract [Definition]

Output: A one-line description of an organization


Input: [Term] description [Mapping] dcterms:description [Definition]

Output: An extended description of an organization


Input: [Term] date of founding [Mapping] schema:foundingDate [Definition]

Output: A date of founding


Input: [Term] date of dissolution [Mapping] schema:dissolutionDate [Definition]

Output: A date of dissolution, termination, expiry, etc.


Input: [Term] image [Mapping] schema:image [Definition]

Output: A URL of an image


Input: [Term] contact detail [Mapping] opengov:contactDetail [Definition]

Output: A means of contacting the organization


Input: [Term] external links [Mapping] rdfs:seeAlso [Definition]

Output: A URL to a document about the organization


Input: [Field Name] Available Rake [Description] The Rake under which the sick mark occurs. [Valid I/P] 2002 inward on 06-jan-2006 Selectable [Field Type]

Output: String List


Input: [Field Name] Location [Description] It tells the location of the Rake [Limit] 15char [Valid I/P] PLTF ReadOnly [Field Type]

Output: String


Input: [Field Name] Department [Description] The department under which the coach mark sick. [Limit] 15char [Valid I/P] AC Defect Selectable [Field Type]

Output: String


Input: [Field Name] Sel [Description] It selects the coach under which the defect found. [Limit] 2char [Valid I/P] 5 Selectable [Field Type]

Output: String


Input: [Field Name] Ch.P.E [Description] The Coach Position from Engine [Limit] 2char [Valid I/P] 3 ReadOnly [Field Type]

Output: String


Input: [Field Name] Ong. Rly [Description] The Owning Railways Regions [Valid I/P] NR ReadOnly [Field Type]

Output: String List


Input: [Field Name] Type [Description] The coach type under which the sick mark found. [Valid I/P] WLRRM ReadOnly [Field Type]

Output: String List


Input: [Field Name] Coach No. [Description] The coach number under which sick mark found. [Valid I/P] 00851 ReadOnly [Field Type]

Output: String List


Input: [Field Name] From [Description] List of station from which the train originate. [Limit] 4char [Valid I/P] NDLS ReadOnly [Field Type]

Output: String


Input: [Field Name] To [Description] List of station at which the train terminate. [Limit] 4char [Valid I/P] BPL ReadOnly [Field Type]

Output: String


Input: [Field Name] Sick Reason [Description] The reason under which the coach become sick. [Valid I/P] AC1/AC2 Selectable [Field Type]

Output: String List


Input: [Field Name] Marking Date [Description] The date at which the coach found sick. [Limit] 11char [Valid I/P] 08-jan-2006 Editable/ Writable [Field Type]

Output: String


Input: [Field Name] Marking Time [Description] The time at which the coach found sick. [Limit] 2char for each [Valid I/P] 22:30 Editable/ Writable [Field Type]

Output: String in hours & minute.


Input: [Parameter Name] JPIMAGEVIEWER_width [Range of Values] Any positive valid integer value eg. 200 [Description]

Output: The width in pixels of the full size image display area

JavaScript CSS Image Viewer - Free Trial Download


Input: [Parameter Name] JPIMAGEVIEWER_height [Range of Values] Any positive valid integer value eg. 200 [Description]

Output: The height in pixels of the full size image display area

JavaScript CSS Image Viewer - Free Trial Download


Input: [Parameter Name] JPIMAGEVIEWER_thumbwidth [Range of Values] Any positive valid integer value eg. 50 [Description]

Output: The width in pixels of the thumbnail images

JavaScript CSS Image Viewer - Free Trial Download


Input: [Parameter Name] JPIMAGEVIEWER_thumbheight [Range of Values] Any positive valid integer value eg. 50 [Description]

Output: The height in pixels of the thumbnail images

JavaScript CSS Image Viewer - Free Trial Download


Input: [Parameter Name] JPIMAGEVIEWER_bgcolor [Range of Values] Any valid HTML color specification eg. #FFFFFF [Description]

Output: The background color

JavaScript CSS Image Viewer - Free Trial Download


Input: [Parameter Name] JPIMAGEVIEWER_bordercolor [Range of Values] Any valid HTML color specification eg. #8C8C8C [Description]

Output: The border color

JavaScript CSS Image Viewer - Free Trial Download


Input: [Parameter Name] JPIMAGEVIEWER_borderwidth [Range of Values] Any positive valid integer value eg. 1 [Description]

Output: The width of the border in pixels

JavaScript CSS Image Viewer - Free Trial Download


Input: [Parameter Name] JPIMAGEVIEWER_bordergap [Range of Values] Any positive valid integer value eg. 5 [Description]

Output: Gap between the border and the image content in pixels

JavaScript CSS Image Viewer - Free Trial Download


Input: [Parameter Name] JPIMAGEVIEWER_lkey [Range of Values] A valid license key [Description]

Output: If the licensed version is being used then the license key should be supplied with this parameter

JavaScript CSS Image Viewer - Free Trial Download


Input: [Setting] Lookup audio CD track names from freedb.org [Description]

Output: This will read the information belonging to a inserted audio CD from an internet database. Thus every song will get its correct name and artist displayed. The IP Address of the CD Database is set in the advancedsettings.xml.


Input: [Setting] Saved music folder [Description]

Output: This option defines the location on your hard drive that ripped tracks will be saved to.


Input: [Setting] Track naming template [Description]

Output: Controls the way that your ripped songs will be named. For a list of options that can be used, see Tags Available for Audio Files


Input: [Setting] Encoder [Description]

Output: This option defines which audio encoder to use when ripping. Note: Ubuntu users can download additional audio encoders via the Official Ubuntu PPA. See Adding audio encoders for Ubuntu for details. Kodi users for other OSes don't need to do anything, as all audio encoders are pre-installed in those builds.


Input: [Setting] -Quality [Description]

Output: This option defines in which quality you want to rip your files.


Input: [Setting] -Bitrate [Description]

Output: This option defines which bitrate to use for the specified audio encoder for audio compression.


Input: [Setting] -Compression level [Description]

Output: For FLAC define compression level, default 5


Input: [Setting] Eject CDs when ripping is complete [Description]

Output: You'll never guess what this does.


Input: [Setting] mail.host [Default] localhost [Description]

Output: SMTP host


Input: [Setting] mail.port [Default] 25 [Description]

Output: SMTP port


Input: [Setting] mail.username [Default] None [Description]

Output: SMTP username


Input: [Setting] mail.password [Default] None [Description]

Output: SMTP password


Input: [Setting] mail.tls [Default] False [Description]

Output: Use TLS


Input: [Setting] mail.ssl [Default] False [Description]

Output: Use SSL


Input: [Setting] mail.keyfile [Default] None [Description]

Output: SSL key file


Input: [Setting] mail.certfile [Default] None [Description]

Output: SSL certificate file


Input: [Setting] mail.queue_path [Default] None [Description]

Output: Location of maildir


Input: [Setting] mail.default_sender [Default] None [Description]

Output: Default from address


Input: [Setting] mail.debug [Default] 0 [Description]

Output: SMTP debug level


Input: [Setting] mail.sendmail_app [Default] /usr/sbin/sendmail [Description]

Output: Sendmail executable


Input: [Setting] mail.sendmail_template [Default] {sendmail_app} -t -i -f {sender} [Description]

Output: Template for sendmail execution


Input: [Description] Accepts a connection request queued for a listening socket. [Routine]

Output: accept


Input: [Description] Assigns a name (local address) to a socket. [Routine]

Output: bind


Input: [Description] Closes an existing socket and releases a socket descriptor. [Routine]

Output: closesocket


Input: [Description] Establishes connection between the endpoints on stream sockets. [Routine]

Output: connect


Input: [Description] Retrieves host address corresponding to a host name from a host database. [Routine]

Output: gethostbyname


Input: [Description] Retrieves the address of the peer to which a socket is connected. [Routine]

Output: getpeername


Input: [Description] Retrieves the local address of the socket. [Routine]

Output: getsockname


Input: [Description] Sets or retrieves some of the operating parameters on a socket. [Routine]

Output: ioctlsocket


Input: [Description] Sets the socket in a listen mode. [Routine]

Output: listen


Input: [Description] Receives incoming data that has been queued for a socket. [Routine]

Output: recv


Input: [Description] Receives incoming data on a datagram socket. [Routine]

Output: recvfrom


Input: [Description] Sends outgoing data on a socket. [Routine]

Output: send


Input: [Description] Sends outgoing data on a datagram socket to destination address. [Routine]

Output: sendto


Input: [Description] Creates a communication socket. [Routine]

Output: socket


Input: [Attribute] org.osgi.framework.system.packages [Comment]

Output: Comma-separated list of additional packages provided by the system and used to resolve package imports. This can be, e.g., javax.* packages.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.basedir [Default] . [Comment]

Output: All paths that are not explicitly defined are considered to be relative to the basedir.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.jars [Default] = basedir [Comment]

Output: The path where the bundle JARs can be found.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.storage [Default] basedir/storage [Comment]

Output: The path of the storage location. Can be used to allocate the framework's private storage on a different medium, for instance if Concierge is executed from a read-only medium.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.classloader.buffersize [Default] 2048 = 2048 Bytes [Comment]

Output: The buffer size for class loader I/O operations. Generally, it is a tradeoff of how many data can be read at once and how much time it takes to allocate the buffer memory. Experiments have shown that the size of 2k is the minimum on many devices. But this can depend on the average size of your bundles, the hardware architecture, disk block size, etc.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.log.enabled [Default] false = disabled [Comment]

Output: Enable the internal LogService of the Concierge framework. This allows the framework to write debug messages to the log. This is particularly useful for headless devices don't support System.out. Simply add a small LogReader that writes all log messages to a disk.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.log.buffersize [Default] 10 = ten entries. [Comment]

Output: Number of log entries that are buffered.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.log.level [Default] 1 = LOG_ERROR [Comment]

Output: The log level. Can be 0 = NONE, 1 = LOG_ERROR, 2 = LOG_WARNING, 3 = LOG_INFO or 4 = LOG_DEBUG. The larger level includes all smaller levels.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.debug.bundles [Default] false = disabled [Comment]

Output: Generate debug messages for bundle operations. Requires the log service to be enabled.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.debug.packages [Default] false = disabled [Comment]

Output: Generate debug messages for package operations. Requires the log service to be enabled.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.debug.services [Default] false = disabled [Comment]

Output: Generate debug messages for service operations. Requires the log service to be enabled.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.debug.classloading [Default] false = disabled [Comment]

Output: Generate debug messages for class loading operations. Requires the log service to be enabled.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.debug [Default] false = disabled [Comment]

Output: Generate full debug output. This is equivalent to ch.ethz.iks.concierge.log.enabled=true, ch.ethz.iks.concierge.log.level=4, ch.ethz.iks.concierge.debug.bundles=true, ch.ethz.iks.concierge.debug.packages=true, ch.ethz.iks.concierge.debug.services=true, and ch.ethz.iks.concierge.debug.classloading=true.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.strictStartup [Default] false = disabled [Comment]

Output: Strict startup means, Concierge terminates if one of the initially started bundle fails to install or if a warning occurs.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.decompressEmbedded [Default] true = enabled [Comment]

Output: Tells Concierge to decompress bundles containing embedded JARs. This can give a remarkable speedup if significant parts of the bundles' code reside inside of embedded JARs. For devices with highly constrained resources, this should be disabled.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Attribute] ch.ethz.iks.concierge.security.enabled [Default] false = disabled [Comment]

Output: Enable OSGi security. Please note, that the security part is not yet 100% complete and not entirely tested. So use with care. Also note, that this property has no effect unless you also specify a Java SecurityManager for your VM.

Maven - Concierge OSGi - An optimized OSGi R3 implementation for mobile and embedded systems - Startup Properties


Input: [Functional Area] Account Details [Priority] High [Size] Medium [Requirement]

Output: User can add a Username


Input: [Priority] High [Size] Large [Requirement]

Output: User can set a Password


Input: [Priority] Medium [Size] Medium [Requirement]

Output: User can set Address Details


Input: [Priority] Low [Size] Small [Requirement]

Output: User can add a Nickname


Input: [Functional Area] Add Payment Methods [Priority] High [Size] Large [Requirement]

Output: User can add a Credit Card payment method


Input: [Priority] Medium [Size] Large [Requirement]

Output: User can add an e-Wallet payment method


Input: [Functional Area] Post Account Creation [Priority] High [Size] Small [Requirement]

Output: User is logged in after creating an Account


Input: [Return Code] 200 [Explanation]

Output: Notification has been accepted and passed on to client (via either direct connection or Proprietary Ping mechanism). This does not guarantee that the notification has been successfully delivered to the app, but does reflect a higher percentage chance of it happening.)


Input: [Return Code] 202 [Explanation]

Output: Notification has been Accepted for delivery, but client is currently unavailable. The notification will be retained for when the client is available again, or the notification expires.


Input: [Return Code] 400 [Explanation]

Output: The version value is incorrect or improperly formatted (e.g. "version=banana")


Input: [Return Code] 403 [Explanation]

Output: Please be sure to use the PUT method when sending the Notification


Input: [Return Code] 404 [Explanation]

Output: The endpoint is not valid and should not be retried.


Input: [Return Code] 413 [Explanation]

Output: The data portion of the request is too large. (See reply text for maximum length.)


Input: [Tool] Sandbox From Scratch [Type] Create TIN [Notes]

Output: Creates a flat, rectangular shaped, TIN or sandbox that can be modified by other sandbox tools.

Modeling terrain and organic shapes | SketchUp Knowledge Base


Input: [Tool] Sandbox From Contours [Type] Create TIN [Notes]

Output: Creates TIN or a sandbox from contour lines at various elevations.

Modeling terrain and organic shapes | SketchUp Knowledge Base


Input: [Tool] Smoove [Type] Large Modifications [Notes]

Output: Allows you sculpt or make large modifications to a TIN by moving groupings of vertices to create hills, berms, or other features.

Modeling terrain and organic shapes | SketchUp Knowledge Base


Input: [Tool] Stamp [Type] Large Modifications [Notes]

Output: Allows you to sculpt or make large modifications to a TIN by stamping footprints into the TIN, such as the footprint of a building.

Modeling terrain and organic shapes | SketchUp Knowledge Base


Input: [Tool] Drape [Type] Large Modifications [Notes]

Output: Allows you to drape the outlines of roads, paths and buildings, drawn on a flat plane, onto a TIN.

Modeling terrain and organic shapes | SketchUp Knowledge Base


Input: [Tool] Add Detail [Type] Small, Detailed, Modifications [Notes]

Output: Allows you to sculpt or make small, detailed, modifications to the a TIN by adding additional triangles to a TIN.

Modeling terrain and organic shapes | SketchUp Knowledge Base


Input: [Tool] Flip Edge [Type] Small, Detailed, Modifications [Notes]

Output: Allows you to sculpt or make small, detailed, modifications to the TIN by adjusting the triangulation of a TIN.

Modeling terrain and organic shapes | SketchUp Knowledge Base


Input: [Tag] trail_visibility=excellent [Requirements] None, orientation unproblematic, no map required [Trail]

Output: Unambiguous path or markers everywhere

Key:trail_visibility - OpenStreetMap Wiki


Input: [Tag] trail_visibility=good [Requirements] Basic sense of direction, map recommended [Trail]

Output: Next marker always visible, but sometimes has to be searched for.

Key:trail_visibility - OpenStreetMap Wiki


Input: [Tag] trail_visibility=intermediate [Requirements] Good sense of direction, map required [Trail]

Output: Track mostly visible

Key:trail_visibility - OpenStreetMap Wiki


Input: [Tag] trail_visibility=bad [Requirements] Basic skills in orientation [Trail]

Output: Path sometimes invisible, route partly pathless

Key:trail_visibility - OpenStreetMap Wiki


Input: [Tag] trail_visibility=horrible [Requirements] Advanced orientational skills [Trail]

Output: Often pathless

Key:trail_visibility - OpenStreetMap Wiki


Input: [Tag] trail_visibility=no [Requirements] Excellent orientational skills [Trail]

Output: Mostly pathless

Key:trail_visibility - OpenStreetMap Wiki


Input: [Type] log4net.Appender.AdoNetAppender [Description]

Output: Writes logging events to a database using either prepared statements or stored procedures.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.AnsiColorTerminalAppender [Description]

Output: Writes color highlighted logging events to a an ANSI terminal window.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.AspNetTraceAppender [Description]

Output: Writes logging events to the ASP trace context. These can then be rendered at the end of the ASP page or on the ASP trace page.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.BufferingForwardingAppender [Description]

Output: Buffers logging events before forwarding them to child appenders.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.ColoredConsoleAppender [Description]

Output: Writes logging events to the application's Console. The events may go to either the standard our stream or the standard error stream. The events may have configurable text and background colors defined for each level.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.ConsoleAppender [Description]

Output: Writes logging events to the application's Console. The events may go to either the standard our stream or the standard error stream.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.DebugAppender [Description]

Output: Writes logging events to the .NET system.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.EventLogAppender [Description]

Output: Writes logging events to the Windows Event Log.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.FileAppender [Description]

Output: Writes logging events to a file in the file system.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.ForwardingAppender [Description]

Output: Forwards logging events to child appenders.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.LocalSyslogAppender [Description]

Output: Writes logging events to the local syslog service (UNIX only).

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.MemoryAppender [Description]

Output: Stores logging events in an in memory buffer.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.NetSendAppender [Description]

Output: Writes logging events to the Windows Messenger service. These messages are displayed in a dialog on a users terminal.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.OutputDebugStringAppender [Description]

Output: Writes logging events to the debugger. If the application has no debugger, the system debugger displays the string. If the application has no debugger and the system debugger is not active, the message is ignored.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.RemoteSyslogAppender [Description]

Output: Writes logging events to a remote syslog service using UDP networking.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.RemotingAppender [Description]

Output: Writes logging events to a remoting sink using .NET remoting.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.RollingFileAppender [Description]

Output: Writes logging events to a file in the file system. The RollingFileAppender can be configured to log to multiple files based upon date or file size constraints.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.SmtpAppender [Description]

Output: Sends logging events to an email address.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.SmtpPickupDirAppender [Description]

Output: Writes SMTP messages as files into a pickup directory. These files can then be read and sent by an SMTP agent such as the IIS SMTP agent.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.TelnetAppender [Description]

Output: Clients connect via Telnet to receive logging events.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.TraceAppender [Description]

Output: Writes logging events to the .NET trace system.

Apache log4net – Apache log4net Manual: Introduction


Input: [Type] log4net.Appender.UdpAppender [Description]

Output: Sends logging events as connectionless UDP datagrams to a remote host or a multicast group using a UdpClient.

Apache log4net – Apache log4net Manual: Introduction


Input: [Method] BufferedImage getResourceAsImage( String name ) [Description]

Output: returns an image (.gif, .jpg, .png) stored in the app's chrome

XulManager API Quick Reference: Luxor XML User Interface Language (XUL) Toolkit


Input: [Method] ImageIcon getResourceAsImageIcon( String name ) [Description]

Output: returns an icon stored in the app's chrome

XulManager API Quick Reference: Luxor XML User Interface Language (XUL) Toolkit


Input: [Method] String getResourceAsString( String name ) [Description]

Output: returns a text file stored in the app's chrome as a String

XulManager API Quick Reference: Luxor XML User Interface Language (XUL) Toolkit


Input: [Method] Properties getResourceAsProperties( String name ) [Description]

Output: returns a properties file stored in the app's chrome as a property table

XulManager API Quick Reference: Luxor XML User Interface Language (XUL) Toolkit


Input: [Method] org.jdom.Document getResourceAsXmlDocument( String name ) [Description]

Output: returns an XML document stored in the app's chrome as a parsed JDOM document

XulManager API Quick Reference: Luxor XML User Interface Language (XUL) Toolkit


Input: [Method] InputStream getResourceAsStream( String name ) [Description]

Output: returns a reference to the resources's InputStream

XulManager API Quick Reference: Luxor XML User Interface Language (XUL) Toolkit


Input: [Method] URL getResourceAsUrl( String name ) [Description]

Output: returns the resources's URL stored in the app's chrome

XulManager API Quick Reference: Luxor XML User Interface Language (XUL) Toolkit


Input: [Layout Manager] TreeLayoutAlgorithm [Description]

Output: Graph is displayed in the form of a vertical tree


Input: [Layout Manager] HorizontalTreeLayoutAlgorithm [Description]

Output: Similar to TreeLayoutAlgorithm but layout is horizontal


Input: [Layout Manager] RadialLayoutAlgorithm [Description]

Output: Root is in the center, the others nodes are placed around this node


Input: [Layout Manager] SpringLayoutAlgorithm [Description]

Output: Layout the graph so that all connections should have approx. the same length and that the edges overlap minimal


Input: [Layout Manager] HorizontalShift [Description]

Output: Moves overlapping nodes to the right


Input: [Layout Manager] CompositeLayoutAlgorithm [Description]

Output: Combines other layout algorithms, for example HorizontalShift can be the second layout algorithm to move nodes which were still overlapping if another algorithm is used


Input: [Key] ids[] [Required] optional [Description]

Output: The image ids that you want to be included in the album.


Input: [Key] title [Required] optional [Description]

Output: The title of the album


Input: [Key] description [Required] optional [Description]

Output: The description of the album


Input: [Key] privacy [Required] optional [Description]

Output: Sets the privacy level of the album. Values are : public | hidden | secret. Defaults to user's privacy settings for logged in users.


Input: [Key] layout [Required] optional [Description]

Output: Sets the layout to display the album. Values are : blog | grid | horizontal | vertical


Input: [Key] cover [Required] optional [Description]

Output: The ID of an image that you want to be the cover of the album


Input: [Updated system variables] ATTDIA [How changed] Default value changed from 0 (off) to 1 (on). [Description]

Output: Controls whether the INSERT command uses a dialog box for attribute value entry.

AutoCAD 2014 News, Features, Resources, Commands, Tips&Tricks


Input: [Updated system variables] LATITUDE [How changed] Now linked to the Latitude setting in the Geographic Location dialog box. [Description]

Output: Specifies the latitude of the geographic marker.

AutoCAD 2014 News, Features, Resources, Commands, Tips&Tricks


Input: [Updated system variables] LONGITUDE [How changed] Now linked to the Latitude setting in the Geographic Location dialog box. [Description]

Output: Specifies the longitude of the geographic marker.

AutoCAD 2014 News, Features, Resources, Commands, Tips&Tricks


Input: [Updated system variables] NORTHDIRECTION [How changed] Now also available in AutoCAD LT. [Description]

Output: Specifies the angle between the Y axis of WCS and the grid north.

AutoCAD 2014 News, Features, Resources, Commands, Tips&Tricks


Input: [Updated system variables] ONLINESYNCTIME [How changed] Default value changed from 5 to 300 minutes. [Description]

Output: Controls the time interval for synchronizing current customization settings with your Autodesk account.

AutoCAD 2014 News, Features, Resources, Commands, Tips&Tricks


Input: [Updated system variables] SNAPGRIDLEGACY [How changed] Now also available in AutoCAD LT. [Description]

Output: Controls whether the cursor snaps to the snap grid only when an operation is in progress.

AutoCAD 2014 News, Features, Resources, Commands, Tips&Tricks


Input: [Tool] Rectangle Selection Tool [Description]

Output: Selects an area in the shape of a rectangle. Simply click and drag to create a rectangular selection. The selection is made once you release the mouse.


Input: [Tool] Ellipse Selection Tool [Description]

Output: Selects an area in the shape of an ellipse (a circular shape). Simply click and drag to create an elliptical selection. The selection is made once you release the mouse.


Input: [Tool] Lasso Selection Tool [Description]

Output: Allows you to draw a selection free-hand with your mouse or other pointer. When you release the mouse button, the selection is closed by connecting the current pointer location to the start location with a straight line. You can go outside the edge of the image display and come back in if you want to.


Input: [Tool] Fuzzy Select Tool (Magic Wand) [Description]

Output: Enables you to make a selection, based on contiguous areas of a similar color range. The color range is determined by the point at which you click on and the value of the Threshold (within the Tool Options dialog).


Input: [Tool] Select By Color Tool [Description]

Output: Allows you to select areas of an image with a similar color range. The difference between this tool and the Fuzzy Select tool, is that the fuzzy select tool selects contiguous pixels - those that are next to, or close to, each other. The Select By Color Tool, on the other hand, selects all pixels within the color range, regardless of their location on the image.


Input: [Tool] Intelligent Sissors [Description]

Output: This tool is useful when you are trying to select a region defined by strong color-changes at the edges. To use the Intelligent Scissors, you click to create a set of "control nodes", also referred to as anchors or control points, at the edges of the region you are trying to select. The tool produces a continuous curve passing through these control nodes, following any high-contrast edges it can find. Note that this tool doesn't always produce a nice, smooth path. Many experienced GIMP users tend to use the Path tool instead.


Input: [Tool] Path Tool [Description]

Output: Technically, this tool is not a selection tool, however it creates paths - which can be turned into selections. This tool allows you to draw around the edge of any object on your image. More importantly, it provides you much more control than the other selection tools when working with complex shapes. Similar to the Intelligent Sissors, the Path tool results in control points that you can move around as required.


Input: [Tool] Foreground Select [Description]

Output: The Foreground Select tool was released in GIMP version 2.4. Using this tool is done in two steps. First, you make selection which contains the entire object. Then you paint over the selected area with a brush, not crossing object’s border. Release mouse button when you’re done and look to see if there are dark blue spots on your objects. If there are some, paint over them with a brush again and release to refine the selection. When there are no more blue areas inside the object, press Enter and your object will be selected.


Input: [Key] ID [Example] Test.Sample [Description]

Output: The name of the directive, in the form Namespace.Directive (implicitly the first line)

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] TYPE [Example] string/null [Description]

Output: The type of variable this directive accepts. See below for details. You can also add /null to the end of any basic type to allow null values too.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] DEFAULT [Example] NULL [Description]

Output: A parseable PHP expression of the default value.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] DESCRIPTION [Example] This is a... [Description]

Output: An HTML description of what this directive does.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] VERSION [Example] 3.1.0 [Description]

Output: Recommended. The version of HTML Purifier this directive was added. Directives that have been around since 1.0.0 don't have this, but any new ones should.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] ALIASES [Example] Test.Example [Description]

Output: Optional. A comma separated list of aliases for this directive. This is most useful for backwards compatibility and should not be used otherwise.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] ALLOWED [Example] 'foo', 'bar' [Description]

Output: Optional. Set of allowed value for a directive, a comma separated list of parseable PHP expressions. This is only allowed string, istring, text and itext TYPEs.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] VALUE-ALIASES [Example] 'baz' => 'bar' [Description]

Output: Optional. Mapping of one value to another, and should be a comma separated list of keypair duples. This is only allowed string, istring, text and itext TYPEs.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] DEPRECATED-VERSION [Example] 3.1.0 [Description]

Output: Not shown. Indicates that the directive was deprecated this version.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] DEPRECATED-USE [Example] Test.NewDirective [Description]

Output: Not shown. Indicates what new directive should be used instead. Note that the directives will functionally be different, although they should offer the same functionality. If they are identical, use an alias instead.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [Key] EXTERNAL [Example] CSSTidy [Description]

Output: Not shown. Indicates if there is an external library the user will need to download and install to use this configuration directive. As of right now, this is merely a Google-able name; future versions may also provide links and instructions.

htmlpurifier-4.6.0.tar.gz: .../dev-config-schema.html | Fossies


Input: [SourceType] Web [Sample Query Parameter] Sushi [Description]

Output: Searches for web content


Input: [SourceType] Image [Sample Query Parameter] Sushi [Description]

Output: Searches for images on the web


Input: [SourceType] News [Sample Query Parameter] Sushi [Description]

Output: Searches news stories


Input: [SourceType] Spell [Sample Query Parameter] Coffee [Description]

Output: Searches Encarta dictionary for spelling suggestions


Input: [SourceType] Phonebook [Sample Query Parameter] sushi in los angeles [Description]

Output: Searches phonebook entries


Input: [SourceType] RelatedSearch [Sample Query Parameter] {inari sushi; sushi restaurant; California roll} [Description]

Output: Returns the query strings most similar to yours


Input: [SourceType] Video [Sample Query Parameter] Sushi [Description]

Output: Searches for video on the web


Input: [Function] defined(VARIABLE) [Description]

Output: returns true if VARIABLE has a real value and false if the variable has not yet been assigned a value. This is not limited to arrays, any data type can be checked. Also see the exists function for information about associative array keys.

Table 5.2-Array Functions


Input: [Function] delete(KEY) [Description]

Output: Removes the key-value pair from the given associative array. If you delete a value from the %ENV array the environment of the current process is changed, not that of the parent.

Table 5.2-Array Functions


Input: [Function] each(ASSOC_ARRAY) [Description]

Output: Returns a two-element list that contains a key and value pair from the given associative array. The function is mainly used so that you can iterate over the associate array elements. A null list is returned when the last element has been read.

Table 5.2-Array Functions


Input: [Function] exists(KEY) [Description]

Output: Returns true if the KEY is part of the specified associative array. For instance, exists($array{"Orange"}) returns true if the %array associative array has a key with the value of "Orange."

Table 5.2-Array Functions


Input: [Function] join(STRING, ARRAY) [Description]

Output: Returns a string that consists of all of the elements of ARRAY joined together by STRING. For instance, join(">>", ("AA", "BB", "CC")) returns "AA>>BB>>CC".

Table 5.2-Array Functions


Input: [Function] keys(ASSOC_ARRAY) [Description]

Output: Returns a list that holds all of the keys in a given associative array. The list is not in any particular order.

Table 5.2-Array Functions


Input: [Function] map(EXPRESSION, ARRAY) [Description]

Output: Evaluates EXPRESSION for every element of ARRAY. The special variable $_ is assigned each element of ARRAY immediately before EXPRESSION is evaluated.

Table 5.2-Array Functions


Input: [Function] pack(STRING, ARRAY) [Description]

Output: Creates a binary structure, using STRING as a guide, of the elements of ARRAY. You can look in Chapter 8, "References," for more information.

Table 5.2-Array Functions


Input: [Function] pop(ARRAY) [Description]

Output: Returns the last value of an array. It also reduces the size of the array by one.

Table 5.2-Array Functions


Input: [Function] push(ARRAY1, ARRAY2) [Description]

Output: Appends the contents of ARRAY2 to ARRAY1. This increases the size of ARRAY1 as needed.

Table 5.2-Array Functions


Input: [Function] reverse(ARRAY) [Description]

Output: Reverses the elements of a given array when used in an array context. When used in a scalar context, the array is converted to a string, and the string is reversed.

Table 5.2-Array Functions


Input: [Function] scalar(ARRAY) [Description]

Output: Evaluates the array in a scalar context and returns the number of elements in the array.

Table 5.2-Array Functions


Input: [Function] shift(ARRAY) [Description]

Output: Returns the first value of an array. It also reduces the size of the array by one.

Table 5.2-Array Functions


Input: [Function] sort(ARRAY) [Description]

Output: Returns a list containing the elements of ARRAY in sorted order. See Chapter 8, "References," for more information.

Table 5.2-Array Functions


Input: [Function] splice(ARRAY1, OFFSET, LENGTH, ARRAY2) [Description]

Output: Replaces elements of ARRAY1 with elements in ARRAY2. It returns a list holding any elements that were removed. Remember that the $[ variable may change the base array subscript when determining the OFFSET value.

Table 5.2-Array Functions


Input: [Function] split(PATTERN, STRING, LIMIT) [Description]

Output: Breaks up a string based on some delimiter. In an array context, it returns a list of the things that were found. In a scalar context, it returns the number of things found.

Table 5.2-Array Functions


Input: [Function] undef(VARIABLE) [Description]

Output: Slways returns the undefined value. In addition, it undefines VARIABLE which must be a scalar, an entire array or a subroutine name.

Table 5.2-Array Functions


Input: [Function] unpack(STRING, ARRAY) [Description]

Output: Does the opposite of pack().

Table 5.2-Array Functions


Input: [Function] unshift(ARRAY1, ARRAY2) [Description]

Output: Adds the elements of ARRAY2 to the front of ARRAY1. Note that the added elements retain their original order. The size of the new ARRAY1 is returned.

Table 5.2-Array Functions


Input: [Function] values(ASSOC_ARRAY) [Description]

Output: Returns a list that holds all of the values in a given associative array. The list is not in any particular order.

Table 5.2-Array Functions


Input: [Description] This is the name of the template to use for this comment. Comment templates are defined in a TWiki template - see Customisation, below. If this attribute is not defined, the type is whatever is defined by COMMENTPLUGIN_DEFAULT_TYPE, either in this topic or in your WebPreferences. [Default] below [Name]

Output: type


Input: [Description] Default text to put into the textarea of the prompt. [Name]

Output: default


Input: [Description] Name of the topic to add the comment to [Default] the current topic [Name]

Output: target


Input: [Description] Regular expression specifying the comment location in the target topic. Read carefully the CommentPlugin documentation! [Name]

Output: location


Input: [Description] For compatibility with older versions only, synonymous with type [Name]

Output: mode


Input: [Description] Set to "on" to disable change notification for target topics [Default] off [Name]

Output: nonotify


Input: [Description] Set to "on" to disable the automatic form that encloses your comment block - remember to insert tags yourself! See CommentPluginExamples#noform for an example. [Default] off [Name]

Output: noform


Input: [Description] Set to "on" to disable insertion of the posted text into the topic. [Default] off [Name]

Output: nopost


Input: [Description] Set to "on" to remove the comment prompt after the first time it is clicked. [Default] off [Name]

Output: remove


Input: [Description] Button label text [Default] Add comment [Name]

Output: button


Input: [Variable] __author__ [Tag]

Output: @author


Input: [Variable] __authors__ [Tag]

Output: @authors


Input: [Variable] __contact__ [Tag]

Output: @contact


Input: [Variable] __copyright__ [Tag]

Output: @copyright


Input: [Variable] __license__ [Tag]

Output: @license


Input: [Variable] __deprecated__ [Tag]

Output: @deprecated


Input: [Variable] __date__ [Tag]

Output: @date


Input: [Variable] __version__ [Tag]

Output: @version


Input: [Type] name [Notes] Single value, single instance. [Description]

Output: The name of this person, or none if the record corresponds to an organization.

Insidious Big Brother Database User Manual: 1. BBDB


Input: [Type] company [Notes] Single value, single instance. [Description]

Output: The name of this person's organization, or none.

Insidious Big Brother Database User Manual: 1. BBDB


Input: [Type] AKA [Notes] Multiple values through commas. [Description]

Output: A list of other names for this person.

Insidious Big Brother Database User Manual: 1. BBDB


Input: [Type] net [Notes] Multiple values through commas. [Description]

Output: A list of this person's network addresses.

Insidious Big Brother Database User Manual: 1. BBDB


Input: [Type] address [Notes] Multiple values through multiple occurences. [Description]

Output: A list of postal (physical) addresses for this person.

Insidious Big Brother Database User Manual: 1. BBDB


Input: [Type] phone [Notes] Multiple values through multiple occurences. [Description]

Output: A list of telephone numbers for this person.

Insidious Big Brother Database User Manual: 1. BBDB


Input: [Type] notes [Notes] Multiple values through multiple occurences. [Description]

Output: Random commentary.

Insidious Big Brother Database User Manual: 1. BBDB


Input: [Parameter] Darkroom cleanliness [Individual Responsible] mammographer [Frequency]

Output: daily

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Processor performance [Individual Responsible] mammographer [Frequency]

Output: daily

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Screen cleanliness [Individual Responsible] mammographer [Frequency]

Output: weekly

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] View boxes and viewing conditions [Individual Responsible] mammographer [Frequency]

Output: weekly

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Image quality (phantom images) [Individual Responsible] mammographer [Frequency]

Output: monthly

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Repeat analysis [Individual Responsible] mammographer [Frequency]

Output: quarterly

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Analysis of fixer retention in film [Individual Responsible] mammographer [Frequency]

Output: quarterly

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Darkroom fog [Individual Responsible] mammographer [Frequency]

Output: semiannually

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Screen-film contact [Individual Responsible] mammographer [Frequency]

Output: semiannually

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Compression [Individual Responsible] mammographer [Frequency]

Output: semiannually

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] AEC density control function [Individual Responsible] diagnostic imaging physicist [Frequency]

Output: annually

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Star pattern focal spot size test [Individual Responsible] diagnostic imaging physicist [Frequency]

Output: annually

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Uniformity of screen speed [Individual Responsible] diagnostic imaging physicist [Frequency]

Output: annually

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Parameter] Assembly physical evaluation [Individual Responsible] diagnostic imaging physicist [Frequency]

Output: annually

ISDH: 410 IAC 5-6.1: X-rays in the Healing Arts


Input: [Option] animation [Type Value] boolean [Default Value] true [Description]

Output: It applies fade transition to the popover.


Input: [Option] html [Type Value] boolean [Default Value] false [Description]

Output: It inserts html elements to the popover.


Input: [Option] placement [Type Value] string/function [Default Value] right [Description]

Output: It sets the position of the popover. If it does not contain any position, then by default it displays to right position.


Input: [Option] selector [Type Value] string [Default Value] false [Description]

Output: Delegate popover objects to specified targets.


Input: [Option] title [Type Value] string/function [Default Value] false [Description]

Output: It sets default value if title attributes is not present.


Input: [Option] trigger [Type Value] string [Default Value] ’click’ [Description]

Output: It defines how tooltip will be triggered such as click, hover, focus and manual.


Input: [Option] delay [Type Value] number/object [Default Value] 0 [Description]

Output: It inserts delay before popover is showed or hidden in ms which does not apply to manual trigger type.


Input: [Option] container [Type Value] string/false [Default Value] false [Description]

Output: It appends popover to a specific element.


Input: [Method and Description] checkNotClosed() Checks if state of this ClosureMonitor is set to closed and if so, throws the causing Exception. [Modifier and Type]

Output: void

ClosureMonitor (Apache Directory LDAP API 1.0.0-M30 API)

Methods


Input: [Method and Description] close() Sets monitor state to closed, and sets the cause to a CursorClosedException without an error message string. [Modifier and Type]

Output: void

ClosureMonitor (Apache Directory LDAP API 1.0.0-M30 API)

Methods


Input: [Method and Description] close(Exception cause) Sets monitor state to closed, and sets the cause to a specific Exception. [Modifier and Type]

Output: void

ClosureMonitor (Apache Directory LDAP API 1.0.0-M30 API)

Methods


Input: [Method and Description] close(String cause) Sets monitor state to closed, and sets the cause to a CursorClosedException with a specific error message string. [Modifier and Type]

Output: void

ClosureMonitor (Apache Directory LDAP API 1.0.0-M30 API)

Methods


Input: [Method and Description] getCause() Gets the cause of the closure. [Modifier and Type]

Output: Exception

ClosureMonitor (Apache Directory LDAP API 1.0.0-M30 API)

Methods


Input: [Method and Description] isClosed() Gets whether the state of this ClosureMonitor is set to closed. [Modifier and Type]

Output: boolean

ClosureMonitor (Apache Directory LDAP API 1.0.0-M30 API)

Methods


Input: [Name] COPY_COBOL [Optional] no [Description]

Output: It's name of the file containing the copy cobol. The name is relative to the service unit root.


Input: [Name] CODE_PAGE [Optional] no [Description]

Output: It's the codepage used by the host. This is important for correct string representation.


Input: [Name] SERVICE_NAME [Optional] no [Description]

Output: It's the name of the service this endpoint represents. It must be a valid java class name.


Input: [Name] OPERATION_NAME [Optional] yes [Default] execute [Description]

Output: It's the name of unic operation this service have. It must be a valid java method name.


Input: [Name] SERVICE_PACKAGE_NAME [Optional] no [Description]

Output: It's the name of the package of the dynamically generated classes for this service. It must be a valid java package name. It will also be used (reversed) to generate the webservice namespace. So if the package is aaa.bbb.ccc the webservice namespace will be http://ccc.bbb.aaa.


Input: [Name] INTERFACE_NAME [Optional] yes [Default] ${SERVICE_NAME}Interface [Description]

Output: It's the name of the dynamically generated interface for this service. It must be a valida java class name.


Input: [Name] INPUT_BEAN_NAME [Optional] yes [Default] ${SERVICE_NAME}InputBean [Description]

Output: It's the name of the dynamically generated java bean that will be used as unic input parameter for the operation represented by this service. It must be a valid java class name.


Input: [Name] OUPUT_BEAN_NAME [Optional] yes [Default] ${SERVICE_NAME}OutputBean [Description]

Output: It's the name of the dynamically generated java bean that will be used as return parameter for the operation represented by this service. It must be a valid java class name.


Input: [Name] USERNAME [Optional] no [Description]

Output: It's the username used for the connection to the CICS Transaction Gateway.


Input: [Name] PASSWORD [Optional] no [Description]

Output: It's the password used for the connection to the CICS Transaction Gateway.


Input: [Name] CONNECTION_TYPE [Optional] no [Description]

Output: The connection type. CICS and DUMMY are the possible values. With DUMMY an echo service is created. The service doesn't connect to host and ca be useful for testing purposes or for have a look at how a copy cobol would be rendered as wsdl. With DUMMY the following parameters became optional: JNDI_CONNECTION_NAME, PROGRAM_NAME, TRANSACTION_NAME, TPN, USERNAME, PASSWORD.


Input: [Name] JNDI_CONNECTION_NAME [Optional] no [Description]

Output: It's the JNDI name for the JCA resource to use with this service.


Input: [Name] PROGRAM_NAME [Optional] no [Description]

Output: It's the cobol program name to be called.


Input: [Name] TRANSACTION_NAME [Optional] no [Description]

Output: It's the transaction associated to the cobol program in the CICS server.


Input: [Name] TPN [Optional] yes [Default] false [Description]

Output: whether the transaction name or tpn name in the JCA CICS ECI interface must be setted, see the IBM JCA CICS ECI manual for more information on this parameter.


Input: [Hotkey] CapsLock Space [Function]

Output: Read the current line of text


Input: [Hotkey] CapsLock PageUp [Function]

Output: Read from top of screen to current position


Input: [Hotkey] CapsLock PageDown [Function]

Output: Read from current position to end of screen


Input: [Hotkey] PageUp/PageDown (no CapsLock) [Function]

Output: Previous/Next screen page


Input: [Hotkey] CapsLock ArrowUp [Function]

Output: Change reading position to one line up