Display a string graphically.
Displays text by converting string into a texture. Invoke prepareToDrawInWindow() after changing properties like string, color and fontName
|
|
Property | x = 0 |
| | x-coordinate for the center of the text (degrees visual angle, centered in window)
|
| |
|
Property | y = 0 |
| | y-coordinate for the center of the text (degrees visual angle, centered in window)
|
| |
|
Property | string = '' |
| | string to render as graphical text
|
| |
|
Property | color = [255 255 255] |
| | [RGB] color of the displayed text
|
| |
|
Property | rotation = 0 |
| | degrees counterclockwise to rotate the entire text
|
| |
|
Property | isFlippedHorizontal = false |
| | wheter or not to flip the text horizontally
|
| |
|
Property | isFlippedVertical = false |
| | wheter or not to flip the text vertically
|
| |
|
Property | typefaceName = 'Helvetica' |
| | string name of the typeface to render
|
| |
|
Property | fontSize = 64 |
| | point size of the font to render
|
| |
|
Property | isBold = false |
| | whether or not to render the font in bold
|
| |
|
Property | isItalic = false |
| | whether or not to render the font with emphasis
|
| |
|
Property | isUnderline = false |
| | whether or not to render the font with an a line under it
|
| |
|
Property | isStrikethrough = false |
| | whether or not to render the font with a line through it
|
| |
|
Property | isVisible = true |
| | true or false, whether to draw() this object
|
| |
|
|
self | dotsDrawableText () |
| | Constructor takes no arguments.
|
| |
|
| set_typefaceName (self, typefaceName) |
| | Keep track of required texture updates.
|
| |
|
| set_fontSize (self, fontSize) |
| | Keep track of required texture updates.
|
| |
|
| set_color (self, color) |
| | Keep track of required texture updates.
|
| |
|
| set_isFlippedHorizontal (self, isFlippedHorizontal) |
| | Keep track of required texture updates.
|
| |
|
| set_isFlippedVertical (self, isFlippedVertical) |
| | Keep track of required texture updates.
|
| |
|
| set_isBold (self, isBold) |
| | Keep track of required texture updates.
|
| |
|
| set_isItalic (self, isItalic) |
| | Keep track of required texture updates.
|
| |
|
| set_isUnderline (self, isUnderline) |
| | Keep track of required texture updates.
|
| |
|
| set_isStrikethrough (self, isStrikethrough) |
| | Keep track of required texture updates.
|
| |
|
| set_string (self, string) |
| | Keep track of required texture updates.
|
| |
|
| prepareToDrawInWindow (self) |
| | Prepare the text texture to be drawn.
|
| |
|
| draw (self) |
| | Draw the text string, centered on x and y.
|
| |
|
self | dotsDrawable () |
| | Constructor takes no arguments.
|
| |
|
| prepareToDrawInWindow (self) |
| | Do any pre-draw setup that requires an OpenGL drawing window.
|
| |
|
| mayDrawNow (self) |
| | Draw() or not, depending on isVisible and possibly other factors.
|
| |
|
| draw (self) |
| | Subclass must redefine draw() to draw graphics.
|
| |
|
| show (self) |
| | Shorthand to set isVisible=true.
|
| |
|
| hide (self) |
| | Shorthand to set isVisible=false.
|
| |
|
| static ensemble | makeEnsemble (name, numTexts, spacing) |
| | function ensemble = makeEnsemble(name, num, yOffset) More...
|
| |
| static frameInfo | drawEnsemble (textEnsemble, textStrings, spacing, showDuration, pauseDuration) |
| | Utility to show text strings using the given ensemble. More...
|
| |
|
static | showText (text, varargin) |
| | Utility for showing text on the current screen.
|
| |
| static frameInfo | drawFrame (drawables, doClear) |
| | draw() several drawable objects and show the next Screen frame. More...
|
| |
| static ensemble | makeEnsemble (name, objects) |
| | Convenient utility for combining a bunch of drawables into an ensemble. More...
|
| |
| static frameInfo | drawEnsemble (ensemble, args, prepareFlag, showDuration, pauseDuration) |
| | Convenient utility for drawing an ensemble either locally or remotely. More...
|
| |


England centre Marchant to play for Blues on sabbatical
England centre Joe Marchant will join Super Rugby side Auckland Blues for a season as part of a sabbatical written into his three-year contract extension with Harlequins.
WELLINGTON: England centre Joe Marchant will join Super Rugby side Auckland Blues for a season as part of a sabbatical written into his three-year contract extension with Harlequins.
The highly-rated 23-year-old, who played in three of England’s warmup tests for the Rugby World Cup, will link up with the Blues between January and the end of June next year.
The arrangement bolsters the Blues' back-line options and covers the absence of Caleb Clarke, who was released to join New Zealand's rugby sevens programme in the leadup to the Tokyo Olympics.
"Firstly I could not be more grateful to Harlequins for allowing me this opportunity to expand and grow my game," Marchant said in a statement.
"The club has supported me every step of the way in my career to date and proven that Harlequins is still willing to support my growth as an individual.
"I am really excited to be given the chance to experience playing in Super Rugby. I am sure that I will learn a lot and I can’t wait to bring my learnings back to the club."
The twice-champion Blues finished bottom in the New Zealand conference and 13th in the 15-team Super Rugby competition in 2019 but head into next season with great expectations after signing All Blacks' superstar flyhalf Beauden Barrett on a long-term deal.
(Reporting by Ian Ransom in Melabourne; Editing by Richard Pullin)


| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The shell’s programmable completion mechanism can be manipulated in two ways; here the low-level features supporting the newer, function-based mechanism are defined. A complete set of shell functions based on these features is described in the next chapter, Completion System, and users with no interest in adding to that system (or, potentially, writing their own — see dictionary entry for ‘hubris’) should skip the current section. The older system based on the compctl builtin command is described in Completion Using compctl.
Completion widgets are defined by the -C option to the zle builtin command provided by the zsh/zle module (see The zsh/zle Module). For example,
zle -C complete expand-or-complete completer
defines a widget named ‘complete’. The second argument is the name of any of the builtin widgets that handle completions: complete-word, expand-or-complete, expand-or-complete-prefix, menu-complete, menu-expand-or-complete, reverse-menu-complete, list-choices, or delete-char-or-list. Note that this will still work even if the widget in question has been re-bound.
When this newly defined widget is bound to a key using the bindkey builtin command defined in the zsh/zle module (Zsh Line Editor), typing that key will call the shell function ‘completer’. This function is responsible for generating the possible matches using the builtins described below. As with other ZLE widgets, the function is called with its standard input closed.
Once the function returns, the completion code takes over control again and treats the matches in the same manner as the specified builtin widget, in this case expand-or-complete.
| 19.2 Completion Special Parameters | ||
| 19.3 Completion Builtin Commands | ||
| 19.4 Completion Condition Codes | ||
| 19.5 Completion Matching Control | ||
| 19.6 Completion Widget Example |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The parameters ZLE_REMOVE_SUFFIX_CHARS and ZLE_SPACE_SUFFIX_CHARS are used by the completion mechanism, but are not special. See Parameters Used By The Shell.
Inside completion widgets, and any functions called from them, some parameters have special meaning; outside these functions they are not special to the shell in any way. These parameters are used to pass information between the completion code and the completion widget. Some of the builtin commands and the condition codes use or change the current values of these parameters. Any existing values will be hidden during execution of completion widgets; except for compstate, the parameters are reset on each function exit (including nested function calls from within the completion widget) to the values they had when the function was entered.
This is the number of the current word, i.e. the word the cursor is currently on in the words array. Note that this value is only correct if the ksharrays option is not set.
Initially this will be set to the empty string. This parameter functions like PREFIX; it contains a string which precedes the one in PREFIX and is not considered part of the list of matches. Typically, a string is transferred from the beginning of PREFIX to the end of IPREFIX, for example:
IPREFIX=${PREFIX%%\=*}= PREFIX=${PREFIX#*=}
causes the part of the prefix up to and including the first equal sign not to be treated as part of a matched string. This can be done automatically by the compset builtin, see below.
As IPREFIX, but for a suffix that should not be considered part of the matches; note that the ISUFFIX string follows the SUFFIX string.
Initially this will be set to the part of the current word from the beginning of the word up to the position of the cursor; it may be altered to give a common prefix for all matches.
This parameter is read-only and contains the quoted string up to the word being completed. E.g. when completing ‘"foo’, this parameter contains the double quote. If the -q option of compset is used (see below), and the original string was ‘"foo bar’ with the cursor on the ‘bar’, this parameter contains ‘"foo ’.
Like QIPREFIX, but containing the suffix.
Initially this will be set to the part of the current word from the cursor position to the end; it may be altered to give a common suffix for all matches. It is most useful when the option COMPLETE_IN_WORD is set, as otherwise the whole word on the command line is treated as a prefix.
This is an associative array with various keys and values that the completion code uses to exchange information with the completion widget. The keys are:
The -q option of the compset builtin command (see below) allows a quoted string to be broken into separate words; if the cursor is on one of those words, that word will be completed, possibly invoking ‘compset -q’ recursively. With this key it is possible to test the types of quoted strings which are currently broken into parts in this fashion. Its value contains one character for each quoting level. The characters are a single quote or a double quote for strings quoted with these characters, a dollars sign for strings quoted with $’...’ and a backslash for strings not starting with a quote character. The first character in the value always corresponds to the innermost quoting level.
This will be set by the completion code to the overall context in which completion is attempted. Possible values are:
when completing inside the value of an array parameter assignment; in this case the words array contains the words inside the parentheses.
when completing the name of a parameter in a parameter expansion beginning with ${. This context will also be set when completing parameter flags following ${(; the full command line argument is presented and the handler must test the value to be completed to ascertain that this is the case.
when completing the name of a parameter in a parameter assignment.
when completing for a normal command (either in command position or for an argument of the command).
when completing inside a ‘[[...]]’ conditional expression; in this case the words array contains only the words inside the conditional expression.
when completing in a mathematical environment such as a ‘((...))’ construct.
when completing the name of a parameter in a parameter expansion beginning with $ but not ${.
when completing after a redirection operator.
when completing inside a parameter subscript.
when completing the value of a parameter assignment.
Controls the behaviour when the REC_EXACT option is set. It will be set to accept if an exact match would be accepted, and will be unset otherwise.
If it was set when at least one match equal to the string on the line was generated, the match is accepted.
The string of an exact match if one was found, otherwise unset.
The number of words that were ignored because they matched one of the patterns given with the -F option to the compadd builtin command.
This controls the manner in which a match is inserted into the command line. On entry to the widget function, if it is unset the command line is not to be changed; if set to unambiguous, any prefix common to all matches is to be inserted; if set to automenu-unambiguous, the common prefix is to be inserted and the next invocation of the completion code may start menu completion (due to the AUTO_MENU option being set); if set to menu or automenu menu completion will be started for the matches currently generated (in the latter case this will happen because the AUTO_MENU is set). The value may also contain the string ‘tab’ when the completion code would normally not really do completion, but only insert the TAB character.
On exit it may be set to any of the values above (where setting it to the empty string is the same as unsetting it), or to a number, in which case the match whose number is given will be inserted into the command line. Negative numbers count backward from the last match (with ‘-1’ selecting the last match) and out-of-range values are wrapped around, so that a value of zero selects the last match and a value one more than the maximum selects the first. Unless the value of this key ends in a space, the match is inserted as in a menu completion, i.e. without automatically appending a space.
Both menu and automenu may also specify the number of the match to insert, given after a colon. For example, ‘menu:2’ says to start menu completion, beginning with the second match.
Note that a value containing the substring ‘tab’ makes the matches generated be ignored and only the TAB be inserted.
Finally, it may also be set to all, which makes all matches generated be inserted into the line.
When the completion system inserts an unambiguous string into the line, there may be multiple places where characters are missing or where the character inserted differs from at least one match. The value of this key contains a colon separated list of all these positions, as indexes into the command line.
If this is set to a non-empty string for every match added, the completion code will move the cursor back to the previous prompt after the list of completions has been displayed. Initially this is set or unset according to the ALWAYS_LAST_PROMPT option.
This controls whether or how the list of matches will be displayed. If it is unset or empty they will never be listed; if its value begins with list, they will always be listed; if it begins with autolist or ambiguous, they will be listed when the AUTO_LIST or LIST_AMBIGUOUS options respectively would normally cause them to be.
If the substring force appears in the value, this makes the list be shown even if there is only one match. Normally, the list would be shown only if there are at least two matches.
The value contains the substring packed if the LIST_PACKED option is set. If this substring is given for all matches added to a group, this group will show the LIST_PACKED behavior. The same is done for the LIST_ROWS_FIRST option with the substring rows.
Finally, if the value contains the string explanations, only the explanation strings, if any, will be listed and if it contains messages, only the messages (added with the -x option of compadd) will be listed. If it contains both explanations and messages both kinds of explanation strings will be listed. It will be set appropriately on entry to a completion widget and may be changed there.
This gives the number of lines that are needed to display the full list of completions. Note that to calculate the total number of lines to display you need to add the number of lines needed for the command line to this value, this is available as the value of the BUFFERLINES special parameter.
Initially this is set to the value of the LISTMAX parameter. It may be set to any other value; when the widget exits this value will be used in the same way as the value of LISTMAX.
The number of matches generated and accepted by the completion code so far.
On entry to the widget this will be set to the number of the match of an old list of completions that is currently inserted into the command line. If no match has been inserted, this is unset.
As with old_list, the value of this key will only be used if it is the string keep. If it was set to this value by the widget and there was an old match inserted into the command line, this match will be kept and if the value of the insert key specifies that another match should be inserted, this will be inserted after the old one.
This is set to yes if there is still a valid list of completions from a previous completion at the time the widget is invoked. This will usually be the case if and only if the previous editing operation was a completion widget or one of the builtin completion functions. If there is a valid list and it is also currently shown on the screen, the value of this key is shown.
After the widget has exited the value of this key is only used if it was set to keep. In this case the completion code will continue to use this old list. If the widget generated new matches, they will not be used.
The name of the parameter when completing in a subscript or in the value of a parameter assignment.
Normally this is set to menu, which specifies that menu completion will be used whenever a set of matches was generated using pattern matching. If it is set to any other non-empty string by the user and menu completion is not selected by other option settings, the code will instead insert any common prefix for the generated matches as with normal completion.
Locally controls the behaviour given by the GLOB_COMPLETE option. Initially it is set to ‘*’ if and only if the option is set. The completion widget may set it to this value, to an empty string (which has the same effect as unsetting it), or to any other non-empty string. If it is non-empty, unquoted metacharacters on the command line will be treated as patterns; if it is ‘*’, then additionally a wildcard ‘*’ is assumed at the cursor position; if it is empty or unset, metacharacters will be treated literally.
Note that the matcher specifications given to the compadd builtin command are not used if this is set to a non-empty string.
When completing inside quotes, this contains the quotation character (i.e. either a single quote, a double quote, or a backtick). Otherwise it is unset.
When completing inside single quotes, this is set to the string single; inside double quotes, the string double; inside backticks, the string backtick. Otherwise it is unset.
The redirection operator when completing in a redirection position, i.e. one of <, >, etc.
This is set to auto before a function is entered, which forces the special parameters mentioned above (words, CURRENT, PREFIX, IPREFIX, SUFFIX, and ISUFFIX) to be restored to their previous values when the function exits. If a function unsets it or sets it to any other string, they will not be restored.
Specifies the occasions on which the cursor is moved to the end of a string when a match is inserted. On entry to a widget function, it may be single if this will happen when a single unambiguous match was inserted or match if it will happen any time a match is inserted (for example, by menu completion; this is likely to be the effect of the ALWAYS_TO_END option).
On exit, it may be set to single as above. It may also be set to always, or to the empty string or unset; in those cases the cursor will be moved to the end of the string always or never respectively. Any other string is treated as match.
This key is read-only and will always be set to the common (unambiguous) prefix the completion code has generated for all matches added so far.
This gives the position the cursor would be placed at if the common prefix in the unambiguous key were inserted, relative to the value of that key. The cursor would be placed before the character whose index is given by this key.
This contains all positions where characters in the unambiguous string are missing or where the character inserted differs from at least one of the matches. The positions are given as indexes into the string given by the value of the unambiguous key.
If completion is called while editing a line using the vared builtin, the value of this key is set to the name of the parameter given as an argument to vared. This key is only set while a vared command is active.
This array contains the words present on the command line currently being edited.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This builtin command can be used to add matches directly and control all the information the completion code stores with each possible match. The return status is zero if at least one match was added and non-zero if no matches were added.
The completion code breaks the string to complete into seven fields in the order:
<ipre><apre><hpre><word><hsuf><asuf><isuf>
The first field is an ignored prefix taken from the command line, the contents of the IPREFIX parameter plus the string given with the -i option. With the -U option, only the string from the -i option is used. The field <apre> is an optional prefix string given with the -P option. The <hpre> field is a string that is considered part of the match but that should not be shown when listing completions, given with the -p option; for example, functions that do filename generation might specify a common path prefix this way. <word> is the part of the match that should appear in the list of completions, i.e. one of the words given at the end of the compadd command line. The suffixes <hsuf>, <asuf> and <isuf> correspond to the prefixes <hpre>, <apre> and <ipre> and are given by the options -s, -S and -I, respectively.
The supported flags are:
This gives a string to be inserted before the given words. The string given is not considered as part of the match and any shell metacharacters in it will not be quoted when the string is inserted.
Like -P, but gives a string to be inserted after the match.
This gives a string that should be inserted into the command line before the match but that should not appear in the list of matches. Unless the -U option is given, this string must be matched as part of the string on the command line.
Like ‘-p’, but gives a string to insert after the match.
This gives a string to insert into the command line just before any string given with the ‘-P’ option. Without ‘-P’ the string is inserted before the string given with ‘-p’ or directly before the match.
Like -i, but gives an ignored suffix.
With this flag the words are taken as names of arrays and the possible matches are their values. If only some elements of the arrays are needed, the words may also contain subscripts, as in ‘foo[2,-1]’.
With this flag the words are taken as names of associative arrays and the possible matches are their keys. As for -a, the words may also contain subscripts, as in ‘foo[(R)*bar*]’.
This adds per-match display strings. The array should contain one element per word given. The completion code will then display the first element instead of the first word, and so on. The array may be given as the name of an array parameter or directly as a space-separated list of words in parentheses.
If there are fewer display strings than words, the leftover words will be displayed unchanged and if there are more display strings than words, the leftover display strings will be silently ignored.
This option only has an effect if used together with the -d option. If it is given, the display strings are listed one per line, not arrayed in columns.
This option only has an effect if used together with the -d option. If it is given, the order of the output is determined by the match strings; otherwise it is determined by the display strings (i.e. the strings given by the -d option).
Gives the name of the group of matches the words should be stored in.
Like -J but naming an unsorted group. These are in a different name space than groups created with the -J flag.
If given together with the -V option, makes only consecutive duplicates in the group be removed. If combined with the -J option, this has no visible effect. Note that groups with and without this flag are in different name spaces.
If given together with the -J or -V option, makes all duplicates be kept. Again, groups with and without this flag are in different name spaces.
The explanation string will be printed with the list of matches, above the group currently selected.
Like -X, but the message will be printed even if there are no matches in the group.
The suffix given with -S will be automatically removed if the next character typed is a blank or does not insert anything, or if the suffix consists of only one character and the next character typed is the same character.
This is a more versatile form of the -q option. The suffix given with -S or the slash automatically added after completing directories will be automatically removed if the next character typed inserts one of the characters given in the remove-chars. This string is parsed as a characters class and understands the backslash sequences used by the print command. For example, ‘-r "a-z\t"’ removes the suffix if the next character typed inserts a lower case character or a TAB, and ‘-r "^0-9"’ removes the suffix if the next character typed inserts anything but a digit. One extra backslash sequence is understood in this string: ‘\-’ stands for all characters that insert nothing. Thus ‘-S "=" -q’ is the same as ‘-S "=" -r "= \t\n\-"’.
This option may also be used without the -S option; then any automatically added space will be removed when one of the characters in the list is typed.
This is another form of the -r option. When a suffix has been inserted and the completion accepted, the function remove-func will be called after the next character typed. It is passed the length of the suffix as an argument and can use the special parameters available in ordinary (non-completion) zle widgets (see Zsh Line Editor) to analyse and modify the command line.
If this flag is given, all of the matches built from words are marked as being the names of files. They are not required to be actual filenames, but if they are, and the option LIST_TYPES is set, the characters describing the types of the files in the completion lists will be shown. This also forces a slash to be added when the name of a directory is completed.
This flag can be used to tell the completion code that the matches added are parameter names for a parameter expansion. This will make the AUTO_PARAM_SLASH and AUTO_PARAM_KEYS options be used for the matches.
This string is a pathname that will be prepended to each of the matches formed by the given words together with any prefix specified by the -p option to form a complete filename for testing. Hence it is only useful if combined with the -f flag, as the tests will not otherwise be performed.
Specifies an array containing patterns. Words matching one of these patterns are ignored, i.e. not considered to be possible matches.
The array may be the name of an array parameter or a list of literal patterns enclosed in parentheses and quoted, as in ‘-F "(*?.o *?.h)"’. If the name of an array is given, the elements of the array are taken as the patterns.
This flag instructs the completion code not to quote any metacharacters in the words when inserting them into the command line.
This gives local match specifications as described below in Completion Matching Control. This option may be given more than once. In this case all match-specs given are concatenated with spaces between them to form the specification string to use. Note that they will only be used if the -U option is not given.
Specifies that the words added are to be used as possible matches, but are not to appear in the completion listing.
If this flag is given, all words given will be accepted and no matching will be done by the completion code. Normally this is used in functions that do the matching themselves.
If this option is given, the words are not added to the set of possible completions. Instead, matching is done as usual and all of the words given as arguments that match the string on the command line will be stored in the array parameter whose name is given as array.
As the -O option, except that instead of those of the words which match being stored in array, the strings generated internally by the completion code are stored. For example, with a matching specification of ‘-M "L:|no="’, the string ‘nof’ on the command line and the string ‘foo’ as one of the words, this option stores the string ‘nofoo’ in the array, whereas the -O option stores the ‘foo’ originally given.
As with -O, the words are not added to the set of possible completions. Instead, the completion code tests whether each word in turn matches what is on the line. If the nth word does not match, the nth element of the array is removed. Elements for which the corresponding word is matched are retained.
This option adds a special match which expands to all other matches when inserted into the line, even those that are added after this option is used. Together with the -d option it is possible to specify a string that should be displayed in the list for this special match. If no string is given, it will be shown as a string containing the strings that would be inserted for the other matches, truncated to the width of the screen.
This option adds number empty matches after the words have been added. An empty match takes up space in completion listings but will never be inserted in the line and can’t be selected with menu completion or menu selection. This makes empty matches only useful to format completion lists and to make explanatory string be shown in completion lists (since empty matches can be given display strings with the -d option). And because all but one empty string would otherwise be removed, this option implies the -V and -2 options (even if an explicit -J option is given). This can be important to note as it affects the name space into which matches are added.
This flag ends the list of flags and options. All arguments after it will be taken as the words to use as matches even if they begin with hyphens.
Except for the -M flag, if any of these flags is given more than once, the first one (and its argument) will be used.
This command simplifies modification of the special parameters, while its return status allows tests on them to be carried out.
The options are:
If the contents of the PREFIX parameter is longer than number characters, the first number characters are removed from it and appended to the contents of the IPREFIX parameter.
If the value of the PREFIX parameter begins with anything that matches the pattern, the matched portion is removed from PREFIX and appended to IPREFIX.
Without the optional number, the longest match is taken, but if number is given, anything up to the numberth match is moved. If the number is negative, the numberth longest match is moved. For example, if PREFIX contains the string ‘a=b=c’, then compset -P ’*\=’ will move the string ‘a=b=’ into the IPREFIX parameter, but compset -P 1 ’*\=’ will move only the string ‘a=’.
As -p, but transfer the last number characters from the value of SUFFIX to the front of the value of ISUFFIX.
As -P, but match the last portion of SUFFIX and transfer the matched portion to the front of the value of ISUFFIX.
If the current word position as specified by the parameter CURRENT is greater than or equal to begin, anything up to the beginth word is removed from the words array and the value of the parameter CURRENT is decremented by begin.
If the optional end is given, the modification is done only if the current word position is also less than or equal to end. In this case, the words from position end onwards are also removed from the words array.
Both begin and end may be negative to count backwards from the last element of the words array.
If one of the elements of the words array before the one at the index given by the value of the parameter CURRENT matches the pattern beg-pat, all elements up to and including the matching one are removed from the words array and the value of CURRENT is changed to point to the same word in the changed array.
If the optional pattern end-pat is also given, and there is an element in the words array matching this pattern, the parameters are modified only if the index of this word is higher than the one given by the CURRENT parameter (so that the matching word has to be after the cursor). In this case, the words starting with the one matching end-pat are also removed from the words array. If words contains no word matching end-pat, the testing and modification is performed as if it were not given.
The word currently being completed is split on spaces into separate words, respecting the usual shell quoting conventions. The resulting words are stored in the words array, and CURRENT, PREFIX, SUFFIX, QIPREFIX, and QISUFFIX are modified to reflect the word part that is completed.
In all the above cases the return status is zero if the test succeeded and the parameters were modified and non-zero otherwise. This allows one to use this builtin in tests such as:
if compset -P '*\='; then ...
This forces anything up to and including the last equal sign to be ignored by the completion code.
This allows the use of completions defined with the compctl builtin from within completion widgets. The list of matches will be generated as if one of the non-widget completion functions (complete-word, etc.) had been called, except that only compctls given for specific commands are used. To force the code to try completions defined with the -T option of compctl and/or the default completion (whether defined by compctl -D or the builtin default) in the appropriate places, the -T and/or -D flags can be passed to compcall.
The return status can be used to test if a matching compctl definition was found. It is non-zero if a compctl was found and zero otherwise.
Note that this builtin is defined by the zsh/compctl module.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following additional condition codes for use within the [[ ... ]] construct are available in completion widgets. These work on the special parameters. All of these tests can also be performed by the compset builtin, but in the case of the condition codes the contents of the special parameters are not modified.
true if the test for the -P option of compset would succeed.
true if the test for the -S option of compset would succeed.
true if the test of the -N option with only the beg-pat given would succeed.
true if the test for the -N option with both patterns would succeed.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
It is possible by use of the -M option of the compadd builtin command to specify how the characters in the string to be completed (referred to here as the command line) map onto the characters in the list of matches produced by the completion code (referred to here as the trial completions). Note that this is not used if the command line contains a glob pattern and the GLOB_COMPLETE option is set or the pattern_match of the compstate special association is set to a non-empty string.
The match-spec given as the argument to the -M option (see Completion Builtin Commands) consists of one or more matching descriptions separated by whitespace. Each description consists of a letter followed by a colon and then the patterns describing which character sequences on the line match which character sequences in the trial completion. Any sequence of characters not handled in this fashion must match exactly, as usual.
The forms of match-spec understood are as follows. In each case, the form with an upper case initial character retains the string already typed on the command line as the final result of completion, while with a lower case initial character the string on the command line is changed into the corresponding part of the trial completion.
Here, lpat is a pattern that matches on the command line, corresponding to tpat which matches in the trial completion.
These letters are for patterns that are anchored by another pattern on the left side. Matching for lpat and tpat is as for m and M, but the pattern lpat matched on the command line must be preceded by the pattern lanchor. The lanchor can be blank to anchor the match to the start of the command line string; otherwise the anchor can occur anywhere, but must match in both the command line and trial completion strings.
If no lpat is given but a ranchor is, this matches the gap between substrings matched by lanchor and ranchor. Unlike lanchor, the ranchor only needs to match the trial completion string.
The b and B forms are similar to l and L with an empty anchor, but need to match only the beginning of the word on the command line or trial completion, respectively.
As l, L, b and B, with the difference that the command line and trial completion patterns are anchored on the right side. Here an empty ranchor and the e and E forms force the match to the end of the command line or trial completion string.
This form is used to mark the end of matching specifications: subsequent specifications are ignored. In a single standalone list of specifications this has no use but where matching specifications are accumulated, such as from nested function calls, it can allow one function to override another.
Each lpat, tpat or anchor is either an empty string or consists of a sequence of literal characters (which may be quoted with a backslash), question marks, character classes, and correspondence classes; ordinary shell patterns are not used. Literal characters match only themselves, question marks match any character, and character classes are formed as for globbing and match any character in the given set.
Correspondence classes are defined like character classes, but with two differences: they are delimited by a pair of braces, and negated classes are not allowed, so the characters ! and ^ have no special meaning directly after the opening brace. They indicate that a range of characters on the line match a range of characters in the trial completion, but (unlike ordinary character classes) paired according to the corresponding position in the sequence. For example, to make any ASCII lower case letter on the line match the corresponding upper case letter in the trial completion, you can use ‘m:{a-z}={A-Z}’ (however, see below for the recommended form for this). More than one pair of classes can occur, in which case the first class before the = corresponds to the first after it, and so on. If one side has more such classes than the other side, the superfluous classes behave like normal character classes. In anchor patterns correspondence classes also behave like normal character classes.
The standard ‘[:name:]’ forms described for standard shell patterns (see Filename Generation) may appear in correspondence classes as well as normal character classes. The only special behaviour in correspondence classes is if the form on the left and the form on the right are each one of [:upper:], [:lower:]. In these cases the character in the word and the character on the line must be the same up to a difference in case. Hence to make any lower case character on the line match the corresponding upper case character in the trial completion you can use ‘m:{[:lower:]}={[:upper:]}’. Although the matching system does not yet handle multibyte characters, this is likely to be a future extension, at which point this syntax will handle arbitrary alphabets; hence this form, rather than the use of explicit ranges, is the recommended form. In other cases ‘[:name:]’ forms are allowed. If the two forms on the left and right are the same, the characters must match exactly. In remaining cases, the corresponding tests are applied to both characters, but they are not otherwise constrained; any matching character in one set goes with any matching character in the other set: this is equivalent to the behaviour of ordinary character classes.
The pattern tpat may also be one or two stars, ‘*’ or ‘**’. This means that the pattern on the command line can match any number of characters in the trial completion. In this case the pattern must be anchored (on either side); in the case of a single star, the anchor then determines how much of the trial completion is to be included — only the characters up to the next appearance of the anchor will be matched. With two stars, substrings matched by the anchor can be matched, too.
Examples:
The keys of the options association defined by the parameter module are the option names in all-lower-case form, without underscores, and without the optional no at the beginning even though the builtins setopt and unsetopt understand option names with upper case letters, underscores, and the optional no. The following alters the matching rules so that the prefix no and any underscore are ignored when trying to match the trial completions generated and upper case letters on the line match the corresponding lower case letters in the words:
compadd -M 'L:|[nN][oO]= M:_= M:{[:upper:]}={[:lower:]}' - \ ${(k)options}
The first part says that the pattern ‘[nN][oO]’ at the beginning (the empty anchor before the pipe symbol) of the string on the line matches the empty string in the list of words generated by completion, so it will be ignored if present. The second part does the same for an underscore anywhere in the command line string, and the third part uses correspondence classes so that any upper case letter on the line matches the corresponding lower case letter in the word. The use of the upper case forms of the specification characters (L and M) guarantees that what has already been typed on the command line (in particular the prefix no) will not be deleted.
Note that the use of L in the first part means that it matches only when at the beginning of both the command line string and the trial completion. I.e., the string ‘_NO_f’ would not be completed to ‘_NO_foo’, nor would ‘NONO_f’ be completed to ‘NONO_foo’ because of the leading underscore or the second ‘NO’ on the line which makes the pattern fail even though they are otherwise ignored. To fix this, one would use ‘B:[nN][oO]=’ instead of the first part. As described above, this matches at the beginning of the trial completion, independent of other characters or substrings at the beginning of the command line word which are ignored by the same or other match-specs.
The second example makes completion case insensitive. This is just the same as in the option example, except here we wish to retain the characters in the list of completions:
compadd -M 'm:{[:lower:]}={[:upper:]}' ...
This makes lower case letters match their upper case counterparts. To make upper case letters match the lower case forms as well:
compadd -M 'm:{[:lower:][:upper:]}={[:upper:][:lower:]}' ...
A nice example for the use of * patterns is partial word completion. Sometimes you would like to make strings like ‘c.s.u’ complete to strings like ‘comp.source.unix’, i.e. the word on the command line consists of multiple parts, separated by a dot in this example, where each part should be completed separately — note, however, that the case where each part of the word, i.e. ‘comp’, ‘source’ and ‘unix’ in this example, is to be completed from separate sets of matches is a different problem to be solved by the implementation of the completion widget. The example can be handled by:
compadd -M 'r:|.=* r:|=*' \ - comp.sources.unix comp.sources.misc ...
The first specification says that lpat is the empty string, while anchor is a dot; tpat is *, so this can match anything except for the ‘.’ from the anchor in the trial completion word. So in ‘c.s.u’, the matcher sees ‘c’, followed by the empty string, followed by the anchor ‘.’, and likewise for the second dot, and replaces the empty strings before the anchors, giving ‘c[omp].s[ources].u[nix]’, where the last part of the completion is just as normal.
With the pattern shown above, the string ‘c.u’ could not be completed to ‘comp.sources.unix’ because the single star means that no dot (matched by the anchor) can be skipped. By using two stars as in ‘r:|.=**’, however, ‘c.u’ could be completed to ‘comp.sources.unix’. This also shows that in some cases, especially if the anchor is a real pattern, like a character class, the form with two stars may result in more matches than one would like.
The second specification is needed to make this work when the cursor is in the middle of the string on the command line and the option COMPLETE_IN_WORD is set. In this case the completion code would normally try to match trial completions that end with the string as typed so far, i.e. it will only insert new characters at the cursor position rather than at the end. However in our example we would like the code to recognise matches which contain extra characters after the string on the line (the ‘nix’ in the example). Hence we say that the empty string at the end of the string on the line matches any characters at the end of the trial completion.
More generally, the specification
compadd -M 'r:|[.,_-]=* r:|=*' ...
allows one to complete words with abbreviations before any of the characters in the square brackets. For example, to complete veryverylongfile.c rather than veryverylongheader.h with the above in effect, you can just type very.c before attempting completion.
The specifications with both a left and a right anchor are useful to complete partial words whose parts are not separated by some special character. For example, in some places strings have to be completed that are formed ‘LikeThis’ (i.e. the separate parts are determined by a leading upper case letter) or maybe one has to complete strings with trailing numbers. Here one could use the simple form with only one anchor as in:
compadd -M 'r:|[[:upper:]0-9]=* r:|=*' LikeTHIS FooHoo 5foo123 5bar234
But with this, the string ‘H’ would neither complete to ‘FooHoo’ nor to ‘LikeTHIS’ because in each case there is an upper case letter before the ‘H’ and that is matched by the anchor. Likewise, a ‘2’ would not be completed. In both cases this could be changed by using ‘r:|[[:upper:]0-9]=**’, but then ‘H’ completes to both ‘LikeTHIS’ and ‘FooHoo’ and a ‘2’ matches the other strings because characters can be inserted before every upper case letter and digit. To avoid this one would use:
compadd -M 'r:[^[:upper:]0-9]||[[:upper:]0-9]=** r:|=*' \ LikeTHIS FooHoo foo123 bar234
By using these two anchors, a ‘H’ matches only upper case ‘H’s that are immediately preceded by something matching the left anchor ‘[^[:upper:]0-9]’. The effect is, of course, that ‘H’ matches only the string ‘FooHoo’, a ‘2’ matches only ‘bar234’ and so on.
When using the completion system (see Completion System), users can define match specifications that are to be used for specific contexts by using the matcher and matcher-list styles. The values for the latter will be used everywhere.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The first step is to define the widget:
zle -C complete complete-word complete-files
Then the widget can be bound to a key using the bindkey builtin command:
bindkey '^X\t' complete
After that the shell function complete-files will be invoked after typing control-X and TAB. The function should then generate the matches, e.g.:
complete-files () { compadd - * }
This function will complete files in the current directory matching the current word.
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated on April 26, 2019 using texi2html 5.0.
Zsh version 5.7.1, released on February 3, 2019.


Specify a complete Hastic Server HTTP URL (for example http://your_hastic_server:8000)
Your access method is Browser, this means the URL needs to be accessible from the browser. Your access method is Server, this means the URL needs to be accessible from the grafana backend/server.Access mode controls how requests to the data source will be handled. Server access mode should be the preferred way if nothing else stated.
All requests will be made from the browser to Grafana backend/server which in turn will forward the requests to the data source and by that circumvent possible Cross-Origin Resource Sharing (CORS) requirements. The URL needs to be accessible from the grafana backend/server if you select this access mode.
All requests will be made from the browser directly to the data source and may be subject to Cross-Origin Resource Sharing (CORS) requirements. The URL needs to be accessible from the browser if you select this access mode.


- Vagrant - Class in eu.shooktea.vmsm.vmtype
-
Representation of Vagrant type of virtual machine.
- valueOf(String) - Static method in enum eu.shooktea.vmsm.module.mage.Magento.DeleteDir
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum eu.shooktea.vmsm.module.mage.Report.HoldTime
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum eu.shooktea.vmsm.Status
-
Returns the enum constant of this type with the specified name.
- values() - Static method in enum eu.shooktea.vmsm.module.mage.Magento.DeleteDir
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum eu.shooktea.vmsm.module.mage.Report.HoldTime
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum eu.shooktea.vmsm.Status
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- View - Class in eu.shooktea.vmsm.view
-
Singleton class managing displayed screens.
- VirtualMachine - Class in eu.shooktea.vmsm
-
Single virtual machine with HTTP server on it.
- VirtualMachine(String, File, URL, VMType) - Constructor for class eu.shooktea.vmsm.VirtualMachine
-
Main constructor for virtual machine.
- VM - Class in eu.shooktea.vmsm
-
Singleton object for keeping currently displayed virtual machine.
- VM.VmChangeListener - Interface in eu.shooktea.vmsm
-
This listener is called whenever virtual machine to be displayed is changed.
- VM.VmEmptyListener - Interface in eu.shooktea.vmsm
-
This listener is called whenever virtual machine to be displayed is changed.
- VM.VmUpdateListener - Interface in eu.shooktea.vmsm
-
This listener is called whenever virtual machine to be displayed is changed.
- vmChanged(VirtualMachine, VirtualMachine) - Method in interface eu.shooktea.vmsm.VM.VmChangeListener
-
- vmConsume() - Method in interface eu.shooktea.vmsm.VM.VmEmptyListener
-
- VMModule - Class in eu.shooktea.vmsm.module
-
Abstract class representing single module.
- VMModule() - Constructor for class eu.shooktea.vmsm.module.VMModule
-
Main constructor of VMModule.
- VMType - Class in eu.shooktea.vmsm.vmtype
-
Representation of type of virtual machine.
- vmUpdated(VirtualMachine) - Method in interface eu.shooktea.vmsm.VM.VmUpdateListener
-


Contracting parties: 48 total- Albania, Algeria, Angola, Barbados, Belize, Brasil, Canada, Cap-Vert, China, Cote d’Ivoire, Croatia, Equatorial Guinea, Egypt, EU, France (St-Pierre et Miquelon), Gabon, Ghana, Guatemala, Guinee Rep, Honduras, Iceland, Japan, Korea (Republic of), Libya, Maroc, Mauritania, Mexico, Namibia, Nicaragua, Nigeria, Norway, Panama, Philippines, Russia, Sao Tome E Principe, Senegal, Sierra Leone, South Africa, Syria, St. Vincent & the Grenadines, Trinidad & Tobago, Tunisia, Turkey, UK, USA, Uruguay, Vanuatu, Venezuela.
Area: Atlantic Ocean and adjacent seas.
Date entered into force: 1969.
FAO association: No.
FAO statistical area: 41, 47, 48, 31, 34, 21, 27.
Objectives: “…conservation of tunas and tuna-like species in the Atlantic Ocean and adjacent seas.”

The x-axes on the figures below represent either current biomass (B2006 or B2005) or current spawning stock biomass (SSB2005) over either biomass at maximum sustainable yield (Bmsy) or spawning stock biomass at maximum sustainable yield (SSBmsy). The y-axes represent current fishing mortality (F2006 or F2005) over fishing mortality that produces maximum sustainable yield (Fmsy). Shown below, are stocks: a) Bluefin tuna (west Atlantic stock); b) Bluefin tuna (east Atlantic stock); c) Yellowfin tuna; d) Skipjack tuna (east Atlantic stock); e) Skipjack tuna (west Atlantic stock); f) Bigeye tuna; g) Albacore tuna (south Atlantic stock); h) Albacore tuna (north Atlantic stock). For data sources, see Cullis-Suzuki and Pauly (2009).
The figures below show time series of biomass of the nine major tuna stocks under ICCAT management; the red dashed line denotes the date ICCAT was established (1969). Species shown below, are: a) Bluefin tuna (west Atlantic stock); b) Bluefin tuna (east Atlantic stock); c) Yellowfin tuna; d) Skipjack tuna (east Atlantic stock); e) Skipjack tuna (west Atlantic stock); f) Bigeye tuna; g) Albacore tuna (south Atlantic stock); h) Albacore tuna (north Atlantic stock). For data sources see Cullis-Suzuki and Pauly (2009).
|
a) |
b) |
c) |
|
d) |
e) |
f) |
|
h) |
i) |
|
|
|


