Simple way to embed html in javasript

If you are not working with React and JSX, this could be a quick way to embed html inside Javascript...

	// Simple way to embed html in javasript
	Array.prototype.joinHtml = function () {
	return this.join('');
	};
	String.prototype.supplant = function (o) {
	return this.replace(/{([^{}]*)}/g,
	function (a, b) {
	var r = o[b];
	return typeof r === 'string' || typeof r === 'number' ? r : a;
	}
	);
	};
	var html = [
	'<div class="{classes}">',
	'<p>{text}</p>',
	'</div>',
	].joinHtml().supplant({
	classes: "class1",
	text: "dummy text"
	});
	console.log(html); // output: <div class="class1"><p>dummy text</p></div>

view raw simple-way-to-embed-html-inside-javascript.js hosted with ❤ by GitHub

Food Recipes: Semantic representation, Formal Language and Visualization

I always enjoyed the precision that programming languages commands give instructions to computers and I have been wondering if that precision could be applied to food recipes.
If computers could understand semantically a recipe, they would be able to perform many interesting tasks.
For example a computer could

• Scale the recipe: Not only multiplying ingredients but also adjusting the time and the difficulty
• Merge recipes fitting one into another taking advantage of the idle moments. It would be possible to plan several recipes with a certain deadline. Something like "I want to prepare Risotto alle Fragole and Arista for 3 people and everything should be ready by 7 pm". This is as example of simplified merging process:
  
• Combine recipes to come out with new variation. There is the "Computer Cooking Contest" that is trying to achieve this result. The event is organised every year, see in the resources section for links.
• Using a version control system, such as Git, where could have people to add variations of the recipe creating branch, merging, committing, etc.
• Computers could, with the help of a machine or robot, cook for you

This is an example of annotated recipe from the CURD database. This recipe is annotated using the MILK language:

	<?xml version="1.0" encoding="UTF-8"?>
	<recipe version="1.1">
	<line>
	<originaltext>24 jalapeno peppers</originaltext>
	<annotation>create_ing(ing0, "24 jalapeno peppers")</annotation>
	</line>
	<line>
	<originaltext>1 pound sausage</originaltext>
	<annotation>create_ing(ing1, "1 pound sausage")</annotation>
	</line>
	<line>
	<originaltext>2 cups all-purpose baking mix</originaltext>
	<annotation>create_ing(ing2, "2 cups all-purpose baking mix")</annotation>
	</line>
	<line>
	<originaltext>1 (16 ounce) package Cheddar cheese, shredded</originaltext>
	<annotation>create_ing(ing3, "1 (16 ounce) package Cheddar cheese, shredded")</annotation>
	</line>
	<line>
	<originaltext>1 tablespoon crushed red pepper flakes</originaltext>
	<annotation>create_ing(ing4, "1 tablespoon crushed red pepper flakes")</annotation>
	</line>
	<line>
	<originaltext>1 tablespoon garlic salt</originaltext>
	<annotation>create_ing(ing5, "1 tablespoon garlic salt")</annotation>
	</line>
	<line>
	<originaltext>1 (16 ounce) package Monterey Jack cheese, cubed</originaltext>
	<annotation>create_ing(ing6, "1 (16 ounce) package Monterey Jack cheese, cubed")</annotation>
	</line>
	<line>
	<originaltext>Preheat oven to 325 degrees F (165 degrees C).</originaltext>
	<annotation>create_tool(t0, "oven")</annotation>
	</line>
	<line>
	<originaltext>Preheat oven to 325 degrees F (165 degrees C).</originaltext>
	<annotation>set(t0,"Preheat to 325 degrees F (165 degrees C)")</annotation>
	</line>
	<line>
	<originaltext>Lightly grease a medium baking sheet.</originaltext>
	<annotation>create_tool(t1, "medium baking sheet")</annotation>
	</line>
	<line>
	<originaltext>Lightly grease a medium baking sheet.</originaltext>
	<annotation>set(t1,"lightly grease")</annotation>
	</line>
	<line>
	<originaltext>Cut a slit in each jalapeno pepper.</originaltext>
	<annotation>cut(ing0, , ing7, "slitted jalapenos", "cut slit in each pepper")</annotation>
	</line>
	<line>
	<originaltext>Remove and discard seeds and pulp.</originaltext>
	<annotation>do(ing7, , ing13, "seedless slitted jalapenos", "Remove and discard seeds and pulp")</annotation>
	</line>
	<line>
	<originaltext>In a medium bowl, mix sausage, baking mix, Cheddar cheese, crushed red pepper, and garlic salt.</originaltext>
	<annotation>create_tool(t2, "medium bowl")</annotation>
	</line>
	<line>
	<originaltext>In a medium bowl, mix sausage, baking mix, Cheddar cheese, crushed red pepper, and garlic salt.</originaltext>
	<annotation>combine({ing1, ing2, ing3, ing4, ing5}, ing8, "sausage stuff", "")</annotation>
	</line>
	<line>
	<originaltext>In a medium bowl, mix sausage, baking mix, Cheddar cheese, crushed red pepper, and garlic salt.</originaltext>
	<annotation>mix(ing8, t2, ing9, "mixed sausage stuff", "mix")</annotation>
	</line>
	<line>
	<originaltext>Stuff jalapenos with the Monterey Jack cheese cubes.</originaltext>
	<annotation>combine({ing6, ing13}, ing10, "cheesy jalapenos", "stuff jalapenos with cheese cubes")</annotation>
	</line>
	<line>
	<originaltext>Shape sausage mixture around the jalapenos to form balls.</originaltext>
	<annotation>combine({ing10, ing9}, ing11, "sausage jalapeno balls", "shape sausage stuff around the jalapenos to form balls")</annotation>
	</line>
	<line>
	<originaltext>Arrange jalapeno balls on the prepared baking sheet.</originaltext>
	<annotation>put(ing11, t1)</annotation>
	</line>
	<line>
	<originaltext>Bake 25 minutes in the preheated oven, until lightly browned.</originaltext>
	<annotation>cook(ing11, t0, ing12, "cooked jalapeno sausage balls", "Bake 25 minutes, until lightly browned")</annotation>
	</line>
	<line>
	<originaltext>Bake 25 minutes in the preheated oven, until lightly browned.</originaltext>
	<annotation>chefcheck(ing12,"lightly browned")</annotation>
	</line>
	</recipe>

