QWaylandQuickShellSurfaceItem Class
The QWaylandQuickShellSurfaceItem class provides a Qt Quick item that represents a QWaylandShellSurface. More...
| Header: | #include <QWaylandQuickShellSurfaceItem> |
| qmake: | QT += waylandcompositor |
| Since: | Qt 5.8 |
| Inherits: | QWaylandQuickItem |
Properties
- moveItem : QQuickItem *
- shellSurface : QWaylandShellSurface *
- 12 properties inherited from QWaylandQuickItem
- 23 properties inherited from QQuickItem
Public Functions
| QWaylandQuickShellSurfaceItem(QQuickItem *parent = nullptr) | |
| QQuickItem * | moveItem() const |
| void | setMoveItem(QQuickItem *moveItem) |
| void | setShellSurface(QWaylandShellSurface *shellSurface) |
| QWaylandShellSurface * | shellSurface() const |
- 29 public functions inherited from QWaylandQuickItem
- 95 public functions inherited from QQuickItem
Signals
| void | moveItemChanged() |
| void | shellSurfaceChanged() |
- 13 signals inherited from QWaylandQuickItem
- 1 signal inherited from QQuickItem
Reimplemented Protected Functions
| virtual void | mouseMoveEvent(QMouseEvent *event) override |
| virtual void | mouseReleaseEvent(QMouseEvent *event) override |
- 2 protected functions inherited from QWaylandQuickItem
- 33 protected functions inherited from QQuickItem
Additional Inherited Members
- 4 public slots inherited from QWaylandQuickItem
- 1 public slot inherited from QQuickItem
- 2 protected functions inherited from QWaylandQuickItem
- 33 protected functions inherited from QQuickItem
Detailed Description
The QWaylandQuickShellSurfaceItem class provides a Qt Quick item that represents a QWaylandShellSurface.
This class is used to render wl_shell
or xdg_shell
surfaces as part of a Qt Quick scene. It handles moving and resizing triggered by clicking on the window decorations.
See also QWaylandQuickItem.
Property Documentation
moveItem : QQuickItem *
This property holds the move item for this QWaylandQuickShellSurfaceItem.
Access functions:
| QQuickItem * | moveItem() const |
| void | setMoveItem(QQuickItem *moveItem) |
Notifier signal:
| void | moveItemChanged() |
shellSurface : QWaylandShellSurface *
This property holds the shell surface rendered by this QWaylandQuickShellSurfaceItem. It may either be a QWaylandXdgSurface or a QWaylandWlShellSurface depending on which shell protocol is in use.
Access functions:
| QWaylandShellSurface * | shellSurface() const |
| void | setShellSurface(QWaylandShellSurface *shellSurface) |
Notifier signal:
| void | shellSurfaceChanged() |
Member Function Documentation
QWaylandQuickShellSurfaceItem::QWaylandQuickShellSurfaceItem(QQuickItem *parent = nullptr)
Constructs a QWaylandQuickWlShellSurfaceItem with the given parent.


This is a complete "Best Practices" starter project that uses standard web components in a multi-page application. No more "Component already registered" errors. For ulta-rapid page display, all components are late-loaded. Loosely coupled component communication using streams. Confirmed to work in all major browsers and IE11.
The starter project contains a number of individual components. One sample component is published though this collection.
To setup and run, follow these instructions, beginning with item 6 (Download and unzip...). This is part of a 10-step Web App Best Practices Tutorial. Refer to chapters 1-8 for the concepts applied in this project.
A printed version of the tutorials/Lab Book is available from https://m.appthings.io .
Do the tutorials, and/or contact https://m.appthings.io for commercial support and training.


devil rjhjd
Welcome To
MyDream Public School
In the last 20 years, MyDream Public school has grown by leaps and bounds to take its place among the top schools of central India. With five branches, and an enrollment of over 7500+ students, SPS also enjoys the distinction of being one of the largest schools in central India. SPS, one of the best School in Bhopal, has a vibrant atmosphere for proper teaching and learning and a faculty rich in talent and experience. As enterprise and endeavour are its watchwords, the school always keeps an eye on new educational initiatives, so that the road to excellence, on which the institution has already launched itself, becomes smoother, more navigable and more accessible. Quality enhancement is its mission - it tries to create a win-win situation for its students with a personalized and positive approach towards education.


Fitness
Diet
tips & tricks
did you know
Near Me
Quiz
Contact Us
Tips & Tricks
Fitness
Diet
Health
Mental Health
Hygiene
Tips


I am a Ph.D. candidate in School of Architecture at Carnegie Mellon University advised by Prof.Vivian Loftness. My research interests lie in the field of indoor environmental quality, post occupancy evaluation, thermal comfort, and thermal alliesthesia in thermal pleasure. I have diverse range of scholarly activities at hand, such as field research, experimental research, developing comfort model, and establishing database. I am currently working on the database which contains occupant satisfaction responses, building system attributes, and environmental measures collected in more than 60 office buildings. This would contribute to finding out associations between each other, suggesting strategies to improve occupants satisfaction by providing occupants with adequate indoor environmental quality with supportive building design.
Cumulative GPA: 4.18/4.3 (4.0/4.0)
M.S. Thesis: “Electroencephalogram (EEG) Variations Associated with Alliesthesia: Thermal Pleasure Induced by Temperature Step-change”
Major GPA: 4.16/4.3 (3.94/4.0, Graduation with High Honors)
Exchange student, University of California Santa Barbara (August 2012 - May 2013)
- Development of Comfort Model for Automobile to Validate Comfort Prediction.
- A Study on the Combined Effects of Indoor Environment (thermal, air, acoustics, and light) on Occupants’ Comfort
- A Research on Indoor Environmental Quality in Subway Stations.
- Optimization of Comfortable Conditions for Occupants.
- Development of ASHRAE Database MKⅡ
- Understanding Occupants’ Comfort Associated with Their Activities in the Korean Healthy House.
Youngjoo Son and Chungyoon Chun (2018), Electroencephalogram to Measure Thermal Pleasure in Thermal Alliesthesia in Temperature Step-change, Indoor Air. [www]
Young Joo Son, Vivian Loftness, and Azizan Aziz (2020), “Visual Environmental Parameters Associated with Occupant Satisfaction in Multiple Office Buildings.” ASHRAE Winter Conference, Orlando, FL, US.
Young Joo Son, Azizan Aziz, and Vivian Loftness (2018), “Visual Environmental Qualities Associated with Occupant Satisfaction in Multiple Office Buildings.” Indoor Air Conference, Philadelphia, PA, US.
Youngjoo Son, Jieun Han and Chungyoon Chun (2017). “Electroencephalogram (EEG) variations associated with alliesthesia: thermal pleasure induced by temperature step-change.” Symposium for Annex 69, Heidelberg, Germany.
Seoyeon Yun, Youngjoo Son and Chungyoon Chun (2016). “Correlation between Mean Skin Temperature and Overall Thermal sensation.” Architectural Institute of Korea Conference, Seoul, Korea.
Youngjoo Son and Chungyoon Chun (2015). “Brain Wave and Thermal Pleasure with Temperature Step-change.” Korean Society for Indoor Environment Conference, Seoul, Korea. Best Research Paper Award.
Jieun Han, Youngjoo Son and Chungyoon Chun (2015). “Indoor Climate and Air Quality in Subway Stations in Seoul.” The ISHVAC-Cobee Conference, Tianjin, China.
Youngjoo Son, Jieun Han and Chungyoon Chun (2015). “Passenger’s Evaluation on Environmental Comfort in Subway Station in Winter.” Architectural Institute of Korea Conference, Seoul, Korea.
Youngjoo Son and Chungyoon Chun (2015). “Temperature Step-change and Thermal Pleasure.” The Korean Home Economics Association Conference, Seoul, Korea.
Youngjoo Son, Yoorim Choi, Minjung Kim, Yongmin Kim and Chungyoon Chun (2014). “Occupants’ Stress based on Brain Waves and Salivary Alpha-amylase Responses on Each PMV Condition.” Indoor Air Conference, Hong Kong, China.
[46-768] Indoor Environmental Quality (IEQ); Energy, Health and Productivity, Fall 2018 and Fall 2019
[48-729] Energy, Productivity, Health and the Quality of the Built Environment, Fall 2017, Fall 2018, and Fall 2019
[90-728] Introduction to Database Management, Spring 2018, Fall 2018, Spring 2019, and Fall 2019
[94-842] R Programming Analysis, Fall 2018
[48-721] Building Controls and Diagnostics, Spring 2018 and Spring 2019


A CHEF IN LOVE A film review by Bradley Null Copyright 1997 Bradley Null
. The title character of A Chef In Love is a Frenchman with equal passions for his restaurant and his lover. These dual passions create an unusual love triangle which, like most of the film's political, romantic, and historical issues, is never quite resolved.
Like the contemporary The English Patient, A Chef In Love is structured around countless flashbacks and takes pleasure in confusing our sense of time and place. It ultimately becomes apparent that these flashbacks present a love story which takes place in pre-Soviet Georgia, and our chef's female love interest is a member of that country's aristocracy. Both of the chef's passionate romances become troubled when the Communist revolution threatens his prosperity, and he is forced to choose loyalty to one of his loves. This story is recounted in a compilation of old letters and diary entries which have been delved up by the woman's son and the chef's niece.
Originally, the woman's son, Anton, is completely unaware of his mother's past relationship and his parents's past identities. However, in an early flashback we see Anton's father chasing his mother with a knife muttering the name of this chef. This serves to quickly verify an unresolved conflict that Anton becomes eager to uncover. The flavor of this subjective flashback, in which the fleeing mother suddenly becomes a turkey and is slaughtered by her husband, establishes the confusion and complexities packed within this film. Throughout, we are taken by surprise as the narrative jumps from past to present, uncovering new evidence and then addressing the effect that the discovery of it has had on Anton.
This flashback structure also adds to the film's theme of repetition and circularity. For example, the camera commonly lingers over the same entrees and artwork in both the past and the present, creating a sense of timelessness for the film's subject. The settings and other decor in the film are also quite beautiful. However, throughout, the camera's persistently tight frame prevents us from enjoying the grandness of these exotic locations and feasts. This denial of spectacle serves to focus attention more tightly on the complex love triangle and the tension it causes, which is developed up to the last frame of the film.
Unfortunately, this preoccupation with the lovers forces most of the others characters into flat and subservient roles. For example, Anton, although he discovers a whole new side of both his mother and father, is denied the screen time to deal with these issues. Likewise, Anton's father is given just enough screen time for us to realize his complexities, but not enough for us to understand them. The most egregious oversight however, is of Marcelle, the cook's niece, who is not characterized at all, and ultimately serves to merely jump-start the narrative by bringing these diary pieces to Anton.
As a mature romance, A Chef In Love is the most compelling film to come along in a long time (far superior to The English Patient). However, it is almost regrettable to witness so many interesting characters and subplots being neglected for the sake of a single, albeit interesting, story.