Macropedia Imperium
Help Me Pick New Logo Through 3 April 2016!
I am in the process of running a logo design contest on 99designs and have created a poll with 6 of the best logo designs I've received. I would love for you to vote on the logo design. It only takes a minute.
Like Sci-Fi? Read My New Online Fiction Series.
Do you like Sci-Fi? While I finish up my next novel, I have started an online fiction series called Forbearance. Picking up from the canteen scene in Bellicose, we meet Keius Minjen, a postal marine, as he tries to survive the battle planet Guna to exact revenge and one day liberate his homeland.
Sign-up if you want me to send you news about upcoming installments of Forbearance or my other writings.
Macropedia/Macropedia Terradoma, Imperium Edition began before the end of the Imperium. The Last Emperor hoped the scholars he chose would document the many successes of the Imperium and solidify both his and the dynasty’s legacy. However, he passed heirless, and the “death spiral” to the Second Decline began. The scholars chose to write as Scholars and not necessarily as puppets of the last dynasty of the Imperium.
Recent Changes (since flagging macropedia for edit/publication).
Here is a sketchy timeline of events within this Lexicon.


Class: Aws::IoTFleetWise::Types::CanSignal
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Struct
|
|
|
Instance Chain:
self,
::Aws::Structure ,
Struct
|
|
| Inherits: |
Struct
|
| Defined in: | gems/aws-sdk-iotfleetwise/lib/aws-sdk-iotfleetwise/types.rb |
Overview
Information about a single controller area network (CAN) signal and the messages it receives and transmits.
Constant Summary
Instance Attribute Summary
-
#factor ⇒ Float
rw
A multiplier used to decode the CAN message.
-
#is_big_endian ⇒ Boolean
rw
Whether the byte ordering of a CAN message is big-endian.
-
#is_signed ⇒ Boolean
rw
Whether the message data is specified as a signed value.
-
#length ⇒ Integer
rw
How many bytes of data are in the message.
-
#message_id ⇒ Integer
rw
The ID of the message.
-
#name ⇒ String
rw
The name of the signal.
-
#offset ⇒ Float
rw
The offset used to calculate the signal value.
-
#start_bit ⇒ Integer
rw
Indicates the beginning of the CAN signal.
Instance Method Summary
::Aws::Structure
- Included
| #to_hash | Alias for Structure#to_h. |
Instance Attribute Details
#factor ⇒ Float
(rw)
A multiplier used to decode the CAN message.
#is_big_endian ⇒ Boolean
(rw)
Whether the byte ordering of a CAN message is big-endian.
#is_signed ⇒ Boolean
(rw)
Whether the message data is specified as a signed value.
#length ⇒ Integer
(rw)
How many bytes of data are in the message.
#message_id ⇒ Integer
(rw)
The ID of the message.
#name ⇒ String
(rw)
The name of the signal.
#offset ⇒ Float
(rw)
The offset used to calculate the signal value. Combined with factor,
the calculation is value = raw_value * factor + offset
.
#start_bit ⇒ Integer
(rw)
Indicates the beginning of the CAN signal. This should always be the least significant bit (LSB).
This value might be different from the value in a DBC file. For
little endian signals, startBit
is the same value as in the DBC
file. For big endian signals in a DBC file, the start bit is the
most significant bit (MSB). You will have to calculate the LSB
instead and pass it as the startBit
.