view raw Armadillo-Eggs.rcp_tagged.xml hosted with ❤ by GitHub

Visualization

If the recipe is semantically represented inside the computer, it could be automatically visualised using some algorithm. A viable format could be similar to:

Other formats:

Video could also be used. Animation could fit better because could be generated in CG. I personally like this point of view in recipe video:

And as a final note, this is a video of my mother that I took several years ago. Not a good example of clarity but... a good recipe:

Resources

1. A method for extracting major workflow composed of ingredients, tools, and actions from cooking procedural text

   By Yoko Yamakata, Shinji Imahori, Hirokuni Maeta, Shinsuke Mori (2016)
   A method for extracting a major workflow of cooking procedure from a Japanese recipe on the Web. It is utilized for various applications including recipe search, summarization, and visualization.
   http://www.ar.media.kyoto-u.ac.jp/publications/yamakata-CEA16.pdf

2. Training the PR2 in Culinary Arts. A Natural Language Model for Parsing Recipes

   By Jessica Zhao, Alejandro Bordallo, Subramanian Ramamoorthy (2016)
   a culinary language model for the kitchen by abstracting cooking instructions into a generalized tripartite form of ACTION, TARGET, TOOL.
   http://stanford.edu/~jesszhao/files/PR2cooking.pdf

3. Predicting the Structure of Cooking Recipes

   By Jermsak Jermsurawong and Nizar Habash (2015)
   An ingredient-instruction dependency tree data structure to represent recipes. The proposed representation allows for more refined comparison of recipes and recipe - parts, and is a step towards semantic representation of recipes
   http://www.aclweb.org/anthology/D/D15/D15-1090.pdf

4. Flow Graph Corpus from Recipe Texts

   By Shinsuke Mori, Hirokuni Maeta, Yoko Yamakata, Tetsuro Sasada4 (2015)
   An attempt at annotating procedural texts with a flow graph as a representation of understanding.The domain we focus on is cooking recipe.
   https://pdfs.semanticscholar.org/7f88/398e8928d32366ebf725eb457cb2fa3a94bf.pdf

10 Criterias to Judge a Good Milk Container

#1 Openability	BAD This container is difficult to open. It require, at first to remove the blue cap. Then there is a small handle that need to be pulled. Sometime it breakes and the pulling action, due to the strenght required, may make you spill some milk	GOOD This container is Easy to open knowing the method. Can be opened with two single steps using one hand while the other hold the bottle. The moviment are slow and would not cause any spill
#2 Closability	BAD The cup net to be screwed to close so it requires some work. It is a separate object that can get lost. It doesn't seal the container ermetically but it gives the false impression that it does so someone may try to store it horizzontally causing milk to spill	GOOD To close the container it is enough to fold it back. It doesn't seal ermetically but it is close enough

GPS nmea GPX (or KLM) converter for Google Maps

This script take large amount of GPS data in nmea format and convert into gpx format to import into Google maps.

I had large amount of data coming from a trip to Iceland and I wanted quicly import it on Google My Maps.

Google has a limit of 5 MB but my data was 90 MB.

To reduce the data the script

• only export latitude and longitude
• approximae the latitude and longitude values reducing the number of decimal digit
• skeep points

There are two variables that you can adjust to get an putput file smaller than 5 MB. In my case the best compromise was

• savePointsEvery = 4
• precision = 6

This generate an ouput file of 4,5 MB

Using instead

• savePointsEvery = 4
• precision = 6

The output file was 6 MB

The output files are in the folder data.

Source

Find the source at https://github.com/lucamug/gps-converter

Example

This is the result after imported in Google Maps: