Josh Peterson joshkpeterson

## arduino_gsm_hello.ino

#include <SoftwareSerial.h>
#include <string.h>

char incoming_char = 0;
SoftwareSerial cell(2, 3);


const char* commands[]={"ATZ",
"AT",

## JsonHelper.cs
using System;
using UnityEngine;

namespace UnityRest
{
    public static class JsonHelper
    {
        public static T[] FromJson<T>(string jsonArray)
        {
            jsonArray = WrapArray (jsonArray);

## fetch-from-contentful.js
#!/usr/bin/env babel-node
require('dotenv').config()
import contentful from 'contentful'
import fs from 'fs-extra-promise'

// Contentful Config
const apiToken = process.env.CONTENTFUL_DELIVERY_API_TOKEN
const spaceId = process.env.CONTENTFUL_SPACE_ID
const client = contentful.createClient({ accessToken: apiToken, space: spaceId })

## react-lifecycle-parent-child.jsx
import React from "react";
import { render } from "react-dom";

const ParentComponent = React.createClass({
  getDefaultProps: function() {
    console.log("ParentComponent - getDefaultProps");
  },
  getInitialState: function() {
    console.log("ParentComponent - getInitialState");
    return { text: "" };

## hi8-anim-howto.md

      
              1 file
            
          
              7 forks
            
          
              5 comments
            
          
              97 stars
            
          
                celoyd
                / hi8-anim-howto.md
            
            
              Last active
              August 1, 2022 15:37
            
              
                A way to make Himawari-8 animations
              
          
    Himawari-8 animation tutorial

Here’s how to make animations like this one. It requires intermediate Unix command-line knowledge, to install some tools and to debug if they don’t work. You’ll need these utilities:

curl (or you can translate to wget)
convert and montage, part of ImageMagick
ffmpeg, plus whatever codecs
parallel, for iteration that’s nicer than shell for loops or xargs
run everything in zsh for leading 0s in numerical ranges to work


## index.html
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title></title>
    <link rel="stylesheet" type="text/css" href="multiline.css">
    <script src="http://d3js.org/d3.v3.js" charset="utf-8"></script>
    <!--<script src="http://d3js.org/d3.v3.min.js" charset="utf-8"></script>-->
</head>
<body>

## README.md

      
              2 files
            
          
              24 forks
            
          
              16 comments
            
          
              144 stars
            
          
                joyrexus
                / README.md
            
            
              Last active
              June 8, 2023 07:45
            
              
                form-data vs -urlencoded
              
          
    Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.
“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data.  Otherwise, use application/x-www-form-urlencoded.”

Matt Bridges' answer in full:
The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing

  
## styles.css
/**
 * VH and VW units can cause issues on iOS devices: http://caniuse.com/#feat=viewport-units
 *
 * To overcome this, create media queries that target the width, height, and orientation of iOS devices.
 * It isn't optimal, but there is really no other way to solve the problem. In this example, I am fixing
 * the height of element `.foo` —which is a full width and height cover image.
 *
 * iOS Resolution Quick Reference: http://www.iosres.com/
 */


## noncritcss.md

      
              1 file
            
          
              10 forks
            
          
              44 comments
            
          
              215 stars
            
          
                scottjehl
                / noncritcss.md
            
            
              Last active
              August 12, 2023 16:57
            
              
                Comparing two ways to load non-critical CSS
              
          
    I wanted to figure out the fastest way to load non-critical CSS so that the impact on initial page drawing is minimal.
TL;DR: Here's the solution I ended up with: https://github.com/filamentgroup/loadCSS/

For async JavaScript file requests, we have the async attribute to make this easy, but CSS file requests have no similar standard mechanism (at least, none that will still apply the CSS after loading - here are some async CSS loading conditions that do apply when CSS is inapplicable to media: https://gist.github.com/igrigorik/2935269#file-notes-md ).
Seems there are a couple ways to load and apply a CSS file in a non-blocking manner:

  
## statify.php
<?php

/**
 * Instructions:
 *
 * 1. Put this into the document root of your Kirby site
 * 2. Make sure to setup the base url for your site correctly
 * 3. Run this script with `php statify.php` or open it in your browser
 * 4. Upload all files and folders from static to your server
 * 5. Test your site

	#include <SoftwareSerial.h>
	#include <string.h>

	char incoming_char = 0;
	SoftwareSerial cell(2, 3);


	const char* commands[]={"ATZ",
	"AT",
	using System;
	using UnityEngine;

	namespace UnityRest
	{
	public static class JsonHelper
	{
	public static T[] FromJson<T>(string jsonArray)
	{
	jsonArray = WrapArray (jsonArray);
	#!/usr/bin/env babel-node
	require('dotenv').config()
	import contentful from 'contentful'
	import fs from 'fs-extra-promise'

	// Contentful Config
	const apiToken = process.env.CONTENTFUL_DELIVERY_API_TOKEN
	const spaceId = process.env.CONTENTFUL_SPACE_ID
	const client = contentful.createClient({ accessToken: apiToken, space: spaceId })
	import React from "react";
	import { render } from "react-dom";

	const ParentComponent = React.createClass({
	getDefaultProps: function() {
	console.log("ParentComponent - getDefaultProps");
	},
	getInitialState: function() {
	console.log("ParentComponent - getInitialState");
	return { text: "" };
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<title></title>
	<link rel="stylesheet" type="text/css" href="multiline.css">
	<script src="http://d3js.org/d3.v3.js" charset="utf-8"></script>
	<!--<script src="http://d3js.org/d3.v3.min.js" charset="utf-8"></script>-->
	</head>
	<body>
	/**
	* VH and VW units can cause issues on iOS devices: http://caniuse.com/#feat=viewport-units
	*
	* To overcome this, create media queries that target the width, height, and orientation of iOS devices.
	* It isn't optimal, but there is really no other way to solve the problem. In this example, I am fixing
	* the height of element `.foo` —which is a full width and height cover image.
	*
	* iOS Resolution Quick Reference: http://www.iosres.com/
	*/
	<?php

	/**
	* Instructions:
	*
	* 1. Put this into the document root of your Kirby site
	* 2. Make sure to setup the base url for your site correctly
	* 3. Run this script with `php statify.php` or open it in your browser
	* 4. Upload all files and folders from static to your server
	* 5. Test your site