| declare module '@nozbe/watermelondb' { | |
| import * as Q from '@nozbe/watermelondb/QueryDescription' | |
| export { default as Collection } from '@nozbe/watermelondb/Collection' | |
| export { default as Database } from '@nozbe/watermelondb/Database' | |
| export { default as CollectionMap } from '@nozbe/watermelondb/Database/CollectionMap' | |
| export { default as Relation } from '@nozbe/watermelondb/Relation' | |
| export { default as Model, associations } from '@nozbe/watermelondb/Model' | |
| export { default as Query } from '@nozbe/watermelondb/Query' | |
| export { tableName, columnName, appSchema, tableSchema } from '@nozbe/watermelondb/Schema' |
| // Have some complicated non-React widgets that manipulate DOM? | |
| // Do they manage a list of DOM elements? Here's how to wrap it | |
| // into a React component so you can "constantly rerender" it. | |
| // A dumb non-react widget that manually manage some DOM node that | |
| // represent a list of items | |
| function NonReactWidget(node) { | |
| this.node = node; | |
| } |
| #import <Foundation/Foundation.h> | |
| #import "RCTBridgeModule.h" | |
| #define RCT_EXTERN_MODULE(objc_name, objc_supername) \ | |
| RCT_EXTERN_REMAP_MODULE(objc_name, objc_name, objc_supername) | |
| #define RCT_EXTERN_REMAP_MODULE(js_name, objc_name, objc_supername) \ | |
| objc_name : objc_supername \ | |
| @end \ | |
| @interface objc_name (RCTExternModule) <RCTBridgeModule> \ |
| #!/usr/bin/env node | |
| // This plugin replaces text in a file with the app version from config.xml. | |
| var wwwFileToReplace = "js/build.js"; | |
| var fs = require('fs'); | |
| var path = require('path'); | |
| var rootdir = process.argv[2]; |
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE | |
| Copyright (C) 2014 ADDY OSMANI <addyosmani.com> | |
| Everyone is permitted to copy and distribute verbatim or modified | |
| copies of this license document, and changing it is allowed as long | |
| as the name is changed. | |
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE | |
| TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION |
| /** @jsx React.DOM */ | |
| var Dashboard = React.createClass({ | |
| render: function() { | |
| return ( | |
| <div> | |
| <h1>Dashboard!</h1> | |
| <ul> | |
| <li><Link to="inbox">Inbox</Link></li> | |
| </ul> |
| var dom = Bloop.dom; | |
| var Box = Bloop.createClass({ | |
| getInitialState: function() { | |
| return { number: 0 }; | |
| }, | |
| updateNumber: function() { | |
| this.state.number++; | |
| }, |
| public static IObservable<TResult> SelectMany<TSource, TResult>(this ObservableCollection<TSource> collection, Func<TSource, IObservable<TResult>> selector) | |
| { | |
| return Observable.Create<TResult>(observer => | |
| { | |
| // assume events are raised on the same thread (i.e. dispatcher), so we don't need a concurrent dictionary | |
| var subscriptions = new Dictionary<TSource, IDisposable>(); | |
| foreach (var source in collection) | |
| { | |
| //subscribe selector to all items already in the collection |
| <#@ template debug="true" hostspecific="true" language="C#" #> | |
| <#@ output extension=".d.ts" #> | |
| <# /* Update this line to match your version of SignalR */ #> | |
| <#@ assembly name="$(SolutionDir)\packages\Microsoft.AspNet.SignalR.Core.2.2.0\lib\net45\Microsoft.AspNet.SignalR.Core.dll" #> | |
| <# /* Load the current project's DLL to make sure the DefaultHubManager can find things */ #> | |
| <#@ assembly name="$(TargetPath)" #> | |
| <#@ assembly name="System.Core" #> | |
| <#@ assembly name="System.Web" #> | |
| <#@ assembly name="System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" #> | |
| <#@ assembly name="System.Xml.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" #> |
Other people's code is awful, and your own code from months previous counts as someone else's. With this and the festive spirit in mind, I dug up a canvas snow demo I made two years ago to see how bad my code really was.
Turns out the performance landscape has changed quite a bit, but after applying a couple of workarounds, best practices, and memory management, I got the demo running smoother than it ever did.
Ugh, I can't believe I just wrote "performance landscape". Anyway...