Ghost of Adventurer:
If you hit the well, the spirits will come out.
While you are fighting with the spirits, I will break the seal of the hidden report in the well
Just, don't kill the spirit while I'm working. Because they will come back to the well if they die.
If I break the seal, the color of the jewelry will change.  You got it?
"I am not sure"
"I see"


|
BitShares-Core
6.1.0
BitShares blockchain implementation and command-line interface software
|
Go to the source code of this file.
Classes | |
| struct | graphene::db::object_id_type |
| struct | graphene::db::object_downcast< ObjectID > |
| This template is used to downcast a generic object type to a specific xyz_object type. More... | |
| struct | graphene::db::object_id< SpaceID, TypeID > |
| struct | fc::get_typename< graphene::db::object_id< SpaceID, TypeID > > |
| struct | fc::reflector< graphene::db::object_id< SpaceID, TypeID > > |
| struct | fc::member_names::member_name< graphene::db::object_id< S, T >, 0 > |
| struct | std::hash< graphene::db::object_id_type > |
Namespaces | |
| graphene | |
| graphene::db | |
| fc | |
| fc::member_names | |
| std | |
Macros | |
| #define | MAP_OBJECT_ID_TO_TYPE(OBJECT) |
Typedefs | |
| template<typename ObjectID > | |
| using | graphene::db::object_downcast_t = typename object_downcast< ObjectID >::type |
Functions | |
| void | fc::to_variant (const graphene::db::object_id_type &var, fc::variant &vo, uint32_t max_depth=1) |
| void | fc::from_variant (const fc::variant &var, graphene::db::object_id_type &vo, uint32_t max_depth=1) |
| template<uint8_t SpaceID, uint8_t TypeID> | |
| void | fc::to_variant (const graphene::db::object_id< SpaceID, TypeID > &var, fc::variant &vo, uint32_t max_depth=1) |
| template<uint8_t SpaceID, uint8_t TypeID> | |
| void | fc::from_variant (const fc::variant &var, graphene::db::object_id< SpaceID, TypeID > &vo, uint32_t max_depth=1) |
| #define MAP_OBJECT_ID_TO_TYPE | ( | OBJECT | ) |
Definition at line 93 of file object_id.hpp.


