Angular-Directive-Project Directives range from very basic to extremely complex. This project will build up to some somewhat difficult directives. Keep in mind that the format we're learning for directives is the same format used to build some extremely complex things in angular. Using directives often and well is one way to show you're a talented developer. Starting Out We've included only a few things for you to begin with. index.html, app.js, styles.css. At this point the best way to get more comfortable with angular is to initialize an app without relying heavily on boilerplate code (reusable code that starts out your projects for you). You'll notice that in the index.html we've included the angular-route CDN. Yes, we'll be using angular's router here. Put an ng-view into your index.html. In your app.js set up a config and set up our first route for when a user is at the '/home' url. If you're having trouble remembering how to set up the router go look at how you set up the router on the previous project. One way these projects will be beneficial to you is allowing you to look back at something *you** did and seeing how you got that something to work.* You may also want add an otherwise that defaults to /home. Create a controller and a template file for this route in your app folder. Don't forget to include the controller as a script in your index.html Check that everything is hooked up correctly. Try adding a div with some text in your home template just to make sure it's showing up. Once you've got that going you're ready to start on some directives. Now let's make our directive. We'll start with a simple one that we can use to display information passed to it. Step 1. Start your directive Woot. When you're initializing your directive just remember that it works very similarly to how you start up a controller or a service. It can also be very helpful to think of your directive as a route. Create your directive. You'll use the directive method on your angular module. It takes two arguments, the name string and the callback function, which will return the object that represents your directive. When naming your directive give it a name with two words; dirDisplay would be nice, but anything works. Just remember it's best practice to give a directive a camel case name so that it's clear in your html what it is. Also we're going to need a template html for our directive. We could do it inline, but let's make another file instead. Just name it something that makes sense for the name of your directive and put it in the same directory as your directive file. For your template just make a <div> and inside a <h1> tag that says User. Now in your home route html add in your directive. It will look like this if you named it dirDisplay: <dir-display></dir-display> Start up your app and go to the home route. Check and make sure you see User where your directive was placed. If you're not seeing it at this point it could mean a few things. Here's some more common issues. You didn't link your directive in your index as a script. Your name for your directive doesn't match the name in your html. Remember camel case becomes snake case so myDirective becomes <my-directive></my-directive>. You're file path to your html template is wrong. You have to think of file paths in angular as relative to the index. Here's some code to see just for this part, and just for the directive's js file. var app = angular.module('directivePractice'); app.directive('dirDisplay', function(){ return { templateUrl: 'app/directives/dirDisplay.html' }; }); What we're returning is the directive object. You won't see anymore code in this tutorial so it's important you get things working right and refer back to what you've already done to advance from now on. Step 2. Advancing directives Your directive should be loaded up now, but it's not really doing much. Let's make it better. In your home controller. Make a variable on your $scope called user. Set it's value to { name: "Geoff McMammy", age: 43, email: "geofdude@gmail.com" } Now inside your directive's html specifically inside the <h3> tags display our new user's name. Then inside maybe some <h4> tags display his email and age. This is going to work exactly the same as if it was just inside your home controller. Reload the page and make sure it works. This is still very cosmetic and really not all that useful. It needs functionality. Add into your directive's object the link property. The link property's value is a function definition that takes (generally) three parameters. scope, element, and attributes. Unlike in other places with angular injection these parameter names don't carry meaning. The first parameter will always represent your $scope for that directive, the second will always be the element that wraps your whole directive, and the third will always be an object containing all the properties and values of the attributes on your directive in the dom. Try the following to get a feel for all three. Add two attributes to your directive in your html. Like this - <dir-display test="myTest" my-check="checkItOut"></dir-display> Now in the link property you've added console.log the three parameters in the function. You'll see an object for scope that should look identical to the $scope of your html function. For element you'll see an object the represents the DOM wrapper for your directive. For attributes you'll see an object that will look like this: { test: "myTest", myCheck: "checkItOut" } An important thing to notice is how it has again converted snake case to camel case for you. my-check became myCheck. Don't forget this. You'll run into this issue one day. It counts for both attributes and directive names. To feel some of what the link function could do let's try this. Add a ng-show to both the email and age wrappers. This should be familiar to you. Now inside your link function add a click event listener to your element property. It's going to look just like jQuery. element.on('click', function(){ }) Inside the click listener's callback add a toggle for the ng-show property you passed in. Along with a console.log to make sure things are connecting when you click. Try it out. Don't call for a mentor when it doesn't work. Let's talk about that first. You should see the console.log firing, but why isn't it toggling. This is going to be a common problem when working with the link function and event listeners. What we have here is an angular digest problem. The value is changing on the scope object, but the change isn't being reflected by our DOM. That's because angular isn't aware of the change yet. Anytime we cause an event to happen using something like jQuery or even angular's jQLite we need to let angular know that we've made a change. Add this line of code in place of your console.log, scope.$apply(). Now try it out. It should be working now, so if you're still having issues it's time to debug. What we've done is forced angular to run it's digest cycle. This is where angular checks the scope object for changes and then applies those to the DOM. This is another good lesson to learn for later. You'll most likely hit this when making changes to your element using event listeners. Step 3. Directive's re-usability. Now our directive has some extremely basic functionality. One of a directive's greatest advantages though is its ability to be placed anywhere and still be functional. Let's say instead we had a list of users instead of just one. Change the $scope property in your home controller to be users and give it this array as its value: [ { name: "Geoff McMammy", age: 43, email: "geofdude@gmail.com", city: "Provo" }, { name: "Frederick Deeder", age: 26, email: "fredeed@gmail.com", city: "Austin" }, { name: "Spencer Rentz", age: 35, email: "spencerrentz@gmail.com", city: "Sacramento" }, { name: "Geddup Ngo", age: 43, email: "geddupngo@gmail.com", city: "Orlando" }, { name: "Donst Opbie Leevin", age: 67, email: "gernee@gmail.com", city: "Phoenix" } ] Now in your home HTML add a ng-repeat to the directive call. Tell it to repeat for each user in users. Reload your page. It's working! But why? How does each directive instance know what information to display? In the link function console.log the scope parameter. Make sure it's outside of your click listener. You'll see five print outs in your console. Open up any one of them and look to the bottom. Open up the user property. It's exactly what we would want! But again why would that be the case? Don't get too caught up in this next bit if it's too hard to understand, but the ng-repeat is essentially making new tiny scope objects for each individual user in our users array. Now each of our directives is still getting a user property on the scope object just like the directive wanted in the beginning. Woot. Step 4. Ramp it up with Isolate Scope. Directives can do so much more. So let's make that happen. That means we should make.... a new directive!!! This directive's purpose will be to display a selected User and the weather in his/her/its location. Link it up just like the last one. Create a js file for our directive and name it dirWeather. Make an html file named dirWeather.html. Link it up in your index.html and add the template to your new directive object. In your directive's template give it an <h3> tag that says Weather just so we can know it's working. Above your ng-repeat on dirDisplay add your new dirWeather directive. If it's not working check the instructions above as to some common reasons why before asking a mentor for help. If you're seeing the Weather text on your page then we're ready to try out the dreaded Isolate Scope. The isolate scope object is one of the stranger API's in angular. I'm sorry but it is. Just refer to this for now. scope: { string: '@', link: '=', func: '&' } The properties on the scope object represent the attributes on the directive in the html. Our example scope object here would look something like this in the html. <example-directive string="a string" link="user" func="updateUser()"></example-directive> The hard part here is the @, =, and &. They each have very important and distinct meanings. @ says take in my attribute value as a string. = says take in my attribute value as a two-way bound variable from the parent scope. & says take in my attribute value as a reference to a function on the parent scope. It's also critical to point out that once you add a scope object you have no isolated your directive's scope. Meaning, aside from the values passed in through attributes, this directive has no connection to the $scope of its parent. That being said let's isolate our directive's scope. :worried: Add the scope property to your dirWeather. Give it the value of an object with a property of currentUser whose value is '='. Remember in your html this will look like current-user. This is the third time I've said so don't expect it again. This means that whatever comes into the currentUser attribute is going to be a value of the parent's scope object. For now test this out by passing in users[0]. Find a way to show that users information inside your dirWeather's html. Remember inside your directive now the user is represented by currentUser. Step 5. &? &!? The '=' value on your scope object has created a two-way binding between users[0] and currentUser. Now let's try out the '&'. On your home controller add a function called getWeather. It takes one parameter called city. This function will make a call to a service so we'll need to create that. Make a weather service. Name it something cool and creative like weatherService. Inside the weather service make a function called getWeather that also takes one parameter, city. Make an $http get to this url - 'http://api.openweathermap.org/data/2.5/weather?q=' After the q= add on the city parameter. If you want you can test this out in postman. See what kind of data you get back. If it's the weather of that city then... you win! Use $q to return a promise that only resolves with the data you want. Temperature (preferably not in Kelvin) and the weather description. Use console.log on the data coming from the $http request to get to what you want. You'll need to add both on an object that you resolve your new promise with. On your home controller have it return the result of invoking the get getWeather function on the service. You should be returning a promise. Now in your home route's HTML pass in the getWeather function to the dirWeather directive through an attribute called weather-call. Add the attribute to your isolate scope object. That was a lot of linking, but let's walk through it. Your controller has a function linked to the service, which is in turn linked to your directive. So if you run the weatherCall function in your directive it will go through your controller to your service and then back. Now things get a little bit tricky. Angular's way of passing along arguments through a directive to your controller are tricky, but once you understand how to do it, it's not hard. I'm going to give an example here of how it works. <my-directive pass-func="callFunc(data)"></my-directive> Here's how it would look in your HTML. But where's the data supposed to be coming from? It seems that you'd rather be able to pass in data from your directive. Well you still can, you just have to essentially tell angular what do use as an argument to replace data when it calls that function in your controller. The actualy function call inside the directive will look like this. $scope.passFunc({data: wantedData}) So what you'll do is pass in an object where the property name is what the argument is named in the HTML where you call the directive. That might sound confusing, but just look at the two code blocks above for a pattern. Note that pass-func becomes $scope.passFunc and data is being replaced with wantedData with the {data: wantedData} object. In our directive we want to replace city in the attribute call, for something else inside the directive. You'll follow the same pattern as above. For now let's get things set up for that function call. Add to the dirWeather directive object a property called controller. It's value will be a function. Yes, this is a controller specifically for your one directive. It works the same as any other controller, except you don't give it a name. It's $scope object will only be accessible within an instance of your directive. Don't forget to inject $scope in the function. Inside your controller function run the weatherCall function with the city property from the currentUser on your $scope. Here's where you need to make sure you've passed in a city argument in the attribute function call, and then replace that with your currentUser's city using an object with a city property. The function call should return a promise, so call .then afterward and add the data onto your $scope to display both the weather and temperature of the currentUser's city. The properties can be named whatever makes sense to you. You may also want to find a way to get rid of all the decimal places on your temperature. Now you should have everything hooked up so it shows Geoff's data and the weather data for Provo. But is that good enough? Step 6. Ramping up our ramp up. Now let's change this so it shows the weather data for whichever user we select. We're going to need to use '&' again. Make a function on the home controller that takes in a parameter and sets a property on the $scope to be that parameter. Maybe you see where this is going. We want to get this function into our dirDisplay controller. But in order to do that we need to isolate dirDisplay's scope. This also means we need to pass in each individual user through the scope object as well. To make it easier on ourselves, let's pass the current user from our ng-repeat into our directive through a user attribute. This way we can leave our two-way bindings as they are. Also pass our new function that sets our current user from our home controller into our directive through a setUser attribute. You'll need to add an argument in there again. Go with user. Your scope object in dirDisplay should have two properties. setUser with the value of '&' and user with the value of '='. As before we're going to need to do some tricky stuff to get our argument back to our controller. Call the setUser function inside our click event listener and pass in an object the sets our user argument to be the user on our directive's scope object. If you've forgotten this part go back up and take a look at how you did it before or the example in this README. Whatever user you click on now should show up in the dirWeather directive as the current user. But we're missing one thing, we want to be able to see the weather for that user too. We'll have to do one more thing that will seem a little bit tricky at first, but it's good to learn if you don't know it already since it's actually used quite frequently. We need to step up a change listener on our currentUser in the dirWeather directive. We'll use angular's $watch functionality. $watch is a method on your $scope that will watch for changes in a variable you give it. It works in two ways. $scope.$watch('property', function(value){ console.log("When $scope.property changes its new value is: ", value) }); And $scope.$watch(function(){ return myVar }, function(value){ console.log("When myVar changes its new value is: ", value); }); Remove the immediate function call that we have in there now. Maybe just comment it out for now because we'll use it in a bit. Now call the $watch method on your scope and have it watch currentUser. Either way of using $watch is fine. Have its callback run the $scope.weatherCall function just like you had it before. One thing to note is that $scope.$watch will always run once to begin with. Since that's what we want here it's great, but just be aware of that. If you've reached this point congratulate yourself. You've messed with some serious stuff today, namely directives. There are still a lot of things about directives that we can't possibly cover in a single project. If you like what we've done so far then you're in a good place to keep going. A developer who understands directives well can build a really clean looking code base. Just look at your home.html. It could have just two lines in it. If you're feeling good move on now to Step 7. Step 7. Finishing touches Try to work out these problems on your own. There should be a way to let the user know that the weather data is loading. Something that appears while our $http request is retrieving our data. The $http request shouldn't fire on both opening and closing a user's information. A color change for the currently active user would be nicer than showing that user's info inside the dirWeather modal. Or at least less redundant. Whatever else you want. We still haven't explored transclusion and ng-transclude so give that a try if you're feeling adventurous. Just know that it's a way for deciding where to put the HTML child elements of a directive. It's cool stuff that can involve some criss-crossing of scopes.