The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


It's a Japanese manga series shōnen written and illustrated by Koyoharu Gotōge. The manga is serialized since 15 of February 2016 and ended on May 18, 2020 in the weekly Weekly magazine Shōnen Jump, with your chapters being brought together in 23 volumes tankōbon by the publisher Shueisha.
| Anime | Mangá |
|---|---|
| Season 1 | Vol. 1 until 22 |


Reading Discussion 2
Key Word(s): Kubernetes, Helm, Loft, Skaffold
Kubernetes
[9/10 not a complete list]
Expository
- Kubernetes 101
- Kubernetes Architecture 101
- The Kubernetes Bible for Beginners & Developers
- Kubeflow
- Benefits of Kubernetes
- Why Kubernetes is a Considerable Step Forward in Software Products Development?
- Local Kubernetes Development
- Containers and Cloud: From LXC to Docker to Kubernetes
- Kubernetes Virtual Clusters for AI/ML Experiments)
- Antifragility in Kubernetes
Longer Reads
- Kubernetes: Up and Running (ch.12-14)
- Hands-On Docker for Microservices with Python: design, deploy, and operate a complex system with multiple microservices using Docker and Kubernetes (ch.5-7)
Research
- Firmament: Fast, Centralized Cluster Scheduling at Scale
- Democratizing Production: Scale Distributed Deep Learning
- Serverless inferencing on Kubernetes
Use cases and other interesting reads
- Kubeflow: Build an ML pipeline
- Poseidon-Firmament, The package for Kubernetes Scheduler
- Helm, The package manager for Kubernetes
- Skaffold, The package for Kubernetes local development
- Loft, The package for Kubernetes virtual cluster
- Virtual Cluster: Sandboxes for ML experiment
Choose from Research and Use cases


Toggle navigation
Basic Gantt Chart
Project
Project information
Custom fields
Change working time
Export
Task
Add task
Add milestone
Summary
Team
Format
Gantt info
© DHTMLX


ArcelorMittal aborts plan to acquire struggling Italian group Ilva
Ilva's Taranto site in southern Italy is at the centre of a huge legal case
by AFP | PTISteel giant ArcelorMittal said Monday it was pulling out of the purchase of struggling Italian group Ilva after Italy's parliament removed a legal protection deemed necessary to undertake crucial environmental work without criminal liability.
Italian government to summon ArcelorMittal over Ilva contract
The Italian government will summon representatives of ArcelorMittal for a meeting following the group's decision to pull out of a contract to take over struggling Italian steel maker Ilva, a government source said on Monday.
"The government will not give its consent to closing Ilva. There is no legal basis for the contract to be cancelled. We will summon Mittal to Rome immediately," the source said, following a meeting of ministers involved in handling the case.
Ilva's Taranto site in southern Italy is at the centre of a huge legal case in which experts cited by prosecutors have said that of the 11,550 people who died in the area over seven years, 7,500 were killed by cardiovascular and respiratory diseases and cancers linked to toxic emissions.


Three new things I have learnt about myself and my ego as a result of the Core learning?

When learning more difficult concepts, my brain disconnects fast.
I am able to understand things, when I continuously tackle it.
What are the roles of values, empathy and self awareness in learning and programming?
To understand who I am as a person and how I can improve in accordance with my learning speed.
What has surprised you the most about core learning?
The importance of mindset
In the coding industry, skill is not everything, there are other factors like EQ that all correlate to success in this field.
What were the most challenging aspects of the core learning?
Understanding my learning style and cater towards it
Why fixate so much on core learning in a web development bootcamp coourse?
Because, success in this industry does not 100% correlate to skill. Core learning is able to help with self development and enhancing the self. So when unpredictable problems arrive, the self is well-equipped to combat these problems.
Does the time you spent studying core learning here feel like a waste of time? Should you have just used that time to practise programming instead?


Knitting for life
a customer survey
Please enter your name:
Please enter your e-mail address:
How old are you ?
What is you specialization?
Scarfs
Pillows
Socks
Blankets
Sweaters
Carpets
Hats
Toys
Gloves
Furniture
Others
Which option best decribes why you are knitting?
Hobby
Job
Other
What types of items you have done so far?
Scarfs
Blankets
Pillows
Socks
Sweaters
Carpets
Hats
Toys
Gloves
Furniture
Others
Please leave your additional comments below:
Submit


--- layout: page permalink: /about_me image_milkyway: feature: https://images.unsplash.com/photo-1444703686981-a3abbc4d4fe3?crop=entropy&dpr=2&fit=crop&fm=jpg&h=550&ixjsv=2.1.0&ixlib=rb-0.3.5&q=50&w=1250 feature: https://images.unsplash.com/photo-1450849608880-6f787542c88a?ixlib=rb-0.3.5&s=11081388185897fbb538648fceb61087&auto=format&fit=crop&w=1932&h=900&q=80 credit: Greg Rakozy creditlink: https://unsplash.com/photos/0LU4vO5iFpM images: fsu: feature: /img/fsu.jpg credit: Bill Lax creditlink: https://www.fsu.edu/administration/ cube_kendama_collection: feature: /img/cube_kendama_collection.jpg ---


|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
InputStream
and Reader
.
See:
Description
| Class Summary | |
| ClassLoaderObjectInputStream | A special ObjectInputStream that loads a class based on a specified
ClassLoader rather than the system default. |
| CountingInputStream | A decorating input stream that counts the number of bytes that have passed through the stream so far. |
| DemuxInputStream | Data written to this stream is forwarded to a stream that has been associated with this thread. |
| NullInputStream | A functional, light weight InputStream that emulates
a stream of a specified size. |
| NullReader | A functional, light weight Reader that emulates
a reader of a specified size. |
| ProxyInputStream | A Proxy stream which acts as expected, that is it passes the method calls on to the proxied stream and doesn't change which methods are being called. |
| ProxyReader | A Proxy stream which acts as expected, that is it passes the method calls on to the proxied stream and doesn't change which methods are being called. |
| SwappedDataInputStream | DataInput for systems relying on little endian data formats. |
This package provides implementations of input classes, such as
InputStream
and Reader
.
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |


Module
open class Module : ModuleProtocol
The Module
type acts as an owner of an underlying GModule
instance.
It provides the methods that can operate on this data type through ModuleProtocol
conformance.
Use Module
as a strong reference or owner of a GModule
instance.
The GModule
struct is an opaque data structure to represent a
dynamically-loaded module.
It should only be accessed via the following functions.
-
Untyped pointer to the underlying
GModule
instance. For type-safe access, use the generated, typed pointer_ptr
property instead.Declaration
Swift
public let ptr: UnsafeMutableRawPointer
-
Designated initialiser from the underlying
C
data type. This creates an instance without performing an unbalanced retain i.e., ownership is transferred to theModule
instance.Declaration
Swift
public init(_ op: UnsafeMutablePointer<GModule>)
Parameters
op
pointer to the underlying object
-
Designated initialiser from the underlying
C
data type.GModule
does not allow reference counting, so despite the name no actual retaining will occur. i.e., ownership is transferred to theModule
instance.Declaration
Swift
public init(retaining op: UnsafeMutablePointer<GModule>)
Parameters
op
pointer to the underlying object
-
Reference intialiser for a related type that implements
ModuleProtocol
GModule
does not allow reference counting.Declaration
Swift
public init<T>(_ other: T) where T : ModuleProtocol
Parameters
other
an instance of a related type that implements
ModuleProtocol
-
Unsafe typed initialiser. Do not use unless you know the underlying data type the pointer points to conforms to
ModuleProtocol
.Declaration
Swift
public init<T>(cPointer p: UnsafeMutablePointer<T>)
Parameters
cPointer
pointer to the underlying object
-
Unsafe typed, retaining initialiser. Do not use unless you know the underlying data type the pointer points to conforms to
ModuleProtocol
.Declaration
Swift
public init<T>(retainingCPointer cPointer: UnsafeMutablePointer<T>)
Parameters
cPointer
pointer to the underlying object
-
Unsafe untyped initialiser. Do not use unless you know the underlying data type the pointer points to conforms to
ModuleProtocol
.Declaration
Swift
public init(raw p: UnsafeRawPointer)
Parameters
p
raw pointer to the underlying object
-
Unsafe untyped, retaining initialiser. Do not use unless you know the underlying data type the pointer points to conforms to
ModuleProtocol
.Declaration
Swift
public init(retainingRaw raw: UnsafeRawPointer)
-
Unsafe untyped initialiser. Do not use unless you know the underlying data type the pointer points to conforms to
ModuleProtocol
.Declaration
Swift
public init(raw p: UnsafeMutableRawPointer)
Parameters
p
mutable raw pointer to the underlying object
-
Unsafe untyped, retaining initialiser. Do not use unless you know the underlying data type the pointer points to conforms to
ModuleProtocol
.Declaration
Swift
public init(retainingRaw raw: UnsafeMutableRawPointer)
Parameters
raw
mutable raw pointer to the underlying object
-
Unsafe untyped initialiser. Do not use unless you know the underlying data type the pointer points to conforms to
ModuleProtocol
.Declaration
Swift
public init(opaquePointer p: OpaquePointer)
Parameters
p
opaque pointer to the underlying object
-
Unsafe untyped, retaining initialiser. Do not use unless you know the underlying data type the pointer points to conforms to
ModuleProtocol
.Declaration
Swift
public init(retainingOpaquePointer p: OpaquePointer)
Parameters
p
opaque pointer to the underlying object
-
Opens a module. If the module has already been opened, its reference count is incremented.
First of all
g_module_open()
tries to openfile_name
as a module. If that fails andfile_name
has the “.la”-suffix (and is a libtool archive) it tries to open the corresponding module. If that fails and it doesn’t have the proper module suffix for the platform (G_MODULE_SUFFIX
), this suffix will be appended and the corresponding module will be opened. If that fails andfile_name
doesn’t have the “.la”-suffix, this suffix is appended andg_module_open()
tries to open the corresponding module. If eventually that fails as well,nil
is returned.Declaration
Swift
public static func open(fileName file_name: UnsafePointer<gchar>, flags: ModuleFlags) -> Module!