Gaia
home
workplace
share link
Profil
Profile-edit
About
Logout
Help
Tree view
Project:
Root node 1
Child node 1
asdas
Childasdde 2
Child node 2
Root node 2
Upload File
Download as Zip
Functions
Load TMS from Path
RUN selected Script!
Information
Settings
sciDB data
read CSV
Scripts
+ new
save Script
delete
Script
BBox
Bounding Box
Bbox


{% extends "tutorial.html" %} {% block html5badge %} {% endblock %} {% block iscompatible %} return !!Modernizr.webgl && navigator.webkitGetUserMedia {% endblock %} {% block content %} {% include "warning.html" %}
This article is about using the JSARToolKit library with the WebRTC getUserMedia API to do augmented reality applications on the web. For rendering, I'm using WebGL due to the increased performance it offers. The end result of this article is a demo application that puts a 3D model on top of an augmented reality marker in webcam video.
JSARToolKit is an augmented reality library for JavaScript. It's an open source library released under the GPL and a direct port of the Flash FLARToolKit that I made for the Mozilla Remixing Reality demo. FLARToolKit itself is port of the Java NyARToolKit, which is a port of the C ARToolKit. Long way, but here we are.
JSARToolKit operates on canvas elements. As it needs to read the image off the canvas, the image needs to come from the same origin as the page or use CORS to get around same-origin policy. In a nutshell, set the crossOrigin
-property on the image or video element you want to use as a texture to ''
or 'anonymous'
.
When you pass a canvas to JSARToolKit for analysis, JSARToolKit returns a list of AR markers found in the image and the corresponding transformation matrices. To draw a 3D object on top of a marker, you pass the transformation matrix to whatever 3D rendering library you're using so that your object is transformed using the matrix. Then, draw the video frame in your WebGL scene and draw the object on top of that and you're good to go.
To analyze video using the JSARToolKit, draw the video on a canvas, then pass the canvas to JSARToolKit. Do this for every frame and you've got video AR tracking. JSARToolKit is fast enough on modern JavaScript engines to do this in realtime even on 640x480 video frames. However, the larger the video frame, the longer it takes to process. A good video frame size is 320x240, but if you expect to use small markers or multiple markers, 640x480 is preferable.
To view the webcam demo, you need to have WebRTC enabled in your browser (on Chrome, go the about:flags and enable MediaStream). You also need to print out the AR marker below. You can also try opening the marker image on your phone or tablet and showing it to the webcam.
Here is a demo of what we're aiming for. This demo creates an image slideshow using AR markers. Show a marker to the camera and it will place a photo on it. Move the marker out of the camera's view and show it again and the image has changed.
The JSARToolKit API is quite Java-like, so you'll have to do some contortions to use it. The basic idea is that you have a detector object that operates on a raster object. Between the detector and the raster is a camera parameter object that transforms raster coordinates to camera coordinates. To get the detected markers from the detector, you iterate over them and copy their transformation matrices over to your code.
The first step is to create the raster object, the camera parameter object and the detector object.
// Create a RGB raster object for the 2D canvas. // JSARToolKit uses raster objects to read image data. // Note that you need to set canvas.changed = true on every frame. var raster = new NyARRgbRaster_Canvas2D(canvas); // FLARParam is the thing used by FLARToolKit to set camera parameters. // Here we create a FLARParam for images with 320x240 pixel dimensions. var param = new FLARParam(320, 240); // The FLARMultiIdMarkerDetector is the actual detection engine for marker detection. // It detects multiple ID markers. ID markers are special markers that encode a number. var detector = new FLARMultiIdMarkerDetector(param, 120); // For tracking video set continue mode to true. In continue mode, the detector // tracks markers across multiple frames. detector.setContinueMode(true); // Copy the camera perspective matrix from the FLARParam to the WebGL library camera matrix. // The second and third parameters determine the zNear and zFar planes for the perspective matrix. param.copyCameraMatrix(display.camera.perspectiveMatrix, 10, 10000);
Next, I'm going to create a video element that's getting webcam video through the WebRTC APIs. For pre-recorded videos, just set the source attribute of the video to the video URL. If you're doing marker detection from still images, you can use a image element in much the same way.
As WebRTC and getUserMedia are still new emerging technologies, you need to feature detect them. For more details, check out Eric Bidelman's article on Capturing Audio & Video in HTML5.
var video = document.createElement('video'); video.width = 320; video.height = 240; var getUserMedia = function(t, onsuccess, onerror) { if (navigator.getUserMedia) { return navigator.getUserMedia(t, onsuccess, onerror); } else if (navigator.webkitGetUserMedia) { return navigator.webkitGetUserMedia(t, onsuccess, onerror); } else if (navigator.mozGetUserMedia) { return navigator.mozGetUserMedia(t, onsuccess, onerror); } else if (navigator.msGetUserMedia) { return navigator.msGetUserMedia(t, onsuccess, onerror); } else { onerror(new Error("No getUserMedia implementation found.")); } }; var URL = window.URL || window.webkitURL; var createObjectURL = URL.createObjectURL || webkitURL.createObjectURL; if (!createObjectURL) { throw new Error("URL.createObjectURL not found."); } getUserMedia({'video': true}, function(stream) { var url = createObjectURL(stream); video.src = url; }, function(error) { alert("Couldn't access webcam."); } );
Once we have the detector running a-ok, we can start feeding it images to detect AR matrices. First draw the image onto the raster object canvas, then run the detector on the raster object. The detector returns the number of markers found in the image.
// Draw the video frame to the raster canvas, scaled to 320x240. canvas.getContext('2d').drawImage(video, 0, 0, 320, 240); // Tell the raster object that the underlying canvas has changed. canvas.changed = true; // Do marker detection by using the detector object on the raster object. // The threshold parameter determines the threshold value // for turning the video frame into a 1-bit black-and-white image. // var markerCount = detector.detectMarkerLite(raster, threshold);
The last step is to iterate through the detected markers and get their transformation matrices. You use the transformation matrices for putting 3D objects on top of the markers.
// Create a NyARTransMatResult object for getting the marker translation matrices. var resultMat = new NyARTransMatResult(); var markers = {}; // Go through the detected markers and get their IDs and transformation matrices. for (var idx = 0; idx < markerCount; idx++) { // Get the ID marker data for the current marker. // ID markers are special kind of markers that encode a number. // The bytes for the number are in the ID marker data. var id = detector.getIdMarkerData(idx); // Read bytes from the id packet. var currId = -1; // This code handles only 32-bit numbers or shorter. if (id.packetLength <= 4) { currId = 0; for (var i = 0; i < id.packetLength; i++) { currId = (currId << 8) | id.getPacketData(i); } } // If this is a new id, let's start tracking it. if (markers[currId] == null) { markers[currId] = {}; } // Get the transformation matrix for the detected marker. detector.getTransformMatrix(idx, resultMat); // Copy the result matrix into our marker tracker object. markers[currId].transform = Object.asCopy(resultMat); }
Here's the code to copy JSARToolKit matrices over to glMatrix matrices (which are 16-element FloatArrays with the translation column in the last four elements). It works by magic (read: I don't know how ARToolKit matrices are setup. Inverted Y-axis is my guess.) Anyway, this bit of sign-reversing voodoo makes a JSARToolKit matrix work the same as a glMatrix.
To use the library with another library, such as Three.js, you need to write a function that converts the ARToolKit matrices to the library's matrix format. You also need to hook into the FLARParam.copyCameraMatrix method. The copyCameraMatrix method writes the FLARParam perspective matrix into a glMatrix-style matrix.
function copyMarkerMatrix(arMat, glMat) { glMat[0] = arMat.m00; glMat[1] = -arMat.m10; glMat[2] = arMat.m20; glMat[3] = 0; glMat[4] = arMat.m01; glMat[5] = -arMat.m11; glMat[6] = arMat.m21; glMat[7] = 0; glMat[8] = -arMat.m02; glMat[9] = arMat.m12; glMat[10] = -arMat.m22; glMat[11] = 0; glMat[12] = arMat.m03; glMat[13] = -arMat.m13; glMat[14] = arMat.m23; glMat[15] = 1; }
Three.js is a popular JavaScript 3D engine. I'm going to go through how to use JSARToolKit output in Three.js. You need three things: a full screen quad with the video image drawn onto it, a camera with the FLARParam perspective matrix and an object with marker matrix as its transform. I'll walk you through the integration in the code below.
Here's a link to the Three.js demo in action. It has debugging output enabled, so you can see some internal workings of the JSARToolKit library.
// I'm going to use a glMatrix-style matrix as an intermediary. // So the first step is to create a function to convert a glMatrix matrix into a Three.js Matrix4. THREE.Matrix4.prototype.setFromArray = function(m) { return this.set( m[0], m[4], m[8], m[12], m[1], m[5], m[9], m[13], m[2], m[6], m[10], m[14], m[3], m[7], m[11], m[15] ); }; // glMatrix matrices are flat arrays. var tmp = new Float32Array(16); // Create a camera and a marker root object for your Three.js scene. var camera = new THREE.Camera(); scene.add(camera); var markerRoot = new THREE.Object3D(); markerRoot.matrixAutoUpdate = false; // Add the marker models and suchlike into your marker root object. var cube = new THREE.Mesh( new THREE.CubeGeometry(100,100,100), new THREE.MeshBasicMaterial({color: 0xff00ff}) ); cube.position.z = -50; markerRoot.add(cube); // Add the marker root to your scene. scene.add(markerRoot); // Next we need to make the Three.js camera use the FLARParam matrix. param.copyCameraMatrix(tmp, 10, 10000); camera.projectionMatrix.setFromArray(tmp); // To display the video, first create a texture from it. var videoTex = new THREE.Texture(videoCanvas); // Then create a plane textured with the video. var plane = new THREE.Mesh( new THREE.PlaneGeometry(2, 2, 0), new THREE.MeshBasicMaterial({map: videoTex}) ); // The video plane shouldn't care about the z-buffer. plane.material.depthTest = false; plane.material.depthWrite = false; // Create a camera and a scene for the video plane and // add the camera and the video plane to the scene. var videoCam = new THREE.Camera(); var videoScene = new THREE.Scene(); videoScene.add(plane); videoScene.add(videoCam); ... // On every frame do the following: function tick() { // Draw the video frame to the canvas. videoCanvas.getContext('2d').drawImage(video, 0, 0); canvas.getContext('2d').drawImage(videoCanvas, 0, 0, canvas.width, canvas.height); // Tell JSARToolKit that the canvas has changed. canvas.changed = true; // Update the video texture. videoTex.needsUpdate = true; // Detect the markers in the video frame. var markerCount = detector.detectMarkerLite(raster, threshold); for (var i=0; i<markerCount; i++) { // Get the marker matrix into the result matrix. detector.getTransformMatrix(i, resultMat); // Copy the marker matrix to the tmp matrix. copyMarkerMatrix(resultMat, tmp); // Copy the marker matrix over to your marker root object. markerRoot.matrix.setFromArray(tmp); } // Render the scene. renderer.autoClear = false; renderer.clear(); renderer.render(videoScene, videoCam); renderer.render(scene, camera); }
In this article we went through the basics of JSARToolKit. Now you are ready to build your own webcam-using augmented reality applications with JavaScript.
Integrating JSARToolKit with Three.js is a bit of a hassle, but it is certainly possible. I'm not 100% certain if I'm doing it right in my demo, so please let me know if you know of a better way of achieving the integration. Patches are welcome :)


