Deleted vscode/clock/.vscode/extensions.json, vscode/clock/.vscode/tasks.json, vscode/clock/include/README, vscode/clock/lib/README, vscode/clock/src/clock.cpp, vscode/clock/test/README, vscode/clock/.gitignore, vscode/clock/.travis.yml, vscode/clock/platformio.ini files

vscode/clock/.gitignore

@@ -1,5 +0,0 @@
-.pio
-.vscode/.browse.c_cpp.db*
-.vscode/c_cpp_properties.json
-.vscode/launch.json
-.vscode/ipch

vscode/clock/.travis.yml

@@ -1,67 +0,0 @@
-# Continuous Integration (CI) is the practice, in software
-# engineering, of merging all developer working copies with a shared mainline
-# several times a day < https://docs.platformio.org/page/ci/index.html >
-#
-# Documentation:
-#
-# * Travis CI Embedded Builds with PlatformIO
-#   < https://docs.travis-ci.com/user/integration/platformio/ >
-#
-# * PlatformIO integration with Travis CI
-#   < https://docs.platformio.org/page/ci/travis.html >
-#
-# * User Guide for `platformio ci` command
-#   < https://docs.platformio.org/page/userguide/cmd_ci.html >
-#
-#
-# Please choose one of the following templates (proposed below) and uncomment
-# it (remove "# " before each line) or use own configuration according to the
-# Travis CI documentation (see above).
-#
-
-
-#
-# Template #1: General project. Test it using existing `platformio.ini`.
-#
-
-# language: python
-# python:
-#     - "2.7"
-#
-# sudo: false
-# cache:
-#     directories:
-#         - "~/.platformio"
-#
-# install:
-#     - pip install -U platformio
-#     - platformio update
-#
-# script:
-#     - platformio run
-
-
-#
-# Template #2: The project is intended to be used as a library with examples.
-#
-
-# language: python
-# python:
-#     - "2.7"
-#
-# sudo: false
-# cache:
-#     directories:
-#         - "~/.platformio"
-#
-# env:
-#     - PLATFORMIO_CI_SRC=path/to/test/file.c
-#     - PLATFORMIO_CI_SRC=examples/file.ino
-#     - PLATFORMIO_CI_SRC=path/to/test/directory
-#
-# install:
-#     - pip install -U platformio
-#     - platformio update
-#
-# script:
-#     - platformio ci --lib="." --board=ID_1 --board=ID_2 --board=ID_N

vscode/clock/.vscode/extensions.json

@@ -1,7 +0,0 @@
-{
-	// See http://go.microsoft.com/fwlink/?LinkId=827846
-	// for the documentation about the extensions.json format
-	"recommendations": [
-		"platformio.platformio-ide"
-	]
-}

vscode/clock/.vscode/tasks.json

@@ -1,12 +0,0 @@
-{
-    // See https://go.microsoft.com/fwlink/?LinkId=733558
-    // for the documentation about the tasks.json format
-    "version": "2.0.0",
-    "tasks": [
-        {
-            "label": "echo",
-            "type": "shell",
-            "command": "echo Hello"
-        }
-    ]
-}

vscode/clock/include/README

@@ -1,39 +0,0 @@
-
-This directory is intended for project header files.
-
-A header file is a file containing C declarations and macro definitions
-to be shared between several project source files. You request the use of a
-header file in your project source file (C, C++, etc) located in `src` folder
-by including it, with the C preprocessing directive `#include'.
-
-```src/main.c
-
-#include "header.h"
-
-int main (void)
-{
- ...
-}
-```
-
-Including a header file produces the same results as copying the header file
-into each source file that needs it. Such copying would be time-consuming
-and error-prone. With a header file, the related declarations appear
-in only one place. If they need to be changed, they can be changed in one
-place, and programs that include the header file will automatically use the
-new version when next recompiled. The header file eliminates the labor of
-finding and changing all the copies as well as the risk that a failure to
-find one copy will result in inconsistencies within a program.
-
-In C, the usual convention is to give header files names that end with `.h'.
-It is most portable to use only letters, digits, dashes, and underscores in
-header file names, and at most one dot.
-
-Read more about using header files in official GCC documentation:
-
-* Include Syntax
-* Include Operation
-* Once-Only Headers
-* Computed Includes
-
-https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

vscode/clock/lib/README

@@ -1,46 +0,0 @@
-
-This directory is intended for project specific (private) libraries.
-PlatformIO will compile them to static libraries and link into executable file.
-
-The source code of each library should be placed in a an own separate directory
-("lib/your_library_name/[here are source files]").
-
-For example, see a structure of the following two libraries `Foo` and `Bar`:
-
-|--lib
-|  |
-|  |--Bar
-|  |  |--docs
-|  |  |--examples
-|  |  |--src
-|  |     |- Bar.c
-|  |     |- Bar.h
-|  |  |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
-|  |
-|  |--Foo
-|  |  |- Foo.c
-|  |  |- Foo.h
-|  |
-|  |- README --> THIS FILE
-|
-|- platformio.ini
-|--src
-   |- main.c
-
-and a contents of `src/main.c`:
-```
-#include <Foo.h>
-#include <Bar.h>
-
-int main (void)
-{
-  ...
-}
-
-```
-
-PlatformIO Library Dependency Finder will find automatically dependent
-libraries scanning project source files.
-
-More information about PlatformIO Library Dependency Finder
-- https://docs.platformio.org/page/librarymanager/ldf.html

