Akka.NET: The Future of Distributed Programming in .NET

Advertisements

Use Chrome As Notepad

2 Good ones with Dark Theme:

data:text/html, <style>html,body{margin: 0; padding: 0;}</style><textarea style="font-size: 1.2em; line-height: 1.2em; background: %23000; color: %233a3; width: 100%; height: 100%; border: none; outline: none; margin: 0; padding: 30px;" autofocus placeholder="Hi..." />

 

data:text/html,<title>Notepad</title><style type="text/css">#e{font-size: 16px; position:absolute;top:0;right:0;bottom:0;left:0;}</style>

http://d1n0x3qji82z53.cloudfront.net/src-min-noconflict/ace.jsvar e=ace.edit("e");e.setTheme("ace/theme/monokai");e.getSession().setMode("ace/mode/javascript");

PDF Stream in Browser

If you are using  or <object> tag to display a streamed PDF file (or other file types) from a server as in:

<object data=”SomeServlet?do=get_doc&id=6″ type=”application/pdf” width=”800″ height=”400″>

make sure the server sends the proper http content-disposition value, which in this case would be inline.

REF: http://stackoverflow.com/questions/9840230/how-to-display-a-pdf-stream-in-a-browser-using-javascript

 

 

SERVER CHANGE

response.setHeader(“Content-Disposition”, “inline; filename=file.pdf”);

 

webpack 2 features

SYSTEMJS INTEROPERABIL ITY

  • SystemJS is a DYNAMIC module loader that Angular 2 uses. It doesn’t work with Webpack  coz it’s a STATIC Module Bundler.
  • But now there’s a Webpack Plugin that creates a MOCK spec that confirms with the SystemJS Spec. This way, SystemJS is fooled into believing that the modules are dynamic, when they’re actually all inside a single static js file outputed by the webpack’s module bundler at build time.

 

SEED

A simple Angular 2 seed featuring Angular 2 and Webpack 2: https://github.com/AngularClass/angular2-seed

FEATURES

https://docs.google.com/document/d/1tRc0MzvRdGK7EbG2LRW8vSyoxKhR_EvRUz3AQRyFZso/edit?pli=1)

List of new webpack 2 features:

  • native ES6 import, export and System.import
  • Tree Shaking for ES6
  • Needs Promise polyfill in old browsers
  • chunk error handling
  • Many plugins now take options objects instead of multiple parameters
  • config can be a function and –env
  • Removed deprecated argument configs (except with one argument shortcut if possible)
  • loaders now match resourcePath instead of resource with query
  • webpack config can return a Promise
  • -p sets NODE_ENV = “production”
  • the uglifyjs plugin no longer minimize other assets
    • there is the LoaderOptionsPlugin now
  • webpackfile.js is now also supported
  • added HashedModuleIdsPlugin
  • webpack differs from the ES6 modules spec: imports are not hoisted
  • everything in resolve.* and resolveLoader.* renamed
  • ResolverPlugin removed, resolve.plugins added
  • loaders in configuration resolve relative to context instead of resource
  • enhanced-resolve should be useable standalone
  • Use emitter approch from webworker pull request to send events
  • Inline mode should be default in webpack-dev-server
  • add array with options to loaders config
  • resolve loaders from webpack config relative to context

 

Introduction

webpack is a bundler for modules. The main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.

TL; DR

  • Bundles both CommonJS and AMD modules (even combined).
  • Can create a single bundle or multiple chunks that are asynchronously loaded at runtime (to reduce initial loading time).
  • Dependencies are resolved during compilation reducing the runtime size.
  • Loaders can preprocess files while compiling, e.g. coffeescript to JavaScript, handlebars strings to compiled functions, images to Base64, etc.
  • Highly modular plugin system to do whatever else your application requires.