douglasjunior

//
//  AsyncTask.swift
//
//  Created by Douglas Nassif Roma Junior on 08/06/15.
//  Copyright (c) 2015 Douglas Nassif Roma Junior. All rights reserved.
//

import Foundation

class AsyncTask<Params, Progress, Result> : NSObject {

douglasjunior

/**
 * Created by douglas on 02/05/16.
 */
public final class TooltipGenerator {

    private Activity activity;
    private Dialog dialog;
    private Context context;
    private List<SimpleTooltip> tooltips = new ArrayList<>();

douglasjunior

set normal (set_color normal)
set magenta (set_color magenta)
set yellow (set_color yellow)
set green (set_color green)
set red (set_color red)
set gray (set_color -o black)

# Fish git prompt
set __fish_git_prompt_showdirtystate 'yes'
set __fish_git_prompt_showstashstate 'yes'

rbresjer

// Created by Rutger Bresjer on 10/10/2017

// Notes:
// - Be sure to enable "Hotspot Configuration" capability for the iOS target
// - Make sure the NetworkExtension framework is linked to the target

#import <Foundation/Foundation.h>
#import <React/RCTBridgeModule.h>

@interface IOSWifiManager : NSObject <RCTBridgeModule>

douglasjunior

Tutorial de instalação do Lets Encrypt no Glassfish 4.x

Gerando certificado Lets Encrypt

Para gerar o certificado Lets Encrypt é muito simples, aqui as instruções estão baseadas em um tutorial publicado pela Locaweb. (Web archive)

Primeiro vamos criar um diretório para isso:

wesbos

let currentColor = '#ebedf0';
let clicking = false; 
const boxes = document.querySelectorAll('.js-calendar-graph-svg rect');
const graph = document.querySelector('.js-calendar-graph-svg');
// code for switching the current color

function handleColorChange(e) {
  const el = e.currentTarget;
  currentColor = el.style['background-color'];
  console.log(currentColor)

douglasjunior

1. Apagar node_modules, mas pra isso ser eficiente todos os seus projetos tem que estar dentro de uma mesma subpasta chamadas, exemplo: /home/user/projetos/.

Você entra na pasta /home/user/projetos/ pelo terminal e roda:

find . -name 'node_modules' -type d -prune -exec rm -rf '{}' +

Se rodar esse comando em pasta errada pode acontecer dele apagar node_modules de dentro das pastas do NVM, ou alguma global, oq vai te forçar a reinstalar todas as versões do Node da sua máquina.

Apagar a pasta build dos projetos Android nativos, mesma regra aplicada ao node_modules:

dchowitz

Debugging ES6 in VS Code

My current editor of choice for all things related to Javascript and Node is VS Code, which I highly recommend. The other day I needed to hunt down a bug in one of my tests written in ES6, which at time of writing is not fully supported in Node. Shortly after, I found myself down the rabbit hole of debugging in VS Code and realized this isn't as straightforward as I thought initially. This short post summarizes the steps I took to make debugging ES6 in VS Code frictionless.

What doesn't work

My first approach was a launch configuration in launch.json mimicking tape -r babel-register ./path/to/testfile.js with babel configured to create inline sourcemaps in my package.json. The debugging started but breakpoints and stepping through the code in VS Code were a complete mess. Apparently, ad-hoc transpilation via babel-require-hook and inline sourcemaps do not work in VS Code. The same result for attaching (instead of launch) to `babel-node

Kudo

Intro

Here are the steps to integrate experimented JavaScriptCore. Hopefully this could solve the JSC crash issue on RN 0.59.

Steps (for RN 0.59)

1. yarn add 'jsc-android@next'
2. Modify build.gradle files.

diff --git a/android/app/build.gradle b/android/app/build.gradle

0x9090

types {
    text/html                             html htm shtml;
    text/css                              css;
    text/xml                              xml;
    image/gif                             gif;
    image/jpeg                            jpeg jpg;
    application/javascript                js;
    application/atom+xml                  atom;
    application/rss+xml                   rss;