Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
# Copyright (C) 2013 Wesley Baugh | |
"""Tools for text classification. | |
Extracted from the [infer](https://github.com/bwbaugh/infer) library. | |
""" | |
from __future__ import division | |
import math | |
from collections import defaultdict, namedtuple, Counter | |
from fractions import Fraction |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
<?php | |
function pre_install() | |
{ | |
global $current_user; | |
require_once('include/utils.php'); | |
require_once('include/utils/file_utils.php'); | |
require_once('config.php'); | |
require_once('include/MVC/Controller/SugarController.php'); |
<?php | |
class FieldChangeHook | |
{ | |
protected static $fetchedRow = array(); | |
/** | |
* Called as before_save logic hook to grab the fetched_row values | |
*/ | |
public function saveFetchedRow($bean, $event, $arguments) |
Steps to add lazy loadding on SugarCRM 6.5.x subpanel:
List some crypto libraries for JavaScript out there. Might be a bit out dated. Scroll to the bottom.
http://www.w3.org/TR/WebCryptoAPI/
This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.
These rules are adopted from the AngularJS commit conventions.
const request = require('request'), | |
fs = require('fs'), | |
path = require('path'), | |
ca = fs.readFileSync(path.join(__dirname, 'root-ca.crt')); | |
const options = { | |
url: 'https://127.0.0.1:3443/', // any @alt_names will work | |
agentOptions: { | |
ca: ca | |
} |
This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.
In that post I talked about 3 main reasons for moving from require.js to webpack:
Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
, elem.offsetTop
, elem.offsetWidth
, elem.offsetHeight
, elem.offsetParent