---
title: Project:M36 Blog
---
Project:M36 Blog
Project:M36 is a mathematically-coherent relational algebra database management system (RDBMS) written in Haskell. This blog covers the software design decisions of the product team.
Posts
$partial("templates/post-list.html")$
Older Posts


--- layout: odisite page.url: /skills_framework/ --- {% include framework_description.html %}
Explore the interactive 2017 skills framework and find out which courses and eLearning resources are available to help you gain each skill.


{% extends "../_base.html" %} {% block title %}{% endblock %} {% block content %}
Topping: {{donut.topping}}
Price: ${{donut.price}}
Shops:
Sorry, this donut is not at any shops.


This is the remote client. To get this working right, have the server running first, then open this page. After that, open the client page.
What should happen, is the client should immediately display
{ "a": 15 }and this page shouldn't display any object, until the client page is opened. When the client page has been opened, this page should show the same object as above. After 1.5 seconds, this page will update the object's a value to 200, both pages should then show
{ "a": 200 }


1. What is an equilateral triangle?
2. What is a hypotenuse?
3. A triangle with one angle greater than 90 degrees?
4. The sum of sides of triangle is called?
5. Which ancient Greek philosopher studied triangles?
© 2021 Hamza Husein


Heesun Lee is a master's student of Computer Science at Rochester Institute of Technology.
Reference: https://phodobit.kr/49


Before Change
def remove_str(self, vert_str):
Removes the given vertex, represented as a string.
cur = self.conn.cursor()
cur.execute("DELETE FROM vertices WHERE id=?", (vert_str,))
self.conn.commit()
cur.close()
def str2perms(self, center_id):
Query database for all the edge permutations that contain a given entity,
represented as a string.
After Change
Removes all permutations of the given edge.
do_with_edge_permutations(edge, self.remove_edge_permutation)
def remove_str(self, vert_str):
Removes the given vertex, represented as a string.
cur = self.open_cursor()
cur.execute("DELETE FROM vertices WHERE id=?", (vert_str,))
self.close_cursor(cur, local=True, commit=True)
def str2perms(self, center_id):
Query database for all the edge permutations that contain a given entity,
represented as a string.


