Install the following apps on your mac running macOS:
- (standalone) Xcode Command Line Tools
- Homebrew
- Git
Modified from: https://www.moncefbelyamani.com
var items = | |
[ | |
{ | |
title : 'Webview events (beforeload, load, progress, redirect)', | |
message : 'In log it should print the values', | |
functionName : Test0 | |
}, | |
{ | |
title : 'Webview events (error)', | |
message : 'In log it should print the error.', |
Install the following apps on your mac running macOS:
Modified from: https://www.moncefbelyamani.com
public abstract class Charset { | |
/** | |
* Convenience method that encodes a string into bytes in charset. | |
* <p> | |
* @param input string of Unicode characters | |
* @param charset name according to http://www.iana.org/assignments/character-sets/character-sets.xhtml | |
* @return binary characters in charset | |
*/ | |
public static Blob encode(final String input, final String charset) { |
//alloy.js | |
require("sqlite_reste_config"); | |
var localDB = require('sqlite_db'); | |
localDB.initDB(); | |
//sqlite_reste_config.js | |
Alloy.Globals.reste = require("reste"); |
git log --graph --oneline --decorate ( git fsck --no-reflog | awk '/dangling commit/ {print $3}' )
This will show you all the commits at the tips of your commit graph which are no longer referenced from any branch or tag – every lost commit, including every stash commit you’ve ever created, will be somewhere in that graph.
//Download and install widget loader : https://github.com/FokkeZB/nl.fokkezb.loading | |
Alloy.Globals.loading = Alloy.createWidget("nl.fokkezb.loading"); |
function NestedScrollViewManager (parent_view) | |
{ | |
// Appcelerator Titanium code for managing scrollviews inside of scrollviews (not true Android | |
// NestedScrollViews, but just a horizontal scrollview inside of a vertical scrollview). | |
// | |
// If you want to put a horizontal scrollview inside a vertical scrollview (like the Netflix app UI), | |
// it seems to work reasonably well on iOS. But on android, the user experience is very janky. | |
// Unless the user's drag movements are nearly exactly horizontal, there will be some movement of | |
// the parent scrollview, and then it becomes very difficult to scroll the child view. Flinging is | |
// almost impossible. |
If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.
To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.
Clone some repo (you've probably already done this step).
git clone git@github...some-repo.git