##Enable user home service
Open the Control panel
, in the User
section go to Advanced
tab and in the section User Home
:
-
Enable user home service
ClickApply
##Enable SSH
Go to Terminal & SNMP
section and:
-
Enable SSH service
# Some files and snippets | |
.eleventy.js | |
_includes/ | |
layouts/ | |
main.njk | |
dayIndex.njk | |
monthIndex.njk | |
yearIndex.njk | |
src/ |
// inert-unert.js: a quick utility for applying or removing the inert property | |
// - @scottjehl, @filamentgroup | |
// (note: inert support polyfill is still needed in some browsers) | |
// usage: | |
// when a modal element such as a dialog is active, | |
// this function will make unrelated elements inert, aiming to affect as few as possible | |
// example: inert( document.querySelector(".modal-open") ); | |
function inert( allButThisElement ){ | |
function inertSiblings( node ){ | |
if( node.parentNode ){ |
// budo boop.ts --live --dir . -- -p [ tsify --target es6 ] | |
import * as B from 'babylonjs' | |
import * as parseMagicaVoxel from 'parse-magica-voxel' | |
import * as createAOMesh from 'ao-mesher' | |
import * as fill from 'ndarray-fill' | |
import * as ndarray from 'ndarray' | |
let canvas : any = document.createElement( "canvas" ); | |
document.body.appendChild(canvas) |
Setting up a Mac for installation
Setting up a Windows machine for installation
ffWorks GUI for the all powerful FFmpeg
This contract for general design sevices is a hybrid of this one on Docracy and the AIGA one also found on Docracy. I wanted something that was simple yet covered the important bits such as payment schedule, kill fee, liability, rights etc. Change the parts in square brackets to suit. I've had this checked by a lawyer but I recommend if you decide to use it you also get it looked at by a lawyer too. Never do work without a contract in place. The majority of clients are good, decent and want to create great work with you — having a solid contract in place will strengthen that relationship and provide you with protection should things go awry.
Throughout the history of Web development, we're always trying to find ways to make the user experience better while maintaining a 'works for everyone' approach. CSS had media queries which allowed us to express that this stylesheet was for print, while that one was for screen. Later, we found that we could do a lot better in servicing the user if only we could know something about that screen and thus the responsive design movement was born. Now, we find ourselves in a similar place - different user agents support different means for interacting with elements and each has potentially different implications.
Consider the humble focus ring - you see it when you are filling out a form with text boxes. It's an important visual indicator because you're about to type and you want to know where those characters are about to land. This is true regarless of the device that you are using because the only way to interact with that element is to type some text. But now
Native HTML controls are a challenge to style. You can style any element in the web platform that uses Shadow DOM with a pseudo element ::pseudo-element
or the /deep/
path selector.
video::webkit-media-controls-timeline {
background-color: lime;
}
video /deep/ input[type=range] {
import urllib2,os; pf='Package Control.sublime-package'; ipp = sublime.installed_packages_path(); os.makedirs( ipp ) if not os.path.exists(ipp) else None; urllib2.install_opener( urllib2.build_opener( urllib2.ProxyHandler( ))); open( os.path.join( ipp, pf), 'wb' ).write( urllib2.urlopen( 'http://sublime.wbond.net/' +pf.replace( ' ','%20' )).read()); print( 'Please restart Sublime Text to finish installation')
From here on out, use Package Control to install everything. ⌘
+Shift
+P
, then type Install
to get a list of installable packages you can 'livesearch through. After installing plugins, they should be running.
I need to write this up in more detail soon, but in chatting with Patrick, it is clear that 140 chars isn't cutting it.
The way I've been thinking about the web on TVs and consoles is something like this:
In my mind, this starts with the basics of designing an interface that works well on a TV and can be interacted with using a remote control. Once we have the basics out of the way, we can proceed to multiscreen interactions.