Welcome to Cab-Driver!!
One of Pune's most well known cab services,
cabFriend never ceases to amaze!
LOGIN


| com.episode6.hackit.mockspresso.BuildMockspresso |
Contains a static method to create new Mockspresso.Builders |
| com.episode6.hackit.mockspresso.exception.CircularDependencyError |
Error thrown when trying to declare multiple @RealObjects that create a circular dependency. |
| com.episode6.hackit.mockspresso.util.CollectionUtil |
Static utilities for collections |
| com.episode6.hackit.mockspresso.junit.MethodRuleChain |
Similar to java's |
| com.episode6.hackit.mockspresso.junit.MethodRules |
Utility methods for Method Rules |
| com.episode6.hackit.mockspresso.exception.NoValidConstructorException |
Exception thrown when trying to create a real object that has no constructor. |
| com.episode6.hackit.mockspresso.util.Preconditions |
Some preconditions |
| com.episode6.hackit.mockspresso.exception.RepeatedDependencyDefinedException |
Exception thrown when trying multiple fields/objects are bound to the same |


Meet The Bois
Untzzer
Sniper king in his gold G-Wagon with memes for days. Also hip with the ladies.
Rush4Hours
Dudu
When a clutch is needed, you can always call on this boi.
Rpslngr66
This boi shows exemplary character and runs the daycare for the bois.
F to pay respects.
RegularImp10050
Fufu
A swole Trinidadian brother with a healthy appetite to get kills in WZ
Yazoo2
The Boi that keeps us in touch with politics. The Bois need to be aware even if they don't leave home.

Ginja-Ben
He's like a ninja but usually wearing red. Doesn't really help for stealth tbh. This boi has lightning Reflexes.
Yomi
The boi to go to for your tech needs.
Games We Play
Warzone
Trending
Win after Win after Win, we don't stop winning.
[Replace Win with loss, winning with losing]
Except the very rare times we lose.
[replace lose with win]
Tekken
The Classic
We take pride with winning against ourselves in this game especially when we play with Rhea
Chess
Checkmate
Don't be misled. We are all intellectuals on the MeAndTheBoisClub.


Desktop Infrastructure [Employment]
May 2015 -- Dec 2016
- Packaged and maintained Perl applications for campus software network
- Used Microsoft SCCM for software and OS deployments to over 4,000 machines
- Maintained license servers for academic applications
Residential Lift Desk Worker [Employment]
August 2012 -- May2014
- Handled office reception and administration duties
- Organize residents information paperwork
Association for Computing Machinery (ACM)
August 2012 -- May2014
Sig Game Visualizer & Beta Testing Team
- Worked in teams to create visualization engine and unit test framework
- Host AI coding competition each semester
Quadrangle Hall Association (QHA)
August 2012 -- May2014
President & Secretary
- Improve organizational & leadership skills and Promote community development
- Member of Resident Hall Association (RHA)


Files | |
| file | cid.h [code] |
| file | codec.h [code] |
| AMQP data encoding and decoding. | |
| file | condition.h [code] |
| An endpoint error state. | |
| file | connection.h [code] |
| A connection to a remote AMQP peer. | |
| file | connection_driver.h [code] |
| Unsettled API - An API for low-level IO integration. | |
| file | delivery.h [code] |
| A message transfer. | |
| file | disposition.h [code] |
| A delivery state. | |
| file | engine.h [code] |
| file | error.h [code] |
| A Proton API error. | |
| file | event.h [code] |
| Protocol and transport events. | |
| file | handlers.h [code] |
| file | import_export.h [code] |
| file | link.h [code] |
| A channel for transferring messages. | |
| file | listener.h [code] |
| Unsettled API - A listener for incoming connections. | |
| file | log.h [code] |
| file | logger.h [code] |
| Facility for logging messages. | |
| file | message.h [code] |
| file | messenger.h [code] |
| Deprecated - Use the Proactor API or Qpid Proton C++. | |
| file | netaddr.h [code] |
| Unsettled API - The network address of a proactor transport. | |
| file | object.h [code] |
| file | proactor.h [code] |
| Unsettled API - An API for multithreaded IO. | |
| file | raw_connection.h [code] |
| file | reactor.h [code] |
| file | sasl.h [code] |
| SASL secure transport layer. | |
| file | sasl_plugin.h [code] |
| file | selectable.h [code] |
| file | session.h [code] |
| A container of links. | |
| file | ssl.h [code] |
| SSL secure transport layer. | |
| file | terminus.h [code] |
| A source or target for messages. | |
| file | tls.h [code] |
| file | transport.h [code] |
| A network channel supporting an AMQP connection. | |
| file | type_compat.h [code] |
| file | types.h [code] |
| AMQP and API data types. | |
| file | url.h [code] |
| Deprecated - Use a third-party URL library. | |


This App demo the IRIS REST API discovery and generation
This Angular App uses Bootstrap and Font Awesome. It was generated with Angular CLI.


PIU Tool is still under construction
Done
- Prepare flat-file data View All Songlist
- Markdown additional update/unlockable charts for prime2
- Prepare song banner lists for display
In Progress...
- Experiment with static web framework (Reactjs)
Backlog
- tag customization (special/gimmick charts)
- Make some magic with data (experiment tools : query tool)
- Workaround with nested object query (alasql or use something else)
- Randomizer
- Data structure refinement (?)
- Whatever I could think of...


{% extends "base_plain.html" %} {% block content %}
Sorry about that. We'll try to have this working again soon.


1 instantiation of ShowCommandProxy
Microsoft.PowerShell.Commands.Utility (1)
commands\utility\ShowCommand\ShowCommand.cs (1)
173
_showCommandProxy = new
ShowCommandProxy
(this);
2 references to ShowCommandProxy
Microsoft.PowerShell.Commands.Utility (2)
commands\utility\ShowCommand\ShowCommand.cs (1)
38
private
ShowCommandProxy
_showCommandProxy;
commands\utility\ShowCommand\ShowCommandProxy.cs (1)
30
_graphicalHostReflectionWrapper = GraphicalHostReflectionWrapper.GetGraphicalHostReflectionWrapper(cmdlet,
ShowCommandProxy
.ShowCommandHelperName);


