Input: [character] © [entity name] © [entity number] © [description] copyright [why is this featured?]

Output: almost every website uses the copyright symbol

Entity Code - A Clear and Quick Reference to HTML Entities Codes


Input: [character] | [entity number] | [description] vertical bar [why is this featured?]

Output: the vertical bar symbol is used to separate menu items or navigation links

Entity Code - A Clear and Quick Reference to HTML Entities Codes


Input: [character] · [entity name] · [entity number] · [description] Medium List Dot [why is this featured?]

Output: similar to the vertical bar, the medium list dot is another option to separate menu items; personally i consider it more stylish

Entity Code - A Clear and Quick Reference to HTML Entities Codes


Input: [character] ↑ [entity name] ↑ [entity number] ↑ [description] up arrow [why is this featured?]

Output: the up arrow can be used in the "back to top" link in a web page

Entity Code - A Clear and Quick Reference to HTML Entities Codes


Input: [character] € [entity name] € [entity number] € [description] Euro Symbol [why is this featured?]

Output: we often find ourselves struggling to find the euro symbol on a keyboard

Entity Code - A Clear and Quick Reference to HTML Entities Codes


Input: [character] ² [entity name] ² [entity number] ² [description] Superscript 2 [why is this featured?]

Output: the superscript 2 is a very common symbol when dealing with numbers, such as; 1000²

Entity Code - A Clear and Quick Reference to HTML Entities Codes


Input: [character] ½ [entity name] ½ [entity number] ½ [description] Fraction ½ [why is this featured?]

Output: give me ½ ...

Entity Code - A Clear and Quick Reference to HTML Entities Codes


Input: [character] ♥ [entity name] ♥ [entity number] ♥ [description] heart [why is this featured?]

Output: i ♥ all this webmasterish stuff!

Entity Code - A Clear and Quick Reference to HTML Entities Codes


Input: [Driver Name] SQLite [Description] SQLite via PySQLite [Implementation Class]

Output: pytable.pysqlite.sqlitedriver.SQLiteDriver


Input: [Driver Name] MkSQL [Description] Metakit via MkSQL (unfinished) [Implementation Class]

Output: pytable.mk.mkdriver.MkDriver


Input: [Driver Name] PyPgSQL [Description] PostgreSQL via PyPgSQL [Implementation Class]

Output: pytable.pypgsql.pgdriver.PGDriver


Input: [Driver Name] PyGreSQL [Description] PostgreSQL via PyGreSQL [Implementation Class]

Output: pytable.pygresql.pgdriver.PGDriver


Input: [Driver Name] psycopg [Description] PostgreSQL via psycopg [Implementation Class]

Output: pytable.psycopg.psycodriver.PsycoDriver


Input: [Driver Name] MySQL [Description] MySQL via MySQLdb [Implementation Class]

Output: pytable.mysql.mydriver.MyDriver


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Unique identifier of the component in a namingContainer. [Name]

Output: id

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.Boolean) [Description] Boolean value to specify the rendering of the component, when set to false component will not be rendered. [Name]

Output: rendered

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to javax.faces.component.UIComponent) [Description] An el expression referring to a server side UIComponent instance in a backing bean. [Name]

Output: binding

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.Object) [Description] Label of the component. [Name]

Output: value

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to javax.faces.event.ActionListener) [Description] An actionlistener to process when command is executed. [Name]

Output: actionListener

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to javax.el.MethodExpression) [Description] A method expression or a string outcome to process when command is executed. [Name]

Output: action

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to boolean) [Description] Boolean value that determines the phaseId of the action event, when true actions are processed at "Apply Request Values", when false at "Invoke Application" phase. [Name]

Output: immediate

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Url to be navigated when menuitem is clicked. [Name]

Output: url

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Target type of url navigation. [Name]

Output: target

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Style of the menuitem label. [Name]

Output: style

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] StyleClass of the menuitem label. [Name]

Output: styleClass

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Javascript event handler for click event. [Name]

Output: onclick

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Client side id of the component(s) to be updated after async partial submit request. [Name]

Output: update

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Component id(s) to process partially instead of whole view. [Name]

Output: process

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Javascript handler to execute before ajax request is begins. [Name]

Output: onstart

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.Boolean) [Description] Disables or enables the menu item. [Name]

Output: disabled

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Javascript handler to execute when ajax request is completed. [Name]

Output: oncomplete

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Javascript handler to execute when ajax request fails. [Name]

Output: onerror

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Javascript handler to execute when ajax request succeeds. [Name]

Output: onsuccess

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.Boolean) [Description] Global ajax requests are listened by ajaxStatus component, setting global to false will not trigger ajaxStatus. [Name]

Output: global

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.Boolean) [Description] When set to true, ajax requests are not queued. [Name]

Output: async

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.Boolean) [Description] Specifies submit mode. [Name]

Output: ajax

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Path of the menuitem image. [Name]

Output: icon

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.Boolean) [Description] When enabled, only values related to partially processed components would be serialized for ajax instead of whole form. [Name]

Output: partialSubmit

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Title text of the menuitem. [Name]

Output: title

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Used to resolve a navigation case. [Name]

Output: outcome

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.Boolean) [Description] Whether to include page parameters in target URI. Default is false. [Name]

Output: includeViewParams

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Required] false [Type] javax.el.ValueExpression (must evaluate to java.lang.String) [Description] Identifier of the target page which should be scrolled to. [Name]

Output: fragment

menuitem (VDL Documentation Generator - Generated Documentation)

Attributes


Input: [Field] ZipCode [Description]

Output: 00000-99999 Five digit numeric ZIP Code of the area.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] UniqueKey [Description]

Output: A unique key number identifying this record for updates.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] ActionType [Description]

Output: A or D, meaning add or delete this record.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] RecordType [Description]

Output: A flag indicating which type of record this is. Ex: Firm, General Delivery, High Rise, PO Box, Rural Route, or Street.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] CarrierRouteID [Description]

Output: Carrier identification code or number for a given delivery route or PO box presentation.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] StreetPreDirAbbr [Description]

Output: The directional abbreviation that comes before an address: Ex: The N meaning North in "N 123 MAIN ST"

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] StreetName [Description]

Output: The official name of the street as assigned by a local governing authority for this record.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] StreetSuffixAbbr [Description]

Output: Code that is the standard USPS abbreviation for the trailing designator in a street address.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] StreetPostDirAbbr [Description]

Output: A geographic direction that follows the street name. Ex: The N meaning North in "123 MAIN ST N"

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] AddressPrimaryLowNumber [Description]

Output: The low number in a range of numeric or alphanumeric components to an address preceding the street name.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] AddressPrimaryHighNumber [Description]

Output: The high number in a range of numeric or alphanumeric components to an address preceding the street name.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] AddressPrimaryOddEven [Description]

Output: Code that identifies the side or sides of a street for which a given address range is applicable.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] BuildingFirmName [Description]

Output: The name of a company, building, apartment complex, shopping center, or other distinguishing secondary address information.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] AddressSecondaryAbbr [Description]

Output: Only Applicable to Record Types F and H.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] AddressSecondaryLowNumber [Description]

Output: The low-end secondary address component in a range of secondary addresses.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] AddressSecondaryHighNumber [Description]

Output: The high-end secondary address component in a range of secondary addresses.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] AddressSecondaryOddEven [Description]

Output: Code that identifies the side or sides of a street for which a given address range is applicable.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] Plus4Low [Description]

Output: ZIP Add-On Low Number in the range. Also known as the +4.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] Plus4High [Description]

Output: ZIP Add-On High Number in the range. Also known as the +4.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] BaseAlternateCode [Description]

Output: Code that specifies whether a record is a base (preferred) or alternate record.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] LACSStatus [Description]

Output: L = LACS Converted, Blank = Not Applicable

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] GovernmentBuilding [Description]

Output: This indicates what type of Government building this is if applicable.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] FinanceNumber [Description]

Output: A code assigned to Postal Service facilities (primarily post offices) to collect cost and statistical data and compile revenue and expense data.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] State [Description]

Output: A 2-character abbreviation for the name of a state, U.S. territory, or armed forces ZIP Code designation.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] CountyFIPSCode [Description]

Output: The 3-digit (FIPS) code assigned to counties in sequence within each state.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] CongressionalDistrict [Description]

Output: The 112th Congressional District this ZIP+4 record is assigned to.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] UrbanizationCityStateKey [Description]

Output: An index to the USPS City State file that provides the urbanization name for this delivery range.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] PreferredLastLineCityStateKey [Description]

Output: Match this field to our ZIP Code Database for City name, City alias, Area Code, TimeZone, and more.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] FromLatitude [Description]

Output: The north/south measurement indicating the beginning for this record.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] FromLongitude [Description]

Output: The east/west measurement indicating the beginning for this record.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] ToLatitude [Description]

Output: The north/south measurement indicating the beginning for this record.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] ToLongitude [Description]

Output: The east/west measurement indicating the beginning for this record.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] CensusTract [Description]

Output: Small, locally delineated statistical areas within selected counties, generally having stable boundaries and, when first established by local communities, designed to have relatively homogeneous demographic characteristics.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] CensusBlock [Description]

Output: Blocks are numbered uniquely within each census tract with a 4-character number that identifies the collection block used in the census and a character block suffix. This character block suffix is often blank.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [Field] TLID [Description]

Output: Tiger Line Identification (TLID) is a universal number associated with Census Bureau products.

ZIP Plus 4 Database (9 Digit ZIP Code Database)


Input: [File] sboxlib (27K) [Description]

Output: All of the files below


Input: [File] sboxread [Description]

Output: A reference sBOX reader which reads from a FILE *


Input: [File] sboxwrit [Description]

Output: A reference sBOX writer which manages a directory in memory and writes it out last.


Input: [File] sboxkit [Requires] sboxread, sboxwrit [Description]

Output: A utility toolkit layered over sboxread and sboxwrit


Input: [File] sboxlib [Requires] sboxread, sboxwrit, and sboxkit [Description]