vscode/clock/platformio.ini

@@ -1,15 +0,0 @@
-;PlatformIO Project Configuration File
-;
-;   Build options: build flags, source filter
-;   Upload options: custom upload port, speed and extra flags
-;   Library options: dependencies, extra library storages
-;   Advanced options: extra scripting
-;
-; Please visit documentation for the other options and examples
-; https://docs.platformio.org/page/projectconf.html
-
-[env:nanoatmega328]
-platform = atmelavr
-board = nanoatmega328
-framework = arduino
-

vscode/clock/src/clock.cpp

@@ -1,109 +0,0 @@
-#include <Adafruit_NeoPixel.h>
-#include <Wire.h> // must be included here so that Arduino library object file references work
-#include <RtcDS3231.h>
-
-void update_clock();
-void showpixel(float centerposf, int pixelwidth, unsigned long color);
-
-RtcDS3231<TwoWire> Rtc(Wire);
-
-#define PIN        6 // Which pin on the Arduino is connected to the NeoPixels?
-const int NUMPIXELS = 83; // How many NeoPixels are attached to the Arduino?
-
-Adafruit_NeoPixel pixels(NUMPIXELS, PIN, NEO_GRB + NEO_KHZ800);
-
-unsigned long color_on, color_off, color_sec, color_min, color_hour, color_hour_over;
-
-const float seconds2pixel = NUMPIXELS /60.0;
-
-void setup() {
-  Serial.begin(9600);
-  Rtc.Begin();
-  pixels.begin(); // INITIALIZE NeoPixel strip object (REQUIRED)
-
-
-  color_on = pixels.Color(0, 0, 255);
-  color_off = pixels.Color(0, 0, 0);
-  color_sec = pixels.Color(0, 255, 0);
-  color_min = pixels.Color(0, 0, 255);
-  color_hour = pixels.Color(255, 0, 0);
-  color_hour_over = pixels.Color(128, 0, 0);
-
-  pixels.fill(color_off);
-  pixels.show();
-  
-}
-
-int last_second = 0;
-int second = 0;
-int minute = 0;
-int hour = 0;
-
-void update_clock()
-{
-  if(last_second != second)
-  {
-  
-    Serial.print("Now is -> ");
-    Serial.print(hour);
-    Serial.print(":");
-    Serial.print(minute);
-    Serial.print(":");  
-    Serial.println(second);
-    
-    last_second = second;
-    // first delete all ...
-    pixels.fill(color_off);
-
-    for(int pixel = 1; pixel < hour; pixel++)
-    {
-      showpixel(seconds2pixel  * pixel, 1,  color_hour_over);
-    }
-    showpixel(seconds2pixel  * hour, 3,  color_hour);
-    showpixel(seconds2pixel  * minute, 5,  color_min);
-    showpixel(seconds2pixel  * second, 3,  color_sec);
-    
-
-    pixels.show();   // Send the updated pixel colors to the hardware.
-  }    
-}
-
-int pixel2numpixels(int pixel)
-{
-  if(pixel >= NUMPIXELS)
-  {
-    pixel = pixel - NUMPIXELS;
-  }
-  return pixel;
-}
-
-
-void showpixel(float centerposf, int pixelwidth, unsigned long color)
-{
-  int centerpixelpos = round(centerposf);
-  int pixelcenter = round((float)pixelwidth/2.0);
-  int pixelpos[pixelwidth] = {0};
-
-  for(int pixel = 0; pixel < pixelwidth; pixel++)
-  {
-    int pixeloffset = pixel - pixelcenter;
-    pixelpos[pixel] = pixel2numpixels(centerpixelpos + pixeloffset);
-    Serial.println(pixelpos[pixel]);
-    pixels.setPixelColor(pixelpos[pixel], color);
-  }
-}
-  
-RtcDateTime now;
-
-void loop() {
-
-  now = Rtc.GetDateTime();
-  hour = now.Hour();
-  minute = now.Minute();
-  second = now.Second();
-
-  //RtcTemperature temp = Rtc.GetTemperature();
-  update_clock();
-
-  
-}

vscode/clock/test/README

@@ -1,11 +0,0 @@
-
-This directory is intended for PIO Unit Testing and project tests.
-
-Unit Testing is a software testing method by which individual units of
-source code, sets of one or more MCU program modules together with associated
-control data, usage procedures, and operating procedures, are tested to
-determine whether they are fit for use. Unit testing finds problems early
-in the development cycle.
-
-More information about PIO Unit Testing:
-- https://docs.platformio.org/page/plus/unit-testing.html