|
Mini51 BSP
V3.02.002
The Board Support Package for Mini51 Series
|
#include <Mini51Series.h>
Data Fields | |
| __I uint32_t | PDID |
| __IO uint32_t | RSTSRC |
| __IO uint32_t | IPRSTC1 |
| __IO uint32_t | IPRSTC2 |
| __IO uint32_t | BODCTL |
| __IO uint32_t | P0_MFP |
| __IO uint32_t | P1_MFP |
| __IO uint32_t | P2_MFP |
| __IO uint32_t | P3_MFP |
| __IO uint32_t | P4_MFP |
| __IO uint32_t | P5_MFP |
| __IO uint32_t | IRCTRIMCTL |
| __IO uint32_t | IRCTRIMIER |
| __IO uint32_t | IRCTRIMISR |
| __IO uint32_t | RegLockAddr |
@addtogroup GCR System Global Control Registers(GCR) Memory Mapped Structure for GCR Controller
Definition at line 1954 of file Mini51Series.h.
| GCR_T::BODCTL |
| Bits | Field | Descriptions |
| [0] | BOD_VL_EXT | Brown-out Detector Selection Extension (Initiated & Write-protected Bit)
The default value is set by flash controller user configuration CBOVEXT bit (config0 [23]). If config0 bit[23] is set to 1, default value of BOD_VL_EXT is 0. If config0 bit[23] is set to 0, default value of BOD_VL_EXT is 1. 0 = Brown-out detector threshold voltage is selected by the table defined in BOD_VL. 1 = Brown-out detector threshold voltage is selected by the table defined below. 11 = 4.4V 10 = 3.7V 01 = 2.7V 00 = 2.2V |
| [2:1] | BOD_VL | Brown-out Detector Threshold Voltage Selection (Initiated & Write-protected Bit)
The default value is set by flash controller user configuration CBOV bit (config0 [22:21]). BOD_VL[1] BOD_VL[0] Brown-out voltage 11 = Disable 10 = 3.7V 01 = 2.7V 00 = Reserved |
| [3] | BOD_RSTEN | Brown-out Reset Enable Control (Initiated And Write-protected Bit)
0 = Brown-out "INTERRUPT" function Enabled; when the Brown-out Detector function is enable and the detected voltage is lower than the threshold, then assert a signal to interrupt the Cortex-M0 CPU. 1 = Brown-out "RESET" function Enabled; when the Brown-out Detector function is enable and the detected voltage is lower than the threshold then assert a signal to reset the chip. The default value is set by flash controller user configuration register config0 bit[20]. When the BOD_EN is enabled and the interrupt is asserted, the interrupt will be kept till the BOD_EN is set to 0. The interrupt for CPU can be blocked by disabling the NVIC in CPU for BOD interrupt or disable the interrupt source by disabling the BOD_EN and then re-enabling the BOD_EN function if the BOD function is required. |
| [4] | BOD_INTF | Brown-out Detector Interrupt Flag
0 = Brown-out Detector does not detect any voltage dropped at AVDD down through or up through the voltage of BOD_VL setting. 1 = When Brown-out Detector detects the AVDD is dropped through the voltage of BOD_VL setting or the AVDD is raised up through the voltage of BOD_VL setting, this bit is set to 1 and the Brown-out interrupt is requested if Brown-out interrupt is enabled. |
| [5] | BOD_LPM | Brown-out Detector Low Power Mode (Write Protect)
0 = BOD operate in normal mode (default). 1 = Enable the BOD low power mode. The BOD consumes about 100uA in normal mode, the low power mode can reduce the current to about 1uA but slow the BOD response. |
| [6] | BOD_OUT | Brown-out Detector Output State
0 = Brown-out Detector status output is 0, the detected voltage is higher than BOD_VL setting. 1 = Brown-out Detector status output is 1, the detected voltage is lower than BOD_VL setting. |
Definition at line 2687 of file Mini51Series.h.
| GCR_T::IPRSTC1 |
| Bits | Field | Descriptions |
| [0] | CHIP_RST | CHIP One-shot Reset (Write Protect)
Setting this bit will reset the CHIP, including CPU kernel and all peripherals, and this bit will automatically return to 0 after the 2 clock cycles. The CHIP_RST is the same as the POR reset, and all the chip module is reset and the chip settings from flash are also reloaded. 0 = Chip normal operation. 1 = CHIP one-shot reset. Note: This bit is the protected bit, and programming it needs to write 0x59, 0x16, and 0x88 to address 0x5000_0100 to disable register protection. Refer to the register REGWRPROT at address GCR_BA + 0x100. |
| [1] | CPU_RST | CPU Kernel Reset
Setting this bit will reset the CPU kernel, and this bit will automatically return to 0 after the 2 clock cycles. 0 = CPU normal operation. 1 = Reset CPU Kernel. Note: This bit is the protected bit, and programming it needs to write 0x59, 0x16, and 0x88 to address 0x5000_0100 to disable register protection. Refer to the register REGWRPROT at address GCR_BA + 0x100. |
Definition at line 2682 of file Mini51Series.h.
| GCR_T::IPRSTC2 |
| Bits | Field | Descriptions |
| [1] | GPIO_RST | GPIO (P0~P5) Controller Reset
0 = GPIO module normal operation. 1 = GPIO module reset. |
| [2] | TMR0_RST | Timer0 Controller Reset
0 = Timer0 module normal operation. 1 = Timer0 module reset. |
| [3] | TMR1_RST | Timer1 Controller Reset
0 = Timer1 module normal operation. 1 = Timer1 module reset. |
| [8] | I2C_RST | I2C Controller Reset
0 = I2C module normal operation. 1 = I2C module reset. |
| [12] | SPI_RST | SPI Controller Reset
0 = SPI module normal operation. 1 = SPI module reset. |
| [16] | UART_RST | UART Controller Reset
0 = UART module normal operation. 1 = UART module reset. |
| [20] | PWM_RST | PWM Controller Reset
0 = PWM module normal operation. 1 = PWM module reset. |
| [22] | ACMP_RST | ACMP Controller Reset
0 = ACMP module normal operation. 1 = ACMP module reset. |
| [28] | ADC_RST | ADC Controller Reset
0 = ADC module normal operation. 1 = ADC module reset. |
Definition at line 2683 of file Mini51Series.h.
| GCR_T::IRCTRIMCTL |
| Bits | Field | Descriptions |
| [0] | TRIM_SEL | Trim Frequency Selection
This bit is to enable the HIRC auto trim. When setting this bit to 1, the HIRC auto trim function will trim HIRC to 22.1184 MHz automatically based on the LXT reference clock. During auto trim operation, if LXT clock error is detected or trim retry limitation count reached, this field will be cleared to 0 automatically. 0 = HIRC auto trim function Disabled. 1 = HIRC auto trim function Enabled and HIRC trimmed to 22.1184 MHz. |
| [5:4] | TRIM_LOOP | Trim Calculation Loop
This field defines that trim value calculation is based on how many LXT clocks in. For example, if TRIM_LOOP is set as 00, auto trim circuit will calculate trim value based on the average frequency difference in 4 LXT clock. 00 = Trim value calculation is based on average difference in 4 LXT clocks. 01 = Trim value calculation is based on average difference in 8 LXT clocks. 10 = Trim value calculation is based on average difference in 16 LXT clocks. 11 = Trim value calculation is based on average difference in 32 LXT clocks. |
Definition at line 2700 of file Mini51Series.h.
| GCR_T::IRCTRIMIER |
| Bits | Field | Descriptions |
| [1] | TRIM_FAIL_IEN | Trim Failure Interrupt Enable Control
This bit controls if an interrupt will be triggered while HIRC trim value update limitation count is reached and HIRC frequency is still not locked on target frequency set by TRIM_SEL. If this bit is high and TRIM_FAIL_INT is set during auto trim operation, an interrupt will be triggered to notify that HIRC trim value update limitation count is reached. 0 = TRIM_FAIL_INT status Disabled to trigger an interrupt to CPU. 1 = TRIM_FAIL_INT status Enabled to trigger an interrupt to CPU. |
| [2] | 32K_ERR_IEN | LXT Clock Error Interrupt Enable Control
This bit controls if CPU could get an interrupt while LXT clock is inaccurate during auto trim operation. If this bit is high, and 32K_ERR_INT is set during auto trim operation, an interrupt will be triggered to notify the LXT clock frequency is inaccurate. 0 = 32K_ERR_INT status Disabled to trigger an interrupt to CPU. 1 = 32K_ERR_INT status Enabled to trigger an interrupt to CPU. |
Definition at line 2701 of file Mini51Series.h.
| GCR_T::IRCTRIMISR |
| Bits | Field | Descriptions |
| [0] | FREQ_LOCK | HIRC Frequency Lock Status
This bit indicates the HIRC frequency locked in 22.1184 MHz. This is a read only status bit and doesn't trigger any interrupt. |
| [1] | TRIM_FAIL_INT | Trim Failure Interrupt Status
This bit indicates that HIRC trim value update limitation count reached and HIRC clock frequency still doesn't lock. Once this bit is set, the auto trim operation stopped and TRIM_SEL will be cleared to 0 by hardware automatically. If this bit is set and TRIM_FAIL_IEN is high, an interrupt will be triggered to notify that HIRC trim value update limitation count was reached. Software can write 1 to clear this bit to 0. 0 = Trim value update limitation count is not reached. 1 = Trim value update limitation count is reached and HIRC frequency is still not locked. |
| [2] | 32K_ERR_INT | LXT Clock Error Interrupt Status
This bit indicates that LXT clock frequency is inaccuracy. Once this bit is set, the auto trim operation stopped and TRIM_SEL will be cleared to 0 by hardware automatically. If this bit is set and 32K_ERR_IEN is high, an interrupt will be triggered to notify the LXT clock frequency is inaccuracy. Software can write 1 to clear this bit to 0. 0 = LXT clock frequency is accuracy. 1 = LXT clock frequency is inaccuracy. |
Definition at line 2702 of file Mini51Series.h.
| GCR_T::P0_MFP |
| Bits | Field | Descriptions |
| [7:0] | P0_MFP | P0 Multiple Function Selection
|
| [8] | P0_ALT0 | P0.0 Alternate Function Selection
|
| [9] | P0_ALT1 | P0.1 Alternate Function Selection
|
| [12] | P0_ALT4 | P0.4 Alternate Function Selection
|
| [13] | P0_ALT5 | P0.5 Alternate Function Selection
|
| [14] | P0_ALT6 | P0.6 Alternate Function Selection
|
| [15] | P0_ALT7 | P0.7 Alternate Function Selection
|
| [23:16] | P0_TYPE | P0[7:0] TTL Or Schmitt Trigger Function Enable Control
0 = P0[7:0]Select I/O input as TTL function. 1 = P0[7:0] Select I/O input as Schmitt Trigger function . |
Definition at line 2691 of file Mini51Series.h.
| GCR_T::P1_MFP |
| Bits | Field | Descriptions |
| [7:0] | P1_MFP | P1 Multiple Function Selection
|
| [8] | P1_ALT0 | P1.0 Alternate Function Selection
|
| [10] | P1_ALT2 | P1.2 Alternate Function Selection
|
| [11] | P1_ALT3 | P1.3 Alternate Function Selection
|
| [12] | P1_ALT4 | P1.4 Alternate Function Selection
|
| [13] | P1_ALT5 | P1.5 Alternate Function Selection
|
| [23:16] | P1_TYPE | P1[7:0] TTL Or Schmitt Trigger Function Enable Control
0 = P1[7:0]Select I/O input as TTL function. 1 = P1[7:0] Select I/O input as Schmitt Trigger function . |
Definition at line 2692 of file Mini51Series.h.
| GCR_T::P2_MFP |
| Bits | Field | Descriptions |
| [7:0] | P2_MFP | P2 Multiple Function Selection
|
| [10] | P2_ALT2 | P2.2 Alternate Function Selection
|
| [11] | P2_ALT3 | P2.3 Alternate Function Selection
|
| [12] | P2_ALT4 | P2.4 Alternate Function Selection
|
| [13] | P2_ALT5 | P2.5 Alternate Function Selection
|
| [14] | P2_ALT6 | P2.6 Alternate Function Selection
|
| [23:16] | P2_TYPE | P2[7:0] TTL Or Schmitt Trigger Function Enable Control
0 = P2[7:0]Select I/O input as TTL function. 1 = P2[7:0] Select I/O input as Schmitt Trigger function . |
Definition at line 2693 of file Mini51Series.h.
| GCR_T::P3_MFP |
| Bits | Field | Descriptions |
| [7:0] | P3_MFP | P3 Multiple Function Selection
|
| [8] | P3_ALT0 | P3.0 Alternate Function Selection
|
| [9] | P3_ALT1 | P3.1 Alternate Function Selection
|
| [10] | P3_ALT2 | P3.2 Alternate Function Selection
|
| [12] | P3_ALT4 | P3.4 Alternate Function Selection
|
| [13] | P3_ALT5 | P3.5 Alternate Function Selection
|
| [14] | P3_ALT6 | P3.6 Alternate Function Selection
|
| [23:16] | P3_TYPE | P3[7:0] TTL Or Schmitt Trigger Function Enable Control
0 = P3[7:0]Select I/O input as TTL function. 1 = P3[7:0] Select I/O input as Schmitt Trigger function . |
| [24] | P32CPP1 | P3.2 Alternate Function Selection Extension
|
Definition at line 2694 of file Mini51Series.h.
| GCR_T::P4_MFP |
| Bits | Field | Descriptions |
| [7:0] | P4_MFP | P4 Multiple Function Selection
|
| [14] | P4_ALT6 | P4.6 Alternate Function Selection
|
| [15] | P4_ALT7 | P4.7 Alternate Function Selection
|
| [23:16] | P4_TYPE | P4[7:0] TTL Or Schmitt Trigger Function Enable Control
0 = P4[7:0]Select I/O input as TTL function. 1 = P4[7:0] Select I/O input as Schmitt Trigger function . |
Definition at line 2695 of file Mini51Series.h.
| GCR_T::P5_MFP |
| Bits | Field | Descriptions |
| [7:0] | P5_MFP | P5 Multiple Function Selection
|
| [8] | P5_ALT0 | P5.0 Alternate Function Selection
|
| [9] | P5_ALT1 | P5.1 Alternate Function Selection
|
| [10] | P5_ALT2 | P5.2 Alternate Function Selection
|
| [11] | P5_ALT3 | P5.3 Alternate Function Selection
|
| [12] | P5_ALT4 | P5.4 Alternate Function Selection
|
| [13] | P5_ALT5 | P5.5 Alternate Function Selection
|
| [23:16] | P5_TYPE | P5[7:0] TTL Or Schmitt Trigger Function Enable Control
0 = P5[7:0]Select I/O input as TTL function. 1 = P5[7:0] Select I/O input as Schmitt Trigger function . |
Definition at line 2696 of file Mini51Series.h.
| GCR_T::PDID |
| Bits | Field | Descriptions |
| [31:0] | PDID | Product Device Identification Number
This register reflects the device part number code. Software can read this register to identify which device is used. For example, the MINI51LDE PDID code is "0x20205100". |
Definition at line 2680 of file Mini51Series.h.
| GCR_T::RegLockAddr |
| Bits | Field | Descriptions |
| [0] | RegUnLock | Register Write-protection Disable Index (Read Only)
0 = Write-protection Enabled for writing protected registers. Any write to the protected register is ignored. 1 = Write-protection Disabled for writing protected registers. The Protected registers are: IPRSTC1 (0x5000_0008) BODCTL (0x5000_0018) PWRCON (0x5000_0200), bit[6] is not protected for power wake-up interrupt clear APBCLK (0x5000_0208), bit[0] watchdog clock enable only CLKSEL0 (0x5000_0210) CLKSEL1 (0x5000_0214), bit[1:0] Watchdog clock source select only NMI_SEL (0x5000_0380), bit[8] NMI interrupt enable only ISPCON (0x5000_C000) ISPTRG (0x5000_C010) WTCR (0x4000_4000) Note: The bits which are write-protected will be noted as" (Write Protect)" beside the description. |
| [7:0] | REGWRPROT | Register Write-protection Code (Write Only)
Some registers have write-protection function. Writing these registers have to disable the protected function by writing the sequence value 0x59, 0x16, 0x88 to this field. After this sequence is completed, the REGPROTDIS bit will be set to 1 and write-protection registers can be normal write. |
Definition at line 2706 of file Mini51Series.h.
| GCR_T::RSTSRC |
| Bits | Field | Descriptions |
| [0] | RSTS_POR | Power-on Reset Flag
The RSTS_POR flag is set by the "reset signal", which is from the Power-On Reset (POR) controller or bit CHIP_RST (IPRSTC1[0]), to indicate the previous reset source. 0 = No reset from POR or CHIP_RST. 1 = Power-on-Reset (POR) or CHIP_RST had issued the reset signal to reset the system. Note: Software can write 1 to clear this bit to 0. |
| [1] | RSTS_RESET | Reset Pin Reset Flag
The RSTS_RESET flag is set by the "reset signal" from the /RESET pin to indicate the previous reset source. 0 = No reset from pin /RESET pin. 1 = The /RESET pin had issued the reset signal to reset the system. Note: Software can write 1 to clear this bit to 0. |
| [2] | RSTS_WDT | Watchdog Reset Flag
The RSTS_WDT flag is set by the "reset signal" from the Watchdog timer to indicate the previous reset source. 0 = No reset from Watchdog timer. 1 = The Watchdog timer had issued the reset signal to reset the system. Note: Software can write 1 to clear this bit to 0. |
| [4] | RSTS_BOD | Brown-out Detector Reset Flag
The RSTS_BOD flag is set by the "reset signal" from the Brown-out Detector to indicate the previous reset source. 0 = No reset from BOD. 1 = The BOD had issued the reset signal to reset the system. Note: Software can write 1 to clear this bit to 0. |
| [5] | RSTS_MCU | MCU Reset Flag
The RSTS_MCU flag is set by the "reset signal" from the Cortex-M0 core to indicate the previous reset source. 0 = No reset from Cortex-M0. 1 = The Cortex-M0 had issued the reset signal to reset the system by writing 1 to bit SYSRESETREQ (AIRCR[2]), Application Interrupt and Reset Control Register, address = 0xE000ED0C in system control registers of Cortex-M0 core. Note: Software can write 1 to clear this bit to 0. |
| [7] | RSTS_CPU | CPU Reset Flag
The RSTS_CPU flag is set by hardware if software writes CPU_RST (IPRSTC1[1]) 1 to reset Cortex-M0 core and Flash memory controller (FMC). 0 = No reset from CPU. 1 = Cortex-M0 core and FMC are reset by software setting CPU_RST to 1. Note: Software can write 1 to clear this bit to 0. |
Definition at line 2681 of file Mini51Series.h.