Output: a combined header file which can be used if sboxlib is compiled into a library.


Input: [File] box [Requires] sboxlib [Description]

Output: Prints out the directory information from an sBOX file, creates a new file, adds an entry to an sBOX file using another file as the data value, renames an entry, or deletes an entry. For maximal instructive purposes, does not use sboxkit.


Input: [File] sboxcan [Requires] sboxread [Description]

Output: Reads in an sBOX and writes out an sBOX in canonical form.


Input: [File] sboxcat [Requires] sboxlib [Description]

Output: "Appends" two or more sBOX files while copying them.


Input: [File] sboxsort [Requires] sboxlib [Description]

Output: Sorts the names in an sBOX file while copying it.


Input: [File] sboxuniq [Requires] sboxlib [Description]

Output: Deletes non-uniquely-named entries from an sBOX file while copying it.


Input: [File] readme.txt (36K) [Description]

Output: Library documentation


Input: [product_locked] bad_or_missing_design_file

Output: Missing design file data or unknown file type.

Products and designs cannot be updated while they are locked - ie no incomplete orders.


Input: [product_locked] incompatible_material

Output: The material you have selected is not compatible with making methods available to the design file.

Products and designs cannot be updated while they are locked - ie no incomplete orders.


Input: [product_locked] wrong_network

Output: This material is not available to your network.

Products and designs cannot be updated while they are locked - ie no incomplete orders.


Input: [product_locked] unknown_material

Output: Could not find requested material. is it available to this Node's material catalog?

Products and designs cannot be updated while they are locked - ie no incomplete orders.


Input: [product_locked] must_have_one_design

Output: Product must have at least one design.

Products and designs cannot be updated while they are locked - ie no incomplete orders.


Input: [product_locked] product_ordered

Output: Cannot delete designs for a product that has orders.

Products and designs cannot be updated while they are locked - ie no incomplete orders.


Input: [No.] 1 [Fuction]

Output: Insert text, images and hyperlink Insert new text, images and hyperlink to a PDF file

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 2 [Fuction]

Output: Annotate and mark up PDF files Annotate a PDF file with sticky note and mark up a PDF file with highlighter, freehand drawing tools and all kinds of shapes

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 3 [Fuction]

Output: Insert, delete, crop, merge and rotate PDF Pages Insert, delete, crop, merge and rotate PDF pages easily

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 4 [Fuction]

Output: Modify and delete PDF text Modify and delete PDF text hassle freely

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 5 [Fuction]

Output: Edit and delete PDF images Crop and delete existing PDF images

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 6 [Fuction]

Output: Support editing large files No size limitations for PDF files imported for editing

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 7 [Fuction]

Output: Split a large PDF Split a large PDF into small ones

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 8 [Fuction]

Output: Add, edit and delete Watermark Add, edit and delete watermark on a PDF

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 9 [Fuction]

Output: Powerful Conversion Convert PDF to Word/Excel/ PPT/ EPUB/ HTML/Text

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [No.] 10 [Wondershare PDFelement] To use the OCR feature, users need to enable PDFelement OCR Plugin. [Fuction]

Output: Support OCR Edit and convert scanned PDF with OCR technology

Top 5 Free Online PDF Editor – Edit PDF Online for Free


Input: [Description] Sets the time when test results and feedback are shown to students: After Submission One-time View On Specific Date After Due Date After Availability and End Date After Attempts are Graded [Feedback Mode]

Output: When


Input: [Description] Shows the final score out of points possible to students. [Feedback Mode]

Output: Score


Input: [Description] Shows all answer options for certain question types, such as multiple choice. [Feedback Mode]

Output: All Answers


Input: [Description] Shows the correct answers. [Feedback Mode]

Output: Correct


Input: [Description] Shows all the student’s submitted answers. [Feedback Mode]

Output: Submitted


Input: [Description] Shows instructor generated feedback messages for each question. [Feedback Mode]

Output: Feedback


Input: [Description] Shows the questions the student answered incorrectly or partially incorrectly. [Feedback Mode]

Output: Show Incorrect Questions


Input: [0] Basic commands [Direct merge] git checkout master git merge branch git commit [Rebase] git checkout branch git rebase master while not done: git rebase --continue [Incremental merge]

Output: git checkout master git-imerge start [...] branch while not done: git commit [...] git-imerge continue git-imerge simplify [...] (This uses the git-imerge tool [1].)


Input: [0] Size of conflicts [Direct merge] All of the changes in master have to be combined with all of the changes in branch in one go. Various changes are mixed up together, even if they were originally committed separately, which can make the conflict large or even intractable. [Rebase] One step of a rebase requires one change from branch to be resolved with all of the changes from master. This is easier than doing a direct merge in one step, but still mixes up unrelated changes. [Incremental merge]

Output: At any step, only one change from master has to be combined with one change from branch. The commit messages and deltas from each of the two changes are available to help you understand the two changes.


Input: [0] Effort [Direct merge] The least amount of effort, if there are only a few simple conflicts. Effort increases highly nonlinearly in the size of the conflict. [Rebase] A bit more effort, if conflicts are simple and isolated. Conflicts tend to be smaller than for direct merge, but more numerous. If there are sequential overlapping conflicts, you might need to resolve similar conflicts multiple times. [Incremental merge]

Output: More processing power required at start of merge. Conflicts are resolved as lots of little conflicts, so the effort scales closer to linearly with the number of pairwise conflicts [2]. Benefits decrease if original changes were not committed in small, self-contained steps.


Input: [0] Interruptibility [Direct merge] After you start a direct merge, there is no way to record partial results. You are forced to either complete the whole merge and then commit it, or abandon the whole merge using git merge --abort. Progress on a direct merge is all-or-nothing. [Rebase] Once a rebase is started, it is awkward to interrupt it [3]. It is true that intermediate results are committed, but because the rebase discards the connection between original commits and rebased commits, you have to do the bookkeeping yourself. [Incremental merge]

Output: Each of the pairwise merges is resolved and committed separately. After each pairwise merge is committed, you can switch branches, do something else for a while, then return later to the incremental merge. Progress on an incremental merge can be locked in in small increments.


Input: [0] Testability, fixability [Direct merge] The results of a direct merge cannot be tested until the whole merge is done. If you mess up one part of the merge, there is no easy way to revert only that part. [Rebase] The individual rebased commits can be tested. But if there is a failure, it is nontrivial to figure out which of the changes on master interacted badly with the rebased commit. [Incremental merge]

Output: Each pairwise merge can be tested individually. If one fails testing, it can be discarded and redone without having to discard earlier pairwise merges. If a failure is discovered after the incremental merge is done, it is possible to use git bisect to find out exactly which of the pairwise merges was faulty.


Input: [0] Collaboration [Direct merge] Since an in-progress direct merge is not savable, the only way to get help from a colleague on a direct merge is to call the colleague to your computer and have him/her work in your working copy. [Rebase] It is strongly recommended that a branch that has been published not be rebased. Thus rebasing is usually applied only to local work done by a single developer. It is awkward to share the work of rebasing a branch [3]. [Incremental merge]

Output: Each pairwise merge commit is a normal commit that can be exchanged with other colleagues via push/fetch/etc. Each pairwise conflict can be resolved by the person most familiar with that part of the code. In fact, if you plan to retain the whole incremental merge in your repository history, then no history rewriting is necessary at all, and there is no problem merging a published branch, or publishing the intermediate merge commits as you go.


Input: [0] Recommendations [Direct merge] In a merge-based workflow, use direct merge for simple merges. If a difficult conflict arises, switch to incremental merge and then simplify the results into a simple merge. [Rebase] In a rebase-based workflow with unpublished local changes, use rebase to update your work onto upstream changes if you only expect trivial conflicts. If you expect (or, midway through the rebase, encounter) nontrivial conflicts, switch to incremental merge and then simplify the results into a rebase. [Incremental merge]

Output: Use incremental merge when: a simple merge or rebase is desired but the conflicts are nontrivial you would like to rebase work that has already been published (simplify results to rebase-with-history) you want to retain a permanent record of how conflicts were resolved you want to collaborate on a merge or rebase


Input: [Selector type] ID selector [Example] #RipVanWinkle [Description]

Output: Matches a single, unique element


Input: [Selector type] HTML element [Example] p [Description]

Output: Matches all paragraphs


Input: [Selector type] HTML element [Example] h1 [Description]

Output: Matches all level-one headers


Input: [Selector type] Class [Example] .classname [Description]

Output: Matches all items with the class classname


Input: [Selector type] Asterisk [Example] * [Description]

Output: Matches all elements


Input: [Selector type] Attribute [Example] input[type=”button”] [Description]

Output: Matches all button input elements


Input: [Variable] %T [Example Value] A Link to Google [Description]

Output: Link text


Input: [Variable] %U [Example Value] http://www.google.com/ [Description]

Output: Link location


Input: [Variable] %I [Example Value] This is the Title Attribute Text [Description]

Output: Link title attribute text


Input: [Variable] %P [Example Value] Born Geek » CoLT Custom Formats [Description]

Output: Current page title


Input: [Variable] %R [Example Value] http://www.borngeek.com/firefox/colt/custom-formats/ [Description]

Output: Current page URL


Input: [Variable] %S [Example Value] — [Description]

Output: Not used for links


Input: [Variable] %L [Example Value] (localized time stamp) [Description]

Output: Local time


Input: [Variable] %N [Example Value] (new line) [Description]

Output: New line character


Input: [Variable] %B [Example Value] (tab) [Description]

Output: Tab character


Input: [Attribute] name [Required] yes [Description] The name of your plugin. [Example] name: MyPlugin [Notes]

Output: Must consist of all alphanumeric characters and underscores (a-z,A-Z,0-9, _) Used to determine the name of the plugin's data folder. Data folders are placed in the ./plugins/ directory by default. It is good practice to name your jar the same as this, for example 'MyPlugin.jar'

Attributes


Input: [Attribute] version [Required] yes [Description] The version of this plugin. [Example] version: 1.4.1 [Notes]

