layout | author | title | revision | version | description |
---|---|---|---|---|---|
default |
mattmc3 |
Modern SQL Style Guide |
2019-01-17 |
1.0.1 |
A guide to writing clean, clear, and consistent SQL. |
- Tools > External Tools
- Add
- Settings:
- title:
Git Bash
- command:
C:\Program Files (x86)\Git\bin\sh.exe
- arguments:
--login -i
- initial directory:
$(SolutionDir)
Let's start by getting it out on the table: Sublime Text is great, and version 3 should no longer be considered "abandonware" as of build 3065. Sublime Text served me very, very well over the years. That said, trying out new things is a major part of leveling-up, and in that vein Vim deserves a go. (And have you seen some of those thoughtbot guys flying around in Vim? It's awesome!)
Getting Vim up-and-running on your Windows machine doesn't have to be an all-day project. In this post, we'll walk through:
- Installing gVim, which gives us both the "classic" command line version as well as the graphical version
- Installing Vundle, the best way to handle Vim-enhancing packages
- Installing ConEmu, a supercharged command line emulator for Windows
/** | |
* This method displays the given text on the screen. | |
*/ | |
private void displayMessage(String message) { | |
TextView priceTextView = (TextView) findViewById(R.id.price_text_view); | |
priceTextView.setText(message); | |
} |
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.