warpech

Additional functionality

• Row resize - Issue #421
• Row move - Issue #556
• Auto row resize - Issue #1457
• Update of column and row headers post moving [preserve A1 co-ord system] [presumably this is just a label – also need to update all references – required for consistency] - - Issue #1458
• Continuous drag down (native scroll div) [drag across] [same as for other drag down – needs to be fixed] - Issue #1459
• Row & column selection [http://stackoverflow.com/questions/19523374/select-entire-handsontable-column-with-icon-click] [required for highlighting vars or periods of interest] - Issue #1440
• Wrap text in cell [odd behaviour with spaci

warpech

Optional version control

Because of the asynchronous nature of bidirectional client-server communication (caused by network latency, server side push, etc), it can be assumed that client and the server state is always out of sync.

To solve the problem expressing changes in the view-model, optional server and client state versioning is introduced:

{
  "_ServerVersion": 0, 
 "_ClientVersion$": 0, 

warpech

#!/bin/bash
#Usage:
#./find-links.sh                    #shows linked pages and orphans
#./find-links.sh --html             #shows linked pages and orphans with HTML links
#./find-links.sh --md               #shows linked pages and orphans with Markdown links
#./find-links.sh --orphans          #shows only orphans
#./find-links.sh --orphans --html   #shows only orphans with HTML links
#./find-links.sh --linked           #shows only linked pages
#./find-links.sh --linked --html    #shows only linked pages with HTML links

warpech

var express = require('express')
var bodyParser = require('body-parser');
var chalk = require('chalk');
var app = express()

app.use(bodyParser.text());

app.use(function(req, res, next) {
  res.header("Access-Control-Allow-Origin", "*");
  res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept, spy-type");

warpech

using edu.stanford.nlp.ling;
using edu.stanford.nlp.neural.rnn;
using edu.stanford.nlp.pipeline;
using edu.stanford.nlp.sentiment;
using edu.stanford.nlp.trees;
using edu.stanford.nlp.util;
using java.io;
using java.text;
using java.util;
using Starcounter;

warpech

{
   "CurrentPage":{
      "Launcher":{
         "Html":""
      },
      "Products":{
         "Html":""
      }
   }
}

warpech

<link rel="import" href="/sys/polymer/polymer.html">
<link rel="import" href="/sys/paper-icon-button/paper-icon-button.html">
<link rel="import" href="/CompositionEditor/elements/compositioneditor-inserter/compositioneditor-inserter.html">

<template>
    <style>
        .CompositionEditor-resetbutton {
            margin: 0;
            padding: 0;
            border: 0;

warpech

<template>
    <template is="dom-bind">
            <starcounter-include view-model="{{model.currentPage}}">
            </starcounter-include>
    </template>
    <palindrom-polymer-notifer></palindrom-polymer-notifer>
</template>


<template>

warpech

// ==UserScript==
// @name         Show labels on GH
// @namespace    http://tampermonkey.net/
// @version      0.1
// @description  try to take over the world!
// @author       You
// @match        https://github.com/*
// @grant        none
// ==/UserScript==

warpech

Commit Messages

Commit messages should say why you made a change, not what you changed.

A good commit message has the following:

• explanation of the problem
• explanation of the solution
• reference to the relevant GitHub issue