<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Minoli Perera on Medium]]></title>
        <description><![CDATA[Stories by Minoli Perera on Medium]]></description>
        <link>https://medium.com/@minoli?source=rss-2f1f8df5e138------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*5GtF099V4WS0BemsBxAA_w.jpeg</url>
            <title>Stories by Minoli Perera on Medium</title>
            <link>https://medium.com/@minoli?source=rss-2f1f8df5e138------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:24:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@minoli/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Walk-through of Cellery hub]]></title>
            <link>https://medium.com/wso2-cellery/walk-through-of-cellery-hub-d9efea66b506?source=rss-2f1f8df5e138------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9efea66b506</guid>
            <category><![CDATA[cellery-hub]]></category>
            <category><![CDATA[cellery]]></category>
            <dc:creator><![CDATA[Minoli Perera]]></dc:creator>
            <pubDate>Wed, 30 Oct 2019 16:03:55 GMT</pubDate>
            <atom:updated>2019-10-31T05:34:21.881Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b-jyZFfHScBX1ONIo5FVyw.png" /><figcaption>Cellery hub (<a href="https://hub.cellery.io/">https://hub.cellery.io/</a>)</figcaption></figure><p>Cellery hub is the central repository to store and maintain cell images which can be shared among other users. You can find and pull already built images and also push your own images to your organization. Cellery hub is accessible through <a href="https://hub.cellery.io/">https://hub.cellery.io</a>.</p><p><em>Note: If you do not have prior experience with Cellery, we suggest you to refer our </em><a href="https://wso2-cellery.github.io/"><em>Cellery site</em></a><em> and </em><a href="https://github.com/wso2-cellery/sdk"><em>documentation</em></a><em> </em>so that you will have an idea about cell images. Also, you need to install cellery to perform cellery hub login, pull and push operations.</p><p>This article will take you on a walk through on the key features of Cellery hub.</p><h4>Explore images and organizations</h4><p>You can search for public cell images or organizations from the explore page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DY3ifdp4rGArkW_DxXOQ6w.jpeg" /><figcaption>Explore — images and organizations</figcaption></figure><p>From here you can go to image overview and organization overview pages.</p><p><strong>Image Overview</strong></p><p>You can select a image to see the version list and the overview details of the cell image including Cellery commands to pull and run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Bi_uF-nMfsGCY4V8bJkJg.jpeg" /><figcaption>Image Overview</figcaption></figure><p>Select a version to see the version overview details including cell dependencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AzzzSrwKJ6plu37YWHBhLA.png" /><figcaption>Image version overview</figcaption></figure><p><strong>Organization Overview</strong></p><p>Select a organization to see the image list and the overview details of the organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fmGVwzyfyemhM_1yAZM_LQ.png" /><figcaption>Organization overview</figcaption></figure><h4>Cellery hub Login</h4><p>You can login to Cellery hub with Google or Github. When logged in you will additionally see “My Images” and “My Organization” buttons in the top navigation bar.</p><p>In my images page, you will see the images you have already pushed to cellery hub.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQiq__IyfaBmoAjnADhXlA.png" /><figcaption>My images</figcaption></figure><p>My organizations will list the organizations you are part of and provides the option to create your own organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_R9GzpWLjfAyC4ZMNMWVpA.png" /><figcaption>My Organizations</figcaption></figure><h4>Pulling images from Cellery hub</h4><p>You can pull an already built image and reuse by using the following cellery CLI command. You need not login to CLI to pull images.</p><pre>//Command<br>$<strong> cellery pull &lt;org-name&gt;/&lt;image-name&gt;:&lt;version&gt;</strong></pre><pre>//Example<br>$<strong> cellery pull wso2cellery/pet-fe-cell:latest</strong></pre><h4>Pushing images to Cellery hub</h4><p>If you want to push images to Cellery hub you need to log in to Cellery hub through CLI. Execute the below command to login.</p><pre>$ <strong>cellery login</strong></pre><p>After running this command a browser tab will open and show the Google and Github login options. After successfully login you will see the following screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pD6RjwsU6sc9_eifL38Sdw.png" /></figure><p>Now you are able to push your images to Cellery hub. If you do not have an organization at this point it will ask you to create one as it is mandatory to have a organization to push a image.</p><p>Once you are logged in through the CLI you can use the following command to push the image to your organization.</p><pre>//Command<br>$<strong> cellery push &lt;org-name&gt;/&lt;image-name&gt;:&lt;version&gt;</strong></pre><pre>//Example<br>$<strong> cellery push minoli/pet-fe-cell:lastest</strong></pre><p>Another way to push images is using a long lived access token. Login to Cellery hub through the browser and click on the user name on the top navigation bar. Go to “My Profile” page and click on “Show CLI Credentials” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCYKr_GY_ZfIiKDmgj_EsA.jpeg" /><figcaption>CLI Credentials</figcaption></figure><p>Get the user ID and access token and execute the following command to push your image.</p><pre>$ <strong>cellery push &lt;org-name&gt;/&lt;image-name&gt;:&lt;version&gt; -u &lt;user-ID&gt; -p &lt;access-token&gt;</strong></pre><p>Then go to “My Images” and “Explore” to see your recently pushed image in the listings.</p><h4>Edit/Delete images and versions</h4><p>You can edit and delete your images, versions and organizations by selecting the options from the three dot menu on the title bar. Details include organization and image summary, and description, organization URL and image keywords. When saved, these details will be updated in the relevant overview pages.</p><p>We hope you got an overview of the main features of Cellery hub and the steps to pull and push your cell images using Cellery CLI. Try it out!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9efea66b506" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wso2-cellery/walk-through-of-cellery-hub-d9efea66b506">Walk-through of Cellery hub</a> was originally published in <a href="https://medium.com/wso2-cellery">wso2-cellery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Observe your microservices with Cellery]]></title>
            <link>https://medium.com/wso2-cellery/observe-your-microservices-with-cellery-42bf3a89b666?source=rss-2f1f8df5e138------2</link>
            <guid isPermaLink="false">https://medium.com/p/42bf3a89b666</guid>
            <category><![CDATA[components]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[cellery]]></category>
            <category><![CDATA[cells]]></category>
            <category><![CDATA[observability]]></category>
            <dc:creator><![CDATA[Minoli Perera]]></dc:creator>
            <pubDate>Thu, 15 Aug 2019 09:56:48 GMT</pubDate>
            <atom:updated>2019-08-15T09:56:48.590Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0yYkIrPWwfehWtmSV7hW7Q.png" /></figure><p>Cellery Observability Dashboard provides the ability for developers, devops and architects to observe the microservices deployed on the Cellery Mesh. It shows the run-time dependencies and metrics of cells and microservices and provides the ability to trace requests to find the root cause for problems in the run-time.</p><p>Let’s take a deep dive on what you can observe with Cellery Observability Dashboard. (Please refer <a href="https://github.com/wso2-cellery/sdk/blob/master/docs/cellery-observability.md#use-cellery-dashboard">here</a> to find out how to setup the dashboard)</p><p><strong>Overview</strong></p><p>When logged in to the dashboard you will see the landing page which provides the overview details of the system. It shows the cell dependencies with health indications on cells.</p><figure><img alt="Overview of the system" src="https://cdn-images-1.medium.com/max/1024/1*MM6lihsRuiSerV-yvnEOiA.png" /><figcaption>Overview of the system</figcaption></figure><p>By looking at the overall system you able to identify the cells which has errors and warnings. The cell shows an error if the number of 5xx request of the cell exceeds 50% of it’s requests.</p><p>The right panels provides the information about the HTTP traffic of the overall system and lists cells with links to distributed tracing information. You can click on a specific cell to see cell its components and traffic details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h5WeY7Q6Ltjh9rAKf9hyqw.png" /><figcaption>Overview of the cell specific information</figcaption></figure><p><strong>Distributed Tracing</strong></p><p>The dashboard shows the traces for all requests which comes to Cellery system. You can filter out requests according to the cell, component and operation names.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vKlMF3tMUhtk7IdGO-Q8OQ.png" /><figcaption>Distributed tracing search results</figcaption></figure><p>A request can be viewed in three perspectives: timeline view, sequence diagram view, and dependency diagram view.</p><p><em>Timeline View</em></p><p>Timeline view mainly focuses on the time that the request spent on a particular operation, and hence it is easy to find out the most time consuming component and operation. Also there is an option in the timeline view, to filter out traces according to types such as components, system etc. Spans within a cell is grouped according to the cell color.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*13PMQUwGZL2Wl8N-9b2mmA.png" /><figcaption>Tracing timeline view</figcaption></figure><p><em>Sequence diagram View</em></p><p>The sequence diagram view depicts the cells and component interactions. The landing view will show the cell wise communications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6RyruW1g_aqWj0yH--lkog.png" /><figcaption>Cell level sequence diagram view</figcaption></figure><p>You can click on the request and see the drilled down view of how components within the same call communicate with each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BeJrttMqLX-szIP6gZC_3w.png" /><figcaption>Component level sequence diagram view</figcaption></figure><p><em>Request Dependency Diagram View</em></p><p>This diagram shows the path of a request. It will show the errors and the warnings of the particular request. The size of a component is proportional to the latency incurred by that component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0qdy_aHCK_K_ba28nGNbaw.png" /><figcaption><em>Request Dependency Diagram View</em></figcaption></figure><p><strong>Metrics</strong></p><p>The metrics are collected from all components and gateways, and based on this the health of a component and cell is determined. Cellery Dashboard shows Cell/Component and system metrics.</p><p><em>Cell/Component based metrics</em></p><p>The metrics can be visualized both per component and cell basis. It can be viewed from the Cell/Component overview page by clicking on metrics tab. There you will be able to see metrics for inbound and outbound requests. Also, you can select an area on the request line graphs to zoom in and you will be able to view the traces to investigate more on the specific requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_RLHFWEVzs9T5yEjkApA2Q.png" /><figcaption>Cell metrics</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HwQP5gr8EmPdymTTqx6upg.png" /><figcaption>Component metrics</figcaption></figure><p><em>System metrics</em></p><p>Cellery provides both kubernetes pod and node level metrics. It illustrates data about CPU, memory, network, and file system usage. Cellery points to the Grafana dashboard to display these metrics. You can go to a component overview, select K8S Pods and click on the metrics icon to view the options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*97k8dfzxJIGH5HffWgciYw.png" /><figcaption>Pod and node metrics select</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iuj9h6pfy3qjWESnnSjpSg.png" /><figcaption>Pod metrics</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yiLtu0pbjEit0fdTpVjmwA.png" /><figcaption>Node metrics</figcaption></figure><p><strong>Cell and Component overview</strong></p><p>You can click on the cells icon on the left navigation bar to view Cell listing which also shows the metrics summary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AON6loNL2KzklQy3D_NXlQ.png" /><figcaption>Cell listing</figcaption></figure><p>You can select on a cell and see the overview details. It contains cell wise dependency details and tabs for component listing and metrics.</p><p>From the components listing you can select a component to see the component’s overview details. It contains component wise dependency details and tabs for Pod listing and metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Aw6dIz4uhDHFYl7qTHvlQ.png" /></figure><p><strong>Other features</strong></p><p>The top tool bar contains options to generate cell colors. The cells in the dashboard is assigned with a unique color and it is used to identify the specific cell throughout the dashboard. You can generate new set of colors for the cells in case it is difficult to differentiate cell colors. Also, there is an option to share the dashboard with other users with the selected time range.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/771/1*PQuHMgYxYwE8Ptklrj6ujA.png" /><figcaption>Share dashboard option</figcaption></figure><p><strong>Conclusion</strong></p><p>Now you have covered all the main features of the Cellery dashboard. We encourage you to use Cellery Observability Dashboard to observe your microservices as it will make your life easier when determining system status and identifying and investigating on errors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42bf3a89b666" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wso2-cellery/observe-your-microservices-with-cellery-42bf3a89b666">Observe your microservices with Cellery</a> was originally published in <a href="https://medium.com/wso2-cellery">wso2-cellery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Importance of Project Management for FYPs]]></title>
            <link>https://medium.com/@minoli/importance-of-project-management-for-a-fyps-3fa26ae91b54?source=rss-2f1f8df5e138------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fa26ae91b54</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[fyp]]></category>
            <dc:creator><![CDATA[Minoli Perera]]></dc:creator>
            <pubDate>Mon, 29 Aug 2016 02:50:33 GMT</pubDate>
            <atom:updated>2016-08-29T04:11:12.054Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CEeV4jy_nnnN_OajJY9R1w.jpeg" /></figure><p>Project Management (PM) plays an important role in software lifecycle as it leads to successful competition of any project whether its a Final year project (FYP) or not. But most of the people think that PM does not have much impact on FYPs. This article will explain the importance of PM for FYPs and will brief on how to manage your project to complete it on time and obtain good grades.</p><p>According to the nature of FYPs its duration is normally within one year. It is very important to stick to a specific plan and complete the project on time to to reduce the stress that most of the students go through during the final project submission days.</p><p>PM process includes :</p><ol><li><strong>Selection of Project Management Methodology</strong></li></ol><p>Project management methodologies are used to optimize resources, to have a flow throughout project’s lifecycle with minimum wasted effort and to successfully meet project’s deadlines. Some of the problems that may occur due to not following a methodology are higher costs and risks, inefficiencies, and inability to meet deadlines.</p><p>When choosing the most suitable methodology the following points should be considered.</p><ul><li>Dividing the project into easily controllable and manageable stages.</li><li>Ability for the stakeholders to constantly get involved in reviews and feedback.</li><li>Involving principles of risk management and challenge management.</li></ul><p><strong>2. Work Breakdown Structure</strong></p><p>Work break down should be structured according to the project’s objectives.</p><p><strong>3. Resource Allocation</strong></p><p>The hardware and software requirements and development technologies and tools needed for the project should be identified.</p><p><strong>4. Time Allocation</strong></p><p>Time allocation should be done according to the workload and the complexity level in each project phase. A detailed Gantt chart should be created to plan the time utilization. It will also help to identify the progress through the project duration.</p><p><strong>5. Risk Identification and Mitigation</strong></p><p>There can be several risks arising during the project’s life cycle which can affect the success of the project, hence it is important to identify the potential risks, impact and should come up with a mitigation plan to avoid them. A simple example would be laptop crash and virus attacks, to avoid the risk should keep a regular backup of project files.</p><p><strong>6. Monitoring Criteria</strong></p><p>A Monitoring Criteria is important as it helps in understanding whether the project is satisfactorily progressing according to the plan. This can be supervised by the mentor as well as yourself.</p><p><strong>7. Selection of Software Development Methodology</strong></p><p>The methodology should be chosen according to the nature of the project and considering the possible risks that can occur during the project’s lifecycle. The main aim of carrying out a project management selection process is to select the most suitable methodology for the project. Comparison of methodologies is a must for this process.</p><p>Waterfall, Agile, Prototyping and Spiral are the most commonly used software development methodologies around the world. Since most of the FYPs are research projects, changes may occur at any phase of the process. Unlike Agile, Spiral and Prototyping, Waterfall methodology does not cater to the requirement of change management and iterative testing as testing is being done only after completing implementation phase.</p><p>Agile methodology is more suitable and useful for teamwork oriented environments where periodic updates needs to be communicated with the members. Spiral methodology has the following advantages compared to other methodologies.</p><ul><li>It is an iterative process which can adapt to changes. Since FYPs include a research part new requirements and significant changes may occur, these can be supported by the model.</li><li>Includes extensive use of prototypes to obtain users and experts feedback before the final product, this will help in producing a better solution according to the user requirements.</li><li>Testing is done iteratively it will help to reduce the number of bugs of the final product.</li><li>Risk management is given a high priority and requires documentation in intermediate stages.</li></ul><p>Working and Structuring your project according to the above points will help you in successfully completing your projects. Good Luck :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fa26ae91b54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to set up Grunt on Ubuntu— Easy steps]]></title>
            <link>https://medium.com/@minoli/how-to-set-up-grunt-on-ubuntu-easy-steps-b59b431da186?source=rss-2f1f8df5e138------2</link>
            <guid isPermaLink="false">https://medium.com/p/b59b431da186</guid>
            <category><![CDATA[task-runners]]></category>
            <category><![CDATA[grunt]]></category>
            <dc:creator><![CDATA[Minoli Perera]]></dc:creator>
            <pubDate>Mon, 01 Aug 2016 05:50:31 GMT</pubDate>
            <atom:updated>2016-08-01T06:00:14.284Z</atom:updated>
            <content:encoded><![CDATA[<p>Grunt is a JavaScript task runner which helps to perform repetitive tasks like compilation, minification, unit testing, linting, etc. It complies Sass into CSS, Compress CSS, JS, files and Combine JS files to single file.</p><p>There are couple of software dependencies to make grunt up and running.</p><ol><li>Node</li><li>npm</li><li>Grunt-CLI</li><li>Grunt</li><li>Grunt plugins</li></ol><p>Run the following Commands on your terminal from the project directory.</p><ol><li><strong>Installing node.js and node.js package manager (npm)</strong></li></ol><pre>sudo apt-get update<br>sudo apt-get install nodejs<br>sudo apt-get install npm</pre><p><strong>2. Installing Grunt-cli</strong></p><pre>npm install -g grunt-cli</pre><p><strong>3. Creating package.json</strong></p><p>This file describe project name, git repository and dependencies.</p><pre>npm init</pre><p>It will ask for project name, version, description, entry point (core file), test command, git repo, keywords, author, license. It is not mandatory to fill all the content.</p><p><strong>4. Installing Grunt</strong></p><pre>npm install grunt --save-dev</pre><p>“--save-dev” adds grunt to the list of packages in the package.json file.</p><p><strong>5. Creating gruntfile.js</strong></p><p>This file configure tasks, loads plugins, and register tasks. Task is an automated command which you can create or you can choose from 4,000 Grunt plugins.</p><p>Following is a skeleton of the grunt js file.</p><pre>module.exports = function(grunt) {   <br> // Project configuration.  <br> grunt.initConfig({<br>  pkg: grunt.file.readJSON(&#39;package.json&#39;),<br> });   </pre><pre> // Load the plugins. <br> // grunt.loadNpmTasks( );       <br> // Default task(s).  <br> // grunt.registerTask(&#39;default&#39;, [ ]); <br>};</pre><p>Fill this file according to the tasks you need to do and your up and running with grunt. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b59b431da186" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing UX for color blind users]]></title>
            <link>https://medium.com/@minoli/designing-ux-for-color-blind-users-d52dcad246a5?source=rss-2f1f8df5e138------2</link>
            <guid isPermaLink="false">https://medium.com/p/d52dcad246a5</guid>
            <category><![CDATA[color-blindness]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Minoli Perera]]></dc:creator>
            <pubDate>Mon, 25 Jul 2016 05:08:03 GMT</pubDate>
            <atom:updated>2016-07-25T05:08:03.913Z</atom:updated>
            <content:encoded><![CDATA[<p>Around 8–10% of males and 0.5% of females suffer from some form of color blindness. This means if you take 100 users around 8-10 users will see the colors in a different way. Therefore it is important to ensure that the content is accessible for all users.</p><p>Mainly there are three types of color-blindness: Red-Blind/Protanopia, Green-Blind/Deuteranopia, Blue-Blind/Tritanopia.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOsuWqQ67tfzW0DIqAIASA.jpeg" /><figcaption>Normal Color Vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HOIGT_89vdFoHSJKZCGtIg.png" /><figcaption>Protanopia : Deuteranopia : Tritanopia</figcaption></figure><p>Following tips will help to improve the experience for color-blind people which also will benefit people with normal vision.</p><ol><li><strong>Adding symbols along with colors</strong></li></ol><p>Some color blind people find it difficult or impossible to see red error messages. Hence it is important to use both colors and symbols to give a message. A Good example is Facebook sign-up form fields.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*fntUGIBh3Nu_RrUNDv8qUw.png" /></figure><p><strong>2. To show contrast use texture/patterns</strong></p><p>It can be difficult for color blind people to distinguish between bars of graphs if the bars are meant to be distinguished by colors only. It is good practice to use different patterns and textures so that even a color blond person would find it easier to understand the graph.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wbEgCW5L2kei_bEu115vNA.png" /></figure><p><strong>3. Use descriptive text for colors when required</strong></p><p>In the following scenario when choosing t-shirt colors, the color blind people find it impossible to differentiate between many of the color options available. The right on the image shows how it is seen by a person with Protanopia. Hence it is better to give the color name when the user hover on the colors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gDWSeEpOQA9j6VL0tzOtBQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d52dcad246a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A jquery plugin which add loading indicators into buttons]]></title>
            <link>https://medium.com/@minoli/a-jquery-plugin-which-add-loading-indicators-into-buttons-c63062081d07?source=rss-2f1f8df5e138------2</link>
            <guid isPermaLink="false">https://medium.com/p/c63062081d07</guid>
            <category><![CDATA[button]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[jquery]]></category>
            <category><![CDATA[plugins]]></category>
            <dc:creator><![CDATA[Minoli Perera]]></dc:creator>
            <pubDate>Mon, 25 Jul 2016 05:00:46 GMT</pubDate>
            <atom:updated>2016-08-01T04:22:47.872Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*Wub_KBO0fXoBEZedoQXKRg.png" /></figure><p>This plugin will easily help you to add loading indicators to buttons. You will need to include both the jquery.buttonLoader.js and buttonLoader.css along with bootstrap.css and font-awesome.css.</p><p><a href="https://jsfiddle.net/Minoli/zcX4h/2054/">https://jsfiddle.net/Minoli/zcX4h/2054/</a></p><h4>Instructions</h4><p>You will need to include both bootstrap.css and font-awesome.css as external resourses.</p><h4>HTML</h4><p>The buttons or links that should have the loading indication must be given the class “has-spinner”. Below is an example of a button and a link which have loading indication.</p><pre>&lt;button class=&quot;btn btn-primary my-btn <strong>has-spinner</strong>&quot;&gt;Button01&lt;/button&gt;<br>&lt;a class=&quot;btn btn-primary my-btn <strong>has-spinner</strong>&quot;&gt;Button02&lt;/a&gt;</pre><h4>Jquery</h4><p>To start loading</p><pre>$(&#39;.my-btn&#39;).buttonLoader(&#39;<strong>start</strong>&#39;);</pre><p>To stop loading</p><pre>$(&#39;.my-btn&#39;).buttonLoader(&#39;<strong>stop</strong>&#39;);</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c63062081d07" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>