Output: Version is an arbitrary string, however the most common format is MajorRelease.MinorRelease.Build (eg: 1.4.1). Typically you will increment this every time you release a new feature or bug fix. Displayed when a user types /version PluginName

Attributes


Input: [Attribute] description [Required] no [Description] A human friendly description of the functionality your plugin provides. [Example] description: This plugin is so 31337. You can set yourself on fire. [Notes]

Output: The description can have multiple lines. Displayed when a user types /version PluginName

Attributes


Input: [Attribute] load [Required] no [Description] Explicitly state when the plugin should be loaded. if not supplied will default to postworld [Example] load: STARTUP [Notes]

Output: Has two possible values STARTUP POSTWORLD

Attributes


Input: [Attribute] author [Required] no [Description] Uniquely identifies who developed this plugin. [Example] author: CaptainInflamo [Notes]

Output: Gives credit to the developer. Used in some server error messages to provide helpful feedback on who to contact when an error occurs. A bukkit.org forum handle or email address is recommended. Is displayed when a user types /version PluginName

Attributes


Input: [Attribute] authors [Required] no [Description] Allows you to list multiple authors, if it is a collaborative project. See author. [Example] authors: [Cogito, verrier, EvilSeph] [Notes]

Output: You can define both author and authors, however they will be merged into one list internally.

Attributes


Input: [Attribute] website [Required] no [Description] The plugin's or author's website. [Example] website: http://forums.bukkit.org/threads/MyPlugin.31337/ [Notes]

Output: If you have no dedicated website, a link to the Bukkit forum post where this plugin is listed is highly recommended. Displayed when a user types /version PluginName

Attributes


Input: [Attribute] main [Required] yes [Description] Points to the class that extends JavaPlugin [Example] main: org.bukkit.plugin.MyPlugin [Notes]

Output: Note that this must contain the full namespace including the class file itself. If your namespace is org.bukkit.plugin, and your class file is called MyPlugin then this must be org.bukkit.plugin.MyPlugin

Attributes


Input: [Attribute] database [Required] no [Description] Set to true if this plugin uses a database. [Example] database: false [Notes]

Output: Using a database is non-trivial. See Plugin_Databases

Attributes


Input: [Attribute] depend [Required] no [Description] A list of plugins that your plugin requires to load. [Example] depend: [OnePlugin, AnotherPlugin] [Notes]

Output: The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists ) Use the "name" attribute of the required plugin in order to specify the dependency. If any plugin listed here is not found your plugin will fail to load. If multiple plugins list each other as a depend, so that there are no plugins without an unloadable dependency, all will fail to load. (See: Wiki: Plugin_Dependencies)

Attributes


Input: [Attribute] softdepend [Required] no [Description] A list of plugins that are required for your plugin to have full functionality. [Example] softdepend: [OnePlugin, AnotherPlugin] [Notes]

Output: The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists ) Use the "name" atrribute of the desired plugin in order to specify the dependancy. Your plugin will load after any plugins listed here. Circular soft dependencies are loaded arbitrarily. (See: Wiki: Plugin_Dependencies)

Attributes


Input: [Attribute] loadbefore [Required] no [Description] A list of plugins should be loaded after your plugin. [Example] loadbefore: [OnePlugin, AnotherPlugin] [Notes]

