| /******This Gist explains how to create instagram like Gradient color transition in android.******/ | |
| 1. Create some gradient color drawables inside drawable Folder. | |
| a) color1.xml | |
| <?xml version="1.0" encoding="utf-8"?> | |
| <shape xmlns:android="http://schemas.android.com/apk/res/android"> | |
| <gradient | |
| android:startColor="#c44e4e" | |
| android:endColor="#dcb9b9" | |
| android:angle="0"/> |
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)
| # Install | |
| # via http://askubuntu.com/questions/510056/how-to-install-google-chrome | |
| wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - | |
| sudo sh -c 'echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list' | |
| sudo apt-get update | |
| sudo apt-get install google-chrome-stable | |
| # Update |
EMOJI CHEAT SHEET
Emoji emoticons listed on this page are supported on Campfire, GitHub, Basecamp, Redbooth, Trac, Flowdock, Sprint.ly, Kandan, Textbox.io, Kippt, Redmine, JabbR, Trello, Hall, plug.dj, Qiita, Zendesk, Ruby China, Grove, Idobata, NodeBB Forums, Slack, Streamup, OrganisedMinds, Hackpad, Cryptbin, Kato, Reportedly, Cheerful Ghost, IRCCloud, Dashcube, MyVideoGameList, Subrosa, Sococo, Quip, And Bang, Bonusly, Discourse, Ello, and Twemoji Awesome. However some of the emoji codes are not super easy to remember, so here is a little cheat sheet. ✈ Got flash enabled? Click the emoji code and it will be copied to your clipboard.
People
😄
| #AND | |
| <b:if cond='data:blog.pageType == "index"'> | |
| <b:if cond='data:blog.searchQuery'> | |
| <!--search_page AND index_page--> | |
| </b:if> | |
| </b:if> | |
| #OR |
| <?php | |
| # http://jeffreysambells.com/2012/10/25/human-readable-filesize-php | |
| function human_filesize($bytes, $decimals = 2) { | |
| $size = array('B','kB','MB','GB','TB','PB','EB','ZB','YB'); | |
| $factor = floor((strlen($bytes) - 1) / 3); | |
| return sprintf("%.{$decimals}f", $bytes / pow(1024, $factor)) . @$size[$factor]; | |
| } | |
| echo human_filesize(filesize('example.zip')); |
| /* | |
| Evaluation Of postfix Expression in C++ | |
| Input Postfix expression must be in a desired format. | |
| Operands must be integers and there should be space in between two operands. | |
| Only '+' , '-' , '*' and '/' operators are expected. | |
| */ | |
| #include<iostream> | |
| #include<stack> | |
| #include<string> |
Lately I've been doing a lot of thinking around versioning in repositories. For all the convenience and ubiquity of package.json, it does sometimes misrepresent the code that is contained within a repository. For example, suppose I start out my project at v0.1.0 and that's what's in my package.json file in my master branch. Then someone submits a pull request that I merge in - the version number hasn't changed even though the repository now no longer represents v0.1.0. The repository is actually now in an intermediate state, in between v0.1.0 and the next official release.
To deal with that, I started changing the package.json version only long enough to push a new release, and then I would change it to a dev version representing the next scheduled release (such as v0.2.0-dev). That solved the problem of misrepresenting the version number of the repository (provided people realize "dev" means "in flux day to day"). However, it introduced a yucky workflow that I really hate
| ul.tree, ul.tree ul { | |
| list-style: none; | |
| margin: 0; | |
| padding: 0; | |
| } | |
| ul.tree ul { | |
| margin-left: 10px; | |
| } | |
| ul.tree li { | |
| margin: 0; |
| Step 1: | |
| Go to: C:\Windows\System32\Drivers\etc\hosts | |
| And add this to the bottom of the file: | |
| ============= | |
| 127.0.0.1 your.domain.com | |
| ============= | |
| Step 2: | |
| Go to [your XAMPP directory]/apache/conf/httpd-xampp.conf |
