HTML theming support¶
New in version 0.6.
Sphinx supports changing the appearance of its HTML output via themes. A theme is a collection of HTML templates, stylesheet(s) and other static files. Additionally, it has a configuration file which specifies from which theme to inherit, which highlighting style to use, and what options exist for customizing the theme’s look and feel.
Themes are meant to be project-unaware, so they can be used for different projects without change.
Using a theme¶
Using an existing theme is easy. If the theme is builtin to Sphinx, you only
need to set the :confval:`html_theme` config value. With the
:confval:`html_theme_options` config value you can set theme-specific options
that change the look and feel. For example, you could have the following in
your conf.py
:
html_theme = "classic"
html_theme_options = {
"rightsidebar": "true",
"relbarbgcolor": "black"
}
That would give you the classic theme, but with a sidebar on the right side and a black background for the relation bar (the bar with the navigation links at the page’s top and bottom).
If the theme does not come with Sphinx, it can be in two static forms: either a
directory (containing theme.conf
and other needed files), or a zip file
with the same contents. Either of them must be put where Sphinx can find it;
for this there is the config value :confval:`html_theme_path`. It gives a list
of directories, relative to the directory containing conf.py
, that can
contain theme directories or zip files. For example, if you have a theme in the
file blue.zip
, you can put it right in the directory containing
conf.py
and use this configuration:
html_theme = "blue"
html_theme_path = ["."]
The third form is a python package. If a theme you want to use is distributed as a python package, you can use it after installing
# installing theme package
$ pip install sphinxjp.themes.dotted
# use it in your conf.py
html_theme = "dotted"
Builtin themes¶
| Theme overview | |
|
alabaster |
classic |
|
sphinxdoc |
scrolls |
|
agogo |
traditional |
|
nature |
haiku |
|
pyramid |
bizstyle |
Sphinx comes with a selection of themes to choose from.
These themes are:
basic – This is a basically unstyled layout used as the base for the other themes, and usable as the base for custom themes as well. The HTML contains all important elements like sidebar and relation bar. There are these options (which are inherited by the other themes):
- nosidebar (true or false): Don’t include the sidebar. Defaults to
False
. - sidebarwidth (an integer): Width of the sidebar in pixels. (Do not
include
px
in the value.) Defaults to 230 pixels.
- nosidebar (true or false): Don’t include the sidebar. Defaults to
alabaster – Alabaster theme is a modified “Kr” Sphinx theme from @kennethreitz (especially as used in his Requests project), which was itself originally based on @mitsuhiko’s theme used for Flask & related projects. Check out at its installation page how to set up properly :confval:`html_sidebars` for its use.
classic – This is the classic theme, which looks like the Python 2 documentation. It can be customized via these options:
- rightsidebar (true or false): Put the sidebar on the right side.
Defaults to
False
. - stickysidebar (true or false): Make the sidebar “fixed” so that it
doesn’t scroll out of view for long body content. This may not work well
with all browsers. Defaults to
False
. - collapsiblesidebar (true or false): Add an experimental JavaScript
snippet that makes the sidebar collapsible via a button on its side.
Doesn’t work with “stickysidebar”. Defaults to
False
. - externalrefs (true or false): Display external links differently from
internal links. Defaults to
False
.
There are also various color and font options that can change the color scheme without having to write a custom stylesheet:
- footerbgcolor (CSS color): Background color for the footer line.
- footertextcolor (CSS color): Text color for the footer line.
- sidebarbgcolor (CSS color): Background color for the sidebar.
- sidebarbtncolor (CSS color): Background color for the sidebar collapse
button (used when collapsiblesidebar is
True
). - sidebartextcolor (CSS color): Text color for the sidebar.
- sidebarlinkcolor (CSS color): Link color for the sidebar.
- relbarbgcolor (CSS color): Background color for the relation bar.
- relbartextcolor (CSS color): Text color for the relation bar.
- relbarlinkcolor (CSS color): Link color for the relation bar.
- bgcolor (CSS color): Body background color.
- textcolor (CSS color): Body text color.
- linkcolor (CSS color): Body link color.
- visitedlinkcolor (CSS color): Body color for visited links.
- headbgcolor (CSS color): Background color for headings.
- headtextcolor (CSS color): Text color for headings.
- headlinkcolor (CSS color): Link color for headings.
- codebgcolor (CSS color): Background color for code blocks.
- codetextcolor (CSS color): Default text color for code blocks, if not set differently by the highlighting style.
- bodyfont (CSS font-family): Font for normal text.
- headfont (CSS font-family): Font for headings.
- rightsidebar (true or false): Put the sidebar on the right side.
Defaults to
sphinxdoc – The theme used for this documentation. It features a sidebar on the right side. There are currently no options beyond nosidebar and sidebarwidth.
scrolls – A more lightweight theme, based on the Jinja documentation. The following color options are available:
- headerbordercolor
- subheadlinecolor
- linkcolor
- visitedlinkcolor
- admonitioncolor
agogo – A theme created by Andi Albrecht. The following options are supported:
- bodyfont (CSS font family): Font for normal text.
- headerfont (CSS font family): Font for headings.
- pagewidth (CSS length): Width of the page content, default 70em.
- documentwidth (CSS length): Width of the document (without sidebar), default 50em.
- sidebarwidth (CSS length): Width of the sidebar, default 20em.
- bgcolor (CSS color): Background color.
- headerbg (CSS value for “background”): background for the header area, default a grayish gradient.
- footerbg (CSS value for “background”): background for the footer area, default a light gray gradient.
- linkcolor (CSS color): Body link color.
- headercolor1, headercolor2 (CSS color): colors for <h1> and <h2> headings.
- headerlinkcolor (CSS color): Color for the backreference link in headings.
- textalign (CSS text-align value): Text alignment for the body, default
is
justify
.
nature – A greenish theme. There are currently no options beyond nosidebar and sidebarwidth.
pyramid – A theme from the Pyramid web framework project, designed by Blaise Laflamme. There are currently no options beyond nosidebar and sidebarwidth.
haiku – A theme without sidebar inspired by the Haiku OS user guide. The following options are supported:
- full_logo (true or false, default
False
): If this is true, the header will only show the :confval:`html_logo`. Use this for large logos. If this is false, the logo (if present) will be shown floating right, and the documentation title will be put in the header. - textcolor, headingcolor, linkcolor, visitedlinkcolor, hoverlinkcolor (CSS colors): Colors for various body elements.
- full_logo (true or false, default
traditional – A theme resembling the old Python documentation. There are currently no options beyond nosidebar and sidebarwidth.
epub – A theme for the epub builder. This theme tries to save visual space which is a sparse resource on ebook readers. The following options are supported:
- relbar1 (true or false, default
True
): If this is true, the relbar1 block is inserted in the epub output, otherwise it is omitted. - footer (true or false, default
True
): If this is true, the footer block is inserted in the epub output, otherwise it is omitted.
- relbar1 (true or false, default
- bizstyle – A simple bluish theme. The following options are supported
beyond nosidebar and sidebarwidth:
- rightsidebar (true or false): Put the sidebar on the right side.
Defaults to
False
.
- rightsidebar (true or false): Put the sidebar on the right side.
Defaults to
New in version 1.3: ‘alabaster’, ‘sphinx_rtd_theme’ and ‘bizstyle’ theme.
Changed in version 1.3: The ‘default’ theme has been renamed to ‘classic’. ‘default’ is still available, however it will emit a notice that it is an alias for the new ‘alabaster’ theme.
Creating themes¶
As said, themes are either a directory or a zipfile (whose name is the theme name), containing the following:
- A
theme.conf
file, see below. - HTML templates, if needed.
- A
static/
directory containing any static files that will be copied to the output static directory on build. These can be images, styles, script files.
The theme.conf
file is in INI format [1] (readable by the standard
Python ConfigParser
module) and has the following structure:
[theme]
inherit = base theme
stylesheet = main CSS name
pygments_style = stylename
[options]
variable = default value
- The inherit setting gives the name of a “base theme”, or
none
. The base theme will be used to locate missing templates (most themes will not have to supply most templates if they usebasic
as the base theme), its options will be inherited, and all of its static files will be used as well. - The stylesheet setting gives the name of a CSS file which will be
referenced in the HTML header. If you need more than one CSS file, either
include one from the other via CSS’
@import
, or use a custom HTML template that adds<link rel="stylesheet">
tags as necessary. Setting the :confval:`html_style` config value will override this setting. - The pygments_style setting gives the name of a Pygments style to use for highlighting. This can be overridden by the user in the :confval:`pygments_style` config value.
- The options section contains pairs of variable names and default values.
These options can be overridden by the user in :confval:`html_theme_options`
and are accessible from all templates as
theme_<name>
.
Distribute your theme as a python package¶
As a way to distribute your theme, you can use python package. Python package brings to users easy setting up ways.
To distribute your theme as a python package, please define an entry point
called sphinx.html_themes
in your setup.py file, and write a setup()
function to register your themes using add_html_theme()
API in it:
# 'setup.py'
setup(
...
entry_points = {
'sphinx.html_themes': [
'name_of_theme = your_package',
]
},
...
)
# 'your_package.py'
from os import path
def setup(app):
app.add_html_theme('name_of_theme', path.abspath(path.dirname(__file__)))
If your theme package contains two or more themes, please call add_html_theme()
twice or more.
New in version 1.2: ‘sphinx_themes’ entry_points feature.
Deprecated since version 1.6: sphinx_themes
entry_points has been deprecated.
New in version 1.6: sphinx.html_themes
entry_points feature.
Templating¶
The guide to templating is helpful if you want to write your own templates. What is important to keep in mind is the order in which Sphinx searches for templates:
- First, in the user’s
templates_path
directories. - Then, in the selected theme.
- Then, in its base theme, its base’s base theme, etc.
When extending a template in the base theme with the same name, use the theme
name as an explicit directory: {% extends "basic/layout.html" %}
. From a
user templates_path
template, you can still use the “exclamation mark”
syntax as described in the templating document.
Static templates¶
Since theme options are meant for the user to configure a theme more easily, without having to write a custom stylesheet, it is necessary to be able to template static files as well as HTML files. Therefore, Sphinx supports so-called “static templates”, like this:
If the name of a file in the static/
directory of a theme (or in the user’s
static path, for that matter) ends with _t
, it will be processed by the
template engine. The _t
will be left from the final file name. For
example, the classic theme has a file static/classic.css_t
which uses
templating to put the color options into the stylesheet. When a documentation
is built with the classic theme, the output directory will contain a
_static/classic.css
file where all template tags have been processed.
| [1] | It is not an executable Python file, as opposed to conf.py ,
because that would pose an unnecessary security risk if themes are
shared. |
Third Party Themes¶
| Theme overview | |
|
sphinx_rtd_theme |
sphinx_rtd_theme – Read the Docs Sphinx Theme. This is a mobile-friendly sphinx theme that was made for readthedocs.org. View a working demo over on readthedocs.org. You can get install and options information at Read the Docs Sphinx Theme page.
Changed in version 1.4: sphinx_rtd_theme has become optional.


Home
Toggle navigation
Oops ! Something went wrong.
Loading...
© All rights reserved | Design by
Ramit Surana


$
Revenue by Solution
Revenue per week
32,556
Revenue Stream
Revenue Analysis
Installations
Installations
136
Installations
View Installations


- You can take over an e-reader and order books, have them delivered to your own e-reader, and charge them to the person who owns the device.
- If you know a password and add it to the URL of a website, it gives you administrative access to the website. You can read personal identifying information, and assign employees to different tasks.
- You find a technology that everyone uses and discover that many of the programs written using that technology make the same programming flaw; that is, if there is an unexpected error then the code that created that error gets the ability to take actions that should not be allowed.
- You can read all the information sent from an IoT device that is supposed to alert care-givers of medication use.
- A researcher notices that their boarding pass is generated locally by javascript. He creates a simple boarding pass generator to bring attention to the problem.
- You find that if you enter the right string into an order form, instead of logging in, you can access all the user names and passwords.


Dashboard
Employees
Attendance
Schedules
Leaves
Reports
Users
Settings
Menu
Quick Access
Add Employee
Clock In/Out
Company
Department
Job Title
Leave Type
Demo Manager
Update User
Change Password
Switch to MyAccount
Logout
Edit User
Employee
Email
Account Type :
EMPLOYEE
ADMIN
Role
Select Role
MANAGER
SUPERVISOR
EMPLOYEE
MANAGER
MANAGER
SUPERVISOR
EMPLOYEE
Status
Select Status
Enabled
Disabled
Enabled
Enabled
Disabled
Password
Confirm Password


Grand Master Meldina:
I am a member of the secret society you have been investigating...
We are called Inquisitors among those who know of our existence.
It is our responsibility to protect the secrets of the Kamael, as well as to unearth conspiracies that might threaten our people. Our work is highly secretive.
We have watched you face dangers and solve problems to obtain this manuscript, and we think you have the skills to take the class transfer test.
If you pass it, you will obtain a power that can take you beyond your current combat skill, just like the rest of our order.
What do you say? Are you interested?
Yes, I want to take the test.


To run this example you have to compile it from root director:
$ make
You should also edit index.html for this exmaple and setup valid video url there.


#include <uwpolling_NODE.h>
|
| enum | UWPOLLING_NODE_STATUS {
UWPOLLING_NODE_STATUS_IDLE = 1,
UWPOLLING_NODE_STATUS_RX_TRIGGER,
UWPOLLING_NODE_STATUS_TX_PROBE,
UWPOLLING_NODE_STATUS_RX_POLL,
UWPOLLING_NODE_STATUS_TX_DATA,
UWPOLLING_NODE_STATUS_WAIT_POLL
} |
| |
| enum | UWPOLLING_PKT_TYPE { UWPOLLING_DATA_PKT = 1,
UWPOLLING_POLL_PKT,
UWPOLLING_TRIGGER_PKT,
UWPOLLING_PROBE_PKT
} |
| |
| enum | UWPOLLING_NODE_REASON {
UWPOLLING_NODE_REASON_TX_DATA,
UWPOLLING_NODE_REASON_RX_TRIGGER,
UWPOLLING_NODE_REASON_PKT_ERROR,
UWPOLLING_NODE_REASON_TX_PROBE,
UWPOLLING_NODE_REASON_RX_POLL,
UWPOLLING_NODE_REASON_BACKOFF_TIMER_EXPIRED,
UWPOLLING_NODE_REASON_RX_POLL_TIMER_EXPIRED,
UWPOLLING_NODE_REASON_NOT_SET,
UWPOLLING_NODE_REASON_EMPTY_DATA_QUEUE,
UWPOLLING_NODE_REASON_WRONG_TYPE,
UWPOLLING_NODE_REASON_WRONG_RECEIVER,
UWPOLLING_NODE_REASON_WRONG_STATE,
UWPOLLING_NODE_REASON_NOT_IN_LIST,
UWPOLLING_NODE_REASON_LIST_NOT_POLLED
} |
| |
| enum | UWPOLLING_TIMER_STATUS { UWPOLLING_IDLE = 1,
UWPOLLING_RUNNING,
UWPOLLING_FROZEN,
UWPOLLING_EXPIRED
} |
| |
Class used to represents the UWPOLLING MAC layer of a node.
Definition at line 74 of file uwpolling_NODE.h.
◆ UWPOLLING_NODE_REASON
| Enumerator |
|---|
| UWPOLLING_NODE_REASON_TX_DATA | |
| UWPOLLING_NODE_REASON_RX_TRIGGER | |
| UWPOLLING_NODE_REASON_PKT_ERROR | |
| UWPOLLING_NODE_REASON_TX_PROBE | |
| UWPOLLING_NODE_REASON_RX_POLL | |
| UWPOLLING_NODE_REASON_BACKOFF_TIMER_EXPIRED | |
| UWPOLLING_NODE_REASON_RX_POLL_TIMER_EXPIRED | |
| UWPOLLING_NODE_REASON_NOT_SET | |
| UWPOLLING_NODE_REASON_EMPTY_DATA_QUEUE | |
| UWPOLLING_NODE_REASON_WRONG_TYPE | |
| UWPOLLING_NODE_REASON_WRONG_RECEIVER | |
| UWPOLLING_NODE_REASON_WRONG_STATE | |
| UWPOLLING_NODE_REASON_NOT_IN_LIST | |
| UWPOLLING_NODE_REASON_LIST_NOT_POLLED | |
Definition at line 125 of file uwpolling_NODE.h.
◆ UWPOLLING_NODE_STATUS
< Variable that rapresents the status of the protocol machine state
| Enumerator |
|---|
| UWPOLLING_NODE_STATUS_IDLE | |
| UWPOLLING_NODE_STATUS_RX_TRIGGER | |
| UWPOLLING_NODE_STATUS_TX_PROBE | |
| UWPOLLING_NODE_STATUS_RX_POLL | |
| UWPOLLING_NODE_STATUS_TX_DATA | |
| UWPOLLING_NODE_STATUS_WAIT_POLL | |
Definition at line 107 of file uwpolling_NODE.h.
◆ UWPOLLING_PKT_TYPE
| Enumerator |
|---|
| UWPOLLING_DATA_PKT | |
| UWPOLLING_POLL_PKT | |
| UWPOLLING_TRIGGER_PKT | |
| UWPOLLING_PROBE_PKT | |
Definition at line 117 of file uwpolling_NODE.h.
◆ UWPOLLING_TIMER_STATUS
| Enumerator |
|---|
| UWPOLLING_IDLE | |
| UWPOLLING_RUNNING | |
| UWPOLLING_FROZEN | |
| UWPOLLING_EXPIRED | |
Definition at line 143 of file uwpolling_NODE.h.
◆ Uwpolling_NODE()
| Uwpolling_NODE::Uwpolling_NODE |
( |
| ) |
|
◆ ~Uwpolling_NODE()
| Uwpolling_NODE::~Uwpolling_NODE |
( |
| ) |
|
|
virtual |
◆ BackOffTimerExpired()
| void Uwpolling_NODE::BackOffTimerExpired |
( |
| ) |
|
|
protectedvirtual |
Method called by the Expire event of the timer.
Here we call the stateTxProbe method
Definition at line 87 of file uwpolling_NODE.cpp.
◆ command()
| int Uwpolling_NODE::command |
( |
int |
argc, |
|
|
const char *const * |
argv |
|
) |
| |
|
virtual |
TCL command interpreter.
It implements the following OTcl methods:
- Parameters
-
| argc | Number of arguments in argv. |
| argv | Array of strings which are the command parameters (Note that argv[0] is the name of the object). |
- Returns
- TCL_OK or TCL_ERROR whether the command has been dispatched successfully or not.
Definition at line 195 of file uwpolling_NODE.cpp.
◆ crLayCommand()
| int Uwpolling_NODE::crLayCommand |
( |
ClMessage * |
m | ) |
|
|
virtual |
Cross-Layer messages interpreter.
- Parameters
-
| ClMessage* | an instance of ClMessage that represent the message received |
- Returns
- 0 if successful.
Definition at line 233 of file uwpolling_NODE.cpp.
◆ getBackOffTime()
| double Uwpolling_NODE::getBackOffTime |
( |
| ) |
|
|
protectedvirtual |
The backoff timer is calculated choosing randomly using a Uniform random variable and multiplying it by a backoff_tuner chosen by the user via tcl.
Definition at line 605 of file uwpolling_NODE.cpp.
◆ getEpoch()
| unsigned long int Uwpolling_NODE::getEpoch |
( |
| ) |
|
|
inlineprotected |
Calculate the epoch of the event.
Used in sea-trial mode
- Returns
- the epoch of the system
Definition at line 666 of file uwpolling_NODE.h.
◆ getPollDropped()
| int Uwpolling_NODE::getPollDropped |
( |
| ) |
|
|
inlineprotected |
Return the number of POLL dropped by the node because of erroneous CRC.
- Returns
- itn n_poll_dropped number of POLL dropped
Definition at line 585 of file uwpolling_NODE.h.
◆ getProbeSent()
| int Uwpolling_NODE::getProbeSent |
( |
| ) |
|
|
inlineprotected |
Returns the number of PROBE packets sent during the simulation.
- Returns
- int n_probe_sent the number of PROBE packets sent
Definition at line 545 of file uwpolling_NODE.h.
◆ getTimesPolled()
| int Uwpolling_NODE::getTimesPolled |
( |
| ) |
|
|
inlineprotected |
Return the number of times the node are polled by the AUV.
- Returns
- int n_times_polled number of times polled
Definition at line 555 of file uwpolling_NODE.h.
◆ getTriggerDropped()
| int Uwpolling_NODE::getTriggerDropped |
( |
| ) |
|
|
inlineprotected |
Return the number of TRIGGER dropped by the node because of erroneous CRC.
- Returns
- int n_trigger_dropped number of TRIGGER dropped by the AUV
Definition at line 575 of file uwpolling_NODE.h.
◆ getTriggerReceived()
| int Uwpolling_NODE::getTriggerReceived |
( |
| ) |
|
|
inlineprotected |
Return the number of TRIGGER packets received by the NODE.
- Returns
- int n_trigger_received number of TRIGGER packets received
Definition at line 565 of file uwpolling_NODE.h.
◆ incrPollDropped()
| void Uwpolling_NODE::incrPollDropped |
( |
| ) |
|
|
inlineprotected |
Increments the number of POLL packets dropped because of erroneous CRC.
Definition at line 535 of file uwpolling_NODE.h.
◆ incrProbeSent()
| virtual void Uwpolling_NODE::incrProbeSent |
( |
| ) |
|
|
inlineprotectedvirtual |
◆ incrTimesPolled()
| virtual void Uwpolling_NODE::incrTimesPolled |
( |
| ) |
|
|
inlineprotectedvirtual |
Increments the number of times that the node has been polled by the AUV.
Definition at line 508 of file uwpolling_NODE.h.
◆ incrTriggerDropped()
| void Uwpolling_NODE::incrTriggerDropped |
( |
| ) |
|
|
inlineprotected |
Increments the number of TRIGGER packets dropped because of erroneous CRC.
Definition at line 526 of file uwpolling_NODE.h.
◆ incrTriggerReceived()
| void Uwpolling_NODE::incrTriggerReceived |
( |
| ) |
|
|
inlineprotected |
Increments the number of TRIGGER packets received.
Definition at line 517 of file uwpolling_NODE.h.
◆ initInfo()
| void Uwpolling_NODE::initInfo |
( |
| ) |
|
|
protectedvirtual |
Initializes the protocol at the beginning of the simulation.
This method is called by a command in tcl.
- Parameters
-
- See also
- command method
Definition at line 242 of file uwpolling_NODE.cpp.
◆ initPkt()
Inits the packet with the MAC address of the receiver and the sender, the size of the packet and the type.
- Parameters
-
| UWPOLLING_PKT_TYPE | the type of the packet |
Definition at line 517 of file uwpolling_NODE.cpp.
◆ Mac2PhyStartTx()
| void Uwpolling_NODE::Mac2PhyStartTx |
( |
Packet * |
p | ) |
|
|
protectedvirtual |
Pass the packet to the PHY layer.
- Parameters
-
| Packet* | Pointer to an object of type Packet that rapresent the Packet to transmit |
Definition at line 450 of file uwpolling_NODE.cpp.
◆ Phy2MacEndRx()
| void Uwpolling_NODE::Phy2MacEndRx |
( |
Packet * |
p | ) |
|
|
protectedvirtual |
Method called when the Phy Layer finish to receive a Packet.
- Parameters
-
| const | Packet* Pointer to an object of type Packet that rapresent the packet received |
Definition at line 617 of file uwpolling_NODE.cpp.
◆ Phy2MacEndTx()
| void Uwpolling_NODE::Phy2MacEndTx |
( |
const Packet * |
p | ) |
|
|
protectedvirtual |
Method called when the PHY layer finish to transmit the packet.
- Parameters
-
| Packet* | Pointer to an object of type Packet that rapresent the Packet transmitted |
Definition at line 463 of file uwpolling_NODE.cpp.
◆ Phy2MacStartRx()
| virtual void Uwpolling_NODE::Phy2MacStartRx |
( |
const Packet * |
p | ) |
|
|
inlineprotectedvirtual |
Method called when the Phy Layer start to receive a Packet.
- Parameters
-
| const | Packet* Pointer to an object of type Packet that rapresent the Packet that is in reception |
Definition at line 450 of file uwpolling_NODE.h.
◆ recvFromUpperLayers()
| void Uwpolling_NODE::recvFromUpperLayers |
( |
Packet * |
p | ) |
|
|
protectedvirtual |
Receives the packet from the upper layer (e.g.
IP)
- Parameters
-
| Packet* | pointer to the packet received |
Definition at line 392 of file uwpolling_NODE.cpp.
◆ refreshReason()
Refresh the reason for the changing of the state.
- Parameters
-
| UWPOLLING_NODE_REASON | The reason of the change of the state |
Definition at line 479 of file uwpolling_NODE.h.
◆ refreshState()
Refresh the state of the protocol.
- Parameters
-
| UWPOLLING_AUV_STATUS | current state of the protcol |
Definition at line 489 of file uwpolling_NODE.h.
◆ RxPollTimerExpired()
| void Uwpolling_NODE::RxPollTimerExpired |
( |
| ) |
|
|
protectedvirtual |
Methods called by the Expire event of the timer.
Here we disable the possibility of the node to receive POLL packets.
Definition at line 114 of file uwpolling_NODE.cpp.
◆ stateIdle()
| void Uwpolling_NODE::stateIdle |
( |
| ) |
|
|
protectedvirtual |
◆ stateRxPoll()
| void Uwpolling_NODE::stateRxPoll |
( |
| ) |
|
|
protectedvirtual |
State of the protocol in which a POLL packet is received.
Here the node check if he's polled or, at least, he is in the list of polled node. If he's the polled node, he goes into the stateTxData state. Otherwise he drops the packet
Definition at line 356 of file uwpolling_NODE.cpp.
◆ stateRxTrigger()
| void Uwpolling_NODE::stateRxTrigger |
( |
| ) |
|
|
protectedvirtual |
State of the protocol in which a TRIGGER packet is received.
Here we check the header of the TRIGGER and we store the information into it (i.e. the range of values into which choose randomly the backoff time
Definition at line 575 of file uwpolling_NODE.cpp.
◆ stateTxData()
| void Uwpolling_NODE::stateTxData |
( |
| ) |
|
|
protectedvirtual |
State of the protocol in which a DATA packet is sent.
Here we compute some statistics related to the transmission of the packet (i.e. the number of data packets transmitted is incremented and we check the number of data packet to transmit
Definition at line 418 of file uwpolling_NODE.cpp.
◆ stateTxProbe()
| void Uwpolling_NODE::stateTxProbe |
( |
| ) |
|
|
protectedvirtual |
State of the protocol in which a PROBE packet is sent.
Here we store into the PROBE header all the information needed, such as the timestamp of the most recent data packet, the number of the packets that the node wish to transmit
Definition at line 298 of file uwpolling_NODE.cpp.
◆ stateWaitPoll()
| void Uwpolling_NODE::stateWaitPoll |
( |
| ) |
|
|
protectedvirtual |
State in which the protocol set up the timer to wait the reception of the POLL packet.
Definition at line 340 of file uwpolling_NODE.cpp.
◆ TxData()
| void Uwpolling_NODE::TxData |
( |
| ) |
|
|
protectedvirtual |
◆ TxPRobe()
| void Uwpolling_NODE::TxPRobe |
( |
| ) |
|
|
protectedvirtual |
◆ waitForUser()
| void Uwpolling_NODE::waitForUser |
( |
| ) |
|
|
protectedvirtual |
Used for debug purposes.
(Permit to have a "step by step" behaviour of the protocol)
Definition at line 687 of file uwpolling_NODE.cpp.
◆ AUV_mac_addr
| int Uwpolling_NODE::AUV_mac_addr |
|
protected |
◆ backoff_timer
◆ backoff_tuner
| double Uwpolling_NODE::backoff_tuner |
|
protected |
◆ BOffTime
| double Uwpolling_NODE::BOffTime |
|
protected |
◆ buffer_data_pkts
| int Uwpolling_NODE::buffer_data_pkts |
|
protected |
Length of buffer of DATA pkts in number of pkts.
Definition at line 677 of file uwpolling_NODE.h.
◆ curr_data_pkt
| Packet* Uwpolling_NODE::curr_data_pkt |
|
protected |
◆ curr_poll_pkt
| Packet* Uwpolling_NODE::curr_poll_pkt |
|
protected |
◆ curr_probe_pkt
| Packet* Uwpolling_NODE::curr_probe_pkt |
|
protected |
◆ curr_state
◆ curr_trigger_pkt
| Packet* Uwpolling_NODE::curr_trigger_pkt |
|
protected |
◆ fout
| std::ofstream Uwpolling_NODE::fout |
|
protected |
◆ initialized
| bool Uwpolling_NODE::initialized = false |
|
staticprotected |
true if the protocol is initialized, false otherwise
Definition at line 692 of file uwpolling_NODE.h.
◆ Intra_data_Guard_Time
| int Uwpolling_NODE::Intra_data_Guard_Time |
|
protected |
Guard Time between one data packet and the following.
Definition at line 687 of file uwpolling_NODE.h.
◆ last_reason
◆ LastPacket
| bool Uwpolling_NODE::LastPacket |
|
protected |
true if the node has just sent the last packet of the queue and has to exit from the TxData state, false otherwise
Definition at line 703 of file uwpolling_NODE.h.
◆ max_data_pkt_tx
| int Uwpolling_NODE::max_data_pkt_tx |
|
protected |
Max number of DATA packets to transmit each cycle.
Definition at line 680 of file uwpolling_NODE.h.
◆ max_payload
| int Uwpolling_NODE::max_payload |
|
protected |
◆ MaxTimeStamp
| double Uwpolling_NODE::MaxTimeStamp |
|
protected |
Timestamp of the most recent data packet generated.
Definition at line 708 of file uwpolling_NODE.h.
◆ N_data_pkt_2_TX
| int Uwpolling_NODE::N_data_pkt_2_TX |
|
protected |
Number of DATA packets to transmit to the AUV.
Definition at line 716 of file uwpolling_NODE.h.
◆ n_poll_dropped
| int Uwpolling_NODE::n_poll_dropped |
|
protected |
◆ N_polled_node
| uint Uwpolling_NODE::N_polled_node |
|
protected |
◆ n_probe_sent
| int Uwpolling_NODE::n_probe_sent |
|
protected |
◆ n_run
| int Uwpolling_NODE::n_run |
|
protected |
◆ n_times_polled
| int Uwpolling_NODE::n_times_polled |
|
protected |
Number of times that the node has been polled by the AUV.
Definition at line 719 of file uwpolling_NODE.h.
◆ n_trigger_dropped
| int Uwpolling_NODE::n_trigger_dropped |
|
protected |
◆ n_trigger_received
| int Uwpolling_NODE::n_trigger_received |
|
protected |
◆ node_id
| uint Uwpolling_NODE::node_id |
|
protected |
◆ out_file_stats
| std::ofstream Uwpolling_NODE::out_file_stats |
|
protected |
◆ packet_index
| int Uwpolling_NODE::packet_index |
|
protected |
◆ pkt_type_info
◆ polled
| bool Uwpolling_NODE::polled |
|
protected |
◆ prev_state
◆ print_stats
| int Uwpolling_NODE::print_stats |
|
protected |
◆ PROBE_uid
| uint Uwpolling_NODE::PROBE_uid |
|
protected |
◆ Q_data
| std::queue<Packet *> Uwpolling_NODE::Q_data |
|
protected |
◆ reason_info
◆ rx_poll_timer
◆ RxPollEnabled
| bool Uwpolling_NODE::RxPollEnabled |
|
protected |
true if the node is enabled to receive the POLL, false otherwise
Definition at line 698 of file uwpolling_NODE.h.
◆ sea_trial
| int Uwpolling_NODE::sea_trial |
|
protected |
Sea Trial flag: To activate if the protocol is going to be tested at the sea.
Definition at line 683 of file uwpolling_NODE.h.
◆ status_info
◆ T_fin
| double Uwpolling_NODE::T_fin |
|
protected |
Upper bound of the range in which choose randomly the backoff time (sent by the AUV in the TRIGGER message)
Definition at line 712 of file uwpolling_NODE.h.
◆ T_in
| double Uwpolling_NODE::T_in |
|
protected |
Lower bound of the range in which choose randomly the backoff time (sent by the AUV in the TRIGGER message)
Definition at line 710 of file uwpolling_NODE.h.
◆ T_poll
| double Uwpolling_NODE::T_poll |
|
protected |
◆ Triggered
| bool Uwpolling_NODE::Triggered |
|
protected |
true if the node has correctly received a TRIGGER, false otherwise
Definition at line 700 of file uwpolling_NODE.h.
◆ tx_data_timer
The documentation for this class was generated from the following files:


organizing idea-share
How can you work for change?
individually and with others and in conjunction with larger movements -- to improve the way people relate to themselves, to one another, to the Earth, and to other aspects of the universe


Guidance
Procurement training sessions for school staff who are responsible or accountable for budgets or buying.
ZIP , 924KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 1.26MB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 838KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 919KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 471KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 493KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 1.13MB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 562KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 799KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 701KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 1.3MB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 895KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
ZIP , 1.13MB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
Procurement training modules for school staff including:
These modules will help school staff understand public procurement legislation and get together to share effective practice and improve their procurement skills.
Each module contains slides, trainer notes and exercises, that you can use to run your own sessions. They follow a simple procurement cycle and are designed to last from 15 to 50 minutes to fit in with your meetings.
Contact us if you have any questions or feedback about these materials.
Published: 20 January 2016
Updated: 21 October 2016


In partnership with the TREE Lab in Northwestern’s School of Education and Social Policy,the Block Museum presented a special online screening, on June 17, 2020, of three documentaries produced by students of the Young People’s Race, Power, and Technology (YPRPT) project. YPRPT is an afterschool program, developed in partnership with community partners including Evanston Township High School, Family Matters, Endangered Peace, and the Lucy Parsons Labs, that brings together NU undergraduate students with youth and community members to jointly investigate the ethical and social dimensions of specific law enforcement technologies such as facial recognition and gang databases.


{{ define "title" }} 404 Not Found - {{ .Site.Title}} {{ end }} {{ define "banner" }}
Tomorrow, and tomorrow, and tomorrow,
Creeps in this petty pace from day to day,
To the last syllable of recorded time;
And all our yesterdays have lighted fools
The way to dusty death. Out, out, brief candle!
Life's but a walking shadow, a poor player,
That struts and frets his hour upon the stage,
And then is heard no more.


[page:Object3D] →
[name]
Base class for Mesh objects, such as [page:MorphAnimMesh] and [page:SkinnedMesh].
Example
var geometry = new THREE.BoxGeometry( 1, 1, 1 );
var material = new THREE.MeshBasicMaterial( { color: 0xffff00 } );
var mesh = new THREE.Mesh( geometry, material );
scene.add( mesh );
Constructor
[name]( [page:Geometry geometry], [page:Material material] )
geometry — An instance of [page:Geometry].
material — An instance of [page:Material] (optional).
Properties
[property:Geometry geometry]
An instance of [page:Geometry], defining the object's structure.
[property:Material material]
An instance of [page:Material], defining the object's appearance. Default is a [page:MeshBasicMaterial] with wireframe mode enabled and randomised colour.
[property:Array morphTargetInfluences]
An array of weights typically from 0-1 that specify how much of the morph is applied.
Undefined by default, but reset to a blank array by [page:Mesh.updateMorphTargets updateMorphTargets].
[property:Array morphTargetDictionary]
A dictionary of morphTargets based on the morphTarget.name property.
Undefined by default, but rebuilt [page:Mesh.updateMorphTargets updateMorphTargets].
[property:Integer drawMode]
Determines how the mesh triangles are constructed from the vertices. See the draw mode [page:DrawModes constants] for all possible values. Default is [page:DrawModes TrianglesDrawMode].
Methods
[method:null updateMorphTargets]()
Updates the morphtargets to have no influence on the object. Resets the
[page:Mesh.morphTargetInfluences morphTargetInfluences],
[page:Mesh.morphTargetDictionary morphTargetDictionary], and
[page:Mesh.morphTargetBase morphTargetBase] properties.
[method:Array raycast]( [page:Raycaster raycaster], [page:Array intersects] )
Get intersections between a casted ray and this mesh. [page:Raycaster.intersectObject] will call this method.
[method:Mesh clone]()
Returns a clone of this Mesh object and its descendants.
Source
[link:https://github.com/mrdoob/three.js/blob/master/src/[path].js src/[path].js]


Spain is a country in Southern Europe. It is in the Iberian Peninsula. Spain has borders with France, Portugal, Andorra and Morocco. In Spain's northeast side are the Pyrenees mountains. The people of Spain are called Spaniards. They speak Castilian or Spanish (in Spanish, "Castellano", from Castilla, or "Español" [espa'ɲol]. They speak other languages in some parts of the country. They are Catalan, Basque, and Galician, Leonese, Aragonese, Aranese Occitan and even Portuguese. The religion of about 56% of the population in Spain is Roman Catholic.


Purpose: This document (1) helps us write the API and (2) is used by API consumers to understand its functionality.
Notes:
The Penn Course Review API
is a simple RESTful API to the data available on PennCourseReview.com The easiest way to explain it is to look at some queries.
Return type: The results will be JSON Objects, which you should be able to turn into a dictionary in whatever language you are working with, using something like json_decode.
Note: All non-canonical links (i.e. redirects) are in blue. The most important canonical links are in red (common access points, or special information).
Usage:
All queries will be of the form http://pennapps.com/courses-demo/[query]?token=pennappsdemo
Note: For security purposes, the string "?token=pennappsdemo" must be appended to the end of each query.
Example Query:
http://pennapps.com/courses-demo/course/CIS-120?token=pennappsdemo
The following are descriptions and sample output of available queries.
### Need to produce useful output for /depts ###
{ "result": { "values": [ { "id": "anaranjado", "name": "Jaime Mundo", "path": "/instructor/anaranjado" }, { "id": "amky", "name": "Alexey Komissarouky", "path": "/instructor/amky" }, ... ] }, "retrieved": "2011-09-13 21:04:37.638522", "valid": true, "version": "0.2" }
### Need to produce useful output for /semesters ###
#Course resource, e.g. "CIS-120 in 2011c".
Note that a Course may have multiple aliases (crosslistings): "Intro to Cognitive Science" is one Course with five aliases ("CIS-140", "COGS-001", "PSYC-107", "PHIL-044", "LING-105")
A Course can be accessed from the following paths:
A Course has the following subpaths:
{ "result": { "aliases": [ "FNAR-337" ], "credits": 1.0, "description": "Explore the majesty of the color Orange in its natural habitat, and ridicule other, uglier colors, such as Chartreuse (eww).", "history": { "path": "/course/88/history" }, "id": 88, "name": "Advanced Orange", "path": "/course/88", "reviews": { "path": "/course/88/reviews" }, "sections": { "path": "/course/88/sections", "values": [ { "aliases": [ "FNAR-337-001" ], "id": "88-001", "name": "Advanced Orange", "path": "/course/88/section/001", "sectionnum": "001" } ] } }, "retrieved": "2011-09-13 21:46:41.575956", "valid": true, "version": "0.2" }
{ "result": { "values": [ { "comments": null, "path": "/course/88/section/001/review/anaranjado", "ratings": { "Course": 2.4500000000000002, "Difficulty": 2.54, "Instructor": 2.5499999999999998, "Learned": 3, "Readings": 3, "Workload": 3 }, "section": { "aliases": [ "FNAR-337-001" ], "id": "88-001", "name": "Advanced Orange", "path": "/course/88/section/001", "sectionnum": "001" } } ] }, "retrieved": "2011-09-13 21:50:09.743629", "valid": true, "version": "0.2" }
{ "result": { "values": [ { "aliases": [ "FNAR-337-001" ], "course": { "aliases": [ "FNAR-337" ], "id": 88, "name": "Advanced Orange", "path": "/course/88" }, "group": 1, "id": "88-001", "instructors": [ { "id": "anaranjado", "name": "Jaime Mundo", "path": "/instructor/anaranjado" } ], "meetingtimes": [ { "day": "W", "end": "15:00", "room": { "building": { "id": "LEVH", "latitude": 13.371337, "longitude": 90.010000000000005, "name": "Levine Hall", "path": "/building/LEVH" }, "id": "LEVH 101", "name": "Wu and Chen Auditorium", "number": "101" }, "start": "13:30", "type": "LEC" } ], "name": "Advanced Orange", "path": "/course/88/section/001", "reviews": { "path": "/course/88/section/001/reviews" }, "sectionnum": "001" } ] }, "retrieved": "2011-09-13 21:52:34.422995", "valid": true, "version": "0.2" }
{ "result": { "aliases": [ "FNAR-337-001" ], "course": { "aliases": [ "FNAR-337" ], "id": 88, "name": "Advanced Orange", "path": "/course/88" }, "group": 1, "id": "88-001", "instructors": [ { "id": "anaranjado", "name": "Jaime Mundo", "path": "/instructor/anaranjado" } ], "meetingtimes": [ { "day": "W", "end": "15:00", "room": { "building": { "id": "LEVH", "latitude": 13.371337, "longitude": 90.010000000000005, "name": "Levine Hall", "path": "/building/LEVH" }, "id": "LEVH 101", "name": "Wu and Chen Auditorium", "number": "101" }, "start": "13:30", "type": "LEC" } ], "name": "Advanced Orange", "path": "/course/88/section/001", "reviews": { "path": "/course/88/section/001/reviews" }, "sectionnum": "001" }, "retrieved": "2011-09-13 21:54:13.297739", "valid": true, "version": "0.2" }
{ "result": { "courses": [ { "aliases": [ "FNAR-337" ], "id": 88, "name": "Advanced Orange", "path": "/course/88" } ], "id": 1000088, "path": "/coursehistory/1000088", "reviews": { "path": "/coursehistory/1000088/reviews" } }, "retrieved": "2011-09-13 22:00:05.138112", "valid": true, "version": "0.2" }
#Section resource, e.g. "CIS-120-001 in 2011c".
A Section can be accessed from the following paths:
A Section has the following subpaths:
{ "result": { "aliases": [ "FNAR-337-001" ], "course": { "aliases": [ "FNAR-337" ], "id": 88, "name": "Advanced Orange", "path": "/course/88" }, "group": 1, "id": "88-001", "instructors": [ { "id": "anaranjado", "name": "Jaime Mundo", "path": "/instructor/anaranjado" } ], "meetingtimes": [ { "day": "W", "end": "15:00", "room": { "building": { "id": "LEVH", "latitude": 13.371337, "longitude": 90.010000000000005, "name": "Levine Hall", "path": "/building/LEVH" }, "id": "LEVH 101", "name": "Wu and Chen Auditorium", "number": "101" }, "start": "13:30", "type": "LEC" } ], "name": "Advanced Orange", "path": "/course/88/section/001", "reviews": { "path": "/course/88/section/001/reviews" }, "sectionnum": "001" }, "retrieved": "2011-09-15 20:36:03.241815", "valid": true, "version": "0.3" }
{ "result": { "values": [ { "comments": "Nyanyanyanyan!", "path": "/course/88/section/001/review/anaranjado", "ratings": { "Course": 2.4500000000000002, "Difficulty": 2.54, "Instructor": 2.5499999999999998, "Learned": 3, "Readings": 3, "Workload": 3 }, "section": { "aliases": [ "FNAR-337-001" ], "id": "88-001", "name": "Advanced Orange", "path": "/course/88/section/001", "sectionnum": "001" } } ] }, "retrieved": "2011-09-15 20:38:37.273812", "valid": true, "version": "0.3" }
{ "result": { "comments": "Nyanyanyanyan!", "path": "/course/88/section/001/review/anaranjado", "ratings": { "Course": 2.4500000000000002, "Difficulty": 2.54, "Instructor": 2.5499999999999998, "Learned": 3, "Readings": 3, "Workload": 3 }, "section": { "aliases": [ "FNAR-337-001" ], "id": "88-001", "name": "Advanced Orange", "path": "/course/88/section/001", "sectionnum": "001" } }, "retrieved": "2011-09-15 20:41:11.705441", "valid": true, "version": "0.3" }
#Review resource.
A Review contains several ratings.
The ratings correspond to the following questions:
| rCourseQuality | Overall Quality of the course. |
| rInstructorQuality | Overall Quality of the instructor. |
| rDifficulty | Please rate the difficulty of the course. (0=easy to 4=difficult) |
| rCommAbility | Instructor's ability to communicate the subject matter. |
| rInstructorAccess | Instructor's accessibility and willingness to to discuss course content and any problems. |
| rReadingsValue | Value of assigned readings. |
| rAmountLearned | Amount learned from this course in terms of knowledge, concepts, skills and thinking ability. |
| rWorkRequired | Please rate the amount of work required for this course. (0=very little to 4=very much) |
| rRecommendMajor | Would you recommend this course to a major? (0=no to 4=strongly) |
| rRecommendNonMajor | Would you recommend this course to a non-major? (0=no to 4=strongly) |
| rStimulateInterest | Was the instructor able to stimulate your interest in the material? |
| rArticulateGoals | Were the goals of the course clearly articulated? |
| rSkillEmphasis | Was the emphasis placed on the language skills (speaking, listening, reading writing) appropriate in terms of the defined goals of the course? |
| rHomeworkValuable | Were homework exercises (and compositions, where appropriate) valuable reinforcement of classroom work? |
| rExamsConsistent | Were the exams consistent with assignments, materials, and method of instruction? |
| rAbilitiesChallenged | Were your linguistic abilities in reading, writing, speaking, and listening sufficiently challenged? |
| rClassPace | How would you rate the pace of the course? (0=much to slow; 1=too slow; 2=just right; 3=too fast; 4=much too fast) |
| rOralSkills | Did the instructor organize appropriate activities in class to encourage the use of oral skills? |
| rInstructorConcern | Was the instructor concerned that students learn the materials? |
| rInstructorRapport | Please evaluate the rapport between the class and the instructor. (0=bad, 4=excellent) |
| rInstructorAttitude | Please rate the instructor's attitude towards the course. |
| rInstructorEffective | Please rate the instructor's effectiveness in presenting and explaining course materials. |
| rGradeFairness | Please rate the fairness of the grading process in the course. |
| rNativeAbility | Do you feel that the skills learned in this course would help you survive in a native environment? |
| rTAQuality | Please evaluate the overall quality of the teaching assistant/drill instructor in the course. |
If accessed from a Section, a Review also contains a full text review.
A Review cannot be accessed from the top-level; it can be accessed from a Section, Course, or Instructor.
#Instructor resource.An Instructor can be accessed from the following paths:
An Instructor has the following subpaths:
{ "result": { "id": "anaranjado", "name": "Jaime Mundo", "path": "/instructor/anaranjado", "reviews": { "path": "/instructor/anaranjado/reviews" }, "sections": { "path": "/instructor/anaranjado/sections" } }, "retrieved": "2011-09-15 20:43:54.813292", "valid": true, "version": "0.3" }
{ "result": { "values": [ { "aliases": [ "FNAR-337-001" ], "id": "88-001", "name": "Advanced Orange", "path": "/course/88/section/001", "sectionnum": "001" } ] }, "retrieved": "2011-09-15 20:44:45.499336", "valid": true, "version": "0.3" }
{ "result": { "values": [ { "comments": null, "path": "/course/88/section/001/review/anaranjado", "ratings": { "Course": 2.4500000000000002, "Difficulty": 2.54, "Instructor": 2.5499999999999998, "Learned": 3, "Readings": 3, "Workload": 3 }, "section": { "aliases": [ "FNAR-337-001" ], "id": "88-001", "name": "Advanced Orange", "path": "/course/88/section/001", "sectionnum": "001" } } ] }, "retrieved": "2011-09-15 20:45:29.818631", "valid": true, "version": "0.3" }
#Course History, e.g. "CIS-120"
A course history is a course over time; it has no associated semester. It also includes previous names. For example, the course history of CIS-160 includes the last several semesters of CIS-160, CIS-260, and CSE-260.
A Course History can be accessed from the following paths:
{ "result": { "courses": [ { "aliases": [ "FNAR-337" ], "id": 88, "name": "Advanced Orange", "path": "/course/88" } ], "id": 1000088, "path": "/coursehistory/1000088", "reviews": { "path": "/coursehistory/1000088/reviews" } }, "retrieved": "2011-09-15 20:59:04.323881", "valid": true, "version": "0.3" }
A Course History has the following subpaths:
#Building
### BUILDING DATA NOT CURRENTLY AVAILABLE ###
A Building can be accessed from the following path:
A Building has the following subpaths
#Department (if top-level)
A Department can be accessed from the following paths:
A Department has the following subpaths:
Note: These is not the only type of resources available, but understanding what these offer should help
Descriptive Aliases, for discovery, etc
Note: see https://gomockingbird.com/mockingbird/#fi6qy0z/ for mockups
Course Page:
Instructor Page:


{% extends "base.html" %} {% block content %}
You can login with any of the providers listed here (no registration required!). Alternatively you can use the classic form to login with us. If you don't have an account yet you can register for one.


“Putto buddhassa dāyādo,
kassapo susamāhito;
Pubbenivāsaṁ yovedi,
saggāpāyañca passati.
Kassapa is the son and heir of the Buddha,
whose mind is immersed in samādhi.
He knows his past lives,
he sees heaven and places of loss,
Atho jātikkhayaṁ patto,
abhiññāvosito muni;
Etāhi tīhi vijjāhi,
tevijjo hoti brāhmaṇo.
and has attained the end of rebirth:
that sage has perfect insight.
It’s because of these three knowledges
that the brahmin is a master of the three knowledges.
Tatheva bhaddā kāpilānī,
tevijjā maccuhāyinī;
Dhāreti antimaṁ dehaṁ,
jetvā māraṁ savāhiniṁ.
In exactly the same way, Bhaddā Kāpilānī
is master of the three knowledges, destroyer of death.
She bears her final body,
having vanquished Māra and his mount.
Disvā ādīnavaṁ loke,
ubho pabbajitā mayaṁ;
Tyamha khīṇāsavā dantā,
sītibhūtamha nibbutā”ti.
Seeing the danger of the world,
both of us went forth.
Now we are tamed, our defilements have ended;
we’ve become cooled and quenched.
…
Bhaddā kāpilānī therī ….


Headers
=======
There are two ways to do headers in Markdown. (In these examples, Header 1 is the biggest, and Header 6 is the smallest.)
You can underline text to make the two top-level headers:
Header 1
========
Header 2
--------
The number of `=` or `-` signs doesn't matter; you can get away with just one. But using enough to underline the text makes your titles look better in plain text.
You can also use hash marks for all six levels of HTML headers:
# Header 1 #
## Header 2 ##
### Header 3 ###
#### Header 4 ####
##### Header 5 #####
###### Header 6 ######
The closing `#` characters are optional.
Horizontal Rules
================
You can insert a horizontal rule by putting three or more hyphens, asterisks, or underscores on a line by themselves:
---
*******
___
You can also use spaces between the characters:
- - - -
All of these examples produce the same output.
Lists
=====
Simple lists
------------
A bulleted list:
- You can use a minus sign for a bullet
+ Or plus sign
* Or an asterisk
A numbered list:
1. Numbered lists are easy
2. Markdown keeps track of the numbers for you
7. So this will be item 3.
A double-spaced list:
- This list gets wrapped in `` tags
- So there will be extra space between items
Advanced lists: Nesting
-----------------------
You can put other Markdown blocks in a list; just indent four spaces for each nesting level. So:
1. Lists in a list item:
- Indented four spaces.
* indented eight spaces.
- Four spaces again.
2. Multiple paragraphs in a list items:
It's best to indent the paragraphs four spaces
You can get away with three, but it can get
confusing when you nest other things.
Stick to four.
We indented the first line an extra space to align
it with these paragraphs. In real use, we might do
that to the entire list so that all items line up.
This paragraph is still part of the list item, but it looks messy to humans. So it's a good idea to wrap your nested paragraphs manually, as we did with the first two.
3. Blockquotes in a list item:
> Skip a line and
> indent the >'s four spaces.
4. Preformatted text in a list item:
Skip a line and indent eight spaces.
That's four spaces for the list
and four to trigger the code block.
Blockquotes
===========
Simple blockquotes
------------------
Blockquotes are indented:
> The syntax is based on the way email programs
> usually do quotations. You don't need to hard-wrap
> the paragraphs in your blockquotes, but it looks much nicer if you do.
Advanced blockquotes: Nesting
-----------------------------
You can put other Markdown blocks in a blockquote; just add a `>` followed by a space:
Parragraph breaks in a blockquote:
> The > on the blank lines is optional.
> Include it or don't; Markdown doesn't care.
>
> But your plain text looks better to
> humans if you include the extra `>`
> between paragraphs.
Blockquotes within a blockquote:
> A standard blockquote is indented
> > A nested blockquote is indented more
> > > > You can nest to any depth.
Lists in a blockquote:
> - A list in a blockquote
> - With a > and space in front of it
> * A sublist
Preformatted text in a blockquote:
> Indent five spaces total. The first
> one is part of the blockquote designator.
Images
======
Images are exactly like links, but they have an exclamation point in front of them:
![Valid XHTML] (http://w3.org/Icons/valid-xhtml10).
The word in square brackets is the alt text, which gets displayed if the browser can't show the image. Be sure to include meaningful alt text for blind users' screen-reader software.
Just like links, images work with reference syntax and titles:
This page is ![valid XHTML][checkmark].
[checkmark]: http://w3.org/Icons/valid-xhtml10
"What are you smiling at?"
**Note:**
Markdown does not currently support the shortest reference syntax for images:
Here's a broken ![checkmark].
But you can use a slightly more verbose version of implicit reference names:
This ![checkmark][] works.
The reference name (`valid icon`) is also used as the alt text.
Inline HTML
===========
If you need to do something that Markdown can't handle, you can always just use HTML:
Strikethrough humor is funny.
Markdown is smart enough not to mangle your span-level HTML:
Markdown works *fine* in here.
Block-level HTML elments have a few restrictions:
1. They must be separated from surrounding text by blank
lines.
2. The begin and end tags of the outermost block element
must not be indented.
3. You can't use Markdown within HTML blocks.
So:
You can not use Markdown in here.
Preformatted Text
=================
You can include preformatted text in a Markdown document.
To make a code block, indent four spaces:
printf("goodbye world!"); /* his suicide note
was in C */
The text will be wrapped in `` and `` tags, and the browser will display it in a monospaced typeface. The first four spaces will be stripped off, but all other whitespace will be preserved.
You cannot use Markdown or HTML within a code block, which makes them a convenient way to show samples of Markdown or HTML syntax:
Code Spans
==========
You can make inline `` tags by using code spans. Use backticks to make a code span:
Press the `` key, then type a `$`.
(The backtick key is in the upper left corner of most keyboards.)
Like code blocks, code spans will be displayed in a monospaced typeface. Markdown and HTML will not work within them:
Markdown italicizes things like this: `I *love* it.`
Don't use the `` tag; use CSS instead.


The generator converts fuel to electricity. It can be produce at different power levels. Click on the device in order to manually toggle between running modes. Note that any connected Energy App may be quick to send its commands to the generator, thereby overriding your manual actions.
1000 W


This screen demonstrates the lazy loading of the google maps api. Check the network tab of the dev tools and the maps api should start loading 2 seconds after the page is loaded. This demo also shows the use of the map-lazy-load-params attribute to allow specification of map API key via an angular/javascript variable.


As we know public transportation is one of the most important part of New York City, through
this data visualization project we aim at analysing the yellow cabs data provided by NYC Open
Data source and generate visualizations that would help a New York cab rider to make a
decision of whether to take a cab or prefer using the subway.
Some of our stats
Total Number of features
Total Number of examples
Lets Start the ride
Please select the pick-up location
Please select the drop-off location
Will there be a cab easily available at this hour?


Resources
The data is on this public sheet. You can contribute by filling out this form. Entries marked with (*) require login.
Journal
- Ai & Society: here (*)
- Computer Music Journal (CMJ): here | here (*)
- Digital Creativity: here (*)
- Electronics (ELECTRONICS): here
- Ieee Transactions On Signal Processing (IEEE TSP): here (*)
- Journal For Artistic Research (JAR): here
- Journal Of Creative Music Systems (JCMS): here | here
- Journal Of Mathematics And Music (JMATHMUSIC): here | here (*)
- Journal Of Network Music And Arts (JONMA): here
- Journal Of New Music Research (JNMR): here (*)
- Journal Of Sonic Studies (JSS): here
- Journal Of The Audio Engineering Society (JAES): here (*)
- Journal Of The Audio Engineering Society (JAES): here (*)
- Journal Of The Canadian Electroacoustic Community (eContact!): here
- Journals Of The University Of California Press (UCPRESS): here (*)
- Leonardo (LEONARDO): here (*)
- Leonardo Music Journal (LMJ): here (*)
- Music Theory Spectrum (SPECTRUM): here
- Nordic Journal For Artistic Research (VIS): here (*)
- Organized Sound (OS): here (*)
- Perspectives Of New Music (PNM): here | here (*)
- Ruukku: here
- Search New Music: here
- Sound Studies: here (*)
- The Conference And The Journal Of The Korea Electro-Acoustic Music Society (The KEAMSAC and Emille Project): here | here
- Transactions Of International Society For Music Information Retrieval (TISMIR): here
Conference
- Audio Mostly: here
- Australasian Computer Music Conference (ACMC): here
- International Computer Music Conference (ICMC): here
- International Conference On Auditory Display (ICAD): here | here
- International Conference On Digital Audio Effects (DAFx): here
- International Society For Music Information Retrieval (ISMIR): here
- Internationales Festival Für Medienkunst (CYNET): here
- Jeu De Temps / Times Play (JTTP): here
- Linux Audio Conference (LAU): here
- New Interfaces For Musical Expression (NIME): here
- Sound And Music Computing (SMC): here
- Web Audio Conference (WAC): here
List-Serv
- Canadian Electroacoustic Community (CEC): here (*)
- Chuck List Archives (chuck-users): here
- Csound List Archives: here
- Jacktrip Users Groop: here (*)
- Librosa Discussion Forum: here (*)
- Linux Audio List Archives (linux-audio-user): here
- Nime Mailing List: here (*)
- Pure Data List Archives (pd-list): here
- Smc Network List: here (*)
- Society For Electro-Acoustic Music In The United States (SEAMUS): here (*)
- Supercollider List Archives (sc-users): here
Catalogue
- Artistic Resarch: here
- Dblp Computer Science Bibliography (DBLP): here
- Electroacoustic Resource Site (EARS): here
- Iain Mccurdy’S Website: here
- Mir Conference Deadlines: here
- Smc Network: here | here
- Soundsoftware Project: here
- The Big Artist Opportunities List: here
- Algorithmic Musicology Team (Algomus): here | here
- Auditory List (McGill University): here (*)
- Degem Deutsche Gesellschaft Für Elektroakustische Musik E.V. (DEGEM): here | here
- Fundacion Destellos: here
- International Computer Music Association (ICMA): here
- Muestra Internacional De Música Electroacústica (Muslab): here
- V2 Lab For The Unstable Media (V2): here
Book
- Audio Content Analysis: here
- Information Retrieval: here
- Mathematics Of The Discrete Fourier Transform (Dft): here
- Music And Computers: A Theoretical And Historical Approach: here
- Theory And Techniques Of Electronic Music: here
Database
- Center For Art And Media Karlsruhe (ZKM): here | here
- Free Sound Fx (Free SFX): here
- International Documentation Of Electroacoustic Music (EMDOKU): here
- See This Sound: here
- Sonus: here
Blog
- Center For Visual Music (CVM): here
- Jack Schaedler’S Circles And Sines (DFT): here
- Music Radar: here
- Sound And Music: here
- Spatial Audio: here
Courses
- Brad Garton’S Youtube Channel: here
- Classes Taught By Miller Puckette: here
- Computer Music Center Courses At Columbia University (CMC Cources): here
- Supercollider Tutorial: here
Institute
- Institute For Research And Coordination In Acoustics/Music (IRCAM): here (*)
- Institute Of Electronic Music And Acoustics (IEM): here (*)
- Maynooth University Research Archive Library (MURAL): here
- Spatial Sound Institute (SSI): here
Books
Festival
- Festival And Platform For Adventurous Music & Art (CMT): here
- Transmediale: here
Foundation
- Foundation For Emerging Technologies And Arts (FETA): here
Plugins
- The Vamp Audio Analysis Plugin System (VAMP): here
Authors
(*) login required.


Currently studying Computer Science in North South University . I am passionate about programming in general. I like to take responsibility for my own action, and always trying to out-do myself. Learning something new gets me going. I am a very fast learner and a perfectionist.


- Microsoft Expression Web (from Expression Studio).
- DevExpress RefactorASP!
--- layout: post title: Web tools market is growing more and more date: 2007-02-05 17:40:00.000000000 +11:00 comments: true categories: - visual-studio - refactorasp - development - devtools - expression-web ---


Our basic massage, customized for your needs. Each massage therapists' style is different and possesses their own uniqueness.
Help target your specific problems such as pain, tension, etc. Comes with a diagnosis.
For treatment of musculoskeletal pain and disability. Involves kneading and manipulation of muscles, joint mobilization, and joint manipulation.
Proven to be effective in treating illness, acupuncture serves to stimulate and activate the body's natural self-healing mechanisms.
The process starts with exfoliation, followed by a 20-minute massage. Full-body wraps utilize various Chinese herbs and essential oils.


A visual representation of an item list. It can contain sections. The items can be clickable or not. Within the items additional widgets can be added.
This documentation will describe also the list-item widget which is an integral part of the list widget.

Header item

Item 1

Item 2

Header item

Item 1

Item 2

All options are accessible throught the getOption and setOptions method of the widget [topmostMarkupElement.list] object or the listItemMarkupElement.listItem object. After setting any of the options for the list widget, it will be unenhanced and enhanced to apply the newly set options.
Please use the theme method of the widget to read the current theme.
HTML-Markup notation: data-corners
JavaScript notation: corners
Possible values:
The corners of the widget will be rectangular.
The corners of the widget will be smoothed.
Default is: smooth
The corners property has no meaning if the isotope property is set to normal.
HTML-Markup notation: data-isotope
JavaScript notation: isotope
Possible values:
A list with a flat border looking like a separate unit.
A simple list without border - intended for embedding.
Default is: normal
HTML-Markup notation: data-isotope
JavaScript notation: isotope
Possible values:
Ordinary list item.
A list item with a chevron on the right.
A list item intended to be a header. It has larger font and a thicker underline border.
Default is: normal
HTML-Markup notation: data-tap
JavaScript notation: tap
If set to yes, the list item will be highlighted when tapped and a pointer cursor will be set if moved over the list item with the mouse.
Default is: no
HTML-Markup notation: data-h-dense
JavaScript notation: hDense
If set to yes, the list item will have no horizontal padding.
Default is: no
HTML-Markup notation: data-v-dense
JavaScript notation: vDense
If set to yes, the list item will have no vertical padding.
Default is: no
HTML-Markup notation: data-dense
JavaScript notation: dense
If set to yes, the list item will have no horizontal and vertical padding.
Default is: no
HTML-Markup notation: data-theme
JavaScript notation: theme
The theme name as string to be used for the widget. Possible values 'a' or 'b'. By default, 'a' stays for dark theme, while 'b' for the bright theme. If omitted, the widget will inherit the theme from its parent.
Please click on the links bellow to see the different live examples. All links will open in a new window. Once a link has opened, you can view the source code of the example.


WITNESS LIST Finance Committee January 15, 1997-9:00A Budget/Comm. on Fire Protection On: Bailey, Ken (Ass. of Fire Fighters), Austin Cain, Randy (TX Fire Chiefs Ass.), Austin James, Ronnie E. (Fire Protection), Austin Shelton, Carlton (Fire Protection), Austin Stalder, Kelley (Fire Protection), Austin Sullivan, Dick (SF and FMA), Austin Warren, Gary L. (Fire Protection), Austin Budget/Comm. on Jail Standards On: Crump, Jack E. (Comm. on Jail Standards), Austin Budget/Comm. on Judicial Conduct On: Flowers, Robert (SConJC), Austin Budget/Comptroller's Judiciary Sec. On: Camarillo, Leslee (Comptroller Judiciary), Austin Carruth, James (Comptroller Judiciary), Austin Dawson-Brown, Claire (Comptroller Judiciary), Austin Earle, Ronnie (Comptroller Judiciary), Austin McCleary, Steve (Comptroller Judiciary), Austin Registering, but not testifying: On: Chape, Robert T. (Comptroller Judiciary), Austin Demos, Chuck (Comptroller Judiciary), Austin Budget/Ct Reporters Certification On: Liedtke, Peg (CRCB), Austin Budget/CJPC On: Fabelo, Tony (CJPC), Austin Budget/CSOT On: Davis, Grace L. (CSOT), Austin Wilson, Robert E. (CSOT), Austin Budget/DPS On: Davis, Tommy (DPS), Austin Haas, Tom (DPS), Austin Martin, Tom (Police Chiefs Assn), Grapevine Thomas, Dudley M. (DPS), Austin Registering, but not testifying: On: Casteel, Bruce (DPS), Austin Urbanowsky, J.R. (Ron) (DPS), Austin Budget/Juvenile Probation Comm. On: Pace, Don (Juvenile Probation), Austin Wright, Vicki L. (Juvenile Probation), Austin Budget/State Law Library On: McCormick, Michael J. (State Law Library), Austin Schlueter, Kay (State Law Library), Austin Budget/State Prosecuting Attorney On: Matthew, Paul (State Prosecuting Att), Austin Budget/TDCJ On: Cole, Pat (TC on FV), Austin McNutt, David (TDCJ), Huntsville Morrow, Mike (TDCJ), Huntsville Scott, Wayne (TDCJ), Huntsville Budget/Youth Commission On: Franks, John (Youth Commission), Austin Graham, Terry (Youth Commission), Austin Harrell, Pete (Youth Commission), Austin Harris, Dwight (Youth Commission), Austin Lawrence, Leonard (Youth Commission), San Antonio Reyes, Linda S. (Youth Commission), Austin Robinson, Steve (Youth Commission), Austin Tamayo, Edna (Youth Commission), Austin


Three heroes: Knight's move
The court horse Guy Julius Caesar to his misfortune overhears the conversation of the boyars and learns about the plot against the prince. What to do? There is no one to protect the prince! The warriors are far away - they catch the robber Potan, Gorynych on vacation, the army at the exercises ... But if the bad guys are going to take over the world, then someone needs to save him? Who is he, a real hero, who will come to the rescue? Of course, the horse Julius! This strategist and the "great combinator". He will certainly save everyone, and if he does not, then at least he will try. The main thing is that the operation to save the world does not turn into a complete disaster.


{% extends "base_content.html" %} {% load i18n %} {% block title %}{% trans "3rd party Authorization Page" %}{% endblock %} {% block content %}
{% blocktrans %} You came on this page because you want to use your voting data and/or play the democracy game on an other website/service than ours. To protect your data *you* need to authorize the 3rd party on this page to acces your data. You can revoke granted acces later if you want. {% endblocktrans %}
{{msg}}


Arrow Pad Example
We will use two translations, French and Dutch, although there is no effective limit on the number of possible translations that can be used with an application. The relevant lines of arrowpad.pro
are
HEADERS = arrowpad.h \ mainwindow.h SOURCES = arrowpad.cpp \ main.cpp \ mainwindow.cpp TRANSLATIONS = arrowpad_fr.ts \ arrowpad_nl.ts
Run lupdate
; it should produce two identical message files arrowpad_fr.ts
and arrowpad_nl.ts
. These files will contain all the source texts marked for translation with tr()
calls and their contexts.
See the Qt Linguist Manual for more information about translating Qt application.
Line by Line Walkthrough
In arrowpad.h
we define the ArrowPad
subclass which is a subclass of QWidget. In the screenshot above, the central widget with the four buttons is an ArrowPad
.
class ArrowPad : public QWidget { Q_OBJECT
When lupdate
is run it not only extracts the source texts but it also groups them into contexts. A context is the name of the class in which the source text appears. Thus, in this example, "ArrowPad" is a context: it is the context of the texts in the ArrowPad
class. The Q_OBJECT
macro defines tr(x)
in ArrowPad
like this:
qApp->translate("ArrowPad", x)
Knowing which class each source text appears in enables Qt Linguist to group texts that are logically related together, e.g. all the text in a dialog will have the context of the dialog's class name and will be shown together. This provides useful information for the translator since the context in which text appears may influence how it should be translated. For some translations keyboard accelerators may need to be changed and having all the source texts in a particular context (class) grouped together makes it easier for the translator to perform any accelerator changes without introducing conflicts.
In arrowpad.cpp
we implement the ArrowPad
class.
upButton = new QPushButton(tr("&Up")); downButton = new QPushButton(tr("&Down")); leftButton = new QPushButton(tr("&Left")); rightButton = new QPushButton(tr("&Right"));
We call ArrowPad::tr()
for each button's label since the labels are user-visible text.
class MainWindow : public QMainWindow { Q_OBJECT
In the screenshot above, the whole window is a MainWindow
. This is defined in the mainwindow.h
header file. Here too, we use Q_OBJECT
, so that MainWindow
will become a context in Qt Linguist.
arrowPad = new ArrowPad;
In the implementation of MainWindow
, mainwindow.cpp
, we create an instance of our ArrowPad
class.
exitAct = new QAction(tr("E&xit"), this); exitAct->setShortcuts(QKeySequence::Quit); connect(exitAct, SIGNAL(triggered()), this, SLOT(close()));
We also call MainWindow::tr()
twice, once for the action and once for the shortcut.
Note the use of tr()
to support different keys in other languages. "Ctrl+Q" is a good choice for Quit in English, but a Dutch translator might want to use "Ctrl+A" (for Afsluiten) and a German translator "Strg+E" (for Beenden). When using tr()
for Ctrl key accelerators, the two argument form should be used with the second argument describing the function that the accelerator performs.
Our main()
function is defined in main.cpp
as usual.
QTranslator translator; translator.load(QString("arrowpad_") + locale); app.installTranslator(&translator);
We choose which translation to use according to the current locale. QLocale::system() can be influenced by setting the LANG
environment variable, for example. Notice that the use of a naming convention that incorporates the locale for .qm
message files, (and TS files), makes it easy to implement choosing the translation file according to locale.
If there is no QM message file for the locale chosen the original source text will be used and no error raised.
Translating to French and Dutch
We'll begin by translating the example application into French. Start Qt Linguist with arrowpad_fr.ts
. You should get the seven source texts ("&Up", "&Left", etc.) grouped in two contexts ("ArrowPad" and "MainWindow").
Now, enter the following translations:
ArrowPad
- &Up - &Haut
- &Left - &Gauche
- &Right - &Droite
- &Down - &Bas
MainWindow
- E&xit - &Quitter
- Ctrl+Q - Ctrl+Q
- &File - &Fichier
It's quickest to press Alt+D (which clicks the Done & Next button) after typing each translation, since this marks the translation as done and moves on to the next source text.
Save the file and do the same for Dutch working with arrowpad_nl.ts
:
ArrowPad
- &Up - &Omhoog
- &Left - &Links
- &Right - &Rechts
- &Down - Omlaa&g
MainWindow
- E&xit - &Afsluiten
- Ctrl+Q - Ctrl+A
- File - &Bestand
We have to convert the tt1_fr.ts
and tt1_nl.ts
translation source files into QM files. We could use Qt Linguist as we've done before; however using the command line tool lrelease
ensures that all the QM files for the application are created without us having to remember to load and File|Release each one individually from Qt Linguist.
Type
lrelease arrowpad.pro
This should create both arrowpad_fr.qm
and arrowpad_nl.qm
. Set the LANG
environment variable to fr
. In Unix, one of the two following commands should work
export LANG=fr setenv LANG fr
In Windows, either modify autoexec.bat
or run
set LANG=fr
When you run the program, you should now see the French version:
Try the same with Dutch, by setting LANG=nl
. Now the Dutch version should appear:
Exercises
Mark one of the translations in Qt Linguist as not done, i.e. by unchecking the "done" checkbox; run lupdate
, then lrelease
, then the example. What effect did this change have?
Set LANG=fr_CA
(French Canada) and run the example program again. Explain why the result is the same as with LANG=fr
.
Change one of the accelerators in the Dutch translation to eliminate the conflict between &Bestand and &Boven.
Files:


Read in lines from a text file
Sometimes you want to take an action on every line in a text file. Several of these scripts create lists of all the files they have to act on. This isn't the fastest way to do things, but it can simplify things somewhat, and lets you examine the list for yourself if you need to. These scripts use the read command inside of a "while" loop. Let's say we've created a temp file containing a list of all the files we need to act on, and now we want to print the MIME type for each of those files to the screen.
{
while read ThisLine; do
Type=`catattr BEOS:TYPE $ThisLine`
echo "The filetype of $ThisLine is $Type"
done
} < /tmp/filelist
filelist is fed into the whole block, and the read command understands that it should read just one line at a time. Always close a while block with "done."
top
Define and invoke functions
Sometimes you want to create "routines," or blocks of commands, that you can invoke from elsewhere in your script. Use this format:
DoPage(){
[command one]
[command two]
[command three
}
This function, called DoPage, will not run automatically. To make it run, just type "DoPage." Functions can be invoked as subroutines from within other functions. For example, if you examine the SimpleTest script, you'll see that it has two major functions: IndexPage and DoPage. It starts running IndexPage. When it creates a link to another page, it jumps to the DoPage function and runs that, which creates the page that's just been linked to. The order of functions in a script is not important, but you cannot invoke a function that hasn't been read in yet. A good way to organize a script based on functions is to put them all at the top, then invoke them in order at the bottom of the script. For example:
Prep(){
[command one]
[command two]
}
IndexPage(){
[command a]
[command b]
DoPage
[command c]
}
DoPage(){
[command I]
[command II]
[command III]
}
### Now run them:
Prep
IndexPage


A simple, modern, framework-independent, well-tested, unobtrusive, notification system.
Samples (click to view):humane("Welcome Back");
humane("Record 392 has been updated");
humane("
Invalid Username and/or Password
");
humane.timeout = (number of milliseconds);
Sets the delay before a message fades out.
Try It: 2000 (2s - default) 5000 (5s) 500 (0.5s)
humane.waitForMove = (true|false);
Wait for mouse, or keyboard action to be taken before clearing message (after timeout)
Try It: true (default) false
Uses CSS Transitions where available otherwise falls back to JS animation, degrades gracefully.


OUR VIEW: Trudeau’s lost opportunity in Surrey – again
Cabinet has five MPs from the West while Ontario gets 17, Quebec gets 11, and Atlantic provinces, four
Considering the Liberal Party of Canada lost two local MP seats to the Conservatives in the Oct. 21 federal election, Prime Minister Justin Trudeau would have been wise to at least field-dress his party’s recent bleed in Surrey by appointing one of this rapidly growing city’s three remaining Liberal MPs to his cabinet.
But he did not. Sukh Dhaliwal (Surrey Newton), Ken Hardie (Fleetwood-Port Kells) and Randeep Sarai (Surrey Centre) remain on the backbenches after the PM revealed his new 37-minister cabinet on Wednesday.
READ ALSO: Trudeau to take sober approach to unveiling new cabinet for minority mandate
Politically speaking, it was close to an electoral miracle, depending on your point of view, that the so-called Natural Governing Party had in the first place occupied all five of Surrey’s seats heading into the election.
While the Liberals enjoy that NGP moniker in some circles nationally, for decades the party had struggled to elect a lone Liberal MP in Surrey, a city prone to elect either small-c conservative MPs – be they Reform, Canadian Alliance, Conservative or even an Independent – or an occasional NDP MP, at least in the north ridings.
This – coupled with the fact that Trudeau desperately needs to throw the West a bone considering his party was shut out in Alberta and Saskatchewan – makes us wonder why he appointed only four B.C. Liberal MPs to his new cabinet and only one MP from Manitoba (Dan Vandal, Saint Boniface-Saint Vital).
All told, only five ministers in Trudeau’s new cabinet hail from the West while Ontario gets 17, Quebec gets 11, and the Atlantic provinces get four.
It will be interesting to see how this lost opportunity plays out.
– Now-Leader


Arizona tribes oppose plan to dam Colorado River tributary
FLAGSTAFF, Ariz. (AP) - Native American tribes in northern Arizona overwhelmingly oppose proposals to dam the Little Colorado River for hydropower.
Phoenix-based Pumped Hydro Storage company is seeking preliminary permits from the federal government to study the sites east of Grand Canyon National Park.
Company manager Steve Irwin has touted the potential economic benefits, including paved roads, tourism and jobs.
The Navajo Nation owns the land and the projects won’t move forward without the tribe’s OK.
The tribe wrote in comments posted online Monday that the projects could negatively impact the tribe’s land, water, wildlife and cultural resources.
The Navajo community closest to the proposed projects already has asked the Federal Energy Regulatory Commission to deny the permits.
The Hopi, Hualapai and Havasupai tribes say they’re also concerned about the possible impacts.
Sign up for Daily Newsletters
Copyright © 2019 The Washington Times, LLC.
Please read our comment policy before commenting.


Google Earth Enterprise Documentation Home | Release notes
Release notes: GEE 5.0.1
This document includes the following information about the Google Earth Enterprise 5.0.1 release:
Overview
GEE 5.0.1 is an incremental release of GEE 5.0. It includes library updates and fixes to several bugs.
Supported Platforms
- Red Hat Enterprise Linux versions 6.0 to 6.5, including the most recent security patches
- CentOS 6.5
- Ubuntu 10.04 and 12.04 LTS
Google Earth Enterprise 5.0.1 is compatible with Google Earth Enterprise Client (EC) and Plugin versions 7.0.1 - <IP_ADDRESS>8 for Windows, Mac, and Linux.
Library updates
- Updated to version 3.14. See change release information.
GDAL:
- Updated to version 1.10.1. See GDAL Release 1.10.1 News for information.
Apache HTTP Server:
- Updated to version 2.2.27. See Apache HTTP Server Project for information.
Libattr extended file attributes:
- Updated from libattr 2.4.46 to version 2.4.47.
Openssl update to address vulnerabilities:
- Updated openssl from v0.9.8r to v0.9.8y.
Known Issues
Resolved Issues
| Number | Description | Resolution |
|---|---|---|
| 13010755 | You can add the Google Base Map as imagery for map databases but viewing a map database in a browser currently requires creating and editing a copy of /opt/google/gehttpd/htdocs/maps_google.html , one HTML file for each map published. |
Fixed. No editing of maps_google.html required. Note that resolution allows using only Google Base Map or the Google Base Map and an imagery layer. See Using Google Base Map. |
| 14357181 | When running the Cutter command, the Apache server connection may not close correctly after the background process has completely executed, leading to a build failure of the portable globe or map. | Fixed. The Apache server now closes the connection appropriately after the cutting process has completed. |
| 14105700 | Portable globes and maps may become unregistered and unpublished from GEE Server when the /globes directory becomes temporarily unavailable. |
Fixed. If you have registered and/or published portable files that are no longer available in your /globes directory, use the geserveradmin --portable_cleanup command to clean up portable globes registration information. The cleanup unregisters/unpublishes portable globes or maps that have been removed from your /globes directory. |
| 11315730 | Uninstalling GEE Fusion 5.x prevents GEE Server 5.x from running; likewise uninstalling GEE Server 5.x prevents GEE Fusion 5.x from running. | Fixed. Uninstalling either Fusion or GEE Server does not impact the running of the remaining installed component. However, do make sure that you continue to use the same release versions of Fusion and GEE Server to avoid any compatibility issues. |
| 13232808 | Portable globes (*.glc ) without a timestamp in the Manage portable dialog may not be registered with GEE Server. |
Fixed. |
| 15274582 | In rare circumstances, tiles may be missing from vector data in 2D portable files. | Fixed. |
| 14463855 |
GEE Server fails when publishing to different publish points that are only distinguished by case, such as "Google" and "google." |
Fixed. In GEE Server, when publishing a database or portable, the publish point you specify is now case insensitive. Upper and lower case are not differentiated. Make sure you specify unique publish point path names. |
| 3941714 |
The GLC assembly tool doesn't clean up files correctly after a composite globe or map is created |
Fixed. |
| 13941482 |
The GLC assembly tool uses the |
Fixed. GLC assembly now uses the /opt/google/gehttpd/htdocs directory forcomposite file processing, that is, the same volume as your Portable globes directory. |
| 13931811 |
When deleting a layer and rebuilding a |
Fixed. |
| 13916427 |
The display of the build progress window of the GLC assembly tool is delayed when clicking Assemble Glc. |
Fixed. |
| 13916422 |
The pan and zoom controls in the Cutter tool window are partially obscured by the Create new offline map panel. |
Fixed. The pan and zoom controls are now hidden. |
| 12239387 | Historical imagery from 5.x-generated imagery projects display incorrectly. | Fixed. Support added for displaying historical imagery from 5.x -generated imagery projects. There is still one remaining issue which requires turning off historical imagery in order to see the most current database in the current version of Google Earth EC. See Known Issues. |
| 13889571 |
When entering subsequent search parameters in a search tab in Google Earth EC, search results from previous query parameters persist in subsequent searches. |
Fixed. |
| 13584831 |
Search parameters that include quotes are not supported. |
Fixed. Note that the comma delimiter cannot be quoted, so the workaround is "38","-122.2", not "38, -122.2". Just quoting either the latitude or the longitude will also work. |
| 13498453 |
When clicking on an item in search results in Google Earth EC that include the FlyToSpot query parameter, a javascript error may occur. |
Fixed. |
| 13609551 |
The Push option available in the context menu when clicking on a database asset that has no valid versions. |
Fixed. |
| 13680266 |
When clicking on a search result that returns a single item in Google Earth EC, a javascript error may occur. |
Fixed. Limits the search bounds
when only one search result is returned and prevents the zoom level from exceeding level 17 for 2D and 3D databases. |
| 11352561 |
There is no option to set a suggestion for a top-level search, typically POI search, in the Publish dialog. |
Fixed. Added a text field to set "suggestion" for top-level search to enable override of default suggestion of "Point of interest" for example, and option to set it to an empty string. |
| 1115030 |
Uninstalling Fusion or Server from |
Fixed. |
| 13459510 | Publishing to the same target in GEE Server may unpublish the database. | Fixed. |
| 12362796 | Databases may disappear from GEE Server after non-use over a period of several days. | Fixed. |
| 12891539 | Search service incorrectly handles UTF-8 encoding query for 2D maps. | Fixed. |
| 12995368 | Missing interface control for setting polygon resolution in the GEE Server Cutter tool. | Fixed by adding the Advanced
option in the GEE Server Cutter tool to set the polygon resolution. See Creating portable globes and maps (5.0). |
| 12981516 | Limited support of UTF-8 encoded queries for geplaces search. |
Fixed. Improved the support of UTF-8 encoded queries for geplaces search, for examplecities . |
| 11715339 | The Preview option in the GEE Server Admin console Databases window fails to display any preview for Fusion 3D databases. | Fixed /opt/google/gehttp/htdocs to point to the correct publish point. |
| 12671863 | Support flyToFirstElement as additional query parameter for the search services. See Create Search Tabs. | Fixed. |
| 8115171 | Document Unable to make reservation error msg. | Fixed. |
| 8114492 | Document Unable to find a suitable resource provider error msg. | Fixed. |
| 11051993 | In certain cases, if a globe is corrupt or permissions are incorrectly set, the GEE Server will crash. | Fix returns more information about damaged globes. |
| 12371493 | Some databases that were not successfully published still appear in the GEE Server admin page. | Fix introduces better error checking. |
| 11435585 | Changing the port of Earth Server breaks GEE Server admin commands. | Fix adds port check to match Apache server. |
| 9765322 | Vector polygons are rendered in the wrong location in certain cases. | Fixed in the polygon pipeline. |
| 7737928 | Cannot build the tutorial SF Terrain project without including WorldTopography terrain resource. | Fixed. |
| 11254639 | KML template should have no references to www.google.com. | Fixed. |
| 11134962 | Horizontal black lines appear at tile boundaries. | Fix in the imagery processing pipeline. |
| 11022364 | Issues Installing 5.x on top of 4.4. | Fixed installer to improve upgrade process. |
| 7442639 | GEE supports only one field per custom Search tab in EC 6.2 and later. |
Fixed. The 5.0.1 release supports
|