# bin-wrapper [![Build Status](https://travis-ci.org/kevva/bin-wrapper.svg?branch=master)](https://travis-ci.org/kevva/bin-wrapper)
> Binary wrapper for Node.js that makes your programs seamlessly available as local dependencies
## Install
`bash
$ npm install --save bin-wrapper
`
## Usage
```js var BinWrapper = require(‘bin-wrapper’); var bin = new BinWrapper({ global: true });
- bin
.src(‘https://raw.github.com/yeoman/node-jpegtran-bin/0.2.4/vendor/win/x64/jpegtran.exe‘, ‘win32’, ‘x64’) .src(‘https://raw.github.com/yeoman/node-jpegtran-bin/0.2.4/vendor/win/x64/libjpeg-62.dll‘, ‘win32’, ‘x64’) .dest(‘vendor’) .use(‘jpegtran.exe’) .run([‘–version’], function (err) {
- if (err) {
- throw err;
}
console.log(‘jpegtran is working’);
});
Get the path to your binary with bin.use:
`js
console.log(bin.use()); // => path/to/vendor/jpegtran.exe
`
## API
### new BinWrapper(opts)
Creates a new BinWrapper instance. Use the global option to enable or disable global checking.
### .src(str)
Accepts a URL pointing to a file to download.
### .dest(str)
Accepts a path which the files will be downloaded to.
### .use(str)
Define which file to use as the binary.
### .run(cmd, cb)
Runs the search for the binary. If no binary is found it will download the file using the URL provided in .src(). It will also check that the binary is working by running it using cmd and checking it’s exit code.
## Options
### global
Type: Boolean Default: true
Whether to check for a binary globally or not.
## License
MIT © [Kevin Mårtensson](http://kevinmartensson.com)


---
layout: portfolio
title: Serrano Australia
subtitle: Sydney
description: Wholesale E-Commerce
image: serranoaustralia/serranoaustralia.png
---
Develop ongoing solutions to ongoing e-commerce related business requirements.
- Implement and manage Multi-Master MySQL replication to ensure hot-swap backup is always available.
- Created entire Yii ecommerce administration based on OpenCart database and integrated Yii into front end to simplify future development.
- Import thousands of products from dozens of suppliers in many different formats directly into database on a reoccurring basis.
- Export selected products to CSV for customer feeds on a reoccurring basis.
- Automate the process of batch order creation from wholesale customers and batch orders to suppliers.
- Developed with AdWords API to auto-populate and manage AdWords campaign based on current categories and products.
- Implemented EBay API to create and and manage EBay items and sales based on current categories and products.
- Create drag-and-drop tools for newsletter generation and newsletter management using MailChimp API.
- Implement processes for Warranty and Returns based on users purchase history.
- Designed an inventory management system to support variations of products and other business requirements.


The repayment plan
{% if data['plan'] == 'Set-date' %}The defendant will pay £1,500 by 4 January 2019.
{% else %}| Regular payments of | £75 | |
| Frequency of payments | Weekly | |
| Make the first payment on | 1 {{ now | date("add", 1, "month") | date( "MMMM YYYY" ) }} | |
| Last payment on | 1 {{ now | date("add", 13, "month") | date( "MMMM YYYY" ) }} | |
| Duration of payments | 1 year |
If you think you can't afford the repayment plan
You can pay a £50 fee to ask the claimant to agree to change the payment terms in the judgment.
If you think the defendant can repay you sooner, you can ask a judge to make a new repayment plan.
{% else %}If you think you can't afford the repayment plan, you can ask a judge to make a new repayment plan.
{% endif %} {% else %} {% if data['who'] == 'claimant' %} {% else %}If you think you can't afford the repayment plan
You can pay a £50 fee to ask the claimant to agree to change the payment terms in the judgment.


Radio Groups
Add a description here.
One
Two
Three
One
Lorem ipsum dolor.
Two
Sit amet consectetur elit.
One
Two
Three
One
Lorem ipsum dolor.
Two
Sit amet consectetur elit.


We’re elated at the increased community involvement since the donation of Harbor to the Cloud Native Computing Foundation. There’s lots of interest around the project, including a steady buzz of activity in our Slack channels and on GitHub.
This blog post is for those interested in contributing to a CNCF project that may not have much experience with the various steps involved. We’re a friendly bunch of developer and the best part of our work on Harbor is interacting with the community!
Contributing to an open source project can initially seem daunting. If you’re feeling like there are “more qualified” individuals to hop in and help, we’ve all been there. We all start somewhere and the great thing about open source – including and especially Harbor – is that this is a no-judgement community. We welcome contributors with all sorts of experiences and backgrounds, from well-spoken writers eager to make our documentation clearer, to bug hunters that are talented at finding the most obscure corner cases, to life-long developers that have been hacking at code for decades – we appreciate ALL contributions.
The topic of contributing to an open source project is vast, particularly with a project like Harbor that has lots of moving parts. This will be the first of (hopefully) several posts where we discuss how to dive into the project and help. I’ll make an effort to be both succinct and practical – please feel free to fork the repo and follow along with the blog post.
The only thing that might help in following along is a bit of experience with Git. Fortunately there are some tremendous resources available for learning Git to varying degrees of interest. GitHub also has some good documentation that describes the various steps involved in the contribution process, and I’ll link to those as appropriate. Because Harbor is hosted on GitHub, understanding GitHub flow will make things much simpler as we tackle our first contribution. Read through this quick tutorial and make sure you grasp the basic concepts before moving forward. If you have questions, ping us on Slack. :)
Let’s start with the first step in any contribution to Harbor: forking the repo. GitHub has a great page that describes how and why we fork and, as described in said page, this is the first step, whether contributing docs, tests or code.
.
Congrats – you’re half way there!
Now comes the fun part: finding something to improve. A good starting place is documentation.
Docs are the easiest place to start making contributions, if only because there’s minimal cognitive overhead involved when updating documentation. There’s always room to improve documentation: cleaning up dead links, fixing typos, clarifying content and instructions, and creating new documentation to make things clearer for users of the Harbor platform.
As is discussed in the GitHub flow tutorial and the Open Source guide, creating a branch is the first step in the process. Branches are used as “sandboxes” where your proposed changes are located. In general, creating a branch is as easy as this:
$ git checkout -b doc-improvements
The previously-referenced GitHub documentation describes the various steps involved, but for completeness we’ll discuss here:
Critically, make sure you’re still in the right branch:
$ git status
The first line of the status output should show that you’re in your feature
branch, in our case doc-improvements
. Still with me?
Fire up your favorite text editor – VSCode, Atom, vim, emacs, even nano(!) – and open the doc file you’d like to improve. Update the documentation as appropriate, save it and then get ready to push it to your Harbor fork.
From a terminal, a git status
will show you what file you’ve just edited.
Make sure this looks right.
I’ll also operate under the assumption that you’ve set up git
properly –
specifically user.name
and user.email
. If in doubt, take a look at
this
doc first. This is important because it ensures that the changes you make
are properly attributed to you!
The next (almost there!) step is to commit the changes in your branch and push upstream:
$ git commit --verbose --signoff --message="Updating documentation to improve
<something>"
$ git push --set-upstream origin <my_branch_name>
The push
command will take your changes and push it to your fork of the
Harbor repo. Now we’re ready to create a Pull Request.
This is perhaps the easiest part of the process. Head over to your fork on
GitHub:
[https://www.github.com/
A banner at the top of the repo will present you with the option of creating a pull request.
Make sure the “base” branch is master
in the goharbor
organization. This
tells GitHub to compare your changes (in your branch) to the upstream Harbor
repository.
Won’t be long before we take a look at your Pull Request. Often there are minor suggestions along the way to make sure things are accurate, but this is the fun part of open source: collaboration!
The Pull Request is very much a “live conversation.” Minor issues will likely be accepted in short order, while larger (perhaps more impacting changes) might result in a discussion. We don’t bite, though, so please don’t be timid: share your opinions, thoughts and feel free to (nicely) push back as appropriate. We make mistakes, too.
I’ll follow-up with future blog posts with further discussion on how to contribute to Harbor. Contributing code can be more involved, particularly if the feature is large, but we encourage you to join the fun. You can find us on GitHub, Slack or on the harbor-users and harbor-dev Google Groups mailing list.
Thanks for reading!
No matching community articles found at this time.


Name
Priority
Action
{{item.name}}
{{item.priority}}
EDIT
Low
Medium
High
SAVE
DELETE
Low
Medium
High


We here at Rolexx Consulting Services are a committed team of financial experts dedicated to bringing you the best experience and results possible. With a combined 86 years of financial consulting experience and a dozen degrees across our team, we are a premium service our customers can trust. We want you to see us not just as your consultants but as a valued associate who will put you first.
Using cryptography to keep exchanges secure, blockchain provides a decentralized database, or “digital ledger”, of transactions that everyone on the network can see. This network is essentially a chain of computers that must all approve an exchange before it can be verified and recorded. In the case of Bitcoin, blockchain stores the details of every transaction of the digital currency, and the technology stops the same Bitcoin being spent more than once. Many see Blockchain as the key to a connected digital future that could eventually permeate all aspects of society.
Autonomous things, abbreviated AuT, or the Internet of autonomous things, abbreviated as IoAT, is an emerging term for the technological developments that are expected to bring computers into the physical environment as autonomous entities without human direction, freely moving and interacting with humans and other objects. Famous examples include Tesla model 'Autopilot' cars, described as such 'Autopilot advanced safety and convenience features are designed to assist you with the most burdensome parts of driving. Autopilot introduces new features and improves existing functionality to make your Tesla safer and more capable over time. Your Tesla will match speed to traffic conditions, keep within a lane, automatically change lanes without requiring driver input, transition from one freeway to another, exit the freeway when your destination is near, self-park when near a parking spot and be summoned to and from your garage.', and Amazon's six wheeled delivery drone Scout, being trialed in specific locations, capable of navigating footpaths and even safely crossing the road at speeds of up to 16 kilometres per hour.
The immersive experience is a sense of amplified realism enabled by use of mixed reality, augmented reality and virtual reality. Immersive Experience creates an enhanced world and changes how we interact with it in three full dimensions using each of our senses, aided by Machine Intelligence.


{{/* Return the section name, make it readable (humanize) and if there are 2 or more entries, make the section name plural (pluralize). */}}
{{ i18n "Related" . }} {{ $i }} More {{ if ge $i 2 }}{{ .Section | humanize | pluralize }}{{ else }}{{ .Section | humanize }}{{end}}
{{ range first .Site.Params.related_posts_number $section_pages }}
-
{{/* If the URL returned is the same as the current URL dim it so we know that that's the page we're on. NOTE: Should probably use a more accessible way of displaying this. */}}
{{ .Title }}
{{ end }}
{{ end }}
{{/* Archives */}}
{{/* Socials */}}


The consumption of food is normally enjoyable to humans. It contains protein, fat, carbohydrates, vitamins, water and minerals
Save Upto 10%
2020/11/10
John Doe
This is a very good product
Items from another merchant are available in the cart. This action will remove those ' +
'items from the cart. Do you wish to continue?


d = dict()
with open(filename) as f:
for idx, word in enumerate(f):
word = word.strip()
d[word] = idx
return d
print("Loading vocab...")
with open(filename) as f:
d = {w.rstrip(): i for i, w in enumerate(f)}
print("- done. {} tokens".format(len(d)))
return d


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.
BEFORE THE NATIONAL GREEN TRIBUNAL PRINCIPAL BENCH NEW DELHI .............. M.A.No.617/2013, 734/2013 & 735/2013 (Arising out of Appeal No.81 of 2013) In the matter of M/s Krishna Stone Crushers Village Devdhar, Tehsil Chachrouli, District Yamuna Nagar (Haryana) .........Appellants AND M.A.No.623/2013, 730/2013 & 731/2013 (Arising out of Appeal No.82 of 2013) In the matter of M/s Jagat Stone Crusher, Village Ballewala, District Yamuna Nagar (Haryana) .........Appellants AND M.A.No.619/2013, 726/2013 & 727/2013 (Arising out of Appeal No.83 of 2013) In the matter of M/s Mehal Stone Crushers, Village Ballewala District Yamuna Nagar (Haryana) .........Appellants AND M.A.No.618/2013, 720/2013 & 721/2013 (Arising out of Appeal No.84 of 2013) In the matter of M/s Gayatri Stone Crushers, Village Ballewala, Tehsil Chachrouli, District Yamuna Nagar (Haryana) 1 .........Appellants AND M.A.No.622/2013, 732/2013 & 733/2013 (Arising out of Appeal No.85 of 2013) In the matter of M/s Kaveri Stone Crushers, Village Devdhar, District Yamuna Nagar (Haryana) .........Appellants AND M.A.No.624/2013, 728/2013 & 729/2013 (Arising out of Appeal No.86 of 2013) In the matter of M/s Dhillon Stone Crushers, Village Mandewala, Yamuna Nagar (Haryana) .........Appellants AND M.A.No.621/2013, 724/2013 & 725/2013 (Arising out of Appeal No.87 of 2013) In the matter of M/s Panchkula Stone Crushers, Village Doiwala, Tehsil Chachrouli, District Yamuna Nagar (Haryana) .........Appellants AND M.A.No.620/2013, 722/2013 & 723/2013 (Arising out of Appeal No.88 of 2013) In the matter of M/s Super Stone Crushers, Village Doiwala, Tehsil Chachrouli, District Yamuna Nagar (Haryana) .........Appellants AND 2 M.A. No.878 of 2013 (Arising out of Appeal No.95 of 2013 In the matter of : 1. M/s. Jai Mata Di Stone Crushers Village Doiwala, Yamuna Nagar (Haryana) .........Appellants Versus 1. Haryana State Pollution Control Board C-11, Sector 6, Panchkula-124505 2. The Regional Officer, Haryana State Pollution Control Board, SCO No.131, Sector 17, Jagadri, Yamuna Nagar-135001 .......Respondents Counsel for Appellants : Mr. Dhruv Tamta and Mr. Harihara, Advocates Counsel for Respondents : Mr. Narender Hooda, Sr. Advocate and Mr. Devinder Pratap Singh, Mr. Vineet Malik and Ms. Chaitali Dhingra, Advocates for Respondents No.1 & 2 JUDGMENT
PRESENT :
Hon'ble Mr. Justice Swatanter Kumar (Chairperson) Hon'ble Mr. Justice U.D. Salvi (Judicial Member) Hon'ble Dr. D.K. Agrawal (Expert Member) Hon'ble Mr. B.S. Sajwan (Expert Member) Hon'ble Dr. R.C.Trivedi (Expert Member) Dated : 9th January, 2014 JUSTICE SWATANTER KUMAR, (CHAIRPERSON):
1. By this common judgment, we shall dispose of the above nine appeals as they arise out of similar facts and raise common legal issues. All the appellants are carrying on the business of stone 3 crushing under different names and styles in the State of Haryana. All of them challenge the legality and correctness of the order passed by the Haryana State Pollution Control Board (for short 'HSPCB') dated 15th March, 2012 which was upheld by the appellate authority vide its order dated 24th January, 2013. Besides referring to the specific facts in the cases, we would take up the Appeal No. 95 of 2013, (M/s. Jai Mata Di Stone Crushers vs. Haryana SPCB and Anr.) as the lead case for reference of the facts. M/s. Jai Mata Di Stone Crushers is a sole proprietorship concern, earlier working under the name and style of M/s Tej Singh Stone Crushers. The said appellant carries on the business of stone crushing, located in district Yamuna Nagar of the State of Haryana and falls under the jurisdiction of HSPCB. When it started its business in the year 1996, the appellant had obtained a No Objection Certificate (for short the 'NOC') from HSPCB on 9th September 1996. The NOC by HSPCB was issued based on the report dated 20th August 1996 of the Revenue authorities specifying that the appellant-unit is within the siting parameters for stone crushing units. After incurring heavy expenditure, it installed expensive equipment and got installed anti-pollution control measures to satisfy the terms and conditions of the consent granted under the Air (Prevention and Control of Pollution) Act, 1981 (for short the 'Act of 1981'). The appellant unit was granted consent from year to year by the HSPCB. The State Government of Haryana issued a notification dated 18th December, 1997 containing certain guidelines for installation and operation of stone crushers. With reference to the 4 said guidelines, a survey/inspection of the various units was conducted by the Regional officers of the HSPCB and reports were prepared. As per the report, Villages Ballewala, Doiwala and Koliwala were submerged in floods in 1978. According to the appellant, thus, the guidelines were inconsequential. In response to the query made by the HSPCB, vide its letter dated 25th August, 2003, the revenue authorities vide their letter dated 12th September, 2003 informed that the three villages had submerged and no abadi was left. Consequently, for giving consent, the measurements were being considered from Lal Dora of Village Devgarh in that area.
2. Another notification dated 30th October, 1998 was issued by the State Government where, inter alia, it intended to give benefit of Schedule II entry (n) to the stone crushers installed and in operation for a continuous period of one year before the coming into force of the notification of 1997. According to this appellant, they never violated either of the notifications afore-stated, rather they were entitled to the benefits of the notifications. No objection with regard to the distance was ever raised and the appellant has been granted consent till the year 2011. The appellant-unit vide its application dated 8th April, 2011 applied for obtaining of consent to operate for a further period of two years (2011-12 and 2012-13). It is pleaded by this appellant that in the year 2007, some villagers filed frivolous suits against the stone crushers, including that of the appellant. An application under order VII Rule 11 of the Code of Civil Procedure, 1908 was filed by the appellant and the other interested parties, which culminated into a withdrawal before the 5 High Court. The appellant alleges that the application for obtaining consent, of the Board was then pending before the Board. On 2nd February, 2012, a show cause notice was issued by the HSPCB to the stone crusher-unit including that of the appellant stating that the units were running in violation to the provisions of the notification dated 18th December, 1997 and the consent had been granted to the appellant under a misconception of the facts, projected by the revenue authorities. The said show cause notice dated 2nd February, 2012 reads as under:
"HARYANA STATE POLLUTION CONTROL BOARD S.C.O. NO. 131, Sector - 17, Jagadhri (Yamuna Nagar) No. HSPCB/YMN/2011/4234 Dated: 02/02/2012 To M/s. Jai Mata Di Stone Crusher, Vill Doiwala, Chhachhrouli, Yamuna Nagar Subject:- Show Cause Notice for closure under section 31-A of the Air (Prevention and control of Pollution) Act, 1981 Whereas, your stone crushing unit is installed and running in utter violation of the mandatory provisions of Haryana Government Notification of dated 18-12-97.
Whereas consent to establish (NOC) to your unit was granted by the Board under misconception of facts as narrated by the Revenue authorities in their reports revealing non existence of certain villages which are, in fact, existing as per recent reports of revenue authorities/Forest Deptt.
Whereas the siting parameters in respect of stone crushers, as per Notification were adjudged by the Board in light of the earlier, reports of the revenue authorities which in fact were not correct and consequently the NOC were issued under misrepresentation of true facts.
Whereas, as per latest inspection / survey carried out by Revenue Department, Yamuna Nagar, your Stone Crusher is falling short of required distance as per notification dated 18.12.1997.6
Whereas, as per latest inspection / survey carried out by Forest Department, Yamuna Nagar, your Stone Crusher is falling short of required distance as per notification dated 18.12.1997.
Whereas, you have failed to submit analysis report under Air Act for the year 2011-12 and also operating your unit without obtaining consent under Air Act for the year 2011-12.
Since your unit is not meeting out the siting parameters and is thus installed and being run in violation of the Notification, hence by this captioned notice you are hereby called upon to show cause as to why the NOC granted under misconception and misrepresentation of true and material facts to you, may not be revoked and why your unit be closed down as per provisions of Air Act, 1981. In view of the above, you are hereby given SCN for Closure for 15 days as to why your unit should not be closed and disconnect electric connection including other captive power under section 31-A of the Air Act, 1981 for non compliance of the provision of the said Act. In case you fail to comply with the deficiencies mentioned above within stipulated period, it will be presumed that you have nothing to say in this regard and accept the status as mentioned above, which will warrant your unit under section 31 - A of Air Act.
"31-A". Not withstanding anything contained in any other, but subject to the provisions of this Act and to any directions that the Central Government may give in this behalf, a Board may, in the exercise of it any person, office or authority and such person, officer or authority/shall be bound to comply with such directions.
Explanations: For the avoidance of doubts, it is hereby declared that the power to issue direction under this section includes the power to direct: -
(a) The closure, prohibition or regulation of any industry, operation or process.
or 7
(b) The stoppage or regulation or supply of electricity, water or any other services.
Regional officer Yamuna Nagar Endst No. HSPCB/YMN/2011/ A copy of the above is forwarded to the Chairman, Haryana State Pollution Control Board, Panchkula for kind information and further necessary action.
Regional officer Yamuna Nagar"
3. To this show cause notice, the appellant submitted a reply dated 15th February, 2012, in which it was claimed that no violation of the notification was committed by the appellants. According to the appellants, without considering the said reply, the HSPCB issued another show cause notice dated 23rd February, 2012 which reads as under: -
"HARYANA STATE POLLUTION CONTROL BOARD S.C.O. NO. 131, Sector - 17, Jagadhri (Yamuna Nagar) No. HSPCB/YMN/2011/5158 Dated: 23/02/2012 To M/s. Jai Mata Di Stone Crusher, Vill Doiwala, Chhachhrouli, Yamuna Nagar Subject:- Show Cause Notice for refusal of Consent under section 21/22 of Air Act, 1981 for the year 2011-
12. Kindly refer to your Consent application under Air Act, 1981 for the year 2011-12 and this office letter no. HSPCB/YMN/2011/4234 Dated 02.02.2012 on the subject mentioned above.
In this connection, it is obvious that your application was found incomplete and not conforming to the requirements of the above Act under which you sought the Consent for the year 2011-12 in the following respect:-8
1. Not submitted operation schedule of the stone crusher.
2. Not submitted Analysis Report under Air Act, 1981.
3. Not meeting the sitting parameters as per 18.12.1997 notification.
Your consent application under Air Act, 1981 for the year 2011-12 has been found incomplete in respect of issue as detailed above. You may like to comply with all these requirements and furnish fresh requisite documents to prove compliance of shortcoming mentioned above.
Your reply must reach in this office within 15 days, failing which it will be finally presumed by the Board that you have nothing to say in this matter and this communication may then be treated as the legal refusal of your consent under Air Act, 1981 for the year 2011-12.
Regional officer Yamuna Nagar Endst No. HSPCB/YMN/2011/ A copy of the above is forwarded to the Chairman, Haryana State Pollution Control Board, Panchkula for kind information and further necessary action.
Regional officer Yamuna Nagar"
4. A reply to this show cause notice was submitted by the appellant on 13th March, 2012 wherein besides stating the aforenoticed facts, it also claimed to have paid the fee for sample analysis.
5. According to the appellant, the HSPCB, without proper application of mind and not considering the replies submitted by them, passed the order dated 15th March, 2012 refusing to grant consent to the appellant. The said order reads as under: -
"HARYANA STATE POLLUTION CONTROL BOARD S.C.O. NO. 131, Sector - 17, JAGADHRI YAMUNA NAGAR, 91-1732-200137 Dated: 15/03/2012 9 Registration No. HSPCB/YMN/2011/5728 To M/s. Jai Mata Di Stone Crusher, Doiwala Yamuna Nagar Subject:- Refusal of consent for the year 2011-12 under Section 21/22 of Air (Prevention And Control of Pollution) Act, 1981 Please referred to your consent application submitted by you for the year 2011-12 under Section 21 and 22 of the Air Act 1981 received in this office.
Your consent application was examined by this office and it has been observed that you are not complying the various provisions is the Air Act 1981 and not complying the sitting parameters of the Notification dated 18.12.1997 accordingly show cause notices containing the observations/deficiencies were issued to your Unit vide this office letter o. 2555 dated 08.09.2011, 4234 dated 02.02.12 and 5180 dated 22.02.12. The replies submitted by you in this reference to show cause notices referred above is not satisfactory. Consent case of your Unit was put up before BLC (upper) meeting held on 27.02.2012 as per the decision of refuse your consent under Air Act 1981 for the year 2011-12 as you have failed to comply the following observations:
1. Not submitted operation schedule of the stone crusher.
2. Unit has not submitted analysis report under Air Act, 1981.
3. Not meeting the Sitting Parameters as per notification dated 18.12.1997.
In view of above referred fact consent application submitted by you under Air Act 1981 is hereby refused for the year 2011-12 rendering yourself liable for legal action under Section 37/38/39 of the Air (Prevention And Control of Pollution) Act, 1981 and all other rules/laws/orders by the Govt/Board from time to time as applicable in the matter.
Sd/-
Divisional Officer, Yamuna Nagar"
6. The order of the HSPCB was challenged by the appellant by 10 filing an appeal before the appellate authority constituted under the Water (Prevention and Control of Pollution) Act, 1974 and the Act of 1981. The appellate authority, after hearing the parties and by a detailed order dismissed the appeals vide its order dated 24th January, 2013. The relevant part of the said order reads as under:-
9. "The Census Department of Government of India, on the basis of Census carried out after every ten years publishes villagewise directory of the District which contains the list of all the villages as per Revenue record and updates the data in respect of population and other related parameters. The respondent Board has placed on record report which is annexed with copy of Memo No. 1637 dated 08.12.2011 from the District Statistical Officer, Yamuna Nagar, addressed to the Regional Officer, Yamuna Nagar with population Census for the years 1991 and 2001 in respect of villages Diowala (69) Bhood Majra (70) Kohliwala (68) and Ballamajra (71) with their population. The population of these villages as per 2011 Census was 261, 541, 329 and 839. This population growth is significant over 1991 Census data. It is yet to be published for the Census conducted for 2011, as informed by the District Statistical Officer, Yamuna Nagar. Thus it is authenticated that these villages existed in the year 1991 and it supported the view that even if these were washed away, these had since been rehabilitated earlier to 1991. So the existence of these villages cannot be questioned and the distance has to be measured from nearest village Abadi as per the requirements 11 of Notification dated 18.12.1997. There is another document titled "Report as on 2002 and Report as on today," prepared by Patwaris of concerned villages, Kanungo and the Tehsildar of Chhachhrauli as on 08.12.2011 in respect of five villages namely (i) Diowala (ii) Ballawala (iii) Kohliwala (iv) Bhood Majra and (v) Bhood Kalan, showing No. of houses in each village and authenticating the existence of these villages in the year 2002. The report of the Distt. Forest Officer, Yamuna Nagar records distance of the Units from the nearest Forest Land as per Govt. record. The report does not mention the year of recorded Forest. As the report does not record year so it does not help us in reaching at any conclusion about the applicability of the said parameter as far as the distance from recorded Forest is concerned on the given date. So we do not have any other view but to agree to the distance clearance of Forest at the time of issue of NOC to the Unit. The respondent Board has also placed on record report which is jointly signed by Revenue Deptt. and the PWD Officers consisting of SDO PWD B&R and the Tehsildar and 3 other Officials. The distance of the Unit of the appellants is much less than required 1000 m. So, according to this report the Unit does not meet the parameters of distance from the nearest village Abadi which should be minimum 1000 mtrs as per Notification. On the basis of overwhelming facts furnished by SDO (c) Bilaspur, in his report addressed to the Deputy Commissioner, Yamuna Nagar with a copy to the Regional 12 Officer respondent No. 2, this Authority is inclined to accept and agree to the truthfulness of the report about siting distance from village abadi.
10. The Refusal Consent for the year 2011-12 vide letter dated 15.03.2012 (Annex A-1) has listed following three issues with regard to which the Unit has failed to comply :-
i) Not submitting operation Schedule of the Stone Crusher.
ii) Unit has not submitted analysis report under Air Act, 1981.
iii) Not meeting the siting parameters as per Notification dated 18.12.1997.
The appellants have contended that they had been granted NOC in the year 1996 on the basis of distance parameters based on reports of the Revenue Authorities and those of the Forest Department about the distance from village Abadi and the recorded Forest, respectively and the respondent now cannot deny Consent after such a long period spanning over 15 years. We do not buy this argument as the NOC and Consent granted on misconceived information cannot be perpetuated as a matter of right. On the basis of documents / reports and oral submissions during the arguments by the respondent counsel we unhesitatingly accept the contention that the Unit is failing in respect of distance parameter from the nearest village abadi as per report dated 08.02.2011 of SDO (c) Bilaspur, Distt. Yamuna Nagar. The Refusal of 13 Consent vide letter No. HSPCB/YMN/2011/5658 dated 15.03.2012 (Annexure A/1) is upheld. The appeal fails and we order accordingly with no order as to costs."
7. Except in Appeal No. 95 of 2013, all other appellants filed review applications before the appellate authority praying for variation/review of the order dated 24th January, 2013 vide which 8 appeals were disposed of. In the review application, all possible grounds were taken including that the judgment suffered from errors apparent on the face of the record and also that the plea of granting of benefit of Clause (n) of Schedule II to the Notification dated 30th October, 1998 had not been considered appropriately by the appellate authority. This review application came to be dismissed by order of the appellate authority dated 5th April, 2013. In Appeal No. 95 of 2013 there is a challenge only to the order dated 24th January, 2013 and the appeal is barred by delay of 210 days as per the averments of the applicant-appellant himself, for which a separate application for condonation of delay bearing M.A. No. 878/2013 had been filed by the appellant.
8. In all other appeals, though there is no challenge to the order dated 5th April, 2013, but in the application for condonation of delay by the appellants, they have referred to the filing of the Review Application before the appellate tribunal and its dismissal vide order dated 5th April, 2013. They have prayed for condonation of delay which according to them is 49 days. 14
9. From the above narration of facts, it is clear that according the HSPCB, the appellants, stone-crusher owners, had committed three violations, namely:
(a) Non-submission of operation schedule of stone crushers;
(b) Non-submission of analysis report under the Act of 1981; and
(c) Not meeting the sitting parameters as per the notification dated 18th December, 1997. In the other show cause notice, it was stated that the stone-crushers were violating the provisions of the notification of 1997 and the HSPCB had granted consent under misconception of the facts as narrated by the authorities, as the above three villages had been rehabilitated. The stone crushers were running within the prohibited distance. The HSPCB had after conducting inspection and survey had passed the order dated 15 th March, 2012 declining grant of consent. These findings of facts were duly approved and concurred by the appellate authority in its order dated 24th January, 2013. The appellate authority, as is evident from the above, referred to the relevant part of the order dated 15th March, 2013 of the HSPCB, wherein paragraph 9, it had examined the rehabilitation of the villages with reference to the population thereof. They also relied upon the report as on 2002 and report as on today prepared by the patwaris of the concerned villages showing the number of houses in each village and authenticating the existence of these villages in the year 2002. These are findings of facts which were concurrently being recorded by the Board and the appellate authority and are duly supported by 15 relevant and admissible records. They have not taken into consideration any irrelevant evidence or material. Thus, there would be no justification before the Tribunal to interfere with these concurrent findings of facts. Human health is of utmost importance and must prevail over a private business interest. These stone crushers give rise to substantial quantity of fine fugitive dust emissions and high level of noise which create health hazards to the workers as well as the surrounding population by way of causing respiratory diseases and hearing impairment. The dust also adversely affects visibility, reduces growth of vegetation and hampers aesthetics of the area. A large body of literature based on field research indicates that air pollution caused by the stone crushing industry has adverse implications, both at the occupational level and community level. Air borne particles of free Silica (SiO2) of sizes smaller than 10 microns are capable of reaching respiratory system and cause silicosis, which in turn can result in normal lung tissues being replaced by non-functioning fibrous tissues (called fibrosis). There are also studies by National Institute of Occupational Health (NIOH) Ahmedabad which point to the high incidence of silicosis and tuberculosis among stone cutters. Presence of stone crushers in the vicinity of villages can therefore be a serious environmental and health hazard. Assuming that these stone crushers were adhering to the parameters, which as per the report of the HSPCB they are not, even then it is an undisputed proposition that their cumulative effect would be 16 injurious to the health of the villagers who are living within 400 or 800 meters of the location of these crushers.
10. Reference in this regard could be made to a recent judgment of the Tribunal in the case of DRG Grade Udyog v. State of Madhya Pradesh and Ors. All (I) NGT Reporter (Delhi) 205 where while discussing the impact of stone crushers on the schools within the close vicinity of the stone crushers, the Tribunal held as under:-
"23. At this stage, we notice some of the adverse impacts of such activity, which have been scientifically analysed, in relation to air and noise pollution with specific reference to children. Children are prone to higher effects of air pollution than adults as they consume much larger quantity of air per unit body weight that exposes them to higher degree of air pollution. Max Kilber, as early as in 1932, invented the theory of "Inverse Size Matter Metabolic Rate Law". This theory supports what we have stated above. Thus, adverse environmental impacts of running of stone crushing units in the vicinity of a school cannot be ignored or ousted on the plea of it not being covered under as residential area.
24. Similarly, the noise generated by the stone crushers will adversely affect the concentration level of children. Such activity is likely to hamper their ultimate performance. Noise has a 'masking' effect. Although a subdued noise is understandable in a quiet room, it is difficult to understand even a raised voice in noisy environment, like working of a stone crusher. This drowning or 'masking' occurs as a result of excitation of auditory nerve cells. In other words, it affects the understanding, concentration and capacity of the children to attentively listen to the lectures of their teachers. Persistent noise has long-term as well as short-term effects on health of children."
11. The notification of 18th December, 1997 has spelt out the protective measures and anti-pollution devices that a stone crusher is required to take and instal. The stone crusher which had started 17 its operations subsequent to the coming into force of the said notification had to be located at a distance of more than one km. from the nearest village abadi. Vide the notification dated 30th October, 1998, for the existing units, this distance was reduced to 400 metres of the village abadi/Lal Dora. This benefit was available to the stone crushers which were in operation one year prior to the issuance of the notification of 1997. The limits of distance prescribed under these notifications were mandatory and not preferential. The notifications impose restriction on the power of the competent authority to permit installation and operation of stone crushers at a distance less than the prescribed distance. In the present case, the stone crushers of the appellant cannot claim the benefit of clause (n) of Schedule II of the notification of 1998 on the ground that the villages had been wiped out in the floods. This is for the reason that the concurrent finding had been returned in this regard by the Board and the appellate authority against the appellant. It has been held with reference to the concurrent reports of the Tehsildar and the Forest Department, as referred to supra, that a large number of houses were found existing at the sites even in the year 1991. The notifications have to be interpreted in a manner that it would advance the cause of environmental protection rather than frustrate the same. The obvious result of accepting the contention of the appellant would cause environmental damage. It is clear from the records before the Tribunal that the units of the appellant are violating the condition 18 of distance imposed under the notification of 1997, as amended by the notification of 1998.
12. In view of the facts of this case and the law aforestated, we do not see any reason to interfere with the order dated 24 th January, 2013 under appeal in these cases.
Limitation:
13. Though we have dealt with and decided this case on merits, as above, still there is another hurdle which the appellants are required to cross as to all these appeals being barred by time. It is even contended that this Tribunal has no jurisdiction to condone the delay in terms of Section 16 of the National Green Tribunal Act, 2010 (NGT Act). Section 16 of the NGT Act reads as under:-
"16. Tribunal to have appellate jurisdiction. - Any person aggrieved by,-
********* h. an order made, on or after the commencement of the National Green Tribunal Act, 2010, granting environmental clearance in the area in which any industries, operations or processes or class of industries, operations and processes shall not be carried out or shall be carried out subject to certain safeguards under the Environment (Protection) Act, 1986;
********* may, within a period of thirty days from the date on which the order or decision or direction or determination is communicated to him, prefer an appeal to the Tribunal:
Provided that the Tribunal may, if it is satisfied that the appellant was prevented by sufficient cause from filing the appeal within the said period, allow it to be filed under this section within a further period not exceeding sixty days."19
14. The provisions of this Section came to be interpreted by a Bench of this Tribunal which has stated the law beyond ambiguity that once there is a delay beyond 90 days, then the Tribunal will have no jurisdiction to condone the same unless and until the communication of the order impugned in the appeal is shown not to have been received so late that it falls beyond the period of 90 days. This Tribunal had the occasion to deal with this aspect and interpretation of the provisions of Section 16 of the Act. Upon discussing the case law at some length and examining the legislative intent underlying this provision, the Tribunal in the case of Nikunj Developers & Others v. the State of Maharashtra & Others [2013 ALL(I) NGT(1) PB 40] held as under:-
"19. From language of the above provision it is clear that the Tribunal loses jurisdiction to condone the delay if the delay is of more than 90 days. Every appeal has to be filed within 30 days from the date of communication of the order. That is, what an applicant is required to ensure before the appeal is heard on merits. However, the Tribunal has been vested with the jurisdiction to entertain the appeal which is filed after 30 days from the date of communication of an order. This power to condone the delay has a clear inbuilt limitation as it ceases to exist if the appeal is filed in excess of 60 days, beyond the prescribed period of limitation of 30 days from the date of communication of such order. To put it simply, once the period of 90 days lapses from the date of communication of the order, the Tribunal has no jurisdiction to condone the delay. The language of the provision is clear and explicit. It admits of no ambiguity and the legislative intent that Tribunal should not and cannot condone the delay in excess of 90 days in all, is clear from the plain language of the provision.
20. As stated in the cases Hiralal Ratan Lal and India Houses (supra) the period of limitation statutorily prescribed, has to be strictly adhered to and cannot be relaxed and or departed from, on equitable consideration. Further, in construing a 20 statutory provision, the first and the foremost rule of construction is that of literary construction. We do not see any reason to expand the scope of the provision and interpret the proviso to Section 16 in the manner that Tribunal can be vested with the power of condoning the delay beyond 90 days. Such interpretation would be contrary to the specific language of the Section and would defeat the very legislative intent and object behind this provision.
21. This controversy need not detain us any further as it is no more res integra and stands answered by the judgment of the Supreme Court in the case of Chhattisgarh State Electricity Board Vs. Central Electricity Regulatory Commission and others (2010) 5 SCC 23 where the court held as under:
"29. Section 34(3) of the Arbitration and Conciliation Act, 1996, which is substantially similar to Section 125 of the Electricity Act came to be interpreted in Union of India v. Popular Construction Company : (2001) 8 SCC 470. The precise question considered in that case was whether the provisions of Section 5 of the Limitation Act are applicable to an application challenging an award under Section 34 of the Arbitration and Conciliation Act, 1996. The two-Judge Bench referred to earlier decisions in Mangu Ram v. Municipal Corporation of Delhi: (1976) 1 SCC 392, Vidyacharan Shukla v. Khubchand Baghel AIR 1964 SC 1099, Hukumdev Narain Yadav v. L.N.
Mishra (supra), Patel Naranbhai Marghabhai v. Dhulabhai Galbabhai : (1992) 4 SCC 264 and held:
12. As far as the language of Section 34 of the 1996 Act is concerned, the crucial words are "but not thereafter" used in the proviso to Sub-section (3). In our opinion, this phrase would amount to an express exclusion within the meaning of Section 29(2) of the Limitation Act, and would therefore bar the application of Section 5 of that Act. Parliament did not need to go further. To hold that the court could entertain an application to set aside the award beyond the extended period under the proviso, would render the phrase "but not 21 thereafter" wholly otiose. No principle of interpretation would justify such a result.
16. Furthermore, Section 34(1) itself provides that recourse to a court against an arbitral award may be made only by an application for setting aside such award "in accordance with" Sub-
section (2) and Sub-section (3). Sub-
section (2) relates to grounds for setting aside an award and is not relevant for our purposes. But an application filed beyond the period mentioned in Section 34, Sub-section (3) would not be an application "in accordance with"
that Sub-section. Consequently by virtue of Section 34(1), recourse to the court against an arbitral award cannot be made beyond the period prescribed.
The importance of the period fixed under Section 34 is emphasised by the provisions of Section 36 which provide that "where the time for making an application to set aside the arbitral award under Section 34 has expired ...
the award shall be enforced under the Code of Civil Procedure, 1908 in the same manner as if it were a decree of the court".
This is a significant departure from the provisions of the Arbitration Act, 1940. Under the 1940 Act, after the time to set aside the award expired, the court was required to "proceed to pronounce judgment according to the award, and upon the judgment so pronounced a decree shall follow" (Section 17). Now the consequence of the time expiring under Section 34 of the 1996 Act is that the award becomes immediately enforceable without any further act of the court. If there were any residual doubt on the interpretation of the language used in Section 34, the scheme of the 1996 Act would resolve the issue in favour of curtailment of the court's powers by the exclusion of the operation of Section 5 of the Limitation Act. (emphasis supplied) 22
30. In Singh Enterprises v. C.C.E., Jamshedpur and Ors. (supra), the Court interpreted Section 35 of Central Excise Act, 1944, which is pari materia to Section 125 of the Electricity Act and observed:
8. The Commissioner of Central Excise (Appeals) as also the Tribunal being creatures of statute are vested with jurisdiction to condone the delay beyond the permissible period provided under the statute. The period up to which the prayer for condonation can be accepted is statutorily provided. It was submitted that the logic of Section 5 of the Limitation Act, 1963 (in short "the Limitation Act") can be availed for condonation of delay. The first proviso to Section 35 makes the position clear that the appeal has to be preferred within three months from the date of communication to him of the decision or order. However, if the Commissioner is satisfied that the appellant was prevented by sufficient cause from presenting the appeal within the aforesaid period of 60 days, he can allow it to be presented within a further period of 30 days. In other words, this clearly shows that the appeal has to be filed within 60 days but in terms of the proviso further 30 days' time can be granted by the appellate authority to entertain the appeal. The proviso to Sub-section (1) of Section 35 makes the position crystal clear that the appellate authority has no power to allow the appeal to be presented beyond the period of 30 days. The language used makes the position clear that the legislature intended the appellate authority to entertain the appeal by condoning delay only up to 30 days after the expiry of 60 days which is the normal period for preferring appeal. Therefore, there is complete exclusion of Section 5 of the Limitation Act. The Commissioner and the High Court were therefore justified in holding that there was no power to condone the delay after the expiry of 30 days' period.
(emphasis supplied)"
23
22. The same view was reiterated in Commissioner of Customs, Central Excise v. Punjab Fibres Ltd. : (2008) 3 SCC 73.
"31. In Commissioner of Customs and Central Excise v. Hongo India Private Limited and Anr. (2009) 5 SCC 791, a three-Judge Bench considered the scheme of the Central Excise Act, 1944 and held that High Court has no power to condone delay beyond the period specified in Section 35H thereof. The argument that Section 5 of the Limitation Act can be invoked for condonation of delay was rejected by the Court and observed:
"30. In the earlier part of our order, we have adverted to Chapter VI-A of the Act which provides for appeals and revisions to various authorities. Though Parliament has specifically provided an additional period of 30 days in the case of appeal to the Commissioner, it is silent about the number of days if there is sufficient cause in the case of an appeal to the Appellate Tribunal. Also an additional period of 90 days in the case of revision by the Central Government has been provided. However, in the case of an appeal to the High Court under Section 35G and reference application to the High Court under Section 35H, Parliament has provided only 180 days and no further period for filing an appeal and making reference to the High Court is mentioned in the Act.
32. As pointed out earlier, the language usedinSections 35, 35B, 35EE, 35G and 3 5H makes the position clear that an appeal and reference to the High Court should be made within 180 days only from the date of communication of the decision or order.
In other words, the language used in other provisions makes the position clear that the legislature intended the appellate authority to entertain the appeal by condoning the delay only up to 30 days 24 after expiry of 60 days which is the preliminary limitation period for preferring an appeal. In the absence of any clause condoning the delay by showing sufficient cause after the prescribed period, there is complete exclusion of Section 5 of the Limitation Act. The High Court was, therefore, justified in holding that there was no power to condone the delay after expiry of the prescribed period of 180 days.
XXXXX XXXXX XXXXX XXXXX
35. It was contended before us that the words "expressly excluded" would mean that there must be an express reference made in the special or local law to the specific provisions of the Limitation Act of which the operation is to be excluded. In this regard, we have to see the scheme of the special law which here in this case is the Central Excise Act. The nature of the remedy provided therein is such that the legislature intended it to be a complete code by itself which alone should govern the several matters provided by it. If, on an examination of the relevant provisions, it is clear that the provisions of the Limitation Act are necessarily excluded, then the benefits conferred therein cannot be called in aid to supplement the provisions of the Act. In our considered view, that even in a case where the special law does not exclude the provisions of Sections 4 to 24 of the Limitation Act by an express reference, it would nonetheless be open to the court to examine whether and to what extent, the nature of those provisions or the nature of the subject-matter and scheme of the special law exclude their operation. In other words, the applicability of the provisions of the Limitation Act, therefore, is to be judged not from the terms of the Limitation Act but by the provisions of the Central Excise Act relating to filing of reference application to the High Court.
(emphasis supplied)
32. In view of the above discussion, we hold that Section 5 of the Limitation Act 25 cannot be invoked by this Court for entertaining an appeal filed against the decision or order of the Tribunal beyond the period of 120 days specified in Section 125 of the Electricity Act and its proviso. Any interpretation of Section 125 of the Electricity Act which may attract applicability of Section 5 of the Limitation Act read with Section 29(2) thereof will defeat the object of the legislation, namely, to provide special limitation for filing an appeal against the decision or order of the Tribunal and proviso to Section 125 will become nugatory."
23. Section 34 of the Arbitration and Conciliation Act, 1996 uses the expression 'not thereafter' while the provision under our consideration uses the terms 'not exceeding'. Both these expressions use negative language. The intention is to divest the Courts/Tribunals from power to condone the delay beyond the prescribed period of limitation. Once such negative language is used, the application of provisions of Section 5 of the Limitation Act or such analogous provisions would not be applicable.
24. The use of negative words has an inbuilt element of 'mandatory'. The intent of legislation would be to necessarily implement those provisions as stated.
25. Introduction or alteration of words which would convert the mandatory into directory may not be permissible. Affirmative words stand at a weaker footing than negative words for reading the provisions as 'mandatory'. It is possible that in some provision, the use of affirmative words may also be so limiting as to imply a negative. Once negative expression is evident upon specific or necessary implication, such provisions must be construed as mandatory. The legislative command must take precedence over equitable principle. The language of Section 16 of the NGT Act does not admit of any ambiguity, rather it is explicitly clear that the framers of law did not desire to vest the Tribunal with powers, specific or discretionary, of condoning the delay in excess of total period of 90 days. At this stage, we may also refer to Principle of Statutory 26 Interpretation by Justice G.P. Singh, 13th Edition, where it is stated as under:
"(c) Use of negative words Another mode of showing a clear intention that the provision enacted is mandatory, is by clothing the command in a negative form. As stated by CRAWFORD:
"Prohibitive or negative words can rarely, if ever, be directory. And this is so even though the statute provides no penalty for disobedience." As observed by SUBBARAO, J.: "Negative words are clearly prohibitory and are ordinarily used as a legislative device to make a statute imperative". Section 80 and Section 87-B of the Code of Civil Procedure, 1908; section 77 of the Railways Act, 1890; Section 15 of the Bombay Rent Act, 1947; section 213 of the Succession Act, 1925; section 5-A of the Prevention of Corruption Act, 1947; section 7 of the Stamp Act, 1899; section 108 of the Companies Act, 1965; section 20(1) of the Prevention of Food Adulteration Act, 1954; section 55 of the Wild Life Protection Act, 1972 (as amended in 1956); section 10A of Medical Council Act, 1965 (as amended in 1993) and similar other provisions have therefore, been construed as mandatory. A provision requiring 'not less than three months' notice' is also for the same reason mandatory.
But the principle is not without exception. Section 256 of the Government of India, 1953, was construed by the Federal Court as directory though worded in the negative form. Directions related to solemnization of marriages though using negative words have been construed as directory in cases where the enactments in question did not provide for the consequence that the marriage in breach of those directions shall be invalid. Considerations of general inconvenience, which would have resulted in holding these enactments mandatory, appear to have outweighed the effect of the negative words in reaching the conclusion that they were in their true meaning merely director. An interesting example, 27 where negative words have been held to be directory, is furnished in the construction of section 25-F of the Industrial Dispute Act, 1947, where compliance of clause (c) has been held to be directory; although compliance of clauses (a) and (b) which are connected by the same negative words is understood as mandatory. These cases illustrate that the rule, that negative words are usually mandatory, is like any other rule subordinate to the context, and the object intended to be achieved by the particular requirement."
26. The provision of Section 16 of the NGT Act are somewhat similar to Section 34 of Arbitration and Conciliation Act, 1996. Thus, adopting an analogous reasoning, as was adopted in Chhattisgarh State Electricity Board (supra), we would have no hesitation in coming to the conclusion that we have no jurisdiction to condone the delay when the same is in excess of 90 days from the date of communication of the order to any person aggrieved."
15. Now, we may apply the above principle to the facts of the present case. As far as the Appeal No. 95/2013 is concerned, the impugned order was passed on 24th January, 2013 and the same was received by the appellant. In the application for condonation of delay, the appellant has not stated as to when the appellant received the said order. Presumably, the order was received immediately thereafter. The appeal ought to have been filed within 30 days of the communication of the order or at best within 90 days upon showing sufficient cause for the condonable delay of 60 days. Beyond this period of 90 days, the Tribunal would not be able to condone the delay even upon showing existence of sufficient cause. As per the appellant, he prays for condonation of 210 days' delay though, in the present case, the order is of 24th January, 2013 and 28 the appeal was filed on 3rd October, 2013. Even if the period of 90 days is excluded, still there would be a delay of eight months and 17 days. After excluding the permissible period of 90 days, the appeal would still be barred by more than six months, which the Tribunal has no jurisdiction to condone. Thus, the appeal is liable to be dismissed on the grounds of limitation alone which we do hereby dismiss.
16. In all other cases, the order of the HSPCB of 15th March, 2012 and that of the appellate authority is of 24th January, 2013. All the appellants had filed review application before the appellate authority which came to be dismissed vide order dated 5 th April, 2013. In the appeals, none of the appellants have challenged specifically the order of review dated 5th April, 2013.
17. It is a settled proposition of law that where a review application is dismissed and the original order, review of which is sought, is maintained, the limitation will be computed with reference to the first order, i.e. 24th January, 2013. There being no challenge to the order dated 5th April, 2013, all these appeals would also be barred by eight months and the Tribunal will have no jurisdiction to condone the delay. All these appeals have been filed much beyond the period of 90 days, the prescribed period and permissible period of limitation beyond which the Tribunal has no jurisdiction to condone the delay. As such all these appeals are also liable to be dismissed on the grounds of limitation. 29
18. In view of our detailed discussion above, we dismiss all these appeals. However, in the facts and circumstances of the case, we leave the parties to bear their own costs.
Justice Swatanter Kumar Chairperson Justice U.D. Salvi Judicial Member Dr. D.K. Agrawal Expert Member B.S. Sajwan Expert Member Dr. R.C. Trivedi Expert Member January 9, 2014 New Delhi 30


Plane slides off snowy runway at Chicago's O'Hare International Airport
by CNN NewsourceCHICAGO -- An American Eagle flight slid off the runway Monday morning at Chicago's O'Hare International Airport as snowy conditions and blustery winds led to hundreds of flight cancellations at the city's major airports.
All 38 passengers and three crew members were deplaned from the aircraft and are now safely back in the terminal, said American Airlines spokesperson Ross Feinstein. The flight originated in Greensboro, North Carolina.
At the time of the incident, there was light snow with visibility of less than a mile, wind gusts of 30 miles per hour and a temperature of 23 Fahrenheit.
As of 10 a.m. ET, 500 flights were canceled at O'Hare and Midway International Airport due to weather conditions
The National Weather Service has issued a winter weather advisory for parts of Chicago until 3 p.m. ET.