Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
IN THE HIGH COURT OF UTTARAKHAND AT NAINITAL Writ Petition (PIL) No. 117 of 2019 With Misc. Application with Counter Affidavit No.13868 of 2019 Vivek Shukla .......Petitioner Versus Muni Chidanand & others .......Respondents Mr. Vivek Shukla, petitioner, in-person. Mr. Vikas Pande, Standing Counsel for the State. Mr. Aditya Pratap Singh, Advocate for the respondent no.6. Coram: Hon'ble Ramesh Ranganathan, C.J. Hon'ble Alok Kumar Verma, J.
Misc. application is allowed and the counter-affidavit, filed on behalf of the seventh respondent, is taken on record.
2. In the counter-affidavit by the Executive Engineer (Irrigation Division) dated 12.10.2019 it is stated that the land (said to be in the possession of the first respondent) belongs to the Revenue Department; further construction work of the wall in question has been stopped by issuing notice dated 22.08.2019, to the Manager of the first respondent, by the Irrigation Department; and since the land belongs to the Revenue Department, all proceedings relating to demolition, if any, is to be carried out by the Revenue Department.
3. Enclosed to the counter-affidavit is a notice dated 22.08.2019, calling upon the Manager of the Parmarth Niketan Trust to remove the encroachment within three days. The three day period, stipulated in the notice dated 22.08.2019, expired on 25.08.2019 nearly three months ago. Further, this notice dated 22.08.2019 is enclosed along with the counter-affidavit dated 12.10.2019, which was filed more than a month and a half after the three day notice period expired on 25.08.2019 and, yet, the counter-affidavit dated 12.10.2019 is silent as to what action the Irrigation Department has taken to remove the encroachment. Since the Executive Engineer (Irrigation) states that the land belongs to the Revenue Department, and the demolition exercise has to be undertaken by them, we consider it appropriate to suo-motu implead the Secretary, Revenue, Government of Uttarakhand as the eighth respondent in the Writ Petition.
24. The District Magistrate, who is the in-charge of the revenue administration of Pauri Garhwal district, has been arrayed as the second respondent in the Writ Petition; and, since government land would come under his control, he is obligated to cause an inquiry and submit a report to this Court as to whether land, belonging to the Revenue Department, has been encroached upon by the first respondent; and if so, what action has been taken by the State Government/District Administration to remove such encroachments. The seventh respondent-Executive Engineer (Irrigation) shall also state, by way of an affidavit to be filed before the next date of hearing, as to what action he has taken, pursuant to the notice issued by him on 22.08.2019 to the Manager of the Parmarth Niketan Trust, though the period stipulated therein expired on 25.08.2019 nearly three months ago.
5. In its counter-affidavit, the Uttarakhand Environment Protection and Pollution Control Board states that the first respondent has not obtained consent to establish and/or consent to operate from the Uttarakhand Environment Protection and Pollution Control Board under the Water (Prevention and Control of Pollution) Act, 1974 and the Air (Prevention and Control of Pollution) Act. 1981, as amended, as applicable.
6. What is, however, not stated in the counter-affidavit is whether or not the first respondent was required to obtain consent to establish and consent to operate. Mr. Aditya Pratap Singh, learned Standing Counsel appearing for the Uttarakhand Environment Protection and Pollution Control Board, would submit that every establishment, which has more than twenty rooms, can only operate the establishment with the prior consent of the Uttarakhand Environment Protection and Pollution Control Board; and, if the allegations of the petitioner are true, the first respondent must then be held to be carrying on operations, though he could not have done so without obtaining prior approval of the Board.
7. Whether or not twenty rooms are being operated in the said establishment is a question of fact which the Uttarakhand Environment Protection and Pollution Control Board is required to ascertain. While Mr. Vivek Shukla, petitioner in-person, states that there are more than hundred rooms, we do not wish to proceed on the basis of these allegations alone and, instead, consider it appropriate to direct the Uttarakhand Environment Protection and Pollution 3 Control Board to cause an inspection of the premises forthwith, and to submit a report to this Court latest by 27.11.2019. In case, the first respondent is found to have violated the Water (Prevention and Control of Pollution) Act, 1974 and the Air (Prevention and Control of Pollution) Act. 1981, the report shall also state as to what action the Board intends taking against the first respondent for such alleged violations.
8. The District Magistrate, Pauri Garhwal shall also cause an inspection forthwith of the said premises, and submit a report to this Court latest by 29.11.2019 as to whether or not the first respondent has encroached upon revenue land belonging to the State Government; and, if so, what action is proposed to be taken by them in this regard.
9. Post on 02.12.2019 in the daily list immediately after 'fresh admission matters'. Both the reports of the District Magistrate, Pauri Garhwal and the Member Secretary, Uttarakhand Environment Protection and Pollution Control Board shall be placed before us on that date.
10. The Executive Engineer (Irrigation) shall also explain, by way of an affidavit to be filed before 02.12.2019, as to what action he has taken pursuant to the notice issued by him on 22.08.2019.
11. Supplementary/rejoinder affidavit, if any, in the meanwhile.
12. Let a certified copy of this order be furnished to the learned counsel for the parties, today itself, on payment of the prescribed charges.
(Alok Kumar Verma, J.) (Ramesh Ranganathan, C. J.) 22.11.2019 22.11.2019 NISHANT