Basically an AI-powered web application able to track changes in the urban landscape.It tracks illegal constructions, local changes in the landscape.

The healthcare sector in India is intended to grow at a compounded Annual Growth Rate (CAGR) of 15 % to touch $158.2 billion in 2017 from $78.6 billion in 2012. Also healthcare spending in India was figured 5 % of gross domestic product (GDP) in 2013 and is anticipated to remain at that level through 2016. Total health care spending in local-currency terms is protruded to rise at an annual rate of over 12 %, from an estimated $96.3 billion in 2013 to $195.7 billion in 2018. While this speedy growth rate will bring back high inflation, it will also be repelled by increasing public and private expenditures on health. The healthcare industry has come a long way from the situations when patients who could afford it had to go overseas; nowadays patients from many countries are constellating to India for their medical emergencies. We know medical services in India delivered via public and private sector. However the government funds apportioned to healthcare segment have always been low in relation to the population of the country simply we can say public health care system is uneven, with underfunded and overfilled hospitals and poor rural coverage. Compromised funding by the Indian government has been ascribed to historic failures on the part of the Ministry of Health and Family Welfare (MHFW) to pay out its apportioned budget to the greatest extent. This is in spite of increasing demand, due in part, to developing incidence of age and lifestyle linked chronic disorders leading from urbanization, changing food habits and lifestyles, getting up obesity levels and far-flung tobacco products. These days India’s health care sector finds close to 50 % spend on in-patient beds for lifestyle diseases mainly urban and semi urban regions. Furthermore, various reports shows that India has world’s highest numbers of diabetes patients and has led in the mushrooming of multi specialty hospitals to battle with lifestyle disorders. The government’s low expending on health care puts much of the load on patients, as showed by the country’s out of pocket expending rate, one of the world’s highest. According to the World Health Organization (WHO) report, just 33 % of Indian health care expenditures in 2012 came from government sources. Of the leftover was out of pocket. At the same time the private sector of Indian healthcare segment, these facilities are run for profit. Medical facilities run by charitable organizations also provide medical services totally free or at minimal charges depending on the financial status of the patients. Looking at Indian healthcare market in a Pan India perspective the statistics for India’s health infrastructure are very low that of other developed countries. The United States of America has 1 bed for every 350 patients while the ratio for Japan is 1 for 85. In contrast, India has 1 bed for every 1,050 patients. To meet bed availability to the criteria of more developed countries, India requires 100,000 beds this decade, at an investment of $50 billion. Also, India’s expenditure on health care information technology is also very low. Indian hospitals will require increasing their IT spending to a great extent to provide bettered and patient-centric service. On the other side of the these facts if look at the trends of the Indian healthcare segment, over the last 40 years India has progressed a huge health infrastructure and workforce at primary, secondary and tertiary care in public, charitable and private medical centers. At present private segment range from those put up by multi specialty/ specialty corporate hospitals, nursing homes, poly clinics and clinics run by qualified medical professionals. The major portion of the private hospitals is small medical care establishments with 85% of them having less than 25 beds capacity. Private tertiary care hospitals, furnishing specialty and multispecialty medical services, account for only 1 - 2% of the total number of institutions, while corporate medical facilities make up less than 1%. The private medical services account for 82% of all out patient (OP) and 52% of inpatient (IP) services at all India level. In the recent past India is getting a favoured medical care destination for many countries due to low cost and good quality medical procedures giving rise to the scope for medical tourism. This leading more hospitals in the private segment advancing their medical facilities to land a share of this business. According to recent reports, India has a possibility to attract 1 million health tourists per annum, which could contribute $ 5 billion. The go on of this would be advance of medical facilities, in terms of new equipments, diagnostic procedures, equipments etc. Also health insurance which was absent earlier has currently going up in impressive manner. Employment scenario Medical segment in India provides direct employment to over 10 million professionals, and opportunities going to be increase in very impressive manner; the employment opportunities are not just limited to doctors and nurses. This profession would need a good number of paramedical professionals and more importantly a large number of mid and senior level managers and with expertise across various specialties’. According to the National Skill Development Corporation(NSDC), "By 2022, India would need 74 lakh medical service workforce” Besides, the size of the healthcare sector is anticipated to grow to Rs 9.64 lakh crore by 2017. With many and different medical services, there are over 10 lakh allied health professionals in India in the areas of nursing associates, medical assistants, medical equipment operators, optometrists, physiotherapists, dieticians, dental assistants, and many other which is still short of the current necessitate. Also there is a significant gap in the availability of medical practitioners and it is a trend that is likely to continue for next few years. Currently India’s ratio of 0.7 doctors & 1.5 nurses per 1,000 people is dramatically lower than the WHO average of 2.5 doctors and nurses per 1,000 people. Moreover, there is an acute shortage of paramedical and administrative professionals. There are over 7,50,000 registered Ayurveda, Yoga, Unani, Siddha and Homoeopathy practitioners in the country. These numbers, when joined with the total number of physicians shaped in allopathy, satisfy to an extent, the total requirement of medical practitioners required in the country," NSDC predictions”. To conclude, "India has become one of the most favoured or affordable destinations for patients looking for best healthcare care at cost much lower than that of other countries”. India can further leverage its status as a fairly priced and quality medical care provider, as result providing to a greater proportion of world population. "Therefore, there is urgency for both qualitative and quantitative skill development programs in the medical segment also policy designers and industry players need to concentrate on advancing technical skills of the clinical and non clinical medical professionals for progressed medical care services".

