A simple way to sort an array.
public int [] binarySearch(int [] array, int value) {
int lastSortedIndex = array.length;
for (int x=array.length; x>0; x--) {
int greatestValue = array[0];
int greatestIndex = 0;
for (int y=0; y<=x; y++) {
if (greatestValue < array[y]) {
greatestValue = array[y];
greatestIndex = y;
}
}
int lastValue = array[x];
array[x] = greatestValue;
array[greatestIndex] = lastValue;
}
return array;
}
Selection sort is an easy to code and explain; just one sentence is enough to describe how it works! However, it is a slow sorting algorithm. It works by continually looping through the unsorted part array to find the largest number, then putting it at the end of the unsorted array. Here’s a demonstration using an array of 5 numbers:
We would loop through the array, looking for the greatest value. This value will be stored in a variable, which can be initialized as the first element in the array. We will need another variable storing the index of the greatest value.
Since the greatest value is initialized to be the value at index 0, that value doesn’t have to be checked. The index we are checking now is 1, which contains a value of 3. It is not bigger than 4, so none of the variables get updated.
The next index to be checked is 2. Since 5 is greater than the previous greatest value of 2, the greatest index becomes 2.
The next index is 3. Since 1 is not greater than 5, the values are not changed.
The next index is 4. Since 2 is not greater than 5, the values are not changed.
We see that 5 is the greatest value at index 2, so we switch the values at the two indices:
Now, the last index is sorted. We no longer need to consider the last index anymore. We can search through indices 0-3 again, finding the largest value and switching it with the value at index 3:
The orange area represents the sorted area.
We can loop through indices 0-2 and put the greatest value at the end of the range:
We loop through indices 0-1 and put the greatest value at the end of the range. In this case, the greatest value, 2, is already at the end of the range:
The only “unsorted” part left is only index 0, but it doesn’t need to be sorted because it’s only a single index. Thus, we have the sorted array:
created with
Nicepage .


About two months ago, I decided to combine a massive dose of 35x salvia with one hit of good acid. So, right when I was peaking, I took the hit of salvia. I was instantly 5-10 mins ahead.  Slowly but surely, it rearranged itself into my normal vision. I forgot everything I had ever learned. My memory for language came back rather quickly. All of my life's memories...gone. I didn't know who I was, nor anyone else in the room, and no idea how I got there. I went around, asking my tripping friend about my life. 'How often do I do this? How long have I known you? How did we meet?'
 Not sure that I can quite describe it. I'll never touch salvia ever again. The amnesia took about 3 hours to end and start to remember things again.  Later on, we went out to the beach during a tropical storm (the plan the whole time), where I had one of my best trips. The raging sea during a tropical storm while you are way out on a pier with waves crashing onto it is a very very amazing experience. So I got the worst and the best out of one trip. I'm never smoking salvia again. Maybe acid, but never salvia. I'm really not too enthusiastic about acid either, now.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


hDOAP is profile (dialect) of XHTML used to express Description of a Project (DOAP) data in XHTML. This document describes and defines that profile. GRDDL may be used to extract machine-readable data from the document.
Status: 2005-05-29 - almost finished, some less common elements need adding to the stylesheets
There are (at least) two ways of creating a hDOAP document. The first is to use an HTML editor and include the attributes for CSS as structured in this sample : redland-doap.html (describes the Redland RDF Toolkit).
The second is to create a standard DOAP file and run it through the XSLT transformation described below. The DOAP-a-matic provides a very easy way of creating the DOAP.
hDOAP is designed to be compatible with the GRDDL technique, a mechanism for Gleaning Resource Descriptions from Dialects of Languages; that is, for getting RDF data out of XML and XHTML documents using explicitly associated transformation algorithms.
There are two ways of making the association. The hDOAP document may contain the following elements:
<head profile="http://www.w3.org/2003/g/data-view"
/>
<link rel="transformation" href="http://purl.org/stuff/hdoap/hdoap2doap.xsl"
/>
This transformation is what is required to convert the document into RDF/XML. The profile here (more formally, metadata profile as specified in section 6.12 Link types of the HTML 4.0 specification) simply states that the result of the transformation will be data considered equivalent to the XHTML document.
But there is a more elegant way of making the association.
When the hDOAP profile is used in documents it can be declared explicitly with the element:
<head profile="http://purl.org/stuff/hdoap/profile" />.
This associates the document with this profile.
A GRDDL-capable client tool, when visiting a page which contains that profile reference will first visit the profile document (this document), apply the transformation declared here (using the data-view profile above). The results of that transformation will contain a statement identifying the transformation that should be applied to convert the hDOAP document into RDF/XML. The GRDDL client has everything it needs to get RDF/XML from the original XHTML document, while the author of the hDOAP document need not concern themselves with the details of the profile, merely including the reference to its URI is enough. Cunning, eh?
To create an XHTML hDOAP document from an RDF/XML DOAP document, you can use the following stylesheet: doap2html.xsl
Sample input: redland-doap.rdf, sample output: redland-doap.html
A CSS stylesheet is also available: hdoap.css, which can be applied to the hDOAP XHTML (e.g. redland.doap.html) or used in concert with doap2html.xsl for client-side styling of (RDF/XML) DOAP documents (e.g. gnome-bluetooth-doap.xml).
Convert RDF/XML DOAP file to hDOAP:
Obtain the RDF/XML from an XHTML you can use the following stylesheet: hdoap2doap.xsl (as specified for GRDDL):
The result of GRDDLing this page:


