Skip to content

Instantly share code, notes, and snippets.

View zjhiphop's full-sized avatar
🎯
Focusing

newboy zjhiphop

🎯
Focusing
74 followers · 340 following
  • cloud-tea
  • USA
View GitHub Profile
@zjhiphop
zjhiphop / Ming.md
Last active December 30, 2015 23:59
Ming relates resources

Links:

  • [LiveReload][1]
  • [iconmoon][2]
  • [big-menus-small-screens-responsive-multi-level-navigation][3]
  • [asg-web-sites][4]
  • [minglabs][5]
  • [git-ftp][6]
  • [sass-way][7]
  • [sass-source-map][8]
  • [Middle-Man-App][9]
@zjhiphop
zjhiphop / regex-answer.md
Last active January 1, 2016 00:39
Best Answer of http://regex.alf.nu/, inspired of https://gist.github.com/jpsim/8057500
  1. Plain Strings (207): foo
  2. Anchors (208): k$
  3. Ranges (202): ^[a-f]4$
  4. Backrefs (201): (...).*\1
  5. Abba (193): ^(?!.*(.)(.)\2\1)
  6. A man, a plan (177): ^(.)[^p].*\1$
  7. Prime (286): ^(?!(..+)\1+$)
  8. Four (199): (.)(.\1){3}
  9. Order (199): ^[^o]?.{5}$
  10. Triples (588): (00[039]|12|015|50)$|1..?4|4.2|1.7|6.0|006
@zjhiphop
zjhiphop / problem.md
Last active January 1, 2016 10:09
KAWO Front-end

Problems

  • When run npm install inside 'kawo_app' dir always got 'error 34'?

Resourses:

  • [sketchmine][1]
  • [sketch-vs-photoshop][2]
  • [XHR2][3]
@zjhiphop
zjhiphop / p4merge4git.md
Created January 6, 2014 14:57 — forked from tony4d/p4merge4git.md
@zjhiphop
zjhiphop / ShellRC.md
Created January 29, 2014 03:46
Shell Tips

Search path for the cd command

  • zsh 
      Search path for the cd command
  cdpath=(.. ~ ~/Documents/project ~/.zsh)
  • bash 
      export CDPATH=".:~:~/workspace"
@zjhiphop
zjhiphop / InfiniteListView.js
Created April 8, 2014 07:26 — forked from kjantzer/InfiniteListView.js
/*
Infinite List View
creates <ul> with triggers for infinite scrolling
@author Kevin Jantzer, Blacktone Audio Inc.
@since 2012-11-06
USE - listen for:
@zjhiphop
zjhiphop / ChromePackagedApps.md
Created August 1, 2014 05:35

##Chrome Packaged Apps

Introduction

Introduced at Google I/O 2012, Chrome packaged apps are a new way to develop apps that are running 'natively' within Chrome on the desktop as well as on Chrome mobile in the near future. I'm currently in the middle of a project where I develop a Chrome packaged app and in this article I would like to share my experience with the development of packaged apps.

Please note: This article should give you a basic insight of topics that I think are helpful to know for developing packaged apps. Furthermore I will give links to each topic, so you can dive deeper into that specific topic if you want to. It's not the goal of this article to act as a complete introduction to Chrome packaged apps, for a much more detailed overview of packaged apps development, please look at the official packaged app documentation.

What are Chrome Packaged Apps

Chrome packaged apps are applic

@zjhiphop
zjhiphop / log.R
Created August 6, 2014 02:15 — forked from mollietaylor/log.R
library(ggplot2)
library(scales)
# load data:
log <- data.frame(Date = c("2013/05/25","2013/05/28","2013/05/31","2013/06/01","2013/06/02","2013/06/05","2013/06/07"),
Quantity = c(9,1,15,4,5,17,18))
log
str(log)
# convert date variable from factor to date format:
@zjhiphop
zjhiphop / example-r-markdown.rmd
Created August 8, 2014 06:05 — forked from jeromyanglim/example-r-markdown.rmd
This post examines the features of [R Markdown](http://www.rstudio.org/docs/authoring/using_markdown)
using [knitr](http://yihui.name/knitr/) in Rstudio 0.96.
This combination of tools provides an exciting improvement in usability for
[reproducible analysis](http://stats.stackexchange.com/a/15006/183).
Specifically, this post
(1) discusses getting started with R Markdown and `knitr` in Rstudio 0.96;
(2) provides a basic example of producing console output and plots using R Markdown;
(3) highlights several code chunk options such as caching and controlling how input and output is displayed;
(4) demonstrates use of standard Markdown notation as well as the extended features of formulas and tables; and
(5) discusses the implications of R Markdown.
@zjhiphop
zjhiphop / chrome.md
Created August 15, 2014 03:44 — forked from 0xjjpa/chrome.md

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

Table of Contents

  1. Understand the Chrome Architecture
  2. Understand the Tabs-Extension Relationship
  3. Picking the right interface for the job