- withAccentColor(Color) - Method in class dashboard.readout.Readout.Builder
-
Specifies the color of the Readout's trim and accents.
- withBaseColor(Color) - Method in class dashboard.control.ButtonGrid.Builder
-
Specifies the color of the ButtonGrid's base.
- withBaseColor(Color) - Method in class dashboard.control.Group.Builder
-
Specifies the color of the Group's base.
- withBaseColor(Color) - Method in class dashboard.readout.Readout.Builder
-
Specifies the color of the Readout's base.
- withButtonColor(Color) - Method in class dashboard.control.AuxArrowPad.Builder
-
Specifies the color of all the buttons in the AuxArrowPad.
- withButtonColor(Color) - Method in class dashboard.control.BufferReadoutControl.Builder
-
Specifies the color of all the buttons in the BufferReadoutControl.
- withButtonColor(Color) - Method in class dashboard.control.MainArrowPad.Builder
-
Specifies the color of all the buttons in the MainArrowPad.
- withButtonColor(Color) - Method in class dashboard.control.MultiIncrementer.Builder
-
Specifies the color of all the buttons in the MultiIncrementer.
- withButtonColor(Color) - Method in class dashboard.control.SingleIncrementer.Builder
-
Specifies the color of all the buttons in the SingleIncrementer.
- withColor(Color) - Method in class dashboard.readout.Readout.Builder
-
Specifies the color of the Readout's display.
- withFont(String) - Method in class dashboard.readout.BufferReadout.Builder
-
Specifies the font to use for the BufferReadout's text.
- withGoal(GPoint) - Method in class dashboard.readout.CompassReadout.Builder
-
Specifies the goal of the CompassReadout.
- withLocation(GPoint, GPoint) - Method in class dashboard.readout.CompassReadout.Builder
-
Specifies the initial position and bearing from which the CompassReadout
should orient itself and its needle.
- withOffColor(Color) - Method in class dashboard.readout.ImageReadout.Builder
-
Specifies the color of the ImageReadout's screen when turned off.
- withOrientation(int) - Method in class dashboard.readout.BarReadout.Builder
-
- withRange(double, double) - Method in class dashboard.readout.LevelReadout.Builder
-
Specifies the minimum and maximum values of the LevelReadout.
- withRowsCols(int, int) - Method in class dashboard.control.ButtonGrid.Builder
-
Specifies the number of rows and columns that the ButtonGrid should have.
- withSpacing(double) - Method in class dashboard.control.ButtonGrid.Builder
-
Specifies the spacing of the ButtonGrid.
- withSpacing(double) - Method in class dashboard.control.Group.Builder
-
Specifies the spacing of the Group.
- withSpacing(double) - Method in class dashboard.readout.Readout.Builder
-
Specifies the spacing of the Readout, which is usually the width of the padding from the
Readout's display to the edge of its base.
- withStartAngle(double) - Method in class dashboard.readout.DialReadout.Builder
-
Specifies the start angle of the DialReadout's dial face.
- withSweepAngle(double) - Method in class dashboard.readout.DialReadout.Builder
-
Specifies the sweep angle of the DialReadout's dial face.
- withViewRadius(double) - Method in class dashboard.readout.MinimapReadout.Builder
-
Specifies the view radius of the MinimapReadout, i.e.


Student at University of California San Diego
Major in Computer Science, minor in Studio Art 3rd year Warren College extra curricular: Tutoring in CSE department for lower division courses including CSE 8a, 8b, 11, and 30 Choreographer on kunFusion dance team Graphics Committee member in Fusion Staff Sailing in Mission Bay (rental through mission bay aquatic center)


Dump XML function permit to generate the XML configuration file and gather it for a specific m0n0wall device
To do this, go to Others - Dump XML and select the host you want the config to be dumped. You should receive a XML file of the current host configuration as it is in the m0n0wall-CMI database. Note that this would not reflect the configuration of the device if you haven't synced it.
To save configuration to monowall, you have two choice:


Sign Up
Enter your email address and password to access admin panel.
Your Full Name
Email address
Password
I accept
Terms and Conditions
Sign Up
Already Have Account ?
Log In


Settings
Alfred Wayne
<EMAIL_ADDRESS>Notification Settings
Push notifications
Call on phone
Notify when second in line
Volume
Account Settings
Log out
Change Email
Change phone number
Delete account


legal_params = []
for fn in legal_params_fns:
legal_params += inspect.getargspec(fn)[0]
legal_params = set(legal_params)
for params_name in params:
if params_name not in legal_params:
for params_name in params:
for fn in legal_params_fns:
if has_arg(fn, params_name):
break
else:
if params_name != "nb_epoch":


|
My Project
|
A description of a byte-code object referenced by a constant. More...
#include <cpool.hh>
Public Types | |
| enum | { primitive =0, string_literal =1, class_reference =2, pointer_method =3, pointer_field =4, array_length =5, instance_of =6, check_cast =7 } |
| Generic constant pool tag types. More... | |
| enum | { has_thisptr = 0x1, is_constructor = 0x2, is_destructor = 0x4 } |
Public Member Functions | |
| CPoolRecord (void) | |
| Construct an empty record. | |
| ~CPoolRecord (void) | |
| Destructor. | |
| uint4 | getTag (void) const |
| Get the type of record. | |
| const string & | getToken (void) const |
| Get name of method or data-type. | |
| const uint1 * | getByteData (void) const |
| Get pointer to string literal data. | |
| int4 | getByteDataLength (void) const |
| Number of bytes of string literal data. | |
| Datatype * | getType (void) const |
| Get the data-type associated with this. | |
| uintb | getValue (void) const |
| Get the constant value associated with this. | |
| bool | hasThisPointer (void) const |
| Is object a method with a this pointer. | |
| bool | isConstructor (void) const |
| Is object a constructor method. | |
| bool | isDestructor (void) const |
| Is object a destructor method. | |
| void | saveXml (ostream &s) const |
| Save object to an XML stream. More... | |
| void | restoreXml (const Element *el, TypeFactory &typegrp) |
| Restore object from XML stream. More... | |
Friends | |
| class | ConstantPool |
A description of a byte-code object referenced by a constant.
Byte-code languages can make use of objects that the system knows about but which aren't fully embedded in the encoding of instructions that use them. Instead the instruction refers to the object via a special encoded reference. This class describes one object described by such a reference. In order to provide a concrete interpretation of the instruction (i.e. a p-code translation), these objects generally resolve to some sort of constant value (hence the term constant pool). The type of constant goes to the formal CPoolRecord tag field which can be a:
For decompilation, knowing the actual constant a byte-code interpreter would need is secondary to knowing what object is being referenced. So the CPoolRecord can hold a constant value, but generally it provides a data-type associated with the object and a symbol name or other string token naming the object.
| anonymous enum |
Generic constant pool tag types.
| anonymous enum |
| void CPoolRecord::restoreXml | ( | const Element * | el, |
| TypeFactory & | typegrp | ||
| ) |
Restore object from XML stream.
Initialize this CPoolRecord instance from a <cpoolrec> tag.
| el | is the <cpoolrec> element |
| typegrp | is the TypeFactory used to resolve data-types |
| void CPoolRecord::saveXml | ( | ostream & | s | ) | const |
Save object to an XML stream.
Save the constant pool object description as a <cpoolrec> tag.
| s | is the output stream |


original message: {{message}}
computed reversed message: {{reversedMessage_c}}
now you can see me
Ask a yes/no question:
{{answer}}


Dreams Catcher
Track your dreams
Add a new Dream:
Name:
Image Url:
Description:
Achieved? (Yes or Not yet)
Category:
Filter by Category:
Unselect the category you've chosen to see ALL dreams
Search:
Filter by Achieved Dreams:
All
Yes
Not Yet
Eat another pizza
Dark mode


We gratefully acknowledge support from the Simons Foundation, member institutions, and all contributors. Donate
{{ macros.compactsearch('level-right') }}
{% if request.session and request.session.user and request.session.user.name %}Logged in as {{ request.session.user.name.forename }} {{ request.session.user.name.surname }} {{ request.session.user.name.suffix }} | My Account | Logout{% else %}Login{% endif %}


Publications
Ground penetrating radar (GPR) models of the regolith and water reservoir of an underground dam in the Brazilian semiarid region
Journal of Applied Geophysics
Imaging scours in straightened and braided gravel-bed rivers with ground-penetrating radar
Near Surface Geophysics
DOI: 10.1002/nsg.12042
Reduction of conceptual model uncertainty using ground-penetrating radar profiles: Field-demonstration for a braided-river aquifer
Journal of Hydrology
How to chase a tracer - combining conventional salt tracer testing and direct push electrical conductivity profiling for enhanced aquifer characterization
Advances in Water Resources
Subsurface flow mixing in coarse, braided river deposits
Hydrology and Earth System Sciences
Morphological perspective on the sedimentary characteristics of a coarse, braided reach: Tagliamento River (NE Italy)
Geomorphology
Efficient Deconvolution of Ground-Penetrating Radar Data
IEEE Transactions on Geoscience and Remote Sensing
Influence of conceptual model uncertainty on contaminant transport forecasting in braided river aquifers
Journal of Hydrology
Effects of river morphology, hydraulic gradients, and sediment deposition on water exchange and oxygen dynamics in salmonid redds
Science of The Total Environment
Spatiotemporal scales of river-groundwater interaction: a multidimensional hydrogeological investigation approach
Grundwasser (German)
The Role of Prior Model Calibration on Predictions with Ensemble Kalman Filter
Ground Water
PhD Thesis
Incorporating sedimentological observations, hydrogeophysics and conceptual knowledge to constrain 3D numerical heterogeneity models of alluvial systems
University of Basel (Switzerland)
Conference proceedings
RGPR - An open-source package to process and visualize GPR data
Conference proceeding: 17th International Conference on Ground Penetrating Radar, June 18–21, 2018 in Rapperswil, Switzerland
Quantifying scour depth in a straightened gravel-bed river with ground-penetrating radar
Conference proceeding: 17th International Conference on Ground Penetrating Radar, June 18–21, 2018 in Rapperswil, Switzerland
Presentations (oral & poster)
Poster: RGPR - An open-source package to process and visualize GPR data
Conference proceeding: 17th International Conference on Ground Penetrating Radar, June 18–21, 2018 in Rapperswil, Switzerland
Oral presentation: Quantifying scour depth in a straightened gravel-bed river with ground-penetrating radar
17th International Conference on Ground Penetrating Radar, June 18–21, 2018 in Rapperswil, Switzerland
Oral presentation: A 3D object-based model to simulate highly-heterogeneous, coarse, braided river deposits
AGU 2016 Fall Meeting, San Francisco, California, USA, 12–16 December 2016
Poster: Cyclic deformations in the Opalinus clay: a laboratory experiment
EGU General Assembly 2015, Vienna, Austria, 12–17 April 2015


