Dániel Vámosi danielvamosi

## .block
license: gpl-3.0
height: 1030
scrolling: yes

## index.html
<!doctype html>
<meta charset="utf-8">
<body>
<script src="//d3js.org/d3.v4.min.js"></script>
<script>

let margin = {top: 100, right: 100, bottom: 100, left: 100};

let width = 960,
    height = 500,

## destructuring.md

      
              1 file
            
          
              31 forks
            
          
              20 comments
            
          
              264 stars
            
          
                yang-wei
                / destructuring.md
            
            
              Last active
              July 4, 2024 16:56
            
              
                Elm Destructuring (or Pattern Matching) cheatsheet
              
          
Should be work with 0.18

Destructuring(or pattern matching) is a way used to extract data from a data structure(tuple, list, record) that mirros the construction. Compare to other languages, Elm support much less destructuring but let's see what it got !
Tuple

myTuple = ("A", "B", "C")
myNestedTuple = ("A", "B", "C", ("X", "Y", "Z"))

  
## .block
license: gpl-3.0

## install_ex.sh
#!/bin/sh

# I use this to install Elixir on our codeship instances for testing. YMMV.
# curl -O https://gist.githubusercontent.com/jamesotron/44f8962cddef781ab830/raw/e75599e95587cbca26e707505fd40dd0f26eb0f5/install_ex.sh
# . ~/install_ex.sh

# You can override your Elixir and Erlang versions from your shell when you call ./install_ex.sh.
export ERLANG_VERSION=${ERLANG_VERSION:-18.0.3}
export ELIXIR_VERSION=${ELIXIR_VERSION:-1.0.5}

## erlang_notes
Loading modules
---------------

Purging = removing the old version of the module (so that it will only have a new
version).

erlang:check_old_code(mymodule).
    Return if the module has an old version loaded.
code:load_file(mymodule).
code:load_abs("/home/me/mymodule"). % no ".beam"

## README.md

      
              2 files
            
          
              7 forks
            
          
              2 comments
            
          
              7 stars
            
          
                will-hart
                / README.md
            
            
              Last active
              March 22, 2024 04:55
            
              
                Stitch together tilemaps into a single image
              
          
    Why?

This is a simple Python / PIL utility for taking a series of images in a tile map set and stitching them together
into a single image. This is being used to convert these http://forums.bistudio.com/showthread.php?178671-Tiled-maps-Google-maps-compatible-(WIP)
for www.anvilproject.com.
How?


Drop the stitcher.py file into the root directory of your tile map set, where all the numbered folders are
Edit two lines in the file, these are commented - one for the number of folders and one for the number of images in each folder


## gist:cba5dbf7653d7eab6a03
F = fun(F, Fd) -> receive stop -> io:format(Fd, "stop~n", []), file:close(Fd), ok; Msg -> io:format(Fd, "~p~n", [Msg]), F(F, Fd) end end.
{ok, Fd} = file:open("/tmp/trace.out", [write]), Tracer = proc_lib:spawn(fun() -> F(F, Fd) end).

%% trace everything
erlang:trace(Pid, true, [all, {tracer, Tracer}]).
%% stop tracing
erlang:trace(Pid, false, [all, {tracer, Tracer}]).
Tracer ! stop.

%% match pattern

## WebSockets.md

      
              1 file
            
          
              32 forks
            
          
              17 comments
            
          
              211 stars
            
          
                subudeepak
                / WebSockets.md
            
            
              Last active
              May 31, 2024 09:36
            
              
                The problems and some security implications of websockets - Cross-site WebSockets Scripting (XSWS)
              
          
    WebSockets - An Introduction

WebSockets is a modern HTML5 standard which makes communication between client and server a lot more simpler than ever. We are all familiar with the technology of sockets. Sockets have been fundamental to network communication for a long time but usually the communication over the browser has been restricted. The general restrictions

The server used to have a permanent listener while the client (aka browser) was not designated any fixed listener for a more long term connection. Hence, every communication was restricted to the client demanding and the server responding.
This meant that unless the client requested for a particular resource, the server was unable to push such a resource to the client.
This was detrimental since the client is then forced to check with the server at regular intervals. This meant a lot of libraries focused on optimizing asynchronous calls and identifying the response of asynchronous calls. Notably t


## xmerl_demo.ex
defmodule XmlNode do
  require Record
  Record.defrecord :xmlAttribute, Record.extract(:xmlAttribute, from_lib: "xmerl/include/xmerl.hrl")
  Record.defrecord :xmlText, Record.extract(:xmlText, from_lib: "xmerl/include/xmerl.hrl")

  def from_string(xml_string, options \\ [quiet: true]) do
    {doc, []} =
      xml_string
      |> :binary.bin_to_list
      |> :xmerl_scan.string(options)
	<!doctype html>
	<meta charset="utf-8">
	<body>
	<script src="//d3js.org/d3.v4.min.js"></script>
	<script>

	let margin = {top: 100, right: 100, bottom: 100, left: 100};

	let width = 960,
	height = 500,
	#!/bin/sh

	# I use this to install Elixir on our codeship instances for testing. YMMV.
	# curl -O https://gist.githubusercontent.com/jamesotron/44f8962cddef781ab830/raw/e75599e95587cbca26e707505fd40dd0f26eb0f5/install_ex.sh
	# . ~/install_ex.sh

	# You can override your Elixir and Erlang versions from your shell when you call ./install_ex.sh.
	export ERLANG_VERSION=${ERLANG_VERSION:-18.0.3}
	export ELIXIR_VERSION=${ELIXIR_VERSION:-1.0.5}
	Loading modules
	---------------

	Purging = removing the old version of the module (so that it will only have a new
	version).

	erlang:check_old_code(mymodule).
	Return if the module has an old version loaded.
	code:load_file(mymodule).
	code:load_abs("/home/me/mymodule"). % no ".beam"
	F = fun(F, Fd) -> receive stop -> io:format(Fd, "stop~n", []), file:close(Fd), ok; Msg -> io:format(Fd, "~p~n", [Msg]), F(F, Fd) end end.
	{ok, Fd} = file:open("/tmp/trace.out", [write]), Tracer = proc_lib:spawn(fun() -> F(F, Fd) end).

	%% trace everything
	erlang:trace(Pid, true, [all, {tracer, Tracer}]).
	%% stop tracing
	erlang:trace(Pid, false, [all, {tracer, Tracer}]).
	Tracer ! stop.

	%% match pattern
	defmodule XmlNode do
	require Record
	Record.defrecord :xmlAttribute, Record.extract(:xmlAttribute, from_lib: "xmerl/include/xmerl.hrl")
	Record.defrecord :xmlText, Record.extract(:xmlText, from_lib: "xmerl/include/xmerl.hrl")

	def from_string(xml_string, options \\ [quiet: true]) do
	{doc, []} =
	xml_string
	\|> :binary.bin_to_list
	\|> :xmerl_scan.string(options)