on the traditional empiricist account we do not have direct access to the facts of the external world 00:11:03 that is we do not experience externality directly but only immediately not immediately but immediately because between us and the external world are those what do you call them oh yes 00:11:18 sense organs and so the question is how faithfully they report what is going on out there well to raise the question how faithful is the sensory report 00:11:30 of the external world is to assume that you have some reliable non-sensory way of answering that question that's the box you can't get out of and so there is always this gap 00:11:42 between reality as it might possibly be known by some non-human creature and reality as empirically sampled by the senses whose limitations and distortions are very well 00:11:56 known but not perfectly classified or categorized or or measured

BTW, the modules used to be called moduleDirectories in previous versions.

The resolving process is basically simple and distinguishes between three variants: absolute path: require("/home/me/file") relative path: require("../src/file") or require("./file") module path: require("module/lib/file")

In contrast to import (which handles 1+2 pretty much the same way, but would send you looking in node_modules right away) path 'module' indeed means your project root for paths without a need to resolve, like output.path in your webpack config... and: (on resolving) Only 3 is subject to resolve.root and resolve.moduleDirectories resolving, see webpack docs here

The problem is that by default, module paths only work with things imported via npm because the new modules variable on resolve defaults to ["node_modules"]. This lets you import 3rd party code from npm really easily. But it means importing your code with a module path needs a config change.

When enabled, symlinked resources are resolved to their real path, not their symlinked location. Note that this may cause module resolution to fail when using tools that symlink packages (like npm link)

resolve: { extensions: ['.jsx', '.js'], modules: [ path.resolve(__dirname, 'src'), 'node_modules' ] },

There was a major refactoring in the resolver (https://github.com/webpack/enhanced-resolve). This means the resolving option were changed too. Mostly simplification and changes that make it more unlikely to configure it incorrectly.

For future reference, webpack 2 removed everything but modules as a way to resolve paths. This means root will not work.

Returns a Promise<?Object> that resolves with no value on success or resolves with an Object of submission errors on failure. The reason it resolves with errors is to leave rejection for when there is a server or communications error.

Note: We do not recommend using resolve of AngularUI Router. The recommended approach is to execute any logic needed before beginning the state transition.

Roassal maps objects and connections to graphical elements and edges. In additions, values and metrics are represented in visual dimentions (e.g., width, height, intensity of graphical elements). Such mapping is an expressive way to build flexible and rich visualization. This chapter gives an overview of Roassal and its main API. It covers the essential concepts of Roassal, such as the view, elements, shapes, and interactions.

Once a Roassal element has been created, modifying its shape should not result in an update of the element.

c := TRCanvas new. shape := TRBoxShape new size: 40. c addShape: shape. shape when: TRMouseClick do: [ :event | event shape remove. c signalUpdate ]. c

| canvas myCircle data |
canvas := TRCanvas new.
myCircle := TREllipseShape new size: 100; color: Color white.
data := #('lion-o' 'panthro' 'tigro' 'chitara' 'munra' 'ozimandias' 'Dr Manhatan').
canvas addShape: myCircle.
myCircle when: TRMouseClick do: [:event | event myCircle remove. canvas signalUpdate  ].
canvas