Output: The value must be in YAML list format (See http://en.wikipedia.org/wiki/YAML#Lists ) Treated as if the listed plugin soft depends on the specifying plugin. Use the "name" atrribute of the desired plugin in order to specify the target. Your plugin will load before any plugins listed here. Circular soft dependencies are loaded arbitrarily. (See: Wiki: Plugin_Dependencies)

Attributes


Input: [Attribute] commands [Required] no [Description] The name of a command the plugin wishes to register, as well as an optional list of command attributes. [Example] commands: flagrate: [optional command attributes] [Notes]

Output: The command name should not contain the leading '/' required to issue a command. You can choose any command name you wish, however 'common' commands such as /kick are often already registered. Use the 'alias' command attribute to supply alternate names. @TODO: verify we're happy with this

Attributes


Input: [Attribute] permissions [Required] no [Description] Permissions that the plugin whishes to register. Each node represents a permission to register. Each permission can have additional attributes. [Example] permissions: inferno.*: [optional permission attributes] inferno.flagate: [optional permission attributes] inferno.burningdeaths: [optional permission attributes] [Notes]

Output: Permission registration is optional, can also be done from code Permission registration allows you to set descriptions, defaults, and child parent relationships Permission names should be kept in the style of .[category].[category].

Attributes


Input: [Flag Name] IIPDGBFN [Notes] HST ops ast/phot db object [Description]

Output: Cross Index

GSC Flags (IIPDGBFN)


Input: [Flag Name] IIPDGBFN [Notes] HST ops non-ast/phot db object [Description]

Output: Cross Index

GSC Flags (IIPDGBFN)


Input: [Flag Name] IIPDGBFN [Notes] Object Record is frozen and cannot be deleted [Description]

Output: Published

GSC Flags (IIPDGBFN)


Input: [Flag Name] IIPDGBFN [Notes] Object deleted from GSC [Description]

Output: Deleted

GSC Flags (IIPDGBFN)


Input: [Flag Name] IIPDGBFN [Notes] Successful Guide Star (NOT implemented) [Description]

Output: Good

GSC Flags (IIPDGBFN)


Input: [Flag Name] IIPDGBFN [Notes] Unsuccessful Guide Star (NOT implemented) [Description]

Output: Bad

GSC Flags (IIPDGBFN)


Input: [Flag Name] IIPDGBFN [Notes] Multiple object records (eg. multiple plates) [Description]

Output: Further records

GSC Flags (IIPDGBFN)


Input: [Flag Name] IIPDGBFN [Notes] Object entered from catalog instead of a plate [Description]

Output: Not Plate Measure

GSC Flags (IIPDGBFN)


Input: [File type] directories [Color]

Output: blue

Linux System Administration :: Resources :: Ldp LDP Intro-linux Html Intro-linux


Input: [File type] compressed archives [Color]

Output: red

Linux System Administration :: Resources :: Ldp LDP Intro-linux Html Intro-linux


Input: [File type] text files [Color]

Output: white

Linux System Administration :: Resources :: Ldp LDP Intro-linux Html Intro-linux


Input: [File type] images [Color]

Output: pink

Linux System Administration :: Resources :: Ldp LDP Intro-linux Html Intro-linux


Input: [File type] links [Color]

Output: cyan

Linux System Administration :: Resources :: Ldp LDP Intro-linux Html Intro-linux


Input: [File type] devices [Color]

Output: yellow

Linux System Administration :: Resources :: Ldp LDP Intro-linux Html Intro-linux


Input: [File type] executables [Color]

Output: green

Linux System Administration :: Resources :: Ldp LDP Intro-linux Html Intro-linux


Input: [File type] broken links [Color]

Output: flashing red

Linux System Administration :: Resources :: Ldp LDP Intro-linux Html Intro-linux


Input: [Description] Unset value. [Enumeration]

Output: UndefinedType

ImageType


Input: [Description] Monochrome bi-level image [Enumeration]

Output: BilevelType

ImageType


Input: [Description] Grayscale image [Enumeration]

Output: GrayscaleType

ImageType


Input: [Description] Grayscale image with opacity [Enumeration]

Output: GrayscaleMatteType

ImageType


Input: [Description] Indexed color (palette) image [Enumeration]

Output: PaletteType

ImageType


Input: [Description] Indexed color (palette) image with opacity [Enumeration]

Output: PaletteMatteType

ImageType


Input: [Description] Truecolor image [Enumeration]

Output: TrueColorType

ImageType


Input: [Description] Truecolor image with opacity [Enumeration]

Output: TrueColorMatteType

ImageType


Input: [Description] Cyan/Yellow/Magenta/Black (CYMK) image [Enumeration]

Output: ColorSeparationType

ImageType


Input: [Description] Optimize type based on image characteristics [Enumeration]

Output: OptimizeType

ImageType


Input: [Description] The documentation version [Default] "0.1" [Name]

Output: String docVersion


Input: [Description] The path for your app. If you don't override this, you can't play with doc playground. [Default] "Fill with basePath config" [Name]

Output: String basePath


Input: [Description] The file where to store the JSON after generation [Default] "restapidoc.json" [Name]

Output: String outputFileGeneration


Input: [Description] The JSON file to read when looking for the report. Usefull if you upload the file in a specific location on the server. [Default] "restapidoc.json" [Name]

Output: String outputFileReading


Input: [Description] The class path for all customs domains (Define custom domain). You must put the full package path and class name. [Default] null [Name]

Output: String customClassName


Input: [Description] The default format in URL .$format => .json [Default] "json" [Name]

Output: String defaultFormat


Input: [Description] The default response type [Default] MediaType.APPLICATION_JSON_VALUE [Name]

Output: String defaultResponseType


Input: [Description] Usefull if you have a prefix in your controller. With MyBookController, the domain will be MyBook. If controllerPrefix is "My", It will be "Book" [Default] "" [Name]

Output: String controllerPrefix


Input: [Description] See controllerPrefix [Default] "Controller" [Name]

Output: String controllerSuffix


Input: [Description] The string representing the format in each service path. This will be replaced by "defaultFormat" value (from config) or extensions value (from annotation doc) [Default] "{format}" [Name]

Output: String defaultFormatString


Input: [Description] You can add some default doc fields for all your domains. Example: grails.plugins.restapidoc.defaultObjectFields = [[name:"id", type:"Long", useFroCreation="false"]] [Default] [] [Name]

Output: List defaultObjectFields


Input: [Description] Default errors to define for all methods. For example: ["400": "Bad Request: missing parameters or bad message format", "401": "Unauthorized: must be auth", "403": "Forbidden: role error", "404": "Object not found"] [Default] [] [Name]

Output: List defaultErrorAll


Input: [Description] Same as defaultErrorAll, but only for GET methods [Default] [] [Name]

Output: List defaultErrorGet


Input: [Description] Same as defaultErrorAll, but only for POST methods. For example: [ "409": "Object already exist" ] [Default] [ ] [Name]

Output: List defaultErrorPost


Input: [Description] Same as defaultErrorAll, but only for PUT methods [Default] [ ] [Name]

Output: List defaultErrorPut


Input: [Description] Same as defaultErrorAll, but only for DELETE methods [Default] [] [Name]

Output: List defaultErrorDelete


Input: [Description] Map to link a method prefix name with a verb. Only used if no verb is defined in @RestApiMethod and no URL Mappings rules are found for the method. You can override or add new rules (e.g. "modify": PUT) [Default] [ "show" : "GET", "list" : "GET", "save" : "POST", "add" : "POST", "update" : "PUT", "edit" : "PUT", "delete" : "DELETE", "remove" : "DELETE" ] [Name]

Output: Map verbPerMethodPrefix


Input: [Description] Same as verbPerMethodPrefix but for the path. Only used if no path is defined in @RestApiMethod and no URL Mappings rules are found for the method. [Default] [ "show" : "show/{id}", "list" : "list", "add" : "add", "save" : "save", "update" : "udpate/{id}", "edit" : "edit/{id}", "delete" : "delete/{id}", "remove" : "delete/{id}", ] [Name]

Output: Map pathPerMethodPrefix


Input: [Description] The default type for your Grails Domain. You may set "Long" if you only set an id for a Book.author in a book response. By default, it will be "Author" [Default] null, meaning that it will be the domain Class name [Name]

Output: String grailsDomainDefaultType


Input: [Description] Default params for all your queries [Default] [] [Name]

Output: List defaultParamsQueryAll


Input: [Description] Default params for all your methods where listing = false [Default] [] [Name]

Output: List defaultParamsQuerySingle


Input: [Description] Default params for all your methods where listing = true For example: defaultParamsQueryMultiple = [ [name:"max",description:"Pagination: Number of record per page (default 0 = no pagination)",type:"int"], [name:"offset",description:"Pagination: Offset of first record (default 0 = first record)",type:"int"] ] [Default] [] [Name]

Output: List defaultParamsQueryMultiple


Input: [Setting] spam_stop [Default] false [Description]

Output: Enables spam protection


Input: [Setting] spam_test [Default] false [Description]

Output: Stops the spam rules from rejecting items, just logs what it would do. You still need spam_stop true set


Input: [Setting] spam_debug [Default] false [Description]

Output: Makes the rejectiosn 'noisey' normally the user will not be informed if the post is rejected DNews pretends it accepted the item. But while debugging your spam rules you might want to set this to true so you can check it is working.


Input: [Setting] spam_keepn [Default] 5 [Description]

Output: Number of rejected items to store in spam_n.tmp files (for reviewing)


Input: [Setting] spam_dup_total [Default] 5000 [Description]

Output: Number of items to 'remember' in our history of 'duplicate' bodies. Uses about 30 bytes per entry.


Input: [Setting] spam_dup_hits [Default] 6 [Description]

Output: Number of duplicate bodies (not cross posted) to allow


Input: [Setting] spam_dup_cross [Default] 400 [Description]

Output: Number of duplicate bodies counting cross posts to allow


Input: [Setting] spam_from_hits [Default] 60 [Description]

Output: Number of messages from any single user per hour


Input: [Setting] spam_from_cross [Default] 1000 [Description]

Output: Number of messages counting cross posts from any single user per hour


Input: [Setting] spam_from_total [Default] 5000 [Description]

Output: Number of users to keep tabs on in our history of duplicate users, uses about 100 bytes per user.


Input: [Setting] spam_host [Default] false [Description]

Output: Use 'nntp-posting-host' instead of 'from' for the above 3 rules


Input: [key] w [action]

Output: move forward


Input: [key] s [action]

Output: move backward


Input: [key] a [action]

Output: strafe left


Input: [key] d [action]

Output: strafe right


Input: [key] space [action]

Output: enter gravity mode, jump


Input: [key] e [action]

Output: enter flight mode, fly straight up


Input: [key] q [action]

Output: fly straight down


Input: [key] c [action]

Output: speed up


Input: [key] z [action]

Output: slow down


Input: [key] shift [action]

Output: color menu


Input: [key] v [action]

Output: color picker


Input: [key] escape [action]

Output: release mouse


Input: [key] h [action]

Output: this help


Input: [Exception] AtomRegisterFailure [Description]

Output: Thrown if SPCanonicalAtom could not register or un-register a canonical atom representation.

se.sics.jasper (Jasper Package Documentation)

Exception Summary


Input: [Exception] ConnectionFailedException [Description]

Output: Deprecated Only intended as an example

se.sics.jasper (Jasper Package Documentation)

Exception Summary


Input: [Exception] ConversionFailedException [Description]

Output: Thrown if a Java value canot be converted to a Prolog term.

se.sics.jasper (Jasper Package Documentation)

Exception Summary


Input: [Exception] IllegalCallerException [Description]

Output: Thrown if SICStus runtime is called from a thread which is not the creator of the SICStus runtime.

se.sics.jasper (Jasper Package Documentation)

Exception Summary


Input: [Exception] IllegalTermException [Description]

Output: Thrown if trying to use a (no longer) valid SPTerm.

se.sics.jasper (Jasper Package Documentation)

Exception Summary


Input: [Exception] SPException [Description]

Output: Represents a exception thrown by Jasper.

se.sics.jasper (Jasper Package Documentation)

Exception Summary


Input: [Field Name] kind [Description]

Output: gerritcodereview#comment


Input: [Field Name] id [Description]

Output: The URL encoded UUID of the draft comment.


Input: [Field Name] path [1] optional [Description]

Output: The path of the file for which the inline comment was done. Not set if returned in a map where the key is the file path.


Input: [Field Name] side [1] optional [Description]

Output: The side on which the comment was added. Allowed values are REVISION and PARENT. If not set, the default is REVISION.


Input: [Field Name] line [1] optional [Description]

Output: The number of the line for which the comment was done. If not set, it’s a file comment.


Input: [Field Name] in_reply_to [1] optional [Description]

Output: The URL encoded UUID of the comment to which this comment is a reply.


Input: [Field Name] message [1] optional [Description]

Output: The comment message.


Input: [Field Name] updated [Description]

Output: The timestamp of when this comment was written.


Input: [Name] AppGuid [Type] string [Required]

Output: Required


Input: [Name] EntityGuid [Type] string [Required]

Output: Required


Input: [Name] MediaGuid [Type] string [Required]

Output: Required


Input: [Name] MediaName [Type] string [Required]

Output: Required


Input: [Name] FullTag [Type] boolean [Required]

Output: Required


Input: [Name] Source [Type] boolean [Required]

Output: Required


Input: [Name] Width [Type] numeric [Required]

Output: Optional


Input: [Name] Height [Type] numeric [Required]

Output: Optional


Input: [Parameter] Virus warning [Setting] Disabled [Comments]

Output: Symantec Norton Antivirus protects My Super PC.


Input: [Parameter] CPU L2 Cache ECC Checking [Setting] Enabled [Comments]

Output: Improves stability and reliability with no real impact to performance.


Input: [Parameter] Quick Power On Self Test [Setting] Enabled [Comments]

Output: Skip Power On Self-Tests for faster boot.


Input: [Parameter] First Boot Device [Setting] CDROM [Comments]

Output: Normally this should be set to HDD-0 to boot directly from the hard drive, but set it to the CDROM for now since that's how we'll need it when we're ready for the step after configuring the BIOS parameters. When it's set to HDD-0 the computer does not look to see if there's a floppy disk in the floppy drive from which it should boot. Set this to Floppy for disaster recovery procedures.


Input: [Parameter] Second Boot Device [Setting] CDROM [Comments]

Output: Normally this would be set to HDD-0 since the First Boot Device is the only boot device.


Input: [Parameter] Third Boot Device [Setting] CDROM [Comments]

Output: Ditto.


Input: [Parameter] Boot Other Device [Setting] Disabled [Comments]

Output: Gives the "ok" for the BIOS to try the Second Boot Device and Third Boot Device if the First Boot Device is a "no-go", but My Super PC just boots from the First Boot Device, which is the hard drive so - Disabled.


Input: [Parameter] Swap Floppy Drive [Setting] Disabled [Comments]

Output: I've only got one floppy drive, so it's going to be A:.


Input: [Parameter] Boot Up Floppy Seek [Setting] Disabled [Comments]

Output: Skipping this check makes the boot go a bit faster.


Input: [Parameter] Boot Up NumLock Status [Setting] Off [Comments]

Output: This item is a matter of personal taste.


Input: [Parameter] Typematic Rate (Chars/Sec) [Setting] 30 [Comments]

Output: 6, 8, 10, 12, 15, 20, 24, 30


Input: [Parameter] Typematic Delay (Msec) [Setting] 250 [Comments]

Output: 250, 500, 750, 1000. This is the delay, in milliseconds, before the keyboard automatically repeats the keystroke that you have pressed continuously.


Input: [Parameter] Security Option [Setting] Setup [Comments]

Output: If you have set a password, select whether the password is required every time the System boots, or only when you enter Setup. I don't even have a password set, so it's a moot point.


Input: [Parameter] APIC Mode [Setting] Disabled [Comments]

Output: Setting to Enabled can cause instabilities. Once the operating system is installed, such as Windows XP in my case, this setting cannot be changed without reinstalling the operating system, regardless of whether the initial setting is Disabled or Enabled. The purpose of setting it to Enabled is to extend the number of IRQ's, which sounds like a real risky proposition. I'm not surprised to see the conclusion reached at APIC: Benefit or Trouble. The number of IRQ's should be fine without being extended, anyway.


Input: [Parameter] MPS Version Control For OS [Setting] 1.1 [Comments]

Output: Not changeable with APIC Mode set to Disabled.


Input: [Parameter] OS Select For DRAM > 64MB [Setting] Non-OS2 [Comments]

Output: IBM's relic.


Input: [Parameter] Report No FDD For WIN 95 [Setting] No [Comments]

Output: When using Windows 95 without a floppy drive, set to Yes. Say - how many ABIT KR7A-133 motherboards do you suppose are out there running under Windows 95 without a floppy drive?


Input: [Parameter] Video BIOS Shadow [Setting] Disabled [Comments]

Output: Your system will perform better with this setting at Disabled. As you can read in the MS Knowledge base, shadowing is not an advantage. Only enable this if you still use DOS mode a lot, where it can improve performance as it will speed up VGA BIOS (C0000-C7FFF) accesses.


Input: [Parameter] Delay for IDE Initial (Secs) [Setting] 0 [Comments]

Output: Certain hard disk drives require some extra time to spin up in a cold boot. If the system does not start after the memory test, try adding time in this field.


Input: [Description] Call, session or event number [Column]

Output: Item no.


Input: [Description] Start date of the call, session or event [Column]

Output: Date


Input: [Description] Start time of the call, session or event [Column]

Output: Time


Input: [Description] Type of call made (when available description can be found at the bottom of the page) [Column]

Output: Type


Input: [Description] Incoming calls (calls you received) Outgoing calls (where you were located at the time of the call) [Column]

Output: From


Input: [Description] Incoming calls (your own number) Outgoing calls (number you dialed) [Column]

Output: Number called


Input: [Description] Call duration [Column]

Output: Min: sec


Input: [Description] Rate for the airtime part of the call; rate for the usage event [Column]

Output: Rate


Input: [Description] Rate for the long distance part of the call [Column]

Output: Long distance


Input: [Description] Total cost for this call, session or event [Column]

Output: Total


Input: [Description] Usage description [Column]

Output: Details


Input: [Description] Event description [Column]

Output: Event description


Input: [Description] Event type [Column]

Output: Event type


Input: [Description] Total usage for each category (call, session or event) [Column]

Output: Total usage


Input: [Description] Subtotal for each category (call, session or event) [Column]

Output: Subtotal


Input: [Description] Total usage cost (includes calls, sessions and events) [Column]

Output: Total


Input: [To...] Type a CAPITAL letter [Use these keys...]

Output: Hold down the Shift key

Keyboard and Mouse Basics - The Keyboard | Buffalo and Erie County Public Library System


Input: [To...] Move the cursor around the screen [Use these keys...]

Output: Use the Arrow keys

Keyboard and Mouse Basics - The Keyboard | Buffalo and Erie County Public Library System


Input: [To...] Make all the letters CAPITAL [Use these keys...]

Output: Use the Caps Lock Key

Keyboard and Mouse Basics - The Keyboard | Buffalo and Erie County Public Library System


Input: [To...] Go to the next line [Use these keys...]

Output: Press the Enter key

Keyboard and Mouse Basics - The Keyboard | Buffalo and Erie County Public Library System


Input: [To...] Remove text to the LEFT of the cursor [Use these keys...]

Output: Press the Back Space key

Keyboard and Mouse Basics - The Keyboard | Buffalo and Erie County Public Library System


Input: [To...] Remove text to the RIGHT of cursor [Use these keys...]

Output: Press the Delete key

Keyboard and Mouse Basics - The Keyboard | Buffalo and Erie County Public Library System


Input: [To...] Type the @ symbol [Use these keys...]

Output: Hold Shift and press the 2 key

Keyboard and Mouse Basics - The Keyboard | Buffalo and Erie County Public Library System


Input: [To...] Type the ~ (tilde) symbol [Use these keys...]

Output: Hold Shift and press the ` key

Keyboard and Mouse Basics - The Keyboard | Buffalo and Erie County Public Library System


Input: [Name] name [required] [Type] string [Description]

Output: Name of the package, used to uniquely identify the package. Must be comprised of only lower case ASCII alpha-numeric characters, "-" or "_".

Package file format (JSON) - DUB - The D package registry


Input: [Name] description [required for publishing] [Type] string [Description]

Output: Brief description of the package

Package file format (JSON) - DUB - The D package registry


Input: [Name] homepage [Type] string [Description]

Output: URL of the project website

Package file format (JSON) - DUB - The D package registry


Input: [Name] authors [Type] string[] [Description]

Output: List of project authors

Package file format (JSON) - DUB - The D package registry


Input: [Name] copyright [Type] string [Description]

Output: Copyright declaration string

Package file format (JSON) - DUB - The D package registry


Input: [Name] license [required for publishing] [Type] string [Description]

Output: License(s) under which the project can be used - see the license specification section for possible values

Package file format (JSON) - DUB - The D package registry


Input: [Name] subPackages [Type] T[] [Description]

Output: Defines an array of sub-packages defined in the same directory as the root project, where each entry is either a path of a sub folder or an object of the same formatas a dub.json file - see the sub package section for more information

Package file format (JSON) - DUB - The D package registry


Input: [Name] configurations [Type] T[] [Description]

Output: Speficies an optional list of build configurations (chosen on the command line using --config=...) - see the configurations section for more details

Package file format (JSON) - DUB - The D package registry


Input: [Name] buildTypes [Type] T[string] [Description]

Output: Defines additional custom build types or overrides the default ones (chosen on the command line using --build=...) - see the build types section for an example

Package file format (JSON) - DUB - The D package registry


Input: [Name] -ddoxFilterArgs [Type] string[] [Description]

Output: Specifies a list of command line flags usable for controlling filter behavior for --build=ddox [experimental]

Package file format (JSON) - DUB - The D package registry


Input: [Report] DELIVERED [Description] The transaction was completed successfully. If a billed message was sent then the end user was charged. [Retries possible?] ✖ [Final status?]


Input: [Report] NO_CREDIT [Description] Delivery of the message failed because the end user did not have sufficient credit to complete the transaction at this time. [Retries possible?] ✔ [Final status?]


Input: [Report] FAILED [Description] The transaction could not be completed. [Retries possible?] ✔ [Final status?]


Input: [Report] VALIDITY_EXPIRED [Description] The message could not be delivered to the end user as the validity period expired. An SMS message is stored temporarily in the SMS center / network operator if the recipient mobile phone is unavailable, e.g. off / out of reception / flight mode / any other reason that the phone can't be contacted. Once deleted from the network's temporary store, the SMS message will no longer be available for dispatch to the recipient mobile phone (even if it becomes online). Mobile networks only store text messages for a limited time as there is a limit to available space in which to store the messages. [Retries possible?] ✔ [Final status?]


Input: [Report] REJECTED [Description] The transaction was rejected by the operator. You must not continue to send charges to the end user. [Retries possible?] ✖ [Final status?]


Input: [Report] INVALID_MSISDN [Description] The transaction could not be completed as the MSISDN was malformed or does not exist. [Retries possible?] ✖ [Final status?]


Input: [Report] ACKNOWLEDGED [Description] The transaction has been acknowledged for delivery by the operator. This is a transient state and may be succeeded by further reports. This status is categorised as "unconfirmed" in the Account Balance. [Retries possible?] ✖ [Final status?]


Input: [Report] ACCEPTED [Description] The transaction has been accepted by the operator and can be treated as DELIVERED. Although this is a transient state it may also be succeeded by further reports. This status is categorised as "confirmed" in the Account Balance. [Retries possible?] ✖ [Final status?]


Input: [Report] UNKNOWN [Description] The transaction could not be categorised as the operator or handset returned an undocumented status. [Retries possible?] ✔ [Final status?]


Input: [Report] OPERATOR_ERROR [Description] The transaction could not be completed as there was an error with the operator. Please contact our support team. [Retries possible?] ✔ [Final status?]


Input: [Tab name] - [Property name] Name [Property value] Tomcat (Pluto:8080) [Description]

Output: Can be any name you want to give it. Mine says what and where

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Tab name] Connect [Property name] Project [Property value] hl-www [Description]

Output: This is your project name

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Tab name] Connect [Property name] Connection Type [Property value] Standard - Socket Attach [Description]

Output: Connect over a socket

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Tab name] Connect [Property name] Connection Properties : Host [Property value] pluto.healthline.com [Description]

Output: DNS name of the host, could be an IP address (I think)

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Tab name] Connect [Property name] Connection Properties : Port [Property value] 8787 [Description]

Output: Same port as specified in address above

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Tab name] Connect [Property name] Allow termination of remote VM [Property value] No [Description]

Output: This is really your choice, I just don't want it.

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Tab name] Source [Property name] Source Lookup Path [Property value] Select your project [Description]

Output: This is so you can see the sources as you debug

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Tab name] Source [Property name] Source Lookup Path [Property value] Select any other source jars you have [Description]

Output: This is so you can see the sources as you debug

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Tab name] Common [Property name] Display in Favorites Menu [Property value] Yes [Description]

Output: This adds the config as a bookmark under the debug icon.

Debugging and Profiling with Eclipse, Jetty, and Tomcat


Input: [Command] call [Description]

Output: Executes arbitrary remote shell command


Input: [Command] cd [Description]

Output: Changes remote working directory


Input: [Command] checksum [Description]

Output: Calculates checksum of remote file


Input: [Command] chmod [Description]

Output: Changes permissions of remote file


Input: [Command] close [Description]

Output: Closes session


Input: [Command] echo [Description]

Output: Prints message onto script output


Input: [Command] exit [Description]

Output: Closes all sessions and terminates the program


Input: [Command] get [Description]

Output: Downloads file from remote directory to local directory


Input: [Command] help [Description]

Output: Displays help


Input: [Command] keepuptodate [Description]

Output: Continuously reflects changes in local directory on remote one


Input: [Command] lcd [Description]

Output: Changes local working directory


Input: [Command] lls [Description]

Output: Lists the contents of local directory


Input: [Command] ln [Description]

Output: Creates remote symbolic link


Input: [Command] lpwd [Description]

Output: Prints local working directory


Input: [Command] ls [Description]

Output: Lists the contents of remote directory


Input: [Command] mkdir [Description]

Output: Creates remote directory


Input: [Command] mv [Description]

Output: Moves or renames remote file


Input: [Command] open [Description]

Output: Connects to server


Input: [Command] option [Description]

Output: Sets or shows value of script options


Input: [Command] put [Description]

Output: Uploads file from local directory to remote directory


Input: [Command] pwd [Description]

Output: Prints remote working directory


Input: [Command] rm [Description]

Output: Removes remote file


Input: [Command] rmdir [Description]

Output: Removes remote directory


Input: [Command] session [Description]

Output: Lists connected sessions or selects active session


Input: [Command] stat [Description]

Output: Retrieves attributes of remote file


Input: [Command] synchronize [Description]

Output: Synchronizes remote directory with local one


Input: [Type] n/a [Meaning] No effect. URLs are always generated as absolute. [Key]

Output: _absolute

Magento get url with or without parameters - dltr.org


Input: [Type] bool [Meaning] Uses the current module, controller, action and parameters [Key]

Output: _current

Magento get url with or without parameters - dltr.org


Input: [Type] string [Meaning] Simply append to the base URL, same effect as passing to $routePath. See _store [Key]

Output: _direct

Magento get url with or without parameters - dltr.org


Input: [Type] bool [Meaning] Uses & instead of & [Key]

Output: _escape

Magento get url with or without parameters - dltr.org


Input: [Type] bool [Meaning] Uses the secure domain given in configuration [Key]

Output: _forced_secure

Magento get url with or without parameters - dltr.org


Input: [Type] string [Meaning] The last part of the URL after a # [Key]

Output: _fragment

Magento get url with or without parameters - dltr.org


Input: [Type] bool [Meaning] Only applies to Mage_Catalog_Model_Product_Url::getUrl(). Prevents category rewrite from being used. [Key]

Output: _ignore_category

Magento get url with or without parameters - dltr.org


Input: [Type] bool [Meaning] Prevents a SID query parameter being used when referencing another store [Key]

Output: _nosid

Magento get url with or without parameters - dltr.org


Input: [Type] string or array [Meaning] If an array it is converted into a string like ?key=value&key=value which will become the $_GET variable. [Key]

Output: _query

Magento get url with or without parameters - dltr.org


Input: [Type] bool [Meaning] Uses the secure domain if allowed in configuration [Key]

Output: _secure

Magento get url with or without parameters - dltr.org


Input: [Type] int or string [Meaning] Either the numeric store ID or textual store code. It will use the correct domain as the base URL. [Key]

Output: _store

Magento get url with or without parameters - dltr.org


Input: [Type] bool [Meaning] Adds ___store to the query parameters. Useful for targetting a store that doesn’t have an unique domain. [Key]

Output: _store_to_url

Magento get url with or without parameters - dltr.org


Input: [Type] string [Meaning] link is the default. direct_link is useful for bypassing the “store code in URLs” feature. js, media and skin append the domain (and possibly store code) with the relevant directory. [Key]

Output: _type

Magento get url with or without parameters - dltr.org


Input: [Type] bool [Meaning] Looks up the module/controller/action/parameters in the database for a search engine friendly equivalent. [Key]

Output: _use_rewrite

Magento get url with or without parameters - dltr.org


Input: [Instrument] High/Low [Type of Option] High [Parameter] Market Price [Change]

Output: Increases


Input: [Instrument] High/Low [Type of Option] Low [Parameter] Market Price [Change]

Output: Decreases


Input: [Instrument] One Touch [Type of Option] Touch [Parameter] Market Price [Change]

Output: Moves towards the touch value


Input: [Instrument] One Touch [Type of Option] No Touch [Parameter] Market Price [Change]

Output: Moves away from touch value


Input: [Instrument] Boundary [Type of Option] In Bound [Parameter] Market Price [Change]

Output: Moves towards the boundary formed by the upper and lower target values


Input: [Instrument] Boundary [Type of Option] Out Bound [Parameter] Market Price [Change]

Output: Moves towards the edges of the boundary formed by the upper and lower target values


Input: [Tool] Beacons [Description]

Output: A user can click on the terrain and place a beacon marking an area of interest.


Input: [Tool] Climate Readout [Description]

Output: Brings up a readout of GCM simulation data (stored at NetCDF files), including wind velocity, temperature and pressure readouts, as well as latitude and longitude information. The user can cycle through different solar days to see the variation of variables over time.


Input: [Tool] Global Planes [Description]

Output: The user can move a translucent horizontal plane through the rendered terrain; the intersection of the plane with the terrain gives a line of constant elevation.


Input: [Tool] Contours [Description]

Output: Using fragment shaders, this feature provides multiple contour lines that the user can move in real-time.


Input: [Tool] Distance Mode [Description]

Output: Measures and displays the distance between two selected beacons.


Input: [Tool] Terrain Profile [Description]

Output: The user can select two points; a heightfield profile of the 'slice' going between these points is displayed.


Input: [Tool] Strike/Dip [Description]

Output: The user can select multiple points on the surface; the program computes a best fitting plane and returns the strike and dip values.


Input: [Tool] Inset Mode [Description]

Output: A small overlay map can be displayed to display the user position and beacon locations relative to the entire globe.


Input: [Tool] Image Overlays [Description]

Output: ADVISER can display a variety of image overlays on top of the terrain, such as Viking, THEMIS, HRSC and MOC. These datasets are textured on top of the MOLA topography.


Input: [Tool] Lighting [Description]

Output: The user can display different colormaps (elevation/slope based); specify the direction for illumination; or set the illumination direction based on the solar position for a certain time of the year.


Input: [Tool] Scale Tools [Description]

Output: The user can change the vertical exaggeration factor for the topography. He can also change the global scale for the model.


Input: [Tool] Traverse [Description]

Output: This mode can show traverses on the terrain. Currently being used in the Mars Palmer Quest Mission Design Project, a Tablet PC can be used to interactively edit traverses. A function can be evaluated along the traverse to indicate interesting areas.


Input: [Symbol] error [Meaning]

Output: SQL error or missing database


Input: [Symbol] internal [Meaning]

Output: An internal logic error in SQLite


Input: [Symbol] permission [Meaning]

Output: Access permission denied


Input: [Symbol] abort [Meaning]

Output: Callback routine requested an abort


Input: [Symbol] busy [Meaning]

Output: The database file is locked


Input: [Symbol] locked [Meaning]

Output: A table in the database is locked


Input: [Symbol] no-memory [Meaning]

Output: A malloc() failed


Input: [Symbol] read-only [Meaning]

Output: Attempt to write a readonly database


Input: [Symbol] interrupt [Meaning]

Output: Operation terminated by sqlite-interrupt()


Input: [Symbol] io-error [Meaning]

Output: Some kind of disk I/O error occurred


Input: [Symbol] corrupt [Meaning]

Output: The database disk image is malformed


Input: [Symbol] not-found [Meaning]

Output: (Internal Only) Table or record not found


Input: [Symbol] full [Meaning]

Output: Insertion failed because database is full


Input: [Symbol] cant-open [Meaning]

Output: Unable to open the database file


Input: [Symbol] protocol [Meaning]

Output: Database lock protocol error


Input: [Symbol] empty [Meaning]

Output: (Internal Only) Database table is empty


Input: [Symbol] schema [Meaning]

Output: The database schema changed


Input: [Symbol] too-big [Meaning]

Output: Too much data for one row of a table


Input: [Symbol] constraint [Meaning]

Output: Abort due to contraint violation


Input: [Symbol] mismatch [Meaning]

Output: Data type mismatch


Input: [Symbol] misuse [Meaning]

Output: Library used incorrectly


Input: [Symbol] no-lfs [Meaning]

Output: Uses OS features not supported on host


Input: [Symbol] authorization [Meaning]

Output: Authorization denied


Input: [Symbol] done [Meaning]

Output: sqlite3:step! has finished executing, so no further data is ready


Input: [Class] DeleteColumnOperation [Description]

Output: Operation used to delete a DITA simple table column.

ro.sync.ecss.extensions.dita.topic.table.simpletable (<oXygen/> XML API)

Class Summary


Input: [Class] DeleteRowOperation [Description]

Output: Operation used to delete a DITA simple table row.

ro.sync.ecss.extensions.dita.topic.table.simpletable (<oXygen/> XML API)

Class Summary


Input: [Class] DITASimpleTableDocumentTypeHelper [Description]

Output: Implementation of the document type helper for DITA simple table model

ro.sync.ecss.extensions.dita.topic.table.simpletable (<oXygen/> XML API)

Class Summary


Input: [Class] InsertColumnOperation [Description]

Output: Operation used to insert one or more DITA simple table columns.

ro.sync.ecss.extensions.dita.topic.table.simpletable (<oXygen/> XML API)

Class Summary


Input: [Class] InsertRowOperation [Description]

Output: Operation used to insert a simple table row for DITA.

ro.sync.ecss.extensions.dita.topic.table.simpletable (<oXygen/> XML API)

Class Summary


Input: [Class] JoinCellAboveBelowOperation [Description]

Output: Operation for joining the content of two cells from adjacent rows, DITA simpletable implementation.

ro.sync.ecss.extensions.dita.topic.table.simpletable (<oXygen/> XML API)

Class Summary


Input: [Class] JoinRowCellsOperation [Description]

Output: This is the DITA simple tables implementation of the operation used to join the content of two or more cells from a table row.

ro.sync.ecss.extensions.dita.topic.table.simpletable (<oXygen/> XML API)

Class Summary


Input: [Class] SimpleTableCellSpanProvider [Description]

Output: This class is responsible for providing information about the DITA simple table cell spanning.

ro.sync.ecss.extensions.dita.topic.table.simpletable (<oXygen/> XML API)

Class Summary


Input: [Interface] Interface support multiple inheritance [Abstract class]

Output: Abstract class does not support multiple inheritance

Difference between abstract class and interface - ASP.NET,C#.NET,MVC,JQuery,JavaScript,SQL Server,WCF examples


Input: [Interface] Interface does'n Contains Data Member [Abstract class]

Output: Abstract class contains Data Member

Difference between abstract class and interface - ASP.NET,C#.NET,MVC,JQuery,JavaScript,SQL Server,WCF examples


Input: [Interface] Interface does'n contains Cunstructors [Abstract class]

Output: Abstract class contains Cunstructors

Difference between abstract class and interface - ASP.NET,C#.NET,MVC,JQuery,JavaScript,SQL Server,WCF examples


Input: [Interface] An interface Contains only incomplete member (signature of member) [Abstract class]

Output: An abstract class Contains both incomplete (abstract) and complete member

Difference between abstract class and interface - ASP.NET,C#.NET,MVC,JQuery,JavaScript,SQL Server,WCF examples


Input: [Interface] An interface cannot have access modifiers by default everything is assumed as public [Abstract class]

Output: An abstract class can contain access modifiers for the subs, functions, properties

Difference between abstract class and interface - ASP.NET,C#.NET,MVC,JQuery,JavaScript,SQL Server,WCF examples


Input: [Interface] Member of interface can not be Static [Abstract class]

Output: Only Complete Member of abstract class can be Static

Difference between abstract class and interface - ASP.NET,C#.NET,MVC,JQuery,JavaScript,SQL Server,WCF examples


Input: [Interface] atm.h [Implementation] atm.cc [Purpose]

Output: ATM itself


Input: [Interface] atmparts.h [Implementation] atmparts.cc [Purpose]

Output: Component parts of ATM


Input: [Interface] session.h [Implementation] session.cc [Purpose]

Output: Perform a customer session


Input: [Interface] transaction.h [Implementation] transaction.cc [Purpose]

Output: Perform a transaction


Input: [Interface] bank.h [Implementation] bank.cc [Purpose]

Output: Manage communication with bank


Input: [Interface] money.h [Implementation] money.cc [Purpose]

Output: Abstract data type Money


Input: [Interface] status.h [Implementation] (None) [Purpose]

Output: Status code values


Input: [Interface] (None) [Implementation] main.cc [Purpose]

Output: Main program


Input: [Required] Yes [Details] Can be "file" of "folder".Type "file" to convert a single file or "folder" to convert a whole folder. [Parameter]

Output: source type


Input: [Required] Yes [Details] The path of the file or folder you want to convert. Make sure your source path don't end with a slash. [Parameter]

Output: source path


Input: [Required] Yes [Details] The target path of the output file/s Make sure your target path don't end with a slash. [Parameter]

Output: target path


Input: [Required] Yes [Details] The name of the table you want to convert or "a" to convert all tables in the file. If you convert a folder you need to type "a". [Parameter]

Output: table name


Input: [Required] No [Details] Type here names of columns yolu want to export. Separate names with comma like this example: CompanyName,FullName [Parameter]

Output: columns


Input: [Required] Yes [Details] Type of the output. Can be equal to "txt", "csv" or "xml". [Parameter]

Output: target file type


Input: [Required] Yes [Details] You can filter data in the table you want to export using the SQL WHERE statement filter. Type here the filter value (Example:FirstName='Jane') or "all" to export all data. [Parameter]

Output: sql filter value


Input: [Directive] #ifdef symbol [Meaning]

Output: If symbol is defined then compile the following code


Input: [Directive] #ifndef symbol [Meaning]

Output: If symbol is not defined then compile the following code


Input: [Directive] #else [Meaning]

Output: Switch from compiling to not compiling and vice versa


Input: [Directive] #endif [Meaning]

Output: Return to previous compiling state


Input: [Directive] #if condition [Meaning]

Output: If the condition evaluates to true then compile the following code


Input: [Directive] #elif [Meaning]

Output: Same as #else but used with #if


Input: [Name] Add Shape [Description]

Output: Adds another shape to the selected SmartArt graphic.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Add Bullet [Description]

Output: Adds a bullet at the same level as the selected text.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Right to Left [Description]

Output: Changes the direction of the chosen element such as an arrow from right to left. This is a toggle option.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Layout [Description]

Output: Enables you to change the hierarchy level of the selected SmartArt component.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Promote [Description]

Output: Promotes the level of the selected SmartArt component.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Demote [Description]

Output: Demotes the level of the selected SmartArt component.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Text Pane [Description]

Output: Makes the text pane visible so that you can also edit the SmartArt text as bullet points. This is a toggle option.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Layouts [Description]

Output: Shows more layouts in the same SmartArt type—so if you have an organization chart on the slide, this shows you more SmartArt layouts for organization charts.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Change Colors [Description]

Output: Lets you change the color combination of the elements contained in the SmartArt graphic.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] SmartArt Styles [Description]

Output: Provides more styles of the selected SmartArt graphic, with changed colors and effects.

SmartArt Diagrams, PowerPoint Presentations


Input: [Name] Reset Graphic [Description]

Output: Resets the graphic to the original SmartArt graphic, which is helpful if you have resized elements.

SmartArt Diagrams, PowerPoint Presentations


Input: [Command Input] None [Abbreviated Command Input] None [Description] This is the Default mode. It is automatically selected when no other primary mode is during the first 15 seconds. Players may pick heroes from taverns belonging to their team. [Mode Name]

Output: Normal Mode


Input: [Command Input] -allpick [Abbreviated Command Input] -ap [Description] Everyone may pick heroes from any tavern. Creeps spawn starting at the 2 minute mark. [Mode Name]

Output: All Pick


Input: [Command Input] -allrandom [Abbreviated Command Input] -ar [Description] Every player gets a random hero from any tavern [Incompatible With] Reverse Mode [Mode Name]

Output: All Random


Input: [Command Input] -teamrandom [Abbreviated Command Input] -tr [Description] Every player gets a random hero from the taverns belonging to their team [Incompatible With] Reverse Mode, Death Match [Mode Name]

Output: Team Random


Input: [Command Input] -moderandom [Abbreviated Command Input] -mr [Description] Randomly picks a mode from All Random, All Pick, Team Random and Normal Mode. [Incompatible With] Reverse Mode, Death Match. [Version Introduced In] 6.28 [Mode Name]

Output: Mode Random


Input: [Command Input] -singledraft [Abbreviated Command Input] -sd [Description] Three different random heroes are offered to each player, one for each Primary Attribute. Each player chooses which of the three heroes they want by typing -pick 1/2/3. [Version Introduced In] 6.50 [Mode Name]

Output: Single Draft


Input: [Command Input] -leaguemode [Abbreviated Command Input] -lm [Description] All forms of random are disabled. 10 players required. The teams will pick in alternating orders, one team picking one hero, the other team picks two heroes, the first team picks two heroes, the other team picks two heroes, the first team picks their two last heroes, the other team picks their last hero (1-2-2-2-2-1). Each player has 20 seconds to pick a hero, otherwise one is randomed for him/her. The team which has the first pick is random. Can only pick from your side, Sentinel or Scourge, like Normal Mode. [Incompatible With] All secondary game modes except Shuffle Players, No Swap, No Repick, and Terrain Snow. [Version Introduced In] 6.21 [Mode Name]

Output: League Mode


Input: [Command Input] -extendedleague [Abbreviated Command Input] -xl [Description] All forms of random are disabled. 10 players required. Both team leaders (blue for Sentinel, pink for Scourge) may remove up to 4 heroes each from all available ones in the first 20 seconds. Players then pick from the remaining heroes like in League Mode. Creeps spawn starting at the 3 minute mark. [Incompatible With] All secondary game modes except Shuffle Players, No Swap, No Repick, and Terrain Snow. [Version Introduced In] 6.43 [Mode Name]

Output: Extended League


Input: [Command Input] -randomdraft [Abbreviated Command Input] -rd [Description] Needs an even amount of players on each team to be activated. 22 random heroes are picked from all available ones and placed into 2 taverns (available for both Sentinel and Scourge). The remaining heroes are removed, as well as the rest of the taverns. Players then pick from those two taverns like in League Mode. [Incompatible With] Mirror Match, Death Match, All Agility, All Intelligence, All Strength, Same Hero, Reverse Mode [Version Introduced In] 6.39 [Mode Name]

Output: Random Draft


Input: [Command Input] -voterandom [Abbreviated Command Input] -vr [Description] Three random matchups will be chosen, and each player gets to cast a vote on which of the three matchups they want, using -option 1/2/3. Needs an even amount of players on each team to be activated. [Incompatible With] Mirror Match, Death Match, All Agility, All Intelligence, All Strength, Same Hero, Reverse Mode [Version Introduced In] 6.35 [Mode Name]

Output: Vote Random


Input: [Shortcut (All Browser)] Shift+Alt+1 [Shortcut (Google Chrome)] Alt+1 [Action]

Output: Home Page


Input: [Shortcut (All Browser)] Shift+Alt+2 [Shortcut (Google Chrome)] Alt+2 [Action]

Output: Timeline Page


Input: [Shortcut (All Browser)] Shift+Alt+3 [Shortcut (Google Chrome)] Alt+3 [Action]

Output: Friend Requests list


Input: [Shortcut (All Browser)] Shift+Alt+4 [Shortcut (Google Chrome)] Alt+4 [Action]

Output: See the Message list


Input: [Shortcut (All Browser)] Shift+Alt+5 [Shortcut (Google Chrome)] Alt+5 [Action]

Output: Notification list


Input: [Shortcut (All Browser)] Shift+Alt+6 [Shortcut (Google Chrome)] Alt+6 [Action]

Output: Account Settings


Input: [Shortcut (All Browser)] Shift+Alt+7 [Shortcut (Google Chrome)] Alt+7 [Action]

Output: Privacy Settings


Input: [Shortcut (All Browser)] Shift+Alt+8 [Shortcut (Google Chrome)] Alt+8 [Action]

Output: Facebook Fan Page


Input: [Shortcut (All Browser)] Shift+Alt+9 [Shortcut (Google Chrome)] Alt+9 [Action]

Output: Facebook Terms of Use


Input: [Shortcut (All Browser)] Shift+Alt+0 [Shortcut (Google Chrome)] Alt+0 [Action]

Output: Facebook Help Center


Input: [Shortcut (All Browser)] Shift+Alt+m [Shortcut (Google Chrome)] Alt+m [Action]

Output: New message


Input: [Shortcut (All Browser)] Shift+Alt+? [Shortcut (Google Chrome)] Alt+? [Action]

Output: Search Box


Input: [Description] Provides useful information about a contribution [Parameter]

Output: contribution

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Unique, permanent identifier for the contribution [Parameter]

Output: @order-number

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Describes the person who made the contribution [Parameter]

Output: source

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] First name [Parameter]

Output: firstname

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Last name [Parameter]

Output: lastname

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Mailing address line 1 [Parameter]

Output: addr1

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Mailing address line 2 [Parameter]

Output: addr2

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Mailing address city [Parameter]

Output: city

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Mailing address state [Parameter]

Output: state

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Mailing address ZIP code [Parameter]

Output: zip

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Mailing address country [Parameter]

Output: country

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Occupation [Parameter]

Output: occupation

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Employer name [Parameter]

Output: employer

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Employer address line 1 [Parameter]

Output: empaddr1

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Employer address line 2 [Parameter]

Output: empaddr2

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Employer address city [Parameter]

Output: empcity

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Employer address state [Parameter]

Output: empstate

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Employer address ZIP code [Parameter]

Output: empzip

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Employer address country [Parameter]

Output: empcountry

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Source email address [Parameter]

Output: email

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Source phone number [Parameter]

Output: phone

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] True if donor prefers contact by email, false if source prefers contact by postal mail [Parameter]

Output: email-preferred

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Number of times this contribution is initially set to recur. This value does not change with time. Non-recurring contributions are indicated with 1. [Parameter]

Output: recurringtimes

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] An opaque alphanumeric string that API clients or interactive users may use to segment contribution data. [Parameter]

Output: refcode

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Collection of donations to individual candidates or committees that are part of this contribution [Parameter]

Output: lineitems

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] A donation to an individual candidate or committee as part of a contribution [Parameter]

Output: lineitem

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] ISO-8601 timestamp when payment was processed for this lineitem [Parameter]

Output: @effective-at

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] The amount of the lineitem as two-place fixed demical (1.23) in dollars (USD). [Parameter]

Output: amount

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] The sequence number of the lineitem. The first month of a recurring contribution generates lineitems with sequence 1. As each following month is processed, a new lineitem with an incremented sequence is added to the contribution. [Parameter]

Output: sequence

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Abbreviated representation of the lineitem's destination [Parameter]

Output: entity

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] The system ID for the destination entity [Parameter]

Output: @id

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] The legal name (Obama for America) of the destination [Parameter]

Output: legalname

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] The display name (Barack Obama) of the destination [Parameter]

Output: displayname

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Abbreviated XML for this contribution's fundraising page [Parameter]

Output: page

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Name (final URL component) of fundraising page [Parameter]

Output: @name

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Page title [Parameter]

Output: title

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Page author [Parameter]

Output: author

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Fundraising page owner [Parameter]

Output: user

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Unique user account identifier [Parameter]

Output: @user-key

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Email address [Parameter]

Output: email

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] For event pages, collection of tickets associated with contribution [Parameter]

Output: tickets

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Individual ticket [Parameter]

Output: ticket

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Name of the ticket type. Set by the fundraising page owner. [Parameter]

Output: type

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Price of this ticket type, as two-place fixed demical (1.23) in dollars (USD). Set by the fundraising page owner. [Parameter]

Output: amount

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Name of person on ticket, assigned by contributor [Parameter]

Output: name

ActBlue — Introduction to the ActBlue Contributions API


Input: [Description] Freeform notes for this ticket, assigned by contributor [Parameter]

Output: notes

ActBlue — Introduction to the ActBlue Contributions API


Input: [Directive] fork [Explanation] If set, run updates of several hosts simultaneously. [Default value]

Output: Yes


Input: [Directive] max_processes [Explanation] Set max number of simultaneous Munin-update processes. Should be no higher than 4 x CPU cores. [Default value]

Output: 16


Input: [Directive] domain_order [Explanation] Change the order of domains/groups. [Default value]

Output: Alphabetically sorted


Input: [Directive] max_graph_jobs [Explanation] Maximum number of parallel processes used by munin-graph when calling rrdgraph. Available since Munin 1.4.0 [Required] 6 [Default value]

Output: The optimal number is very hard to guess and depends on the number of cores of CPU, the I/O bandwidth available, if you have SCSI or (S)ATA disks and so on. You will need to experiment. Set on the command line with the -n n option. Set to 0 for no forking.


Input: [Directive] max_cgi_graph_jobs [Explanation] Maximum number of concurrent/parallel. munin-cgi-graph or munin-fastcgi-graph jobs. [Required] 6 [Default value]

Output: Should probably be the same as max_graph_jobs


Input: [Directive] local_address [Explanation] Sets the local IP address that munin-update should bind to when contacting the nodes. May be used several times (one line each) on a multi-homed host. [Required] No [Default value]

Output: Should default to the most appropriate interface based on routing decision, if you don't set it explicitly.


Input: [Directive] contact.contact.max_messages number [Explanation] Close (and reopen) command after given number of messages. E.g. if set to 1 for an email target, Munin sends 1 email for each warning/critical. Useful when relaying messages to external processes that may handle a limited number of simultaneous warnings. [Default value]

Output: Unlimited


Input: [Directive] contacts contact-list [Explanation] A list of the available contacts to use by default. [Default value]

Output: Defaults to all contacts with a command definition.


Input: [Press] HOME [To do this]

Output: Go to column A of the active row

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] END+ arrow [To do this]

Output: Go to the edge of the spreadsheet

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] CTRL+HOME [To do this]

Output: Go to cell A1 of the active worksheet

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] CTRL+END [To do this]

Output: Go to last cell of the spreadsheet data

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] PAGEUP OR PAGEDOWN [To do this]

Output: Scroll one window up or down

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] ALT+PAGEUP OR PAGEDOWN [To do this]

Output: Scroll one window left or right

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] CTRL+. [To do this]

Output: Move among the four corners of the selected range

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] Click the Name box, type the cell reference you want to go to and press ENTER [To do this]

Output: Go to a specified cell

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] LEFT ARROW or RIGHT ARROW [To do this]

Output: Move one column to the left or right.

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] UP ARROW or DOWN ARROW [To do this]

Output: Move one row up or down.

45+ Shortcuts to make Microsoft Excel easier


Input: [Press] CTRL+ALT+LEFT ARROW or RIGHT ARROW [To do this]

Output: Move between noncontiguous selected ranges

45+ Shortcuts to make Microsoft Excel easier


Input: [Description] The name of a file for applicants. Each line in the file is a full class name, which will be an applicant who wants to be redefined for logging before be loaded. [Default value] limpidlog.applicants [Option]

Output: applicants


Input: [Description] The full name of the implementation of limpidlog.Bytecoder. [Default value] limpidlog.asm1.Bytecoder1 [Option]

Output: bytecoderClass


Input: [Description] The JDBC driver name of database which stores log data when the option logProxy is database. [Option]

Output: databaseDriverName


Input: [Description] The URL of database which stores log data when the option logProxy is database. [Option]

Output: databaseUrl


Input: [Description] The user name of database which stores log data when the option logProxy is database. [Option]

Output: databaseUserName


Input: [Description] The password for the user of database which stores log data when the option logProxy is database. [Option]

Output: databasePassword


Input: [Description] Indicates if general debug information should be logged. This is for debugging inside of LimpidLog. [Default value] false [Option]

Output: debug


Input: [Description] The base name for logging to a file. [Default value] limpidlog [Option]

Output: fileLogBaseName


Input: [Description] The maximum size of the log file. When the file is bigger than this, a new log file will be used. Unit: Meg. [Default value] 100 M [Option]

Output: fileLogMaxSize


Input: [Description] Indicates should or not log method argument [Default value] true [Option]

Output: logOnArgument


Input: [Description] Indicates should or not log on field assignment [Default value] true [Option]

Output: logOnField


Input: [Description] Indicates should or not log on event of increase [Default value] true [Option]

Output: logOnIncrease


Input: [Description] Indicates should or not log on event of returning from a method [Default value] true [Option]

Output: logOnReturn


Input: [Description] Indicates should or not log on event of store. [Default value] true [Option]

Output: logOnStore


Input: [Description] The full name of the class which implements limpidlog.LogProxy. It can be keyword console, database or file. [Default value] console [Option]

Output: logProxy


Input: [Description] Indicates should or not be interested in logging of classes of LimpieLog. [Default value] true [Option]

Output: noLimpidlog


Input: [Description] Indicates should or not be interested in logging of Java classes. [Default value] true [Option]

Output: noJava


Input: [Description] Indicates should or not be interested in logging of classes starts with "sun.". [Default value] true [Option]

Output: noSun


Input: [Description] The port number used for agent and manager of LimpidLog. [Default value] 9876 [Option]

Output: port


Input: [Description] The name of properties file of LimpidLog. [Default value] limpidlog.properties [Option]

Output: properties


Input: [Description] The query timeout of database which stores log data when the option logProxy is database. [Option]

Output: queryTimeout


Input: [Description] Indicates should or not to use literal name for local variables. [Default value] true [Option]

Output: useLocalVariableName


Input: [Name] account_id [Description]

Output: id


Input: [Name] Name of the account owner [Description]

Output: name


Input: [Name] E-mail [Description]

Output: email


Input: [Name] Account balance [Description]

Output: balance


Input: [Name] Status of premium account [Description]

Output: premium


Input: [Name] Premium account start date [Description]

Output: premium start


Input: [Name] Premium account end date [Description]

Output: premium end


Input: [Align Bottom] Align Centers Horizontally [B] E

Output: Horizontally aligns the centers of the selected objects

Shortcut keys for CorelDRAW - Articles - Vectorboom