Changing Seas, Changing Strategies for advancing long-term biodiversity conservation through MPA networks in Canada

Changing and Advancing the Backend from Express to Nest js

Capable home advance credit planning is transforming into a testing errand for the home advance advancing industry with the unfaltering need to stay mindful of new managerial consistence measures, high costs, changing headways and all the more firmly spending arranges. Invensis offers you trustworthy and exhibited home advance business process outsourcing organizations that can effectively improve your execution. Invensis contract advance get ready outsourcing organizations license you to free yourself from the troubles of separating, evaluating and taking care of the voluminous data associated with home credits.

Empowering Women for a Digital India: 333 Rachna.com The founder of 333Rachna.com, Mrs. Rachna Sharma has a unique vision for women worldwide. A pioneer in the field of real estate digitalization, making the transition to a paperless business 333acre.com has been led by her, changing the way people do business from surveying the markets to registration, learning about circle rates and completing online transactions. Moving towards a cashless economy under the inspiring vision of Prime Minister Shri Narendra Modi’s Digital India launched in September 2015, 333Rachna.com works towards a new era of women empowerment. Advancing towards a digital payments economy, India is one of the world’s largest economies to do so. 333Rachna.com aims to work towards making Digital India a reality for women in different spheres

Innovations in Warehousing Transforming over time from godowns to warehouses, warehouses have grown to become the backbone of the manufacturing and the service industry. In the old times, warehouses meant humongous spaces managed by a huge manpower. There have been businesses that have been solely dependent on managing warehouses. Today, the very nature of handling such spaces is changing. With supply chain getting advanced and evolved over time, warehousing is on a continuous improvement process. Today, the amount of material handling, demands use of automation instead of a large workforce to save on labour costs and on-time distribution. Specially in the manufacturing industry, with lean manufacturing and lean inventory becoming the aim, having sophisticated material handling systems has become the need of the hour. Similarly, growing consumerism has led to ever increasing amount of logistics handling in the service sector, for which proper warehousing stands crucial for effective growth. Warehousing in India India- The changing scenario Now, if we go through the past and the current scenario of Indian industry we can specifically note some changes over the period of time. Demand for modern and sophisticated warehouses has witnessed a tremendous increase in India in last few years because of influx of multinational companies as well as export-oriented companies who are ready to invest in the warehouse infrastructure. Need for large scale warehousing or dedicated logistics parks is fast catching up in India as it is mostly fragmented and unorganised industry dominated by many small players. Also, the role of warehouses has increased due to wider product range, emphasis on shorter lead times and constant changes in customer demand with changing dynamics of the country. In the recent study done by World Bank, India has jumped 19 positions in the Logistics Performance Index (LPI) which means India is on the growth path as far as the Logistics handling capacity is considered. Also, in 2017, India made the highest ever jump to come within the top 100 countries in the “Ease of Doing Business’ index of the World Bank. This indicates that, India is preferred by the world leaders to set up their businesses keeping in view the ability India withholds. Although India is on the path of technological advancement, it needs more efforts to be taken to be at par with the other developed countries higher up the order. Out of the many fields, warehousing and logistics management is one such important field that needs attention. The greater investment opportunity in the warehousing sector will offer a better investment return and lead to the growth of business in India. The warehouse industry in India is growing at a rate of 10 percent every year. Considering the current scenario, the growth in Indian warehouse industry is led by various factors, prominent amongst them are:- growth of manufacturing, engineering and service industry; growth of e-commerce, e-retail, digitization, government thrust on cashless economy; growing load of domestic consumption; fast growing exports and international trade; Growth in private and foreign investments with government’s Make in India Campaign; Introduction of GST integrating India into a unified market; Increase in trade through foreign investments in the SEZs(Special Economic Zones) Growth in openness of the Indian economy and market integration; According to studies, Indian logistics market is expected to grow at a CAGR of 12.17% by 2020 driven by the growth in the manufacturing, retail, FMCG and e-commerce sectors. About 80% handling and warehousing facilities are not mechanized and traditional manual methods clearly indicate that there is an acute shortage of organized and good quality warehousing. Why innovating in warehousing is crucial? The major reasons that indicate innovating in warehousing and logistics management is crucial can be comprehended as follows- Labour Problems- Labour in India though available in large number as well as being cheap, it is illiterate and highly unskilled. Compared to other countries, labour in India are not capable of receiving advanced industrial training, understanding problems in industries and working towards its own interest and those of nation as a whole. Hence, there are issues of labour union, regulation issues and differences between labour unions and company management. Another issue is the inadequate facilities available at the training centers because of which the percentage of trained workers in Indian industry is very low. Bulky Material- Industries like textile, iron and steel industry etc. handle huge quantity of bulky material every day. A large workforce is required to handle such huge quantity and managing such a large workforce requires efficient managers. This increases labour costs, material handling costs, inventory costs and demands huge space for storage. Environment issues- With mass productivity being the prime moto today, industries face problems of space availability, land issues etc. Sometimes challenging environment to work in like in cold storages, high work temperature areas also hinder the productivity of workers. In such cases replacing man with machines can be a boon. Solution to problems of Warehousing Automation and optimization are key to Innovations in warehousing. Harnessing the power of technology and maximizing a facility's potential can help overcome the drawbacks. This demands companies to improve their warehousing facilities and advancing their logistics handling with efficient supply chain management environment. One such expert in material handling solutions and logistics management is Daifuku. Daifuku, provides its expertise in utilizing the warehouse space optimally with its custom-made solutions. Daifuku’s AS/RS helps pace up the movement and use the right amount of space with the least human dependency. A final word Innovations in warehousing will most certainly help achieve improved operating efficiency, cut cycle time, prevent material handling loss and provide controlled access. Daifuku’s products such as AS/RS, Unit Load AS/RS, Mini Load AS/RS, Racking Systems help deliver speed and efficiency for today’s supply chain management (SCM) environment. Daifuku caters to all types of customer needs and designs and builds ensuring high quality and long-term reliability.