--- layout: tweet ---
I'm so tired today, <fill in joke, metaphor, yawning>
9/10/2009, 9:39:42 AM
Favs: 0
Retweets: 0


David B Steffelbauer
Researcher at Delft University of Technology.
Gebouw 23, Office 4.79
Stevinweg 1
2628 CN Delft, Netherlands
I am a Marie Skłodowska Curie Fellow of the LEaDing Fellows PostDoc Programme at the Water Management Department of Delft University of Technology and at LIACS (Leiden University’s Institute of Advanced Computer Science).
My research interest is located in the interdisciplinary field of hydroinformatics. I envision my research to contribute in solving urgent water related problems by developing innovative methods and algorithms that utilize multi-sensor data and help to increase the total efficiency of urban water systems. My main research interests lie in understanding (i) how urban water systems behave under failures and (ii) how to prevent such failures in advance.
I studied physics at Graz University of Technology and specialized during my studies on theoretical and computational physics with a thesis in the field of quantum many body theory entitled “Andreev-reflection in one-dimensional quantum systems” and supervised by Prof. Hans Gerd Evertz.
After my studies in Physics, I switched my research field to Civil Engineering. I recently completed my PhD under supervision of Prof. Daniela Fuchs-Hanusch at the Institute of Urban Water Management at TU Graz. My thesis focussed on model-based leak localisation in water distribution systems and designing optimal sensor placement algorithms beyond state-of-the-art through incorporating uncertainties.
news
| Sep 10, 2018 | First day of my fellowship at TU Delft. Super excited! |


Harry and Meghan ‘have told the Queen they won't be spending Archie’s first Christmas with her’
Royal experts say Her Majesty could be a "little hurt"
by Nancy BrownThe Duke and Duchess of Sussex have reportedly told the Queen that they won't be spending Christmas with the royal family at Sandringham.
The couple were originally due to head to the States with son Archie for a six-week break from the limelight.
It was thought they would spend Archie's first Thanksgiving in his mother's homeland, before heading back to his father's for his first Christmas.
However, instead it's claimed that the couple will stay in Los Angeles and enjoy Christmas with Meghan's mother Doria Ragland.
Read more: Holly Willoughby cuts a stylish figure on the ITV Palooza red carpet
Harry has always spent Christmas at Sandringham, except from 2012 when he was in Afghanistan.
A source told The Sun the pair have declined the Queen's invite to her Norfolk estate.
"They need some time away to recharge and decide their plans for next year," they said.
Read more: Abbey Clancy shares the secrets of her sensational figure
Royal biographer Ingrid Seward added that Christmas at Sandringham can be "quite stressful" and the couple may not want to go with Archie at such a young age.
She said: "I think it’s sad they don’t want to be part of the family gathering, particularly now the Queen and the Duke of Edinburgh are in their dotage."
Ingrid also revealed that Harry's grandmother may be upset that he hasn't decided to spend the festive season with his family, but her "stiff upper lip" will stop her from showing it.
She added: "The Queen might be a little hurt but she’s far too gracious to ever let it show or be known."
Earlier this week it was reported that Harry and Meghan were considering spending the festive season in Los Angeles.
A source told Hello!: "It's been a hectic year and they are ready to have some downtime."
The news will do little to heal reports of a rift between Harry and his brother Prince William.
Head to our Facebook page @EntertainmentDailyFix and let us know what you think of our story.


--- layout: page title: About Me description: background: '/img/bg-about.jpg' ---
Hi, I am Ruo Ning (Nancy) Qiu, a forth-year undergraduate student at the University of Toronto. I am currently pursuing a specialist in Math & its Application in Teaching with double minor in Statistics and Computer Science.
Currently, I am exploring my research interests in mathematics (stochastic processes & dynamical systems) and mathematics education. I really enjoy teaching what I have learned in mathematics to others and discussing teaching methods with my peers.
In my spare times, I like to fold origami, crochet/knit things, and capture memories with phone photography.


