We will be playing with android's gorgeous new Material Design theme. We will be covering the following material widgets and animations that were introduced in Android 5.0 (API level 21).
| /* | |
| * Copyright (C) 2015 Jared Rummler <[email protected]> | |
| * | |
| * Licensed under the Apache License, Version 2.0 (the "License"); | |
| * you may not use this file except in compliance with the License. | |
| * You may obtain a copy of the License at | |
| * | |
| * http://www.apache.org/licenses/LICENSE-2.0 | |
| * | |
| * Unless required by applicable law or agreed to in writing, software |
| [ | |
| { | |
| "group": "Lecture Rooms", | |
| "rooms": [ | |
| { | |
| "slug": "saal1", | |
| "schedulename": "Saal 1", | |
| "thumb": "http://localhost/streaming-website/thumbs/s1.png", | |
| "link": "http://localhost/streaming-website/saal1/", | |
| "display": "Saal 1", |
Original solution sacrifices new api lint check.
Here my solution:
int minSdk = hasProperty('minSdk') ? minSdk.toInteger() : 16
apply plugin: 'com.android.application'
android {
compileSdkVersion 23
This is a 20x14 Pixels LED table. Each of the pixels can display almost all colors.
You can play the game with the controllers. It is in ffii.ino on this page. You will need to upload it, see Programming. If you would like to see the making of the LED table, you can visit Youtube. If you have any questions, you can leave a comment below or contact me via email.
To use the LED table you can plug it into the power plug in the wall. If you would like to use the controllers, one of their ends should be plugged into A0 or A1 or A2 or A3 on the Arduino and the other end into Ground or GND or the blue line on the breadboard. You will notice if they are not plugged in correctly: They will not work. In rar cases where you connect 5V and ground directly to eachother, you will melt the cables or destroy the Arduino. Do not do that.
| package com.donnfelker.tasko; | |
| import android.content.Context; | |
| import android.graphics.Bitmap; | |
| import android.graphics.drawable.BitmapDrawable; | |
| import android.graphics.drawable.Drawable; | |
| import android.graphics.drawable.StateListDrawable; | |
| import android.support.test.espresso.matcher.BoundedMatcher; | |
| import android.text.TextUtils; | |
| import android.view.View; |
Here, you might lay out the reasons behind writing this code. You can link to specs, issues, or bugs in order to give someone a better idea of how a decision was made. This is your chance to give context to your reviewer. Ego depletion - the idea that willpower is used up over time - can be easily applied to your reviewer. We are human, after all. You'll likely get one shot at a quality review, so help your reviewer help you. Flush out this section.
How did you test this code? Did you write a unit test, or test it manually? Can you provide an animated gif or a screenshot to demonstrate your code does what it purports to do? What about test output or a useful snippet from a logfile? Help show that your code works.
Is there some part of the code that you know probably doesn't work as it should? Call out potential weak spots, and get help addressing them.
| # Goes in your .git/config file | |
| [alias] | |
| # Temporarily stop tracking a file in git. | |
| # usage: git unwatch path/to/file | |
| unwatch = update-index --assume-unchanged | |
| # Resume tracking a file in git. | |
| # usage: git watch path/to/file | |
| watch = update-index --no-assume-unchanged |
| #!/bin/sh | |
| set -e | |
| if [ -z "$1" ]; then | |
| shot_path=$(date +%Y-%m-%d-%H-%M-%S).mp4 | |
| else | |
| shot_path="$*" | |
| fi |
| [ | |
| { | |
| "author": "CCC", | |
| "conference": "33C3", | |
| "description": "Live-Streaming vom 33C3", | |
| "endsAt": "2016-12-30T20:00:00+0000", | |
| "groups": [ | |
| { | |
| "group": "Live", | |
| "rooms": [ |