Product | Status | Details |
---|---|---|
NGINX | yes | source |
Kong | yes | source |
React and OnsenUI work great for cordova apps, there are a couple things to keep in mind when working with Cordova Apps.
Since Cordova Apps load from the file system they do not work great with absolute urls, they use relative urls, which means
<script src="/bundle.js"></script> will not work as you might expect when using a web server. Since the root file system ofdevice is not where the files are located. You can resolve this using a relative url.
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
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars
file, reference that vars
file from your task
, and encrypt the whole vars
file using ansible-vault encrypt
.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
Install Package Control for easy package management.
- Open the console with
Ctrl+`
- Paste in the following:
- http://tutsplus.com/tutorial/writing-modular-javascript/
- https://github.com/aranm/scalable-javascript-architecture
- https://github.com/patrick99e99/scalable-js-architecture-app
- http://scaleapp.org/
- http://addyosmani.com/largescalejavascript/
- https://github.com/tcorral/Hydra.js/
- http://alanlindsay.me/kerneljs/
- http://terrifically.org/
- https://github.com/gorillatron/cerebral
/* | |
S A N I T A R Y V I E W P U B L I C A T I O N P A T T E R N | |
This pattern adresses three issues; memory leaks, involuntarily allowing unwanted event listeners to live | |
on, and the cumbersome process of publishing a view to the page. The first two issues are dealt with through | |
making sure that previously published views are removed properly, and not merely have their html | |
overwritten. And, as will see, the solution to fixing the removal process will also mean a streamlining | |
of the publication process! | |
We do this through the use of two mixin modules; one for our views, and one for our router. |
package net.odoe.components | |
{ | |
import flash.events.Event; | |
import mx.core.FlexGlobals; | |
import mx.events.CloseEvent; | |
import mx.events.FlexEvent; | |
import mx.logging.ILogger; | |
import mx.managers.PopUpManager; | |
<?php | |
if ( ! defined('EXT')){ | |
exit('Invalid file request'); | |
} | |
$conf['app_version'] = "169"; | |
$conf['license_number'] = "1234-1234-1234-1234"; | |
$conf['debug'] = "1"; | |
$conf['install_lock'] = "1"; |
<?php | |
/* | |
EE2 hidden configuration variables | |
Last updated: Jun 20 2010 | |
Obtain this list by putting print_r($this->EE->config->config); on a PHP-enabled template. | |
See: http://eeinsider.com/tips/view/config-overrides-for-ee-1-and-2/ | |
*/ |