Openfire Plugin Developer Guide
Introduction
Plugins enhance the functionality of Openfire. This document is a developer's guide for creating plugins.
The plugin development is based on Apache Maven.
Topics that are covered in this document:
What is Maven?
Maven is a project management tool which can manage the complete building life cycle. Maven simplifies and standardizes the project build process. by handling compilation, testing, library dependency, distribution, documentation and team collaboration. The Maven developers claim that Maven is more than just a build tool. We can think of Maven as a build tool with more features. Maven provides developers ways to manage project (Builds, Test, Documentation, Reporting, Dependencies, Releases, Distribution, Mailing List).
Structure of a Plugin
Plugins live in the plugins
directory of openfireHome
. When a plugin
is deployed as a JAR or WAR file, it is automatically expanded into a directory. The files in a
plugin directory are as follows:
The web
directory exists for plugins that need to add content to the Openfire Admin Console.
Further details are below.
The plugin.xml
file specifies the main Plugin class. A sample
file might look like the following:
The meta-data fields that can be set in the plugin.xml file:
- name
- the name of the plugin.
- description
- the description of the plugin.
- author
- the author of the plugin.
- version
- the version of the plugin.
- date
- the date the plugin was released. The date must be in the form yyyy-MM-dd, such as 2006-07-21.
- url
- a URL where additional information about the plugin is available.
- minServerVersion
- the minimum version of Openfire required to run the plugin (supported by Openfire 2.1.2 and later). If the server version is less than the required value, the plugin will not be started.
- priorToServerVersion
- the server version up, but not including, on which this plugin can run.
- minJavaVersion
- the minimum Java specification version the plugin needs to run.
- databaseKey
- if the plugin requires it's own database tables, the databaseKey element should be set with a schema key
name (often the same name as the plugin). Database schema files for each supported database should then
be placed in the
database
directory of the plugin. For example, given the key "foo", schema files would be called "foo_mysql.sql", "foo_oracle.sql", etc. We recommend that you prefix your tables with "of" (openfire) to avoid conflicts with possible other applications installed in the same database. The scripts should make an entry into the ofVersion table using the key so that schema version information can be tracked, e.g.:INSERT INTO ofVersion (name, version) VALUES ('foo', 0);
- databaseVersion
- the database schema version (if a database schema is defined). New plugins with a database schema should
start at version 0. If future versions of the plugin require updates to the schema, those updates can be
defined by creating sub-directories in the
database/upgrade
directory for each version number. For example, the directoriesdatabase/upgrade/1
anddatabase/upgrade/2
would contain scripts such as "foo_mysql.sql" and "foo_oracle.sql" that contain the relevant database changes for each version. Each script should update version information in the ofVersion table, e.g.:UPDATE ofVersion set version=1 where name='foo';
- parentPlugin
- the name of the parent plugin (given as "foo" for the "foo.jar" plugin). When a plugin has a parent plugin, the parent plugin's class loader will be used instead of creating a new class loader. This lets plugins work together more closely. A child plugin will not function without its parent present.
- licenseType
- indicates the license agreement that the plugin is governed by. Valid values are:
- "commercial": the plugin is released under a commercial license agreement.
- "gpl": the plugin is released under the GNU Public License (GPL).
- "apache": the plugin is released under the Apache license.
- "internal": the plugin is for internal use at an organization only and will not be re-distributed.
- "other": the plugin is released under a license agreement that doesn't fall into one of the other categories. The license agreement should be details in the plugin's Readme.
Several additional files can be present in the plugin to provide additional information to end-users (all placed in the main plugin directory):
readme.html
- readme file for plugin, which will be displayed to end users.
changelog.html
- Optional changelog file for plugin, which will be displayed to end users.
logo_small.png
- Optional small (16x16) icon associated with the plugin. It can also be a .gif file.
logo_large.png
- Optional large (32x32) icon associated with the plugin. It can also be a .gif file.
Your plugin class must be implement the Plugin
interface from the Openfire API as well as have a default (no argument)
constructor. The Plugin interface has methods for initializing and destroying the plugin.
General Plugin Best Practices
When choosing a package name for your plugin, we recommend that you choose something distinctive to you and/or your organization to help avoid conflicts as much as possible. For example, if everyone went with org.example.PluginName, even if PluginName was different, you might start running into some conflicts here and there between class names. This is especially true when working with clustering.
Modifying the Admin Console
Plugins can add tabs, sections, and pages to the admin console. There are a several steps to accomplishing this:
-
An
<adminconsole />
section must be added to theplugin.xml
file. -
JSP files must be compiled and put into the classpath of the plugin. A
web.xml
file containing the compiled JSP servlet entries must be put into theweb/
directory of the plugin.
Note: the Openfire build script can assist with compiling JSPs and creating the web.xml. This is detailed below. -
Any images required by your JSP pages must live in
web/images/
directory. Only GIF and PNG images are supported.
The <adminconsole />
section of plugin.xml
defines additional tabs, sections
and entries in the Admin Console framework. A sample plugin.xml
file might look like the
following:
In this example, we've defined a new tab "Example", a sidebar section "My Plugin" and two pages:
"My Plugin Admin" and "My Plugin Overview". We've registered my-plugin-admin.jsp
respectively
my-plugin-overview.jsp
as the pages.
By default, the tabs, sidebars and pages will be presented in the order in which they are defined. You can, however, define explicit ordering by adding an "order" attribute to each element. It's numeric value defines order. If no order is specified, the value 0 (zero) is used as a default. In the example above, the items are ordered using this construct. In the admin console, the "My Plugin Overview" page will be presented before the "My Plugin Admin" page, as its 'order' value is lower. If neither item had defined the 'order' attribute, the presentation of both pages would have been reversed (as it would have used to order in which the pages are defined in XML).
You can override existing tabs, sections, and items by using the existing id attribute values in your own
<adminconsole>
definition.
Admin Console Best Practices
There are several best practices to consider when making changes to the Openfire admin console via a plugin. The general theme is that plugins should integrate seamlessly:
- Integrate into existing tabs and sidebar sections whenever possible instead of creating your own. Only create new tabs for very significant new functionality.
- Don't use the word "plugin" in names of tabs, sidebars and items. For example, instead of having an item called "Gateway Plugin", it could be called "Gateway Settings".
- Try to match the UI of the existing admin console in your custom plugin pages.
- There is no need to create an admin console entry to show plugin meta-data. Instead, let Openfire inform the user about which plugins are installed and provide plugin management.
Writing Pages for the Admin Console
Openfire uses the Sitemesh framework to decorate pages in the admin console. A globally-defined decorator is applied to each page in order to render the final output, as in the following diagram:
Creating pages that work with Sitemesh is easy. Simply create valid HTML pages and then use meta tags to send instructions to Sitemesh. When rendering the output, Sitemesh will use the instructions you provide to render the decorator along with any content in the body of your HTML page. The following meta tags can be used:
- pageID
- the ID of the page, which must match an entry in the admin console XML described above. Either a pageID or subPageID must be specified.
- subPageID
- the ID of the sub-page, which must match an entry in the admin console XML described above. Sub-pages are used for administrative actions related to a parent page ID. For example, editing or deleting a particular group. Either a pageID or subPageID must be specified.
- extraParams
- (Optional) extra parameters that should be passed in to the page. For example, on a page to delete a group it might be the ID of the group. Parameters must be URL encoded.
- decorator
- (Optional) overrides the Sitemesh decorator to use for the page. A decorator named
none
is available that will simply render the page without a decorator.
The following HTML snippet demonstrates a valid page:
Using i18n in your Plugins
It's possible to translate your plugin into multiple languages (i18n). To do so, use the following procedure:
- Create a "i18n" directory in the root directory of your plugin.
- Add each resource file using the %[plugin_name]%_i18n "_" language ".properties" naming convention, where [plugin_name] is the name of the plugin directory. See the translator guide for more information about resource bundles.
- Convert Strings in your JSP files to refer to the internationalized keys. For example:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %> <%@ taglib uri="http://java.sun.com/jsp/jstl/fmt" prefix="fmt" %> ... <fmt:message key="some.key.name" />
-
Internationalize Strings in your Java files using the LocaleUtils class:
org.jivesoftware.util.LocaleUtils.getLocalizedString("some.key.name", "[plugin_name]");
-
Internationalize Strings in your plugin.xml file using the ${var} format:
<sidebar id="gateways" name="${plugin.sidebar.name}" description="${plugin.sidebar.description}"> <description>${plugin.description}</description>
Building the plugin
Your plugin project should define a Maven pom.xml file to build plugins. Your plugin can inherit from an Openfire provided parent pom. This can be obtained through Ignite's Maven repository. An example of such a pom file is shown below.
The Maven pom.xml will help you build and develop plugins. It should look for plugin development directories in the following format:
To build the plugin, build the maven 'package' goal. Typically, this is done as such:
mvn clean package
When the build succeeds, the target/
folder in your project will have serveral files. One file
is named PLUGINNAME-openfire-plugin-assembly.jar
. This is the Openfire plugin
Note: Before you provide the plugin jar file to Openfire, it must be renamed! Remove
-heapdump-openfire-plugin-assembly
from the file name. For example: a file named
demo-openfire-plugin-assembly.jar
should be renamed to demo.jar
If you create a src/web/WEB-INF/web.xml file, any servlets registered there will be initialized when the plugin starts up. Only servlet registrations and servlet mappings will be honored from the web.xml file. Note: this feature is implemented by merging your custom web.xml file into the web.xml file generated by the JSP compilation process.
Implementing Your Plugin
Plugins have full access to the Openfire API. This provides a tremendous amount of flexibility for what plugins can accomplish. However, there are several integration points that are the most common:
Register a plugin as a Component.
Components receive all packets addressed to a particular sub-domain. For example,
test_component.example.com
. So, a packet sent to<EMAIL_ADDRESS>would be delivered to the component. Note that the sub-domains defined as components are unrelated to DNS
entries for sub-domains. All XMPP routing at the socket level is done using the primary server domain
(example.com in the example above); sub-domains are only used for routing within the XMPP server.
Register a plugin as an IQHandler
IQ handlers respond to IQ packets with a particular element name and namespace. The following code snippet demonstrates how to register an IQHandler:
Register a plugin as a PacketInterceptor
Register the plugin as a PacketInterceptor to receive all packets being sent through the system and optionally reject them. For example, an interceptor could reject all messages that contained profanity or flag them for review by an administrator.
Persisting settings
You can store persistent plugin settings as Openfire properties using the JiveGlobals.getProperty(String)
and JiveGlobals.setProperty(String, String)
methods. Make your plugin a property listener to
listen for changes to its properties by implementing the org.jivesoftware.util.PropertyEventListener
method. You can register your plugin as a listener using the PropertyEventDispatcher.addListener(PropertyEventListener)
method. Be sure to unregister your plugin as a listener in your plugin's destroyPlugin()
method.
CSRF protection
Admin pages are liable to CSRF attacks. Openfire provides facilities to aid plugin authors to protect against these attacks on their admin pages. To enable CSRF protection:
- Set the plugin.xml
minServerVersion
to 4.5.0 or above as this is when support was added. - Set the plugin.xml
csrfProtectionEnabled
totrue
to enable CSRF protection for the plugin. This will;- Guard against CSRF attacks for all requests to admin pages except GET requests
- Set a servlet request attribute with key "csrf"
- Ensure that GET requests do not modify any settings or change any data as this protection is not enabled for GET requests
- Ensure that any form submitted in the admin page has a field called
csrf
whose value is that defined by the request attribute "csrf" - for example:
<input name="csrf" value="<c:out value="${csrf}"/>" type="hidden">
If a CSRF attack is detected, the admin page will be reloaded (with a simple HTTP GET request) with
the session attribute FlashMessageTag.ERROR_MESSAGE_KEY
set to indicate the problem - it's
therefore advised to include the <admin:FlashMessage/>
at the top of your JSP page.
NOTE: It is still important to ensure that all your output is properly escaped using
<c:out>
tags or the equivalent.
Plugin FAQ
Can I deploy a plugin as a directory instead of a JAR?
No, all plugins must be deployed as JAR or WAR files. When a JAR or WAR is not present for the plugin, Openfire assumes that the file has been deleted and that the users wants to destroy the plugin, so it also deletes the directory.
I've made a change to an existing plugin but can't get it to install when I upload it. Why?
Naming is important. The uploaded JAR must match name with the plugin (i.e. the POM artifactId). For example,
the Monitoring and Archiving Plugin must be uploaded as monitoring.jar
rather than
my_better_monitoring.jar
.
If you're compiling using the maven-assembly-plugin
, be sure to look at the config in the
example plugin.


Annual anomaly scorecard for non-copepod group abundances on the Scotian Shelf sections. The Y values are anomalies from the mean for the reference period,
1999-2010, in standard deviation (sd) units (mean and sd listed at right).
Read more...
Data Source: DFO Canadian Science Advisory Secretariat,
Johnson, C., Devred, E., Casault, B., Head, E., and Spry, J. 2018. Optical, Chemical, and Biological
Oceanographic Conditions on the Scotian Shelf and in the Eastern Gulf of Maine in 2016. DFO Can. Sci.
Advis. Sec. Res. Doc. 2018/017. v + 57 p.;


| Pace (Tempo) |
Slow Fast |
|---|---|
| Emotion Intensity (Arousal) |
Relaxing Intense |
| Joyfulness (Valence) |
Sad Happy |
| Genre |
Best match: , second best match: |
Author: Mu Chen
<EMAIL_ADDRESS>University of Illinois - Urbana Champaign


| System |
Produced/Sold by |
Technology Base |
Major Capabilities |
Major Limitations |
Example Site |
| Drupal |
Dries Buytaert/Drupal.org |
PHP/MySQL |
- Plain installation
- Feature rich
- Forums
- Blogs
- OpenID
- Profiles
- Themes
- Plugins
|
Installation and Modification are not user friendly, Limited Compatibility due to new Features, Inefficient loads |
Drupal Demo |
| Joomla! |
Joomla.org |
PHP |
Easy to Install, Plugin Rich, Heavily Supported, Updated Often, easy Navigation |
Paid Plugins, Higher server load, Not new user friendly, Plugin Cross Compatibility |
Joomla Demo |
| Typo3 |
Typo3.org |
Can be configured for multiple languages |
Modular, Diverse, large library of Extensions, Power Admin tools, wide Content coverage, easy to rollback changes. |
Hard to install and hard to modify, Module options create higher server loads, Admin requires know-how |
Typo3 Demo |
| Quick.Cms |
OpenSolution.org |
PHP/HTML/CSS |
Easy to install and Modify, Intuitive Administration tools, Heavily supported, Efficient and low system requirements |
Smaller selection of plugins and templates, Database design can be inefficient with larger pages, does require knowledge of PHP/CSS/HTML for extensive modifications |
Quick.CMS Demo |
| ExpressionEngine |
ExpressionEngine.com |
Technology Base |
Flexible and Extensive features, Easy to Modify, Quick to learn to make changes, Feature rich, |
Paid Software, does require some prior knowledge of HTML and CSS, can get complex for deeper features. |
ExpressionEngine Demo |