Read Post
WGR614v10 and WNR1000v3 Cross-Flashing Firmware Update - part 2
You might want to read Part 1 before continuing. If you reach this page, meaning that you don't have backdoor telnet available, or for some reason telnetenable
doesn't work on your WGR614v10, or you want to experiment further with your router. There is possibility (not tested) that you can also flash WGR614v10 firmware onto WNR1000v3. You might be able to go back and forth between both firmware versions. Everything is possible, all you need to do is try!
In Cross-Flashing Part 1, we tricked WGR614v10 to accept WNR1000v3 firmware update by burning WNR1000v3 board ID onto WGR614v10. Then, we can use the web interface to upgrade the firmware. This trick is trying to fool the firmware to see and validate the wrong hardware for the right firmware. Now, we could actually do the opposite. If we hack the firmware to include the right signature for the right hardware, then we could upgrade a wrong firmware onto the right hardware. To do this, we need to know the board ID.
Download latest firmware upgrades for WGR614v10 and WNR1000v3 from Netgear Download Center. Open both *.chk file using a hex editor. Windows users can use HexEdit, Linux and OS X users can use hexedit command line from macports or brew.
WGR614v10 - WGR614v10-V<IP_ADDRESS>_60.0.85NA.chk - U12H139T01_NETGEAR is the board ID.
WNR1000v3 - WNR1000v3-V<IP_ADDRESS>_60.0.93NA.chk - U12H139T00_NETGEAR is the board ID.
Swap those board IDs and save the firmware as new files. Now the WGR614v10 firmware can be flashed onto WNR1000v3 device and vice versa.
DO NOT UPDATE FIRMWARE OVER WIRELESS CONNECTION. DO IT THROUGH AN ETHERNET CABLE. DO IT AT YOUR OWN RISK! THERE IS NO WARRANTY THIS METHOD WILL WORK FOR YOU. YOU'VE BEEN WARNED!
PLEASE MAKE SURE YOU CHECK HARDWARE COMPATIBILITY BEFORE FLASHING ANY FIRMWARE.  DO IT AT YOUR OWN RISK! THERE IS NO WARRANTY THIS METHOD WILL WORK FOR YOU. YOU'VE BEEN WARNED!


in
html5
,
templates
50+ best free responsive event template in 2015
in
html5
,
templates
50+ best free responsive restaurant template in 2015
in
html5
,
templates
50+ best free responsive coming soon template in 2015
in
html5
,
templates
50+ best free responsive photography template in 2015
in
html5
,
templates
50+ best free responsive corporate template in 2015
in
html5
,
templates
50+ best free responsive event template in 2015
in
html5
,
templates
50+ best free responsive restaurant template in 2015
in
html5
,
templates
50+ best free responsive coming soon template in 2015
in
html5
,
templates


I'm Jeffey Agustin Fresh Graduate from the University of Manila. I'm currently live in Malabon City. I passionate Web Design.


Open the console.
If the tables do not render, refresh the page.
Chrome often bugs out on 'console.table' on first load.


{% extends 'base.html' %} {% load staticfiles %} {% block styles %} {% endblock %} {% block index %}
Yes. But I've been living in Austin long enough to know that being weird is often encouraged. Especially after moving here from Florida. Yet, ironically, I had never heard of the state's "strange" stereotype until moving out of it. I wouldn't say this off-beat background led me to my current path, but I'm sure it helped.
In the summer of 2016 I began building a tiny house on wheels with my friend while studying independently to become a software engineer - Python being my weapon of choice. Each has brought on its own challenges. From implementing electrical wiring to understanding the command line, I've learned a lot. And it's not just building, but designing, problem solving, and managing personal projects that has exercised some of my deepest creative abilities to solve the inherent challenges of engineering something from scratch.
 I love sleep because it's like a time machine to breakfast. I enjoy reading, cooking, and practicing yoga and meditation in my free time and stay up too late when I don't have free time. Hiking to hidden water spots and travelling to see family has also been very rewarding since moving to Austin in the Fall of 2014.
Is to teach and illustrate what I've learned. Whether it's a how-to guide or a story or otherwise, the narrative will be rich and informative. I'd like to help those just getting started in a format that would have been useful for the beginner that's still inside of me.
When your side projects become your main goals in life, it is then that true passion reveals itself.
What started as a desire to live minimally has manifested into reality. Not seen are the labyrinth of hidden systems that most don't appreciate in their home. The complexities of a building are woven elegantly in to the most practical asset in your life: your home.
This minimalistic tint started by the THOW has bled into my path towards programming, and Python has fulfilled this essence to the fullest with its simple syntax and powerful libraries. My main focus right now is data visualization and the power of dynamic, realtime web apps.
"The balance of power shifts on the Internet to the individual."
"Everyone's drunk on the term 'blog'."
- Jason Calacanis
My formidable years have been spent learning from books, professors, and mentors.
From a soft piece of clay to the sculptor himself, many fulfilling experiences were forged here. In an efficiency-focused major I gained the perspective of a business mindset applied towards engineering applications. For my senior design project my team and I built a software tool for Crowley Maritime to standardize their ship bidding processess, saving them time and money from increased efficiency and error reduction. It was this direct experience that allowed me to get a job at OpenSymmetry...
As my first job outside of school I certainly landed in a fortunate spot. Great mentorship allowed me to grow and apply myself in challenging roles. I became comfortable working with clients through our software implementation lifecycle: from requirements gathering and design through building, testing, and go-live using Xactlys or IBMs incentive-based management solution.
I specialize in furniture building and data visualization web apps and would love to collaborate with you on a new project. Feel free to reach out and schedule a meeting to discuss your project. Here's a copy of my resume if you're hiring.


--- layout: default permalink: /impressum/ --- Icons made by Freepik and Smashicons from www.flaticon.com. {% include footer.html %}


| This is still under construction! Don't believe it yet! | Course | TuTh 10:00-11:30 am, 460-334 |
| Course email | |
| Discussion | https://piazza.com/stanford/fall2013/linguist278 |
| Instructor | Christopher Manning |
| Office hrs | Thu 11:30-12:30, and by appointment |
| Office | Gates 2484 |
| Plan | Assignment | Reading/Reference | |
|---|---|---|---|
| Sep 26 |
|
|
|
| Sep 28 |
|
||
| Oct 3 |
|
|
|
| Oct 5 | |||
| Oct 10 |
|
|
|
| Oct 12 | |||
| Oct 15 |
|
|
|
| Oct 17 |
|
||
| Oct 22 |
|
|
|
| Oct 24 | |||
| Oct 29 |
|
|
|
| Oct 31 | |||
| Nov 5 |
|
|
|
| Nov 7 | |||
| Nov 12 |
|
|
|
| Nov 14 | |||
| Nov 19 |
|
|
|
| Nov 21 |
|
||
| Thanksgiving recess | |||
| Dec 3 |
|
||
| Dec 5 |


Iterators¶
Twitter API has multiple endpoints that exposes pages api. The implementation might differ from endpoint to endpoint.
Tweetinvi hides this complexity to you via iterators
.
When you see a tag iterators it informs you that the endpoint can be reached via an iterator.
Iterator¶
Iterators let you request multiple pages until no more items are available.
NextPageAsync()
request twitter for the next page of resultsNextCursor
is updated after each call toNextPageAsync
. It can be used to start a new request at this position.Completed
is updated after each call toNextPageAsync
. It is marked as true when no more results are available.
Iterator page¶
Pages are enumerators and contain elements returned by a single request.
ToArray()
returns the content of the page.NextCursor
contains the next cursor to use for following requests.IsLastPage
informs whether the page was the last one that could be reached.
Example¶
var timelineTweets = new List<ITweet>();
var timelineIterator = userClient.Timelines.GetHomeTimelineIterator();
while (!timelineIterator.Completed)
{
var page = await timelineIterator.NextPageAsync();
timelineTweets.AddRange(page);
}
Restart from a previous cursor¶
As mentioned you can restart from a previous cursor state.
var firstFriendIdsIterator = client.Users.GetFollowerIdsIterator(new GetFollowerIdsParameters("tweetinvi")
{
PageSize = 50
});
var firstPage = await firstFriendIdsIterator.NextPageAsync();
After having retrieved a first page, we can now request a new one from the previous cursor.
var friendIdsIterator = client.Users.GetFollowerIdsIterator(new GetFollowerIdsParameters("tweetinvi")
{
Cursor = firstFriendIdsIterator.NextCursor,
// or Cursor = firstPage.NextCursor
});
var secondPage = await friendIdsIterator.NextPageAsync();
Flavour of iterators¶
As mentioned earlier Twitter exposes different support of pages. As a consequence parameters might differ between 2 types of iterator.
Cursor iterators¶
Cursor iterators accesses cursor endpoint properly supported by Twitter API
int PageSize
defines the maximum number of items that will be returned per request.string Cursor
defines the cursor that will be used for executing the first request.
var friendIdsIterator = client.Users.GetFollowerIdsIterator(new GetFollowerIdsParameters("tweetinvi")
{
Cursor = "previous_cursor",
PageSize = 50
});
MinMax iterators¶
MinMax iterators accesses older api endpoints that have less reliable support for cursors
int PageSize
defines the maximum number of items that will be returned per request.long? SinceId
defines the minimum id that can be returned by Twitterlong? MaxId
defines the maximum id that can be returned by TwitterContinueMinMaxCursor
defines when the cursor is considered complete. By default it will be considered complete when 0 results are being returned.
var timelineIterator = userClient.Timelines.GetHomeTimelineIterator(new GetHomeTimelineParameters()
{
MaxId =<PHONE_NUMBER>18409,
SinceId =<PHONE_NUMBER>184091,
PageSize = 50,
ContinueMinMaxCursor = ContinueMinMaxCursor.UntilNoItemsReturned
});
Multi-Levels iterators¶
Twitter API misses some useful endpoints. Tweetinvi created multi level cursors that takes care of handling the complexity for you
Twitter do not provide any endpoint to retrieve a collection of friends. It only supports retrieving friend ids.
The Users.GetFollowersIterator
is an example of a multi level cursor and is used exactly as other cursors.
var friendsIterator = client.Users.GetFollowersIterator(new GetFollowersParameters("tweetinvi"));
while (!friendsIterator.Completed)
{
var page = await friendsIterator.NextPageAsync();
}
Here is what happens behind the scenes when a user has more than 5000 friends:
1st call to
await friendsIterator.NextPageAsync();
, Tweetinvi performs 2 requests and returns 100 users.GetFriendIds
that return 5000 friend idsGetUsers
that return 100 users
Next 49x calls to
await friendsIterator.NextPageAsync();
; Tweetinvi 1 request to get the next users.GetUsers
that return 100 users
On the 51st call to
await friendsIterator.NextPageAsync();
; Tweetinvi performs again 2 requests.GetFriendIds
that return 5000 friend idsGetUsers
that return 100 users