Praveen Puglia praveenpuglia

## Rich Text Editor.html
<!doctype html>
<html>
<head>
<title>Rich Text Editor - FROM MDN!</title>
<script type="text/javascript">
var oDoc, sDefTxt;

function initDoc() {
  oDoc = document.getElementById("textBox");
  sDefTxt = oDoc.innerHTML;

## .csscomb.json
{
  "config": {
    "remove-empty-rulesets": true,
    "always-semicolon": true,
    "color-case": "lower",
    "block-indent": "  ",
    "color-shorthand": true,
    "element-case": "lower",
    "eof-newline": false,
    "leading-zero": true,

## Package Control.sublime-settings
{
	"in_process_packages":
	[
	],
	"installed_packages":
	[
		"BracketHighlighter",
		"Emmet",
		"GitHub Markdown Snippets",
		"Handlebars",

## es2015-features.js
/*======================================================
=            ARROW FUNCTIONS & LEXICAL this            =
======================================================*/
// OLD WAY
var squares = [1,2,3,4,5,6,7,8,9].map(function(value){
    // this === window
    return value * value;
});

// NEW WAY

## CSS Variables - Thoughts.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                praveenpuglia
                / CSS Variables - Thoughts.md
            
            
              Last active
              December 16, 2015 04:48
            
          
    Thanks for replying to me! :)
I really didn't know about the recommendation process back then. It's pretty recent that I came to know about it. I am not sure if any of the suggestion helps at the moment since it's now a recommendation.
I am also sure that the working group must have thought about exhaustive scenarios so I may not even be making a point.
I know $ or @ couldn't be used since they were already getting used in preprocessors and @ specifically, I feel, wouldn't go with the existing syntax of CSS.
I met Chris Lilley few days ago and I came to know that $ could be used but it would create multiple problems.

  
## hcf.js
	function hcf(n1, n2){
		var hcf = (n1 > n2) ? findHcf(n2, n1) : findHcf(n1, n2);
		console.log("HCF of ", n1, " & ", n2, " is ", hcf);
	}

	function findHcf(b, a) {
		console.log("Divisor : ", b," Dividend: ", a);
		var q, r;
		q = Math.floor(a/b);
		r = a - b*q;

## shadow-dom.md

      
              1 file
            
          
              23 forks
            
          
              6 comments
            
          
              212 stars
            
          
                praveenpuglia
                / shadow-dom.md
            
            
              Last active
              March 28, 2024 15:06
            
              
                Everything you need to know about Shadow DOM
              
          
    I am moving this gist to a github repo so more people can contribute to it. Also, it makes it easier for me to version control.
Please go to - https://github.com/praveenpuglia/shadow-dom-in-depth for latest version of this document.
Also, if you find the document useful, please shower your love, go ⭐️ it. :)
Shadow DOM


Heads Up! It's all about the V1 Spec.

In a nutshell, Shadow DOM enables local scoping for HTML & CSS.

  
## debug.component.ts
import { Component, Input } from '@angular/core';

@Component({
  selector: 'dump',
  template: `
    <pre><code>{{data | json}}</code></pre>
  `,
  styles: [
    `
  :host {

## webpack.config.js
// Require things!
const path = require('path');
const webpack = require('webpack');
const HtmlWebpackPlugin = require('html-webpack-plugin');

// The configuration starts here!
module.exports = {
  // The entry point for webpack to start generating a dependency graph.
  entry: { index: './src/index.js' },


## no-dispatch.ts
@Effect({ dispatch: false })
logout$: Observable<Action> = this.actions$.pipe(
  ofType(UserActionTypes.LOGOUT),
  tap(action => {
    delete window.localStorage.user;
    this.router.navigate(['login']);
  })
);
	<!doctype html>
	<html>
	<head>
	<title>Rich Text Editor - FROM MDN!</title>
	<script type="text/javascript">
	var oDoc, sDefTxt;

	function initDoc() {
	oDoc = document.getElementById("textBox");
	sDefTxt = oDoc.innerHTML;
	{
	"config": {
	"remove-empty-rulesets": true,
	"always-semicolon": true,
	"color-case": "lower",
	"block-indent": " ",
	"color-shorthand": true,
	"element-case": "lower",
	"eof-newline": false,
	"leading-zero": true,
	{
	"in_process_packages":
	[
	],
	"installed_packages":
	[
	"BracketHighlighter",
	"Emmet",
	"GitHub Markdown Snippets",
	"Handlebars",
	/*======================================================
	= ARROW FUNCTIONS & LEXICAL this =
	======================================================*/
	// OLD WAY
	var squares = [1,2,3,4,5,6,7,8,9].map(function(value){
	// this === window
	return value * value;
	});

	// NEW WAY
	function hcf(n1, n2){
	var hcf = (n1 > n2) ? findHcf(n2, n1) : findHcf(n1, n2);
	console.log("HCF of ", n1, " & ", n2, " is ", hcf);
	}

	function findHcf(b, a) {
	console.log("Divisor : ", b," Dividend: ", a);
	var q, r;
	q = Math.floor(a/b);
	r = a - b*q;
	import { Component, Input } from '@angular/core';

	@Component({
	selector: 'dump',
	template: `
	<pre><code>{{data \| json}}</code></pre>
	`,
	styles: [
	`
	:host {
	// Require things!
	const path = require('path');
	const webpack = require('webpack');
	const HtmlWebpackPlugin = require('html-webpack-plugin');

	// The configuration starts here!
	module.exports = {
	// The entry point for webpack to start generating a dependency graph.
	entry: { index: './src/index.js' },
	@Effect({ dispatch: false })
	logout$: Observable<Action> = this.actions$.pipe(
	ofType(UserActionTypes.LOGOUT),
	tap(action => {
	delete window.localStorage.user;
	this.router.navigate(['login']);
	})
	);