Welcome {{ user.first_name }}
Vocabulary ➡
Voc Add
Voc List
Voc Delete
Daily Memory ➡
Daily Word
Daily Sentence
Daily Person
Fallback content goes here.
Home


Notebooks
Story: Moon and stars: an incantation
Moon and stars: an incantation
Title
Moon and stars: an incantation
Collection
Summary
Various statements are given with regard to the nature and movements of the celestial bodies. The first of these treats of the Moon and Stars, ending with the “Bushman–rice” Star Canopus (B I. 291–294... An incantation to the Moon and stars.
Comments
1) This story is found in Book I
Contributors
Date
1871
Categories
Poetry, Celestial bodies and aeroscopy
Keywords
Moon (and stars) , Moon (incantation to) , Moon (actions of) , Moon (waxes and wanes) , Moon (lives and dies) , Moon (the place where it comes) , heavens (an incantation to the Moon and stars) , clouds (an incantation to the Moon and stars) , stars (incantation to the Moon and) , stars (doings of) , stars (actions of) , stars ('little') , stars ('woman') , stars (the colour of) , stars (the Moon and) , stars (an incantation to) , stars (follow the Moon) , stars (walk in heaven) , stars (female) , stars (the gender of) , stars (the child of) , stars (red) , stars (the daughter of) , stars (the 'Bushman–rice' star Canopus) , springbok (and an incantation to the Moon and stars) , ostrich (and an incantation to the Moon and stars) , gemsbok (and an incantation to the Moon and stars) , incantation (to the Moon and stars) , incantation (song) , incantation (poetry) , incantation (prayer) , incantation (verse) , child (the star's) , child (incantation to the Moon and stars) , song (incantation to the Moon and stars) , poetry (incantation to the Moon and stars) , verse (incantation to the Moon and stars) , prayer (incantation to the Moon and stars) , prayer (for food) , food (and an incantation to the Moon and stars)
Story Pages
291-295


Free Images by Forum Images.com
About
As we firmly believe in the free software philosophy, in this archive you will find
a set of free images that were primarily designed for use with the phpBB version
2.x forum software that is available from
http://www.phpbb.com/
Usage
You may use these images free of charge, but if you wish to, please
feel free to place a link somewhere on your site/forum linking back to our main
site at http://www.forumimages.com/
Contents Of This Archive
19px Smilies (emoticons) - phpBB default set (with a few additions)
File Version: 1.00
Date: January 27, 2003
Help
Please do not ask for help with adding these images to your forum and/or web site
- Read the documentation that came with the software as well as checking the
Forum Images web site.
Distribution
This file should accompany the images if you are re-distributing this archive. No
charge is to be made for the supply of these images without prior permission of
Darren Burnhill.
Contacting Us
The most reliable way in which to contact us is via the phpBB Community forum;
Member Name: Daz
Profile: http://www.phpbb.com/phpBB/profile.php?mode=viewprofile&u=2135
Email contact is available at the Forum Images web site for those that need to, although we do not accept requests through the web site.
Legal Information
Unless stated otherwise, all images are copyright © Darren Burnhill 2002 -
please do not sell these graphics without prior permission.
We create all the images ourselves, but if you feel we have in any way infringed
on your rights as a company or individual, please contact us via the Forum Images
web site.


Zawinski's Law
`Prev `__
Z
`Next `__
--------------
**Zawinski's Law**
“Every program attempts to expand until it can read mail. Those programs
which cannot so expand are replaced by ones which can.” Coined by Jamie
Zawinski (who called it the “Law of Software Envelopment”) to express
his belief that all truly useful programs experience pressure to evolve
into toolkits and application platforms (the mailer thing, he says, is
just a side effect of that). It is commonly cited, though with widely
varying degrees of accuracy.
--------------
+---------------------------+----------------------------+--------------------------+
| `Prev `__ | `Up <../Z.html>`__ | `Next `__ |
+---------------------------+----------------------------+--------------------------+
| zapped | `Home <../index.html>`__ | zbeba |
+---------------------------+----------------------------+--------------------------+


The XcooBee Cafe is a template site. This is a sample template from w3 schools we use to show the use of XcooBee Cookie Kit. You can look at the source of this html to see how we can handle user cookie choice and process only when we have been given consent easily. We can use simple HTML tags for managed cookie declaration or write our own JavaScript code. Of course, we have quite a bit of information about the technical underpinnings of the XcooBee Cookie Kit (XCK).
Please review them on our documentation site XcooBee Cookie Kit Documentation.
You can also view our brief video for developers https://www.youtube.com/watch?v=gKYNoARNXRo
From here on we have placeholder text and more text from our template:
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
In addition to our full espresso and brew bar menu, we serve fresh made-to-order breakfast and lunch sandwiches, as well as a selection of sides and salads and other good stuff.
Opening hours: everyday from 6am to 5pm.
Address: 15 Main street, 28201, CLT
Here are our current terms of service:
We serve you coffee and tea and other great products but if you act or do any of the following we will ask you to get lost:
We respect all our visitors privacy. To that end we will follow this privacy policy:
Effective date: November 27, 2018
Cafe LLC ("us", "we", or "our") operates The XcooBee Cafe.local website (the "Service").
This page informs you of our policies regarding the collection, use, and disclosure of personal data when you use our Service and the choices you have associated with that data. Our Privacy Policy for Cafe LLC is managed through Free Privacy Policy Website.
We use your data to provide and improve the Service. By using the Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, accessible from cafe.local
We collect several different types of information for various purposes to provide and improve our Service to you.
While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you ("Personal Data"). Personally identifiable information may include, but is not limited to:
We may also collect information how the Service is accessed and used ("Usage Data"). This Usage Data may include information such as your computer's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data.
We use cookies and similar tracking technologies to track the activity on our Service and hold certain information.
Cookies are files with small amount of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Tracking technologies also used are beacons, tags, and scripts to collect and track information and to improve and analyze our Service.
You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Service.
Examples of Cookies we use:
Cafe LLC uses the collected data for various purposes:
Your information, including Personal Data, may be transferred to — and maintained on — computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from your jurisdiction.
If you are located outside United States and choose to provide information to us, please note that we transfer the data, including Personal Data, to United States and process it there.
Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.
Cafe LLC will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information.
Cafe LLC may disclose your Personal Data in the good faith belief that such action is necessary to:
The security of your data is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.
We may employ third party companies and individuals to facilitate our Service ("Service Providers"), to provide the Service on our behalf, to perform Service-related services or to assist us in analyzing how our Service is used.
These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.
Our Service may contain links to other sites that are not operated by us. If you click on a third party link, you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every site you visit.
We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.
Our Service does not address anyone under the age of 18 ("Children").
We do not knowingly collect personally identifiable information from anyone under the age of 18. If you are a parent or guardian and you are aware that your Children has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from children without verification of parental consent, we take steps to remove that information from our servers.
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
We will let you know via email and/or a prominent notice on our Service, prior to the change becoming effective and update the "effective date" at the top of this Privacy Policy.
You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.
If you have any questions about this Privacy Policy, please contact us:


BEFORE THE NATIONAL GREEN TRIBUNAL SOUTHERN ZONE AT CHENNAI Appeal No. 49 of 2013 (SZ) B E T W E E N: 1. Mr. P. Kantarao S/O P. Rangiah Pynampuram (Village) Muthukur Mandal SPSR Nellore Dist Andhra Pradesh 2. Mr. D. Nagiah S/O D. Cheeniah Nelatur (Village) Muthukur Mandal SPSR Nellore Dist Andhra Pradesh 3. Mr. G. Sreenivasulu Reddy S/O G. Subramanyam Reddy Musunuru Mandal Muthukur Mandal SPSR Nellore Dist Andhra Pradesh 4. Mr. P. Bargavamma W/O P. Vihayalaxmana Reddy Varakavipudi (Village) TP Gudur Mandal SPSR Nellore Dist, AP .... Appellants 1 AND 1. The Secretary Ministry of Environment and Forests Government of India Paryavaran Bhawan, CGO Complex Lodhi Road, New Delhi 110003 2. The Government of Andhra Pradesh Rep. by its Chief Secretary Secretariat, Hyderabad 500022 3. The Member Secretary Andhra Pradesh State Pollution Control Board Paryavaran Bhawan, A-3 Industrial Estate Sanath Nagar Hyderabad 500018. 4. The Environmental Engineer Andhra Pradesh Pollution Control Board Regional Office 1st Floor APSFC Building A.K. Nagar, Nellore 524004 5. The District Collector Nellore District Nellore 6. Andhra Pradesh Power Development Company Ltd., Rep. by its Project Manager GTS Colony, Kalyan Nagar Erragadda, Hyderabad 500045. .....Respondents 2 (Advocates appeared: M/s V. Suthakar and K.S. Viswanathan, Advocates for Appellant(s), Smt. C. Sangamithirai, Advocate for Respondent No. 1, Shri M. Govindaraj, Advocate for Respondent No. 2 and 4, Shri T. Sai Krishnan, Advocate for Respondent No. 3 and Respondent No. 4, Mr. R. Theagarajan, Sr. Counsel for Shri. D. Bharatha Charavathy, Advocate for Respondent No.6) CORAM: 1. Hon'ble Shri Justice Dr. P. Jyothimani (Judicial Member) 2. Hon'ble Prof. Dr. R. Nagendran (Expert Member) J U D G M E N T
Dated : 17th December, 2013 Judgement delivered by Hon'ble Justice Dr. P.
Jyothimani, Judicial Member
1. This appeal is directed against the communication of Respondent No. 1, the Ministry of Environment and Forests (MoEF), Government of India dated 3rd May, 2012 and the consequential order of consent given by the Andhra Pradesh Pollution Control Board (APPCB), respondent No. 3, dated 19th December, 2012, to and in favour of the respondent No. 6 and for further direction to the respondents to conduct a fresh Environmental Impact Assessment in respect of the Thermal Power 3 Project proposed by the Project proponent namely respondent No. 6 strictly in accordance with the Environmental Impact Assessment Notification 2006.
2. The Appellants are the villagers of six villages in Muthukur Mandal namely Pynapuram, Nelatur, Musunuruvaripalem, Varakavipudi, Mamidipudi & Pidatapoluru situated close to Krishnapatnam port in Nellore District. The Government of Andhra Pradesh in the year 1995 by a notification dated 2nd August, 1995 acquired 299 acres of land in survey number 117-179 in Musunuruvaripalem, Pynapuram village for providing housing colonies for the employees of Krishnapattnam Power Project. The said Thermal Power Plant requires Environmental Clearance (EC) from the MoEF as per the EIA notification 2006. As per the said Notification dated 14th September, 2006, Thermal Power Plant falls under category 'A' which includes apart from new projects, expansion and modernisation of existing projects or change in product-mix and requires prior Environmental Clearance (EC) from Central Government in the Ministry of Environment and Forest. As per the notification, it requires public hearing to be conducted at the location of the project before EC is granted.
3. The Government of Andhra Pradesh is stated to have approved the proposal for establishment of 2 x 800 MW capacity Thermal Power Plant in the above said place and thereafter the respondent No. 6 has applied for EC from respondent No.1. It is said that in accordance with the notification a public hearing was held on 6th January, 2007 by the District Collector and it is stated that in the 4 public hearing it was informed that respondent No. 6 was proposing to set up 2 x 800 MW coal based thermal power station at Melatur and Krishnapatnam in an area measuring 1270 acres. It is stated that certain objections were raised by the public. The respondent No. 1 has granted EC for the project on 17th July, 2007. As per the said clearance, it contemplates construction of an ash pond for disposal of fly ash/bottom ash to be generated during the course of generating Thermal Power and the said pond was proposed to be set up within the Thermal Power Plant area. The APPCB in the order dated 1st October, 2007 has issued consent for establishment to respondent No. 6 in respect of the said project.
4. Thereafter, respondent No. 1 is said to have considered the request of respondent No. 6 to shift the ash pond to a different location in survey No. 190 to 300 of Pynapuram village and granted permission by the impugned order dated 3rd May, 2012. According to the Appellant, the place of relocation of ash pond was originally earmarked for construction of a housing colony to the employees of the Power Plant and is situated in the midst of six thickly populated villages and such clearance for relocation has been granted by respondent No. 1 in spite of objections. It is stated by the Appellants that after many representations made by villagers, APPCB in fact had issued a notice to the respondent No. 6 not to undertake any change in location of the ash pond without prior consent from the Board. Subsequently, the APPCB, in the impugned order dated 19 th December, 2012 has issued consent for change of location of ash pond to the new site.
5
5. It is challenging the said impugned orders of the respondents No. 1 & 3, the present appeal has been filed by the Appellants on the grounds, that even as per the information of the respondent No. 6 dated 6th April, 2013, sought for by the villagers, the proposed new location of ash pond is a classified "Tank Poromboke'', that the permission for relocation has been granted not by considering the objections raised by the public, that in spite of the notice given by the respondent No. 3 APPCB, directing the respondent No. 6 not to proceed with the shifting of the ash pond to the new site by the notice dated 6th October, 2012, within nearly two months namely on 19th December, 2012, the respondent No. 3 has passed order granting permission which is illegal and arbitrary, that the clearance given by respondent No. 1 is in violation of EIA Notification, 2006, that by the impugned orders, the lands which are categorised as water body is being illegally permitted to be used for ash pond resulting in damaging the water body, that the proposal for relocation of ash pond to a place other than the original location requires a fresh EC by MoEF which is possible only after following the EIA Notification 2006 and conducting public hearing afresh for the relocation. For a change in location of the ash pond to a different area, there ought to have been a fresh Environmental Impact Assessment and therefore, the non following of the procedure is fatal to the impugned orders. It is also the case of the Appellants that the coal based thermal project in the coastal area is creating incriminating effect resulting in ecological, human disaster and that the burning of about 4 lakhs tonnes of coal everyday and spewing of 1.45 lakh tonnes per day of 6 toxic fume in the environment will emit Sulphur, Zinc, Mercury and other dangerous elements to the environment. It is also their case that the agricultural activities, ecology, water bodies, sea and health of people are endangered by the impugned order and that the act of the Government in acquiring land for the respondent No. 6 which are shown as "Tank Poromboke'' in the revenue registers and permitting it to be used as relocated fly ash pond for the project is against law and that the impugned order is against the Judgments and pronouncement of various orders of the Courts and the Tribunal.
6. In the reply filed by the 1st respondent, MoEF, it is stated that the EC was granted in accordance with the notification, that in the public proceeding held on 6th January, 2007 conducted by the APPCB, the public have overwhelmingly welcomed the power project, that as far as the original of EC granted to respondent No. 6, the project proponent is required to utilise 100 per cent of fly ash from the day of commencing of the plant, that for the ash pond which is for storage of bottom ash, the respondent 6 is required to develop a 3 tier green belt around the ash pond for arresting any fugitive emissions, that the earlier proposed location of ash pond was nearer to a water body and a creek which drained into the Buckingham Canal and therefore it was felt undesirable which necessitated the approval of the new location, that the Expert Appraisal Committee examined the proposal for change of ash pond location in its meeting held on 12th/13th September, 2011 and agreed for the proposal of respondent No. 6 for relocation, that it was thereafter, based on the Expert Appraisal Committee Report the respondent No. 1 has 7 permitted relocation under the impugned order dated 3rd May, 2012, which is well in accordance with the notification, and that the respondent No. 1 has carried out the exercise of according approval for change of location of ash pond after duly considering that the change is nowhere prejudicial to the environment at large and hence it is valid in law.
7. The respondent No. 3 APPCB in its reply while admitting that the Thermal Power Project proposed by the respondent No. 6 is covered under 'A' category of the notification, stated that the notification itself makes it clear that fresh EC is required only in the event of expansion or modernisation of the existing projects or activities listed in the Schedule to the notification with additional capacity beyond the limits specified and in the event of any change in the product mix in the existing manufacturing unit and therefore, according to respondent No. 3, the change in place of ash pond within the total area already approved does not require a fresh EC and it does not require any further public hearing.
8. It is also the case of the respondent No. 3 APPCB that the ash pond originally proposed was only an emergency ash pond and the proposed relocation is also to be established within the plant site of 1270 acres and permission was granted subject to the conditions that the ash pond water has to be recycled and should not be discharged into the sea. It is further stated that even though the representation of the villagers dated 10th September, 2012 has stated that the proposed relocation of the ash pond is situated in the midst of six villages, there was no objection raised by any one that the 8 proposed relocated place of ash pond was situated in a tank or water body. The notice issued by the respondent No. 4 on behalf of the APPCB dated 6th October, 2012 to respondent No. 6 directing not to undertake the relocation work was only to the effect that the same cannot be done without obtaining prior consent from the APPCB under Section 25 of the Water (Prevention and Control of Pollution) Act 1974 and Section 21 of the Air (Prevention and Control of Pollution) Act 1981 and therefore, the notice dated 6th October, 2012 is not a bar for subsequent issuance of consent to establish by the respondent No. 3 which was done after referring to the order of the respondent No.1 dated 3rd May, 2012 and taking note of the fact that the relocation of the ash pond by the respondent No. 6 will avoid contamination of fresh water tank adjacent to the site earlier envisaged. It is also stated that respondent No. 4 has made a site inspection of the proposed new place for establishment of the ash pond in Pyampuram Village on 7th November, 2012 and the report was placed for obtaining the consent to establish before Committee in the meeting held on 23rd November, 2012 and after detailed examination, the Committee recommended not only to extend the period of consent to establish up to 13th January, 2015 but also for the change of ash pond location subject to certain conditions. It is also stated that against order of the respondent No. 3, appellate authority is provided, and Appellate Authority's period has been extended by the Government of Andhra Pradesh in the order dated 1st July, 2013 and thereafter the Appellant cannot straightaway approach the Tribunal. It is also stated that since the proposed 9 relocated place of ash pond is situated within 1270 acres of land in respect of which EC has been given after conducting public hearing in 2007, there is no necessity for having another public hearing.
9. On behalf of respondent No. 5 the District Collector, it is stated that with regard to land for relocation by the project proponent, even though the said lands were originally classified as "Tank Poromboke'', it was reclassified later as "assessed waste" land since there was no tank in existence. In the Affidavit dated 30th July, 2013 it is stated that the Revenue Board of the erstwhile combined Madras Province has abandoned the tank as early as in the year 1924. The sanction of Revenue Board for abandoning the tank was communicated from the District Collector, Nellore in the letter dated 17th August, 1924. While paying compensation for the acquired land in the year 2006 many of the assignees were not paid compensation based on the diglot alone which was having misleading information without incorporating the above said record of 1924. It is stated that after the mistakes were identified the payment of compensation was ordered by the District Collector as per the order dated 31st August, 2010.
10. Respondent No. 6, project proponent in its reply has stated that at the outset the appeal is barred by limitation. The order of the respondent no. 1 dated 3rd May, 2012 and the consequential order dated 19th December, 2012 are challenged after the limitation period of 30 days and further condonable limit of 60 days. It is the further case of the said respondent No. 6 that when the Government of Andhra Pradesh has approved the proposal for establishing 2x800 10 MW capacity Thermal Power Plant in the name of Shri Damodaram Sanjeevaiah Thermal Power Station at Nelatur Village in the year 2006 and subsequent land acquisition proceedings were completed, a Special Purpose Vehicle in the name of the 6th respondent being a subsidiary company was floated and thereafter an application was made to the respondent No. 1 for the grant of EC. The respondent No. 1 after conducting a public hearing on 6th January, 2007 and circulating the Environmental Impact Assessment Report to the public as well as to the appropriate authorities, by the order dated 17th July 2007 has granted EC for the project subject to conditions. It is stated that based on the detailed project report, preliminary specifications were prepared and tenders were awarded for the project for which a total financial outlay was estimated at 10,450 crores and so far an expenditure of Rupees 7,900 crores has been incurred and the plant is nearing completion as per the Schedule and coal firing is to take place during September 2013 and energy production from December 2013. During the course of execution of the project more area was required for accommodating coal handling system and therefore, the originally allotted ash pond could not be continued and had to be shifted. As the movement of the ash pond could not be done either on the Western or Eastern side since it would be closer to the major water bodies at Nelatur Village Buckingham Canal, it was decided that there is a need for developing a 3 tier green belt area, and a decision was taken to relocate the ash pond on the northern side of the main plant which was originally earmarked for the proposed township area. On the basis that the shifting will avoid 11 proximity to major water bodies, respondent No.6 by a communication dated 30th May, 2011 has sought permission from the respondent No. 1 as per clause 6 of the EC already granted for relocation of the ash pond. It was after the proper detailed presentation made on 13th September, 2011, the request of the respondent No. 6 was placed before the Expert Appraisal committee of the respondent No. 1 in its meeting held on 13th September, 2011 and thereafter, by an order dated 3rd May, 2012 the respondent No. 1 has granted permission for relocation of the ash pond.
11. Based on the complaint of the appellants, respondent No.4, in the communication dated 6th October, 2012 has directed the respondent No. 6 not to proceed with the relocation before obtaining prior consent from respondent No. 3. Accordingly, the 6th respondent applied to the respondent No.3 on 6th November, 2012 and the said respondent after examining the proposal in detail, by order dated on 19th December, 2012 has granted consent. Therefore, according to the respondent No. 6, everything was done strictly in accordance with law and the work of construction of ash pond was started by levelling the land and making excavation. In the meantime, on filing the above appeal the Tribunal has granted an order of stay on 24th December, 2013. It is stated that almost the entire work has been completed. The mandatory requirement of the notification has been fully followed. The various grounds raised by the appellant have also been denied. It is also denied that there is any "Tank Poromboke'' in the proposed site where the ash pond is to be relocated. The ash pond is envisaged by way of zero effluent discharge technology in 100 acres 12 and ash particles will be pumped into the ash pond area in a semi solid state and the entire slush will settle in the pond and water stagnate above the sediment is subsequently sent to a lagoon and reused in the plant and no water will be discharged into the sea. It is stated that the project involved in borrowing of money from a German Company and another firm in New Delhi, involving payment of huge interest and therefore, everyday of delay will cost to the exchequer. Accordingly, the respondent No. 6 has prayed for dismissal of the appeal.
12. It is the submission of Mr. K.S. Vishwanathan, learned counsel appearing for the appellants that when the original Terms of Reference by the project proponent has shown the place of ash pond in 100 acres as an emergency ash pond, whenever any change of place by way of relocation was proposed the same should have been by a reference to EAC and after conducting a public hearing. Otherwise, according to him a fresh clearance is required by following procedures including the public hearing for relocation. Therefore, according to him in the absence of such clearance, the order of the MoEF in granting permission for relocation is prima facie bad and it suffers from inherent illegality. He would also contend that the impugned order of the respondent No. 1 (MoEF) is liable to be struck down on the ground of non application of mind. It is his submission that based on the original EC dated 17th July, 2007, Rs.8000/- crores have been spent and thereafter, the relocation of ash pond is proposed with the purpose of drawing water from sea for which no pipelines have been made ready. He has also submitted that the 13 project proponent has not divulged the complete details to enable the MoEF to pass orders in a proper manner and the MoEF in its turn has failed to find out the real truth in respect of relocation of ash pond independent of divulgence of correct fact by the project proponent. He also submitted that the permission granted by the Pollution Control Board after the impugned order of the MoEF is also mechanical and not by independent exercise of its power. It is his submission that when the water body was going to be dealt with, the Government should have been properly represented. On the other hand, the collector and the RDO have only acted helping the project proponent to obtain permission for relocation.
13. Per Contra, Mr. R. Theagarajan, Learned Senior Counsel appearing for respondent No. 6, project proponent contended that as per the EIA notification 2006, a fresh EC is required only in cases of expansion and modernisation of the existing project. According to him even in the original EC the place of ash pond has been stated as an emergency ash pond and the relocation is only within the entire campus demarcated for the industry and therefore, it would not amount to an expansion or modernisation. It is his further submission that as stated by the RDO and the collector, the place where the relocation of ash pond is to be made, is not a water body and the same has been entered in the earlier records by mistake which was subsequently rectified. Therefore, according to him, a fresh EC is not required and consequently the impugned order of the MoEF and the consequential order of the Pollution Control Board (PCB) cannot be held to be bad in law.
14
14. The Learned Counsel appearing for the MoEF Mrs. Sangamithirai would also reiterate her stand that the impugned order has been passed by the MoEF in accordance with the EIA Notification and in as much as the relocation of ash pond is within the area allocated for the industry and the same has been considered to be more ecologically viable by the MoEF, one cannot jump to a conclusion that the impugned order is bad in law and passed with non application of mind. That is also the contention of the Learned Counsel appearing for the Andhra Pradesh Pollution Control Board.
15. We have heard the Learned Counsel appearing for the appellant as well as the respondents elaborately and referred to various documents and given our anxious thought to the issues involved in this case.
16. The main facts are not in dispute. The respondent No. 6 was created as a Special Purpose Vehicle being a subsidiary company of Andhra Pradesh Power Generation Corporation Ltd. which has got 51 per cent of the share with the balance 49 per cent share with the Government of Andhra Pradesh and the respondent No. 6, jointly. On a proposal made by the respondent No. 6 for establishing a 2 x 800 MW capacity Thermal Power Plant at Krishnapatnam, Nellore, Andhra Pradesh, the Government has approved the same to be found in the name of Shri Damodaram Sanjeevaiah Thermal Power Station (SDSTPS) at Nelatur Village, Muthukur Mandal, Nellore District, Andhra Pradesh. An application was made by the project proponent, the respondent No. 6 by way of a proposal to the respondent No. 1 in form 1 as per the EIA notification 2006. As per the proposal, the 15 requirement of lands for the project was 1250 acres which includes land for coal conveyers and the estimated requirement of coal was 13,656 TPD. The water requirement for the project was estimated at 2, 96,400 ML per day which has to be drawn from sea. It has been stated in Form 1 by the project proponent that there is no ecologically sensitive area within 10 km from the project boundary and no forest land is involved.
17. On the basis of the said proposal, a public hearing was held in accordance with the EIA Notification 2006 of the MoEF, Government of India, on 6th July, 2007 in the elementary school at Nelatur conducted by the District Collector with the Environmental Engineer Nellure as the convenor. Admittedly, public representatives as well as the officers have participated in the public hearing and thereafter the proposal was referred as per Para 12 of EIA notification 2006, to the Expert Appraisal Committee. It is based on the report of the said Committee that the MoEF in the order dated 17th July, 2007 has granted EC to the project subject to various terms and conditions. One of the conditions contemplated in the EC issue by the MoEF reads as follows:
" Para xii. Fly ash shall be collected in Silos in dry form and bottom ash in hydro bins and its 100 per cent utilisation shall be ensured from the day of the Commission of the plant. In emergency, the unutilized fly ash/bottom ash shall be disposed off at the proposed ash disposal site through HCSD system. Borrow earth shall not be taken from ash pond area for construction of ash dyke etc."
16
18. The said EC also contains a clause which contemplates a fresh reference to the Ministry in cases of any deviation or alteration in the project proposed. It is relevant to extract the said clause of the EC for the better appreciation of the entire fact " 'Clause 6' In case of any deviation or alteration in the project proposed from those submitted to the Ministry for clearance, a fresh reference should be made to the Ministry to assess the adequacy of the conditions imposed and to incorporate additional environmental protection measures required, if any ".
A close reading of the said clause makes it abundantly clear that in cases of deviation or alteration in the project from the proposal originally submitted, a duty is contemplated on the project proponent to make a fresh reference to the Ministry. The Ministry assesses the adequacy of the conditions already imposed and incorporate additional environmental protection measures. Therefore for the purpose of the Ministry to have the benefit of a fresh reference one has to satisfy that from the original project proposal, a deviation or alteration is sought for. In the absence of the meaning of the word "deviation" or "alteration", it is to be irresistibly concluded that what is deviation or alteration of a project already proposed is subject to the satisfaction of the Ministry. If the Ministry is satisfied, for which it may always refer the proposal for deviation or alteration to the Expert Appraisal Committee if it is of category 'A' project or to the State Level Expert Appraisal Committee (SEAC) if it is of category 'B' project, and on such subjective satisfaction of the Ministry, it is 17 entitled to assess the adequacy of conditions already imposed or to incorporate additional environmental protection measures required. It is relevant to note that even in such event whether the Ministry has to issue a fresh Environment Clearance or not is not clear both in the original order of the Ministry given to the project proponent dated 17th July, 2007 and for that matter even in the Environment Clearance Regulations 2006 also.
19. However, in the Environment Clearance Regulations 2006, para 2 which deals with the requirements of prior EC, while making it clear that in respect of projects falling under category A in the schedule, it is the Central Government in the Ministry of Environment and Forest and in respect of matters falling under category B, it is the State Level Environmental Impact Assessment Authority (SEIAA), states that such authority shall confer prior EC in respect of all new projects and activities listed in the schedule, expansion and modernization of existing projects or activities listed in the schedule or any change in product mix in an existing manufacturing unit included in the schedule beyond the specified range. We feel it appropriate to extract the said paragraph number 2 which would throw light on the issue involved in this case.
" 2) Requirements of prior Environmental Clearance (EC)- The following projects or activities shall require prior environmental clearance from the concerned regulatory authority, which shall hereinafter referred to as the Central Government in the Ministry of Environment and Forests for matters falling under Category 'A' in the 18 Schedule and as State level Environment Impact Assessment Authority (SEIAA) for matters falling under Category 'B' in the said Schedule, before any construction work, or preparation of land by the project management except for securing the land, is started on the project or activity:
(i) All new projects or activities listed in the Schedule to this notification;
(ii) Expansion and modernization of existing projects or activities listed in the Schedule to this notification with addition of capacity beyond the limits specified for the concerned sector, that is, projects or activities which cross the threshold limits given in the Schedule, after expansion or modernization;
(iii) Any change in product-mix in an existing manufacturing unit included in Schedule beyond the specified range."
(emphasis supplied)
20. Therefore it is clear that deviation or alteration of the proposal as contained in the EC given to the project proponent in this case is different from expansion and modernization of existing projects etc., contemplated in the Environment Clearance Regulations 2006.
21. On the other hand to be more clear, if a project is proposed to be deviated or altered by the project proponent which mean that without expansion and modernization but within the devices and 19 mechanisms contemplated in the original proposal, such deviation or alteration does not require a fresh prior Environmental Clearance and it has to be only made as a reference to the Ministry to assess the adequacy of condition already imposed and also to decide whether new environmental protection measure ought to be incorporated as additional conditions. Consequently, such proposals or deviation or alteration which does not require fresh EC need not undergo the fresh process of grant of EC including the public hearing. On the other hand, as contemplated in paragraph 2 elicited above, if in respect of an existing project, a proposal for expansion and modernization with additional capacity which crosses the threshold limits given in the schedule after the expansion or modernisation, is deemed to be a fresh proposal which requires fresh consideration and issuance of fresh prior EC in which event necessarily it has to undergo the entire process including the public hearing.
22. Now having analysed the contents of the Environmental Clearance given to the project proponent by the Ministry dated 17th July, 2007 in relation to the conditions regarding deviation and alteration and also the provisions of Environmental Clearance regulations 2006 particularly related to expansion and modernization of project, we have to consider the facts of the present case in the above background. Since we are concerned in this case about the shifting and relocation of the ash pond, it is not necessary to go into the various aspects related to the land acquisition etc, suffice to state that the entire project for which original EC was granted by the Ministry, was contained in the area of 1250 acres. The 20 project proponent, in the communication dated 31st May, 2011 and addressed to the Ministry of Environment and Forests Government of India has stated that as per the original EC the ash pond situated in 120 acres and was located close to an existing fresh water body and saline water creek which joins Buckingham Canal and during the detailed engineering study it was found that to relocate the ash pond area away from the main project will be environmentally advantageous and therefore, requested permission from the Ministry to shift the ash pond to a place which is admittedly within the total extent of 1250 acres originally demarcated for the project township, in order to avoid proximity to existing fresh water body and water creek which joins Buckingham Canal. The said letter of the project proponent also points out that the said request was made as per clause 6 of the original Environmental Clearance dated on 17th July, 2007 elicited above. Along with the said letter, the project proponent has also enclosed some basic information more particularly about the ash pond to be relocated apart from other particulars in the communication dated 30th August, 2011.
23. As it is seen in the impugned order of the Ministry of Environment and Forest, Government of India dated 3rd May, 2012, the said request made by the project proponent was considered by the Expert Appraisal committee (Thermal Power) in its meeting held on 12th and 13th September, 2011 and made its recommendation and accordingly the Government has permitted the change of ash pond location to the new site at co-ordinates 14º 21 ' 06" North to 14º 21' 29 " North Longitudes and 80º 06 ' 58" to 80º 07 ' 45" East Latitude. 21 In fact, in the said order dated 3rd May, 2012 the Ministry has imposed further conditions which are as follows :
" xxv) The project proponent shall upload the status of compliance of the conditions stipulated in the environmental clearance issued vide this Ministry's letter of even no. dated 17th July, 2007 in its website and updated periodically and also simultaneously send the same by e-mail to the Regional Office of the Ministry of Environment and Forests.
xxvi) Criteria pollutants levels including NOX, RSPM (PM10 & PM2.5), SOX (from stack & ambient air) shall be regularly monitored and results displayed in your website and also at the main gate of the power plant.
xxvii) A three tier thick green belts on either side of the Colony and Ash Pond shall be developed to prevent fugitive emissions and status of implementation shall be reported to the Regional Office of the Ministry regularly."
24. Therefore, it is clear that the impugned order of respondent No. 1 is in terms of the original EC granted dated 17 th July, 2007 particularly para 6 as stated above by sending a new proposal for relocation of the ash pond within the original area of the entire project, which cannot be treated as a proposal for modernisation or expansion with any additional capacity beyond the limits granted in the schedule or any change in the product mix in the existing manufacturing unit which alone requires a fresh prior EC. Therefore, we are of the view that the relocation of the ash pond on the facts 22 and the circumstances of the present case cannot be treated as expansion or modernisation beyond the original capacity and therefore, it does not require a fresh Environmental Clearance from the Ministry. Consequently, there is no obligation on the part of the Ministry to direct a fresh public hearing.
25. Consequent to this conclusion, the next question which follows is as to whether there was any malafide on the part of the respondent No. 6 or non consideration of the issue by the respondent No. 1 in its proper perspective and independently. The reason mentioned for the proposed relocation of ash pond is to protect a fresh water body and creek which joins the sea. As it is seen in the impugned order the recommendation of the Expert Appraisal committee (Thermal Power) in respect of the proposal for relocation of pond has been considered by the Ministry while granting such permission. Not only that, the Government as a matter of abundant caution has directed for the development of a 3 tier thick green belt on either side of the colony and ash pond to prevent fugitive emissions and also directed the status of implementation to be informed to the Ministry. We see no malafide either on the part of respondent No. 6 or the respondent No. 1 in this regard and one can never say that the impugned order of respondent No. 1 is either devoid of merit or passed with non application of mind. There is no question of assessing technical reason in a participatory manner at the stage of consideration of alteration since it is not in the form of expansion or modernisation beyond the capacity as per the Environmental Clearance Notification 2006. The contention of the 23 Learned Counsel appearing for the appellants that the Environmental Appraisal Committee during the time when it considered the proposal for relocation of ash pond should have set up issue based manifesto is certainly not applicable at that stage.
26. There is one other issue that is raised on behalf of the appellants namely that the APPCB having issued a show cause notice on 6th October, 2012 to the project proponent has abruptly changed its stand in the impugned order dated 19th December, 2012. The said contention in our view is totally baseless. On a reference to the notice issued by the Andhra Pradesh Pollution Control Board (APPCB) dated 6th October, 2012 which is after the permission granted by the MoEF dated 3rd May, 2012, it is seen that what is stated by the APPCB in the said notice is that the project proponent should not undertake any change in location of ash pond without obtaining prior consent from the APPCB as per the Water (Prevention and Control of Pollution) Act 1974 and Air (Prevention and Control of Pollution) Act 1981. It was after the communication dated 6th November, 2012 made by the APPCB, the project proponent has stated that the consent issued by the Board originally for 5 years has expired on 30th September, 2012 and pointing out the order of the Ministry dated 3rd May, 2012 requested the Board to extent the validity of the consent to establish till 31st March, 2015 explaining various progress of works taken up by the project proponent. Thereafter, the Executive Engineer of the Pollution Control Board has filed a detailed report. Considering the detailed report of the Executive Engineer dated 17th October, 2012 and the inspection report of the regional officer dated 24 12th November, 2012 which were considered by the CFE Committee in the meeting held on 23rd November, 2012 and recommended not only the extension of the consent to establish up to 31st March, 2015 but also for relocation of the ash pond, based on which the impugned order came to be passed. In fact, the impugned order of the Pollution Control Board reiterates the conditions imposed by the MoEF, Government of India for the purpose of developing a 3 tier thick green belt to prevent fugitive emissions. In such view of the matter we hold that there is certainly no change in the attitude of the APPCB and there is no reason to come to the conclusion that the impugned order of the APPCB is malafide or one passed with non - application of mind.
27. There is one other point which has been raised in the grounds of appeal by the appellants namely that the place where the ash pond is permitted to be relocated has been shown as a "reservoir" and "Tank Poromboke" in the revenue records and therefore, permission granted to shift the ash pond of the project proponent in a water body is illegal and will affect the ecological conditions. In fact, the Learned Counsel appearing for the appellants has relied upon a decision of this Tribunal dated 20th September, 2011. That was a case where in respect of Koradi Thermal Power Project in Nagpur District of Maharashtra there was an allegation of misrepresentation of the distance between the Thermal Power Plant Project from Nagpur City as 11 kilometers which is stated to be wrong and it was in those circumstances considering the impact on the public health this Bench has made certain directions to the MoEF to 25 take note of the issue as to whether the nuclear radiations from the Thermal Power Projects can cause any cumulative affect.
28. In the affidavit filed by the Thasildar of Muthukur Mandal, Nellore District, on behalf of the respondent No. 5 dated 8th July, 2013, it was stated that an extent of 190.62 acres of patta land and 108.78 acres of Government land were handed over to the project authorities. It was also stated in the said affidavit that earlier even in the said extents of land wherever it is classified as Tank/Tank Poromboke/Channel Poromboke, they were reclassified as Assessed Waste and assigned to the eligible persons as there was no tank in existence. However, when a document from the revenue department in the form of adangal, dated 18th July, 2013 was shown where the said survey number 213/1 was stated to be a "pond poromboke", issued by another Thasildar of Muthukur Mandal, it was explained in the affidavit filed by the Revenue Divisional Officer, Nellore dated 30th July,2013 that a part of the area earmarked for relocation of ash pond included in survey number 213/1 etc are shown as Pynampuram Small Tank (Pynampuram Chinna Cheruva) as shown in the survey map. It is explained that in the original diglot maintained in the year 1908 compiled by the then British Government based on which the above said map was prepared, it was mentioned as small tank. But thereafter, by a process of law, the Revenue Board of the erstwhile Combined Madras Province in the year 1924 has abandoned the tank as communicated by the District Collector of Nellore dated 17th August, 1924. It is also stated in the said affidavit that when the land was acquired in the year 2006 and 26 question of payment of compensation was considered, many of the assignees including those lands which were abandoned in 1924 stated above were not granted compensation by referring to the above said diglot alone. It was in those circumstances the then Revenue Divisional Officer has filed an affidavit in Andhra Pradesh High Court in a Writ Petition stating that they were Government lands but cultivated by individuals. However, after the public agitation, the matter was in detailed examined by the District Collector including the 1924 records mentioned above and thereafter by an order dated 31st August, 2010 the District Collector has ordered payment of compensation to the occupants of the said survey numbers and therefore it ceased to be a water body. In such factual circumstance explained in clear terms, we are unable to accept the contention raised on behalf of the appellants that the new place of relocation of ash pond is remaining a water body. The reference made by the Learned Counsel for the applicants to the judgment of the Andhra Pradesh High Court in K. Venket Reddy Vs. Government of Andhra Pradesh and Ors., reported in 2006 (1 ALD 29) has no application to the facts of the present case especially when due process was followed as early as in the year 1924 when the tank was abandoned.
29. The further reliance placed on the judgment of the Hon'ble Supreme Court, rendered in Hinch Lal Tiwari Vs. Kamla Devi and Ors, reported in 2001(6) SCC 496) is also not applicable to the facts of the present case. That was a case where admittedly there was a consistent finding by the authorities below that the place concerned was a pond. However, the High Court has differed and it was in those 27 circumstances the Hon'ble Apex Court has made some significant observations regarding the material resources of the community. It is relevant to extract the following paragraphs of the judgment for a better appreciation of the issue involved therein which is as follows :-
"12) On this finding in our view, the High Court ought to have confirmed the order of the Commissioner. However, it proceeded to hold that considering the said report the area of 10 biswas could only be allotted and the remaining five Biswas of land which have still the character of a pond, could not be allotted. In our view, it is difficult to sustain the impugned order of the High Court. There is concurrent finding that a pond exists and the area covered by it varies in the rainy season. In such a case no part of it could have been allotted to anybody for construction of house building or any allied purposes.
13) It is important to notice that the material resources of the community like forests, tanks, ponds, hillock, mountain etc. are nature's bounty. They maintain delicate ecological balance. They need to be protected for a proper and healthy environment which enables people to enjoy a quality life which is the essence of the guaranteed right under Article 21 of the Constitution. The Government, including the Revenue Authorities i.e. Respondents 11 to 13, having noticed that a pond is falling in disuse, should have bestowed their attention to develop the same which would, on one hand, have prevented ecological disaster and on the other provided better environment for the benefit of the public at large. Such vigil is 28 the best protection against knavish attempts to seek allotment in non- abadi sites."
30. The said judgment was given on the admitted facts of the said case which in our respectful view is not applicable to the facts of the present case on hand.
31. Therefore, looking at any angle we are unable to come to a conclusion that the impugned orders of the respondent No. 1 and 3 suffer from any illegality. Accordingly, we confirm both the impugned orders as valid in law and the appeal stands dismissed. No order as to the cost.
Order delivered by the Hon'ble Judicial Member Justice Dr. P. Jyothimani on the 17th of December, 2013 from the Principal Bench New Delhi, by video conferencing and also signed by the Hon'ble Expert Member Prof. Dr. R. Nagendran at Southern Zone (Chennai) on the same day.
............................................., JM (Dr. Justice P. Jyothimani) ............................................., EM (Prof.Dr. R. Nagendran) Chennai, 17th December, 2013 29


About Me
I am learning how to make this website
1
1
Projects
This is one of of them
2
2
Education
I've taken LOTS of classes
3
3
Resume
Here's Part of My Expereince
(Working on Formating This Properly)
4
4
Contact Me
<EMAIL_ADDRESS>LinkedIn
5
5


SignalR Demo.
Navigate to Live Chart so you can see real time chart data.
Navigate to Chat and open another client to test the chat.


GameObject Class
A GameObject is an entity within a xeoEngine Scene.
Overview
See the Scene class documentation for more information on GameObjects.
Boundaries
World-space
A GameObject provides its World-space boundary as a Boundary3D that encloses the Geometry positions after transformation by the GameObject's Modelling transform.
var scene = new XEO.Scene();
var geometry = new XEO.Geometry(myScene, {
//...
});
var translate = new XEO.Translate(scene, {
xyz: [-5, 0, 0] // Translate along -X axis
});
var object = new XEO.GameObject(myScene, {
geometry: myGeometry,
transform: translate
});
// Get the World-space Boundary3D
var world = object.world;
// Get World-space object-aligned bounding box (OBB),
// which is an array of eight vertices that describes
// the box that is aligned with the GameObjectbject
var obb = world.obb;
// Get the World-space axis-aligned bounding box (ABB),
// which contains the extents of the boundary on each axis
var aabb = world.aabb;
// get the World-space center of the GameObject:
var center = world.center;
View-space
A GameObject also provides its View-space boundary as a Boundary3D that encloses the Geometry positions after their transformation by the View and Modelling transforms.
// Get the View-space Boundary3D
var view = object.view();
// Get View-space object-aligned bounding box (OBB),
// which is an array of eight vertices that describes
// the box that is aligned with the GameObjectbject
var obb = view.obb;
// Get the View-space axis-aligned bounding box (ABB),
// which contains the extents of the boundary on each axis
var aabb = view.aabb;
// get the View-space center of the GameObject:
var center = view.center;
Constructor
GameObject
-
[scene]
-
[cfg]
Parameters:
-
[scene]
Scene optional -
[cfg]
optionalConfigs
-
[id]
String optionalOptional ID, unique among all components in the parent Scene, generated automatically when omitted.
-
[meta]
String:Object optionalOptional map of user-defined metadata to attach to this GameObject.
-
[camera]
String | Camera optional -
[clips]
String | Clips optional -
[colorTarget]
String | ColorTarget optionalID or instance of a ColorTarget to attach to this GameObject. Must be within the same Scene as this GameObject. Defaults to the parent Scene's default instance, colorTarget.
-
[depthTarget]
String | DepthTarget optionalID or instance of a DepthTarget to attach to this GameObject. Must be within the same Scene as this GameObject. Defaults to the parent Scene's default instance, depthTarget.
-
[depthBuf]
String | DepthBuf optional -
[visibility]
String | Visibility optionalID or instance of a Visibility to attach to this GameObject. Must be within the same Scene as this GameObject. Defaults to the parent Scene's default instance, visibility.
-
[modes]
String | Modes optional -
[geometry]
String | Geometry optional -
[layer]
String | Layer optional -
[lights]
String | Lights optional -
[material]
String | Material optional -
[morphTargets]
String | MorphTargets optionalID or instance of a MorphTargets to attach to this GameObject. Must be within the same Scene as this GameObject. Defaults to the parent Scene's default instance, morphTargets.
-
[reflect]
String | Reflect optionalID or instance of a CubeMap to attach to this GameObject. Must be within the same Scene as this GameObject. Defaults to the parent Scene's default instance, reflection.
-
[shader]
String | Shader optional -
[shaderParams]
String | ShaderParams optionalID or instance of a ShaderParams to attach to this GameObject. Must be within the same Scene as this GameObject. Defaults to the parent Scene's default instance, shaderParams.
-
[stage]
String | Stage optional -
[transform]
String | Transform optional
-
Item Index
Properties
Methods
destroy
()
Destroys this component.
Fires a destroyed event on this Component.
Automatically disassociates this component from other components, causing them to fall back on any defaults that this component overrode on them.
error
-
message
Logs an error for this component to the JavaScript console.
The console message will have this format: [ERROR] [<component type> =<component id>: <message>
Also fires the message as an error event on the parent Scene.
Parameters:
-
message
StringThe message to log
fire
-
event
-
value
-
[forget=false]
Fires an event on this component.
Notifies existing subscribers to the event, retains the event to give to any subsequent notifications on that location as they are made.
Parameters:
-
event
StringThe event type name
-
value
ObjectThe event parameters
-
[forget=false]
Boolean optionalWhen true, does not retain for subsequent subscribers
log
-
message
Logs a console debugging message for this component.
The console message will have this format: [LOG] [<component type> <component id>: <message>
Parameters:
-
message
StringThe message to log
off
-
handle
Parameters:
-
handle
StringPublication handle
on
-
event
-
callback
-
[scope=this]
Subscribes to an event on this component.
The callback is be called with this component as scope.
Parameters:
-
event
StringThe event
-
callback
FunctionCalled fired on the event
-
[scope=this]
Object optionalScope for the callback
Returns:
Handle to the subscription, which may be used to unsubscribe with {@link #off}.
once
-
event
-
callback
-
[scope=this]
Subscribes to the next occurrence of the given event, then un-subscribes as soon as the event is handled.
This is equivalent to calling on, and then calling off inside the callback function.
Parameters:
-
event
StringData event to listen to
-
callback
Function(data)Called when fresh data is available at the event
-
[scope=this]
Object optionalScope for the callback
Properties
billboard
Component
camera
Camera
canvas
Boundary2D
final
Canvas-space 2D boundary.
If you call destroy on this boundary, then this property will be assigned to a fresh Boundary2D instance next time you reference it.
canvasBoundary
Boundary2D
final
Canvas-space 2D boundary.
If you call destroy on this boundary, then this property will be assigned to a fresh Boundary2D instance next time you reference it.
clips
Clips
colorBuf
ColorBuf
colorTarget
ColorTarget
The ColorTarget attached to this GameObject.
Must be within the same Scene as this GameObject. Defaults to the parent Scene's default colorTarget when set to a null or undefined value.
Fires a colorTarget event on change.
depthBuf
DepthBuf
depthTarget
DepthTarget
The DepthTarget attached to this GameObject.
Must be within the same Scene as this GameObject. Defaults to the parent Scene's default depthTarget when set to a null or undefined value.
Fires a depthTarget event on change.
destroyed
Boolean
True as soon as this Component has been destroyed
geometry
Geometry
glsl
JSON
final
JSON object containing the (GLSL) source code of the shaders for this GameObject.
This is sometimes useful to have as a reference when constructing your own custom Shader components.
Will return null if xeoEngine has not yet rendered this GameObject.
glslString
String
final
The (GLSL) source code of the shaders for this GameObject, as a string.
This is sometimes useful to have as a reference when constructing your own custom Shader components.
Will return null if xeoEngine has not yet rendered this GameObject.
json
JSON
final
JSON object containing the state of this Component.
layer
Layer
lights
Lights
material
Material
metadata
Object
Arbitrary, user-defined metadata on this component.
model
Boundary3D
final
Model-space 3D boundary.
If you call destroy on this boundary, then this property will be assigned to a fresh Boundary3D instance next time you reference it.
modes
Modes
morphTargets
MorphTargets
The MorphTargets attached to this GameObject.
Must be within the same Scene as this GameObject. Defaults to the parent Scene's default morphTargets when set to a null or undefined value.
Fires a morphTargets event on change.
reflect
Reflect
shader
Shader
shaderParams
ShaderParams
The ShaderParams attached to this GameObject.
Must be within the same Scene as this GameObject. Defaults to the parent Scene's default shaderParams when set to a null or undefined value.
Fires a shaderParams event on change.
stage
Stage
string
String
final
String containing the serialized JSON state of this Component.
transform
Component
The Model-to-World-space transform attached to this GameObject.
Must be within the same Scene as this GameObject. Defaults to the parent Scene's default transform (an identity matrix) when set to a null or undefined value.
Fires a transform event on change.
Updates GameObject/boundary, GameObject/worldObb and GameObject/center
type
String
final
JavaScript class name for this Component.
This is used when loading Scenes from JSON, and is included in the JSON representation of this Component, so that this class may be instantiated when loading it from the JSON representation.
For example: "XEO.AmbientLight", "XEO.ColorTarget", "XEO.Lights" etc.
view
Boundary3D
final
View-space 3D boundary.
If you call destroy on this boundary, then this property will be assigned to a fresh Boundary3D instance next time you reference it.
viewBoundary
Boundary3D
final
View-space 3D boundary.
If you call destroy on this boundary, then this property will be assigned to a fresh Boundary3D instance next time you reference it.
visibility
Visibility
The Visibility attached to this GameObject.
Must be within the same Scene as this GameObject. Defaults to the parent Scene's default visibility when set to a null or undefined value.
Fires a visibility event on change.
world
Boundary3D
final
World-space 3D boundary.
If you call destroy on this boundary, then this property will be assigned to a fresh Boundary3D instance next time you reference it.
worldBoundary
Boundary3D
final
World-space 3D boundary.
If you call destroy on this boundary, then this property will be assigned to a fresh Boundary3D instance next time you reference it.
Events
billboard
Fired whenever this GameObject's billboard property changes.
Event Payload:
-
value
ObjectThe property's new value
camera
Fired whenever this GameObject's camera property changes.
Event Payload:
-
value
ObjectThe property's new value
clips
Fired whenever this GameObject's clips property changes.
Event Payload:
-
value
ObjectThe property's new value
colorBuf
Fired whenever this GameObject's colorBuf property changes.
Event Payload:
-
value
ObjectThe property's new value
colorTarget
Fired whenever this GameObject's colorTarget property changes.
Event Payload:
-
value
ObjectThe property's new value
depthBuf
Fired whenever this GameObject's depthBuf property changes.
Event Payload:
-
value
ObjectThe property's new value
depthTarget
Fired whenever this GameObject's depthTarget property changes.
Event Payload:
-
value
ObjectThe property's new value
destroyed
Fired when this Component is destroyed.
geometry
Fired whenever this GameObject's geometry property changes.
Event Payload:
-
value
ObjectThe property's new value
layer
Fired whenever this GameObject's layer property changes.
Event Payload:
-
value
ObjectThe property's new value
lights
Fired whenever this GameObject's lights property changes.
Event Payload:
-
value
ObjectThe property's new value
material
Fired whenever this GameObject's material property changes.
Event Payload:
-
value
ObjectThe property's new value
modes
Fired whenever this GameObject's modes property changes.
Event Payload:
-
value
ObjectThe property's new value
morphTargets
Fired whenever this GameObject's morphTargets property changes.
Event Payload:
-
value
ObjectThe property's new value
picked
Fired when this GameObject is picked via a call to the Canvas/pick:method method on the parent Scene's Canvas.
Event Payload:
-
objectId
StringThe ID of this GameObject.
-
canvasX
NumberThe X-axis Canvas coordinate that was picked.
-
canvasY
NumberThe Y-axis Canvas coordinate that was picked.
picked
Fired when this GameObject is picked via a call to the Canvas/pick:method method on the parent Scene's Canvas.
Event Payload:
-
objectId
StringThe ID of this GameObject.
-
canvasX
NumberThe X-axis Canvas coordinate that was picked.
-
canvasY
NumberThe Y-axis Canvas coordinate that was picked.
reflect
Fired whenever this GameObject's reflect property changes.
Event Payload:
-
value
ObjectThe property's new value
shader
Fired whenever this GameObject's shader property changes.
Event Payload:
-
value
ObjectThe property's new value
shaderParams
Fired whenever this GameObject's shaderParams property changes.
Event Payload:
-
value
ObjectThe property's new value
stage
Fired whenever this GameObject's stage property changes.
Event Payload:
-
value
ObjectThe property's new value
transform
Fired whenever this GameObject's transform property changes.
Event Payload:
-
value
ObjectThe property's new value
visibility
Fired whenever this GameObject's visibility property changes.
Event Payload:
-
value
ObjectThe property's new value


30% of roads coordinated
40% of roads coordinated
50% of roads coordinated
100% of roads coordinated
Over 15 years


pips Red=78 White=83
(CorrectAnswer= 0/0, ErrorScore= 0)
The 50th World Backgammon Championships took place in Monte Carlo last week. The event was advertised as the 43rd Championship but that is because the numbering system went awry some years ago. Bill Robertie proved conclusively in his article on the topic last year (see https://thegammonpress.com/world-backgammon-championship-1/) that 2018 would be the 50th Championship so I will use his numbering system now and in the future. What a shame that the most famous winner of them all, Paul Magriel (1978), passed away earlier this year and could not witness the landmark occasion.
 In the history of the championship there have been four female World Champions: Carol Crawford (1973), Lee Genud (1981), Katie Scalamandre (2000) and Akiko Yazawa (2014). This year Akiko became the first woman ever to become a double World Champion. She remained unbeaten throughout the week in the double elimination event.
In the final she played Philip Kazemieh from Germany. Philip is a relative newcomer to top-level backgammon and that showed in some of his play in the final. As Philip won the defeated bracket (defeating Lawrence Powell of the UK in the final of that part of the draw) he would have to win two matches against Akikio.
The first match was to 19 points and Philip jumped out to an early 9-4 lead and looked set to force a decider. Sadly, for him from that point he would win only one more point as Akiko won the match 19-10.
The key to the turnaround occurred in this week’s position. Akiko (Black) was on roll and correctly doubled. An expert would know this is a drop. Black leads in the race and White will rarely win when he hits a shot because his board has already cracked and it could get a lot worse before he gets a shot. It was a blunder to take.
From here play continued: Black 64: 7/3, 7/1 White 21: 8/5 Black 61: 8/1 (leaving a blot). Great excitement ensued as Philip rolled 53 and hit playing, 21/18*,21/16. Akiko rolled 51 and fanned. Philip now rolled quickly a without considering a redouble. In fact, the position is a tiny drop but it is a double blunder not to redouble, you must give your opponent the chance to make an error!
Play continued White 62: 18/12, 16/14 Black 62: bar/19, 3/1. We have reached the second position above with White on roll.
Now Philip is a long way from a redouble although for money this would be a perfectly correct redouble but the match score meant he could not redouble. He rolled 53, played 14/9, 12/9. Now Akiko rolled 52 and made one of her few blunders in the match by electing to stay by playing 6/1, 5/3. She should run with 19/12 as she will only be 8 pips behind in the race. Philip now correctly redoubled to 4 and Akiko correctly took as she had both hitting and racing chances
The excitement continued when Philip rolled 52, played 9/7, 9/4, leaving a blot. There was loud cheering when Akiko rolled double ones (19/18*/15) and Philip fanned. Akiko redoubled to 8 and of course, Philip had to pass. That made the score 8-9 and from there the momentum was all with Akiko. Philip compounded his problems at 14-10 behind when he doubled far too early in a complex back game and was punished when Akiko won a gammon to lead 18-10. The match ended in the next game.
This passage of play demonstrates just how difficult match play backgammon can be. It also demonstrates how exciting it can be. The USBGF streamed the match and Falafel and friends provided the commentary which was enjoyed by thousands of people online across the world.
Congratulations also to UK players Raj Jansari, for reaching the semi-finals of the undefeated bracket, Martin Barkwill, who was part of the three-man team that won the Team Championship, and of course to Lawrence Powell on his bronze medal for finishing third.
 In the history of the championship there have been four female World Champions: Carol Crawford (1973), Lee Genud (1981), Katie Scalamandre (2000) and Akiko Yazawa (2014). This year Akiko became the first woman ever to become a double World Champion. She remained unbeaten throughout the week in the double elimination event.
In the final she played Philip Kazemieh from Germany. Philip is a relative newcomer to top-level backgammon and that showed in some of his play in the final. As Philip won the defeated bracket (defeating Lawrence Powell of the UK in the final of that part of the draw) he would have to win two matches against Akikio.
The first match was to 19 points and Philip jumped out to an early 9-4 lead and looked set to force a decider. Sadly, for him from that point he would win only one more point as Akiko won the match 19-10.
The key to the turnaround occurred in this week’s position. Akiko (Black) was on roll and correctly doubled. An expert would know this is a drop. Black leads in the race and White will rarely win when he hits a shot because his board has already cracked and it could get a lot worse before he gets a shot. It was a blunder to take.
From here play continued: Black 64: 7/3, 7/1 White 21: 8/5 Black 61: 8/1 (leaving a blot). Great excitement ensued as Philip rolled 53 and hit playing, 21/18*,21/16. Akiko rolled 51 and fanned. Philip now rolled quickly a without considering a redouble. In fact, the position is a tiny drop but it is a double blunder not to redouble, you must give your opponent the chance to make an error!
Play continued White 62: 18/12, 16/14 Black 62: bar/19, 3/1. We have reached the second position above with White on roll.
Now Philip is a long way from a redouble although for money this would be a perfectly correct redouble but the match score meant he could not redouble. He rolled 53, played 14/9, 12/9. Now Akiko rolled 52 and made one of her few blunders in the match by electing to stay by playing 6/1, 5/3. She should run with 19/12 as she will only be 8 pips behind in the race. Philip now correctly redoubled to 4 and Akiko correctly took as she had both hitting and racing chances
The excitement continued when Philip rolled 52, played 9/7, 9/4, leaving a blot. There was loud cheering when Akiko rolled double ones (19/18*/15) and Philip fanned. Akiko redoubled to 8 and of course, Philip had to pass. That made the score 8-9 and from there the momentum was all with Akiko. Philip compounded his problems at 14-10 behind when he doubled far too early in a complex back game and was punished when Akiko won a gammon to lead 18-10. The match ended in the next game.
This passage of play demonstrates just how difficult match play backgammon can be. It also demonstrates how exciting it can be. The USBGF streamed the match and Falafel and friends provided the commentary which was enjoyed by thousands of people online across the world.
Congratulations also to UK players Raj Jansari, for reaching the semi-finals of the undefeated bracket, Martin Barkwill, who was part of the three-man team that won the Team Championship, and of course to Lawrence Powell on his bronze medal for finishing third.
Cube analysis 2-ply cubeless equity +0.629 (Money: +0.629) 0.803 0.023 0.000 - 0.197 0.001 0.000 Cubeful equities: 1. Double, pass +1.000 2. Double, take +1.148 (+0.148) 3. No double +0.912 (-0.088) Proper cube action: Double, pass


Siesta is an object relational mapper for php7 build for performant database access implementing the active record pattern.
Furthermore it allows to define own plugins to generate custom coding into entity or service classes or even generate
additional classes like DTO. The database access is realized with stored procedures for all standard operations. Custom
stored procedure can be defined in xml format. Currently only drivers for for MySQL are available.
Important features:
Code Generation
Instead of writing a large generic engine with tons of code, the needed code for persistency operations
is generated from descriptions. Therefore the needed persistency footprint is very small, hence fast.
Stored Procedures insted of ad-hoc SQL
Siesta relies to 100% on Stored Procedures. The generator creates all needed stored procedures directly in the database.
In contrast to classic ad hoc sql the stored procedures are precompiled in the database which increases performance.
Furthermore custom stored procedures can be defined.
Extensibility
Code generation approaches tend to limit programmers ability to change behaviour. Therefore an
import design principle is to allow for extensibilty at every given point. Own generator plugins can be defined or
existing ones replaced or overwritten.
In Memory replication
Siesta for MySQL allows to replicate tables with a memory engine. That means the table exist twice once with the
defined engine and one with the memory engine. All modifying operations are executed on both tables. Read operations
are only performed on the memory table.
Delimiting Tables / Record History
Sometimes it is important to track changes to objects. Therefore Siesta allows to generate a second history table.
Every time the a record is changed, the changes will be stored to the history table with a valid from and valid until
entry.
code coverage report
Installation with composer
composer require gm314/siesta
Create configuration file with
vendor/bin/siesta init
SSH Clone URL : git@github.com:gperler/siesta.git
Github repository https://github.com/gperler/siesta
(1) After having installed Siesta run vendor/bin/siesta init
on the command line. It will ask you for
database connection details and generate an initial configuration file.
(2) Copy the following xml into a file called hello.entity.xml
. And place it somewhere in your
project directory. The suffix .entity.xml is important, because Siesta will by default look for all files that
end with .entity.xml. You can change this in the config file.
<entityList> <entity name="Customer" namespace="Siesta\HelloWorld" table="Customer"> <attribute name="id" type="int" dbType="INT" primaryKey="true" required="true" autoValue="autoincrement"/> <attribute name="firstName" type="string" dbType="VARCHAR(100)"/> <attribute name="lastName" type="string" dbType="VARCHAR(100)"/> <collection name="addressList" foreignTable="Address" foreignReferenceName="customer"/> </entity> <entity name="Address" namespace="Siesta\HelloWorld" table="Address"> <attribute name="id" type="int" dbType="INT" primaryKey="true" required="true" autoValue="autoincrement"/> <attribute name="name" type="string" dbType="VARCHAR(100)"/> <attribute name="customerId" dbName="fk_customer" type="int" dbType="INT"/> <reference name="customer" foreignTable="Customer" onDelete="cascade" onUpdate="cascade"> <referenceMapping localAttribute="customerId" foreignAttribute="id"/> </reference> </entity> </entityList>
(3) Run vendor/bin/siesta gen
on the command line. This will generate 4 files in the
folder src/Siesta/HelloWorld. See configuration below to change this.
<?php namespace test; use Siesta\Config\Config; use Siesta\HelloWorld\Address; use Siesta\HelloWorld\Customer; require_once 'vendor/autoload.php'; // will load database configuration Config::getInstance(); // create a new Address $address = new Address(); $address->setName("London Residence"); // create a new Customer $customer = new Customer(); $customer->setLastName("Woon"); $customer->setFirstName("Jamie"); $customer->addToAddressList($address); // true enables the cascading save. The customer including the address will be saved. $customer->save(true);
First you should use vendor/bin/siesta init
to create a config file. The command will aks for your database
connection data and test the connection. It will create a file called siesta.config.json
. If no other
config file is specified Siesta will always search for this file.
The config file generated consist of 3 parts. Connection, Generator and Reverse.
{ "connection": [ { ... } ], "generator": { ... }, "reverse": { ... } }
Most values are self explanatory. Currently there is only a MySQL driver. The driver value points to the
driver class implementing the Siesta\Database\Driver
interface. In the postConnectStatementList
you
can place several statements that are executed after connection. You can even define several connections.
The database access methods provide an optional parameter called $connectionName
If supplied you can
tell Siesta to use the specific connection. If the parameter is not set, Siesta will use the default configuration.
{ "name": "default", "driver": "Siesta\\Driver\\MySQL\\MySQLDriver", "host": "<IP_ADDRESS>", "port": 3306, "database": "siesta2", "user": "root", "password": "", "charSet": "utf8", "isDefault": null, "postConnectStatementList": [] }
The command vendor/bin/siesta gen --configFile myConfig.json
will scan the current working
directory for entity xml files and generate the PHP classes and perform database migrations. The parameter
--configFile is optional. If not supplied, Siesta will search for a file called siesta.config.json.
The generator part describes how the generator works. dropUnusedTables
tells siesta if not used
tables should be deleted or not.
The entityFileSuffix
tells Siesta for which entity files it
should look. By default it will scan your entire project directory and use all files that match the suffix.
The migrationMethod
direct
will update the database when running the command.
You can also specify the value sql
which will put alter statements into a file in the
migrationTargetPath
directory.
If you do not specify table name or dbName for columns the configures strategies tableNamingStrategy
and columnNamingStrategy
will be used to determine the names. A strategy is simply a class that
implements the Siesta\NamingStrategy\NamingStrategy
interface. You can implement your own strategy.
Just place the class name in the configuration file and make sure your strategy is autoloaded.
Available strategies are
baseDir
will tell Siesta where to put generated classes. By default paths
are deriverd psr-0 compliant from the provivide namespace. Example. If the baseDir is "src"
and the namespace is Siesta\HelloWord the class will be stored in src/Siesta/HelloWorld directory.
When specifying a targetPath
in the entity xml, the targetDirector will be
baseDir/targetPath.connectionName
for the generator. If none is supplied the default
connection will be used for generating/migratinggenericGeneratorConfiguration
allows you to totally change the way that Siesta is
generating entities and Service class. If you want to add your own code generator plugins or
remove mehtods that you don't like or just enhance them, you can copy the default configuration,
adapt the generators and have it your style. See the Generator section for
more details.
{ "dropUnusedTables": true, "entityFileSuffix": ".entity.xml", "migrationMethod": "direct", "migrationTargetPath": "migration", "tableNamingStrategy": "Siesta\\NamingStrategy\\ToUnderScoreStrategy", "columnNamingStrategy": "Siesta\\NamingStrategy\\ToUnderScoreStrategy", "baseDir": "src", "connectionName": null, "genericGeneratorConfiguration": null }
The console command vendor/bin/siesta gen --configFile myConfig.json
will reverse engineer
an existing database schema and create XML files. The --configFile parameter is optional.
The third reverse section in the config file describes how an existing schema is reverse engineered.
The targetPath
specifies where the xml should be stored. You can either place all information in one file
(singleFile
true) or create an XML file for every table. Therefore Siesta either uses the targetFile
option or
the entityFileSuffix
.
classNamingStrategy
and attributeNamingStrategy
determine how Classes and
attributes should be called based on the name of the table and the column.
Available strategies are.
Siesta\NamingStrategy\NamingStrategy
interface.defaultNamespace
allows you to specifiy which namespace should be used in the entity xml
files. The connectionName
allows to use a specific connection defined in the connection
section.
{ "targetPath": "\/reverse", "singleFile": true, "targetFile": "Reverse.xml", "entityFileSuffix": ".entity.xml", "classNamingStrategy": "Siesta\\NamingStrategy\\ToClassCamelCaseStrategy", "attributeNamingStrategy": "Siesta\\NamingStrategy\\ToCamelCaseStrategy", "defaultNamespace": null, "connectionName": null }


Live Life to its fullest Before you taste its bitrness. Dont respond to haters as they are the only ones who agree that you are Better than them.


<EMAIL_ADDRESS>uses GMAIL? login using google
OR
Proceed with your email address
By continuing, I confirm to Terms and Services and Privacy Policy of Digio.in


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 GUJARAT AT AHMEDABAD SPECIAL CIVIL APPLICATION No 2633 of 1997 -------------------------------------------------------------- NEW G.I.D.C. HOUSING ASSOCIATION Versus STATE OF GUJARAT -------------------------------------------------------------- Appearance: SUO MOTU for Petitioner MR MAULIN R RAVAL for Respondent No. 1 MR HARESH J TRIVEDI for Respondent No. 2 MR BN DOCTOR for Respondent No. 3 MR BR PARIKH for Respondent No. 4 -------------------------------------------------------------- CORAM : MR.JUSTICE B.C.PATEL and MR.JUSTICE M.S.SHAH Date of Order: 05/05/97 ORAL ORDER
The Unit was served with notice dated 30.1.1997 under section 31-A of the Air (Prevention and Control of Pollution) Act, 1981. It was noticed that the Unit had failed to provide adequate air pollution control equipment to control the emission of particulate matter SO2 and NO2 into the atmosphere. It was also noticed that the unit has failed to operate and maintain air pollution control equipment efficiently. It was further observed that the level of the noise measured at different location in the nearby residential area were ranging between 75 DBCA and 110 DBCA for which the residents of the nearby area made several complaints.
On or about 15-4-1997, the Unit was directed, with a view to reduce the propagation of noise towards the residential area, to procure green belt alongwith the periphery of the unit and go for plantation in three rows.
The Unit is directed to place on record the figures of turn over for the last three years.
S.O. to 23-6-1997.
( B.C.Patel J. ) ( M.S.Shah J. ) sharma


 So me have to ask you given much thought what if you go to place where you could die at any moment?
Chocolate i sure love that stuff wow
Vanilla
Cookies & Cream
Cookies & Cream
ReP
L
y


{% include 'bootstrap.html' %}
{% include 'navbar.html' %}
Forms
Registration
Concurrent Enrollment Petition
Over 17 Hours Petition
Course Repetition Petition
Pass/Fail Application
Foreign Language Waiver
Undergraduates Taking Graduate Classes
PDFs
Registration Form


The life records our intravenous drip, selecting precious plots, and letting us learn to treasure the love.
45 days learning in Ganesiville
This Summer, I went to University of Florida (UF) for summer intern.  During this interning time, I experienced a lot, not only the academic style in America, but also the unique culture in the countryside of Florida.
The most impressing thing in my mind is the hospitality of American friends. We were invited to the hot-pot party of the local family, and were lucky to visit the Christian church there, where I experienced many nice people who greeted with us and chatted a lot about the history there with us.
Trip to the Universal Studios
During the summer intern in USA, we also made a trip to the Universal Studios, a famous tourist attraction in Florida, as well as another place, NASA. We had a great time there. The first day after we arrived Orlando, we went to NASA first, where we learned a lot about the history and the amazing stories about the NASA. After that day, we drove to the Universal Studios. It was greatly exciting. We played a lot, and tried the Mexican food there. Very wonderful! In the last day in Orlando, we went to International Outltes for shopping. We baught a lot of clothes.
Finally, thanks to Yan and her American firends, we saved a lot of cost on the transportation. We were very thankful to them for their companying us during the trip to Orlando!
Treating Hans's friend from Thailand
In the National Holiday, our family treated a friend of my brother Hans, who comes from Thailand. We invited him to our home and treated him with traditional Chinese food, like crab, which is on season. And we also went to Tianzi Fang, where there are many traditional buildings and traditional craftsmanships, which left him and us a deep impression.
In the afternoon, we went to Oriental Pearl TV Tower to have a bird-eye view of Shanghai. We lined for a long time, but it's worth waiting after we climbed up to 293m-high floor, where the 360° view of the Bund and the HuangPu River greatly impressed us. It was really exciting.
Next month, my brother will go to Thai to visit his friend. I believe it will also be an exciting trip for him. Looking forward to that!


|
services
|
Loads a games services to the Services. More...
Public Member Functions | |
| void | Dispose () |
| void | SetServiceRegistration< RegistrationInterface > (ServiceRegistration serviceRegistration) |
| void | SetServiceRegistration (ServiceRegistration serviceRegistration, Type registrationInterface) |
| void | LoadServices (bool forceReload, Action onCompleteCallback=null) |
| void | UnloadServices () |
| void | Register< RegistrationInterface, ConcreteType > () |
| Register a service that will be instantiated from a concrete type. More... | |
| void | Register< RegistrationInterface > (RegistrationInterface service) |
| Directly register a service to a provided instance More... | |
| void | Register (Type registrationInterface, Type concreteType, int registrationGroup, ServiceResourceType resourceType=ServiceResourceType.NONE, string overrideResourcePath=null) |
Static Public Member Functions | |
| static ServiceLoader | FindOrCreate (bool disableSelfLoad=true, bool disposeAfterLoad=true) |
| static ServiceLoader | FindOrCreate< T > (bool disableSelfLoad=true, bool disposeAfterLoad=true) |
| static void | DoDefaultInitService (ServiceRegistration reg, Services loc, Action onCompleteCallback) |
Public Attributes | |
| bool | m_disposeAfterLoad = true |
| Services | m_services |
| bool | m_autoLoadOnAwake = false |
| bool | m_dieIfServicesExists = false |
Static Public Attributes | |
| static bool | DEBUG_LOAD_SERVICES = false |
| static string | RESOURCE_PATH = "Service/Services" |
Protected Member Functions | |
| Services | EnsureServicesExists () |
| virtual void | DoLoadServices (Action onCompleteCallback) |
| virtual void | BeforeLoadServices () |
| virtual void | SetServiceRegistrations () |
| virtual void | FindAutowireServiceRegistrations () |
| virtual void | FindFactoryServiceRegistrations () |
| virtual void | FindSceneServiceRegistrations () |
| virtual void | RegisterServices (ServiceRegistration[] serviceRegistrations) |
| virtual void | InitializeServices (ServiceRegistration[] serviceRegistrations, Action onCompleteCallback) |
| virtual void | DoStartServices () |
| After all services are registered in servicelocator add calls here to services you want started with app startup. More... | |
| virtual void | UnregisterServices () |
Properties | |
| bool | disposeAfterLoad [get, set] |
| Services | services [get, set] |
| static Action< ServiceLoader > | onAfterSetServiceRegistratonsStatic [get, set] |
| Use this to override default service registrations with a delegate More... | |
| Action | onAfterSetServiceRegistratons [get, set] |
| Use this to override default service registrations with a delegate. Handy for test scenarios where you don't want to have to create a whole ServiceLoader subclass. More... | |
Loads a games services to the Services.
Generally, each game should subclass ServiceLoader and override DoSetFactoryServiceRegistrations to install most services.
For services that need to be configure in the Unity scene, any gameobject that is a direct child of the ServiceLoader and has exactly one (non-transform) component, will be auto registered using the concrete type of that component as the registration interface.
Alternatively if you have a unity-configured service component but you want to use a registration interface that is NOT the component's concrete type, create a custom GenericMBServiceRegistration subclass for that component.
|
inlineprotectedvirtual |
After all services are registered in servicelocator add calls here to services you want started with app startup.
|
inline |
Directly register a service to a provided instance
|
inline |
Register a service that will be instantiated from a concrete type.
| RegistrationInterface | the interface that will be used to locate this service with calls to BeatThat.Service.Services.Locate<RegistrationInterface>(). |
| ConcreteType | The concrete type of the service. Must implement the given registration interface. If this type is a MonoBehaviour, it will be created by unity's Object.Instantiate, otherwise if will be created by its zero-arg constructor |
| ConcreteType | : | class | |
| ConcreteType | : | RegistrationInterface | |
| ConcreteType | : | new() | |
| RegistrationInterface | : | class |
|
getset |
Use this to override default service registrations with a delegate. Handy for test scenarios where you don't want to have to create a whole ServiceLoader subclass.
This executes AFTER onAfterSetServiceRegistratonsStatic
The on after service registratons.
|
staticgetset |
Use this to override default service registrations with a delegate
Handy for test scenarios where you don't want to have to create a whole ServiceLoader subclass and when you maybe don't have a handle on the ServiceLoader (maybe it doesn't exist yet).
This executes BEFORE onAfterSetServiceRegistratons
The on after service registratons.


Hello from second step
This step has a handler for the next event fired from this step only, rather than from the entire wizard.
next
This is step #3


Lextor
Sign Out
Lextor Control Unit
Motor Drive
Tab pane three. Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Ultrasonic
Tab pane three. Lorem ipsum dolor sit amet, consectetur adipiscing elit.
×
Output is Displayed Here.
Stream From Pi
Live
Made with Pingendo


Memory Game built from scratch using only HTML5, CSS3 & vanilla Javascript.
When the game starts, all cards are turned face down.
The player then flips over two cards, selecting them by clicking on them.
If the two cards have the same image, they remain face up. If not, they are flipped face down again after a short delay. When all cards on the board are facing up the timer stops and the results board pops up with top five player's names.
Created with ♥ by Lazar Kulasevic.


Use the Zeep Mobile control panel (above) to set your phone number.
Post to base; ?> from your phone with a text message like this: " hello !" Send your text to 88147.


A handy right-side text box for news, updates or maybe a profile. The choices are practically limitless for this blue box!
The rounded corners on this text box is done with CSS that was developed by Adam Kalsey.
Update: You're looking at an updated version of this design. Thanks to everyone who provided feedback for the update, especially Andreas. A list of details on what was done is listed further down.
If you're thinking to yourself that this one looks a lot like Prozac Afternoon (v1.2), you'd be right. I had an urge to use the same layout with green as the main color. Don't ask why because I don't even know myself. But people seem to be feeling it.
Grass Stains (v1.2) was tested in Windows with Firefox1.0.7, IE6.0, Netscape7.2 and Opera7.54 with valid css and xhtml 1.0-strict.
As is, download time for 56k is 5.27 seconds; ISDN 128K at 1.75 seconds; T1 at .33 seconds.
All images amount to just a touch over 23KB.
This is an open source design originally developed for the OSWD community and is free to be used and adpated as such. If you need help figuring things out or have questions about customizing this design, you can contact me through OpenWebDesign.org.
If you use this design, please drop me a line so that I can see it in action. Thanks and good luck!


Pantheon - the Temple of all the gods
Pantheon is a majestic temple and one of the best preserved ancient monuments in Europe. This powerful design takes its name from the Greek words pan - and all theoi - gods and was built just to honor the most important Roman deities. At the beginning of the seventh century has been adapted to the Christian church of Santa Maria ad Martyres - Blessed Mary of the Martyrs.
The circular structure was built on the Champ de Mars, at the behest of the emperor Hadrian in the years 118 - 125 r. Century AD, on the site of an earlier temple built a century earlier during the reign of Augustus. On the facade of the Pantheon bears a large inscription in bronze: M.AGRIPPA.LFCOS.TERTIUM.FECIT (it was build by Marcus Agrippa, son of Lucius, Consul for the third time), with the result that the builder of the temple was just a friend and son-in-Octavian Augustus, Marek Agrippa.
For the interior of the temple have large, 20-tone original doors cast in bronze.
Pantheon is housed in a small, charming square Piazza della Rotonda, full of cafes and restaurants. You can very well spend the afternoon with coffee, enjoying the wonderful view of this amazing monument of Rome which is the Pantheon.
Entrance to the Pantheon is so far free of charge; building is sometimes closed on Sunday mornings (masses).