| # source : http://code.google.com/p/natvpn/source/browse/trunk/stun_server_list | |
| # A list of available STUN server. | |
| stun.l.google.com:19302 | |
| stun1.l.google.com:19302 | |
| stun2.l.google.com:19302 | |
| stun3.l.google.com:19302 | |
| stun4.l.google.com:19302 | |
| stun01.sipphone.com | |
| stun.ekiga.net |
| WebPDecodeAndDraw = function (data) { | |
| var decoder = new WebPDecoder(); | |
| var bitmap = decoder.WebPDecode(data, data.length); | |
| if (bitmap) { | |
| //Draw Image | |
| var output = ctx.createImageData(canvas.width, canvas.height); | |
| var biWidth = canvas.width; | |
| var outputData = output.data; |
| const { resolve } = require('path'); | |
| /** | |
| * Resolve tsconfig.json paths to Webpack aliases | |
| * @param {string} tsconfigPath - Path to tsconfig | |
| * @param {string} webpackConfigBasePath - Path from tsconfig to Webpack config to create absolute aliases | |
| * @return {object} - Webpack alias config | |
| */ | |
| function resolveTsconfigPathsToAlias({ | |
| tsconfigPath = './tsconfig.json', |
| upload(files) { | |
| const config = { | |
| onUploadProgress: function(progressEvent) { | |
| var percentCompleted = Math.round((progressEvent.loaded * 100) / progressEvent.total) | |
| console.log(percentCompleted) | |
| } | |
| } | |
| let data = new FormData() | |
| data.append('file', files[0]) |
A modest proposal for a first-class destiny operator equivalent in Svelte components that's also valid JS.
Svelte 2 has a concept of computed properties, which are updated whenever their inputs change. They're powerful, if a little boilerplatey, but there's currently no place for them in Svelte 3.
This means that we have to use functions. Instead of this...
<!-- Svelte 2 -->
<h1>HELLO {NAME}!</h1>
I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.
But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.
Svelte is a language.
Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?
A few projects that have answered this question:
-A component must have a default export, but the default export is not the component
-The default export and its properties must be structured a certain way, you can't just use JavaScript
-Components, actions, animations, transitions, custom events etc must be registered, not just imported
-Components can be registered with a shorthand, because the normal way is cumbersome
-methods are attached to the prototype, and `this` is the component, even though it looks (including to linters and typecheckers) as though the `methods` object itself is the context
-Events must be method calls, not arbitrary expressions
-`event` has a special meaning in method calls, as does `this`, as does `refs`, as do `console` and other special names
So far, most of us have been writing Svelte components into .html files, with a few exceptions (Parcel users, for example, have additional constraints to work with). We're currently discussing whether this should change.
Once you've read the pros and cons, please vote!
Pros:
| /* Written for MintNetwork Yukari Cluster - 500 page handling */ | |
| const bs = document.getElementById('babyshark'); | |
| /* Localize babyshark */ | |
| function localize(langCode) { | |
| const country = window.navigator.userLanguage || window.navigator.language; | |
| let ytCode = ""; | |
| const lang = langCode || country.split('-')[0]; | |
| switch (lang) { |