User does not have enough rights to remove the question.
The question cannot be removed because the given skill is assigned to the diagnostic test 1">tests of the following topic, 1">topics, and there are only 2 questions or fewer available for that skill.
Please remove the skill from the above topic 1">topics first, then perform this operation.


A handler implementation that helps you implement sequentially layered protocols using Chains of Responsibility pattern.


Navigation
Home
Menu
Track Order
Contact Us
Grill n Chill

Login

;
Register
Registration
Username:
Password:
Password confirmation:
Phone:
Email:
Submit
Reset
Continue ordering


ImageArea
public enum ImageArea
Undocumented
-
The full image size.
Declaration
Swift
case full
-
The last vertical third.
Declaration
Swift
case bottom
-
The second horizontal third of the last vertical third.
Declaration
Swift
case bottomCenter
-
The first horizontal third of the last vertical third.
Declaration
Swift
case bottomLeft
-
The last horizontal third of the last vertical third.
Declaration
Swift
case bottomRight
-
The second horizontal third of the second vertical third.
Declaration
Swift
case center
-
The first horizontal third of the second vertical third.
Declaration
Swift
case centerLeft
-
The last horizontal third of the second vertical third.
Declaration
Swift
case centerRight
-
A custom area of the image defined by a CGRect.
Declaration
Swift
case custom(rect: CGRect)
-
The second vertical third.
Declaration
Swift
case horizontalCenter
-
The first horizontal third.
Declaration
Swift
case left
-
The last horizontal third.
Declaration
Swift
case right
-
The first vertical third.
Declaration
Swift
case top
-
The second horizontal third of the first vertical third.
Declaration
Swift
case topCenter
-
The first horizontal third of the first vertical third.
Declaration
Swift
case topLeft
-
The last horizontal third of the first vertical third.
Declaration
Swift
case topRight
-
The second horizontal third.
Declaration
Swift
case verticalCenter