public abstract class BasicTextUI extends TextUI implements ViewFactory
Basis of a text components look-and-feel. This provides the
basic editor view and controller services that may be useful
when creating a look-and-feel for an extension of
JTextComponent
.
Most state is held in the associated JTextComponent
as bound properties, and the UI installs default values for the
various properties. This default will install something for
all of the properties. Typically, a LAF implementation will
do more however. At a minimum, a LAF would generally install
key bindings.
This class also provides some concurrency support if the
Document
associated with the JTextComponent is a subclass of
AbstractDocument
. Access to the View (or View hierarchy) is
serialized between any thread mutating the model and the Swing
event thread (which is expected to render, do model/view coordinate
translation, etc). Any access to the root view should first
acquire a read-lock on the AbstractDocument and release that lock
in a finally block.
An important method to define is the getPropertyPrefix()
method
which is used as the basis of the keys used to fetch defaults
from the UIManager. The string should reflect the type of
TextUI (eg. TextField, TextArea, etc) without the particular
LAF part of the name (eg Metal, Motif, etc).
To build a view of the model, one of the following strategies can be employed.
create(javax.swing.text.Element)
method.
Warning:
Serialized objects of this class will not be compatible with
future Swing releases. The current serialization support is
appropriate for short term storage or RMI between applications running
the same version of Swing. As of 1.4, support for long term storage
of all JavaBeansTM
has been added to the java.beans
package.
Please see XMLEncoder
.
| Modifier and Type | Class and Description |
|---|---|
static class |
BasicTextUI.BasicCaret |
static class |
BasicTextUI.BasicHighlighter |
| Constructor and Description |
|---|
BasicTextUI()
Creates a new UI.
|
| Modifier and Type | Method and Description |
|---|---|
View |
create(Element elem)
Creates a view for an element.
|
View |
create(Element elem,
int p0,
int p1)
Creates a view for an element.
|
protected Caret |
createCaret()
Creates the object to use for a caret.
|
protected Highlighter |
createHighlighter()
Creates the object to use for adding highlights.
|
protected Keymap |
createKeymap()
Creates the keymap to use for the text component, and installs
any necessary bindings into it.
|
void |
damageRange(JTextComponent tc,
int p0,
int p1)
Causes the portion of the view responsible for the
given part of the model to be repainted.
|
void |
damageRange(JTextComponent t,
int p0,
int p1,
Position.Bias p0Bias,
Position.Bias p1Bias)
Causes the portion of the view responsible for the
given part of the model to be repainted.
|
protected JTextComponent |
getComponent()
Fetches the text component associated with this
UI implementation.
|
EditorKit |
getEditorKit(JTextComponent tc)
Fetches the EditorKit for the UI.
|
protected String |
getKeymapName()
Fetches the name of the keymap that will be installed/used
by default for this UI.
|
Dimension |
getMaximumSize(JComponent c)
Gets the maximum size for the editor component.
|
Dimension |
getMinimumSize(JComponent c)
Gets the minimum size for the editor component.
|
int |
getNextVisualPositionFrom(JTextComponent t,
int pos,
Position.Bias b,
int direction,
Position.Bias[] biasRet)
Provides a way to determine the next visually represented model
location that one might place a caret.
|
Dimension |
getPreferredSize(JComponent c)
Gets the preferred size for the editor component.
|
protected abstract String |
getPropertyPrefix()
Gets the name used as a key to look up properties through the
UIManager.
|
View |
getRootView(JTextComponent tc)
Fetches a View with the allocation of the associated
text component (i.e.
|
String |
getToolTipText(JTextComponent t,
Point pt)
Returns the string to be used as the tooltip at the passed in location.
|
protected Rectangle |
getVisibleEditorRect()
Gets the allocation to give the root View.
|
protected void |
installDefaults()
Initializes component properties, such as font, foreground,
background, caret color, selection color, selected text color,
disabled text color, and border color.
|
protected void |
installKeyboardActions() |
protected void |
installListeners()
Installs listeners for the UI.
|
void |
installUI(JComponent c)
Installs the UI for a component.
|
protected void |
modelChanged()
Flags model changes.
|
Rectangle |
modelToView(JTextComponent tc,
int pos)
Converts the given location in the model to a place in
the view coordinate system.
|
Rectangle |
modelToView(JTextComponent tc,
int pos,
Position.Bias bias)
Converts the given location in the model to a place in
the view coordinate system.
|
void |
paint(Graphics g,
JComponent c)
Paints the interface.
|
protected void |
paintBackground(Graphics g)
Paints a background for the view.
|
protected void |
paintSafely(Graphics g)
Paints the interface safely with a guarantee that
the model won't change from the view of this thread.
|
protected void |
propertyChange(PropertyChangeEvent evt)
This method gets called when a bound property is changed
on the associated JTextComponent.
|
protected void |
setView(View v)
Sets the current root of the view hierarchy and calls invalidate().
|
protected void |
uninstallDefaults()
Sets the component properties that have not been explicitly overridden
to
null . |
protected void |
uninstallKeyboardActions() |
protected void |
uninstallListeners()
Uninstalls listeners for the UI.
|
void |
uninstallUI(JComponent c)
Deinstalls the UI for a component.
|
void |
update(Graphics g,
JComponent c)
Superclass paints background in an uncontrollable way
(i.e.
|
int |
viewToModel(JTextComponent tc,
Point pt)
Converts the given place in the view coordinate system
to the nearest representative location in the model.
|
int |
viewToModel(JTextComponent tc,
Point pt,
Position.Bias[] biasReturn)
Converts the given place in the view coordinate system
to the nearest representative location in the model.
|
contains, createUI, getAccessibleChild, getAccessibleChildrenCount, getBaseline, getBaselineResizeBehavior
protected Caret createCaret()
protected Highlighter createHighlighter()
protected String getKeymapName()
protected Keymap createKeymap()
The set of bindings used to create the keymap is fetched
from the UIManager using a key formed by combining the
getPropertyPrefix()
method
and the string .keyBindings
. The type is expected
to be JTextComponent.KeyBinding[]
.
getKeymapName()
,
JTextComponent
protected void propertyChange(PropertyChangeEvent evt)
evt
- the property change eventprotected abstract String getPropertyPrefix()
protected void installDefaults()
protected void uninstallDefaults()
null
. A property is considered overridden if its current
value is not a UIResource
.protected void installListeners()
protected void uninstallListeners()
protected void installKeyboardActions()
protected void uninstallKeyboardActions()
protected void paintBackground(Graphics g)
g
- the graphics contextprotected final JTextComponent getComponent()
protected void modelChanged()
protected final void setView(View v)
v
- the root viewprotected void paintSafely(Graphics g)
g
- the graphics contextpublic void installUI(JComponent c)
null
or an instance of
UIResource
.
installUI
in class ComponentUI
c
- the editor componentComponentUI.installUI(javax.swing.JComponent)
public void uninstallUI(JComponent c)
uninstallUI
in class ComponentUI
c
- the editor componentComponentUI.uninstallUI(javax.swing.JComponent)
public void update(Graphics g, JComponent c)
NOTE: NOTE: Superclass is also not thread-safe in its rendering of the background, although that is not an issue with the default rendering.
update
in class ComponentUI
g
- the Graphics
context in which to paintc
- the component being painted;
this argument is often ignored,
but might be used if the UI object is stateless
and shared by multiple componentsComponentUI.paint(java.awt.Graphics, javax.swing.JComponent)
,
JComponent.paintComponent(java.awt.Graphics)
public final void paint(Graphics g, JComponent c)
paint
in class ComponentUI
g
- the graphics contextc
- the editor componentComponentUI.update(java.awt.Graphics, javax.swing.JComponent)
public Dimension getPreferredSize(JComponent c)
getPreferredSize
in class ComponentUI
c
- the editor componentJComponent.getPreferredSize()
,
LayoutManager.preferredLayoutSize(java.awt.Container)
public Dimension getMinimumSize(JComponent c)
getMinimumSize
in class ComponentUI
c
- the editor componentJComponent.getMinimumSize()
,
LayoutManager.minimumLayoutSize(java.awt.Container)
,
ComponentUI.getPreferredSize(javax.swing.JComponent)
public Dimension getMaximumSize(JComponent c)
getMaximumSize
in class ComponentUI
c
- the editor componentJComponent.getMaximumSize()
,
LayoutManager2.maximumLayoutSize(java.awt.Container)
protected Rectangle getVisibleEditorRect()
public Rectangle modelToView(JTextComponent tc, int pos) throws BadLocationException
modelToView
in class TextUI
tc
- the text component for which this UI is installedpos
- the local location in the model to translate >= 0BadLocationException
- if the given position does not
represent a valid location in the associated documentTextUI.modelToView(javax.swing.text.JTextComponent, int)
public Rectangle modelToView(JTextComponent tc, int pos, Position.Bias bias) throws BadLocationException
modelToView
in class TextUI
tc
- the text component for which this UI is installedpos
- the local location in the model to translate >= 0BadLocationException
- if the given position does not
represent a valid location in the associated documentTextUI.modelToView(javax.swing.text.JTextComponent, int)
public int viewToModel(JTextComponent tc, Point pt)
viewToModel
in class TextUI
tc
- the text component for which this UI is installedpt
- the location in the view to translate. This
should be in the same coordinate system as the mouse events.TextUI.viewToModel(javax.swing.text.JTextComponent, java.awt.Point)
public int viewToModel(JTextComponent tc, Point pt, Position.Bias[] biasReturn)
viewToModel
in class TextUI
tc
- the text component for which this UI is installedpt
- the location in the view to translate. This
should be in the same coordinate system as the mouse events.biasReturn
- filled in by this method to indicate whether
the point given is closer to the previous or the next
character in the modelTextUI.viewToModel(javax.swing.text.JTextComponent, java.awt.Point)
public int getNextVisualPositionFrom(JTextComponent t, int pos, Position.Bias b, int direction, Position.Bias[] biasRet) throws BadLocationException
getNextVisualPositionFrom
in class TextUI
t
- the text component for which this UI is installedpos
- the position to convert >= 0b
- the bias for the positiondirection
- the direction from the current position that can
be thought of as the arrow keys typically found on a keyboard.
This may be SwingConstants.WEST, SwingConstants.EAST,
SwingConstants.NORTH, or SwingConstants.SOUTHbiasRet
- an array to contain the bias for the returned positionBadLocationException
public void damageRange(JTextComponent tc, int p0, int p1)
damageRange
in class TextUI
tc
- the text component for which this UI is installedp0
- the beginning of the range >= 0p1
- the end of the range >= p0TextUI.damageRange(javax.swing.text.JTextComponent, int, int)
public void damageRange(JTextComponent t, int p0, int p1, Position.Bias p0Bias, Position.Bias p1Bias)
damageRange
in class TextUI
p0
- the beginning of the range >= 0p1
- the end of the range >= p0public EditorKit getEditorKit(JTextComponent tc)
getEditorKit
in class TextUI
tc
- the text component for which this UI is installedTextUI.getEditorKit(javax.swing.text.JTextComponent)
public View getRootView(JTextComponent tc)
NOTE:The View hierarchy can be traversed from the root view, and other things can be done as well. Things done in this way cannot be protected like simple method calls through the TextUI. Therefore, proper operation in the presence of concurrency must be arranged by any logic that calls this method!
getRootView
in class TextUI
tc
- the text component for which this UI is installedTextUI.getRootView(javax.swing.text.JTextComponent)
public String getToolTipText(JTextComponent t, Point pt)
getToolTipText
in class TextUI
JTextComponent.getToolTipText(java.awt.event.MouseEvent)
,
View.getToolTipText(float, float, java.awt.Shape)
public View create(Element elem)
create
in interface ViewFactory
elem
- the elementView
public View create(Element elem, int p0, int p1)
elem
- the elementp0
- the starting offset >= 0p1
- the ending offset >= p0 Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.


You may exchange or return merchandise purchased on Bliiq for a full refund,
(shipping fee is not refundable), based on original form of payment, within 30 days of the
purchase date.
If the product is unopened, it can be exchanged at any time. You are responsible for the
shipping charges incurred both on your original order as well as the charges to get the
product back to us. If your item has been opened or used, restrictions (such as
restocking fee) may apply.
If you believe you have received a defective product upon arrival, please contact us
immediately at 1-855-205-8370 7AM-7PM MT M-F for further instruction.
Have questions? Please Email us, we will get back to you within 1-2 business days.
WAREHOUSE / WARRANTY
Bliiq Return Department
11877 Douglas Rd STE 102-243
Alpharetta GA 30005
Shipping a return? Please also include RMA number above the address field. Obtain an RMA number by contacting customer experience, or submitting a return request/warranty claim.


Can a Neural Network recognize sketch drawings?
SketchCNN is a Convolutional Neural Network that can recognize sketch drawings.
Trained on millions of examples from Quick Draw dataset it can recognize sketches across over 100 different categories.
The classes that can be recognized are:
hourglass remote_control traffic_light face cake laptop toothpaste postcard strawberry hamburger
train television shoe castle baseball_bat elephant sword map hammer streetlight
pizza book mug tooth umbrella lightning dragon paint_can light_bulb basket
knife hat firetruck basketball pants drums keyboard popsicle octagon teapot
rainbow guitar envelope skateboard paintbrush stairs suitcase tennis_racquet shorts truck
toothbrush car door star bread mailbox smiley_face cell_phone nail mountain
microphone snowman tornado fish telephone eyeglasses sun binoculars floor_lamp t-shirt
windmill washing_machine key compass ladder saw bed grapes pineapple pencil
ice_cream hot_air_balloon coffee_cup leaf skyscraper snowflake dumbbell pillow wheel house
anvil lighthouse teddy-bear scissors axe rifle radio lantern alarm_clock stop_sign submarine
"Sketch" recognizes a single sketch and outputs the first 5 classes with highest probabilities.
The accuracy is increased by not converting to a tensor the entire canvas but only the minimum bounding box of the sketch.
"MultiSketch" recognizes multiple sketches and outputs the class with the highest probability.
There are two methods to find the sketches in the canvas; first is combining the bounding boxes of the different strikes used in the sketches
in order to find the minimum bounding box for each. The second method uses K-means algorithm to find the clusters of the different sketches.
This requires, however, the user to input the number of sketches they draw on the canvas.
I've tried using the elbow method to automatically pick the correct number of clusters but as good as it sounds in theory there is
no guarantee that while iterating over the number of clusters and computing the SSE each and every single one of them ends in the global minimum.
Actually, even with the user inputing the number of clusters and the clusters being chosen at the same position as random input datapoints many times the
K-means algorithm will end up in a local minimum.


Read time: 3.2 minutes (319 words)
Tracing Sphinx Domain Directives¶
Sphinx domains provide a kind of namespace for a collection of directives that extend Sphinx. They were designed to support documenting a number of languages, but can be used to manage other extensions as well.
PyLiT will provide a number of directives that control processing of reStructuredText blocks. In order to design a domain for this purpose, we need to figure out how domains work. That means (unfortunately) spending some time doing that “read the code” work and trying to decipher what is going on.
We begin building a new domain for Sphinx by setting up the basic class. This domain will be named pylit and will support one code directive to get started.
The package we are building is named sphinxcontrib-pylit, and can be imported using sphinxcontrib.pylit. Our starting directory structure is set up first:
$ mkdir -p sphinxcontrib.pylit
$ touch sphinxcontrib/__init__.py
$ touch sphinxcontrib/pylit/__init__.py
Sphinx Startup¶
When Sphinx first starts an instance of the Application class is created. Part of that process sets up a registry where application data is stored. After loading all built-in extensions, the user defined extensions found in the configuration file are imported and recorded in the registry.
The extension loading process first check to see if this extension has already been loaded. If not, it tries to import the named extension. If that works, it checks to see if a setup function exists in the extension and that routine is called with the current application instance as a parameter. The setup function can return a metadata dictionary or None. Once all of this succeeds, the new extension is recorded in app.extensions along with all other built-in and user extensions. The new entry is an instance of the Extension class.
The sequence of calls to perform all of this is as follows:
application
__init__.py ->
self.registry =SphinxComponentRegistry()
for extension in self.config.extensions:
self.setup_extension(extension)
setup_extension(extension)
self.registry.load_extension(self, extension)
registry
load_extension(app, extension)
mod = import_module(extension)
setup = getattr(mod, 'setup', None)
meta = setup(app)
app.extensions[extension] = Extension(extension, mod **metadata)
extension object
self.name = extension name
self.mod the imported module
self.metadata
self.version if any
A simple test of proper extension setup would involve checking that the new extension is imported and listed in the app.extensions list.
Sphinx Domain API¶
Setting up a basic domain is pretty simple. All we need is a class that inherits from the SphinxDomain class:
from sphinx.domains import Domain
class PylitDomain(Domain):
name = 'pylit'
label = "Literate Programming for Sphinx'
roles = {
'pilitref': XRefRole()
}
directives = {
'code': Pylitnode,
}
indices = {
PylitIndex,
}
initial_data = {
'pylit_blocks': [],
In the extension setup function, any defined domains are loaded through app.add_domain() method.


Date: Fri, 8 Jun 90 19:55 EDTFrom: David A. Moon<EMAIL_ADDRESS>Subject: Issue: CLOS-CONDITIONS-AGAIN (Version 6)
To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>This version includes the amendment that was passed at the X3J13 meeting today.
Issue: CLOS-CONDITIONS-AGAIN
References: ANSI CL draft specification, page 5-4
Related issues: CLOS-CONDITIONS
Category: ADDITION and CHANGE
Edit history: 30-Apr-90, Version 1 by Moon (for Pitman)
30-Apr-90, Version 2 by Moon (deal with slots)
2-May-90, Version 3 by Pitman (minor wording clarifications)
2-May-90, Version 4 by Moon (final check for typos)
5-Jun-90, Version 5 by Moon (mention multiple inheritance)
8-Jun-90, Version 6, by Moon (as amended at X3J13 meeting)
Problem description:
The condition system should not be too tightly integrated into CLOS, for
two reasons: Some implementations already have a native condition system
that is not based on CLOS, and it should be possible to integrate the
native conditions and the ANSI CL conditions. Some people would like to
define an ANSI Common Lisp subset that does not contain CLOS but does
contain conditions.
The problem areas are the use of DEFCLASS, MAKE-INSTANCE, and DEFMETHOD
to define and create conditions, rather than using more abstract macros
that conceal the implementation of conditions in terms of CLOS, and
exposure of the implementation of condition slots as CLOS slots. If user
code was written in a more abstract way, it could run in a subset language
that did not contain CLOS.
This is Symbolics issue #7.
Proposal (CLOS-CONDITIONS-AGAIN:ALLOW-SUBSET):
1. Specify that conforming code must use DEFINE-CONDITION (not DEFCLASS)
to define conditions, and MAKE-CONDITION (not MAKE-INSTANCE) to make
conditions. (These two operators already exist in ANSI Common Lisp.)
2. Specify that conforming code must use the :REPORT option of
DEFINE-CONDITION (not DEFMETHOD for PRINT-OBJECT) to define a condition
reporter.
3. Specify that conforming code must not use SLOT-VALUE, SLOT-BOUNDP,
SLOT-MAKUNBOUND, or WITH-SLOTS on condition objects. Instead it must
call the accessor functions defined by DEFINE-CONDITION.
4. Clarify that this proposal does not rule out the use of multiple
parent-types in DEFINE-CONDITION.
Rationale:
1. The reasons are two:
- permit flexibility in making the native class system compatible
with the ANSI CL one
- permit dialects that don't want CLOS to be available to run most
common condition-related code.
2. The reasons are three:
- isolate the report part without forcing the user to deal with the
case of *PRINT-ESCAPE* being true.
- keep a CL subset from having to implement DEFMETHOD to get this
important functionality.
- don't define two ways to do the same thing.
3. Using the existing accessor functions seems more conservative than
requiring non-CLOS subsets to implement an ersatz SLOT-VALUE function.
Note also that the requirement here (in #3) is on conforming -code-.
An -implementation- can permit the use of SLOT-VALUE, SLOT-BOUNDP,
SLOT-MAKUNBOUND, and/or WITH-SLOTS as an extension and still be
conforming. Programs which used such an extension would not be
conforming and might not be portable to all implementations.
4. There is no substitute for multiple inheritance, and given the
limited set of operations that can be performed on conditions, it
is easy to fake it.
Current practice:
1. DEFINE-CONDITION and MAKE-CONDITION are already in the language.
2. The :REPORT option to DEFINE-CONDITION exists.
3. Some implementations support use of WITH-SLOTS and some do not.
Programs that use WITH-SLOTS are not yet portable.
4. DEFINE-CONDITION is already specified to support multiple inheritance.
Cost to Implementors:
Trivial.
Cost to Users:
They have to write their programs in terms of the condition abstractions
if they want them to be portable.
Cost of non-adoption:
Condition-using programs will not be portable to Common Lisp subsets that
don't have CLOS.
Performance impact:
None.
Benefits:
See rationale.
Esthetics:
Abstraction is more esthetic than revealing the implementation.
Discussion:
Pitman and Moon support this proposal.


lb slc loopback
apic loopback
| Application generator
| Create a new LoopBack application. |
lb bluemix
apic bluemix
| Bluemix configuration generator
| Add Bluemix deployment artifacts to a LoopBack application. |
lb datasource
slc loopback:datasource apic create --type datasource
| Data source generator
| Add a new data source to a LoopBack application. |
lb model
slc loopback:model apic create --type model
| Model generator
| Add a new model to a LoopBack application. |
lb property
slc loopback:property apic loopback:property
| Property generator
| Add a new property to an existing model. |
lb acl
slc loopback:acl apic loopback:acl
| ACL generator
| Add a new access control list (ACL) entry to the LoopBack application. |
lb relation
slc loopback:relation apic loopback:relation
| Relation generator
| Add a new model relationship. |
lb remote-method slc loopback:remote-method apic loopback:remote-method
| Remote method generator
| Add a new remote method.. |
lb middleware slc loopback:middleware apic loopback:middleware
| Middleware generator
| Add a new middleware configuration. |
lb boot-script< slc loopback:boot-script apic loopback:boot-script
| Boot script generator
| Add a new boot scripts. |
lb export-api-def slc loopback:export-api-def apic loopback:export-api-def
| API definition generator
| Export Swagger API definition. |
lb swagger slc loopback:swagger apic loopback:swagger
| Swagger generator
| Generates a fully-functional application that provides APIs conforming to the Swagger 2.0 specification. |
apic loopback:refresh |
Refresh definitions command |
Generate a product and an OpenAPI (Swagger) definition |
lb soap |
SOAP generator |
Generate application artifacts based on WSDL file. |


Organic Source
Our palm Dates trees are grown in climatic areas with rich soil. which will give the body high nutritional value.
Fast Shipping
We make sure you recieve your order as soon as we have finished packging it.
Quality Assurance
For every purchase you make, we will ensure there are no damages or faults.


NARS: Non-Axiomatic Reasoning System
What is NARS?
Logic
NAL 0
NAL 1
NAL 2
Development
NARS
About
Logic
Development


World Out of Bounds is a new, intriguing way for people to understand the practices of different cultures around the globe. Each issue focuses on a different region of the world, where the top journalists will uncover the various ‘taboos’ practiced in those regions. Articles will include, but are not limited to: cuisine, marriage, coming of age practices, taboos of that region, medical practices, and so much more. The mission is to bring to light the different practices and start and new age of acceptance and understanding.
Don’t be limited to the cultural ‘norms’ in the United States, get out of bounds and experience the knowledge and adventure World Out of Bounds has to offer.


Buttons:
Simple button
Button 1
Div based button
Button 2
Div based button with width attribute set on initial node
Button 3
Expando button using animation
Button 4
Super expando who's definition only needs to override the animation from Expando. Everything else is inherited.
Button 5
All of these extend from one another making slight changes to template or actions.


ATHANDIA
New Projects
Account Setting
Notification
Favorite Projects
Search for Others'
My Projects
TITLE
OWNER
SUBJECT
Physics
Maths
Chemistry
Biology
Computer Science
Engineering
Social Science
Environmental Science
ABSTRACT
EVERY JOURNEY
STARTS WITH
A SINGLE STEP
Add details to your new project!
CANCEL
SUBMIT


Chapter 4 Community & Outreach
Researchers in academia and national labs are incentivized to become experts in one or more specialized domains. While research software plays a critical role in achieving such mastery, skills to develop such software are rarely taught in formal settings. These skills are often picked up from secondary special interest communities and online resources. We plan to formalize such community resources and associated activities in our institute plans.
The institute’s Community area will build a thriving community of like-minded peers for researchers to seek advice, learn about training opportunities, and funding announcements. A community manager will curate state of the art information on best practices for research software development. We will work closely with The Center for Scientific Collaboration and Community Engagement (CSCCE) to train a research engineer who seeks to pursue a career in community management. CSCCE specalizes in professionalizing scientific community building and their training program can be completed while the community manager is getting started with their position. The Community area will also administer a competitive fellowship program for early career researchers. These fellowships will provide funding, training, and prestige/recognition to pursue a career that promotes the development and use of research software. The thriving community will also provide venues and annual conference focused on software across disciplines where researchers can share their work, learn about new software, and software development techniques.
Many of the current challenges around sustainability of software, and those who produce it, are mostly social and cultural and not limited by any unassailable technical challenges. While other areas of the institute such as Policy and Education & Training lay down the guidelines and training necessary to grow the research software enterprise, a strong community strategy will be key to maintaining it. URSSI will act as the hub for all types of researchers interested in using and developing research software. The institute will provide necessary resources to address shared challenges and help catalyze collaborations to tackle emerging problems. URSSI’s Community & Outreach area will achieve this mission through the set of activities described below.
4.1 Community & Outreach Resources
Managing the URSSI community will require the following staff and resources:
Managing communications (website with regular posts, moderating a mailing list), producing high quality newsletters, and acting as a community liaison will require 2-3 FTEs.
This could involve a Director of Community (could be part of a PI’s time), with the remaining part of the area’s workforce split over two positions: a community manager and fellowship coordinator (to be split with the Incubator Area), reporting to the Director of Community. We will work closely with The Center for Scientific Collaboration and Community Engagement to recruit one of their scientific community manager trainees as a fellow. We may also recruit someone who will undergo their training upon joining URSSI.
Besides the budget for the 2-3 positions, the Community & Outreach area of the institute will also require budget for:
Technical infrastructure (including: website, mailing list, archiving of resources). Maintaining a high quality newsletter will require access to high quality data feeds, all of which require paid subscriptions. The team will also require technical help to maintain a static site on GitHub.
One URSSI fellow (as part of a cohort of 4-5 fellows/year) can be asked to focus on community. Much like the BSSW fellowship, an URSSI fellow can propose a community related topic to pursue for the year of their fellowship.
Participant support for fellows and speakers to attend annual meetings
Base costs for an annual URSSI conference (with the rest to be supported by registration and sponsorships)
4.2 Community & Outreach Methods
4.2.1 Fellowship Program
URSSI will run an annual fellowship program modeled heavily on the successful program run by the UK Software Sustainability Institute (Sufi and Jay 2018). We will recruit 3-5 fellows from a pool of US graduate students, postdocs, and research software engineers. Since research software suffers from a lack of diversity, the fellowship selection process committee will focus on providing opportunities for candidates from underrepresented groups. The community team will rely on existing research and tools on candidate selection to make decision making transparent and free from human biases as much as possible (Huppenkothen, McFee, and Norén 2020). One of the criteria used to select fellows will be a diversity statement that fellows will be required to submit, and ~50% of the selected fellows will be members of underrepresented groups, with a lower bound of 25%. Each fellow will affiliate with one or more areas of URSSI (Policy, Education, Community, Incubator) and propose an activity that would take no more than 1 day a week of their time. Fellowship stipend will provide an appropriate time buyout and also cover travel to biannual collaborations workshops, and the annual URSSI conference. Fellows will be given an additional travel budget to present their research software activities at society and discipline conferences. Each fellow will be paired with an URSSI mentor and success will be based on entry and exit interviews.
The fellowship program is aimed at the people and careers portion of URSSI’s impact goals.
4.2.2 In-person events
Create new community events: Building upon the work of small workshops such as Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE), there is an opportunity for URSSI to host an annual in-person conference for scientists, developers, and students to connect and discuss research software development and their applications. One of the criteria used to select funded attendees will be a diversity statement that applicants will be required to submit, and at least 25% of the selected applicants to be funded will be members of underrepresented groups. The conference will initially be medium sized (with a limit of 300 participants) and grow depending on the interest. Talks and workshops will span the entire continuum from applied computational research to software development. The event will also feature a “demo day” for URSSI incubated projects, which would be a cross cutting activity with the Incubator program. The costs for such an event will be supplemented by a mix of registration fees and sponsorships.
In-person events are aimed at the people and careers and research software ecosystem portions of URSSI’s impact goals.
4.2.3 Online community events
Promote existing activities: One of URSSI’s strengths will lie in amplifying the work of existing initiatives. We will achieve this by showcasing projects in our weekly newsletter, by inviting projects to present their work on monthly community calls (aka webinars), and by highlighting/crossposting news via partner organizations such as the Carpentries, rOpenSci, Workshop on Sustainable Software for Science (WSSSPE), Mozilla, and others. The community manager will work with various parters and data feeds to curate and disseminate a high quality newsletter similar to the the data science newsletter operated by the Academic Data Science Allaince (ADSA). The institute will budget for costs associated with newsfeed subscriptions.
Community calls: Modeled after the successful series organized by Mozilla and rOpenSci, a monthly webinar series will expose researchers to the latest best practices and new trends in research software, and will provide them an opportunity to interact with prominent research software engineers. This free and open series will provide additional opportunity for the community to participate, especially for those that are constrained by travel. Past calls, including videos, code, and Q&A will be archived and made searchable by a dedicated community coordinator. We will consider diversity when chosing participants who will present in these calls, and seek to have at least 25% of the presenters being members of underrepresented groups.
Online community events are aimed at all three portions of URSSI’s impact goals: research software sustainability, people and careers, and the research software ecosystem.
4.2.4 Curating and disseminating best practices
URSSI fellows will convene ad hoc panels of experts to curate information on state of the art practices for scientific computing. The topics will cover many foundations of research software engineering including but not limited to collaborative software developing with modern version control, software testing, code review, packaging and distribution, and overall software design. The materials will also provide strong guidance on open science practices to increase impact of such work. These include guidance on licensing, properly archiving research software, and citation.
Curating and disseminating best practices is primarily aimed at the research software sustainability portion of URSSI’s impact goals, and secondarily at the people and careers and research software ecosystem portions.
4.2.6 Other activities
Besides the activities described above, the institute will feature these ongoing activities:
- URSSI will serve as a broker for software expertise and connect developers to scientific projects seeking contractors, expert advice or collaborators on grants. The community team will coordinate some combination of a job/skills board to better leverage expertise among US institutions. [TODO: Flesh out details of this program]
- Promote training events from URSSI and other communities
- Develop an ambassador program for early career researchers to promote sustainable software and current issues to their local communities. Examples of similar programs include the Campus Champions program at XSEDE, and the SSI fellows program (Sufi and Jay 2018).
An URSSI ambassador program will be a light touch activity (less engaged than the fellows program) and provide students at US colleges and universities with resources to support campus colleagues effectively use research software to advance their research. The program will provide a venue to build community among early stage students (advanced undergraduates, beginning graduate students). One of the criteria used to select ambassadors will be a diversity statement that potential ambassadors will be required to submit, and at least 25% of the ambassadors will be members of underrepresented groups.
- Hosting a blog, with a series of staff and guest blog posts, including cross-posting relevant blog posts from others
4.3 Community & Outreach Assessment and Metrics
Goals:
- Steadily grow the number of subscribers and participants each year
- Grow the diversity of participants, instructors, and speakers each year. Self reported data on affiliations and domains of expertise will also provide a measurable metric of impact across domains.
- Grow the number of applications we receive for the fellowship program every year
- Grow the rate of paper and poster submissions every year
- Improve the careers of those who participate in URSSI
Metrics:
- Number of subscribers to the newsletter, visitors to the website, and social media followers over time
- Quantify instructors, presenters, lesson developers, and participants by demographic and geographic breakdown
- Count citations of software that have participated in URSSI
- Tracking career paths of fellows will also act as a measure of success for the program
Impacts:
This table maps URSSI activities from this chapter to the three portions of URSSI’s intended impact. (A complete table of impacts from all URSSI activities can be found in Chapter 10 (Metrics and Evaluation).) In the impact cells, X indicates a designed primary impact on an activity, and y indicates a designed secondary impact.
| Activity | Impact on Research Software | Impact on people and careers | Impact on research software ecosystem |
|---|---|---|---|
| Fellowships | X | ||
| In-person events | X | X | |
| Community calls | X | X | X |
| Curate best practices | X | y | y |
| Newsletter & social media | y | X |


Nctu Dcat Web Design
Web Design
Overview
This is a web design project. I redesigned the official website of the Communication Technology Department of NCTU. By understanding the teaching philosophy and characteristics that the department wants to show, reconstruct the interactive map and information architecture from the old website structure, and convey the personality and style of the department with a brand new visual appearance.
Role
Designer
Illustrator, XD, After Effects, Photoshop
March 2018 - September 2019
Background
In the Department of Communication and Technology, NCTU, information and communication technology continue to innovate, which not only brings digital convergence but also blurs the boundaries between traditional media. As the only Department of Communication and Science and Technology in Taiwan, it emphasizes the integration of communication majors, interdisciplinary, and multi-skill learning.
Design Process
Concept
Using bright and vivid main colors, overlapping geometric figures echo each other, fusing different textures and textures, and presenting gradation effects, trying to visually show the concept of this department-the combination of "humanities, technology, and creativity".
Details
The whole website uses the main visual element and design to create motion graphics showing the different themes.
Mobile UI
Responsive web design (RWD) makes web pages render well on a variety of devices and window or screen sizes.


Login
MORE THAN 30 MILLION AMERICANS ARE LIVING WITH DIABETES
Find the best insurance for you to live with diabetes
Find Your Formulary
Complete Form Below
Receive Your Specific Results
Find the Current Price Tier for Your Medications
Type 1 Diabetes
Type 2 Diabetes
Please select the insurance provider you are providing information about:
BlueCross BlueShield
Etna Group
Humana Group
United Health
Medicare
Fill in the blank
Please indicate the plan year you are providing information for:
Do you use insulin?
Yes
No
Which fast-acting insulin do you use?
Lispro (Humalog)
Aspart (Novolog)
Glulisine (Apidra)
Which slow-acting insulin do you use?
Detemir
Flargine
Degludec
How do you inject fast acting and slow acting insulin?
Pens/Tips
Vials/Syringes
Pump
What size do you need (Length)?
12.7 mm
4 mm
What size do you need (Gauge)?
32G
28G
What volume do you need?
3/10cc
1/2cc
1cc
Which provider do you get your pump from?
Medtronic
Tandem
Insulet
Animas
Roche
Sooil
Which pills do you take?
None
Biguanides
Metformin (Glucophage)
Metformin liquid (Riomet)
Metformin extended release
Email address
We'll never share your email with anyone else.
Subcribe to email notifications?
Yes
No
Create account for more details?
Yes
No
Password
Telephone
Review My Options


The Undertaker reveals why he changed his gimmick during The Attitude Era
by Abhilash MendheThe premiere of Stone Cold Steve Austin's "The Broken Skull Sessions" is on the horizon, and WWE has been giving us several sneak peeks into the episode, via its Youtube channel. A new clip has just been uploaded on the channel, which shows Mark Calaway talking about his transformation to The American Bada** in May 2000.
After a short hiatus in early 2000, The Undertaker made his WWE return in May, and came out donning a completely different gimmick. The Phenom had taken a biker identity, and was sporting bandanas and sunglasses. He also began coming down to the ring on a motorcycle. This drastic change in character was hailed by many, though there were some who weren't too thrilled with it.
Also read: Vince McMahon still haunted by 6-time World Champion joining AEW, says former WWE announcer
While speaking with Steve Austin on the premiere of "The Broken Skull Sessions", Mark Calaway revealed why he made the transition to The American Bada**.
I always felt like if I started feeling stale, my audience is probably feeling it before me, 'cause you get wrapped up in what you're doing. So, the small changes, the breaks at the right time. But I don't think I would've made it through if I hadn't changed when I did go to "The American Bada**". The character, I don't think would've lasted through The Attitude Era.
We want to know what you think of the matches that you see on TV! Go to our WWE page here and rate and comment what you thought of them!


Create or replace resources from their YAML or JSON definitions. If adding a template, you'll have the option to process the template.


This site works best if JavaScript is enabled in your browser.
!!
✓
>>
#
~
🔎
✨
⤺
⤻
👁
👁
👁
☰
×
×
✓
!!
!
×
!!
×
×
nbsp;
×
×
×
×
:
:
:
×
QQQQ
✓
!!
!
×
:
:
:
×
Show BlocklyProp-Client (older) downloads
×
Show BlocklyProp-Client (older) downloads


Catering is an act,that involves the making and delivering of food. The perfect preparation of food starts from the cleaniness of your raw food stuffs There are several methods in preparation of food, the method varries according country or locality but the best food always bring out joy in people. The earliest account of major services being catered in the United States is a 1778 ball in Philadelphia catered by Caesar Cranshell to celebrate the departure of British General William Howe.Catering business began to form around 1820, centering in Philadelphia.Catering became a respectable and profitable business.Does working hard in the kitchen while everyone else is eating, drinking and socializing in the living room sound like your idea of a good time? If your goal is to be in the catering business, the answer should be an emphatic yes.Americans' love of dining and entertaining has created a tremendous market for off-premises caterers all across the country. A wide range of social and business events are providing an opportunity for caterers to cook up tasty dishes and delicious
we offer the best services and satisfactory to our customers, we entertain and study our customers to give them the best services they want at every particular time.
do not heistate to contact us:
I_crunchy Services,22nd Rudey Road, New York.
you can also contact us on 01234567 or email: i_crunchy@foods.co


Interfaces describing functional objects.
Functional objects need to implement these interfaces in order to interact with numericalMethods.
For example, an object somefunction
representing a real
function of several real variables would implement the interfaces
{@link numericalMethods.function.DoubleValued} and {@link
numericalMethods.function.DoubleArrayParametrized}. A method which
minimizes such a function would have the signature
minimize({@link
numericalMethods.function.DoubleArrayParametrized} p, {@link
numericalMethods.function.DoubleValued} v, double[] initialGuess)
.
To minimize the function represented by someFunction
,
one would invoke
minimize(someFunction, someFunction, someInitialGuess)
.


|
VItA
1.1
Virtual Iterative Angiogenesis library
|
#include <DistributionGenerator.h>
Public Member Functions | |
| DistributionGenerator () | |
| virtual | ~DistributionGenerator () |
| virtual void | initialize (int seed, double *boundingBox) |
| virtual vector< point > | getNPoints (int n)=0 |
Protected Attributes | |
| double * | boundingBox |
| mt19937 | generator |
Abstract generator of points.
| DistributionGenerator::DistributionGenerator | ( | ) |
Constructor
|
virtual |
Destructor
|
pure virtual |
Return a vector of n
points of the distribution.
| n | Amount of output points. |
Implemented in NormalDistributionGenerator, CompositeDistributionGenerator, and UniformDistributionGenerator.
|
virtual |
Initializer of the generator. Execute it before any getter call is performed.
Reimplemented in NormalDistributionGenerator, CompositeDistributionGenerator, and UniformDistributionGenerator.
|
protected |
Bounding box of the domain where the points will be generated.
|
protected |
Random generator.


Tycho is structured as a set of independently installable and releasable packages. The package mechanism is a simple extension to the Tcl package mechanism to support nested packages. The mechanism is designed to allow installation and loading of arbitary subsets of Tycho. Tycho can thus be used as:
Contents
The Tycho package is the top-level package, and will always be installed if you are using any of the Tycho packages (except those that are noted to be completely independent of Tycho). The Tycho package includes a few [incr Tcl] files that are used for installing and locating packages, and for starting up Tycho as a stand-alone application. The Tycho package is usually contained in a directory named tycho (the generic name) or something like tycho0.2.1devel (the current development version).
The Tycho package provides the "bootstrap" mechanism that finds all other packages contained within the tycho directory. (Note that Tycho packages do not have to be installed into the tycho directory, as long as Tcl can find them -- installing them into tycho, however, guarantees that they will be found!) When a script executes a package require command, and the required package is not yet known to Tcl, Tcl will find the tycho directory and source the file pkgIndex.tcl. This file in turn searches the tycho directory for packages.
In order to make sure that Tcl can find the tycho directory, either that directory or its parent must be in the tcl variable auto_path. Here are two ways to ensure that this is so:
file dirname [info library]itkwish, when started, will know about all packages in the tycho directory. itclsh will not, so scripts that run in itclsh will need to do a package require Tycho before attempting to load any other Tycho packages.
lappend auto_path $env(TYCHO)before doing a package require on any Tycho packages. All of the scripts provided in the standard Tycho installation for running Tycho stand-alone check for the TYCHO environment variable before requiring Tycho packages.
Note that you do not have to install any of these packages:
the top-level Tycho package can be used simply as a convenient
way of structuring your own packages, if you wish.
Location of Tycho packages
Packages can be located anywhere within the Tycho directory,
provided that the package searcher can find them. In order
to make sure that this is so, each package must
If you have Tycho installed, and you are creating your
own [incr Tcl] application, you can create a package within
the
Making a Tycho package
Tycho packages follow the standard rules for Tcl packages.
In each package, create a pkgIndex.tcl file. Typically,
this file contains something like this:
package ifneeded Kernel 0.1 \ [list source [file join $dir kernel.tcl]]where Kernel is the name of the package, 0.1 is its version number, and kernel.tcl is the package load file (see below).
In that same directory, create the package load file, which will be sourced in response to a package require on that package. This file typically contains something like this:
package require Tycho package provide Kernel 0.1 lappend auto_path [file dirname [info script]] set ::tycho::packages(Kernel) [file dirname [info script]]The first line states this package requires the top-level Tycho package. Packages that implement graphical applications will typically require the TFC package instead of Kernel.
The second line tells Tcl that Kernel is being provided. The third ensure that the files in the package can now be auto-loaded on demand.
The final line is required so that Tycho installation and
configuration scripts know what directory the package was loaded
from. Additional initialization code can be added after that -- for
example, applications packages typically call the
::tycho::register procedure in TFC to associate file extensions
with code to open files with those extensions.
Using Tycho packages
Any script that starts Tycho, whether as a stand-alone
application or as a part of another application, will need
to do a package require on at least one Tycho
package. There are three main cases:
package require Tycho ::tycho::startThis loads the top-level Tycho package, and then calls a procedure that starts Tycho as an application. ::tycho::start takes arguments that can be used to control how Tycho starts and what packages it loads. By default, it loads all known Tycho packages, but this can be turned off. If the script has been started as a shell script, then the procedure ::tycho::processCommandLine can be used to convert command-line arguments into a form suitable for use by ::tycho::start.
package require Kernelwhile a graphical utility would call at least
package require TFCSome utilities may require other Tycho packages; as long as they are installed, the application can load them with, for example,
package require HTML package require SlateA number of the Tycho packages themselves provide stand-alone applicatins in this manner. For example, the scripts that generate class diagrams and extract documentation from code do this.
package require Slate package require HTMLbefore attempting to use the facilities of these packages, and these facilities will be loaded for use by your application.


Who's this guy?
| $ echo \| $ > 'Full Stack Developer' 🁢
Python • JavaScript • NodeJS • TypeScript • Java-core • HTML5/CSS3/LESS • SQL • NoSQL
AWS • GCP • Docker • Kubernetes • Git • Adobe Suite • Jira • VSCode • VirtualBox
OS Familiarity
Linux, MacOS, Windows, Android, iOS
Full stack software engineer
Born in India. Living in San Francisco
Raised by 90’s
4 years of work Experience
Now available for you
Designed and developed a custom Incremental Backup strategy, reducing the machine work hours of 8 hrs run to only 30 min
Tech stack: Shell, Typescript, MongoDB
Developed a cross language automated alert system for critical machine failures, defined over a mapped error code alarm messaging microservice.
Tech stack: Typescript, Python, C++, Matlab
Designed multiple bots as a service to work with git workflows and integrations.
Tech stack: Python, Jenkins, Github Actions, Slack API
Built a log interpreter to emulate browser user interactions for in-depth debugging.
Tech stack: Js, V8 Engine, Jest, Jasmine
One click feature to clone application configurations in different environments which led to significant decrease in configuration time.
A social network for horses
Tech Stack: Nodejs, ReactJs, Docker and kubernetes, web accelerator - caching
A WebApp for data visualization and data modeling of real – time data from telecom sensors deployed across Australia with functional Artificial Intelligence and analytics. A white-label product ready to be redeployed with a single
click creating a raw server less
Tech Stack: Python, React.js, AWS DynamoDB, S3, IAM and CloudFront
A Social Data intelligence Android, iOS and JAVA Backend application aggregating data from social networks, defined geography with user presence within the geographical area of interest, and tags with elevated API permissions (from
Facebook, twitter and Instagram) for Dataveillance – Social surveillance
A Think alike gaming iOS application – Swift3, Multilingual based on remote data, Multiplayer, and Statistics and summary
A Multilingual, Multiplayer pick odd one out trivial game with an In-app pay by feature for statistics and summary for both iOS and Android platform – Swift3 and Java-core
Designed and developed an android application to identify and maintain a log of all notifications, by interpreting application importance, prioritizing and scheduling notification delivery on the basis of user preference. A notification
manager like a mailbox for mails.
Tech Stack: Android, Java, firebase and SQLite
An intelligent creative twitter bot pushing new recipes with unique set of ingredients.
Tech stack: Python, PIL, AWS EC2
A collaborative birthday artifact generator.
Tech stack: Python, PIL, AWS Lambda, AWS API Gateway
An android application where painting isn't just rubbing your brushes on an empty canvas. Laying out a new idea with your friends is just one another great outcome from here, infinite potential. Multiuser drawing board.
Tech
stack: Java, Firebase
Location: Hayward CA (USA)
Software Engineering Intern (June 2019 - Present)
Location: Indore MP (IND)
Software Engineer II
(2017-2018)
•
Software Engineer I
(2016-2017)
•
Software Engineer Intern
(2015-2016)
Location: Indore MP (IND)
Software Engineering Intern
(2014-2015)


Your browser does not support iframes.
Click the button to change the background color of the document in the iframe.


| Interface | Description |
|---|---|
| AdsLoader |
Interface for loaders of ads, which can be used with
AdsMediaSource . |
| AdsLoader.AdViewProvider |
Provides views for the ad UI.
|
| AdsLoader.EventListener |
Listener for ads loader events.
|
| AdsMediaSource.MediaSourceFactory |
Factory for creating
MediaSource s to play ad media. |
| Class | Description |
|---|---|
| AdPlaybackState |
Represents ad group times relative to the start of the media and information on the state and
URIs of ads within each ad group.
|
| AdPlaybackState.AdGroup |
Represents a group of ads, with information about their states.
|
| AdsMediaSource |
A
MediaSource that inserts ads linearly with a provided content media source. |
| SinglePeriodAdTimeline |
A
Timeline for sources that have ads. |
| Exception | Description |
|---|---|
| AdsMediaSource.AdLoadException |
Wrapper for exceptions that occur while loading ads, which are notified via
MediaSourceEventListener#onLoadError(int, MediaPeriodId, LoadEventInfo, MediaLoadData,
IOException, boolean) . |
| Annotation Type | Description |
|---|---|
| AdPlaybackState.AdState |
Represents the state of an ad in an ad group.
|
| AdsMediaSource.AdLoadException.Type |
Types of ad load exceptions.
|


Express is a Node.js web application framework it provides a variety of features for web and mobile applications.
With a vast amount of HTTP utility methods and middleware at your fingertips, creating a quality API is fast and easy.
Express provides fundamental web application features, without disrupting Node.js' features.
Many popular frameworks are based on Express
$ npm install express --save
Creates an Express application. The express() function is a top-level function exported by the express module.
const express = require('express')
const app = express()
The app object conventionally denotes the Express application. create it by calling the express() function.
const express = require('express')
const app = express()
app.get('/', function (req, res){
res.send('hello world')
})
app.listen(3000)
The app object has methods for:
- hello
- Routing HTTP requests
- Configuring middleware
- Rendering HTML views
- Registering a template engine
The req object represents the HTTP request and has properties for the request query string, parameters , body, HTTP headers, and so on. In this documentation and by convention, the object is always referred to as req (the HTTP response is res) but its actual name is determined but the parameters to the callback function in which you're working.
for example:
app.get('/user/:id', function (req, res) {
res.send('user' + req.params.id)
})
can also have:
app.get('/user/:id', function(request, response){
response.send('user + request.params.id')
})
The res object represents the HTTP response that an Express app sends when it gets an HTTP request.
In this documention and by convention, the object is always referred to as res(the HTTP request is req)nut its actual name is determined by the parameters to the callback function in which you're working.
for example:
app.get('/user/:id', function (req, res){
res.send('user' + req.params.id)
})
can also have:
app.get('user/:id', function (request, response){
response.send('user' + request.params.id)})
A router objest is isolated instance of middleware and routes. You can think oof it as a "mini-application," capable only of performing middleware and routing functions. Every Express application has a built-in app router.
A router behaves like middleware itself, so you can use it as an argument to app.use() or as the argument to another router's use() method.
The express object has a Router() method that creates a new router object.
Once you've created a router object, you can add middleware abd HTTP method routes to it just like an appliction. For example:
// invoked for any requests passed to this router
router.use(function (req, res, next){
// ..some login here .. like my other middleware
next()
})
//will handle any request that ends in /events
// depends on where the router is "use()'d"
router.get('/events', function(req, res, next){
//..
})
You can then use a router for a particular root URL in this way separating your routes into files or even mini-apps.
// only requests to /calendar/* will be sent to our "router"
app.use('/calendar', router)
The documentation on this page was taken fromExpressjs.com


Where-go:
December 6th, 2009
by where comes?
by road or air?
by railway?
be the waters that will take you back?
or the woods do carry you away?
The electric lines do you justice-?
nor do the word of mouth that over I distribute myself
Under those electric lines
they cut the forest down to make them
and they span across the mountain ranges
clear the air for wired lines- and broadcasts
bouncing all around
When someday soon come turning round
no tornado
no roots to fall and trip over
no harvest from the land
bare fields by lonely roads
dirty city streets
where the agony
that brought them there
-can be forgotten?
Where did it go?
our haunted lonely sorrow
they us here to cities, detached
from the land that suffocates under
and tendrils spring from every crack of
And you, whose movements are
in perfect measure to
reverberate in arriving here in this place
A world I never have left


{% extends 'base.html' %} {% load i18n %} {% block content %}
{% blocktrans with object=object %}Are you sure you want to assing "{{institution}}" to monitoring "{{monitoring}}"?{% endblocktrans %}


Class SIPWebSocketChannel
A SIP transport Channel for transmitting SIP over a Web Socket communications layer as per RFC7118.
var sipTransport = new SIPTransport();
var wsSipChannel = new SIPWebSocketChannel(IPAddress.Loopback, 80);
var wssCertificate = new System.Security.Cryptography.X509Certificates.X509Certificate2("localhost.pfx");
var wssSipChannel = new SIPWebSocketChannel(IPAddress.Loopback, 433, wssCertificate);
sipTransport.AddSIPChannel(wsSipChannel);
sipTransport.AddSIPChannel(wssSipChannel);
Implements
Inherited Members
Namespace: SIPSorcery.SIP
Assembly: SIPSorcery.dll
Syntax
public class SIPWebSocketChannel : SIPChannel, IDisposable
Constructors
| Improve this Doc View SourceSIPWebSocketChannel(IPAddress, Int32)
Declaration
public SIPWebSocketChannel(IPAddress listenAddress, int listenPort)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Net.IPAddress | listenAddress | |
| System.Int32 | listenPort |
SIPWebSocketChannel(IPAddress, Int32, X509Certificate2)
Creates a new secure web socket server (e.g. wss://localhost).
Declaration
public SIPWebSocketChannel(IPAddress listenAddress, int listenPort, X509Certificate2 certificate)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Net.IPAddress | listenAddress | The IPv4 or IPv6 address to listen on. |
| System.Int32 | listenPort | The network port to listen on. |
| System.Security.Cryptography.X509Certificates.X509Certificate2 | certificate | The X509 certificate to supply to connecting clients. Unless the client has been specifically configured otherwise the it will perform validation on the certificate which typically involved checking that the hostname of the server matches the certificate's common name. |
SIPWebSocketChannel(IPEndPoint, X509Certificate2)
Creates a SIP channel to listen for and send SIP messages over a web socket communications layer.
Declaration
public SIPWebSocketChannel(IPEndPoint endPoint, X509Certificate2 certificate)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Net.IPEndPoint | endPoint | The IP end point to listen on and send from. |
| System.Security.Cryptography.X509Certificates.X509Certificate2 | certificate |
Fields
| Improve this Doc View SourceSIP_Sec_WebSocket_Protocol
Declaration
public const string SIP_Sec_WebSocket_Protocol = "sip"
Field Value
| Type | Description |
|---|---|
| System.String |
Methods
| Improve this Doc View SourceClose()
Stops the web socket server and closes any client connections.
Declaration
public override void Close()
Overrides
| Improve this Doc View SourceDispose()
Calls close on the channel when it is disposed.
Declaration
public override void Dispose()
Overrides
| Improve this Doc View SourceHasConnection(SIPEndPoint)
Checks whether there is an existing client web socket connection for a remote end point.
Declaration
public override bool HasConnection(SIPEndPoint remoteEndPoint)
Parameters
| Type | Name | Description |
|---|---|---|
| SIPEndPoint | remoteEndPoint | The remote end point to check for an existing connection. |
Returns
| Type | Description |
|---|---|
| System.Boolean | True if there is a connection or false if not. |
Overrides
| Improve this Doc View SourceHasConnection(String)
Checks whether the web socket SIP channel has a connection matching a unique connection ID.
Declaration
public override bool HasConnection(string connectionID)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | connectionID | The connection ID to check for a match on. |
Returns
| Type | Description |
|---|---|
| System.Boolean | True if a match is found or false if not. |
Overrides
| Improve this Doc View SourceHasConnection(Uri)
Not implemented for the this channel.
Declaration
public override bool HasConnection(Uri serverUri)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Uri | serverUri |
Returns
| Type | Description |
|---|---|
| System.Boolean |
Overrides
| Improve this Doc View SourceIsAddressFamilySupported(AddressFamily)
Checks whether the specified address family is supported.
Declaration
public override bool IsAddressFamilySupported(AddressFamily addresFamily)
Parameters
| Type | Name | Description |
|---|---|---|
| System.Net.Sockets.AddressFamily | addresFamily | The address family to check. |
Returns
| Type | Description |
|---|---|
| System.Boolean | True if supported, false if not. |
Overrides
| Improve this Doc View SourceIsProtocolSupported(SIPProtocolsEnum)
Checks whether the specified protocol is supported.
Declaration
public override bool IsProtocolSupported(SIPProtocolsEnum protocol)
Parameters
| Type | Name | Description |
|---|---|---|
| SIPProtocolsEnum | protocol | The protocol to check. |
Returns
| Type | Description |
|---|---|
| System.Boolean | True if supported, false if not. |
Overrides
| Improve this Doc View SourceSendAsync(SIPEndPoint, Byte[], String)
Ideally sends on the web socket channel should specify the connection ID. But if there's a good reason not to we can check if there is an existing client connection with the requested remote end point and use it.
Declaration
public override Task<SocketError> SendAsync(SIPEndPoint destinationEndPoint, byte[] buffer, string connectionIDHint)
Parameters
| Type | Name | Description |
|---|---|---|
| SIPEndPoint | destinationEndPoint | The remote destination end point to send the data to. |
| System.Byte[] | buffer | The data to send. |
| System.String | connectionIDHint | The ID of the specific web socket connection to try and send the message on. |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<System.Net.Sockets.SocketError> | If no errors SocketError.Success otherwise an error value. |
Overrides
| Improve this Doc View SourceSendSecureAsync(SIPEndPoint, Byte[], String, String)
Not implemented for the WebSocket channel.
Declaration
public override Task<SocketError> SendSecureAsync(SIPEndPoint dstEndPoint, byte[] buffer, string serverCertificateName, string connectionIDHint)
Parameters
| Type | Name | Description |
|---|---|---|
| SIPEndPoint | dstEndPoint | |
| System.Byte[] | buffer | |
| System.String | serverCertificateName | |
| System.String | connectionIDHint |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<System.Net.Sockets.SocketError> |


Your Best Friend Match!
×
Survey Page
About You
Name (required)
Link to Photo (required)
Submit
API Friends List |
Git Hub Repo


Allow to apply jQuery Themeroller styles.
Status: pre-alpha
Standard tree:
Table tree:
Columnview tree:
jquery.fancytree.js project home Link to this page Example Browser View source code


As the title says, the BF4stats do not show the ranking of my weapons in the stats list in my battlelog account, same for who ever else I view
Thank you!
BrainFooLong
Administrator
Right, it's buggy now.
I will fix this soon.
Topicstarter
MexosAreYummy
Thank you very much, I appreciate it :)
BrainFooLong
Administrator
Will be fixed in next update - Some days after BF Hardline release.


Created by Ilya Buziuk / @ilyabuziuk
Collection of data
Tools for DB managment
Structured Query Language for relational DBs
Necessity of common interface for all DB
Java Database Connectivity (JDBC)
Avoid using any proprietary APIs
"Write once, compile once, run anywhere"
DB's launching point for JDBC
Maintains a list of Driver implementations
single DB connection / used for sending SQL statements
<!-- MySQL connector -->
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>5.1.35</version>
</dependency>
Class.forName("com.mysql.jdbc.Driver");
connection = DriverManager.getConnection(URL, USERNAME, PASSWORD);
preparedStatement = connection.prepareStatement("INSERT INTO tasks (id, description, done) VALUES (?, ?, ?)");
preparedStatement.setInt(1, task.getId());
preparedStatement.setString(2, task.getDescription());
preparedStatement.setBoolean(3, task.isDone());
preparedStatement.executeUpdate();
attack data-driven applications, in which malicious SQL statements are inserted into an entry field for execution (e.g. to dump the database contents to the attacker). TOP website vulnerabilities
User Name:
Password:
txtUserId = getRequestString("UserId");
txtSQL = "SELECT * FROM Users WHERE UserId = " + txtUserId;
SELECT * FROM Users WHERE UserId = 105 or 1=1
uName = getRequestString("UserName");
uPass = getRequestString("UserPass");
sql = "SELECT * FROM Users WHERE Name ='" + uName + "' AND Pass ='" + uPass + "'"
SELECT * FROM Users WHERE Name ="" or ""="" AND Pass ="" or ""=""
SELECT * FROM Users WHERE UserId = 105; DROP TABLE users
Statement stmt = conn.createStatement("INSERT INTO students VALUES('" + user + "')");
stmt.execute();
Statement stmt = conn.prepareStatement("INSERT INTO student VALUES(?)");
stmt.setString(1, user);
stmt.execute();
connection.close();
statement.close();
data access object
abstract interface to some type of database or other persistence mechanism
public class Employee {
private int id;
private String name;
.... // geters & setters
}
interface EmployeeDAO {
List<Employee> findAll();
List<Employee> findById();
List<Employee> findByName();
boolean insertEmployee(Employee employee);
boolean updateEmployee(Employee employee);
boolean deleteEmployee(Employee employee);
}
class EmployeeDAOImpl implements EmployeeDAO {
.... // Concrete implementation
}
SELECT c.CustomerName, o.OrderID, o.OrderDate
FROM Customers as c
INNER JOIN Orders as o
ON c.CustomerID = o.CustomerID
A series of data manipulation statements that must either fully complete or fully fail, leaving the database in a consistent state
Connections are in autocommit mode by default


| 1 | package nl.tudelft.jpacman.npc.ghost; | |
| 2 | ||
| 3 | import java.util.List; | |
| 4 | import java.util.Map; | |
| 5 | ||
| 6 | import nl.tudelft.jpacman.board.Direction; | |
| 7 | import nl.tudelft.jpacman.board.Square; | |
| 8 | import nl.tudelft.jpacman.board.Unit; | |
| 9 | import nl.tudelft.jpacman.level.Player; | |
| 10 | import nl.tudelft.jpacman.sprite.Sprite; | |
| 11 | ||
| 12 | /** | |
| 13 | *
 | |
| 14 | * An implementation of the classic Pac-Man ghost Bashful. | |
| 15 | *
 | |
| 16 | *
 | |
| 17 | * Nickname: Inky. Bashful has truly earned his name. In a game of chicken | |
| 18 | * between Pac-Man and Bashful, Bashful might just run away. This isn't always | |
| 19 | * the case, but if Blinky is right behind you, it's a safe bet. He can't be | |
| 20 | * scared off while he patrols the southeast portion of the maze. In Japan, his | |
| 21 | * name is Kimagure/Aosuke. | |
| 22 | *
 | |
| 23 | *
 | |
| 24 | * AI: Bashful has the most complicated AI of all. When the ghosts are | |
| 25 | * not patrolling their home corners, Bashful considers two things: Shadow's | |
| 26 | * location, and the location two grid spaces ahead of Pac-Man. Bashful draws a | |
| 27 | * line from Shadow to the spot that is two squares in front of Pac-Man and | |
| 28 | * extends that line twice as far. Therefore, if Bashful is alongside Shadow | |
| 29 | * when they are behind Pac-Man, Bashful will usually follow Shadow the whole | |
| 30 | * time. But if Bashful is in front of Pac-Man when Shadow is far behind him, | |
| 31 | * Bashful tends to want to move away from Pac-Man (in reality, to a point very | |
| 32 | * far ahead of Pac-Man). Bashful is affected by a similar targeting bug that | |
| 33 | * affects Speedy. When Pac-Man is moving or facing up, the spot Bashful uses to | |
| 34 | * draw the line is two squares above and left of Pac-Man. | |
| 35 | *
 | |
| 36 | *
 | |
| 37 | * Source: http://strategywiki.org/wiki/Pac-Man/Getting_Started | |
| 38 | *
 | |
| 39 | * | |
| 40 | * @author Jeroen Roosen | |
| 41 | * | |
| 42 | */ | |
| 43 | public class Inky extends Ghost { | |
| 44 | ||
| 45 | private static final int SQUARES_AHEAD = 2; | |
| 46 | ||
| 47 | /** | |
| 48 | * The variation in intervals, this makes the ghosts look more dynamic and | |
| 49 | * less predictable. | |
| 50 | */ | |
| 51 | private static final int INTERVAL_VARIATION = 50; | |
| 52 | ||
| 53 | /** | |
| 54 | * The base movement interval. | |
| 55 | */ | |
| 56 | private static final int MOVE_INTERVAL = 250; | |
| 57 | ||
| 58 | /** | |
| 59 | * Creates a new "Inky", a.k.a. Bashful. | |
| 60 | * | |
| 61 | * @param spriteMap | |
| 62 | * The sprites for this ghost. | |
| 63 | */ | |
| 64 | public Inky(Map<Direction, Sprite> spriteMap) { | |
| 65 | super(spriteMap, MOVE_INTERVAL, INTERVAL_VARIATION); | |
| 66 | } | |
| 67 | ||
| 68 | /** | |
| 69 | * {@inheritDoc} | |
| 70 | * | |
| 71 | *
 | |
| 72 | * Bashful has the most complicated AI of all. When the ghosts are not | |
| 73 | * patrolling their home corners, Bashful considers two things: Shadow's | |
| 74 | * location, and the location two grid spaces ahead of Pac-Man. Bashful | |
| 75 | * draws a line from Shadow to the spot that is two squares in front of | |
| 76 | * Pac-Man and extends that line twice as far. Therefore, if Bashful is | |
| 77 | * alongside Shadow when they are behind Pac-Man, Bashful will usually | |
| 78 | * follow Shadow the whole time. But if Bashful is in front of Pac-Man when | |
| 79 | * Shadow is far behind him, Bashful tends to want to move away from Pac-Man | |
| 80 | * (in reality, to a point very far ahead of Pac-Man). Bashful is affected | |
| 81 | * by a similar targeting bug that affects Speedy. When Pac-Man is moving or | |
| 82 | * facing up, the spot Bashful uses to draw the line is two squares above | |
| 83 | * and left of Pac-Man. | |
| 84 | *
 | |
| 85 | * | |
| 86 | *
 | |
| 87 | * Implementation: by lack of a coordinate system there is a | |
| 88 | * workaround: first determine the square of Blinky (A) and the square 2 | |
| 89 | * squares away from Pac-Man (B). Then determine the shortest path from A to | |
| 90 | * B regardless of terrain and walk that same path from B. This is the | |
| 91 | * destination. | |
| 92 | *
 | |
| 93 | */ | |
| 94 | // CHECKSTYLE:OFF To keep this more readable. | |
| 95 | @Override | |
| 96 | public Direction nextMove() { | |
| 97 | Unit blinky = Navigation.findNearest(Blinky.class, getSquare()); | |
| 98 | if (blinky == null) { | |
| 99 | return randomMove(); | |
| 100 | } | |
| 101 | ||
| 102 | Unit player = Navigation.findNearest(Player.class, getSquare()); | |
| 103 | if (player == null) { | |
| 104 | return randomMove(); | |
| 105 | } | |
| 106 | ||
| 107 | Direction targetDirection = player.getDirection(); | |
| 108 | Square playerDestination = player.getSquare(); | |
| 109 |
1
1. nextMove : Changed increment from 1 to -1 → SURVIVED |
for (int i = 0; i < SQUARES_AHEAD; i++) { |
| 110 | playerDestination = playerDestination.getSquareAt(targetDirection); | |
| 111 | } | |
| 112 | ||
| 113 | Square destination = playerDestination; | |
| 114 | List<Direction> firstHalf = Navigation.shortestPath(blinky.getSquare(), | |
| 115 | playerDestination, null); | |
| 116 | if (firstHalf == null) { | |
| 117 | return randomMove(); | |
| 118 | } | |
| 119 | ||
| 120 | for (Direction d : firstHalf) { | |
| 121 | destination = playerDestination.getSquareAt(d); | |
| 122 | } | |
| 123 | ||
| 124 | List<Direction> path = Navigation.shortestPath(getSquare(), | |
| 125 | destination, this); | |
| 126 | if (path != null && !path.isEmpty()) { | |
| 127 | return path.get(0); | |
| 128 | } | |
| 129 | return randomMove(); | |
| 130 | } | |
| 131 | // CHECKSTYLE:ON | |
| 132 | ||
| 133 | } | |
Mutations | ||
| 109 |
1.1 |


Tool Example 6
changing the default share title for all tools
Some services (such as Facebook) do not allow you to define the share title for a URL. Facebook will always use the Open Graph tags it finds on the page when it crawls it. You can use the Facebook Sharing Debugger to test your Open Graph tags.
You can test on the tool below, the sidebar on the right (on desktop) or the bar on the bottom (on mobile).
Any inline tool specifying a share URL using the share-title attribute will not be effected by this.