Skip to main content

Javascript 30 Notes for Day 1, 2.

I'm actually on Day 6, but I like to have a good buffer to go over notes and make sure everything is uploaded to GitHub properly when completed.

This is Wes Bos' JavaScript 30, sent to me by a good friend, and I'm going to be doing this every day for a month.

Then, probably doing them again.

Day 1, we made a soundboard; GitHub files. Day 2, It's a clock...but no files.




data attributes (data-___) data key to data key  audio (find audio and play it, find div so it can animate itself)

line 61 - we’re listening for an event.
the code won’t have any reaction on the screen, but in the console it will.

audio.current time =0; rewinds it back to the beginning so you can wail on the buttons like a madman

audio.play(); plays the noises

in css, see transition:all, which scales up the border color. You can put a timeout in both the html and css, but they may go out of sync.

I changed my colors to hexidecimal code #afcd38

in the remove transition function (

if(e.propertyName !== 'transform') return;

this.classList.remove('playing'); 

)

When you go to Elements, to the keys div class, and press a corresponding letter, you can very quickly see the classes change.


If you press and hold the corresponding buttons, you can get the animation stuck in permanent ‘on’ mode.

Day 2; There's no code files because I still haven't gotten my clock to move, and I'm not sure why.





 * a rotate on each hand depending on the time
  • transform-origin
Have to adjust the axis via the origin (100% among the x-axis to put us on the very right hand side (or, the middle of a clock)

  • transform: rotate
rotate the entire thing by default 90 to start at 12:00, and the second hand transform with rotate gets a snappy tick.

But since default is left to right instead of top to bottom, it needs to be offset.

  • transition
 to 0.05 seconds

There’s a weird little backwards transition when the minute hand hits 12 all the hands kind of freak out for a second as the degrees go backward.

We can temporarily take off the transition with some if statements.

  • transition-timing-function
 (you can make it go backwards, or make a cool little bounce. Let’s make the bounce.)

Establish your secondhand with a const and document.queryselector.

SetDate function
run it every second with setInterval (setdate, 1000);

const statements of now, seconds, and secondsDegree

0 seconds = 0 degrees
60 seconds  = 360 degrees.

(Though I suppose it should be 60 seconds is also 360 degrees)

Pull it into the function and tell it to transform via rotation.



EMPLOYERS: This is me sharing notes and putting new skills into practice.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.