The Nobel Prize in Chemistry (Swedish: Nobelpriset i kemi) is awarded annually by the Royal Swedish Academy of Sciences to scientists in the various fields of chemistry. It is one of the five Nobel Prizes established by the 1895 will of Alfred Nobel, who died in 1896. These prizes are awarded for contributions in physics, literature, peace, and physiology or medicine.As dictated by Nobel's will, the award is administered by the Nobel Foundation and awarded by a committee that consists of five members elected by the Royal Swedish Academy of Sciences.[2] The first Nobel Prize in Chemistry was awarded in 1901 to Jacobus Henricus van 't Hoff, of the Netherlands. Each recipient receives a medal, a diploma and a monetary award prize that has varied throughout the years.[3]


Image
public class Image: Misc
The Image
widget displays an image. Various kinds of object can be
displayed as an image; most typically, you would load a Pixbuf
(pixel
buffer
) from a file, and then display that. There’s a initializer to do
this, Image.init(fileName:)
, used as follows:
let image = Image(fileName: "myfile.png")
If the file isn’t loaded successfully, the image will contain a “broken
image” icon similar to that used in many web browsers. If you want to handle
errors in loading the file yourself, for example by displaying an error
message, then load the image with Pixbuf.init(fromFile:)
, then create the
Image
with Image.init(pixbuf:)
.
The image file may contain an animation, if so the Image
will display an
animation (PixbufAnimation
) instead of a static image.
Image
is a subclass of Misc
, which implies that you can align it
(center, left, right) and add padding to it, using Misc
methods.
Image
is a “no window” widget (has no Window
of its own), so by default
does not receive events. If you want to receive events on the image, such as
button clicks, place the image inside a EventBox
, then connect to the
event signals on the event box.
-
Creates a new empty
Image
widget.Declaration
Swift
public convenience init()
-
Creates a new
Image
displaying the filefileName
. If the file isn’t found or can’t be loaded, the resultingImage
will display a “broken image” icon. It always returns a validImage
widget.If the file contains an animation, the image will contain an animation.
If you need to detect failures to load the file, use
Pixbuf.init(fromFile:)
to load the file yourself, then create theImage
from the pixbuf. (Or for animations, usePixbufAnimation.init(fromFile:)
.The storage type (
Image.storageType
) of the returned image is not defined, it will be whatever is appropriate for displaying the file.Parameter
Parameter filename: a filename.Declaration
Swift
public convenience init(fileName: String)
Parameters
filename
a filename.
-
Creates a
Image
displaying an icon from the current icon theme. If the icon name isn’t known, a “broken image” icon will be displayed instead. If the current icon theme is changed, the icon will be updated appropriately.Parameter
Parameter iconName: an icon nameParameter
Parameter size: a stock icon size.Declaration
Swift
public convenience init(iconName: String, iconSize size: IconSize)
Parameters
iconName
an icon name
size
a stock icon size.
-
Creates a new
Image
displaying the resource filepath
. If the file isn’t found or can’t be loaded, the resultingImage
will display a “broken image” icon. It always returns a validImage
widget.If the file contains an animation, the image will contain an animation.
If you need to detect failures to load the file, use
Pixbuf.init(fromFile:)
to load the file yourself, then create theImage
from the pixbuf. (Or for animations, usePixbufAnimation.init(fromFile:)
.The storage type (
Image.storageType
) of the returned image is not defined, it will be whatever is appropriate for displaying the file.Parameter
Parameter path: a resource pathDeclaration
Swift
public convenience init(resourcePath path: String)
Parameters
path
a resource path
-
Undocumented
Declaration
Swift
public class Image: Misc
-
See `Image.init(fileName:) for details.
Parameter
Parameter fileName: a filename ornil
.Declaration
Swift
public func setFrom(fileName: String?)
Parameters
fileName
a filename or
nil
. -
See `Image.init(iconName:iconSize:) for details.
Parameter
Parameter iconName: an icon nameParameter
Parameter size: an icon size.Declaration
Swift
public func setFrom(iconName: String, iconSize size: IconSize)
Parameters
iconName
an icon name
size
an icon size.
-
See
Image.init(resourcePath:)
for details.Parameter
Parameter path: a resource pathDeclaration
Swift
public func setFrom(resourcePath path: String)
Parameters
path
a resource path
-
Resets the image to be empty.
Declaration
Swift
public func clear()
-
The pixel size to use for named icons. If the pixel size is value != -1, it is used instead of the icon size set by
Image.setFrom(iconName:iconSize:)
.Declaration
Swift
public var pixelSize: Int


Collection module.
MIT. See LICENSE for full details.
A generic first-in-first-out (FIFO) queue implementation.
| T | The type stored in the queue. |
auto queue = new Queue!(string); queue.enqueue("Foo"); queue.enqueue("Bar"); queue.enqueue("Baz"); assert(!queue.empty); assert(queue.count == 3); assert(queue.contains("Bar")); assert(queue.peek() == "Foo"); assert(queue.dequeue() == "Foo"); assert(queue.dequeue() == "Bar"); queue.clear(); assert(!queue.contains("Baz")); assert(queue.empty); assert(queue.count == 0);
Construct a new queue.
By default the queue is allocated enough memory for 10,000 items. If more items are added, the queue can grow by doubling its allocation, ad infinitum. If the items within reduce to only use half of the current allocation the queue will half it. The queue will never shrink below the minimum capacity amount.
| size_t minCapacity | The minimum number of items to allocate space for. The queue will never shrink below this allocation. |
| AssertError | If the minimum allocated size is not big enough for at least one item. |
| OutOfMemoryError | If memory allocation fails. |
Get the number of items stored in the queue.
The number of items stored in the queue.
Test if the queue is empty or not.
true if the queue is empty, false if not.
Add an item to the queue.
This method reallocates and doubles the memory used by the queue if no more items can be stored in available memory.
| T item | The item to push onto the queue. |
| OutOfMemoryError | If memory reallocation fails. |
Return the front item in the queue but don't remove it.
The front item in the queue.
| AssertError | If the queue is empty. |
Remove and return the front item in the queue.
This method reallocates the memory used by the queue, halfing it if half will adequately hold all the items.
The front item in the queue.
| AssertError | If the queue is empty. |
| OutOfMemoryError | If memory reallocation fails. |
Check if a value is contained in the queue.
This is a simple linear search and can take quite some time with large queues.
| T item | The item to find in the queue. |
true if the item is found on the queue, false if not.
Clears the queue.
This method reallocates the memory used by the queue to the minimum size if more is currently allocated.
| OutOfMemoryError | If memory reallocation fails. |


Add Requirement
List Requirements
Search Requirements
Add Candidate
List Candidates
Search Candidates
Load Email
List Email
Search Email
Load Email
UserName:
Password:
Host:
pop.gmail.com
Port:
995
Load Email


It may be convenient to use this procedure in combination with SPSSINC SPLIT DATASET, which can break up a dataset according to the values of a splitting variable.
Input Data Files Specified by Wildcard
Expression. Choose a directory to process and, optionally,
specify a file pattern. For example,
c:\mydata\x*.sav
would process all the sav files in directory c:\mydata whose
names start with the letter x.
• If no file-name expression is given,*.sav is assumed.
• You must choose either this option or the following Input Data option but not both.
Input Data Files Specified in a File. Process all the files listed in the specified file. The SPSSINC SPLIT DATASET command can produce a file in the correct format.
• You must choose either this option or the preceding Input Data option but not both.
Syntax File to Execute for Each Data File. The syntax file will be invoked for each input dataset. It should read the file and carry out any desired operations. File handles and macros are defined to refer to the input file and various output locations. The file handles are as follows.
• For a SAV file you could read the data with
the command
GET FILE="JOB_INPUTFILE".
• Macros are defined with these same names except starting with "!". Two additional macros are defined.
The text !JOB or JOB is replaced by the root name specified in the root-name control.
• Macro text is quoted. Here is an example of
code that could be used to export Viewer contents to the
specified Viewer directory using the name of the data file with
extension .xls.
DEFINE !out ()
!QUOTE(!CONCAT(!EVAL(!UNQUOTE(!JOB_VIEWERDIR)), "/",
!EVAL(!unquote(!JOB_DATAFILEROOT)), ".xls"))
!ENDDEFINE.
OUTPUT EXPORT /XLS DOCUMENTFILE =!out.
Directory for Output Data Files. If specified, for each dataset the data file will be written as an .sav file to that directory after the syntax completes. This can be useful when carrying out transformations for a set of files. You can, of course, leave this field blank and write any data file output you choose. The JOB_OUTPUTDATADIR file handle or !JOB_OUTPUTDATADIR macro identifies the data output location specified in this command
Viewer Output. Viewer output can be saved either in a separate file for each data file or as a single file for the entire job. Select the appropriate radio button, and enter either a directory name or a file specification. If you choose to write a single file but enter only a directory in the following control, the file will be named VIEWER.SPV. The Browse button for that control only allows a directory to be specified, but you can type in a file name.
Write Job Log to File. Specify a file for the job log. The log lists the files processed and written by the procedure, each with a time stamp.
• Operations carried out by the syntax file are not recorded.
• If a serious error occurs in processing a file, there will be an error entry in the log.
Syntax to Execute before Processing. You can specify a syntax file that will be executed once before input file processing starts. Macros and file handles will be defined as for the first file in the processing list. If a serious error occurs, processing is stopped.
Syntax to Execute after All Processing. You can specify a syntax file that will be executed once after all the input files are processed. Macros and file handles will be defined as for the last file in the processing list.
Log File Mode. Choose whether the log entries for the job are appended to an existing file or replace the contents.
Data File Processing after Each Step. Choose Close to have all datasets closed after each iteration of input file processing. Leaving datasets open after each step is useful if you are combining many datasets into one. The final dataset could be saved after this command completes.
Error Handling. If an error occurs, you can choose whether to continue processing with the next data file or to stop processing any further files. If possible, the output data and Viewer files will still be written for the data file that caused the error even if stopping is specified.
Root name for macros and file handles. By default, the file handles and macros defined have the prefix JOB and !JOB, respectively followed by an underscore. You can specify a different prefix in place of JOB. The prefix will have ! prepended to it for macros.!.
Use this subdialog box to define your own macros that can be used in the syntax file. You can define up to five macros named !PARM1 to !PARM5 whose values will be ordinary syntax or variable names, and up to five macros named !QPARM1 to !QPARM5 whose values will be quoted literal strings. The quoted string are useful for titles or string expressions in transformations.
Macros Where Values Are Unquoted. Enter any macro text that represents any SPSS syntax that should appear without quotation marks.
Macros Where Value Is a Quoted Literal. Enter any macro text that represents SPSS syntax that should appear in quotation marks such as a title, label, or file name.
• Use single quotes (') if you need to quote literals in the definition. The generated macro text will be enclosed in double quotes(").
SELECT IF !PARM1 EQ !QPARM1.
FREQUENCIES !PARM1.
• Set the Error Handling parameter to Continue with next file since if no cases are selected, the FREQUENCIES command will generate an error. (OMS could be used to suppress the resulting Warnings table.)
• Write the Viewer output to a single file for ease of viewing the result.
In order to use a file to specify the files that should be processed, create a file with one name per line including the path to the file. The name must be enclosed in double quotes ("). Anything following on the line is ignored. Blank lines and lines starting with # are ignored.
© Copyright IBM Corp. 1989, 2013


Santa set to open magical Christmas grotto at Notcutts
by Gemma JarvisSanta has come early and will be stopping off at Notcutts Garden Centre in Woodbridge this weekend to kick off the festive season.
Usually transported by reindeers and a sleigh, he will be arriving by limousine to open the magical grotto specially created inside the centre.
Treat the children to a meet and greet with Santa where they can enjoy the enchanted winter grotto and receive a special gift from the man himself.
Darren Brooks, general manager at Notcutts Woodbridge, said: "Christmas is a magical time of year at Notcutts and, while our garden centre is glittering with lights and decorations, we will also have a host of festive activities for the whole family to enjoy all season.
"Starting with Santa's big arrival on November 17, the free event is a fantastic way to get into the Christmas spirit.
"We hope lots of local families will head down to Notcutts to celebrate the magic with us."
To book, call 01394 445 400 or go to the Notcutts website.


SOLVER.GET macro
Returns information about current settings for Solver. The settings are specified in the Solver Parameters and Solver Options dialog boxes.
If this function is not available, you must install the Solver add-in.
Syntax
SOLVER.GET(type_num, sheet_name)
Type_num is a number specifying the type of information you want.
The following settings are specified in the Solver Parameters dialog box.
Type_Num
|
Returns
|
2
|
A number corresponding to the Equal To option
1 = Max
2 = Min
3 = Value of
|
3
|
The value in the Value Of box
|
4
|
The reference (as a multiple reference if necessary) in the By Changing Cells box
|
5
|
The number of constraints
|
6
|
An array of the left sides of the constraints in the form of text
|
7
|
An array of numbers corresponding to the relationships between the left and right sides of the constraints:
1 = <=
2 = =
3 = >=
4 = int
|
8
|
An array of the right sides of the constraints in the form of text
|
The following settings are specified in the Solver Options dialog box:
Type_Num
|
Returns
|
10
|
The maximum number of iterations
|
11
|
The precision
|
12
|
The integer tolerance value
|
13
|
TRUE if the Assume Linear Model check box is selected; FALSE otherwise
|
14
|
TRUE if the Show Iteration Results check box is selected; FALSE otherwise
|
15
|
TRUE if the Use Automatic Scaling check box is selected; FALSE otherwise
|
16
|
A number corresponding to the type of estimates:
1 = Tangent
2 = Quadratic
|
17
|
A number corresponding to the type of derivatives:
1 = Forward
2 = Central
|
18
|
A number corresponding to the type of search:
1 = Quasi-Newton
2 = Conjugate Gradient
|
Sheet_name is the name of a sheet that contains the scenario for which you want information. If sheet_name is omitted, it is assumed to be the active sheet.
Return to index