Serial Interface
The base address of interface registers is CC006400.
All registers are 32-bit.
SI Channel 0 Output Buffer
CC006400
SIC0OUTBUF :
Bits Mnemonic Type Reset Description
31:24 R 0 Reserved
23:16 CMD RW 0 Command: This byte is the opcode for the command
sent to the controller during each command/response
packet. This is the first data byte sent from the SI I/F to
the game controller in the command/response packet.
15:8 OUTPUT0 RW 0 Output Byte 0: This is the first data byte of the
command packet. It is the second data byte sent from
the SI I/F to the game controller in the
command/response packet.
7:0 OUTPUT1 RW 0 Output Byte 1: This is the second databyte of the
command packet. It is the third data byte sent from the
SI I/F to the game controller in the command/response packet.
This register is double buffered, so main processor writes to the
SIC0OUTBUF will not interfere with the serial interface output
transfer. Internally, a second buffer is used to hold the output data to be
transferred across the serial interface. To check if SIC0OUTBUF
has been transferred to the second buffer, main processor polls the
SISR[WRST0] register. When SICOOUTBUF is transferred, SISR[WRST0] is cleared.
SI Channel 0 Input Buffer High
CC006404
SIC0INBUFH:
Bits Mnemonic Type Reset Description
31 ERRSTAT R 0 Error Status: This bit represents the current error status
for the last SI polling transfer on channel 0. This
register is updated after each polling transfer on this channel.
0 = No error on last transfer
1 = Error on last transfer
30 ERRLATCH R 0 Error Latch: This bit is an error status summary of the
SISR error bits for this channel. If an error has
occurred on a past SI transfer on channel 0 (polling or
Com transfer), this bit will be set. To determine the
exact error, read the SISR register. This bit is actually
an `or` of the latched error status bits for channel 0 in
the SISR. The bit is cleared by clearing the appropriate
error status bits latched in the SISR. The no response
error indicates that a controller is not present on this channel.
0 = No errors latched
1 = Error latched. Check SISR.
29:24 INPUT0 R Input Byte 0: This is the first data byte of the response
packet sent from the game controller to the SI I/F for
channel 0. The top two bits of the byte returning from
the controller are assumed to be `0`, so they are not
included.
23:16 INPUT1 R Input Byte 1: This is the second data byte of the
response packet sent from the game controller to the SI
I/F for channel 0.
15:8 INPUT2 R Input Byte 2: This is the third data byte of the response
packet sent from the game controllers to the SI I/F for
channel 0.
7:0 INPUT3 R Input Byte 3: This is the fourth data byte of the
response packet sent from the game controller to the SI
I/F for channel 0.
SIC0INBUFH and SIC0INBUFL are double buffered to prevent
inconsistent data reads due to main processor conflicting with incoming
serial interface data. To insure data read from SIC0INBUFH and
SIC0INFUBL are consistent, a locking mechanism prevents the double buffer from
copying new data to these registers. Once SIC0INBUFH is read, both SIC0INBUFH
and SIC0INBUFL are `locked` until SIC0INBUFL is read. While the buffers are
`locked`, new data is not copied into the buffers. When SIC0INBUFL is read, the
buffers become unlocked again.
SIC0INBUF SI Channel 0 Input Buffer Low
Mnemonic: SIC0INBUFL
Offset: 0x08
Size 32 bits SIC0INBUFL
Bits Mnemonic Type Reset Description
31:24 INPUT4 R 0 .times. 0 Input Byte 4: See Description of
SIC1INBUFH[INPUT1].
23:16 INPUT5 R 0 .times. 0 Input Byte 5: See Description of
SIC1INBUFH[INPUT1].
15:8 INPUT6 R 0 .times. 0 Input Byte 6: See Description of
SIC1INBUFH[INPUT1].
7:0 INPUT7 R 0 .times. 0 Input Byte 7: See Description of
SIC1INBUFH[INPUT1].
SIC1OUTBUF SI Channel 1 Output Buffer
Mnemonic: SIC 1
OUTBUF
Offset: 0x0C
Size 32 bits SIC1OUTBUF
Bits Mnemonic Type Reset Description
31:24 R 0 .times. 0 Reserved
23:16 CMD RW 0 .times. 0 Command: For SI channel 1. See
SIC0OUTBUFF[CMD]
description.
15:8 OUTPUT0 RW 0 .times. 0 Output Byte 0: For SI channel 1. See
SIC0OUTBUFF[OUTPUT0
description.
7:0 OUTPUT1 RW 0 .times. 0 Output Byte 1: For SI channel 1. See
SIC0OUTBUFF[OUTPUT1]
description.
SIC1INBUF SI Channel 1 Input Buffer High
Mnemonic:
SIC1INBUFH
Offset: 0x10
Size 32 bits SIC1INBUFH
Bits Mnemonic Type Reset Description
31 ERRSTAT R 0 .times. 0 Error Status: See Description of
SIC0INBUFH[ERRSTAT].
30 ERRLATCH R 0 .times. 0 Error Latch: See Description of
SIC0INBUFH[ERRLATCH].
29:24 INPUT0 R 0 .times. 0 Input Byte 0: See Description of
SIC0INBUFH[INPUT0].
23:16 INPUT1 R 0 .times. 0 Input Byte 1: See Description of
SIC0INBUFH[INPUT1].
15:8 INPUT2 R 0 .times. 0 Input Byte 2: See Description of
SIC0INBUFH[INPUT1].
7:0 INPUT3 R 0 .times. 0 Input Byte 3: See Description of
SIC0INBUFH[INPUT1].
SIC1INBUF SI Channel 1 Input Buffer Low
Mnemonic:
SIC1INBUFL
Offset: 0x14
Size 32 bits SIC1INBUFL
Bits Mnemonic Type Reset Description
31:24 INPUT4 R 0 .times. 0 Input Byte 4: See Description of
SIC0INBUFH[INPUT1].
23:16 INPUT5 R 0 .times. 0 Input Byte 5: See Description of
SIC0INBUFH[INPUT1].
15:8 INPUT6 R 0 .times. 0 Input Byte 6: See Description of
SIC0INBUFH[INPUT1].
7:0 INPUT7 R 0 .times. 0 Input Byte 7: See Description of
SIC0INBUFH[INPUT1].
SIC2OUTBUF SI Channel 2 Output Buffer
Mnemonic: SIC2OBUF
Offset: 0x18
Size 32 bits SIC2OUTBUF
Bits Mnemonic Type Reset Description
31:24 R 0 .times. 0 Reserved
23:16 CMD RW 0 .times. 0 Command: For SI Channel 2. See
SIC0OUTBUFF[CMD]
description
15:8 OUTPUT0 RW 0 .times. 0 Output Byte 0: For SI channel 2. See
SIC0OUTBUFF[OUTPUT0]
description.
7:0 OUTPUT1 RW 0 .times. 0 Output Byte 1: For SI channel 2. See
SIC0OUTBUFF[OUTPUT1]
description.
SIC2INBUF SI Channel 2 Input Buffer High
Mnemonic:
SIC2INBUFH
Offset: 0x1C
Size 32 bits SIC2INBUFH
Bits Mnemonic Type Reset Description
31 ERRSTAT R 0 .times. 0 Error Status: See Description of
SIC0INBUFH[ERRSTAT].
30 ERRLATCH R 0 .times. 0 Error Latch: See Description of
SIC0INBUFH[ERRLATCH].
29:24 INPUT0 R 0 .times. 0 Input Byte O: See Description of
SIC0INBUFH[INPUT1].
23:16 INPUT1 R 0 .times. 0 Input Byte 1: See Description of
SIC0INBUFH[INPUT0].
15:8 INPUT2 R 0 .times. 0 Input Byte 2: See Description of
SIC0INBUFH[INPUT1].
7:0 INPUT3 R 0 .times. 0 Input Byte 3: See Description of
SIC0INBUFH[INPUT1].
SIC2INBUF SI Channel 2 Input Buffer Low
Mnemonic:
SIC2INBUFL
Offset: 0x20
Size 32 bits SIC2INBUFL
Bits Mnemonic Type Reset Description
31:24 INPUT4 R 0 .times. 0 Input Byte 4: See Description of
SIC0INBUFH[INPUT0].
23:16 INPUT5 R 0 .times. 0 Input Byte 5: See Description of
SIC0INBUFH[INPUT0].
15:8 INPUT6 R 0 .times. 0 Input Byte 6: See Description of
SIC0INBUFH[INPUT0].
7:0 INPUT7 R 0 .times. 0 Input Byte 7: See Description of
SIC0INBUFH[INPUT0].
SIC30UTBUF SI Channel 3 Output Buffer
Mnemonic: SIC3OBUF
Offset: 0x24
Size 32 bits SIC3OUTBUF
Bits Mnemonic Type Reset Description
31:24 R 0 .times. 0 Reserved
23:16 CMD RW 0 .times. 0 Command: For SI channel 3. See
SIC0OUTBUFF[CMD0]
description
15:8 OUTPUT0 RW 0 .times. 0 Output Byte 0: For SI channel 3. See
SIC0OUTBUFF[OUTPUT0]
description
7:0 OUTPUT1 RW 0 .times. 0 Output Byte 1: For SI channel 3. See
SIC0OUTBUFF[OUTPUT1]
description
SIC3INBUF SI Channel 3 Input Buffer High
Mnemonic:
SIC3INBUFH
Offset: 0x28
Size 32 bits SIC3INBUFH
Bits Mnemonic Type Reset Description
31 ERRSTAT R 0 .times. 0 Error Status: See Description of
SIC0INBUFH[ERRSTAT].
30 ERRLATCH R 0 .times. 0 Error Latch: See Description of
SIC0INBUFH[ERRLATCH].
29:24 INPUT0 R 0 .times. 0 Input Byte 0: See Description of
SIC0INBUFH[INPUT0].
23:16 INPUT1 R 0 .times. 0 Input Byte 1: See Description of
SIC0INBUFH[INPUT1].
15:8 INPUT2 R 0 .times. 0 Input Byte 2: See Description of
SIC0INBUFH[INPUT1]
7:0 INPUT3 R 0 .times. 0 Input Byte 3: See Description of
SIC0INBUFH[INPUT1].
SIC3INBUF SI Channel 3 Input Buffer Low
Mnemonic:
SIC3INBUFL
Offset: 0x2C
Size 32 bits SIC4INBUFL
Bits Mnemonic Type Reset Description
31:24 INPUT4 R 0 .times. 0 Input Byte 4: See Description of
SIC0INBUFH[INPUT1].
23:16 INPUT5 R 0 .times. 0 Input Byte 5: See Description of
SIC0INBUFH[INPUT1].
15:8 INPUT6 R 0 .times. 0 Input Byte 6: See Description of
SIC0INBUFH[INPUT1].
7:0 INPUT7 R 0 .times. 0 Input Byte 7: See Description of
SIC0INBUFH[INPUT1].
SIPOLL SI Poll Register
Mnemonic: SIPOLL
Offset:
0x30
Size 32 bits SIPOLL
Bits Mnemonic Type Reset Description
31:26 R 0 .times. 0 Reserved
25:16 X RW 0 .times. 07 X lines register: determines the
number of horizontal
video lines between polling (the polling
interval).
The polling begins at vsync. 0 .times. 07
is the minimum
setting (determined by the time required to
complete
a single polling of the controller). The
maximum
setting depends on the current video mode
(number of
lines per vsync) and the SIPOLL[Y]
register. This
register takes affect after vsync.
15:8 Y RW 0 .times. 0 Y times register: This register
determines the number
of times the SI controllers are polled in a
single
frame. This register takes affect after
vsync.
7 EN0 RW 0 .times. 0 Enable channel 0: Enable polling of
channel 0.
When the channel is enabled, polling begins
at the
next vblank. When the channel is disabled,
polling is
stopped immediately after the current
transaction.
The status of this bit does not affect
communication
RAM transfers on this channel.
1 = Polling of channel 0 is enabled
0 = Polling of channel 0 is disabled
6 EN1 RW 0 .times. 0 Enable channel 1: See description for
SIPOLL[EN0].
5 EN2 RW 0 .times. 0 Enable channel 2: See Description for
SIPOLL[EN0].
4 EN3 RW 0 .times. 0 Enable channel 3: See Description for
SIPOLL[EN0].
3 VBCPY0 RW 0 .times. 0 Vblank copy output channel 0: Normally
main
processor writes to the SIC0OUTBUF register
are
copied immediately to the channel 0 output
buffer if a
transfer is not currently in progress. When
this bit is
asserted, main processor writes to channel
0's
SIC0OUTBUF will only be copied to the
outbuffer
on vblank. This is used to control the
timing of
commands to 3D LCD shutter glasses
connected to
the VI.
1 = Copy SIC0OUTBUF to output buffer only
on
vblank.
0 = Copy SIC0OUTBUF to output buffer after
writing.
2 VBCPY1 RW 0 .times. 0 Vblank copy output channel 1: See
Description for
SIPOLL[VBCPY0].
1 VBCPY2 RW 0 .times. 0 Vblank copy output channel 2: See
Description for
SIPOLL[VBCPY0].
0 VBCPY3 RW 0 .times. 0 Vblank copy output channel 3: See
Description for
SIPOLL[VBCPY0].
SICOMCSR SI Communication Control Status Register
Mnemonic: SICOMCSR
Offset: 0x34
Size 32 bits SICOMCSR
Bits Mnemonic Type Reset Description
31 TCINT RWC 0 .times. 0 Transfer Complete Interrupt Status
and clear. On
read this bit indicates the current
status of the
communication transfer complete
interrupt. When a
`1` is written to this register, the
interrupt is cleared.
Write:
0 = No effect
1 = Transfer Complete Interrupt
Read:
0 = Transfer Complete Interrupt not
requested
1 = Transfer Complete Interrupt has been
requested
30 TCINTMSK RW 0 .times. 0 Transfer Complete Interrupt Mask:
Interrupt masking
prevents the interrupt from being sent to
the main
processor, but does not affect the
assertion of
SICOMCSR[TCINT]
0 = Interrupt masked
1 = Interrupt enabled
29 COMERR R 0 .times. 0 Communication Error: This indicates
whether the
last SI communication transfer had an
error. See SiSr
for the cause of the error.
0 = No
1 = Error on transfer
28 RDSTINT R 0 .times. 0 Read Status Interrupt Status and
clear. On read this
bit indicates the current status of the
Read Status
interrupt. The interrupt is set whenever
SISR[RDSTn] bits are set. The interrupt
is cleared
when all of the RdSt bits in the SISR are
cleared by
reading from the Si Channel Input
Buffers. This
interrupt can be used to indicate that a
polling transfer
has completed and new data is captured in
the input
registers
Read:
0 = Transfer Complete Interrupt not
requested
1 = Transfer Complete Interrupt has been
requested
27 RDSTINTMSK RW 0 .times. 0 Read Status interrupt Mask:
Interrupt masking
prevents the interrupt from being sent to
the main
processor, but does not affect the
assertion of
SICOMCSR[RDSTINT]
0 = Interrupt masked
1 = Interrupt enabled
26:23 R 0 .times. 0 Reserved
22:16 OUTLNGTH RW 0 .times. 0 Communication Channel Output Length
in bytes.
Minimum transfer is 1 byte. A value of 0
.times. 00 will
transfer 128 bytes. These bits should not
be modified
while SICOM transfer is in progress.
15 R 0 .times. 0 Reserved
14:8 INLNGTH RW 0 .times. 0 Communication Channel Output Length
in bytes.
Minimum transfer is 1 byte. A value of 0
.times. 00 will
transfer 128 bytes. These bits should not
be modified
while SICOM transfer is in progress.
2:1 CHANNEL RW 0 .times. 0 Channel: determines which SI
channel will be used
the communication interface.
00 = Channel 1
01 = Channel 2
10 = Channel 3
11 = Channel 4
These bits should not be modified while
SICOM
transfer is in progress.
0 TSTART RW 0 .times. 0 Transfer Start: When a `1` is
written to this register,
the current communication transfer is
executed. The
transfer begins immediately after the
current
transaction on this channel has
completed. When
read this bit represents the current
transfer status.
Once a communication transfer has been
executed,
polling will resume at the next vblank if
the channel's
SIPOLL[ENn] bit is set.
Write:
0 = Do not start command
1 = Start command
Read:
0 = Command Complete
1 = Command Pending
When programming the SICOMCSR after a SICOM transfers has already
started (e.g., SICOMCSR[TSTART] is set), the example software reads the current
value first, then and/or in the proper data and then write the new data back.
The software should not modify any of the transfer parameters (OUTLNGTH,
INLNGTH, CHANNEL) until the current transfer is complete. This is done to
prevent a SICOM transfer already in progress from being disturbed. When writing
the data back, the software should not set the TSTART bit again unless the
current transfer is complete and another transfer is required.
SISI SI
Status Register
Mnemonic: SISR
Offset: 0x38
Size 32 bits
SISR
Bits Mnemonic Type Reset Description
31 WR RW 0 .times. 0 Write SICnOUTBUF Register: This
register controls
and indicates whether the SICnOUTBUFs have
been
copied to the double buffered output buffers.
This bit
is cleared after the buffers have been
copied.
Write
1 = Copy all buffers
0 = No effect
Read
1 = Buffer not copied
0 = Buffer copied
30 R 0 .times. 0 Reserved
29 RDST0 R 0 .times. 0 Read Status SIC0OINBUF Register: This
register
indicates whether the SIC0INBUFs have been
captured new data and whether the data has
already
been read by the main processor (read
indicated by
main processor read of SIC01NBUF[ERRSTAT,
ERRLATCH, INPUT0, INPUT1)]
1 = New data available, not read by main
processor
0 = No new data available, already read by
main
processor
28 WRST0 R 0 .times. 0 Write Status SIC0OUTBUF Register: This
register
indicates whether the SIC0OUTBUFs have been
copied to the double buffered output buffers.
This bit
is cleared after the buffers have been
copied.
1 = Buffer not copied
0 = Buffer copied
27 NOREP0 RWC 0 .times. 0 No Response Error Channel 0: This
register indicates
that a previous transfer resulted in no
response from
the controller. This can also be used to
detect
whether a controller is connected. If no
controller is
connected, this bit will be set. Once set
this bit
remains set until it is cleared by the main
processor.
To clear this bit write `1` to this register.
Write:
0 = No effect
1 = Clear No Response Error
Read:
0 = No Response Error not asserted
1 = No Response Error asserted
26 COLL0 RWC 0 .times. 0 Collision Error Channel 0: This
register indicates
data collision between controller and main
unit.
Once set this bit remains set until it is
cleared by the
main processor. To clear this bit write `1`
to this
register.
Write:
0 = No effect
1 = Clear Collision Error
Read:
0 = Collision Error not asserted
1 = Collision Error asserted
25 OVRUN0 RWC 0 .times. 0 Over Run Error Channel 0: This register
indicates
that the main unit has received more data
than
expected. Once set this bit remains set until
it is
cleared by the main processor. To clear this
bit write
`1' to this register.
Write:
0 = No effect
1 = Clear Over Run Error
Read:
0 = Over Run Error not asserted
1 = Over Run Error asserted
24 UNRUN RWC 0 .times. 0 Under Run Error Channel 0: This
register indicates
that the main unit has received less data
than
expected. Once set this bit remain set until
it is.
cleared by the main processor. To clear this
bit write
`1` to this register.
Write:
0 = No effect
1 = Clear Under Run Error
Read:
0 = Under Run not asserted
1 = Under Run asserted
23:22 R 0 .times. 0 Reserved
21 RDST1 R 0 .times. 0 Read Status SIC1OINBUF Register: See
SISR[RDST0].
20 WRST1 R 0 .times. 0 Write Status SIC0OUTBUF Register: See
SISR[WRST0].
19 NOREP1 RWC 0 .times. 0 No Response Error Channel 1: See
SISR[NOREP0].
18 COLL1 RWC 0 .times. 0 Collision Error Channel 1: See
SISR[COLL0].
17 OVRUN1 RWC 0 .times. 0 Over Run Error Channel 1: See
SISR[OVRUN0].
16 UNRUN1 RWC 0 .times. 0 Under Run Error Channel 1: See
SISR[UNRUN0].
15:14 R 0 .times. 0 Reserved
13 RDST2 R 0 .times. 0 Read Status SIC1OINBUF Register: See
SISR[RDST2].
12 WRST2 R 0 .times. 0 Write Status SIC0OUTBUF Register: See
SISR[WRST2].
11 NOREP2 RWC 0 .times. 0 No Response Error Channel 2: See
SISR[NOREP0].
10 COLL2 RWC 0 .times. 0 Collision Error Channel 2: See
SISR[COLL0].
9 OVRUN2 RWC 0 .times. 0 Over Run Error Channel 2: See
SISR[OVRUN0].
8 UNRUN2 RWC 0 .times. 0 Under Run Error Channel 2: See
SISR[UNRUN0].
7:6 R 0 .times. 0 Reserved
5 RDST3 R 0 .times. 0 Read Status SIC1OINBUF Register: See
SISR[RDST2].
4 WRST3 R 0 .times. 0 Write Status SIC0OUTBUF Register: See
SISR[WRST2].
3 NOREP3 RWC 0 .times. 0 No Response Error Channel 3: See
SISR[NOREP0].
2 COLL3 RWC 0 .times. 0 Collision Error Channel 3: See
SISR[COLL0].
1 OVRUN3 RWC 0 .times. 0 Over Run Error Channel 3: See
SISR[OVRUN0].
0 UNRUN3 RWC 0 .times. 0 Under Run Error Channel 3: See
SISR[UNRUN0].
SIEXILK SI EXI Clock Lock
Mnemonic: SIEXILK
Offset: Ox3C
Size 32 bits SIEXILK
Bits Mnemonic Type Reset Description
31 LOCK RW 0 .times. 1 Lock: This bit prevents the main
processor from setting the EXI clock
frequencies to 32 MHz.
0 = EXI Clocks Unlocked, 32 MHz
EXICLK setting permitted.
1 = EXI Clock Locked, 32 MHz
EXICLK setting not permitted.
30:0 R 0 .times. 0 Reserved
FIG. 8D is an even more detailed overall view of
serial interface 1000 showing the details of serial
interface communication circuitry and registers 1012. Controllers 52a and 52b
(and 52c and 52d, if present) are connected to game console 54 via connector
ports 1002. Modem 1404 modulates and demodulates data transferred between the
controllers and the console. In the example system, communication between the
console and the controllers uses duty-cycle (pulse-width) modulation and the
data is communicated over one line. The communication is half-duplex. The byte
transfer order is "big-endian" in which within a given multi-byte numeric
representation, the most significant byte has the lowest address (i.e., the data
is transferred "big-end" first). Controller input/output buffer 1016 is used for
normal data transfers involving controllers 52a-52d. As shown in FIG. 8D,
input/output buffer 1016 is arranged as a double buffer. Communication RAM 1014
is provided for use in variable-size data transfers to and from controllers
52a-52d. In the example system, the maximum data size of these variable-size
data transfers is 32 words. Of course, the present invention is not limited in
this respect. Channel selector circuit 1408 controls selectors 1412a-1412d to
selectively connect modem 1404 to either communication RAM 1014 or input/output
buffer 1016. An HV counter latch circuit 1406 latches the screen position of a
flash signal when a trigger input is received from a light gun unit. In the
example system shown in FIG. 8, triggers inputs to the HV counter latch circuit
1406 are provided for connectors 1 and 2 only. It will be apparent that trigger
inputs may be provided for the other connectors if desired. HV counter latch
circuit 1406 may also be used with light pens connected to connectors 1 and/or
2.
Additional details of the serial interface may be found
in application Ser. No. 09/722,664 filed Nov. 28, 2000 of Shimuzu et al.
entitled "Controller Interface for a Graphics System", the contents of which are
incorporated herein.
Cut from USPTO #6609977
org - ogamespec@gmail.com


Your privacy is important to us. It is Midnight Lizard's policy to respect your privacy regarding any information being processed by the extension downloaded from one of the following locations:
Midnight Lizard web-extension does not collect any of your personal information, browsing history, IP addresses, etc. Also it does not sell or transfer your personal information to advertisers or other third-parties.
Midnight Lizard web-extension does not use browser cookies. To optimize initial page load it stores last applied settings in localStorage. To optimize consequent page loads it caches styles and images processing results in sessionStorage.
To store user settings Midnight Lizard web-extension uses chrome.storage in Chromium-based browsers and browser.storage in Firefox. By default user settings are synchronized between user devices but this behavior can be opted out on the Global settings tab.
Midnight Lizard web-extension has links to external sites that are not operated by us. Please be aware that we have no control over the content and practices of these sites, and cannot accept responsibility or liability for their respective privacy policies.
In the future Midnight Lizard web-extension might include user login form in order to provide some personalized services to the user. Any personal information exchange related to this will be a subject of the Website Privacy Policy.
This policy is effective as of 1 January 2019.


Then, specify what should happen when the element is dragged. In the example above, the ondragstart attribute calls a function, drag(event), that specifies what data to be dragged.The dataTransfer.setData() method sets the data type and the value of the dragged data:


This page contains some extra notes about setting up SEEK for production (i.e. for real use rather than for development).
By reading and following these extra notes, you will more performance out of SEEK, and reduce the ongoing maintenance.
This will make sure some of the rake tasks affect the appropriate database.
To save time later there are also some additional packages to install:
sudo apt-get install apache2-mpm-prefork apache2-prefork-dev libapr1-dev libaprutil1-dev libcurl4-openssl-dev
You will need to install SEEK as the www-data user. First, to make the installation simpler, give this user a dedicated home directory:
sudo /etc/init.d/apache2 stop sudo usermod -d /home/www-data www-data sudo usermod -s /bin/bash www-data sudo mkdir /home/www-data sudo chown www-data /home/www-data sudo /etc/init.d/apache2 start
We recommend installing SEEK in /srv/rails/seek - first you need to create this and grant permissions to www-data
sudo mkdir -p /srv/rails sudo chown www-data /srv/rails
Now switch to the www-data user
sudo su - www-data cd /srv/rails
Before following the standard INSTALL guide you need to set an environment variable to indicate that you intend to setup and run SEEK as production.
export RAILS_ENV=production
you will need to reset this variable if you close your shell and start a new session
You can now follow the overall Installation Guide, and then return to this page for some additional steps to get SEEK running together with Apache, and also automating the required services.
If you have problems with requiring a sudo password during the RVM steps - first setup RVM and ruby-1.9.3 as a user with sudo access, and repeat the steps as the www-data user. This means the required packages should then be installed. At the time of writing this guide this shouldn't be necessary.
Assets - such as images, javascript and stylesheets, need to be precompiled - which means minifying them, grouping some together into a single file, and compressing. These then get placed into public/assets. To compile them run the following command. This can take some time, so be patient
bundle exec rake assets:precompile
First you need to setup Passenger Phusion .Still as the www-data user, run the command:
bundle exec passenger-install-apache2-module
This will compile a module for Apache, and at the end present you with some lines that need adding to /etc/apache2/http.conf. These will look something like the following, but the paths will most likely be different:
LoadModule passenger_module<EMAIL_ADDRESS>PassengerRoot<EMAIL_ADDRESS>PassengerDefaultRuby /home/www-data/.rvm/wrappers/ruby-1.9.3-p448@seek/ruby
You will need to be a user that has sudo permissions, and edit this file:
sudo nano /etc/apache2/http.conf
Now create a virtual host definition for SEEK:
sudo nano /etc/apache2/sites-available/seek
which looks like (if you have registered a DNS for your site, then set ServerName appropriately):
<VirtualHost *:80> ServerName www.yourhost.com DocumentRoot /srv/rails/seek/public <Directory /srv/rails/seek/public> AllowOverride all Options -MultiViews </Directory> <LocationMatch "^/assets/.*$"> Header unset ETag FileETag None # RFC says only cache for 1 year ExpiresActive On ExpiresDefault "access plus 1 year" </LocationMatch> </VirtualHost>
The LocationMatch block tells Apache to serve up the assets (images, CSS, Javascript) with a long expiry time, leading to better performance since these items will be cached. You may need to enable the headers and expires modules for Apache, so run:
sudo a2enmod headers sudo a2enmod expires
Now enable the SEEK site, and disable the default that is installed with Apache, and restart:
sudo a2ensite seek sudo a2dissite default sudo service apache2 restart
If you now visit localhost (note there is no 3000 port) - you should see SEEK.
If you wish to restart SEEK, maybe after an upgrade, without restarting Apache you can do so by running (as www-data)
touch /srv/rails/seek/tmp/restart.txt
The following steps show how to setup sunspot:solr search, delayed_job and soffice to run as a service, and automatically start and shutdown when you restart the server.
Create the file /etc/init.d/solr-seek and copy the contents of gist.github.com/3143434 into it.
Then run
sudo chmod +x /etc/init.d/solr-seek sudo update-rc.d solr-seek defaults
start it up with:
sudo /etc/init.d/solr-seek start
Create the file /etc/init.d/delayed_job-seek and copy the contents of gist.github.com/3169625 into it.
The run:
sudo chmod +x /etc/init.d/delayed_job-seek sudo update-rc.d delayed_job-seek defaults
start it up with:
sudo /etc/init.d/delayed_job-seek start
Create the file /etc/init.d/soffice and copy the contents of gist.github.com/3787679 into it.
The run:
sudo chmod +x /etc/init.d/soffice sudo update-rc.d soffice defaults
start it up with:
sudo /etc/init.d/soffice start


--- title: "Learn to wait" layout: "post" permalink: "/2014/05/learn-to-wait.html" uuid: "8077037841213540359" guid: "tag:blogger.com,1999:blog-5396845717692802313.post-8077037841213540359" date: "2014-05-16 05:23:00" updated: "2014-05-16 05:23:47" description: blogger: siteid: "5396845717692802313" postid: "8077037841213540359" comments: "0" categories: author: name: "Zhujun Yao" url: "https://plus.google.com/107886982505645319479?rel=author" image: "//lh5.googleusercontent.com/-sv9wVMH_yJA/AAAAAAAAAAI/AAAAAAAAABY/RoZM-GWMhyI/s512-c/photo.jpg" ---


A GREAT conflict was about to come off between the Birds and the Beasts. When the two armies were collected together the Bat hesitated which to join. The Birds that passed his perch said: “Come with us”; but he said: “I am a Beast.”  Luckily at the last moment peace was made, and no battle took place, so the Bat came to the Birds and wished to join in the rejoicings, but they all turned against him and he had to fly away. He then went to the Beasts, but soon had to beat a retreat, or else they would have torn him to pieces. “Ah,” said the Bat, “I see now,
“HE THAT IS NEITHER ONE THING NOR THE OTHER HAS NO FRIENDS.”
THE HART was once drinking from a pool and admiring the noble figure he made there. “Ah,” said he, “where can you see such noble horns as these, with such antlers!  At that moment a Hunter approached and sent an arrow whistling after him. Away bounded the Hart, and soon, by the aid of his nimble legs, was nearly out of sight of the Hunter; but not noticing where he was going, he passed under some trees with branches growing low down in which his antlers were caught, so that the Hunter had time to come up. “Alas! alas!” cried the Hart:
“WE OFTEN DESPISE WHAT IS MOST USEFUL TO US.”
A SERPENT in the course of its wanderings came into an armourer’s shop. As he glided over the floor he felt his skin pricked by a file lying there. In a rage he turned round upon it and tried to dart his fangs into it; but he could do no harm to heavy iron and had soon to give over his wrath.
“IT IS USELESS ATTACKING THE INSENSIBLE.”
A MAN came into a Wood one day with an axe in his hand, and begged all the Trees to give him a small branch which he wanted for a particular purpose. The Trees were good-natured and gave him one of their branches. What did the Man do but fix it into the axe head, and soon set to work cutting down tree after tree. Then the Trees saw how foolish they had been in giving their enemy the means of destroying themselves.
A GAUNT Wolf was almost dead with hunger when he happened to meet a House-dog who was passing by. “Ah, Cousin,” said the Dog. “I knew how it would be; your irregular life will soon be the ruin of you. Why do you not work steadily as I do, and get your food regularly given to you?”
“I would have no objection,” said the Wolf, “if I could only get a place.”
“I will easily arrange that for you,” said the Dog; “come with me to my master and you shall share my work.”
So the Wolf and the Dog went towards the town together. On the way there the Wolf noticed that the hair on a certain part of the Dog’s neck was very much worn away, so he asked him how that had come about.
“Oh, it is nothing,” said the Dog. “That is only the place where the collar is put on at night to keep me chained up; it chafes a bit, but one soon gets used to it.”
“Is that all?” said the Wolf.
ONE fine day it occurred to the Members of the Body that they were doing all the work and the Belly was having all the food. So they held a meeting, and after a long discussion, decided to strike work till the Belly consented to take its proper share of the work. So for a day or two, the Hands refused to take the food, the Mouth refused to receive it, and the Teeth had no work to do. But after a day or two the Members began to find that they themselves were not in a very active condition: the Hands could hardly move, and the Mouth was all parched and dry, while the Legs were unable to support the rest. So thus they found that even the Belly in its dull quiet way was doing necessary work for the Body, and that all must work together or the Body will go to pieces.
A HART hotly pursued by the hounds fled for refuge into an ox-stall, and buried itself in a truss of hay, leaving nothing to be seen but the tips of his horns. Soon after the Hunters came up and asked if any one had seen the Hart. The stable boys, who had been resting after their dinner, looked round, but could see nothing, and the Hunters went away. Shortly afterwards the master came in, and looking round, saw that something unusual had taken place. He pointed to the truss of hay and said: “What are those two curious things sticking out of the hay?” And when the stable boys came to look they discovered the Hart, and soon made an end of him. He thus learnt that
“NOTHING ESCAPES THE MASTER’s EYE.”
ONE hot summer’s day a Fox was strolling through an orchard till he came to a bunch of Grapes just ripening on a vine which had been trained over a lofty branch. “Just the things to quench my thirst,” quoth he. Drawing back a few paces, he took a run and a jump, and just missed the bunch. Turning round again with a One, Two, Three, he jumped up, but with no greater success.
A QUARREL had arisen between the Horse and the Stag, so the Horse came to a hunter to ask his help to take revenge on the Stag. The Hunter agreed, but said: “If you desire to conquer the Stag, you must permit me to place this piece of iron between your jaws, so that I may guide you with these reins, and allow this saddle to be placed upon your back so that I may keep steady upon you as we follow after the enemy.” The Horse agreed to the conditions, and the Hunter soon saddled and bridled him. Then with the aid of the Hunter the Horse soon overcame the Stag, and said to the Hunter: “Now, get off, and remove those things from my mouth and back.”
“Not so fast, friend,” said the Hunter.
A PEACOCK once placed a petition before Juno desiring to have the voice of a nightingale in addition to his other attractions; but Juno refused his request. When he persisted, and pointed out that he was her favourite bird, she said:
“BE CONTENT WITH YOUR LOT; ONE CANNOT BE FIRST IN EVERYTHING.”
WHEN first the Fox saw the Lion he was terribly frightened, and ran away and hid himself in the wood. Next time however he came near the King of Beasts he stopped at a safe distance and watched him pass by. The third time they came near one another the Fox went straight up to the Lion and passed the time of day with him, asking him how his family were, and when he should have the pleasure of seeing him again; then turning his tail, he parted from the Lion without much ceremony.
“FAMILIARITY BREEDS CONTEMPT.”
A MAN and a Lion were discussing the relative strength of men and lions in general. The Man contended that he and his fellows were stronger than lions by reason of their greater intelligence. “Come now with me,” he cried, “and I will soon prove that I am right.” So he took him into the public gardens and showed him a statue of Hercules overcoming the Lion and tearing his mouth in two.
“That is all very well,” said the Lion, “but proves nothing, for it was a man who made the statue.”
“WE CAN EASILY REPRESENT THINGS AS WE WISH THEM TO BE.”
IN a field one summer’s day a Grasshopper was hopping about, chirping and singing to its heart’s content. An Ant passed by, bearing along with great toil an ear of corn he was taking to the nest.
“Why not come and chat with me,” said the Grasshopper, “instead of toiling and moiling in that way?”
“I am helping to lay up food for the winter,” said the Ant, “and recommend you to do the same.”
“Why bother about winter?” said the Grasshopper; “we have got plenty of food at present.” But the Ant went on its way and continued its toil. When the winter came the Grasshopper had no food, and found itself dying of hunger, while it saw the ants distributing every day corn and grain from the stores they had collected in the summer. Then the Grasshopper knew:
“IT IS BEST TO PREPARE FOR THE DAYS OF NECESSITY.”
“WELL, little one,” said a Tree to a Reed that was growing at its foot, “why do you not plant your feet deeply in the ground, and raise your head boldly in the air as I do?”
“I am contented with my lot,” said the Reed. “I may not be so grand, but I think I am safer.”
“Safe!” sneered the Tree. “Who shall pluck me up by the roots or bow my head to the ground?” But it soon had to repent of its boasting, for a hurricane arose which tore it up from its roots, and cast it a useless log on the ground, while the little Reed, bending to the force of the wind, soon stood upright again when the storm had passed over.
“OBSCURITY OFTEN BRINGS SAFETY.”
A FOX was boasting to a Cat of its clever devices for escaping its enemies. “I have a whole bag of tricks,” he said, “which contains a hundred ways of escaping my enemies.”
“I have only one,” said the Cat; “but I can generally manage with that.” Just at that moment they heard the cry of a pack of hounds coming towards them, and the Cat immediately scampered up a tree and hid herself in the boughs. “This is my plan,” said the Cat. “What are you going to do?” The Fox thought first of one way, then of another, and while he was debating the hounds came nearer and nearer, and at last the Fox in his confusion was caught up by the hounds and soon killed by the huntsmen.
A WOLF found great difficulty in getting at the sheep owing to the vigilance of the shepherd and his dogs. But one day it found the skin of a sheep that had been flayed and thrown aside, so it put it on over its own pelt and strolled down among the sheep. The Lamb that belonged to the sheep, whose skin the Wolf was wearing, began to follow the Wolf in the Sheep’s clothing; so, leading the Lamb a little apart, he soon made a meal off her, and for some time he succeeded in deceiving the sheep, and enjoying hearty meals.
“APPEARANCES ARE DECEPTIVE.”
A DOG looking out for its afternoon nap jumped into the Manger of an Ox and lay there cosily upon the straw. But soon the Ox, returning from its afternoon work, came up to the Manger and wanted to eat some of the straw. The Dog in a rage, being awakened from its slumber, stood up and barked at the Ox, and whenever it came near attempted to bite it. At last the Ox had to give up the hope of getting at the straw, and went away muttering:
“AH, PEOPLE OFTEN GRUDGE OTHERS WHAT THEY CANNOT ENJOY THEMSELVES.”
IN the old days men used to worship stocks and stones and idols, and prayed to them to give them luck. It happened that a Man had often prayed to a wooden idol he had received from his father, but his luck never seemed to change. He prayed and he prayed, but still he remained as unlucky as ever. One day in the greatest rage he went to the Wooden God, and with one blow swept it down from its pedestal. The idol broke in two, and what did he see? An immense number of coins flying all over the place.
A FISHER once took his bagpipes to the bank of a river, and played upon them with the hope of making the fish rise; but never a one put his nose out of the water. So he cast his net into the river and soon drew it forth filled with fish. Then he took his bagpipes again, and, as he played, the fish leapt up in the net. “Ah, you dance now when I play,” said he.

THERE was once a young Shepherd Boy who tended his sheep at the foot of a mountain near a dark forest.  He rushed down towards the village calling out “Wolf, Wolf,” and the villagers came out to meet him, and some of them stopped with him for a considerable time. This pleased the boy so much that a few days afterwards he tried the same trick, and again the villagers came to his help. But shortly after this a Wolf actually did come out from the forest, and began to worry the sheep, and the boy of course cried out “Wolf, Wolf,” still louder than before. But this time the villagers, who had been fooled twice before, thought the boy was again deceiving them, and nobody stirred to come to his help. So the Wolf made a good meal off the boy’s flock, and when the boy complained, the wise man of the village said:
“A LIAR WILL NOT BE BELIEVED, EVEN WHEN HE SPEAKS THE TRUTH.”
A YOUNG Man had been caught in a daring act of theft and had been condemned to be executed for it. He expressed his desire to see his Mother, and to speak with her before he was led to execution, and of course this was granted. When his Mother came to him he said: “I want to whisper to you,” and when she brought her ear near him, he nearly bit it off. All the bystanders were horrified, and asked him what he could mean by such brutal and inhuman conduct. “It is to punish her,” he said. “When I was young I began with stealing little things, and brought them home to Mother. Instead of rebuking and punishing me, she laughed and said: ‘It will not be noticed.’
IN the old days, when men were allowed to have many wives a middle-aged Man had one wife that was old and one that was young; each loved him very much, and desired to see him like herself. Now the Man’s hair was turning grey, which the young Wife did not like, as it made him look too old for her husband. So every night she used to comb his hair and pick out the white ones. But the elder Wife saw her husband growing grey with great pleasure, for she did not like to be mistaken for his mother. So every morning she used to arrange his hair and pick out as many of the black ones as she could. The consequence was the Man soon found himself entirely bald.

Now it chanced that a Wolf was passing close under the window as this was said. So he crouched down by the side of the house and waited. “I am in good luck today,” thought he. “It is sure to cry soon, and a daintier morsel I haven’t had for many a long day.” So he waited, and he waited, and he waited, till at last the child began to cry, and the Wolf came forward before the window, and looked up to the Nurse, wagging his tail. But all the Nurse did was to shut down the window and call for help, and the dogs of the house came rushing out. “Ah,” said the Wolf as he galloped away,
“ENEMIES’ PROMISES WERE MADE TO BE BROKEN.”
A TORTOISE desired to change its place of residence, so he asked an Eagle to carry him to his new home, promising her a rich reward for her trouble. The Eagle agreed, and seizing the Tortoise by the shell with her talons, soared aloft. On their way they met a Crow, who said to the Eagle: “Tortoise is good eating.” “The shell is too hard,” said the Eagle in reply. “The rocks will soon crack the shell,” was the Crow’s answer; and the Eagle, taking the hint, let fall the Tortoise on a sharp rock, and the two birds made a hearty meal off the Tortoise.
“Never Soar Aloft On An Enemy’s Pinions”
ONE fine day two Crabs came out from their home to take a stroll on the sand. “Child,” said the mother, “you are walking very ungracefully. You should accustom yourself to walking straight forward without twisting from side to side.”
“Pray, mother,” said the young one, “do but set the example yourself, and I will follow you.”
“EXAMPLE IS THE BEST PRECEPT.”
AN ASS once found a Lion’s skin which the hunters had left out in the sun to dry. He put it on and went towards his native village. All fled at his approach, both men and animals, and he was a proud Ass that day. In his delight he lifted up his voice and brayed, but then every one knew him, and his owner came up and gave him a sound cudgelling for the fright he had caused. And shortly afterwards a Fox came up to him and said: “Ah, I knew you by your voice.”
“FINE CLOTHES MAY DISGUISE, BUT SILLY WORDS WILL DISCLOSE A FOOL.”
TWO Fellows were travelling together through a wood, when a Bear rushed out upon them. One of the travellers happened to be in front, and he seized hold of the branch of a tree, and hid himself among the leaves. The other, seeing no help for it, threw himself flat down upon the ground, with his face in the dust. The Bear, coming up to him, put his muzzle close to his ear, and sniffed and sniffed.  Then the fellow in the tree came down to his comrade, and, laughing, said “What was it that Master Bruin whispered to you?” “He told me,” said the other,
“NEVER TRUST A FRIEND WHO DESERTS YOU AT A PINCH.”


{{records1[0]}}
{{records1[1]}}
{{records1[2]}}
{{records1[3]}}
{{x.file_name}}
{{x.saved_records}}
{{x.non_saved_records}}
{{x.error_log}}


Top 10 Two-Wheelers In October 2019 – Honda Activa Beats Hero Splendor
by Team GaadiWaadiLast month, Honda Activa topped the sales chart by clocking a sale of 281,273 units, while Hero Splendor found itself on the second place with a monthly sale of 264,137 units.
Honda Activa, the popular automatic scooter brand, has maintained its numero uno status by selling the highest number of copies in October 2019. Last month, the scooter brand registered a sales figure of 281,273 units, which helped it settle at the top of the monthly sales chart. This is a 7.24 per cent increase from 262,260 units sold in October 2019.
The second place has been taken by the very popular Hero Splendor, which sold 264,137 units last month. This is a 1.57 per cent drop from 268,377 units sold in October 2018. Also, the Splendor was the top-selling two-wheeler in October 2018, ahead of the Activa (262,260 units).
Even the third spot on the monthly sales charts goes to a motorcycle from Hero MotoCorp. The HF Deluxe was the third most popular two-wheeler with a sale of 185,751 units in October 2019. This is a drop of 7.2 per cent from the 200,312 units sold in the corresponding month last year.
| Model | October 2019 Sales | October 2018 Sales |
| 1. Honda Activa | 2,81,273 | 2,62,260 |
| 2. Hero Splendor | 2,64,137 | 2,68,377 |
| 3. Hero HF Deluxe | 1,85,751 | 2,00,312 |
| 4. Bajaj Pulsar | 95,509 | 90,363 |
| 5. Honda CB Shine | 87,743 | 91,319 |
| 6. TVS Jupiter | 74,560 | 1,02,132 |
| 7. Bajaj Platina | 70,466 | 74,064 |
| 8. Bajaj CT 100 | 61,483 | 93,676 |
| 9. TVS XL Super | 60,174 | 82,357 |
| 10. Suzuki Access | 53,552 | 45,090 |
Last month, three models from Bajaj Auto, viz Pulsar, Platina and CT100, made it to the top 10 selling two-wheelers. The Pulsar range of motorcycle found itself at the fourth spot with a sale of 95,509 units. On the other hand, the Platina and the CT100 were settled at seventh and eighth spot by clocking a sales figure of 70,466 units and 61,483 units, respectively.
TVS Jupiter, which has been the second-highest selling scooter in the country, managed to land at the sixth spot by clocking a total sale of 74,560 units. It may be noted that the Jupiter had managed to make it to the fourth spot in October 2018. The XL Super, on the other hand, made it to the ninth spot by clocking a monthly sale of 60,174 units.
The tenth position has been occupied by the Suzuki Access. It registered a sale of 53,552 units last month. It may be noted here that the Access wasn’t a part of the top 10 selling list of October 2018. While the Hero Glamour, which was on the tenth spot of the previous year’s list, has failed to make it to the last month’s list of best-selling 10 models.


Manakad Road,Thodupuzha. Thodupuzha, Idukki - 685584(Near Co-Operative Hospital)
0486 2220547
+91<PHONE_NUMBER> +91<PHONE_NUMBER> +91<PHONE_NUMBER> +91<PHONE_NUMBER>


My Test Store
Shopping Cart
Product
Quantity
Price
Air Conditioner SPL 1.5 HP NP
1
₦ 550
Air Conditioner Instalation Kit 5hp
1
₦ 500
5M Cables
1
₦ 500
Total
₦
Total + Shipping
₦
Order Summary
Items:
₦ 1,550
Shipping & Handling:
₦
Total:
₦
Shipping Address
31 Kade St, Abuja, Nigeria
Billing Information
John Doe
31 Kade St, Abuja, Nigeria


Image
{{ image.name }}Replace the following credentials in application.properties
client-key : activated client id
secret-key : client secret
bucket-name : the bucket name where to upload the image
region : region


--- layout: default description: "五子棋" header-img: "img/404-bg.jpg" permalink: /games/gomokupvp.html ---


Module sqltable.pool
A connection pooling object.
This allows for lots of tables to be opened with only as many connections as are needed to be created. Also, it provides for some level of fault tolerance: stale connections are automatically purged.
Functions
| _pool.type (pool) | Return the type of database this pool connects to. |
| _pool.get (pool) | Checkout a connection from the pool for use. |
| _pool.put (pool, connection) | Return a connection to the pool. |
| _pool.connections (pool) | Returns a count of the total number of connections this pool has open. |
| _pool.outstanding (pool) | Returns a count of connections that exist, but are in use and not waiting in the pool. |
| _pool.close (pool) | Shuts down the pool. |
| _pool.reset (pool) | Resets a pool by closing all connections, then reconnecting with just one. |
| _pool.setup_hook (pool, fcn) | Sets a 'setup hook' that will be called every time a new connection is opened. |
| _pool.connect (params) | "Connect" to a database. |
Functions
- _pool.type (pool)
-
Return the type of database this pool connects to.
Parameters:
- pool Pool to checked
Returns:
-
Database type of pool
- _pool.get (pool)
-
Checkout a connection from the pool for use.
Parameters:
- pool Pool to retrieve connection from
Returns:
-
A usable LuaDBI connection
- _pool.put (pool, connection)
-
Return a connection to the pool.
Parameters:
- pool Pool receiving connection
- connection Connection to be returned
- _pool.connections (pool)
-
Returns a count of the total number of connections this
pool has open.
Parameters:
- pool Pool to check
Returns:
-
Total number of connections in pool
- _pool.outstanding (pool)
-
Returns a count of connections that exist, but are in use
and not waiting in the pool.
Parameters:
- pool Pool to check
Returns:
-
Number of outstanding connections in pool
- _pool.close (pool)
-
Shuts down the pool.
THIS EXPLODES BADLY if there are outstanding connections not yet returned. Stop all queries before calling it!
Parameters:
- pool Pool to close
- _pool.reset (pool)
-
Resets a pool by closing all connections, then reconnecting
with just one. This is handy if your program forks and/or you
want to recycle all file handles.
Parameters:
- pool Pool to reset
- _pool.setup_hook (pool, fcn)
-
Sets a 'setup hook' that will be called every time a new
connection is opened.
The pool will be reset once a hook is set, thus closing all open connections and reconnecting.
Parameters:
- pool this pool object
- fcn Setup hook to call
- _pool.connect (params)
-
"Connect" to a database. This opens the first connection to
a database to ensure the settings are correct, then returns
a pool object containing one connection.
Parameters:
- params


Christopher Doyle
"We have a responsibility to ensure we are contributing to the betterment of society, not the destruction of it."
Raphael Roake: How do you, if at all, navigate ethics in your practice?
Chrisopher Doyle: We have a very simple approach. We have a list of industries that we won't engage/work with. We also research every client we do take on to ensure we understand their culture, their product and their impact on the world.
RR: Do you think we (as designers) have a responsibility to consider and challenge things such as the ethics behind the companies / products / services we engage with?
CD: Yes, absolutely. Whether it's design or advertising—whatever you wanna call it—we are essentially helping businesses to sell ideas and products. We are directly linked to the visibility and success of a business. We have a responsibility to ensure we are contributing to the betterment of society, not the destruction of it.
RR: Are there any cases of this happening in your practice or in the wider industry that you thought were interesting or different?
CD: Not in our practice as yet, no. In a previous role I was asked to work on the rebrand of a church though and I refused. It was interesting. Quite an uncomfortable situation.
RR: How far do we push that with clients or bosses?
CD: As far we feel we should. I think it's about not entering into relationships that are questionable in the first place. As an employee I just couldn't do it. It felt right saying no, despite the challenges that came with it.
RR: And maybe any advice for a overly idealogical young design student? Or any other thoughts you have on the topic.
CD: Being idealogical is great. Certainly don't worry about being 'overly' ideological.
"My advice is to do good work, for work for good people, who run good businesses and get paid. It's not easy to consistently nail all four but that's our goal. "


--- layout: base title: "DITA Open Toolkit" toc: false ---
The DITA Open Toolkit, or DITA-OT for short, is a set of Java-based, open-source tools that provide processing for XML content authored in the Darwin Information Typing Architecture.
Download and install the toolkit to get started with topic-based writing and publishing.
Download DITA-OTThe DITA Open Toolkit is primarily a publishing tool used to convert DITA content into various output formats. The toolkit supports all versions of the OASIS DITA specification, including 1.0, 1.1, 1.2, and 1.3.
Note: While the DITA standard is owned and developed by OASIS, the DITA Open Toolkit project is governed separately. DITA-OT is an independent, open-source implementation of the DITA standard.
The following transformation types are supported out of the box with any toolkit installation:
PDF – PDF output is based on a plug-in that produces XSL Formatting Objects (XSL-FO) output. The XSL-FO output may be converted to PDF using an open-source rendering tool (Apache FOP) or commercial tools such as RenderX XEP or Antenna House Formatter.
HTML – HTML5 and XHTML output are supported along with a variety of HTML-based navigation types. The HTML output contains class values based on the DITA elements so CSS files may be used to customize the output style.
TocJS – The TocJS transformation type includes HTML5 output along with JavaScript-based frames for navigation, including table of contents (ToC) sections that expand and collapse.
HTML Help – Microsoft Compiled HTML Help output produces a compiled help (.chm) file with HTML topics, table of contents, and index.
Eclipse Help – Eclipse output is an HTML-based format that also produces navigation and index files for use with Eclipse information centers.
Eclipse Content – Normalized DITA plus Eclipse project files.
Java Help – HTML topics, table of contents and index for use with the Java Help platform.
ODT – OpenDocument Text is based on the Open Document Format for Office Applications (ODF) standard, for use with tools like OpenOffice and Google Docs.
Word RTF – Rich Text Format output is supported for basic content, but complex markup and some advanced features of DITA may not be supported.
DocBook – An earlier semantic markup language for technical documentation.
troff – troff-based man pages are supported; one man page is generated for each input topic. Note that tables are not supported by this transformation type.
The toolkit’s plug-in mechanism allows new transformation types to be added.
The DITA Open Toolkit is licensed for use under the Apache License 2.0. A copy of the Apache License 2.0 can be found at the root directory of the DITA Open Toolkit deliverable package.


Things my cat loves
Food
- He loves wet food.
- He also loves dry food
Scritches
- He loves scritches on his fuzzy head
- He loves scritches down his back and above his bum
- He pretends not to love scritches on his tum
Singing at me while I work
- He sings at me when I sleep
- He sings at me while I work
- He sings when he wants to play
- Most of all, he sings when he's hungry
He is the fuzziest boy and the best cat!


BITE CLUB
Dundee teen jailed after taking bite out of friend’s face in savage nightclub scrap over ex-boyfriend
by Aidan SmithA DUNDEE teen has been jailed for 16 months after biting her friend's face in a savage nightclub attack.
Danielle Gaffar, 19, carried out the frenzied assault on terrified Kyra Strachan, then 18, at Dundee's Aura club on February 3.
Dundee Sheriff Court heard the pair were friends but had fallen out over Gaffar's ex-boyfriend.
The court was told victim Strachan required plastic surgery as a result of the assault and also how Gaffar received death threats as a result of the publicity of the case.

Horror pictures posted on social media at the time showed a section of Kyra's cheek hanging off after the attack.
The victim also suffered bruising to her face and forehead.
Sheriff Thomas Hughes said there was “no alternative” to custody.


Trading_GeteBayDetailsResponseType Class Reference
| Inherits from | Trading_AbstractResponseType : NSObject |
| Declared in | Trading_GeteBayDetailsResponseType.h Trading_GeteBayDetailsResponseType.m |
Overview
Details about a specified site in response to GeteBayDetailsRequest.
If no DetailName
field is identified in the request, all elements of GeteBayDetailsResponse are
returned. Otherwise, eBay returns only the elements corresponding to the specified
DetailName fields. UpdateTime gives the time of modification of the most recently
modified DetailName.
@ingroup EBayAPIInterface
Tasks
-
countryDetails
Lists the country code and associated name of the countries supported by
property
the eBay system, regardless of the site specified in the request. -
currencyDetails
Lists the currencies supported by the eBay system, regardless of the site
property
specified in the request.
Note:
This container is only returned if CurrencyDetails is included as a
DetailName filter in the request, or if no DetailName filters are
used in the request.
-
dispatchTimeMaxDetails
A dispatch time specifies the maximum number of business days a seller commits
property
to for shipping an item to domestic buyers after receiving a cleared payment.
Returns all dispatch times in the system, regardless of the site specified in
the request.
Note:
This container is only returned if DispatchTimeMaxDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
paymentOptionDetails
Deprecated
property
Use GetCategoryFeatures instead, and pass in
PaymentMethods as a FeatureID value in the request. -
regionDetails
No longer returned; replaced by ShippingLocationDetails.
property -
shippingLocationDetails
Lists the regions and locations supported by eBay’s shipping services. Returns
property
all shipping locations supported by eBay, regardless of the site specified in
the request.
Note:
This container is only returned if ShippingLocationDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
shippingServiceDetails
Lists the shipping services supported by the specified eBay site. Returns only
property
the shipping services that are applicable to the site specified in the
request.
Note:
This container is only returned if ShippingServiceDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
siteDetails
Lists all available eBay sites and their associated SiteID numbers.
property
Note:
This container is only returned if SiteDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
taxJurisdiction
Details the different tax jurisdictions or tax regions applicable to the
property
site specified in the request.
Note:
This container is only returned if TaxJurisdiction is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
urlDetails
Lists eBay URLs that are applicable to the site specified in the request.\
property
Note:
This container is only returned if URLDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request
-
timeZoneDetails
Lists the details of the time zones supported by the eBay system.
property
Note:
This container is only returned if TimeZoneDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
itemSpecificDetails
The site’s validation rules (e.g., string lengths) for custom Item Specifics.
property
Note:
This container is only returned if ItemSpecificDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
unitOfMeasurementDetails
Lists the suggested unit-of-measurement strings to use with Item Specifics
property
descriptions.
Note:
This container is only returned if UnitOfMeasurementDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
regionOfOriginDetails
No longer returned.
property -
shippingPackageDetails
Lists the various shipping packages supported by the specified site.
property
Note:
This container is only returned if ShippingPackageDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
shippingCarrierDetails
Lists the shipping carriers supported by the specified site.
property
Note:
This container is only returned if ShippingCarrierDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
returnPolicyDetails
Lists the return policies supported by the eBay site specified in the request.
property
Note:
This container is only returned if ReturnPolicyDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
listingStartPriceDetails
Lists the minimum starting prices for the supported types of eBay listings.
property
Note:
This container is only returned if ListingStartPriceDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
buyerRequirementDetails
Details various eBay-buyer requirements.
property -
listingFeatureDetails
Details the listing features available for the site specified in the request.
property
Note:
This container is only returned if ListingFeatureDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
variationDetails
Site-level validation rules for multi-variation listings (for example, the
property
maximum number of variations per listing). Use GetCategoryFeatures to
determine which categories on a site support variations. Use
GetCategorySpecifics for rules related to recommended or required variation
specifics.
Note:
This container is only returned if VariationDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
excludeShippingLocationDetails
Lists the locations supported by the ExcludeShipToLocation feature. These are
locations that a seller can list as areas where they will not ship an item.
The codes reflect the <a href=
“http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm”
propertyISO 3166 location codes.
-
updateTime
The time of the most recent modification to any feature detail. If specific
property
feature details are passed in the request, gives the most recent modification time
of those feature details. -
recoupmentPolicyDetails
Details the recoupment policies for the site specified in the request.
property
Note:
This container is only returned if RecoupmentPolicyDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
-
shippingCategoryDetails
A shipping service category supported for the site.
property
Note:
This container is only returned if ShippingCategoryDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
Each shipping service supported for a site is automatically categorized by eBay into one of the
shipping categories available for that site depending on how the shipping service shipping time
aligns with the shipping times specified by eBay for each category.
Notice that you cannot specify a ShippingCategory
as an input to any API call - eBay does this categorizing automatically. ShippingCategory is read-only data
that is returned in the ShippingServiceDetails container. One possible use of this data is to segregate shipping
services by ShippingCategory in a pick list. (For an example of this, see the Services pulldown menu in the
Give buyers shipping details form in the eBay Sell Your Item flow.)
One way to populate the picklist would be to call GeteBayDetails
with DetailName set to ShippingServiceDetails.
Then sort these results by ShippingCategory and populate the picklist.
Properties
buyerRequirementDetails
Details various eBay-buyer requirements.
@property (nonatomic, retain) NSMutableArray *buyerRequirementDetails
Discussion
Details various eBay-buyer requirements.
entry type : class Trading_SiteBuyerRequirementDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
countryDetails
Lists the country code and associated name of the countries supported by
the eBay system, regardless of the site specified in the request.
@property (nonatomic, retain) NSMutableArray *countryDetails
Discussion
Lists the country code and associated name of the countries supported by
the eBay system, regardless of the site specified in the request.
entry type : class Trading_CountryDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
currencyDetails
Lists the currencies supported by the eBay system, regardless of the site
specified in the request.
Note:
This container is only returned if CurrencyDetails is included as a
DetailName filter in the request, or if no DetailName filters are
used in the request.
@property (nonatomic, retain) NSMutableArray *currencyDetails
Discussion
Lists the currencies supported by the eBay system, regardless of the site
specified in the request.
Note:
This container is only returned if CurrencyDetails is included as a
DetailName filter in the request, or if no DetailName filters are
used in the request.
entry type : class Trading_CurrencyDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
dispatchTimeMaxDetails
A dispatch time specifies the maximum number of business days a seller commits
to for shipping an item to domestic buyers after receiving a cleared payment.
Returns all dispatch times in the system, regardless of the site specified in
the request.
Note:
This container is only returned if DispatchTimeMaxDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *dispatchTimeMaxDetails
Discussion
A dispatch time specifies the maximum number of business days a seller commits
to for shipping an item to domestic buyers after receiving a cleared payment.
Returns all dispatch times in the system, regardless of the site specified in
the request.
Note:
This container is only returned if DispatchTimeMaxDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_DispatchTimeMaxDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
excludeShippingLocationDetails
Lists the locations supported by the ExcludeShipToLocation feature. These are
locations that a seller can list as areas where they will not ship an item.
The codes reflect the <a href=
“http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm”
ISO 3166 location codes.
@property (nonatomic, retain) NSMutableArray *excludeShippingLocationDetails
Discussion
Lists the locations supported by the ExcludeShipToLocation feature. These are
locations that a seller can list as areas where they will not ship an item.
The codes reflect the <a href=
“http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm”
ISO 3166 location codes.
entry type : class Trading_ExcludeShippingLocationDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
itemSpecificDetails
The site’s validation rules (e.g., string lengths) for custom Item Specifics.
Note:
This container is only returned if ItemSpecificDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *itemSpecificDetails
Discussion
The site’s validation rules (e.g., string lengths) for custom Item Specifics.
Note:
This container is only returned if ItemSpecificDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_ItemSpecificDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
listingFeatureDetails
Details the listing features available for the site specified in the request.
Note:
This container is only returned if ListingFeatureDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *listingFeatureDetails
Discussion
Details the listing features available for the site specified in the request.
Note:
This container is only returned if ListingFeatureDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_ListingFeatureDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
listingStartPriceDetails
Lists the minimum starting prices for the supported types of eBay listings.
Note:
This container is only returned if ListingStartPriceDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *listingStartPriceDetails
Discussion
Lists the minimum starting prices for the supported types of eBay listings.
Note:
This container is only returned if ListingStartPriceDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_ListingStartPriceDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
paymentOptionDetails
Deprecated
Use GetCategoryFeatures instead, and pass in
PaymentMethods as a FeatureID value in the request.
@property (nonatomic, retain) NSMutableArray *paymentOptionDetails
Discussion
Deprecated
Use GetCategoryFeatures instead, and pass in
PaymentMethods as a FeatureID value in the request.
entry type : class Trading_PaymentOptionDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
recoupmentPolicyDetails
Details the recoupment policies for the site specified in the request.
Note:
This container is only returned if RecoupmentPolicyDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *recoupmentPolicyDetails
Discussion
Details the recoupment policies for the site specified in the request.
Note:
This container is only returned if RecoupmentPolicyDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_RecoupmentPolicyDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
regionDetails
No longer returned; replaced by ShippingLocationDetails.
@property (nonatomic, retain) NSMutableArray *regionDetails
Discussion
No longer returned; replaced by ShippingLocationDetails.
entry type : class Trading_RegionDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
regionOfOriginDetails
No longer returned.
@property (nonatomic, retain) NSMutableArray *regionOfOriginDetails
Declared In
Trading_GeteBayDetailsResponseType.h
returnPolicyDetails
Lists the return policies supported by the eBay site specified in the request.
Note:
This container is only returned if ReturnPolicyDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) Trading_ReturnPolicyDetailsType *returnPolicyDetails
Discussion
Lists the return policies supported by the eBay site specified in the request.
Note:
This container is only returned if ReturnPolicyDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
type : class Trading_ReturnPolicyDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
shippingCarrierDetails
Lists the shipping carriers supported by the specified site.
Note:
This container is only returned if ShippingCarrierDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *shippingCarrierDetails
Discussion
Lists the shipping carriers supported by the specified site.
Note:
This container is only returned if ShippingCarrierDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_ShippingCarrierDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
shippingCategoryDetails
A shipping service category supported for the site.
Note:
This container is only returned if ShippingCategoryDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
Each shipping service supported for a site is automatically categorized by eBay into one of the
shipping categories available for that site depending on how the shipping service shipping time
aligns with the shipping times specified by eBay for each category.
Notice that you cannot specify a ShippingCategory
as an input to any API call - eBay does this categorizing automatically. ShippingCategory is read-only data
that is returned in the ShippingServiceDetails container. One possible use of this data is to segregate shipping
services by ShippingCategory in a pick list. (For an example of this, see the Services pulldown menu in the
Give buyers shipping details form in the eBay Sell Your Item flow.)
One way to populate the picklist would be to call GeteBayDetails
with DetailName set to ShippingServiceDetails.
Then sort these results by ShippingCategory and populate the picklist.
@property (nonatomic, retain) NSMutableArray *shippingCategoryDetails
Discussion
A shipping service category supported for the site.
Note:
This container is only returned if ShippingCategoryDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
Each shipping service supported for a site is automatically categorized by eBay into one of the
shipping categories available for that site depending on how the shipping service shipping time
aligns with the shipping times specified by eBay for each category.
Notice that you cannot specify a ShippingCategory
as an input to any API call - eBay does this categorizing automatically. ShippingCategory is read-only data
that is returned in the ShippingServiceDetails container. One possible use of this data is to segregate shipping
services by ShippingCategory in a pick list. (For an example of this, see the Services pulldown menu in the
Give buyers shipping details form in the eBay Sell Your Item flow.)
One way to populate the picklist would be to call GeteBayDetails
with DetailName set to ShippingServiceDetails.
Then sort these results by ShippingCategory and populate the picklist.
entry type : class Trading_ShippingCategoryDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
shippingLocationDetails
Lists the regions and locations supported by eBay’s shipping services. Returns
all shipping locations supported by eBay, regardless of the site specified in
the request.
Note:
This container is only returned if ShippingLocationDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *shippingLocationDetails
Discussion
Lists the regions and locations supported by eBay’s shipping services. Returns
all shipping locations supported by eBay, regardless of the site specified in
the request.
Note:
This container is only returned if ShippingLocationDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_ShippingLocationDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
shippingPackageDetails
Lists the various shipping packages supported by the specified site.
Note:
This container is only returned if ShippingPackageDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *shippingPackageDetails
Discussion
Lists the various shipping packages supported by the specified site.
Note:
This container is only returned if ShippingPackageDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_ShippingPackageDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
shippingServiceDetails
Lists the shipping services supported by the specified eBay site. Returns only
the shipping services that are applicable to the site specified in the
request.
Note:
This container is only returned if ShippingServiceDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *shippingServiceDetails
Discussion
Lists the shipping services supported by the specified eBay site. Returns only
the shipping services that are applicable to the site specified in the
request.
Note:
This container is only returned if ShippingServiceDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_ShippingServiceDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
siteDetails
Lists all available eBay sites and their associated SiteID numbers.
Note:
This container is only returned if SiteDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *siteDetails
Discussion
Lists all available eBay sites and their associated SiteID numbers.
Note:
This container is only returned if SiteDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_SiteDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
taxJurisdiction
Details the different tax jurisdictions or tax regions applicable to the
site specified in the request.
Note:
This container is only returned if TaxJurisdiction is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *taxJurisdiction
Discussion
Details the different tax jurisdictions or tax regions applicable to the
site specified in the request.
Note:
This container is only returned if TaxJurisdiction is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_TaxJurisdictionType
Declared In
Trading_GeteBayDetailsResponseType.h
timeZoneDetails
Lists the details of the time zones supported by the eBay system.
Note:
This container is only returned if TimeZoneDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *timeZoneDetails
Discussion
Lists the details of the time zones supported by the eBay system.
Note:
This container is only returned if TimeZoneDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_TimeZoneDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
unitOfMeasurementDetails
Lists the suggested unit-of-measurement strings to use with Item Specifics
descriptions.
Note:
This container is only returned if UnitOfMeasurementDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) NSMutableArray *unitOfMeasurementDetails
Discussion
Lists the suggested unit-of-measurement strings to use with Item Specifics
descriptions.
Note:
This container is only returned if UnitOfMeasurementDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
entry type : class Trading_UnitOfMeasurementDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
updateTime
The time of the most recent modification to any feature detail. If specific
feature details are passed in the request, gives the most recent modification time
of those feature details.
@property (nonatomic, retain) NSDate *updateTime
Discussion
The time of the most recent modification to any feature detail. If specific
feature details are passed in the request, gives the most recent modification time
of those feature details.
type : NSDate, wrapper for primitive date
Declared In
Trading_GeteBayDetailsResponseType.h
urlDetails
Lists eBay URLs that are applicable to the site specified in the request.\
Note:
This container is only returned if URLDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request
@property (nonatomic, retain) NSMutableArray *urlDetails
Discussion
Lists eBay URLs that are applicable to the site specified in the request.\
Note:
This container is only returned if URLDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request
entry type : class Trading_URLDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h
variationDetails
Site-level validation rules for multi-variation listings (for example, the
maximum number of variations per listing). Use GetCategoryFeatures to
determine which categories on a site support variations. Use
GetCategorySpecifics for rules related to recommended or required variation
specifics.
Note:
This container is only returned if VariationDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
@property (nonatomic, retain) Trading_VariationDetailsType *variationDetails
Discussion
Site-level validation rules for multi-variation listings (for example, the
maximum number of variations per listing). Use GetCategoryFeatures to
determine which categories on a site support variations. Use
GetCategorySpecifics for rules related to recommended or required variation
specifics.
Note:
This container is only returned if VariationDetails is included as a
DetailName filter in the request, or if no DetailName
filters are used in the request.
type : class Trading_VariationDetailsType
Declared In
Trading_GeteBayDetailsResponseType.h


{% extends 'database/base.html' %} {% block title %}Thunder Games - Subgenres{% endblock %} {% block subgenre_active %}active{% endblock %} {% block body %}
Add a new subgenre
There are no subgenres.


Structure for storing parameters for DMA view3 that can be performed by the DMA Master transfer. More...
#include <xdmad.h>
Public Attributes | |
| uint32_t | mbr_nda |
| Next Descriptor Address number. More... | |
| uint32_t | mbr_ubc |
| Microblock Control Member. More... | |
| uint32_t | mbr_sa |
| Source Address Member. More... | |
| uint32_t | mbr_da |
| Destination Address Member. More... | |
| uint32_t | mbr_cfg |
| Configuration Register. More... | |
| uint32_t | mbr_bc |
| Block Control Member. More... | |
| uint32_t | mbr_ds |
| Data Stride Member. More... | |
| uint32_t | mbr_sus |
| Source Microblock Stride Member. More... | |
| uint32_t | mbr_dus |
| Destination Microblock Stride Member. More... | |
Structure for storing parameters for DMA view3 that can be performed by the DMA Master transfer.
| uint32_t _LinkedListDescriporView3::mbr_bc |
Block Control Member.
| uint32_t _LinkedListDescriporView3::mbr_cfg |
Configuration Register.
| uint32_t _LinkedListDescriporView3::mbr_da |
Destination Address Member.
| uint32_t _LinkedListDescriporView3::mbr_ds |
Data Stride Member.
| uint32_t _LinkedListDescriporView3::mbr_dus |
Destination Microblock Stride Member.
| uint32_t _LinkedListDescriporView3::mbr_nda |
Next Descriptor Address number.
| uint32_t _LinkedListDescriporView3::mbr_sa |
Source Address Member.
| uint32_t _LinkedListDescriporView3::mbr_sus |
Source Microblock Stride Member.
| uint32_t _LinkedListDescriporView3::mbr_ubc |
Microblock Control Member.


The overlay is intended to provide application wide border / chrome with controls such as back, mute, pause etc.
The overlay also provides flashing which is a useful cheap effect across many game scenarios.
type
The overlay button.?duration
The period of time over which the flash should fade to 0.?asTime
If true treats the time as milliseconds, otherwise as frame updates.?startingAlpha
The alpha at which the flash starts. Range: 0...1.?color
The color of the flash. Defaults to white.type
The overlay button.x
The horizontal position.y
The vertical position.width
The width of the button hitArea, if null will not redefine.height
The height of the button hitArea, if null will not redefine.type
The overlay button.?isVisible
If true shows the button, if false hides it.


According to its authors, “the ISO/IEC TS 22424 series supports long-term reservation of EPUB publications via a dual strategy”. The standard is made up of 2 parts, which are sold as separate documents on the ISO website:
In this blog post I will take a closer look at both parts of the standard. What do they purport, what is their scope, and to what degree do they live up to their stated promises? Readers who are only interested in the most important findings may want to jump to the “Summary and discussion” section at the end of this post.
We recently started using Microsoft OneDrive at work. The other day a colleague used OneDrive to share a folder with a large number of ISO images with me. Since I wanted to work with these files on my Linux machine at home, and no official OneDrive client for Linux exists a this point, I used OneDrive’s web client to download the contents of the folder. Doing so resulted in a 6 GB ZIP archive. When I tried to extract this ZIP file with my operating system’s (Linux Mint 19.3 MATE) archive manager, this resulted in an error dialog, saying that “An error occurred while loading the archive”:
The output from the underlying extraction tool (7-zip) reported a “Headers Error”, with an “Unconfirmed start of archive”. It also reported a warning that “There are data after the end of archive”. No actual data were extracted whatsoever. This all looked a bit worrying, so I decided to have a more in-depth look at this problem.
Following earlier work on the preservation of optical media and data tapes, I recently got a request to make an inventory of offline digital data carriers in the KB’s deposit collection. The goal was to obtain approximate figures on the various carrier types in the collection. This was partially prompted by a project on at-risk digital heritage on physical carriers by the Dutch Digital Heritage Network (NDE) that the KB is participating in. This blog post presents the results.
A few weeks ago one of my web archiving colleagues approached me with an interesting question. From a list of Dutch web domains, he wanted to identify the (Dutch) province in which each domain is hosted. He was particularly interested in domains hosted in the province of Friesland. After some experimentation I was able to answer this question using a two-step procedure:
Geo-locate the web domains using a custom Python script.
Combine the results of the geolocation exercise with openly available geographical data using QGIS, an open-source geographical information system (GIS).
Even though the outcome of the analysis is not particularly interesting, I imagine both the geolocation methodology and the GIS analysis steps might be useful to others. So, this blog post is primarily intended as a tutorial that gives a walkthrough of the steps I followed.
Earlier this year I published this blog post on the recovery of data from ’90s data tapes. I will give a presentation on this during the upcoming iPres 2019 conference, and wrote a paper that discusses this work in more detail than my earlier blog post. The original paper (in PDF format) can be found here. The paper references a wealth of useful resources, but some of these are not easily accessible because the LaTeX template used does not handle hyperlinks well (this will be fixed in the final, post-conference version of the paper). Because of this I’ve created a web-friendly version of the paper below.


James Charles Announces New YouTube Makeup Competition Series
by Amy LeeJames Charles is launching a competition series!
The 20-year-old YouTube star announced on Friday that he will be a host, mentor and executive producer on a new competition series for YouTube Originals, where aspiring makeup creatives take on innovative challenges to become the next big thing in the beauty influencer world.
In the video posted on his YouTube channel, Charles excitedly reveals the project, a concept he came up with three years ago: "I came up with the name, the description, literally every single challenge I wanted the contestants to go through, literally guest judges as well," Charles says in the video.
The show, which is the "first-ever beauty and social media influencer competition show of its kind," is set to air on Charles' channel in spring 2020. Fans can now enter to become one of the six contestants who will compete to win the grand prize of $50,000.


Endless Plains [am72], plain, in Imperia, peasants: 138
Last updated Turn #118
Endless Plains [am72], plain, in Imperia, peasants: 138
------------------------------------------------------------------------
22: Sir Uther [s3o], Imperial Empire, baron, with ten soldiers, 50 lt.
22: xbowmen, eight hvy. wagons, 11 riding horses, 50 oxen, arrived from
22: the west, accompanied by:
22: Sir Andrew [v9a], Imperial Empire, with seven soldiers, 41 pikemen,
22: four hvy. wagons, ten nazgul
23: Sir Uther [s3o], Imperial Empire, baron, with ten soldiers, 50 lt.
23: xbowmen, eight hvy. wagons, 11 riding horses, 50 oxen, went east,
23: accompanied by:
23: Sir Andrew [v9a], Imperial Empire, with seven soldiers, 41 pikemen,
23: four hvy. wagons, ten nazgul
24: Stack of nazgul [cp2x], nazgul, number: 3, arrived from the north.
25: Grolax [f1g], refugee, with one wild horse, one riding horse, arrived
25: from the east.
26: Stack of nazgul [cp2x], nazgul, number: 3, went south.
27: Polgar [w5c], refugee, with one soldier, one skirmisher, arrived from
27: the east.
28: Grolax [f1g], refugee, with one wild horse, one riding horse, went
28: west.
30: Polgar [w5c], refugee, with one soldier, one skirmisher, went west.
30: The population grows by one peasant.
Routes leaving Endless Plains:
North, plain, to Endless Plains [al72], 7 days
East, plain, to Endless Plains [am73], 7 days
South, mountain, to Imperial Mountains [an72], 10 days
West, plain, to Endless Plains [am71], 7 days
It is raining.
Seen here:
Stack of nazgul [cq4w], nazgul, number: 3
Stack of nazgul [fs1m], nazgul, number: 3
Grolax [f1g], refugee, with one wild horse, one riding horse
Polgar [w5c], refugee, with one soldier, one skirmisher


Using the Animation Builder
| To do this, we use the Animation Builder, which can be opened from either the Create Tab (as shown in Figure 1.1.1) or the Project menu (as shown in Figure 1.1.2). |
Figure 1.1.1 Figure 1.1.2 |
| The first step in the Animation Builder is to select an imageMap (as shown in Figure 1.1.3). Choose an imageMap and click the Select button. |
Figure 1.1.3 |
| The next step is to actually build your animation. (as shown in Figure 1.1.4). By just dragging and dropping, you can use whichever frames you want and put them in any order you want. Don't forget to check the settings in the bottom right. The Total Time parameter is very important for controlling the look of your animation. This screen can also be accessed from the object library by double clicking on the animation, so you don't have to guess about the time. |
Figure 1.1.4 |


/ Sentinel /
Home
About
Contact
Dropdown
Poverty Index
Human Freedom Index
Global Peace Index
Militarization Index
Global Burden of Disease
Human Development Index
Environmental Sustainability
Gender Inequality
Poverty Index
Want to Learn How to Help? Start Your Search Here!